Nokia NPC-1 Series Guide

Programmes After Market Services
NPC-1 Series Transceivers
Issue 1 10/01 ãNokia Corporation
Troubleshooting Instructions

NPC-1
Troubleshooting Instructions PAMS Technical Documentation
Page 2 ãNokia Corporation Issue 1 10/01
Table of Contents Page No
Troubleshooting Instructions ..........................................................................................1
Transceiver Troubleshooting ......................................................................................... 4
Baseband Troubleshooting ..........................................................................................4
General about testing................................................................................................. 4
Troubleshooting ........................................................................................................ 5
Power up faults.......................................................................................................... 6
Flash Programming does not work.......................................................................... 10
Charging.................................................................................................................. 12
Audio failures.......................................................................................................... 13
Accessory detection................................................................................................. 15
Sleep Clock ............................................................................................................. 16
Display/Keyboard lights do not work ..................................................................... 18
Display does not work............................................................................................. 19
Buzzer does not work.............................................................................................. 20
Vibra does not work................................................................................................ 20
Keyboard does not work ......................................................................................... 20
Infrared does not work ............................................................................................ 21
Receiver Troubleshooting ..........................................................................................22
General instructions for RX troubleshooting.......................................................... 22
Path of the received signal ...................................................................................... 22
Fault finding charts for receiver chain .................................................................... 22
Transmitter Troubleshooting .....................................................................................26
General instructions for TX troubleshooting .......................................................... 26
Path of the transmitted signall................................................................................. 26
Fault finding charts for the transmitter.................................................................... 26
Synthesizer Troubleshooting .....................................................................................30
19.44 MHz reference oscillator............................................................................... 30
RX VHF VCO......................................................................................................... 31
TX VHF VCO......................................................................................................... 32
UHF SYNTHESIZER............................................................................................. 33

PAMS Technical Documentation Troubleshooting Instructions
NPC-1
Issue 1 10/01 ãNokia Corporation Page 3
List of Figures Page No
Fig 1 Power up sequence .....................................................................................................7
Fig 2 Fault tree, phone does not power up...........................................................................9
Fig 3 Fault tree, charging.....................................................................................................13
Fig 4 Fault tree, earpiece fail ...............................................................................................14
Fig 5 Fault tree, microphone fail .........................................................................................15
Fig 6 Fault tree, accessory detection....................................................................................16
Fig 7 Fault tree, sleep clock.................................................................................................17
Fig 8 Fault tree, Display/Keyboard lights............................................................................18
Fig 9 Fault tree, Display does not work...............................................................................19
Fig 10 Fault tree, infrared ....................................................................................................21
Fig 11 Fault tree. AMPS......................................................................................................23
Fig 12 Fault tree. Transmitter troubleshooting....................................................................27
Fig 13 Fault tree: Power control loop..................................................................................29
Fig 14 Detected voltages......................................................................................................30
Fig 15 Fault tree: 19.44 MHz oscillator...............................................................................31
Fig 16 Fault tree: RX VHF VCO.........................................................................................32
Fig 17 Fault tree: TX VHF VCO.........................................................................................33
Fig 18 Fault tree: UHF Synthesizer.....................................................................................34

NPC-1
Troubleshooting Instructions PAMS Technical Documentation
Page 4 ãNokia Corporation Issue 1 10/01
Transceiver Troubleshooting
The Troubleshooting instructions are divided into following sections:
1 How to check/fix the system/sleep clock.
2 How to check/fix the power supplies.
3 Contact service case.
4 How to check/fix the SIM faults.
5 How to check/fix the Audio faults.
6 How to check/fix the charger faults.
The first thing to do 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 about testing
The phone has three different modes for testing and/or repairing the phone. The modes
can be selected with suitable resistors connected to BSI- and BTEMP- lines as illustrated
in the table below:
If the corresponding resistors are connected, the MCU software automatically enters into
the local or test mode when the supply voltage is connected to the phone.
The power can be switched on by:
Table 1: Phone operating mode
Mode BSI-resistor BTEMP resistor Remarks
Normal 68k 47k
Local 560_ (<1k_) Whatever
Test > 1k 560_ (<1k_) Recommended for baseband test-
ing. Same as local mode, but mak-
ing a phone call is possible.

