Nokia NSB-1 Series Guide

NSB–1/3 Series Transceivers
PAMS Technical Documentation
Original 06/98
Troubleshooting
Instructions

PAMS
Technical Documentation
NSB–1/3
Troubleshooting Instructions
Page 2 Original 06/98
CONTENTS
Page No
Trouble Shooting 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phone is totally dead 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flash programming doesn’t work 4. . . . . . . . . . . . . . . . . . . . . . .
Flash Programming (1) 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flash Programming failure (2) 7. . . . . . . . . . . . . . . . . . . . . . .
Power doesn’t stay on, or phone is jammed 8. . . . . . . . . . . . . .
Display Information: Contact Service 9. . . . . . . . . . . . . . . . . . . .
The phone doesn’t register to the network or phone doesn’t make a call 9
Phone register failure 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Instructions for RX troubleshooting 12. . . . . . . . . . . . . . . . . . .
Instructions for TX troubleshooting 14. . . . . . . . . . . . . . . . . . .
Fault finding chart for 13 MHz oscillator 16. . . . . . . . . . . . . . .
Fault finding chart for VHF VCO 17. . . . . . . . . . . . . . . . . . . . . .
Fault finding chart for UHF VCO 18. . . . . . . . . . . . . . . . . . . . . .
SIM card is out of order 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SIM Card failure 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Audio failure (1) 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Audio failure (2) 22. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Charger failure 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

PAMS
Technical Documentation NSB–1/3
Troubleshooting Instructions
Page 3
Original 06/98
Trouble Shooting
The following hints should facility finding the cause of the problem when
the circuitry seems to be faulty. This trouble shooting instruction is di-
vided following section.
1. Phone is totally dead
2. Flash programming does not work
3. Power does not stay on or the phone is jammed
4. Display information: Contact Service
5. Phone does not register to the network or phone does not make a call.
6. Plug in SIM card is out of order ( insert SIM card or card rejected).
7. Audio fault.
8. Charging fault
The first thing to do is carry out a through visual check of the module. En-
sure in particular that:
a) there are not any mechanical damages
b) soldered joints are OK

PAMS
Technical Documentation
NSB–1/3
Troubleshooting Instructions
Page 4 Original 06/98
Phone is totally dead
This means that phone doesn’t take current at all when the power switch
is pressed or when the watchdog disable pin (X001 pin 11) is grounded.
Used battery voltage must be higher than 3.0 V. Otherwise the hardware
of CCONT (N100) prevents totally to switch power on.
Phone is totally dead
YES
YES
Voltage at pin 29 of CCONT (N100)
is 3.6 V
NO Faulty circuit N100
YES
N100 pin 55 (VBB) 2.8 V
N100 pin 25 (VXO) 2.8 V
when PWR switch is pressed
or watchdog disable pin is grounded
NO CCONT (N100) pin 29 0V when
PWR switch is pressed or
watchdog disable is grounded
YES
See section: Power Doesn’t Stay On
YES
Faulty circuit N100
NO Check X99,R103
Check UI module
NO Failure in VBAT line
Check X101, X102
Check VBATT at CCONT
(N100 pins 8,12,...) =3.6V
Flash programming doesn’t work
There are two possibilities to route programming voltage VPP.
– If regulator N200 is used the programming voltage comes from the reg-
ulator (VPPSW) via UI–connector to flash memory D210.
– Other way is to route Vpp from CCONT pin36 to UI–connector and
again to flash memory.
In flash programming error cases the flash prommer can give some in-
formation about a fault.
The fault information messages could be:
– MCU doesn’t boot
– Serial clock line failure
– Serial data line failure
– External RAM fault
– Algorithm file or alias ID don’t find
– MCU flash Vpp error

PAMS
Technical Documentation NSB–1/3
Troubleshooting Instructions
Page 5
Original 06/98
In cases that the flash programming doesn’t succeed there is a possibility
to check short circuits between the memories and the MCU (MAD2).
This test is useful to do, when the fault information is: MCU doesn’t boot,
Serial clock line failure or Serial data line failure.
The test procedure is following:
1. Connect the short circuit wire between the test points J206 and J207.
2. Switch power on
3. If the voltage level in testpoint J205 is 2.8 V (”1”), the interface is OK. If
there is a short circuit, the voltage level in testpoint J205 stays low and
32kHz square wave signal can be seen in the lines which are already
tested.
This test can only be used to find short circuits, not open pins. Also upper
data lines (15:8) of flash circuit D210 are not included to this test.
CCONT pin 54( PURX )
MAD pin 38 ( MCUAD0)
MAD pin 134 ( ExtSysResX))selftest
passed J205

