CCS Technical Documentation RH-34 Series Transceivers Troubleshooting - Baseband Issue 1 11/2003 Confidential ©2003 Nokia Corporation
RH-34 Troubleshooting - Baseband CCS Technical Documentation Contents Page No Troubleshooting Overview ............................................................................................ 4 Power Up and Reset .....................................................................................................6 Power up with PWR key ........................................................................................... 8 Power up when charger is connected ......................................
RH-34 Troubleshooting - Baseband CCS Technical Documentation Keypad faults .............................................................................................................47 Power key................................................................................................................ 47 UI modules .............................................................................................................. 48 FM Radio.................................................................
RH-34 Troubleshooting - Baseband CCS Technical Documentation Troubleshooting Overview The Baseband module of the RH-34 transceiver is a trimode CDMA dual band engine. The Baseband architecture is based on the DCT4 Apollo engine. RH-34 Baseband consists of three main ASIC's: Universal Energy Management (UEM), Universal Phone Processor (UPP), and a 128-Megabit FLASH. The Baseband architecture supports a power-saving function called "sleep mode".
RH-34 Troubleshooting - Baseband CCS Technical Documentation Issue 1 11/2003 Confidential ©2003 Nokia Corporation Page 5
RH-34 Troubleshooting - Baseband CCS Technical Documentation Power Up and Reset Power up and reset is controlled by the UEM ASIC. RH-34 baseband can be powered up in the following ways: 1 By the Power button, which means grounding the PWRONX pin of the UEM 2 By connecting the charger to the charger input 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.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Reference signal PwrOnX Charger Detection RTC UEMRSTX VFlash1 VIO VCORE VANA VR3 19.
RH-34 Troubleshooting - Baseband 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-34 Troubleshooting - Baseband CCS Technical Documentation Monitoring the VBAT voltage level is done by charge control block (CHACON). MSTRX='1' output reset signal (internal to UEM) is given to UEM's RESET block when VBAT>VMSTR+ and UEM enters into reset sequence. If VBAT is detected to fall below VMSTR- during start-up charging, charging is cancelled. It will restart if new rising edge on VCHAR input is detected (VCHAR rising above VCHDET+).
RH-34 Troubleshooting - Baseband CCS Technical Documentation In the ACTIVE mode, the phone is in normal operation, scanning for channels, listening to a base station, transmitting and processing information. There are several sub-states in the active mode depending on the phone present state such as: burst reception, burst transmission, if DSP is working etc. In active mode, SW controls the UEM RF regulators: VR1A and VR1B can be enabled or disabled. These regulators work of the UEM charge pump.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Table 1: RH-34 Baseband Regulators Maximum current (mA) Vout (V) Notes VCORE DD/DC 300 1.5 Output voltage selectable 1.0V/1.3V/1.5V/1.8V Default power at power-up is 1.5V VIO 150 1.8 Enabled always except during power-off mode VFLASH1 70 2.78 Enabled always except during power-off mode VFLASH2 40 2.78 Enabled only when data cable is connected VANA 80 2.
RH-34 Troubleshooting - Baseband CCS Technical Documentation RFConvClk (19.2 MHz digital) The UPP distributes the 19.2 MHz 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.
RH-34 Troubleshooting - Baseband CCS Technical Documentation CBUSClk Interface A 1.2 MHz clock signal is used for CBUS, which is used by the MCU to transfer data between UEM and UPP. DBUS Clk Interface A 9.6 MHz clock signal is used 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.
RH-34 Troubleshooting - Baseband CCS Technical Documentation SleepCLK (Digital) The UEM provides a 32kHz sleep clock for internal use and to UPP, where it is used for the sleep mode timing. SleepCLK (Analog) 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-34 Troubleshooting - Baseband 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-34 Troubleshooting - Baseband 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-34 Troubleshooting - Baseband CCS Technical Documentation .
RH-34 Troubleshooting - Baseband CCS Technical Documentation tor inside the battery pack on the BSI line indicates the battery size. NTC-resistor inside the battery measures the battery temperature on the BTEMP line. Temperature and capacity information are needed for charge control. These resistors are connected to BSI and BTEMP pins of battery connector. Phone has 100 kW pull-up resistors for these lines so that they can be read by A/D inputs in the phone.
RH-34 Troubleshooting - Baseband CCS Technical Documentation R200 V100 battery Figure 6: 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-34 Troubleshooting - Baseband X102 CCS Technical Documentation F100 2 L100 ________ "VCHARIN" 42R/100MHz 1.5A C106 V100 1 1n0 0 C110 2 22p CHARGER(4:0) Figure 7: Charging circuit 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.
RH-34 Troubleshooting - Baseband CCS Technical Documentation microphone; MIC2 input is used for headsets (HDB-4). MIC3 input is used for the Universal Headset. Every microphone input can have either a differential or single ended AC connection to UEM circuit. In RH-34, the internal microphone MIC1 and external microphone MIC2 for Tomahawk accessory detection are both differential. However, the Universal Headset interface is single-ended.
RH-34 Troubleshooting - Baseband CCS Technical Documentation TOMAHAWK System Connector UPP FM Radio Xtal1 HSEARN Stereo audio Amplifier HSEARP Audio R Data Audio L Clock HSEARRN FMClk FMCtrlDa FMCtrlClk FMWrEn HSEARRP W/R Genio(24) Genio(12) Genio(18) Genio(6) Rfin1 40pF 100P 68nH Antenna signal Figure 9: FM Radio (N356) Audio (N150)-, antenna- and digital interface connections Table 3: FM radio interface timing FM radio signal Min FMWrEn 20µs FMCtrlClk 50ms FMCtrlDa Nom Max Con
RH-34 Troubleshooting - Baseband CCS Technical Documentation Stereo Audio output signal are fed to Stereo Amplifier. Volume control of the FM audio signal is made by circuitry inside the amplifier. Amplified audio signal is fed to headset or IHF speaker. Headset is also used as antenna input for the radio. FM Radio Test To hear the FM radio, you first connect headset to Tomahawk or UHJ ports because the headset will be an FM radio antenna.
RH-34 Troubleshooting - Baseband CCS Technical Documentation FM Radio signals before Radio on Ch1 : FMClk(32.
RH-34 Troubleshooting - Baseband CCS Technical Documentation FM Radio signals after Radio on Accessory RH-34 is designed to support Tomahawk and Universal Headset accessories, differential and single-ended, respectively. Detection of Tomahawk accessories is done through the ACI signal where the Universal Headset is detected on GenIO (21). The following picture shows the pin out of the Tomahawk connector.
RH-34 Troubleshooting - Baseband 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 CCS Technical Documentation 10 XMic P 11 HSear N 12 HSear P 13 HSear R N 14 HSear R P In Tomahawk accessories, perform the following functions: Charging, Accessory detection, FBUS communication, USB communication, and fully differential audio interface for mono and stereo outputs. These modes are explained in the following sections.
RH-34 Troubleshooting - Baseband CCS Technical Documentation 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-34 Troubleshooting - Baseband 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 in the following figure: Page 28 ©2003 Nokia Corporation Confidential Issue 1 11/2003
RH-34 Troubleshooting - Baseband CCS Technical Documentation Accessory detection though ACI USB and Audi on (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) A waveform showing such interface is shown in the following figure: Issue 1 11/2003 Confidential ©2003 Nokia Corpora
RH-34 Troubleshooting - Baseband CCS Technical Documentation RUIM (SIM CAR) RH-34 supports RUIM for China products. The following waveform can be used 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 taken when the RUIM is installed on the phone and measures the signals when the phone is turned on. The following picture shows the proper waveforms when the interface is working.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Figure 10: RUIM signal waveform Test Points RH-34 BB test points, regulators, and BB ASICs.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Top view Page 32 ©2003 Nokia Corporation Confidential Issue 1 11/2003
RH-34 Troubleshooting - Baseband CCS Technical Documentation Bottom view Issue 1 11/2003 Confidential ©2003 Nokia Corporation Page 33
RH-34 Troubleshooting - Baseband CCS Technical Documentation Top troubleshooting map T op P hone totally dead YE S P hone dead YE S F las h faults YE S P hone is jammed YE S C harger faults NO F las h programming does n't work NO P hone does n't s tart up or phone is jammed NO C harging does n't work NO Page 34 ©2003 Nokia Corporation T op page 2 Confidential Issue 1 11/2003
RH-34 Troubleshooting - Baseband CCS Technical Documentation T op 2 A udio faults YE S A udio faults YE S Dis play faults YE S K eypad faults NO Dis play or L E Ds not working NO K eypad does n't work E ND Issue 1 11/2003 Confidential ©2003 Nokia Corporation Page 35
RH-34 Troubleshooting - Baseband CCS Technical Documentation Phone is totally dead Phone is dead Phone current is zero or too high? ¾ If current is zero, check X100 solder and 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 (VANA, VIO, VCORE, VFlash1, and VR3). See phone's top view diagram for test points. ¾ Make sure the System Clk is 19.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Flash programming doesn’t work Flash faults Phone does not set Flashbus TXD line high after startup YES Measure BSI pulse during Flash programming. Is it OK? NO Check BSI line X100, C230, R203, R202 YES Measure FBusRx (2.78V) signal during flash programming from production pattern and test point TP03 (1.8V).
RH-34 Troubleshooting - Baseband CCS Technical Documentation Flash faults, page 2 Reflow the flash. Is it OK? NO NO Can you read manufacturer ID and device ID? Reflow or change flash. Reflow the UPP.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Phone is jammed Phone is jammed Check VBATT, VIO, VCORE, VFlash1, VANA, VR3 capacitors. Are they OK? (See phone top view diagram for capacitor locations) NO Measure VIO, VCORE, VFlash1, VANA, and VR3 voltages. Are they OK? YES Check BSI/BTEMP lines and VBATT lines. If OK, change UEM Repair NO YES Measure 32kHz Sleep Clk from test point J974 and J975. Is it OK? Measure 32kHz Clk crystal.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Power doesn’t stay on or the phone is jammed Phone is jammed, page 2 Phone shutdown after 32 seconds YES Has the phone been flashed? Flash the phone NO YES NO Reflow or change UPP and re-flash NO Measure DBusClk (9.6MHz), Data, and EnX signals at TP13, TP11, TP09. Is it OK? YES NO Reflow or change UEM and re-flash Reflow or change UPP NO Read phone info. Is it OK? Measure watchdog signal Cbus from test points TP15, TP08, TP05.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Charger faults Charger faults Connect charger. Make sure battery is connected. Battery bar doesn't work (scroll) NO Retest NO Check X102, F100, L100, V100, C106, C110 NO Change UEM NO Change UEM YES Measure voltage over V100. Is it > 3.0 Vdc? YES Read BTEMP value. Is it ~25C (0319)? YES Remove (fuse) F100 and measure current.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Audio faults Earpiece Audio faults Is the earpiece working? 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 loopback only. Inject a 1KHz sine signal 20mVp-p on XMIC.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Microphone Audio faults, page 2 Is the microphone working? NO Change the microphone. 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 MIC1, Enable HF only (differential). Talk through the microphone. Measure MICB1 voltage from MICP pads on bottom connector. Is it ~2.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Vibra Audio faults, page 3 Is Vibra working? NO Measure VBATT voltage pin 1 of M300. Is it OK? NO Check VBATT line YES Set phone in Local Mode. Use Phoenix "Message Sender" and navigate 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" YES Measure the UEM signal on pin 2 of M300.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Display faults Display faults Are the Keyboard and LCD LEDs turned on when phone is turned on or when making a phone call? NO Measure VBATT voltage at R315. Is it OK? NO Check VBATT line at X100 connector and C109 YES Set phone to Local Mode. Use Phoenix "Message Sender" and navigate as follows: DEV_HOST--> DEV_PC-->PN_LIGHT--> OBJ_ROUTING_REQ-->OBJ_PC--> UTID-->LIGHT_CONTROL_REQ--> LIGHT_CONTROL_TARGER_KBD.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Display faults, page 2 Does the Display start? NO Try changing display module. Does it work? Retest YES NO YES Set phone in Local Mode. Use Phoenix "Message Sender" and navigate 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_PATTERN--> SB_LENGTH. Select "TEST_PATTERN_ALTPIXELS" and click "Send" Check VIO and VFlash1 at X302.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Keypad faults Power key Keypad faults Is the power key working? NO Measure voltage at R306. Is it high? NO Check S302, C310, and R306. If OK, change UEM YES Retest YES Measure voltage at R306 when power key is pressed.
RH-34 Troubleshooting - Baseband CCS Technical Documentation UI modules Keypad faults, page 2 Are UI modules keys working? NO Change keypads module. Is it working? YES Retest NO Make sure there are no shorts on Z300. If OK, change UPP NO Change Z300 NO Measure ROW0-4 (P10-P15) signals between UPP and X301. Are they ~1.8V? YES YES Measure COL1-4 (P01-P04) signals between UPP and X302. Are they ~1.
RH-34 Troubleshooting - Baseband CCS Technical Documentation FM Radio FM Radio faults Is the FM radio working? NO Power on the phone and turn FM radio on by Phoenix NO Check solder on N356, X101, and replace N356 if not working. NO Check VFlash2 line YES Measure VFlash2 (VCCD/VCCA/ VCCVCO) at C359/ C372/L357. Is it 2.8V? YES YES Does the FM radio produce a "Bong" sound when changing channels (frequencies)? Measure FM1=1.8V, FM2=11 Khz, FM3=1.8V, and FM4=32 Khz.
RH-34 Troubleshooting - Baseband CCS Technical Documentation FM Radio faults 2 Measure VREF at C365. Is it 1.6V? NO Check C365 NO Change FM Radio chip (N356) YES Measure VAFL/VAFR at C164/C168. Does it have an audio signal? Retest NO YES Is FM Radio working? YES END GPS Module Overview The GPS circuitry utilizes RF signals from satellites stationed in geosynchronous orbit to determine longitude and latitude of the handset.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Figure 11: GPS block diagram The basic GPS BB troubleshooting method is to put the GE and CE in the proper mode, then check to make sure that necessary inputs from the CE are good (power, clock, etc.). Then, ensure that these inputs produce the proper outputs. Because of the large level of integration (most functionality is contained in the two ASIC chips), the amount of diagnostics one is able to do is limited.
RH-34 Troubleshooting - Baseband CCS Technical Documentation Vcore at 1.5V? Troubleshoot CE power supply Vio at 1.8V? NO GPS_RF_CLK (19.2MHz) OK? NO Troubleshoot CE VCTCXO circuit GPS_EN_RESET is held high? NO BB ASIC being held in reset, troubleshoot source in the CE GPS_SLEEPCLK (32.768KHz) OK? NO Troubleshoot CE sleep clock circuit VRF_GPS OK? NO VRF_GPS regulator enable line low? NO Replace regulator (N052) GPS_CLK (16.