PAMS Technical Documentation Troubleshooting Instructions
NPC-1
Issue 1 10/01 ãNokia Corporation Page 5
1 Pressing the power key.
2 Connecting the local/test mode resistors to the bsi/btemp lines and connecting
the battery voltage to the phone.
3 Connecting a charger.
4 Phone’s internal functions (Real time clock alarm)
In the local and test mode, the baseband can be controlled through MBUS or FBUS (FBUS
is recommended) connections using Phoenix service software.
Troubleshooting
Note: Most of the baseband repair actions require removing the baseband shield.
The shield must not be removed unless authorized by PAMS.
Note: ESN has to re-written onto the phone, if the UEM is replaced. This can be
done only in Central Service.
The BB troubleshooting instructions consist of the following topics:
1Powerup
2 Flash programming
3Audio
• Earpiece
• Microphone
4 Charging
5 Accessory detection
6Sleepclock
7 User interface
•Display
• Lights
• Buzzer
•Vibra
• Keyboard

NPC-1
Troubleshooting Instructions PAMS Technical Documentation
Page 6 ãNokia Corporation Issue 1 10/01
8 Infrared
Power up faults
Power up sequence
1 The UEM acts as a HW master during start up
• Vbatt limits: 2.1V for internal state machine, 3V triggering whole startup
• Regulator sequencing
• HW "core" regulators "on": Vio, Vcore, VR3, Vflash1
• These regulators supply the processors, memory, chip interfaces and
clock source in RF
• Reset releasing delay
• 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 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.
3 MCU runs the FLASH MCU code
• the phone initialization, user interfaces, internal blocks etc.
• Core regulator voltage setting for required DSP speed
• Initializes the DSP and concerning HW
• Releases DSP reset -> DSP starts running

PAMS Technical Documentation Troubleshooting Instructions
NPC-1
Issue 1 10/01 ãNokia Corporation Page 7
Note: In figure below, the RF_Clk frequency appears to be lower than 19.44MHz
because of a too low oscilloscope sampling frequency (2kS/s).
Figure 1: Power up sequence
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
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.
3 Software running

NPC-1
Troubleshooting Instructions PAMS Technical Documentation
Page 8 ãNokia Corporation Issue 1 10/01
• Default value for Vcore is 1.5 volts and, if the software is running, Vcore will
rise to 1.8 volts.
• Cbus (1.08MHz) clock starts running.
Phonedoes not startup normallyor doesnot stayon
Note: In case of power up faults, it is not possible to force the phone on by disabling
the watchdog. Instead, measurements should be taken immediately when the power
key is pressed or when the battery voltage is connected to the phone (local/test
mode).
The easiest way to check if the software is running when the phone takes an abnormal
amount of current is to measure the cbusclk and Vcore.
The Dbus clock (programmable 9.72MHz) is not automatically visible in the test and local
modes.

PAMS Technical Documentation Troubleshooting Instructions
NPC-1
Issue 1 10/01 ãNokia Corporation Page 9
Figure 2: Fault tree, phone does not power up
Try to start phone to
test or local mode Check the
power key
Check X101
Measure
Vflash1,Vana,Vio,Vcore
,VR3when pwr key
pressed
Check 19.44MHz
RF-clock from C420
Check that purx
goes up to 1.8V
Change UPP
(D400)
Change the
UEM (D200)
OK
Measure VBAT
from C261
Check R202,
R205, C217,
C220
Check G790
(missing,
misaligned)
Measure
J406. Should
be 1.08 MHz
Check
C420
Check
19.44MHz from
G790
Change N801
FAIL
Re-flash phone
OK
OK
FAIL
VANA & VR3
missing
FAIL
OK
OK
OK
Check
R792,C792,
C793
Change
G790
OK
FAIL
FAIL
OK
OK
FAIL
OK
OK
OK
FAIL
Programmng ok,
but phone doesn't
start Go to flash failure
chart
Programming
fails

NPC-1
Troubleshooting Instructions PAMS Technical Documentation
Page 10 ãNokia Corporation Issue 1 10/01
Flash Programming does not work
Flashprogrammingprocedure
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).
2 When the phone is powered (VBAT>3V), the MBUS and FBUSTX lines are pulled
up internally by the phone.
3 The prommer sends a command to the UEM, using FBUSRX, to enter the Flash-
mode. During the sending of this command, the prommer keeps the BSI line high
and MBUS is used as a serial clock.
4 When the Flash-mode command is acknowledged, UEM enters the Flash-mode
and releases reset (PURX) to MCU.
5 After reset is released, UPP checks if there is a request for the Bootstrap code
(that resides in the UPP ROM).
6 The request for Bootstrap is the MBUS pulled down by the prommer (if the boot-
strap is not requested, the bootstrap code jumps to FLASH SW).
7 If the Bootstrap code is requested, UPP enters the Flash-mode and sets FbusTX to
'0' as an acknowledgement to the prommer. This is an indication that UPP can
run, at least, the fixed Bootstrap code – although it is not able to run the FLASH
code. UPP then sends an UPP-ID to the prommer via the FBUSTX line.
8 After the prommer has received the UPP-ID, it sends a corresponding Secondary
Boot Code to the phone via FBUSRX. The Secondary Boot Code, when run in UPP,
requests UPP to send information to the prommer about the flash type and other
HW-related parameters about the device to be flashed.
9 Prommer then sends the Algorithm Code corresponding to the HW parameters,
and this algorithm, when run in UPP, takes over handling the MCUSW transfer to
Flash.
10 12 volts can be supplied to Vpp (by the prommer) to speedup flashing.

