How it Works
Nokia
Loading...
6090
Service Manual install
12 pgs95.06 Kb3
User Manual
49 pgs613.7 Kb1
User Manual [fr]
49 pgs701.44 Kb0
Service Manual gm8bv7
20 pgs1.25 Mb1
Service Manual trouble
63 pgs249.13 Kb1
User Manual [no]
49 pgs659.69 Kb0
User Manual [nl]
49 pgs635.61 Kb0
Service manual
373 pgs5.78 Mb1
Service Manual ah89v4
8 pgs521.84 Kb1
Service Manual techinfo
66 pgs339.26 Kb0
Service Manual servtool
14 pgs356.63 Kb0
Service Manual servsoft
73 pgs763.91 Kb0
Service Manual general
8 pgs27.39 Kb0
Service Manual frontsec
8 pgs45.86 Kb0
User Manual [de]
49 pgs687.72 Kb0
Service Manual parts
39 pgs71.7 Kb0
Service Manual mech
14 pgs864.28 Kb2
User Manual
11 pgs36.05 Kb0
User Manual [sv]
49 pgs695.18 Kb0
User Manual
47 pgs817.21 Kb0
Service Manual jbd2
28 pgs247.27 Kb0
Service Manual gm8bv6
20 pgs1.2 Mb1
User Manual
12 pgs125.23 Kb0
User Manual [da]
49 pgs674.73 Kb0
User Manual [it]
49 pgs676.67 Kb0
User Manual [fi]
49 pgs648.13 Kb0
User Manual
47 pgs573.72 Kb0
User Guide
33 pgs446.2 Kb0
User Manual
84 pgs297.85 Kb0
User Manual [pl]
47 pgs1.22 Mb0
User Manual [tr]
47 pgs721.34 Kb0
Table of contents
Loading...

Nokia 6090 Service Manual trouble

Programme’s After Market Services
NME–3 Series Transceivers

Troubleshooting

Issue 1 10/99
NME–3
PAMS
Troubleshooting
Technical Documentation
CONTENTS
Introduction 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radiounit failures 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flashing failures 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phone doesn’t Power On 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phone doesn’t Power Off 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handset not recognized 15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Phone doesn’t register to network or phone doesn’t make a call 15
Receiver faults 19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transmitter faults 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AMC not working 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Car Radio Mute not working 48. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Backlight dimming not working 49. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Audio failure Handsetmode 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Audiofailure Handsfreemode 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Failure in Data interface 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SIM–Card not recognized 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handset failures 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Microphone path fault 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Earpiece path fault 60. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LCD fault 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SIM interface fault 61. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Keypad fault 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BLD fault 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hall sensor fault 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power key fault 63. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Issue 1 10/99
PAMS
NME–3
Technical Documentation

Introduction

This document gives a comprehensive guide to NME–3 faultfinding.
NOTE
ules and ensure that: a) There is no mechanical damages at the units b) Soldered joints are o.k. c) check which unit is broken HS or Radiounit
NOTE
umentations. (Power supply connected to the unit, IGNS high, Handset conneced,...)
The following hints should make it easier to find the cause of the problem when the product seems to be faulty. This trouble shooting instruction is divided into the following sections:
: The first thing to do is carry out a through visual check of the mod-
: Make sure that the system is installed as specifided in the AS doc-
Troubleshooting
1. Which Unit is broken
2. RU failures
3. HS failures
Which Unit is broken
To check which unit is broken, the following steps should be performed: Have a look at the failure describtion, if it doesn’t already indicate which
unit is broken, follow the procedure descibed below:
if there is a handset audio problem, connect the HS to a reference Radio­unit and check if the problem is still there.
if the the system is not working at all then follow the steps described be­low:
– Connect the HS to 8V – check if the current consumption is O.K. – check if the Nokia Hands are shown – If both things are O.K. connect the HS to a reference Radiounit and check if it
works without problems
– In this case it is most likely a Radiounit problem, in all other cases it is most likely
a Handset problem
– Important NOTE: After repair of one unit it allways have to be checked that the
combination of both units is working !!!
Issue 1 10/99
NME–3
PAMS
Troubleshooting

