CCS Technical Documentation RH-17 Series Transceivers Troubleshooting — BB Issue 1 04/2003 Confidential Nokia Corporation
RH-17 Troubleshooting — BB Page 2 Nokia Corporation CCS Technical Documentation Confidential Issue 1 04/2003
RH-17 Troubleshooting — BB CCS Technical Documentation Contents Page No Troubleshooting - Baseband .......................................................................................... 5 Overview ......................................................................................................................5 BB and RF Architecture ..............................................................................................6 Power Up and Reset ...................................................
RH-17 Troubleshooting — BB Page 4 Nokia Corporation CCS Technical Documentation Confidential Issue 1 04/2003
RH-17 Troubleshooting — BB CCS Technical Documentation Troubleshooting - Baseband Overview The Baseband module of RH-17 transceiver is a CDMA single band engine. The Baseband architecture is based on the DCT4 Apollo engine. RH-17 Baseband consists of three ASICs: Universal Energy Management (UEM), Universal Phone Processor (UPP), and a 64-megabit Flash. The Baseband architecture supports a power-saving function called “sleep mode”.
RH-17 Troubleshooting — BB CCS Technical Documentation BB and RF Architecture VBatt PRODTP VPP Battery ExtBusC Flash Charger Bottom Conn. MBus UEM UPP VIO VCORE FBusRx VANA FBusTx VR1A VR1B CBus DBus VR2 VR3 Vflash2 MBus VR4 Sleep Clk 32 KHz Core Vflash1 FBus VR5 VR6 VR7 VCTCXO 19.2 MHz RF Bus Front End LCD/Key UHF SYNTH Robin Batman PA VBatt Figure 1: RH-17 Power Distribution Power Up and Reset Power up and reset is controlled by the UEM ASIC.
RH-17 Troubleshooting — BB CCS Technical Documentation 3 By the RTC Alarm, when the RTC logic has been programmed to give an alarm After receiving one of the above signals, the UEM counts a 20ms delay and then enters in reset mode. The watchdog starts up, and if the battery voltage is greater than Vcoff+, a 200ms delay is started to allow references etc. to settle. After this delay elapses the VFLASH1 regulator is enabled. Then, 500us later VR3, VANA, VIO and VCORE are enabled.
RH-17 Troubleshooting — BB CCS Technical Documentation Reference signal PwrOnX Charger Detection RTC UEMRSTX VFlash1 VIO VCORE VANA VR3 19.
RH-17 Troubleshooting — BB CCS Technical Documentation Power up with PWR key When the Power on key is pressed, the UEM enters the power-up sequence. Pressing the power key causes the PWRONX pin on the UEM to be grounded. The UEM PWRONX signal is not part of the keypad matrix. The power key is only connected to the UEM. This means that when pressing the Power key, an interrupt is generated to the UPP that starts the MCU.
RH-17 Troubleshooting — BB CCS Technical Documentation The Power-down procedure is controlled by the UEM. Power Consumption and Operation modes During power off mode, power (VBAT) is supplied to UEM, BUZZER, VIBRA, LED, PA and PA drivers (Tomcat and Hornet). During this mode, the current consumption on this mode is approximately 35uA. In sleep mode, both processors, MCU and DSP, are in stand-by mode. Phone will go to sleep mode only when both processors made this request.
RH-17 Troubleshooting — BB CCS Technical Documentation the UEM switch off, when the battery voltage has reached 4.2 V. Charging current is monitored by measuring the voltage drop across a 220 mOhm resistor. Power Distribution In normal operation the baseband is powered from the phone‘s battery. The battery consists of one Lithium-Ion cell. In the case of RH-17, the battery capacity is 850 mAh.
RH-17 Troubleshooting — BB CCS Technical Documentation Table 2: RH-17 RF Regulators Regulator Maximum current [mA] Vout [V] Notes VR1A 10 4.75 Enabled when the receiver is on VR1B 10 4.75 Enabled when the transmitter is on VR2 100 2.78 Enabled when the transmitter is on VR3 20 2.78 Enabled when SleepX is high VR4 50 2.78 Enabled when the receiver is on VR5 50 2.78 Enabled when the receiver is on VR6 50 2.78 Enabled when the transmitter is on VR7 45 2.
RH-17 Troubleshooting — BB CCS Technical Documentation RFConvClk (19.2 MHz digital) The UPP distributes the 19.2MHz Clk to the internal processors, the DSP and MCU, where SW multiplies this clock by seven for the DSP and by two for the MCU. CBUSClk Interface A 1.2 MHz clock signal is use for CBUS, which is used by the MCU to transfer data between UEM and UPP.
RH-17 Troubleshooting — BB CCS Technical Documentation DBUSClk Interface A 9.6 MHz clock signal is use for DBUS, which is used by the DSP to transfer data between UEM and UPP. The system clock can stopped during sleep mode by disabling the VCTCXO power supply from the UEM regulator output (VR3) by turning off the controlled output signal SleepX from UPP. SLEEPClk (Digital) The UEM provides a 32kHz sleep clock for internal use and to UPP, where it is used for the sleep mode timing.
RH-17 Troubleshooting — BB CCS Technical Documentation SLEEPClk (Analog) However, when the system enters sleep mode or power-off mode, the external 32KHz crystal provides a reference to the UEM RTC circuit to turn on the phone during power-off or sleep mode.
RH-17 Troubleshooting — BB CCS Technical Documentation Flash programming Connections to Baseband The Flash programming equipment is connected to the baseband using test pads for galvanic connection. The test pads are allocated in such a way that they can be accessed when the phone is assembled. The flash programming interface consist of the VPP, FBUSTX, FBUSRX, MBUS, and BSI signals and use by the FPS8 to flash.
RH-17 Troubleshooting — BB CCS Technical Documentation note a falling edge is required to load the compare register. Flashing • Flash programming is done through VPP, FBUSTX, FBUSRX, MBUS and BSI signals. • When phone has entered to flash programming mode, prommer will indicate to UEM that flash programming will take place by writing 8-bit password to UEM. Prommer will first set BSI to "1" and then uses FBUSRX for writing and MBUS for clocking. After that BSI is set back to "0”.
RH-17 Troubleshooting — BB CCS Technical Documentation FLASH_2 CH1 CH2 CH3 CH4 = = = = PURX MBUS FBUSTX FBUSRX M easure points Production test pattern (J396) FLASH_3 CH1 CH2 CH3 CH4 = = = = PURX MBUS FBUSTX FBUSRX Measure points Production test pattern (J396) Data transfer has started (Fbus_Rx) Charging operation Battery In RH-17, a Lithium-Ion cell battery with a capacity of 850 mAh is used. Reading a resistor inside the battery pack on the BSI line indicates the battery size.
RH-17 Troubleshooting — BB CCS Technical Documentation BTEMP line. Temperature and capacity information are needed for charge control. These resistors are connected to BSI pin of the battery connectore and BTEMP of the phone. Phone has 100 kΩ pull-up resistors for these lines so that they can be read by A/D inputs in the phone.
RH-17 Troubleshooting — BB CCS Technical Documentation R200 V100 battery Figure 4: Charging circuitry Charger Detection Connecting a charger creates voltage on VCHAR input of the UEM. When VCHAR input voltage level is detected to rise above 2 V (VCHdet+ threshold) by UEM charging starts. VCHARDET signal is generated to indicate the presence of the charger for the SW. The charger identification/acceptance is controlled by EM SW.
RH-17 Troubleshooting — BB CCS Technical Documentation Charge Control In active mode, charging is controlled by UEM’s digital part. Charging voltage and current monitoring is used to limit charging into safe area. For that reason UEM has programmable charging cut-off limits: VBATLim1=3.6 V (Default) VBATLim2L=5.0 V and VBATLim2H=5.25 V. VBATLim1, 2L, 2H are designed with hystereses. When the voltage rises above VBATLim1, 2L, 2H+ charging is stopped by turning charging switch OFF.
RH-17 Troubleshooting — BB CCS Technical Documentation LCD and four LEDs for the keypad. The signal use to drive the LED driver for the LCD and keyboard is KLIGHT. Black/White LCD is used in RH-17. Interface is using 9-bit data transfer. The interface is quite similar to DCT3 type interface except Command/Data information is transferred together with the data. D/C bit set during each transmitted byte.
RH-17 Troubleshooting — BB CCS Technical Documentation 1 Charger 2 Charger GND 3 ACI 4 Vout 5 USB Vbus 6 USB D+ / Fbus Rx 7 USB D- / Fbus Tx 8 Data GND 9 XMic N 10 XMic P 11 HSear N 12 HSear P 13 HSear R N 14 HSear R P In Tomahawk accessories, we can perform the following functions: Charging, Accessory detection, FBUS communication, USB communication, and fully differential audio interface for mono and stereo outputs. These modes will be explained on the following sections.
RH-17 Troubleshooting — BB CCS Technical Documentation CH4 = PURX In Channel 4, we can see that PURX is release and this is when the phone operation goes from “RESET” mode to “POWER_ON” mode. Tomahawk headset detection Accessory detection on Tomahawk is done digitally.
RH-17 Troubleshooting — BB CCS Technical Documentation FBus detection FBus communication in Tomahawk is done through the following lines: Pin 2 (Charge GND) Pin 3 (ACI) Pin 4 (Vout) Pin 6 (FBus Rx) Pin 7 (FBus Tx) A waveform for such communication is shown: Issue 1 04/2003 Nokia Corporation Confidential Page 25
RH-17 Troubleshooting — BB CCS Technical Documentation Accessory detection though ACI USB and Audion (mono or stereo) and FM radio communication in Tomahawk is done through the following signals: USB Audio/FM Pin 5 (USB Vbus) Pin 9 (XMic N) Pin 6 (USB +) Pin 10 (SMIC P) Pin 7 (USB -) Pin 11 (HSEAR N) Pin 8 (Data GND) Pin 12 (HSEAR P) Pin 13 (HSEAR R N) Pin 14 (HSEAR R P) Page 26 Nokia Corporation Confidential Issue 1 04/2003
RH-17 Troubleshooting — BB CCS Technical Documentation A waveform showing such interface is shown in the following figure: RUIM (SIM Car) RH-17 will support RUIM for China products. The waveform below can be use to verify that sim_vcc; sim_i/o, sim_clk and sim_rst signals are activated in the correct sequence at power-up. This picture can be takan when the RUIM is install on the phone and measue the signals when the phone is turned on.
RH-17 Troubleshooting — BB CCS Technical Documentation . Figure 7: RUIM Signal Waveform Test Points RH-17 (Haukka) BB test points, regulators, and BB ASICs.
RH-17 Troubleshooting — BB CCS Technical Documentation Top View Issue 1 04/2003 Nokia Corporation Confidential Page 29
RH-17 Troubleshooting — BB Page 30 Nokia Corporation CCS Technical Documentation Confidential Issue 1 04/2003
RH-17 Troubleshooting — BB CCS Technical Documentation Bottom View Troubleshooting The following hints should help to find the cause of the problems when the circuitry seems to be faulty. This troubleshooting instruction is divided into the following sections. 1. Top troubleshooting map 2. Phone is totally dead 3. Power doesn‘t stay on or the phone is jammed 4. Flash programming doesn‘t work 5. Display is not working 6. Audio fault 7.
RH-17 Troubleshooting — BB CCS Technical Documentation Top troubleshooting map Top P lly ta to e n ad ho de YES Phone dead NO g in m m k r ra o og w pr 't h esn s a o Fl d YES Flash faults YES Phone is jammed NO t n' e es on do ph d e r on p o me Ph rt u jam a st is NO Charger h C e do n g rk i g o ar w 't sn YES NO Page 32 Nokia Corporation Top 2 Confidential Issue 1 04/2003
RH-17 Troubleshooting — BB CCS Technical Documentation YES Audio faults Au dio fa ult s Top 2 NO s D LE g r n o i y rk la wo isp ot D n YES Display faults Ke yp ad wo do rk esn 't NO YES Keypad faults END Issue 1 04/2003 Nokia Corporation Confidential Page 33
RH-17 Troubleshooting — BB CCS Technical Documentation Phone is totally dead Phone is dead - If current is zerro check X101 make sure Vbatt connector makes contact. -If current is too high check for shorts - Make sure all BB regulators are at their respective voltage levels like VANA, VIO, VCORE(DC-DC), VFlash1, and VR3. See phones top view diagram for test points. - Make sure the System Clk is 19.2MHz and that the Sleep Clk is 32KHz - Also make sure PURX and SleepX signals are high (1.8V).
RH-17 Troubleshooting — BB CCS Technical Documentation Flash programming doesn‘t work Flash faults The phone does not set Flashbus TXD line high after the startup. Yes Measure BSI pulse during Flash programing. Is it OK? Check BSI line X101, C230, R206, R203 No Yes Measure FBusRx (2.78V) signal during flash programing from production pattern and testpoint J412 (1.8V). Is it the same? No No Re-flow or Change UEM Change UPP No Yes Measure test point FBusTx (J411) (1.
RH-17 Troubleshooting — BB CCS Technical Documentation Flash Faults page 2 Can you read the manufactor ID and the Device ID? No Re-flow or Change Flash Yes Is the phone totally dead? Yes No Phone doesn't start up or the phone is jammed? Yes No Retest Page 36 Nokia Corporation Confidential Issue 1 04/2003
RH-17 Troubleshooting — BB CCS Technical Documentation Power doesn‘t stay on or the phone is jammed Phone is jammed Measure VIO, VCORE, Vflash1, VANA, and VR3 votages. Are they OK ? Check VBATT, VIO, VCORE, VFlash1, VANA, VR3 capacitors. Are they OK ? See phones top view diagram for cap location. Yes Check BSI/BTEMP lines and VBATT lines if OK re-flow or change UEM No No Repair Yes Measure 32kHz Sleep Clk from testpoint . Is it OK? No Measure the 32kHz Clk crystal.
RH-17 Troubleshooting — BB CCS Technical Documentation Jammed Page 2 Yes Phone shutdown after 32 seconds Has the phone being faslh? No Flash the phone Yes No Measure DBusClk 9.6MHz signal from testpoint J413. Is it OK? No No Re-flow or Change UPP and re-flash Yes Re-flow or Change UEM and re-flash Re-flow or Change UPP Yes Read phone info. Is it OK? Measure watchdog signal CBusDA from testpoint J407. Is it OK? No Yes Measure FBusRx signal during phone info read from testpoint J412.
RH-17 Troubleshooting — BB CCS Technical Documentation Charger Charger Connect Charger Make sure battery is connedted. Battery bar doesn't work (scroll) No Retest Yes Measure voltage over V100. Is it > 3.0 Vdc? No Check X102, F100, L100, V100, C106. Yes Read BTEMP value. Is it ~ 25C (0319)? No Change UEM Yes Remove (fuse) F100 and measure current.
RH-17 Troubleshooting — BB CCS Technical Documentation Audio faults Audio faults Is the earpiece working? Yes No Change earpiece. Is it working now? Yes Retest No Set phone in LOCAL mode. Use phoenix "Baseband Audio Control" and set the following: Enable Tx, Enable Rx, Select MIC2 (0dB), Enable earpiece and enable digital loop back only.
RH-17 Troubleshooting — BB CCS Technical Documentation Audio faults 2 Is the microphone working? No Change the michropone. Is it working now? Yes Retest No Yes Set phone in LOCAL mode. Use Phoenix "Baseband Audio Control" and set the following: Enable Tx, Enable Rx, Select MIC1, Enable HF only (differential). Talk throug the michrophone. Measure MICB1 voltage from MICP pads on bottom connector. Is it ~2.1V? No Check connections at C195 and R165. If OK change UEM.
RH-17 Troubleshooting — BB CCS Technical Documentation Audio faults 3 Is BUZZER working? No Measure VBATT voltage from B302. Is it OK? No Check VBATT line. Yes Yes Set phone in LOCAL mode. Use Phoenix "Baseband Audio Control". Under Buzzer on Frequency and Duty cycle input 20. Check signal on pin 2 of B302.
RH-17 Troubleshooting — BB CCS Technical Documentation Audio faults 4 No Is VIBRA working? Measure VBATT voltage pin 1 of M300. Is it OK? No Check VBATT line. Yes Yes Set phone in LOCAL mode. Use Phoenix "Message Sender" and navegate down as follows: DEV_HOST --> DEV_PC --> PN_ACCESSORY --> PN_OBJ_ROUTING_REQ --> PN_OBJ_PC --> UTID_100 --> ACC_VIBRA_CTRL_REQ. Select "ACC_ON" and click "Send' Measure the UEM signal on pin 2 of M300.
RH-17 Troubleshooting — BB CCS Technical Documentation Display faults Display faults Are the Keyboard LED's turned on when phone is turned on or when making a phone call? No Measure VBATT voltage at C313. Is it OK? No Check VBATT line and C311, C312, C313, C314, and R300. Yes Yes Set phone in LOCAL mode. Use Phoenix "Message Sender" and navigate down as follows: DEV_HOST --> DEV_PC --> PN_LIGHT --> OBJ_ROUTING_REQ --> OBJ_PC --> UTID --> LIGHT_CONTROL_REQ --> LIGHT_CONTROL_TARGER_K BD.
RH-17 Troubleshooting — BB CCS Technical Documentation Display faults 2 Are the Keyboard LED's turned on when phone is turned on or when making a phone call? No Measure VBATT voltage at C313. Is it OK? No Check VBATT line and C311, C312, C313, C314, and R300. Yes Yes Set phone in LOCAL mode. Use Phoenix "Message Sender" and navigate down as follows: DEV_HOST --> DEV_PC --> PN_LIGHT --> OBJ_ROUTING_REQ --> OBJ_PC --> UTID --> LIGHT_CONTROL_REQ --> LIGHT_CONTROL_TARGER_K BD.
RH-17 Troubleshooting — BB CCS Technical Documentation Display faults 3 Does the display start? No Try changing display module. Does is works? Yes Retest No Yes Set phone in LOCAL mode. Use Phoenix "Message Sender" and navegate down as follows: DEV_HOST --> DEV_PC --> PN_TEST --> OBJ_ROUTING_REQ --> OBJ_PC --> UTID --> TEST_UI_TEST_REQ --> TEST_DISPLAY_SET --> NUM_SB: --> TEST_SB_UI_DISPLAY_PATTE RN -->SB_LENGTH.
RH-17 Troubleshooting — BB CCS Technical Documentation Keypad faults Keypad faults Is the power key working? No Measure voltage at S300. Is it HIGH? No Check S300, C305 and R304. If OK change UEM. Yes Yes Measure voltage at S300 when power key is pressed. Is it HIGH? Yes No Check S300.
RH-17 Troubleshooting — BB CCS Technical Documentation Keypad faults 2 Are the UI modules keys working? No Change Keypads module. Is it working? Yes Retest No Yes Measure ROW0-4 (P10-P14) signals between UPP and X302. Are they ~1.8V? No Make sure there are no shorts on Z300. If OK change UPP. Yes Measure COL1-4 (P1-P4) signals between UPP and X302. Are they ~1.8V? No Change Z300. Yes Make sure there are no shorts on Z300. If OK change UPP.
