Nokia N-GageQD Service Manual 06a rh29 bb trouble
Nokia Customer Care
RH-29 Series Cellular Phones
6a - Baseband Troubleshooting
Issue 1 05/2004 Copyright © 2004 Nokia Corporation Page 1
Company Confidential
RH-29 Company Confidential
6b - Baseband Troubleshooting Nokia Customer Care
Table of Contents
Page No
Introduction to RH-29 Troubleshooting ........................................................................................... 3
General guidelines for RH-29 troubleshooting ............................................................................3
Tools needed for troubleshooting ................................................................................................. 3
General guidelines............................................................................................................................. 3
Nominal current consumption ..........................................................................................................4
Troubleshooting Paths............................................................................................................................ 5
Dead or jammed device ......................................................................................................................5
Partially damaged device ...................................................................................................................6
Most common symptoms reported by customer .........................................................................6
Most common symptoms for audio problems........................................................................... 6
Symptoms related to energy management ................................................................................ 6
Problems related to UI module:..................................................................................................... 6
Most common RF related symptoms: .......................................................................................... 6
ASIC is changed ....................................................................................................................................7
UEM changed...................................................................................................................................... 7
UPP_WD2 changed ........................................................................................................................... 7
ZOCUS changed.................................................................................................................................. 7
Test points ..............................................................................................................................................7
“CONTACT SERVICE” on display ........................................................................................................8
1CK Baseband HW Subarea Troubleshooting.................................................................................. 9
Flashing troubleshooting .................................................................................................................... 9
Energy management troubleshooting ..........................................................................................11
Device does not stay on................................................................................................................ 11
General power checking ............................................................................................................... 12
Power key troubleshooting .......................................................................................................... 14
Clocks troubleshooting.................................................................................................................. 14
Charging checking.......................................................................................................................... 16
Energy management calibration ................................................................................................ 19
ADC-reading..................................................................................................................................... 20
Backup battery ............................................................................................................................... 21
SIM card .......................................................................................................................
Memory troubleshooting ..................................................................................................................26
Serial interface troubleshooting ....................................................................................................27
CBUS................................................................................................................................................... 27
FBUS ................................................................................................................................................... 28
MBUS.................................................................................................................................................. 28
MMC troubleshooting .......................................................................................................................29
Vibra .......................................................................................................................................................30
ZOCUS ....................................................................................................................................................31
UI Module Troubleshooting ............................................................................................................... 32
Keymat backlight ................................................................................................................................32
Keyboard problem ..............................................................................................................................33
Display blank ........................................................................................................................................34
Image on display not correct ..........................................................................................................35
Backlight does not turn on .............................................................................................................36
Handportable audio ............................................................................................................
Accessory Audio ..................................................................................................................................40
..................... 22
...............37
Page 2 Copyright © 2004 Nokia Corporation Issue 1 05/2004
Company Confidential
Company Confidential RH-29
Nokia Customer Care 6b - Baseband Troubleshooting
Introduction to RH-29 Troubleshooting
This document is intend to be a guide for localizing and repairing electrical faults in the
RH-29 device. First there is a brief guide for fault localizing. Then fault repairing is
divided into troubleshooting paths.
Before any service operation you must be familiar with the RH-29 product and module
level architecture. You have to also be familiar with the RH-29 specified service tools
such as the Phoenix service software, flashing tools and software.
General guidelines for RH-29 troubleshooting
Tools needed for troubleshooting
• Service tools (as listed at service tools chapter in service manual)
• Laboratory power supply with current indicator
• Oscilloscope
• Digital multimeter
General guidelines
If the device cannot be turned on by any means, see “dead device” troubleshooting
Current consumption (missing consumption) gives an idea whether the device is able to
start up.
Dropping supply voltage or very large current consumption indicates a short circuit
Check whether the connection with Phoenix works and what can be discovered with
Phoenix (ADC-readings, baseband self-test, BB-calibrations etc.)
Check baseband self-tests with Phoenix if “CONTACT SERVICE” is shown on the display.
Check visually display and rocker faults.
Force phone to LOCAL mode and make keyboard test by phoenix.
Check that board-to-board connector is OK, and connectors make good contacts.
If liquid damage, stop repairing!
Flash the phone before disassembling it, if the fault is not obvious and the Phoenix connection is OK.
Disassemble phone:
Try to locate failed module.
Issue 1 05/2004 Copyright © 2004 Nokia Corporation Page 3
Company Confidential
RH-29 Company Confidential
6b - Baseband Troubleshooting Nokia Customer Care
Check failed module visually:
Mechanical damages?
Solder joints OK?
Continue with specific troubleshooting procedure for the module:
If there is an obvious fault, repair it before reflashing the device.
Flash first if a fault is not obvious.
If flashing is not working go to flashing troubleshooting.
Due to CSP packages short circuits or broken solder joints are not easily seen. If the
examined signal seems to be continuously in low or high level, then measure for possible
short circuit to ground (signal low) or to supply voltage (signal high) Note that if a problem is not found from any visible contact/component it can be under CSPs where the signal is connected.
Care must be taken when assembling and disassembling the transceiver. Failure to do
this may result in unnecessary damage to device.
Nominal current consumption
NOTE: Service tools need some amount of current to work.
The following current consumption values are measured from a complete RH-29.
Vbatt = 3.6V
Measured nominal currents are drawn from the main battery.
Measurements have been made with a current probe connected to an oscilloscope.
Operating mode Current consumption
Idle 90 mA
2w audio call (backlights off) 250 mA
Page 4 Copyright © 2004 Nokia Corporation Issue 1 05/2004
Company Confidential
Company Confidential RH-29
Nokia Customer Care 6b - Baseband Troubleshooting
Troubleshooting Paths
Dead or jammed device
Disassemble
yes
Check UI
connector
Replace
UI module
Issue 1 05/2004 Copyright © 2004 Nokia Corporation Page 5
Company Confidential
RH-29 Company Confidential
6b - Baseband Troubleshooting Nokia Customer Care
Partially damaged device
If the device is working, but some functionality is missing try to localize where the problems is and see relevant part of this manual. E.g audio is not working see “Audio Troubleshooting”, if charging is not working see chapter Charging troubleshooting etc.
Most common symptoms reported by customer
In this chapter is described most common symptoms reported by customers when the
device is brought in for service. Some tips where the trouble can be found are given also.
When troubleshooting use these tips and follow the given troubleshooting path.
Most common symptoms for audio problems
“Earpiece sound is missing”
”Handsfree sound is missing”
”Headset is not recognized”
”Microphone is not working”
”Volume cannot be adjusted”
” Ringing tones does not work”
”Audio volume too low”
If symptom is something like above see audio troubleshooting.
Symptoms related to energy management
“Phone does not stay on”
”Charging is not working”
”Time is lost during battery change”
”Charging takes too long”
”Operating time is very short”
These symptoms lead to relevant part of energy management troubleshooting
Problems related to UI module:
“UI-module keypad is not working”
”Backlight is dim”
”Backlight not even”
”Backlight is blinking”
”Keypad or display backlight is not working”
”Display related problems”
See UI- module troubleshooting.
Most common RF related symptoms:
“Call cannot be made”
”Phone does not find signal”
”Call is often dropped”
See RF troubleshooting
Page 6 Copyright © 2004 Nokia Corporation Issue 1 05/2004
Company Confidential
Company Confidential RH-29
Nokia Customer Care 6b - Baseband Troubleshooting
ASIC is changed
ASIC’s can be changed only at a defined service level.
UEM changed
If UEM is changed baseband calibrations should be made. New IMEI must be programmed also. ZOCUS calibration is not necessary.
UPP_WD2 changed
IMEI must be reprogrammed.
ZOCUS changed
Zocus must be re-calibrated
Test points
Test Point Signal Test Point Signal Test Point Signal
J109 UEMInt J203 TXQD J477 SIM IF
J123 SLEEPCLK J204 AUXD J482 MMC IF
J124 SLEEPX J311 FLASH CE J483 MMC IF
J125 PURX J312 FLASH CE J484 MMC IF
J170 RFCLK_I J314 SDRAMCLK J485 MMC IF
J190 EARDATA J315 FLASH CLK J487 MMC IF
J191 MICDATA J334 Shutdown
Audio PA
J192 SIMIODAI J390 Current sense
resistor
J193 SIMCLKI J391 Current sense
resistor
J194 SIMIOCTRL J392 Current sense
resistor
J195 MBUSTX J393 Current sense
resistor
J196 MBUSRX J470 SIM IF J496 MMC IF
J488 MMC IF
J490 MMC IF
J492 MMC IF
J493 MMC IF
J495 MMC IF
J197 FBUSTXI J471 SIM IF J497 MMC IF
J198 FBUSRXI J472 SIM IF J498 MMC IF
J199 RFCONVCLK J473 SIM IF J499 MMC IF
J200 RXID J474 SIM IF
J201 RXQD J475 SIM IF
J202 TXID J476 SIM IF
Issue 1 05/2004 Copyright © 2004 Nokia Corporation Page 7
Company Confidential
RH-29 Company Confidential
6b - Baseband Troubleshooting Nokia Customer Care
“CONTACT SERVICE” on display
CONTACT SERVICE on display (Self-tests by Phoenix)
Display information: “Contact Service”
This fault means that software is able to run and thus the watchdog of UEM can be
served.
Self-test functions are executed when the phone is powered on and if one or more selftest functions fail, the message “Contact Service” is shown on the display.
MCU self-test cases can be split into two categories: The ones that are executed during
power up and the ones that are executed only with a PC connected. These test and the
items included are as follows:
If some self-test failed, see relevant chapter in this troubleshooting document.
Page 8 Copyright © 2004 Nokia Corporation Issue 1 05/2004
Company Confidential
Company Confidential RH-29
Nokia Customer Care 6b - Baseband Troubleshooting
1CK Baseband HW Subarea Troubleshooting
Flashing troubleshooting
RH-29 has three memory components installed on the main PWB. The best indication of
which one is causing problems can be obtained by flashing the device. It has to be kept
in mind that all three flashes are interfaced with UPP WD2 asic that might it self have
some problems. The necessary steps are described below. Phoenix error messages during
flashing greatly help on defining what is wrong. To be able to flash the device, most
device BB area components must function properly.
Flashing
faults
The phone does
not set Flashbus
TXD line high
after startup
No
The phone does
not set the
flashbus TXD
line low after the
startup
No
Memory
faults page
2
Yes
Yes
Measure BSI
pulse during
flash
programming
Is it ok?
Yes
Measure
FBUSTX line
during flash
programming is
it 1.8V?
Yes
No
No
Check connections
Check BB voltages
Check clocks
Change UEM
Check BSI line
Check BSI line
Battery connector, flex,
Battery connector,
C239, Z383, R384
C381, R192 and C231
Change
UEM
Change UPP
WD2
Issue 1 05/2004 Copyright © 2004 Nokia Corporation Page 9
Company Confidential
RH-29 Company Confidential
g
6b - Baseband Troubleshooting Nokia Customer Care
Memory
faults
page2
"Secondary
receive fail" or
"Algorithm send
failed"
messa
Prommer
message about
sdram failure?
manufacturer ID
and device ID
e?
No
No
Wrong
No
Yes
Yes
Yes
Change UPP_WD2
Activity in SDRAM
Activity in sdram
Clk path (R101)?
clk J108 pad?
(J314)?
No
Change UPP_WD2
Change Flash Chip
according to Phoenix
messages
If both chips report wrong
ID's -> change UPP_WD2
Yes
Change SDRAM
Yes
Voltages
Voltages
VmemA and
VmemA and
Vio OK?
VioA ok?
No
EM
troubles
"Flash informs
about a failure"
during flashing
No
Retest
Yes
Check flash0 bypass caps, check
Vpp connection to flasher, Check
Vpp resistor(4.7k)
Vpp resistor (R310)
Ok->Change flash0
Page 10 Copyright © 2004 Nokia Corporation Issue 1 05/2004
Company Confidential
Company Confidential RH-29
Nokia Customer Care 6b - Baseband Troubleshooting
NAK" ?
C586 "Phone fail
response received"
or C684 "Data block
message ?
C385 "Data block
handling timeout"
OK ->flash (D311)
check R310 (4.7k)
Check flash byp ass
connection to flasher,
caps, check VPP R310
No
Yes
Flashing with option
"phone only" succesful ?
-> still not OK
->change BT module
Bluetooth module is unable to start flashing
-> check V601, R601,R602,R627 and C602
ID" ?
manufacture
A204 "Wrong
ID and device
SDRAM
failure" ?
message about
C108 "Prommer
C202 "Algorithm
send" or C281 "phone
C106 "Secondary
C103 "Boot serial line"
No No No No No No No
C101 "boot timeout "
Yes
Flashing
Yes
fail ?
message cheksum"
message ?
receive fail"
Fail ?
fail" message
or C102 "boot start txd
faults
and SDRAM
Change Flash chip
allredy
changed
Yes Yes Yes Yes Yes
Yes Yes Yes
Measure BSI
(D100)
according to phoenix
messages (typical D312)
if both chips report wrong
ID's -->change UPP WD2
Change
Yes
No Yes
Check BSI line
Change
Change UPP
Battery connector
SDRAM (D310)
fail
phone
Op.Start
UEM (D190)
Change
UPP WD2 (D100)
Doesn't help
Change
WD2 (D100)
(X382) and C381
UEM (D190)
Change
UEM (D190)
No
?
change flash
(128Mb) D311
Flashing starts ok
show error code C101
after 5s flashing stop's and
VIO C216 (1.8V),
UEMRSTX R431(VBAT)
and PURX J125(1.8)
Voltage VIO OK ?
OK ?
Sleep clock (J123)
is it ok ?
programming
pulse (X382,pin2
"middle") during flash
No
try flashing with
Check connections
powers from FPS-8
reflash
Change and
Yes
chips?
Broken flash-
Yes
No
Check N260
SMPS Regulator
No
?
VcoreA (1.5V)
Change
UEM (D190)
Yes
Current
mode ?
consumpti on
50mA in local
Check
XTAL ( B601)
Mjoelner (N601)
Change
UEM (D190)
Yes
Change
and reflash
UPP WD2 (D100)
Yes
No
OK
Sleep clock (J123)
NoNo
No
?
RFClk (C602)
Bias 800-1000mV ?
2.78V
Pulses to
(2.78V)
VR3(C212)
at power up ?
Change
UEM (D190)
Change
UPP WD2 (D100)
Yes Yes
Change
UPP WD2 (D100)
Issue 1 05/2004 Copyright © 2004 Nokia Corporation Page 11
Company Confidential
RH-29 Company Confidential
6b - Baseband Troubleshooting Nokia Customer Care
Energy management troubleshooting
Device does not stay on
If the device is switched off without any visible reason, there may be problems in the following areas:
• UEM watchdog problem (WD is not updated by SW)
• BSI line problem (BSI line is floating => contact failure)
• Battery line problem
• Soldering problem
The most likely reason is UEM WD (watchdog), which turns the device off after about 32
seconds if SW is jammed.
This may caused by SW problem, UPP_WD2 problem (Not server by SW), UEM or memory
malfunctions.
The following tests are recommended:
• General power checking
• Clocks
• Memory testing
• Serial Interface
If there is something wrong in BSI line, the device seems to be dead after the power key
is pressed. However the regulators of the device are on a few seconds before the powerdown.
This mode can easily be detected from the current consumption of the device. After a
few seconds the current consumption drops almost to 0 mA.
In this case check component or soldering
• Battery connector X382
EMI-filter R381
UEM D190 (pin number C2)
If phone boots to TEST or LOCAL mode with normal battery, BSI is short circuited to
ground. Check EMI-filter and filtering capacitors, which are located to BSI.
Page 12 Copyright © 2004 Nokia Corporation Issue 1 05/2004
Company Confidential
Company Confidential RH-29
C
(J
)
Nokia Customer Care 6b - Baseband Troubleshooting
General power checking
Use service tool SF-20. Battery voltage should be at least 3.6V. After phone disassembly,
use module jig MJ-21.
Supply voltage
drops? (or current
is large >1A)
Vbatt1-3, Vbatbb,
Vbattihf meas. from
300,C301 & C302
C301, C302 & C303
J125
PURX (PIN 44
?
)BT module)
Short circuit in Vbatt1-3,
Vbattbb or Vbattihf lines. Try to
find short circuit. Check
components which are able to
short circuit these lines,
(filtering components etc.)
Check Vcorea
and Vmema
voltages, OK?
Check sleep
123
clock (PIN 26 BT mod.)
32.768Khz?
See next page
Meas. from
C200, OK?
Check B190,
C199, C200
Issue 1 05/2004 Copyright © 2004 Nokia Corporation Page 13
Company Confidential
RH-29 Company Confidential
6b - Baseband Troubleshooting Nokia Customer Care
Vcorea dead
Voltages at
C262, C263 and L260
(both sides), OK?
No
Change
L260 OK?
No
Change N260 and
Retest
Yes
Yes
Retest
Retest
Page 14 Copyright © 2004 Nokia Corporation Issue 1 05/2004
Company Confidential
Loading...