PAMS
Technical Documentation
NSB–1/3
Troubleshooting Instructions
Page 6 Original 06/98
Flash Programming (1)
Flash programming doesn’t work
EEPROM (D230) pin8 (VBB) 2.8V
VVCXO 2.8V (G703, C721) NO
See section: Phone is totally dead
YES
J121 (Purx)=”1” (2.8V) NO Sleep clock (SCLK) J201
square wave 32 kHz NO
YES
Faulty circuit N100
or over loaded PurX line
check sleep
clock circuitry
(B150,R197...)
YES
MAD2 pin 93 (J200): 13MHz sine wave
clock signal: 500 mVpp min.
YES
NO
Check that following lines are correct from X131 to D200:
YES
If the fault information from the prommer is:
b) serial data line failure
a) MCU doesn’t boot
c) serial clock line failure
connect:
FBUS_TX: X131 pin13 –> D200 pin104
FBUS_RX: X131 pin12 –> D200 pin109
check also pullup and pulldown resistors: R200, R201, R123
OK
GND : X131 pin 9 –> GND
connect watchdog disable (J114) to GND (J113)
OK
OK
Enable the selftest function of D200 by connecting
shortcircuit between testpoints J206 and J207
Connect an oscilloscope to testpoint J205 and switch
power on
Voltage level rises to ”1” after power on at testpoint J205 NO
YES
There is a shortcircuit
somewhere in memory control
lines or MCU address lines or
MCU lower (7:0) data lines
There could be open pins in circuits D200 (D211, D240)
If not, the PCB or D200 (D221, D210) is faulty
WDDIS line –> N100 pin29
check
Check
Fault finding chart
for 13 MHz
oscillator
MBUS: X131 pin11 –> D200 pin112

PAMS
Technical Documentation NSB–1/3
Troubleshooting Instructions
Page 7
Original 06/98
Flash Programming failure (2)
Flash progrmming doesn’t work
YES
If the fault information from the prommer is:
External RAM fault
YES
Check pins of SRAM (D221)
Check control lines of SRAM:
RAMSelX ... Flash progrmming doesn’t work
YES
If the fault information from the prommer is:
Algorithm file or alias ID don’t find, ID is un-
known etc.
YES
Check control lines and upper data lines (15:8)
of FLASH: ROM1SelX...
Check pins of FLASH (D210)
Flash progrmming doesn’t work
YES
If the fault information from the prommer is:
MCU flash Vpp error
D210 pin13 (C211)
Vpp=2.8V
Faulty component
D210 or C211
YES
NO
Check UI connector X99
and zero ohm resistor
Check output of regulator
N200 pin4 2.8V
NO
Faulty component N200
or C213, C212
Check V8
N200 pin6
NO
YES
YES
Check V109,
C124, C148
Faulty
component
N100

PAMS
Technical Documentation
NSB–1/3
Troubleshooting Instructions
Page 8 Original 06/98
Power doesn’t stay on, or phone is jammed
If this kind of fault has come after flash programming, there are most
probably open pins in ICs.
The soldered joints of ICs: D200 (MAD2), D210 (FLASH), N100
(CCONT), D221 (SRAM) are useful to check at first.
Normally the power will be switched of by CCONT (N100) after 30 se-
conds, if the watchdog of the CCONT can not be served by software.
The watchdog updating can be seen by oscilloscope at pin 50 (DataselX)
of CCONT.
In normal case there is a short pulse from ”1” –> 0 every 8 seconds.
The power off function of CCONT can be prevented by connecting a short
circuit wire from CCONT pin 29 to ground.
Power doesn’t stay on or phone is jammed
EEPROM (D230) pin8 (VBB) 2.8V
VVCXO 2.8V (CCONT pin25 –> G703) NO
YES
J121 (PURX) = ”1” (2.8V) NO J201 sleepclk (SLCLK)
square wave 32 kHz NO
YES
Faulty circuit N100
or over loaded PurX line
check sleep
clock circuitry
YES
MAD2 (D200) pin 93: 13 MHz sine wave
clock signal: 500 mVpp min.
YES
NO
YES
Connect watchdog (WWDDIS) to GND (J113,J114)
N100 is faulty
OK
VBAT is correct
3.6 V
YES
CCONT watchdog is served?
(pin 50 pulses 1 –> 0)
NO
YES
software is able to run
check UI module
after few seconds, check
BSI and BTEMP lines
If power is switched off
Open pins or faulty circuit:
D200, D210, D221, N100
(B150, R197...)
Check:
Fault finding chart for
13MHz oscillator

PAMS
Technical Documentation NSB–1/3
Troubleshooting Instructions
Page 9
Original 06/98
Display Information: Contact Service
This fault means that software is able to run and thus the watchdog of
CCONT (N100) can be served.
Selftest functions are run when power is switched on and software is
started to excute from flash.
If any of selftests failed, contact service information will be shown on dis-
play.
The phone doesn’t register to the network or phone
doesn’t make a call
f the phone doesn’t register to the network or the phone doesn’t make a
call, the reason could be either the baseband or the RF part.
The phone can be set to wanted mode by WinTesla service software and
determinate if the fault is in RF or in baseband part (RF interface mea-
surements).
The control lines for RF part are supplied both the System Asic
(MAD2;D200) and the RFI (Cobba; N300). MAD2 handles digital control
lines ( like synthe, TxP etc.) and Cobba handles analog control lines (like
AFC, TxC etc.).
The DSP software is constructed so that operation states of DSP (MAD2)
can be seen in external flag (DSPXF) output pin (D200 pin 91).
MAD2 pin 91 (DSPXF)
1 2 3
1. DSP initialization done
2.Synchronization to network
done
3. Registrarition to network
done.
J222

PAMS
Technical Documentation
NSB–1/3
Troubleshooting Instructions
Page 10 Original 06/98
1
2
3
MAD2 pin 91 (DSPXF)
J222
MAD2 pin 91 (DSPXF)
J222
MAD2 pin 91 (DSPXF)
J222
init
initialize patch code download
dsp
constants
download
initialization
done
synchronization
OK
channel
scan starts
PSW
search last PSW
OK
send RACH
RACH OK
go SDCCH
imediate assigment
OK