Radiounit failures

This chapter describes how to find failures in the Radiounit:
Radiounit doesn’t Powerup
Connect the Radiounit to +12V while ignition sense is switched off and look to see if the Leds are turned ON for a short time
– If they don’t turn on at all,
– check the current consumtion, if it is about 300– 400uA the wakeup
logic should be checked, if it is much less or more there is a Problem
in the powersupply – Check the status of all voltages – Check the status of the wakeup logic
– If the Leds stay on,
– Check the digital part
Technical Documentation
– Check powerdown logic
– If the LEDs go off as specifed and current is O.K.: – Try to wakeup the radiounit by turning Ignition sense ON,
– if the Leds stay on go to the next step – if they don’t stay on or don’t turn on at all check the Ignition circuit
– Try to wakeup the radiounit by pressing the powerbutton of the HS,
– if the Leds stay on go on, try flashing the unit – if they don’t stay on or don’t turn on at all check the Powerbutton cir-
cuit
Issue 1 10/99
PAMS
NME–3
Technical Documentation
12V at V1
Yes
12V at C437
Yes
3.8V at C426
No
No
No
Check PCB fuse, and solder­joints on system­connector
Check L13
Check N402 and V404
Troubleshooting
Yes
12V at C410
Yes
8V at C415
Yes
8V at C404
Yes
No
No
Check N401
No
PURX high D701 Pin 9
Yes
voltage at C403 =0.7V
No
Check N400
No
Yes
Check Overvoltagecircuit
Check wakeup logic
Check V400, V403
Powersupply O.K.
Issue 1 10/99
Figure 1.
Check the voltages and powersupply
NME–3
PAMS
Troubleshooting
Is Pin 9 of D702 high
No
Is Pin 13 of D702 high
Yes
Yes
No
Check circuit on Pin 13 of D702
Technical Documentation
Disconnect the Powersupply Connect Probe to Pin 3 of D701 set scope to singletrigger falling edge, reconnect the powersupply
Scope pic according figure 1
Yes
No
Check D701
Check D702
Check that a low pulse is produced on Pin 10 of D702 when switching Power On
D701 Pin 9 high
Yes
LEDs on
Yes
No
Check CCONT
No
Check Powersupply
Check Digitalpart
Figure 2. check wakeup circuit
Issue 1 10/99
PAMS
NME–3
Technical Documentation
32 Khz clock on N700 Pin 48
Yes
13 Mhz clock on N700 Pin 48
Yes
No
Check CCONT and 32Khz oscilator
No
Check VCXO circuit
Troubleshooting
Frequent data from MAD to CCONT on CCONT PIN 49–51
No
Check D600.. D603 for open solder joints shortcircuits and broken components
Yes
Try to flash new SW
Issue 1 10/99
Figure 3. check digital part
NME–3
PAMS
Troubleshooting
D702 Pin 10 high ??
No
Is SW producing a Powerdown signal on R721
Check circuit arround V707 and D702
Technical Documentation
Yes Check circuit connected
to this pin
No
Signal on R600 low
Yes
Signal on R603 low
Yes
No
No
check related circuit
check related circuit
Try to Flash new SW
check digital part
Figure 4. Check Powerdownlogic
Issue 1 10/99
PAMS
NME–3
Technical Documentation

Flashing not possible