PAMS Technical Documentation Troubleshooting Instructions
NPC-1
Issue 1 10/01 ãNokia Corporation Page 11
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.
Flashprogrammingerrorcodes
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.
Table 2: Table 2. Flash programming error codes.
Error Description Not working properly
C101 "The Phone does not set FbusTx line high
after the startup." Vbatt
Vflash1
Vcore
VIO
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."
PURX(also to Safari)
VR3
Rfclock(VCTCXO->Safari->UPP)
Mbus from Prommer->UEM->UPP(MbusRx)(SA1)
FbusTx from UPP->UEM->Prommer(SA1)
C103 "Boot serial line fail." Mbus from Prommer->UEM->UPP(MbusRx)(SA0)
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." Mbus from Prommer->UEM->UPP(MbusRx) FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
C106 "The Phone has not received Secondary
code bytes correctly." Mbus from Prommer->UEM->UPP(MbusRx) FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
C107 "The Phone MCU can not start Secondary
code correctly." UPP
A204 " The flash manufacturer and device IDs in
the existing Algorithm files do not match
with the IDs received from the target
phone."
Flash
Signals between UPP-Flash
A387 "The MCU ID in the MCUSW.” UPP
C601 "The prommer has detected that Vpp volt-
age level has dropped below the limit" Vpp from prommer - >Flash

NPC-1
Troubleshooting Instructions PAMS Technical Documentation
Page 12 ãNokia Corporation Issue 1 10/01
Charging
Note: The charging voltage and current can be checked by connecting the phone to
the service software and reading the ad- converter values of the vchar and ichar.
If charging fails when the ACP-9 or the LCH-9 is used, and works with ACP-7, ACP-8 and
LCH-8, check that the charge control pin of the system connector is connected to the
ground.
C383
C583
C683
"The Prommer has not received Phone
acknowledge to the message."
(C383-during algorithm download to tar-
get phone)
(C583-during erasing)
(C683-during programming)
Flash
UPP
Signals between UPP-Flash
C384
C584
C684
"The Phone has generated NAK signal dur-
ing data block transfer."
(C384-during algorithm download to tar-
get phone)
(C584-during erasing)
(C684-during programming)
Flash
UPP
Signals between UPP-Flash
C585
C685 Data block handling timeout" (C585-during erasing)
(C685-during programming)
Flash
UPP
Signals between UPP-Flash
C586
C686 "The status response from the Phone informs about fail."
(C586-during erasing)
(C686-during programming)
Flash

PAMS Technical Documentation Troubleshooting Instructions
NPC-1
Issue 1 10/01 ãNokia Corporation Page 13
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 In case 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 soft-
ware. This loop will connect audios only through the UEM. In this case, the UPP is
not used.
In case the internal microphone/XEAR fails: Feed the tone to the microphone and
measure the signal from the XEAR line. The Audio test box JBA-8 is needed. The
Phone doesn't start
charging
Connect charger and
check VCHARIN
Change the
UEM
Check
F100,L100,V100,C105
Check bottom
connector
- VIN
- Charge control pin
Check
R202,R203,R205,C217,
C220,C201,C202 and
R200
Fail
OK
Check ICHAR
OK
FAIL
OK

