Nokia Customer Care6 - Troublehsooting Instructions
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 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” 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.
6 - Troublehsooting InstructionsNokia Customer Care
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.
6 - Troublehsooting InstructionsNokia 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”
”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”
Nokia Customer Care6 - Troublehsooting Instructions
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.
6 - Troublehsooting InstructionsNokia 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.
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.
Nokia Customer Care6 - Troublehsooting Instructions
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.
Nokia Customer Care6 - Troublehsooting Instructions
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.
6 - Troublehsooting InstructionsNokia 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 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.
Nokia Customer Care6 - Troublehsooting Instructions
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
12MHz
Oscillator
VCXO
26MHz
Mjoelner
SysClk
Bluetooth
Audio
Clock
Amadeus
Audio
Codec
RFClk
RFBusClk
Figure 1: Clock diagram.
Buffer
MMC Clock
UPPWD2UEM
SDRClk
Flash
Clock
MMC
RFConvClock
SIM Clock
DBus Clock
Sleep Clock
Nectar
CBus Clock
FM Clock
SIM
Clock
SDRAM
SIMZocusFlash
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.
6 - Troublehsooting InstructionsNokia Customer Care
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 22 below.) If not change UEM.
Figure 2: Sleep clock
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 –
Nokia Customer Care6 - Troublehsooting Instructions
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.
6 - Troublehsooting InstructionsNokia Customer Care
Maximum tolerances are:
ReadingCheck pointTolerance
ReadingCheck pointTolerance
Vbatt SCAL
Vchar8.4V± 40mV
Ichar500mA± 20mA
BSI75k± 1.3kohm
Btemp273K(47k)± 5K
4.2V± 25mV
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.
Nokia Customer Care6 - Troublehsooting Instructions
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
GND
UPP
SIM
C5 C6 C7
C1C2C3
BSI line from battery
SIMCLK
SIMRST
SIMDATA
VSIM
BSI
GND
UEM
SIMIF
register
SIMIO
SIMClk
Data
UEM
digital
logic
SIMIO
SIMClk
Data
UIF Block
UEMInt
CBusDa
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.