Nokia E330N Service Manual Trouble Shooting
Customer Care Solutions
NEM-4 Series Transceivers
6 Troubleshooting Instructions
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-1 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||||
BB Troubleshooting |
CCS Technical Documentation |
||||
|
|
|
|
|
|
Page 6(a)-2 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
Company confidential |
NEM-4 |
CCS Technical Documentation |
|
Introduction to NEM-4 Troubleshooting ....................................................................... |
3 |
General guidelines for NEM-4 trouble shooting............................................................ |
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 |
ASIC is changed .......................................................................................................... |
7 |
Test points .................................................................................................................... |
7 |
“CONTACT SERVICE” on display .......................................................................... |
10 |
Baseband HW subarea Troubleshooting...................................................................... |
11 |
Flashing Troubleshooting .......................................................................................... |
11 |
ADSP flashing Troubleshooting ................................................................................ |
13 |
Energy management Troubleshooting ....................................................................... |
14 |
Audio Troubleshooting .............................................................................................. |
31 |
Headset Troubleshooting ........................................................................................... |
35 |
Memory Troubleshooting .......................................................................................... |
37 |
MMC Troubleshooting .............................................................................................. |
38 |
VIBRA ....................................................................................................................... |
40 |
ZOCUS ...................................................................................................................... |
41 |
UI Troubleshooting ...................................................................................................... |
41 |
UI Troubleshooting cases .......................................................................................... |
41 |
Keymat Backlight ...................................................................................................... |
42 |
Keyboard .................................................................................................................... |
43 |
Display blank ............................................................................................................. |
44 |
Backlight does not turn on ......................................................................................... |
45 |
FM Radio Troubleshooting.......................................................................................... |
46 |
FM Radio component layout ..................................................................................... |
46 |
FM Radio Troubleshooting diagram ......................................................................... |
48 |
RF Troubleshooting ..................................................................................................... |
53 |
Abbreviations in fault finding charts ......................................................................... |
53 |
Introduction ................................................................................................................ |
53 |
RF Key component placement ................................................................................... |
54 |
RF Measurement points ............................................................................................. |
55 |
RF in general................................................................................................................ |
58 |
RF Power Supply Configuration.................................................................................. |
61 |
Receiver ....................................................................................................................... |
62 |
General instructions for RX Troubleshooting ........................................................... |
62 |
Receiver fault finding ................................................................................................ |
66 |
Rx Signal paths .......................................................................................................... |
68 |
Transmitter ................................................................................................................... |
70 |
General instructions for EGSM TX Troubleshooting ............................................... |
70 |
TX Path of the transmitted EGSM900 signal ............................................................ |
79 |
General instructions for GSM1800/1900 TX Troubleshooting ................................. |
83 |
DCS 1800/PCS 1900 Tx fault finding flow chart ...................................................... |
83 |
Path of the transmitted GSM1800/1900 signal .......................................................... |
84 |
Draft 2 8/2003 |
Copyright Nokia. All rights reserved.. |
Page 1 |
RH-20 |
Company confidential |
|
|
|
|
|
|
CCS Technical Documentation
Fault finding chart for GSM1800/GSM1900 transmitter |
..........................................85 |
NEM-4 Synthesizer...................................................................................................... |
86 |
General instructions for Synthesizer Troubleshooting .............................................. |
86 |
26 MHz reference oscillator (VCXO) ....................................................................... |
90 |
VCO ........................................................................................................................... |
90 |
Fault finding chart for PLL Synthesizer .................................................................... |
91 |
PLL Block diagram .................................................................................................... |
92 |
PLL power supply ...................................................................................................... |
93 |
Frequency lists ........................................................................................................... |
96 |
Phoenix tuning ............................................................................................................. |
99 |
RF tuning after repairs ............................................................................................... |
99 |
RX Calibration (incl. VCXO Calibration) ................................................................. |
99 |
RX AGC limits ........................................................................................................ |
104 |
RX Band Filter Response Compensation ................................................................ |
107 |
TX Power tuning ...................................................................................................... |
114 |
TX I/Q Tuning ......................................................................................................... |
116 |
Bluetooth Troubleshooting ...................................................................................... |
130 |
Page 2 |
Copyright Nokia. All rights reserved. |
Draft 2 8/2003 |
|
|
|
|
Company Confidential |
NEM-4 |
|
|
|
|||
CCS Technical Documentation |
BB Troubleshooting |
||||
|
|
|
|
|
|
Introduction to NEM-4 Troubleshooting
This document is intend to be a guide for localizing and repairing electrical faults in the NEM-4 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 NEM-4 product and module level architecture. You have to also be familiar with the NEM-4 specified service tools such as the Phoenix service software, flashing tools and software.
General guidelines for NEM-4 trouble shooting
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” trouble shooting
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 selftest, bb-calibrations etc.)
Check baseband selftests 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 phone before disassembling it if fault is not obvious and Phoenix connection is OK.
Disassemble phone:
Check failed module visually:
Mechanical damages?
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-3 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||||
BB Troubleshooting |
CCS Technical Documentation |
||||
|
|
|
|
|
|
Solder joints OK?
Continue with specific trouble shooting 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 trouble shooting
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 NEM-4.
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 |
5mA |
|
|
2W audio call |
350mA (LOCAL MODE) |
|
|
MP3 playback |
nominal 80mA |
|
|
FM-radio playback |
nominal 25mA |
|
|
Page 6(a)-4 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
|
|
|
|
Company Confidential |
NEM-4 |
|
|
|
|||
CCS Technical Documentation |
BB Troubleshooting |
||||
|
|
|
|
|
|
Troubleshooting paths
Dead or jammed device
Disassemble
Check UIdisplay connector
Replace
UIdisplaymodule
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-5 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||||
BB Troubleshooting |
CCS Technical Documentation |
||||
|
|
|
|
|
|
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”
”Headset is not recognized”
”Microphone is not working”
”Volume cannot be adjusted”
”Ringing tones does not work”
”Audio volume too low”
“Radio does not work”
“IHF sound is missing”
“Headset sound is missing”
“MP3/AAC play does not work”
If the symptom is something like above, see audio Troubleshooting.
Most common symptoms for USB and BT problems
“Bluetooth does not work or a connection can not be established”
“USB connection does not work or PC cannot find device”
If symptoms are something like above, follow USB or Bluetooth Troubleshooting guidelines.
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”
Page 6(a)-6 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
|
|
|
|
Company Confidential |
NEM-4 |
|
|
|
|||
CCS Technical Documentation |
BB Troubleshooting |
||||
|
|
|
|
|
|
These symptoms lead to relevant part of energy management Troubleshooting
Problems related to UI:
“Keypad is not working” ”Backlight is dim” ”Backlight not even” ”Backlight is blinking”
”Keypad or display backlight is not working” ”Display related problems”
“Rocker is not working”
Most common RF related symptoms:
“Call cannot be made” ”Phone does not find signal” ”Call is often dropped”
See RF 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
|
|
Table 1: Test points in Baseband area (F6) |
|
|
Test |
Signal description |
|
|
Point |
|
|
|
|
|
|
|
|
|
|
|
J128 |
GPIO1 (WD2->ADSP) |
|
|
|
|
|
|
J129 |
GPIO0 (ADSP->WD2) |
|
|
|
|
|
|
J904 |
VCOREA enable (N261 EN, UEMRST) |
|
|
|
|
|
|
J900 |
VHPA enable (N266 EN, GENIO14) |
|
|
|
|
|
|
J901 |
VAUD (N265 EN, GENIO25) |
|
|
|
|
|
|
J903 |
VAUX2 enable (N264 EN, GENIO16) |
|
|
|
|
|
|
J218 |
GENTest0 |
|
|
|
|
|
|
J004 |
N330 (Boomer) _SHUTDOWN (from WD2 GENIO8) |
|
|
|
|
|
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-7 |
|
|
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
|
|
|
|
|
|||
BB Troubleshooting |
CCS Technical Documentation |
||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J906 |
ADSP S11 (WD2->ADSP through UEM level shifter |
|
|
|
|
|
|
|
IRLEDC) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J907 |
ADSP S13 (ADSP->WD2 through UEM level shifter |
|
|
|
|
|
|
|
IRRXN) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J558 |
ADSP CLKR0 (BCLK_OUT) to AIC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J559 |
ADSP DR0 (DIGITAL_AUDIO_IN) from AIC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J560 |
ADSPDX0 (DIGITAL_AUDIO_OUT) to AIC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J561 |
ADSP FSX0 (LRC_OUT) to AIC |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J562 |
ADSP C1 (ADSP Flash OE#) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J563 |
ADSP C2 (ADSP Flash WE#) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J567 |
ADSP C3 (ADSP Flash CE1#) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J564 |
ADSP GPIO2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J565 |
ADSP GPIO3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J312 |
FLASH _CE (D310) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J315 |
FLASH CLK (D310, D311, D313) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J311 |
FLASH _CE (D311) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J313 |
FLASH _CE (D313) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J314 |
SDRAM CLK (D312) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J197 |
GPIO13 (Keyboard matrix ROW0) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J196 |
GPIO12 (Keyboard matrix ROW1) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J179 |
GPIO16 (Keyboard matrix COL4) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J116 |
GPIO30 (Keyboard matrix COL5) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J119 |
GPIO15 (Keyboard matrix ROW3) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J118 |
GPIO14 (Keyboard matrix ROW2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J176 |
GPIO18 (Keyboard matrix ROW5) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J175 |
GPIO17 (Keyboard matrix ROW4) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J177 |
GPIO10 (Keyboard matrix COL2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J178 |
GPIO11 (Keyboard matrix COL3) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J117 |
GPIO8 (Keyboard matrix COL0) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J180 |
GPIO9 (Keyboard matrix COL1) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J181 |
GENIO1 (ROCKER1) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J145 |
GENIO2 (ROCKER2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J182 |
GENIO10 (ROCKER3) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J194 |
GENIO28 (MUSIC PL KEY) |
|
|
|
|
|
|
|
|
|
||||
Page 6(a)-8 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|||||
|
|
Company Confidential |
|
|
|
|
|
|
|
|
|
|
|
|
Company Confidential |
|
NEM-4 |
|
|
|
|
|
|
|
|||
CCS Technical Documentation |
BB Troubleshooting |
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J184 |
GENIO11 (ROCKER5) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J183 |
GENIO13 (ROCKER4) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J912 |
LCD signal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J185 |
LCD signal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J186 |
LCD signal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J187 |
LCD signal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J188 |
LCD signal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J189 |
LCD signal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J190 |
LCD signal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J191 |
LCD signal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J113 |
LCD signal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J114 |
LCD signal |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J905 |
UEM DLIGHT (Display LED driver control) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J404 |
SIM Data |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J405 |
SIM Clock |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J406 |
SIM Reset |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J913 |
MMC CMD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J914 |
MMCDAT0 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J577 |
N470 |
Dir3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J579 |
N470 |
Dir2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J576 |
N470 |
A1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J578 |
N470 |
A3 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J593 |
N470 |
A2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J910 |
N470 |
EN2 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J911 |
N470 |
EN1 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J568 |
USB PU ? |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J569 |
USB D+ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J575 |
USB D- |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J398 |
VBAT (After current sense monitor) R382 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
J902 |
N301Zint |
|
|
|
|
|
|
|
|
|
|
|
|
|
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-9 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||||
BB Troubleshooting |
CCS Technical Documentation |
||||
|
|
|
|
|
|
“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.
Selftest 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 selftest 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 selftest is failed, see relevant chapter in this Troubleshooting document.
Page 6(a)-10 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
|
|
|
|
Company Confidential |
NEM-4 |
|
|
|
|||
CCS Technical Documentation |
BB Troubleshooting |
||||
|
|
|
|
|
|
Baseband HW subarea Troubleshooting
Flashing Troubleshooting
NEM-4 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 |
Yes |
Check connections |
|
|
|
||
|
|
Check BB voltages |
|
not set Flashbus |
|
|
|
|
|
Check clocks |
|
TXD line high |
|
|
|
|
|
Change UEM |
|
after startup |
|
|
|
|
|
|
|
No |
|
|
|
The phone does |
Yes |
Measure BSI |
No |
|
||||
Check BSI line |
||||||||
not set the |
|
pulse during |
|
|
|
Check BSI line |
||
|
|
|
|
Battery connector, flex, |
||||
flashbus TXD |
|
flash |
|
|
|
Battery connector, |
||
|
|
|
|
C239, Z383, R384 |
||||
line low after the |
|
programming |
|
|
|
C226, R220 and R385 |
||
startup |
|
Is it ok? |
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
Yes |
|
|
|
|
|
No |
|
|
|
|
|
|
Change |
|
|
|
|
|
|
|
UEM |
|
|
|
|
Measure |
|
|
|
|
||
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
||
|
|
FBUSTX line |
No |
|
|
|||
|
|
during flash |
|
|
||||
|
|
programming is |
|
|
|
|
|
|
Memory |
|
it 1.8V? |
|
|
|
|
|
|
faults page |
|
|
Yes |
|
|
|
Change UPP |
|
2 |
|
|
|
|
|
WD2 |
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-11 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||||
BB Troubleshooting |
CCS Technical Documentation |
||||
|
|
|
|
|
|
Memory faults page2
"Secondary receive fail" or "Algorithm send failed" message?
No
Prommer 
message about
sdram failure? 
No
Wrong manufacturer ID and device ID
No
"Flash informs about a failure" during flashing
No
Retest
ADSP Flashing
Yes
Change UPP_WD2
Change SDRAM
Yes
|
|
|
|
Yes |
|
|
|
ActivivityininSDRAMsdram |
|||
Yes |
|
ClkclkJ314J108pad? |
|||
|
|
|
No |
||
|
|
|
|||
|
|
|
|
|
|
|
|
Change UPP_WD2 |
|
|
|
Yes |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Change Flash Chip |
|
||
|
|
according to Phoenix |
|
||
|
|
messages |
|
||
|
If both chips report wrong |
|
|||
|
ID's -> change UPP_WD2 |
|
|||
|
|
|
|
|
|
Voltages
Voltages
VmemA and
VmemA and
Vio OK?
VioA ok?
No
EM troubles
Check flash0 bypass caps, check Yes Vpp connection to flasher, Check
VppVppresistorresistor(4(R314,.7k)4.7k)
Ok->Change flash0
Page 6(a)-12 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
|
|
|
|
Company Confidential |
NEM-4 |
|
|
|
|||
CCS Technical Documentation |
BB Troubleshooting |
||||
|
|
|
|
|
|
ADSP flashing Troubleshooting
ADSP flash environment consists of ADSP, ADSP flash, EMIF (external memory interface), communication interfaces (USB and UPP/UEM), ADSP flash protecting control and power supplies for ADSP and ADSP flash.
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-13 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||||
BB Troubleshooting |
CCS Technical Documentation |
||||
|
|
|
|
|
|
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 X381 EMI-filter R385
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 6(a)-14 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
|
|
|
|
Company Confidential |
NEM-4 |
|
|
|
|||
CCS Technical Documentation |
BB Troubleshooting |
||||
|
|
|
|
|
|
General power checking
Use service tool FLA-41R. Battery voltage should be at least 3.6V. After phone disassembly, use module jig MJS-8Q.
Vbatt1-3,VBATHF,Vbatbb, VbattihfBT voltagemeasmeas. from. C301, C302 & C313
PURX (J125)R433
1.8V?
Check Vcorea 
and Vmema voltages, OK?
Check sleep clock (J124)J123 32.768Khz?
Short circuit in Vbatt1-3, VBATHFVbattbbororBTVbatvoltageihf lines. .Tryto find short circuit. Check components which are able to short cuircuit these lines, (filtering components etc.)
See next page
Meas. from
C197, OK?
Check B190,
C196, C197
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-15 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||||
BB Troubleshooting |
CCS Technical Documentation |
||||
|
|
|
|
|
|
VCOREA Troubleshooting |
|
|
|
|
|
Page 6(a)-16 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
|
|
|
|
|
Company Confidential |
NEM-4 |
|
|
|
|
|||
|
CCS Technical Documentation |
BB Troubleshooting |
||||
|
|
|
||||
VMEMA Troubleshooting |
|
|||||
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-17 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||||
BB Troubleshooting |
CCS Technical Documentation |
||||
|
|
|
|
|
|
Audio Power Troubleshooting |
|
|
|
|
|
Page 6(a)-18 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
|
|
|
|
Company Confidential |
NEM-4 |
|
|
|
|||
CCS Technical Documentation |
BB Troubleshooting |
||||
|
|
|
|
|
|
Clocks Troubleshooting
Clocks include the following:
RF-clock
ADSP Clock
DBUS, CBUS clocks
Flash and SDRAM clocks
Sleep clock
Bluetooth clock
SIM clock
MMC clock
NEM-4 has three external oscillators for baseband clocking. The main clock is generated by 26MHz oscillator (B601) and routed through Mjoelner RF ASIC to UPP_WD2 engine ASIC. Sleep Clock is generated by 32kHz oscillator to UEM, which then supplies it to UPP_WD2, Bluetooth module and FM radio chip. The third oscillator generates 12MHz clock for ADSP and AIC. UPP_WD2 uses the system clock to generate various clocks for different purposes.
|
Audio |
|
|
|
12MHz |
Clock |
Amadeus |
|
|
Oscillator |
|
|
|
|
|
|
|
Buffer |
|
VCXO |
|
|
MMC Clock |
MMC |
26MHz |
|
|
||
|
Audio |
|
||
|
|
|
|
|
|
|
Codec |
|
Nectar |
|
|
|
|
FM Clock
Mjoelner |
RFClk |
RFConvClock |
|
|
|
|
|
SysClk |
RFBusClk |
SIM Clock |
|
|
|
||
|
|
|
|
|
UPPWD2 |
DBus Clock |
UEM |
|
|
Sleep Clock
Bluetooth |
|
|
|
|
SDRClk |
Flash |
CBus Clock |
SIM |
|
Clock |
||||
Clock |
|
|||
|
|
|||
SDRAM |
Flash |
Zocus |
SIM |
Figure 1: Clock diagram
System clock can be measured from the lower pad of capacitor C171. This clock should be running when phone is on.
In SLEEP mode the VCXO is off. UEM generates low frequency clock signal (32.768 kHz) that is fed to UPP_WD2, Bluetooth and ZOCUS.
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-19 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||||
BB Troubleshooting |
CCS Technical Documentation |
||||
|
|
|
|
|
|
When the flashing of the device does not succeed, but powering is OK, follow these instructions.
Note: The absence of clocks may indicate that the device (put phone to LOCAL mode when the sleep is not allowed or press buttons so that phone is not in sleep mode) is in sleep mode. Make sure that the device is not in sleep during clocks measuring.
IMPORTANT: Clock signals have to be measured with 1MΩ (or greater) probes!
Measure signal from J170. This should be 26Mhz clock signal. See RF Troubleshooting for further information.
Check the crystal oscillator (B190) is oscillating at 32.768kHz frequency. If not change B190. If ok, measure SleepClk from test point from capacitor C521. Frequency should be the same 32.678kHz (see Figure 2, “Sleep clock,” on page 20 below.) If not change UEM.
Figure 2: Sleep clock
(Capacitor(TestpointC521)J124)
ADSP Clock (12MHz sine wave) can be measured from oscillator B550.
Charging checking
Use the BL5-C battery and JBV-1/MJF-26 calibration set to test charging. (NOTE: power supply cannot be charged if it not has a current sinking capability.) When you are charging totally empty battery, remember that start-up charging might take a little bit longer time than normal. During this time display is blank.
If charger is not NMP approved type and its current and voltage is not within NMP charger window then software does not start charging and there is “NOT CHARGING” on the display. Voltage should be between 5.3V - 9.5V and current between 200mA –
Page 6(a)-20 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
|
|
|
|
Company Confidential |
NEM-4 |
|
|
|
|||
CCS Technical Documentation |
BB Troubleshooting |
||||
|
|
|
|
|
|
900mA
Remove and reconnect battery and charger few times before you start to measure device. This check ensures that the fault really exists.
(Refer to “Charging Troubleshooting”)
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-21 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||||
BB Troubleshooting |
CCS Technical Documentation |
||||
|
|
|
|
|
|
|
Figure 3: Charging Troubleshooting |
||||
Phoenix and JBV1/MJF26
Check BL5-C, Btemp, BSI,
X381,X606, R385, R404
Page 6(a)-22 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
|
|
|
|
Company Confidential |
NEM-4 |
|
|
|
|||
CCS Technical Documentation |
BB Troubleshooting |
||||
|
|
|
|
|
|
Nothing
happens when ACP-12
is connected
Measure Vchar |
Check |
F381,0, TVS, |
|
||||
at C388at C384and .C387Is it |
. Is it |
|
|
||||
|
|
V383V381and L3810. |
|
|
|||
>3.0Vdc? |
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Check R191
Checkand Z190R191,. is it OK?
Are they ok?
Replace
Replace R191
R190/Z190 and
and retest
retest.
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-23 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||||
BB Troubleshooting |
CCS Technical Documentation |
||||
|
|
|
|
|
|
Energy management calibration
During energy management calibration A/D-converter, BSI, Btemp, Battery voltage, Charger voltage and Charger current are calibrated.
Limits for calculated calibration values are as follows:
Channel |
Low |
High |
|
|
|
ADC Offset |
-50 |
50 |
|
|
|
ADC Gain |
26000 |
29500 |
|
|
|
BSI Gain |
860 |
1180 |
|
|
|
Vbatt Offset |
2400 |
2600 |
|
|
|
Vbatt Gain |
10000 |
11000 |
|
|
|
Vchar |
57000 |
63000 |
|
|
|
Ichar |
3600 |
5000 |
|
|
|
ADC-offset over limits:
Inspect BSI line and components in it (R385, Pull-up resistor R220). If these are OK, change UEM.
BSI Gain over limits:
Inspect BSI line and components in it (R385, Pull-up resistor R220). If these are OK, change UEM.
Page 6(a)-24 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
|
|
|
|
Company Confidential |
NEM-4 |
|
|
|
|||
CCS Technical Documentation |
BB Troubleshooting |
||||
|
|
|
|
|
|
Vbatt offset and Gain:
Inspect Vbatt lines and component in it.
Vchar over limits:
Inspect components which are connected Vchar line: V383, F381 and L381
Ichar over limits:
Inspect components which are connected at Vchar line. If those are OK, First change current sense resistor (R191), if calibration is not still successful change UEM.
Calibration can be checked using ADC-readings. Known voltages, currents and resistances are fed and read by ADC-readings, read values and known values can be compared.
ADC-reading
Divided and scaled battery voltage, Charger voltage, Charger current, BSI and Btemp values can be read by this tool. Read values few times before you can be sure that results are accurate.
NOTE: IF Vbatt Scaled and Divided unit results are different default calibration values are used. In this case perform EM-calibration to get full performance of phone.
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-25 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||
|
|
|
|
|
|
||||
BB Troubleshooting |
|
|
CCS Technical Documentation |
||||||
|
|
|
|
|
|
|
|
|
|
|
Maximum tolerances are: |
|
|
|
|
|
|
||
|
|
|
|
|
|
||||
|
Reading |
|
Check point |
Tolerance |
|
|
|
|
|
|
|
|
|
|
|
||||
|
Reading |
|
Check point |
Tolerance |
|
|
|
|
|
|
|
|
|
|
|
||||
|
Vbatt SCAL |
|
4.2V |
± 25mV |
|
|
|
|
|
|
|
|
|
|
|
||||
|
Vchar |
|
8.4V |
± 40mV |
|
|
|
|
|
|
|
|
|
|
|
||||
|
Ichar |
|
500mA |
± 20mA |
|
|
|
|
|
|
|
|
|
|
|
||||
|
BSI |
|
75k |
± 1.3kohm |
|
|
|
|
|
|
|
|
|
|
|
||||
|
Btemp |
|
273K(47k) |
± 5K |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Backup battery
Symptom of backup battery fault is
Real Time Clock loses the correct time during short main battery removal.
The same symptom can also be seen when the backup battery is empty. About 30 minutes is needed to fully charge the backup battery in the device. NOTE: Backup battery is charged when the phone is powered or when the device is LOCAL or TEST mode.
Always check the backup battery visually for any leakage or any other visual defect.
Check that the backup battery is correctly mounted in the device before closing the cover.
Check with Phoenix that backup battery is OK
Measure the voltage of backup battery
•Normal operation when the voltage is > 2.0V
•Fully charged when the voltage is about 3.2V (because of large internal impedance voltage won’t stay above 3.0V a long time after charging is disabled)
Enable backup battery charging (start to charge main battery or boot device to LOCAL or TEST mode)
Measure voltage of backup battery during charging, It should arise if it is not 3.2V, yet.
When the voltage is over 2.0V for sure, check backup battery with Phoenix. -> In not OK then D190 is faulty.
Ensure that the RTC is running.
Page 6(a)-26 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
|
|
|
|
Company Confidential |
NEM-4 |
|
|
|
|||
CCS Technical Documentation |
BB Troubleshooting |
||||
|
|
|
|
|
|
SIM card
The whole SIM interface locates in two chips UPP_WD2 and UEM. UEM contains the SIM interface logic level shifting. UPP provides SIMClk through UEM to the SIM. SIM interface supports both 3 V and 1.8 V SIMs.
UPP & UEM SIM connections
|
SIM |
GND |
|
GND |
|
|
|
|
|
||
|
|
SIMDATA |
|
|
|
C5 |
C6 |
C7 |
|
SIMIO |
SIMIO |
C1 |
C2 |
C3 |
|
SIMClk |
SIMClk |
|
|
SIMCLK |
|
Data |
Data |
|
|
|
|
||
|
|
SIMRST |
|
|
|
|
|
VSIM |
UEM |
|
UPP |
|
|
|
SIMIF |
|
|
|
|
|
register |
|
|
|
|
|
|
|
UIF Block |
|
|
|
|
UEM |
UEMInt |
|
|
|
|
|
|
|
|
BSI |
|
digital |
CBusDa |
BSI line from battery |
|
logic |
|||
|
CBusEnX |
||||
|
|
|
|
|
|
|
|
|
|
|
CBusClk |
The SIM power up/down sequence is generated in the UEM. This means that the UEM generates the RST signal to the SIM. Also the SIMCardDet signal is connected to UEM. The card detection is taken from the BSI signal, which detects the removal of the battery. Monitoring of the BSI signal is done by a comparator inside UEM. The threshold voltage is calculated from the battery size specifications.
The SIM interface is powered up when the SIMCardDet signal indicates ”card in”. This signal is derived from the BSI signal. SW tries first to power up the SIM with 1.8 V. If this doesn't succeed power up is repeated with VSIM switched to 3 V.
The data communication between the card and the phone is asynchronous half duplex. The clock supplied to the card is in GSM system 1.083 MHz or 3.25 MHz. The data baudrate is SIM card clock frequency divided by 372 (by default), 64, 32 or 16.
Issue 1 09/2003 |
Copyright 2003 Nokia Corporation |
Page 6(a)-27 |
|
Company Confidential |
|
NEM-4 |
Company Confidential |
|
|
|
|
|
|
||||
BB Troubleshooting |
CCS Technical Documentation |
||||
|
|
|
|
|
|
|
Figure 4: SIM Power Up. |
||||
Ch1 Vsim
Ch2 Reset
Ch3 Clock
Ch4 I/O
Measured with 3Vsim
Figure 5: SIM answer to reset.
SIM answer to reset |
CH1 = SIM_CLK |
CH2 = SIM_RST |
CH3 = SIM_I/O |
CH4 = SIM_PWR |
Measure points |
SIM connector |
Page 6(a)-28 |
Copyright 2003 Nokia Corporation |
Issue 1 09/2003 |
|
Company Confidential |
|
Loading...