NPC-1
Troubleshooting Instructions PAMS Technical Documentation
Page 14 ãNokia Corporation Issue 1 10/01
Audio loop (Audio test/Hp InExt 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.
Earpieceor externalmicrophoneline does notwork
Figure 4: Fault tree, earpiece fail
Earpiece doesn't
work
Run audio-loop
selftest with
phoenix
Check R157
Check
earpiece
Change UEM
Feed 1KHz to Xmic
by JBA-8 and
measure from
earpiece
Change UPP
Fail
OK
OK
OK
Fail
OK

PAMS Technical Documentation Troubleshooting Instructions
NPC-1
Issue 1 10/01 ãNokia Corporation Page 15
Microphoneor XEARline doesnot work
Figure 5: Fault tree, microphone fail
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 MJS-18 test jig. Changes normally from high to low when no acces-
sory is connected.
3 When the headset HDC-5 is connected, the hookint- value should be between
600 and 700.
Microphone doesn't
work
Run audio-loop
selftest with
phoenix
Check
R156,C151,C152,C157,L164
Check
microphone
Change UEM
Feed 1KHz to Mic
by JBA-8 and
measure from Xear
Change UPP
Fail
Ok
Ok
Ok
Ok
Fail

NPC-1
Troubleshooting Instructions PAMS Technical Documentation
Page 16 ãNokia Corporation Issue 1 10/01
Figure 6: Fault tree, accessory detection
Sleep Clock
Missing/non-functional sleep clock causes
• entering sleep mode fails (higher current consumption -> shorter standby time).
The
• Baseband self tests cannot be run.
• Phone clock (on display) does not function properly.
Accessory detection
doesn't work normally
Check HeadInt
ad-value with Phoenix
(No accessory
connected)
- HeadInt ~0 *)
Change UEM
Check R152,C161,L160
Check
R150,R201,C104,C105,
L162,L163
Check R151
and C160
Check bottom
connector
* On local or test mode
Headint <400
Use the xmic- switch on MJS-18
and check hookint ad-value.
Should go from high (~1000) to
low (~0)
Ok
Fail
Ok
Fail
Ok
Ok
Ok
Ok

PAMS Technical Documentation Troubleshooting Instructions
NPC-1
Issue 1 10/01 ãNokia Corporation Page 17
Figure 7: Fault tree, sleep clock
Sleep mode
not working
Measure sleep clock
from J204 Check C203
&C204
Change B200
Change UPP
(D400)
Fail Measure sleep clock
from B200
Change UEM
(D200)
Fail
Ok Ok Ok

NPC-1
Troubleshooting Instructions PAMS Technical Documentation
Page 18 ãNokia Corporation Issue 1 10/01
Display/Keyboard lights do not work
Figure 8: Fault tree, Display/Keyboard lights.
Display/Keyboard
lights are not working
Check R300 (Display) and
R301 (Keyboard) Replace
resistor(s)
Check LEDs
V300...V303 (Display) and
V304...V309 (Keyboard) Replace
LED(s)
Use Display Test in
Phoenix to set lights
ON/OFF
FAIL
OK
FAIL
OK
Replace UEM
FAIL

PAMS Technical Documentation Troubleshooting Instructions
NPC-1
Issue 1 10/01 ãNokia Corporation Page 19
Display does not work Figure 9: Fault tree, Display does not work
Display does not work
Check that phone
powers up normally
(current consumption,
power up sequence)
Check display visually
(possible cracks on
COG driver or glass,
capacitors loose or
broken
Check PWB and
elastomer
connector
Run LCD test in
Phoenix
(BB Self Tests/
ST_LCD_TEST)
Proceed to phone
doesn't power up
troubleshooting
Replace
display module
Clean PWB and
replace
elastomer if
needed
Check
capacitors
C302...C304
FAIL
OK
FAIL
FAIL
OK
FAIL Replace
capacitors(s)
FAIL
Replace
elastomer
OK
OK
Replace
display module
FAIL
Use Display Test
in Phoenix to
check if display
works
OK
In any phase of display
troubleshooting use Display Test in
Phoenix to produce test patterns on
display.
Also check with a known good
display module to see if it works.
Replace
display module
FAIL

NPC-1
Troubleshooting Instructions PAMS Technical Documentation
Page 20 ãNokia Corporation Issue 1 10/01
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 (fre-
quency, strength). If it does not effect the sound level, change the buzzer.
Vibra does not work
Check spring connectors and C307&C308.
• No vibration: Try using a known good vibra instead. If there is still no vibration,
change the UEM(D200)
• Weak vibration: Use the Vibra test in Phoenix to set the vibra’s parameters (fre-
quency, duty cycle). If it does not effect the magnitude of the vibration, change
the vibra.
Keyboard does not work
Check that there is no dirt between the dome sheet and the PWB. If the keyboard still
does not operate normally, try to use the Keyboard test in Phoenix to see if the pressed
key is identified. If it is not identified, change the UPP(D400).