The flash programming can be done via system connector X1. In production, the first programming is done applying 12V flashvoltage to TP610. In aftersales the Flashvoltage is generated by an on board regu­lator.
The main differences between production flashing and aftersales flashing are :
a) FLASH programming voltage is produced in a different way. b) Signal routings are different.
The fault finding diagrams for production flash programming are shown in figures 5 and 6. The fault finding diagrams for aftersales flash programming are shown in figures 7 and 8.
Troubleshooting
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
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 J229 and J230.
2. Switch power on to start selftest
3. If the voltage level in D600 PIN 134 is 2.8 V (”1”), the interface is OK. If there is a short circuit, the voltage level in D600 PIN 134 stays low and 32kHz square wave signal can be seen in the lines which are already tested.
Selftest behaviour can be seen on the next page.
Note this test can be found only short circuits, not open pins.
Also upper data lines (15:8) of flash circuit D602 are not included to this test.
Issue 1 10/99
NME–3
PAMS
Troubleshooting
passed
Technical Documentation
CCONT pin 54
MAD pin 38
MAD pin 134
( PURX )
( MCUAD0)
( ExtSysResX))selftest
Page 10
Issue 1 10/99
PAMS
NME–3
Technical Documentation
Production Flash Programming Failure (1)
Flash programming doesn’t work
YES
If the fault information from the prommer is:
a) MCU doesn’t boot b) serial data line failure
c) serial clock line failure
connect:
connect watchdog disable (WDDIS) line (N700 PIN 28) to ground
OK
EEPROM (D601) Pin 8 (VBB) 2.8V
C706 (VXO) 2.8V
YES
NO
Troubleshooting
See section: Phone is totally dead
check C213, R213
YES
R607 (RFC) 13Mhz
800 mV min
NO
check buffer V300 and
VCXO G300
NO TP700 clock(SCLK)
D701 PIN 9 PURX =”1” 2.8V
YES
NO
MAD2 (D600) pin 93 13 Mhz sine wave
clock signal: 500 mVpp min.
YES
Check that following lines are correct: FCLK (MBUS) line: X1 pin 22 –> D600 pin 112 FTX (fbus_tx) line: X1 pin 6 ––> D600 pin 104
FRX (fbus_rx) line: X1 pin21 .–>D600 pin 109
check also pullup and pulldown resistors: R606,R614,R617
Check D700, no low signal from N650
OK
Enable the selftest function of D200 by connecting
Voltage level rises to ”1” after power on at D600 Pin 134
D600 PIN 17 to GND
Connect an oscilloscope to D600 PIN 134 and
power on
YES
square wave 32 kHz
YES
Faulty circuit N700
or over loaded PurX line
NO
There is a shortcircuit
somewhere in memory control
lines or MCU address lines or
MCU lower (7:0) data lines
check sleep
NO
clock circuitry
(B701,R707,..)
Issue 1 10/99
There could be open pins in circuits D600 (D602, D603)
If not, the PCB or D600 (D602, D603) is faulty
Figure 5.
Page 11
NME–3
PAMS
Troubleshooting
Production 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 (D603) Check control lines of SRAM:
RAMSelX ...
Flash progrmming doesn’t work
YES
Technical Documentation
If the fault information from the prommer is: Algorithm file or alias ID don’t find, ID is un­known etc.
YES
Check pins of FLASH (D602)
Check control lines and upper data lines (15:8) of FLASH: ROM1SelX...
Flash progrmming doesn’t work
YES
If the fault information from the prommer is: MCU flash Vpp error
YES
Check connection between TP610 ––> D210; 13
Check components C600, R612, N600, V600
OK
Page 12
Faulty component D602
Figure 6.
Issue 1 10/99
PAMS
NME–3
Technical Documentation
Aftersales Flash Programming failure (3)
Flash programming doesn’t work
YES
If the fault information from the prommer is:
a) MCU doesn’t boot b) serial data line failure
c) serial clock line failure
connect:
connect the shortcircuit wire from N700 pin 29 to Ground (watchdog)
OK
EEPROM (D601) pin 8 (VBB)
C706 (VTX) 2.8V
YES
NO
VBAT is correct
3.8 V
Troubleshooting
YES
N700 is faulty
check C213, R213
YES
R607 (RFC) 13Mhz
800 mV min
NO
check buffer V300 and
VCXO G300
NO C728 sleep clock (SCLK)
D701 Pin 9 PURX = ”1” (2.8V)
YES
NO
MAD2 (D600) pin 93 13 Mhz sine wave
clock signal: 500 mVpp min.
YES
Check that following lines are correct: FCLK (MBUS) line: X1 pin 22 –> D600 pin 112 FTX (fbus_tx) line: X1 pin 6 ––> D600 pin 104
FRX (fbus_rx) line: X1 pin21 .–>D600 pin 109
check also pullup and pulldown resistors: R606,R614,R617
Check D700, no low signal from N650
OK
Enable the selftest function of D200 by connecting
Voltage level rises to ”1” after power on at D600 Pin 134
D600 PIN 17 to GND
Connect an oscilloscope to D600 PIN 134 and
power on
YES
square wave 32 kHz
YES
Faulty circuit N700
or over loaded PurX line
NO
There is a shortcircuit
somewhere in memory control
lines or MCU address lines or
MCU lower (7:0) data lines
NO
clock circuitry
(B 701, R707)
check sleep
Issue 1 10/99
There could be open pins in circuits D600 (D602, D603)
If not, the PCB or D600 (D602, D603) is faulty
Figure 7.
Page 13
NME–3
PAMS
Troubleshooting
Aftersales Flash Programming failure (4)
Flash progrmming doesn’t work
YES
If the fault information from the prommer is: External RAM fault
YES
Check pins of SRAM (D603) Check control lines of SRAM:
RAMSelX ...
Flash progrmming doesn’t work
YES
Technical Documentation
If the fault information from the prommer is: Algorithm file or alias ID don’t find, ID is un­known etc.
Check pins of FLASH (D602)
Check control lines and upper data lines (15:8) of FLASH: ROM1SelX...
Flash progrmming doesn’t work
YES
If the fault information from the prommer is: MCU flash Vpp error
YES
Vpp > 3 V in D602 pin 13 (or C600)
YES
Check components C600, R612
OK
NO
YES
Vpp > 3 V in testpoint TP610
YES
Check D601 for bad soldering
NO
Check regulator N600
Page 14
Faulty component D601
Figure 8.
Issue 1 10/99
PAMS
NME–3
Technical Documentation

