Nokia 6340 Service Manual 9 npm 2nx trouble
CCS Technica l Documentation
NPM-2NX Series Transceivers
T roubleshooting
Issue 1 07/02 ãNokia Corporation
NPM-2NX
Troubleshooting CCS Technical Documentation
Contents
Page No
Transceiver Troubleshooting ......................................................................................... 4
General about testing ...................................................................................................4
Phone operating modes ............................................................................................. 4
Measurement points .....................................................................................................5
Baseband Troubleshooting............................................................................................. 7
Power up sequence ......................................................................................................7
Phone does not start up normally or does not stay on............................................. 10
Flash Programming does not work.......................................................................... 11
Flash programming error codes............................................................................... 13
Charging ....................................................................................................................15
Audio failures ............................................................................................................15
Earpiece or external microphone line does not work.............................................. 17
.Microphone or XEAR line does not work ............................................................. 18
Accessory detection ...................................................................................................19
Power supply for data cable .......................................................................................20
Sleep Clock ................................................................................................................20
Display/Keyboard lights do not work ........................................................................22
Display does not work ...............................................................................................23
Buzzer does not work.............................................................................................. 23
Vibra does not work ...................................................................................................24
Keyboard does not work ............................................................................................24
SIM does not work .....................................................................................................24
Infrared does not work ...............................................................................................25
RF Troubleshooting ..................................................................................................... 26
Introduction ................................................................................................................26
Abbreviations in fault finding charts....................................................................... 26
Receiver ....................................................................................................................... 27
General instructions for RX troubleshooting......................................................... 27
Path of the received signal .........................................................................................28
AMPS ........................................................................................................................29
TDMA800 ..................................................................................................................33
TDMA1900 ................................................................................................................33
GSM1900 ...................................................................................................................36
Transmitter................................................................................................................... 44
General instructions for TX troubleshooting .............................................................44
AMPS/TDMA ............................................................................................................44
GSM1900 ...................................................................................................................44
Path of the transmitted signal ....................................................................................44
Fault finding charts for transmitter ............................................................................45
AMPS...................................................................................................................... 45
TDMA800............................................................................................................... 48
TDMA1900, GSM1900 .......................................................................................... 48
Power control loop .....................................................................................................51
AMPS AND TDMA................................................................................................ 52
GSM1900................................................................................................................ 53
Synthesizers ................................................................................................................. 54
19.2 MHz reference oscillator ...................................................................................54
Page 2 ãNokia Corporation Issue 1 07/02
NPM-2NX
CCS Technical Documentation Troubleshooting
Fault finding chart for 19.2 MHz oscillator ............................................................ 55
RX VHF VCO ...........................................................................................................55
Fault finding chart for RX VHF VCO .................................................................... 55
BB PLL ......................................................................................................................56
Fault finding chart for BB PLL............................................................................... 57
TX VHF VCO ............................................................................................................58
Fault finding chart for TX VHF VCO..................................................................... 58
UHF SYNTHESIZER ...............................................................................................59
Fault finding chart for UHF SYNTHESIZER......................................................... 60
Description of NPM-2NX RF Auto-tune Tuning ........................................................ 61
TDMA RF tunings .....................................................................................................61
TDMA RX tunings.................................................................................................. 61
TDMA TX tunings.................................................................................................. 62
GSM RF tunings ........................................................................................................64
GSM RX tunings..................................................................................................... 64
GSM TX tunings..................................................................................................... 66
List of Figures
Fig 1 UEM regulator's filter capacitors................................................................................5
Fig 2 BB testpoints ..............................................................................................................6
Fig 3 Power up sequence .....................................................................................................9
Fig 4 Fault tree, phone does not power up...........................................................................11
Fig 5 Fault tree, charging ....................................................................................................15
Fig 6 Fault tree, earpiece fail ..............................................................................................17
Fig 7 Fault tree, microphone fail .........................................................................................18
Fig 8 Fault tree, accessory detection ...................................................................................19
Fig 9 Fault tree, data cable...................................................................................................20
Fig 10 Fault tree, sleep clock...............................................................................................21
Fig 11 Fault tree, Display/Keyboard lights..........................................................................22
Fig 12 Fault tree, display ....................................................................................................23
Fig 13 Fault tree, infra red ...................................................................................................25
Issue 1 07/02 ãNokia Corporation Page 3
NPM-2NX
Troubleshooting CCS Technical Documentation
Transceiver T roubleshooting
General about testing
Phone operating modes
Phone has three different modes for testing/repairing phone. Modes can be selected with
suitable resistors connected to BSI- and BTEMP- lines as following:
Table 1: Mode selection resistors
Mode BSI- resistor BTEMP- resis t or Remarks
Normal 68k 47k
Local 560_ (<1k_) What ever
Test 3.3k (> 1k) 560_ (<1k_) Recommended with baseband testing. Same as
local mode, but making a phone call is possible.
The MCU software enters automatically to local or test mode at start-up if corresponding resistors are connected.
Note! Baseband doesn't wake up automatically when the battery voltage is c o nnected
(normal mode). Power can be switched on by
• Pressing the power key
• connecting a charger
• RC-alarm function
In the local and test mode the baseband can be controlled through MBUS or FBUS (FBUS
is recommended) connections by a Phoenix service software.
Page 4 ãNokia Corporation Issue 1 07/02
NPM-2NX
VR6
VR4
VR2
VR7
VR3
VR1B
VR1A
V
E
V
H
V
H
VANA
VIO
VR5
CCS Technical Documentation Troubleshooting
Measurement points
Figure 1: UEM regulator's filter capacitors
COR
FLAS
FLAS
UEM
VSIM
Issue 1 07/02 ãNokia Corporation Page 5
NPM-2NX
UEMINT PURX DbusCLK
FbusRX
Dbu
sENX
MbusRX
MbusTX
UEM
FLASH
UPP
Troubleshooting CCS Technical Documentation
Figure 2: BB testpoints
RFCLK:
Init clk
19.22MHz
GSM 13MHz
Page 6 ãNokia Corporation Issue 1 07/02
NPM-2NX
CCS Technical Documentation Troubleshooting
Baseband Troubleshooting
Note: ESN and IMEI has to re-written to phone If UEM is replaced. This can be
done only in Central Service.
The Baseband Troubleshooting instructions consists of the following topics:
•Power up
• Flash programming
•Audio
•Earpiece
•Microphone
• Charging
• Accessory detection
• Data cable
•Sleep clock
• User interface
•Display
•Lights
•Buzzer
•Vibra
•Keyboard
•Infra red
• Power up faults
Power up sequence
UEM acts as a HW master during start up
• Vbatt limits: 2.1V for internal state machine, 3V triggeri ng whole startup
• Regulator sequencing
Issue 1 07/02 ãNokia Corporation Page 7
NPM-2NX
Troubleshooting CCS Technical Documentation
•Hw "core" regulators "on": Vio, Vcore, VR3, Vflash1
•These regulators are supplying 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
•Core is ready to run but waiting for PURX release
• Reset releasing
•UPP releases the SLEEPX up to "non sleep" -state to prevent the UEM switching
the regulators "OFF"
MCU starts running the Bootsrap Code
•written in stone/ UPP internal ROM
•the program checks if there exists any reason for FDL mode (Flash Down Load)
•If there exists executable code in FLASH and there exists no reason for FDL, the
MCU starts running the MCU program from FLASH.
MCU runs the FLASH MCU code
•the phone initialization, user interfaces, internal bloc ks etc
•Core regulator voltage setting for required DSP speed
•Initializes the DSP and concerning hw
•Releases DSP reset -> DSP starts running
Note: In the figure below RF_Clk frequency appears to be lower than 19.2MHz
because of too low oscilloscope sampling frequency (2kS/s).
Page 8 ãNokia Corporation Issue 1 07/02
NPM-2NX
CCS Technical Documentation Troubleshooting
Figure 3: Power up sequence
1 Powe r key presse d
• After 20ms UEM enters RESET MODE if VBAT>Vmstr+
2 2) VFLASH1, Vana, Vcore, Vio and VR3 goes high.
• VCTCXO enabled by VR3 -> RFClk 19.2 MHz running.
3 Purx released
• Purx released by UEM, UEMINT goes high for 100 ms and about
500ms RFCLK will change 13MHz (GSM mode), SleepX goes high and
UEM starts feeding SleepClk (32 KHz) to UPP. NOTE! Sleepclock starts
running in crystal circuitry (B200) immedia tely when battery voltag e is
supplied.
4 Software running
• Default value for Vcore is 1.5 volts and if software is running Vcore will
rise to 1.8 volts.
• Cbus (1.00MHz/GSM and 1.08MHz/TDMA) clock starts running.
Issue 1 07/02 ãNokia Corporation Page 9
NPM-2NX
Troubleshooting CCS Technical Documentation
Phone does not start up normally or does not stay on
Note! In case of power up faults, it's not possible to force phone on by disabling watchdog. Instead, measurements should be done immediately when power key pressed or
when battery voltage connected to phone (loc al/test mode).
The easist way to check if software is running when phone takes abnormal amount of
current is to measure cbusclk and Vcore.
Dbus clock (programmable 9.72MHz TDMA, 13MHz GSM) is not automatically visible on
test and local mode.
Page 10 ãNokia Corporation Issue 1 07/02
NPM-2NX
CCS Technical Documentation Troubleshooting
Figure 4: Fault tree, phone does not power up
OK
Check 13MHz /GSM
or 19.44/TDMA
RF-clock from C420
OK
Try to start phone to
test or local mode
FAIL
Measure
Vflash1,Vana,Vio,Vcore
,VR3 when pwr key
pressed
VR3
missing
Check G801
(missing,
misaligned)
FAIL
Check
C420
OK
Check 19.2MHz
from G801
OK
FAIL
OK
FAIL
R816,C867,C8
66, R817, C868
OK
Check
Check the
power key
OK
Check R202,
R203, R205,
C217, C220
OK
Check
X101,C108,
C109,Z101
FAIL
Measure VBAT
from C262
OK
OK
troubleshooting
Check that purx
goes up to 1.8V
OK
Measure J406.
1.08
MHz/TDMA
and
1.00MHz/GSM
OK
Change UPP
(D400)
FAIL
FAIL
Re-flash phone
Programmng ok,
but phone doesn't
start
Flash Programming does not work
See RF
Change
G801
Change the
UEM (D200)
Programming
fails
Go to flash failure
chart
Flash programming procedure
• Phone communicates with prommer via production test pattern, using signals:
Issue 1 07/02 ãNokia Corporation Page 11
NPM-2NX
Troubleshooting CCS Technical Documentation
•FBUSTX(serial data to phone),
•FBUSRX(serial data from phone),
•MBUS(serial clock for FBUSRX)
•VPP(External flashing voltage for speed up flashing)
• Also BSI line is used when initializing flashing(battery connector)
• When phone is powered(VBAT>3V ) MBUS and FBUSTX lines are pulled up internally by phone.
• Prommer sends command to UEM, using FBUSRX, to enter Flash-mode. During
the sending of this command prommer keeps BSI line high and MBUS is used as a
serial clock.
• When Flash-mode command is acknowledged UEM enters Flash-mode and
releases reset (PURX) to MCU.
• After reset is released UPP checks if there is a request for Bootstrap code (that
resides in UPP ROM).
• Request for Bootstrap is MBUS pulled down by Prommer.(If bootstrap is not
requested, bootstrap code jumps to FLASH SW.)
• If Bootstrap code is requested UPP enters Flash-mode and sets FbusTX to ' 0 ' as
acknowledgement to prommer. This is an indication that UPP can run, at least,
the fixed Bootstrap code – although not able to run FLASH code. UPP then sends
an UPP-ID to prommer via FBUSTX line.
• After prommer has received UPP-ID it sends corresponding Secondary Boot Code
to phone via FBUSRX. Secondary Boot Code, when run in UPP, requests UPP to
send information to prommer about flash type and other HW related parameters
about the device to be flashed.
• Prommer then sends the Algorithm Code
and this algorithm, when run in UPP, takes over handling the MCUSW transfer to
Flash.
corresponding to the HW parameters
• 12 volts can be supplied to Vpp(by prommer) to speedup flashing.
• FLASH Program includes a package of MCU and DSP software and a ll default
parameters for the phone. The tuning values will be added/rewritten during
Flash/Alignment phase.
Page 12 ãNokia Corporation Issue 1 07/02
NPM-2NX
CCS Technical Documentation Troubleshooting
Flash programming error codes
Error codes can be seen from "FPS-8 Flash" in Phoenix.
Underlined note means that item under consideration is being used first time in flashing
sequence.
Table 2: Flash programming error co de s
Error Description Not workin g properly
C101 "The Phone does not set Fb us Tx line high af ter the
startup."
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."
C103 "Boot serial line fail." Mbus from Prommer->UEM-
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."
C106 "The Phone has not received Secondary code bytes
correctly."
Vbatt
Vflash1
Vcore
VIO
BSI and FbusRX from prommer to UEM.
FbusTx from UPP->UEM->Prommer(SA0)
PURX(also to Safari)
VR3
Rfclock(VCTCXO->Safari->UPP)
Mbus from Prommer->UEM>UPP(MbusRx)(SA1)
FbusTx from UPP->UEM->Prommer(SA1)
>UPP(MbusRx)(SA0)
FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
Mbus from Prommer->UEM->UPP(MbusRx)
FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
Mbus from Prommer->UEM->UPP(MbusRx)
FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
C107 "The Phone MCU can not start Seconda r y co de cor-
rectly."
A204 " The flash manufacturer and device IDs in the
existing Algorithm files do not match with the IDs
received from the target phone."
A387 "The MCU ID in the MCUSW UPP
C601 "The prommer has detected that Vpp voltage level
has dropped below the limit"
C383
C583
C683
"The Prommer has not received Phone acknowledge
to the message."
(C383-during algorithm download to target phone)
(C583-during erasing)
(C683-during programming)
UPP
Flash
Signals between UPP-Flash
Vpp from prommer - >Flash
Flash
UPP
Signals between UPP-Flash
Issue 1 07/02 ãNokia Corporation Page 13
NPM-2NX
Troubleshooting CCS Technical Documentation
C384
C584
C684
C585
C685
C586
C686
"The Phone has generated NAK signal during data
block transfer."
(C384-during algorithm download to target phone)
(C584-during erasing)
(C684-during programming)
Data block handling timeout"
(C585-during erasing)
(C685-during programming)
"The status response from the Phone informs about
fail."
(C586-during erasing)
(C686-during programming)
Flash
UPP
Signals between UPP-Flash
Flash
UPP
Signals between UPP-Flash
Flash
Page 14 ãNokia Corporation Issue 1 07/02
NPM-2NX
CCS Technical Documentation Troubleshooting
Charging
Note: Charging voltage and current can be checked by connecting phone to service
software and reading ad- converter values of vchar and ichar.
Figure 5: Fault tree, charging
Phone doesn't start
charging
Connect charger and
check VCHARIN,
check CHRG_CTRL
if used ACP -9,
LCH-8, LCH-9,
DCH-12, HFU-2
Fail
F100,L100,V100,C105
Check
, R107,C107
OK
Check ICHAR
FAIL
Check
R202,R203,R205,C217,
C220,C201,C202 and
R200
OK
Change t he
UEM
OK
Check bottom
connector
- VIN
- CHRG_CTRL
Audio failures
In case of audio failures there are three possibilities to ch eck audio lines.
1 Make a phone call against tester and check audios.
2 In case of earpiece/XMIC fail: Feed 1Khz signal to XMIC line and measure signal
from earpiece line. Audio test box JBA-8 is needed. Audio loop (Audio test/Ext In
Hp Out) must be switched on by Phoenix service software. This loop will connect
audios only through UEM. In this case UPP is not used.
Issue 1 07/02 ãNokia Corporation Page 15
NPM-2NX
Troubleshooting CCS Technical Documentation
3 In case of internal microphone/XEAR fail: Feed tone to microphone and measure
signal from XEAR line. Audio test box JBA-8 is needed. Audio loop (Audio test/Hp
In Ext Out) must be switched on by Phoenix service software. This loop will connect audios only through UEM. In this case UPP is not used.
4 Run audio- loop selftest with Phoenix (BB Self tests/ST_EAR_DATA_LOOP_TEST).
This loop will test the eardata/micdata lines between UPP and UEM.
Page 16 ãNokia Corporation Issue 1 07/02
NPM-2NX
CCS Technical Documentation Troubleshooting
Earpiece or external microphone line does not work
Figure 6: Fault tree, earpiece fail
Earpiece does n't
work
Run audio- loo p
selftest with
phoenix
OK
Check R157,L152,
L158,C150,C164,
C153, C 165,R152,
C156,C155,R164,
R161,R153,R150,
C159,C167,V153
OK
Check
earpiece
OK
Change UEM
Fail
Feed 1KHz to Xmic
by JBA-8 and
measure from
earpiece
Fail
OK
Change UPP
Issue 1 07/02 ãNokia Corporation Page 17
NPM-2NX
Troubleshooting CCS Technical Documentation
.Microphone or XEAR line does not work
Figure 7: Fault tree, microphone fail
Microphone doesn't
work
Run audio- l oop
selftest with
phoenix
Ok
Check
C151,C152,C157,L151,C162,
C168,C169,R156,R162,R166,
R159,C154,C158,C161,C166,
R163,L159,V152
Ok
Check
microphone
Ok
Change UEM
Fail
Feed 1KHz to Mic
and measure from
Xear by JBA-8
Fail
Ok
Change UPP
Page 18 ãNokia Corporation Issue 1 07/02
NPM-2NX
k
CCS Technical Documentation Troubleshooting
Accessory detection
• - Start phone to normal mode when checking accessory detection.
• - Ad- converter value of headint and hookint - lines can be checked with Phoenix
ADC-reading.
• - When headset HDC-9 connected and headset push button is held down, headint- value should be between 10 and 50 and hookint- value between 0-30.
Figure 8: Fault tree, accessory detection
Accessory d etection
doesn't work normally
Check HeadInt and
HookInt ad-value with
Phoenix
(No accessory
connected)
- HeadInt and HooInt
~1000
Fail
Check headint-line
L152,C150,R152,C153,
R154,
C160,R153,R150,C159
Ok
Check hookint-line
L159,R163,C158,R155,
R151,C161,V152
Ok
Ok
Connect HDC-9 and keep the
HDC-9 switch close while
reading headint and hookint
ad-value.
Both v a l ues s h ould go close to
zero (~0...50)
Fail
Calibrate ADC
and check
access ory
detection again
O
Check bottom
connector
Ok
Change UEM
Issue 1 07/02 ãNokia Corporation Page 19
NPM-2NX
Troubleshooting CCS Technical Documentation
Power supply for data cable
DLR-3 needs power supply for data transfering. SGND will supply 2.8V to DLR-3.
- Start phone to normal mode when checking DLR-3 detect ion
Figure 9: Fault tree, data cable.
DLR-3 data cable
doesn't work
Connect DLR-3, check
DLR-3 detection
Fail
Check the
components of
XMIC, HEADINT
and MIC B 2 lines
Ok
Check bot tom
connector
Ok
Ok
Check VFlash2
(~2.8V)
OK
Check SG ND voltage from
bottom connector
(2.40-2.90V)
Fail
Check V151,V152,R161,
C164,L158
Ok
Fail
Ok
Change U EM
Sleep Clock
Missing/non-functional sleep clock causes
• Entering sleep mode fails (higher current consumption -> shorter standby time)
• Baseband self tests cannot be run
Page 20 ãNokia Corporation Issue 1 07/02
Loading...