Nokia Customer Care RH-21 Series Transceivers Troubleshooting Issue 2 07/2004 2004 Nokia Corporation.
RH-21 Troubleshooting Page 2 Company Confidential Nokia Customer Care 2004 Nokia Corporation.
Company Confidential Nokia Customer Care RH-21 Troubleshooting Contents Page No Troubleshooting ............................................................................................................. 5 Baseband Troubleshooting ..........................................................................................5 General testing information....................................................................................... 5 Troubleshooting ...................................................
RH-21 Troubleshooting Page 4 Company Confidential Nokia Customer Care 2004 Nokia Corporation.
Company Confidential Nokia Customer Care RH-21 Troubleshooting Troubleshooting The first thing to do when a problem is encountered is to carry out a thorough visual check of the module. Make sure that: • there are no mechanical damages • the solder joints are OK Note: Before changing anything, ALL SUPPLY VOLTAGES AND THE SYSTEM CLOCK / SLEEP CLOCK should be checked. Baseband Troubleshooting General testing information There are three different modes for testing and/or repairing the phone.
RH-21 Troubleshooting Company Confidential Nokia Customer Care Troubleshooting Note: Most of the baseband repair actions require removing the baseband shield. The shield must not be removed unless separately authorized by the program. Note: The phone’s ESN has to re-written to the UEM, if the UEM is replaced. This can be done only in Central Service.
Company Confidential Nokia Customer Care • RH-21 Troubleshooting Supply voltages stabilize to their UEM HW default values • RFCLK grows to full swing • The core is ready to run but waiting for the PURX release • Reset releasing • The UPP releases the SLEEPX up to the "non sleep" state to prevent the UEM switching the regulators "OFF" 2 MCU starts running the Bootstrap Code • written in stone/ UPP internal ROM • the program checks if there is any reason for the FDL mode (Flash Down Load) • If
RH-21 Troubleshooting Company Confidential Nokia Customer Care 1 Power key pressed • After 20ms, UEM enters RESET MODE if VBAT>Vmstr+ • VFLASH1, Vana, Vcore, Vio, and VR3 goes high • VCTCXO enabled by VR3 -> RFClk 19.44 MHz running 2 Purx released • Purx released by UEM, UEMINT goes high for 100 ms, SleepX goes high, and SleepClk (32 KHz) starts running. 3 Software running • Default value for Vcore is 1.5 volts and, if software is running, Vcore will rise to 1.8 volts • Cbus (1.
Company Confidential Nokia Customer Care RH-21 Troubleshooting Figure 2: Fault tree, phone does not power up Issue 2 07/2004 2004 Nokia Corporation.
RH-21 Troubleshooting Company Confidential Nokia Customer Care Flash Programming does not work Flash programming procedure 1 The phone communicates with the prommer via the production test pattern, using the following signals: • FBUSTX (serial data to phone) • FBUSRX (serial data from phone) • MBUS (serial clock for FBUSRX) • VPP (External flashing voltage for speed up flashing) • The BSI line is also used when initializing flashing (battery connec- tor) 2 When the phone is powered (VBAT>3V), t
Company Confidential Nokia Customer Care RH-21 Troubleshooting Flash/Alignment phase. Flash programming error codes The various error codes can be seen from the "FPS-8 Flash" in Phoenix. The underlined text in the following table means that the item under consideration is being used for the first time in the flashing sequence. Error Description Not working properly C101 "The Phone does not set FbusTx line high after the startup." Vflash1 VBatt BSI and FbusRX from prommer to UEM.
RH-21 Troubleshooting Company Confidential Nokia Customer Care C107 "The Phone MCU can not start Secondary code correctly." UPP C586 "The erasing status response from the Phone informs about fail." Flash C686 "The programming status response from the Phone informs about fail." Flash Cx81 "The Prommer has detected a checksum error in the message, which it has received from the Phone.
Company Confidential Nokia Customer Care RH-21 Troubleshooting Figure 3: Fault tree, charging Audio failures In case of audio failures, there are three possibilities to check the audio lines. 1 Make a phone call against tester and check audios. 2 If the earpiece/XMIC fails: Feed a 1Khz signal to the XMIC line and measure the signal from the earpiece line. The Audio test box JBA-8 is needed. The Audio loop (Audio test/Ext In Hp Out) must be switched on by the Phoenix service software.
RH-21 Troubleshooting 3 Company Confidential Nokia Customer Care Run the audio-loop self-test with Phoenix (BB Self Tests/ ST_EAR_DATA_LOOP_TEST). This loop will test the ear-data/mic-data lines between the UPP and the UEM. Earpiece or external microphone line does not work Figure 4: Fault tree, earpiece failure Page 14 2004 Nokia Corporation.
Company Confidential Nokia Customer Care RH-21 Troubleshooting Microphone or XEAR line does not work Figure 5: Fault tree, microphone failure Accessory detection 1 Start the phone in the normal mode when checking for accessory detection. 2 The Ad-converter value of the hookint-line can be checked with the Xmic switch on an MJ-8 test jig. Changes normally from high to low when no accessory is connected. 3 When the headset HDC-5 is connected, the hookint-value should be between 600 and 800.
RH-21 Troubleshooting Company Confidential Nokia Customer Care Figure 6: Fault tree, accessory detection Sleep Clock Missing/nonfunctional sleep clock causes • Entering sleep mode fails (higher current consumption -> shorter standby time) Page 16 • Baseband self-tests cannot be run • Phone clock (on display) does not function properly 2004 Nokia Corporation.
Company Confidential Nokia Customer Care RH-21 Troubleshooting Figure 7: Fault tree, sleep clock Issue 2 07/2004 2004 Nokia Corporation.
RH-21 Troubleshooting Company Confidential Nokia Customer Care User Interface Display/Keyboard lights do not work Figure 8: Fault tree, Display/Keyboard lights Page 18 2004 Nokia Corporation.
Company Confidential Nokia Customer Care RH-21 Troubleshooting Display does not work Figure 9: Fault tree, Display does not work Issue 2 07/2004 2004 Nokia Corporation.
RH-21 Troubleshooting Company Confidential Nokia Customer Care MIDI does not work Check speaker B180 and the following components: N180, R100, R181, R182, R183, R184, C183, C180, C184, C181, C182, C179, L180, and L181 • No sound: Try using a known good SALT speaker instead. If there is still no sound, change the UEM (D200) • Weak sound: Use the Audio test in Phoenix to set the SALT speaker parameters (frequency, strength). If it does not affect the sound level, change the SALT speaker.
Company Confidential Nokia Customer Care RH-21 Troubleshooting (Antenna/ext RF) – Diplexer – Duplexer – Low Noise Amplifier (LNA) – RX band filter – First mixer – 135.54 MHz RX IF filter – IF-amplifier – second mixer – 14 kHz low-pass filter – adjustable IQ amplifier – Baseband. Fault-finding charts for receiver chain AMPS Figure 10: Fault tree, AMPS Issue 2 07/2004 2004 Nokia Corporation.
RH-21 Troubleshooting Page 22 Company Confidential Nokia Customer Care 2004 Nokia Corporation.
Company Confidential Nokia Customer Care N N Check RF level at RX IF filter input at 135.54 MHz RH-21 Troubleshooting Check RF level at J751 and J752 at 2034.06 MHz Start synthesizer troubleshoot Y Y Note ! Change SAFARI (N801) Check all discrete components and voltages around SAFARI N Check RF level at RX IF filter output at 135.
RH-21 Troubleshooting Company Confidential Nokia Customer Care TDMA800 Since the same physical signal path is used for both analog and digital modes at the lower band, there is no need for additional troubleshooting in the digital mode. So if the digital mode at the lower band is not working properly, start the analog mode troubleshooting. TDMA1900 (only dualband) Only EXT RF connector –> 1st IF needs separate troubleshoot at upper band. After down conversion (RF –> 135.
Company Confidential Nokia Customer Care Issue 2 07/2004 2004 Nokia Corporation.
RH-21 Troubleshooting Company Confidential Nokia Customer Care Table 2: Flash programming error codes Error Description Not working properly C101 "The Phone does not set FbusTx line high after the startup." Vflash1 VBatt BSI and FbusRX from prommer to UEM. FbusTx from UPP->UEM->Prommer(SA0) C102 "The Phone does not set FbusTx line low after the line has been high. The Prommer generates this error also when the Phone is not connected to the Prommer.
Company Confidential Nokia Customer Care RH-21 Troubleshooting C103 "Boot serial line fail." Mbus from Prommer->UEM>UPP(MbusRx)(SA1) FbusRx from Prommer->UEM>UPP FbusTx from UPP->UEM->Prommer C104 "MCU ID message sending failed in the Phone." FbusTx from UPP->UEM->Prommer C105 "The Phone has not received Secondary boot codes length bytes correctly.
RH-21 Troubleshooting Company Confidential Nokia Customer Care Cx87 "Wrong MCU ID." RFClock UPP(Vcore) Startup for flashing Required startup for flashing Vflash1 VBatt Page 28 2004 Nokia Corporation.
Company Confidential Nokia Customer Care RH-21 Troubleshooting Transmitter fault-finding General instructions for TX troubleshooting Always use RF cable connected from external RF connector to analyzer via (rf-power) attenuator. This is important to protect analyzer against excessive rf-power and not to let leak unwanted rf-power to the cellular frequencies. Start Phoenix software and select TX mode under testing (AMPS, DAMPS, or TDMA1900).
RH-21 Troubleshooting Page 30 Company Confidential Nokia Customer Care 2004 Nokia Corporation.
Company Confidential Nokia Customer Care RH-21 Troubleshooting TDMA800 The transmitter chain is exactly the same as AMPS mode, with the exception of the IPA current. Therefore it is important that AMPS has no faults. Issue 2 07/2004 2004 Nokia Corporation.
RH-21 Troubleshooting Company Confidential Nokia Customer Care TDMA1900 (only dualbander) TDMA1900 mode and DAMPS mode have a common RF modulator, making it important that the DAMPS mode has no faults. Power control loop Basically power detection is done with the Power detector module and power control is done inside Safari. Power detection is basically similar for both bands, except both bands have individual couplers. Page 32 2004 Nokia Corporation.
Company Confidential RH-21 Troubleshooting Nokia Customer Care N Is PWRDET vs. output power OK? See chart below. Check VR2 and RFTEMP . Check C930, C931 and PWRDET module. Note ! See PWRDET vs. Output power curve Y N Is DAC value vs. PWRDET (mV) OK? Check UEM (BaseBand) Detected voltages are described in the next table and diagram. TYPICAL DETECTED VOLTAGES AT POWER LEVELS PL2…PL10 FOR DUALBANDER 800A PL 2 3 4 5 6 7 8 9 10 Pout TXPWRDET dBm dac mV 26.5 633 1671 22.5 393 1038 18.5 237 625 14.
RH-21 Troubleshooting Company Confidential Nokia Customer Care 2000 1800 Detected voltage [mV] 1600 1400 1200 800A 800D 1000 1900D 800 600 400 200 0 2 4 6 8 10 P o w e r le ve l TYPICAL DETECTED VOLTAGES AT POWER LEVELS PL2…PL10 FOR SINGLE BANDER 800A PL 2 3 4 5 6 7 8 9 10 Pout TXPWRDET dBm dac mV 25.5 559 1475 21.5 388 1023 17.5 234 618 13.5 140 371 9.5 81 215 5.5 45 120 - 800D Pout TXPWRDET dBm dac mV 27.3 671 1771 23.3 465 1228 19.3 281 742 15.3 168 445 11.3 98 258 7.3 54 144 3.
Company Confidential RH-21 Troubleshooting Nokia Customer Care 2000 1800 Detected voltage [mV] 1600 1400 1200 800A 1000 800D 800 600 400 200 0 2 3 4 5 6 7 8 9 10 P o w e r le ve l Synthesizer fault-finding There are four oscillators generating the needed frequencies for the RF section: 19.44 MHz reference oscillator, 2GHz UHF VCO, TX VHF cascade amplifier VCO, and RX VHF VCO integrated in Safari. RX VHF frequency is fixed at 271.08 MHz and TX VHF has two fixed frequencies: 361.
RH-21 Troubleshooting Company Confidential Nokia Customer Care Fault-finding chart for 19.44 MHz oscillator 2 Change VCTCXO OK 2.No START HERE! Is VCTCXO oscillating? 19.44MHz 1.No OK! OK 1 Check voltage C792 2.78 V No OK Check resistor R792 Page 36 2004 Nokia Corporation.
Company Confidential Nokia Customer Care RH-21 Troubleshooting RX VHF VCO The RX VHF VCO signal is used to generate receiver Intermediate frequency. RX VHF VCO has one fixed frequency (271.08 MHz). Operating frequency is locked in Phase-locked loop. RX VHF VCO output signal is fed to Safari. The inside of the Safari signal is divided into the Phase detector and RX parts. Before I/Q modulator frequency is divided by 2. Fault-finding chart for RX VHF VCO Measure oscillator frequency over L730 coil.
RH-21 Troubleshooting Company Confidential Nokia Customer Care TX VHF VCO The TX VHF VCO signal is used to generate transmitter Intermediate frequency. TX VHF VCO has two fixed frequencies (361.08 MHz for lower band and 363.6 MHz for upper band). Operating frequency is locked in Phase-locked loop and frequency is divided by two before modulator. Fault-finding chart for TX VHF VCO AMPS, CH383 -> TX VHF frequency 361.08 MHz TDMA1900, CH1000 -> TX VHF frequency 363.
Company Confidential Nokia Customer Care RH-21 Troubleshooting of the VCO depends on the DC control voltage, which is controlled by the PLL circuit inside Safari. Fault-finding chart for UHF Synthesizer Issue 2 07/2004 2004 Nokia Corporation.
RH-21 Troubleshooting Page 40 Company Confidential Nokia Customer Care 2004 Nokia Corporation.
