CCS Technical Documentation RH-42 Series Transceivers Troubleshooting Instructions Issue 2 09/2003 Confidential Nokia Corporation
RH-42 Troubleshooting Instructions Page 2 Nokia Corporation CCS Technical Documentation Confidential Issue 2 09/2003
CCS Technical Documentation RH-42 Troubleshooting Instructions Contents Page No Transceiver Troubleshooting ......................................................................................... 5 Baseband Troubleshooting ..........................................................................................5 General testing........................................................................................................... 5 Troubleshooting ...................................................
RH-42 Troubleshooting Instructions Page 4 Nokia Corporation CCS Technical Documentation Confidential Issue 2 09/2003
RH-42 Troubleshooting Instructions CCS Technical Documentation Transceiver Troubleshooting First, carry out a thorough visual check of the module. Make sure that: • there is no mechanical damage • 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 The phone has three different modes for testing and/or repairing the phone.
RH-42 Troubleshooting Instructions CCS Technical Documentation The BB troubleshooting instructions consist of the following topics: 1 Power up 2 Flash programming 3 Audio • Earpiece • Microphone 4 Charging 5 Accessory detection 6 Sleep clock 7 User interface • Display • Lights • Buzzer • Keyboard Power up faults Power up sequence 1 The UEM acts as a HW master during start up • Vbatt limits: 2.
RH-42 Troubleshooting Instructions CCS Technical Documentation • 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 Bootsrap Code • Written in stone/ UPP internal ROM • The program checks if there is any reason for the FDL mode (Flash Down Load) • If there is an executable code in FLASH and there is no reason for FDL, the MCU starts running the MCU program from FLASH.
RH-42 Troubleshooting Instructions 1 CCS Technical Documentation 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 UEM starts feeding SleepClk (32 KHz) to UPP. Note: The sleepclock starts running in the crystal circuitry (B200) immediately when the battery voltage is supplied.
RH-42 Troubleshooting Instructions CCS Technical Documentation Try to start phone to test or local mode OK Check the power key OK FAIL OK Measure Vflash1, Vana, Vio, Vcore, VR3 when pwr key pressed Check R202, R206, R207, C220, C240 VANA and VR3 missing OK Check G790 (missing or misaligned) Check X101 FAIL FAIL Check 19.44MHz RF clock from C420 Measure VBAT from C261 Check C420 FAIL OK OK Check 19.
RH-42 Troubleshooting Instructions CCS Technical Documentation 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 connector).
RH-42 Troubleshooting Instructions CCS Technical Documentation 11 The FLASH Program includes a package of MCU and DSP software and all default parameters for the phone. The tuning values will be added/rewritten during the 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 table below means that the item under consideration is being used for the first time in the flashing sequence.
RH-42 Troubleshooting Instructions CCS Technical Documentation C383 C583 C683 "The Prommer has not received Phone acknowledge to the message." (C383-during algorithm download to target phone) (C583-during erasing) (C683-during programming) Flash UPP Signals between UPP-Flash C384 C584 C684 "The Phone has generated NAK signal during data block transfer.
RH-42 Troubleshooting Instructions CCS Technical Documentation Phone doesn't start charging Connect charger and check VCHARIN Fail Check F100, L100, V100, and C106 OK OK Check ICHAR Fail Check R202, R206, R207, C201, C202, C220, C240, and R200 Check bottom connector -VIN _Charge control pin OK Change the UEM 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.
RH-42 Troubleshooting Instructions CCS Technical Documentation (Audio test/Hp In Ext Out) must be switched on by the Phoenix service software. This loop will connect audios only through the UEM. In this case, the UPP is not used. 3 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.
RH-42 Troubleshooting Instructions CCS Technical Documentation Microphone or XEAR line does not work Mic rophone does n't work R un audio loop s elftes t with P hoenix F ail F eed 1K Hz to MIC by J B A -8 and meas ure from XE A R OK OK C hec k R 156, C 151, C 152, C 157, L 164 F ail OK C hec k mic rophone C hange UP P C hange UE M Figure 5: Fault tree, microphone failure Issue 2 09/2003 Nokia Corporation Confidential Page 15
RH-42 Troubleshooting Instructions CCS Technical Documentation 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 Xmicswitch on an MJS-18 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-42 Troubleshooting Instructions CCS Technical Documentation Sleep Clock Missing/nonfunctional sleep clock causes • Entering sleep mode fails (higher current consumption -> shorter standby time). • Baseband self tests cannot be run. • Phone clock (on display) does not function properly.
RH-42 Troubleshooting Instructions CCS Technical Documentation Display/Keyboard lights do not work Dis play/K eyboard lights are not working C hec k R 300 (Dis play) and R 301 (K eyboard) F ail R eplac e res is tor(s ) F ail R eplac e L E D(s ) F ail R eplac e UE M OK C hec k L E Ds V 300...V 303 (Dis play) and V 304...
RH-42 Troubleshooting Instructions CCS Technical Documentation Display does not work Dis play does not work C hec k that phone powers up normally (c urrent c ons umption, power up s equenc e) F ail P roc eed toP hone Does n't P ower Up troubles hooting In any phas e of Dis play troubles hooting, us e Dis play T es t in P hoenix to produc e tes t patterns on dis play. A ls o c hec k with a known good dis play module to s ee if it works .
RH-42 Troubleshooting Instructions CCS Technical Documentation Buzzer does not work Check spring connectors and C306. • No sound: Try using a known good buzzer instead. If there is still no sound, change the UEM (D200) • Weak sound: Use the Audio test in Phoenix to set the buzzer parameters (frequency, strength). If it does not affect the sound level, change the buzzer. Keyboard does not work Check that there is no dirt between the dome sheet and the PWB.
RH-42 Troubleshooting Instructions CCS Technical Documentation Fault-finding charts for receiver chain AMPS Apply 881.49MHz = ch 383 -116dBm, 8kHz dev, 1 kHz sine to external RF connector X900 Y Connect HS to cellular tester. Open AF: 1kHz sine meas SINAD AF:>12 dB Y AMPS RX chain OK N Start troubleshooting N Start troubleshooting N Check UHF Vc (from C773) V: 1.8...2.1V Y Check RXVHF Vc (from C740). V:0.7...1.3 Y Apply 881.
RH-42 Troubleshooting Instructions Check input level at diplexer (Z907) input CCS Technical Documentation Change EXT RF connector Note! Check all soldering and components in antenna circuit before changing. N Change diplexer (Z907) Note! Check all soldering and discrete components of front end.
RH-42 Troubleshooting Instructions CCS Technical Documentation Check RF level at RX IF filter input at 135.54MHz (Z830) N Check RF level at J751 and J752 at 2034.06MHz N Start synthesizer troubleshooting Y Change Taco (N801) Y Check RF level at RX IF filter output at 135.54MHz Note! Check all discrete components and voltages around Taco. N Change RX IF filter (Z830) N Check RF level by L730 without having electrical contact at 271.
RH-42 Troubleshooting Instructions CCS Technical Documentation 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.
RH-42 Troubleshooting Instructions CCS Technical Documentation AMPS, PL2, CH383 Visual check of TX -PA -TX SAW -Duplex filter -Passive components OK Start synthesizer troubleshooting OK Check supply voltage -VR2 -VBATTRF -VR5 -IPA1 NOK Check UEM and UPP (baseband) NOK Check UEM (baseband) NOK Taco Change Taco or Z960 or Z960 OK Check TXi/q signals test points J901...
RH-42 Troubleshooting Instructions Check TX SAW input and output power IL:-3dB CCS Technical Documentation NOK Change TX SAW filter (Z905) or (T961) NOK Change PA (N901) NOK Change PWRDET (N930) NOK Change Z906 or Z907 or RF connector OK Is ltot 700...900 mA? Check PA output power and gain. Output power: ~28dBm Gain: ~30dB OK Check PWRDET (N930) insertion loss IL<0.3dB OK Check duplexer (Z906), diplexer (Z907) and RF connector (X900) insertion loss. Dupl IL ~2.2dB Dipl ~0.35dB RF conn ~0.
RH-42 Troubleshooting Instructions CCS Technical Documentation TDMA800 The transmitter chain is exactly the same as the AMPS mode, except for the IPA current. Power control loop Basically, the power detection is done with the Power detector module and power control is done inside the Taco. Is PWRDET vs output power OK? See chart below. N Check VR2 and RFTEMP. Check C930, C931, and PWRDET module. N Check UEM (baseband) Note! See PWRDET vs Output power curve Y Is DAC value vs.
RH-42 Troubleshooting Instructions CCS Technical Documentation Note: TXPWRDET is the difference between TX on burst and off burst. 2500 Voltage [mV] 2000 1500 A800 D800 1000 500 0 2 3 4 5 6 7 8 9 1 Power Level Figure 13: Detected voltage limits Synthesizer Troubleshooting There are four oscillators generating the needed frequencies for RF section: 19.
RH-42 Troubleshooting Instructions CCS Technical Documentation 2. Change VCTCXO OK START HERE! Is VCTCXO oscillating? 19.44MHz OK! 2. No 1. No OK 1. Check voltage at C792 2.78V No OK Check resistor R792 Figure 14: Fault tree: 19.44 MHz oscillator RX VHF The RX VHF signal is used to generate receiver Intermediate frequency. RX VHF has one fixed frequency 271.08 MHz. Operating frequency is locked in Phase locked Loop. RX VHF PLL output signal is integrated in Taco.
RH-42 Troubleshooting Instructions CCS Technical Documentation Fault-finding chart for RX VHF VCO 3. Replace Taco OK 1. START HERE Is frequency locked to 271.08MHz? OK Yes 2. No 1. No OK 2. Check resonator components: L730, C740, C741, R741 Figure 15: Fault tree: RX VHF TX VHF The TX VHF signal is used to generate transmitter Intermediate frequency. TX VHF VCO has one fixed frequency (361.08). Operating frequency is locked in Phase locked loop.
RH-42 Troubleshooting Instructions CCS Technical Documentation UHF Synthesizer The UHF VCO signal is used for RF channel selection. This signal is fed as a local signal for 1st mixer of RX path and for upconverter of TX path. When operating on lower band the VCO signal is divided by 2 before feeding. This synthesizer is used for channel selection in all modes. The UHF synthesizer consists of an external 2GHz VCO module with loop filter components and integrated PLL parts in Taco.
RH-42 Troubleshooting Instructions Page 32 Nokia Corporation CCS Technical Documentation Confidential Issue 2 09/2003