Phone doesn’t Power On

This is described in section 2.2.1

Phone doesn’t Power Off

Press Powerbutton, and check if Powerdown pulse is produced on R 721, if it isn’t check Powerbutton circuit, if it is produced check circuit around
D702 according to Figure 5. Set Auto power off to 45 seconds, switch Ignition Off, look if a message
Power will switch of if not used comes up after some seconds. If not check Ignitionsensecircuit
If yes check if the powerdownpulse is produced on R721, if it is check cir­cuit arround D702 according to figure 2.
If no pulse is produced check the connection from R721 to D600 !!

Handset not recognized

Connect a probe to R606, and check if the line is high and carrying HS signals, if it check the resistor and the MAD D600.
Troubleshooting
If yes follow the M–Bus signal to the connector.

Phone doesn’t register to network or phone doesn’t make a call

If 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 by both the System Asic (MAD2;D600) and the RFI (Cobba; N800). 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 (D600 pin 91).
After power up, DSP signals all completed functions by changing the state of the XF pin (see figure 9 for complete timing and figure10 for detailed timing).
Issue 1 10/99
Page 15
NME–3
PAMS
Troubleshooting
Technical Documentation
1. DSP initialization done
2.Synchronization to network done
3. Registrarition to network done.
1 2 3
MAD2 pin 91 (DSPXF)
Figure 9.
Page 16
Issue 1 10/99
PAMS
NME–3
Technical Documentation
init initialize
1
patch code download
2
dsp constants download
initialization done
Troubleshooting
MAD2 pin 91 (DSPXF)
channel scan starts
PSW search last PSW
OK
3
send RACH RACH OK
go SDCCH imediate assigment OK
synchronization OK
MAD2 pin 91 (DSPXF)
MAD2 pin 91 (DSPXF)
Issue 1 10/99
Figure 10.
Page 17
NME–3
PAMS
Troubleshooting
Phone register failure
Phone doesn’t register to the network
Analog supply voltage VCOBBA is >2.7 V
at pin 7,12 ... of Cobba (N800)
Analog reference voltage Vref is 1.5 V
Supply voltage VCP (N700 pin 32) > 4.8 V
Supply voltage VRX (N700 pin 9) > 2.7 V
Supply voltage VSYN_1 (N700 pin 15) > 2.7 V
Supply voltage VSYN_2 (N700 pin 4) > 2.7 V
Supply voltage VTX (N700 pins 11, 20) > 2.7 V
phone doesn,t make a call
or
YES
YES
at pin 9 of Cobba (N800)
YES
during the receiving slot
during the transmitting slot
Check
NO
N700
NO
Check
R800,C800
NO Check
Technical Documentation
N700, D600
YES
Synthesizer lines: SEna (N101 pin 56),
SClk (N101 pin 54)
SData (N101 pin 55)
pulses 0 –> 1 during receiving slot
YES
NO
Check
D600
RF control lines: RxC (N800 pin 18) 0 –> 2.3 Vmax during receiving slot
AFC (N800 pin 19) 0 – 1.2 V typ. during receiving slot
YES
Analog data signal RxIP (N800 pin 22) 0–> 1.5 V DC during receiving slot Analog data signal RxIN (N800 pin 22) 0–> 1.5 V DC during receiving slot
Used benefit signal is biased to DC and its amplitude is 50 mVpp
nominal and frequency is 13 MHz
YES
NO
DAX signal (N800 pin 48) pulses 1 –> 0 during receiving slot
YES
RF control lines: TxC (N800 pin 17) 0 –> 2.3 Vmax during transmit slot
TxP (D600 pin 176) 0–>1 (2.8 V) during transmit slot
YES
NO
Check
N800
NO
Check
N800 if DC is failed
Check
RF part if benefit signal is failed
Check
N800
Check
NO
N800 if TxC is failed
Check
D600 if TxP is failed
Page 18
Analog data signals: TxIN (N800 pin 13) 0–> 0.8 V DC during transmit slot
TxIP (N800 pin 14) 0 –>0.8 V DC during transmit slot TxQN (N800 pin 15) 0 –>0.8 V DC during transmit slot TxQP (N800 pin 16) 0 –>0.8 V DC during transmit slot
Used benefit signal is biased to DC and its amplitude is 300 mVpp
nominal and frequency is 64 kHz
NO
YES
Check
N800
Check
RF part
Issue 1 10/99
PAMS
NME–3
Technical Documentation

Receiver faults

This section gives an overview of the strategies used to hunt failures and defects in the receiver path of the radio unit. Tracking of receiver errors is best done by following the RX signal path and tracking the signal applied to the antenna port with a probe and a spectrum analyzer. The following steps should be done prior to the signal tracking:
– Apply test signal generated by CMD55 to antenna port.
– Set radio unit to local mode with Wintesla. – Choose RF Controls from Wintesla Testing menu. – Perform the following settings:
The test signal should then be tracked through the rx signal path by fol­lowing the procedures given in the figures below.
Troubleshooting
Frequency: 947 MHz Level: –55dBm
Set RX continuous mode Set Cont. mode channel 60 Tick front end on.
The RF levels given in the following flow charts were measured with a Hewlett Packard RF probe. When measuring the levels with a different probe the resulting levels may be different. The most important thing to check is wether there is a signal present or not.
Issue 1 10/99
Page 19
Loading...
+ 44 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use