Nokia 9110 Service Manual 07trbl2
PAMS Technical Documentation
RAE–2 Series
Chapter 7
Troubleshooting
Original 02/99
Copyright 1999. Nokia Mobile Phones. All Rights Reserved.
RAE–2
PAMS
Troubleshooting
Amendment
Number
Date Inserted By Comments
02/99 Original
Technical Documentation
AMENDMENT RECORD SHEET
Page 7 – 2
Original 02/99
PAMS
RAE–2
Technical Documentation
CONTENTS –Troubleshooting
Introduction 7 – 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General 7 – 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Current consumption 7 – 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Finding faulty module 7 – 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CMT Troubleshooting 7 – 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Baseband faults 7 – 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CMT is totally dead 7 – 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power doesn’t stay on or phone is jammed 7 – 9. . . . . . . . . . . .
Display Information: Contact Service 7 – 10. . . . . . . . . . . . . . . . . .
The phone doesn’t register to the network... 7 – 10. . . . . . . . . . .
SIM card is out of order 7 – 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Audio fault 7 – 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Charging fault 7 – 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Flash programming doesn’t work 7 – 17. . . . . . . . . . . . . . . . . . . . .
RF Fault 7 – 21. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Required Servicing Equipment: 7 – 21. . . . . . . . . . . . . . . . . . . . . .
Test Points on BS8 Module 7 – 21. . . . . . . . . . . . . . . . . . . . . . . . . .
Transmitter fault 7 – 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Receiver fault 7 – 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AFC Fault 7 – 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1st IF 7 – 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2nd IF 7 – 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UHF LO 7 – 30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VHF LO 7 – 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting
Page No
PDA Troubleshooting and Service 7 – 32. . . . . . . . . . . . . . . . . . . . . . . . .
Required Servicing Equipment: 7 – 32. . . . . . . . . . . . . . . . . . . . . . . . .
Block Diagram 7 – 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BS1 PDA Components 7 – 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BS1 Troubleshooting 7 – 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power–on malfunction 7 – 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Power Circuitry Check 7 – 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting Diagram of the PLL clock 7 – 40. . . . . . . . . . . .
Troubleshooting Diagram of the LCD 7 – 44. . . . . . . . . . . . . . . . .
Troubleshooting Diagram of the PDA LCD Backlight 7 – 45. . . .
Troubleshooting Diagram of the PDA Keyboard 7 – 46. . . . . . . .
Troubleshooting Diagram of the serial connections 7 – 47. . . . .
Troubleshooting Diagram of the IR connection 7 – 49. . . . . . . . .
Troubleshooting Diagram of the lid switch 7 – 50. . . . . . . . . . . . .
Troubleshooting Diagram of the HF Speaker 7 – 51. . . . . . . . . . .
Troubleshooting Diagram of the Earphone 7 – 52. . . . . . . . . . . . .
Original 02/99
Page 7 – 3
RAE–2
PAMS
Troubleshooting
Troubleshooting Diagram of the Memory Card interface 7 – 53.
POST BEEP Codes 7 – 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UI Troubleshooting 7 – 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mechanical Troubleshooting 7 – 55. . . . . . . . . . . . . . . . . . . . . . . . . . .
Keyboard Troubleshooting 7 – 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CMT LCD Module Troubleshooting 7 – 56. . . . . . . . . . . . . . . . . . . . .
PDA LCD Display Troubleshooting 7 – 59. . . . . . . . . . . . . . . . . . . . . .
CMT Backlighting Circuit Troubleshooting 7 – 63. . . . . . . . . . . . . . . .
PDA LCD Backlighting Circuit Troubleshooting 7 – 64. . . . . . . . . . .
Technical Documentation
Page 7 – 4
Original 02/99
PAMS
RAE–2
Technical Documentation
Introduction
This document is intend to be a guide for localizing and repairing electrical faults in RAE–2 device. First there is short guide for fault localizing.
Then fault repairing is divided into three troubleshooting paths, each per
any module. Needed equipments are present before any actions.
Before any service operation you must be familiar with RAE–2 product
and module level architecture. You must also be familiar with RAE–2
specified service tools like the WinTesla service software, Flashing tools
and softwares. Basic skills of using RF measurement devices are required when you are starting to follow RF troubleshooting paths.
General
When you have a faulty RAE–2 device and you are starting troubleshooting it, check first the following basics.
Troubleshooting
–
Device hasn’t any mechanical damage.
– Device, especially connectors, are not dirty or moist.
– Screws are tightened as specificed.
– Battery voltage is high enough (nominal battery voltage is 3.6V).
– Current consumption is in normal area (this can be checked with Service Battery
BBS–5, if ReLink mode is disabled).
Current consumption
PDA mode (PDA current) Off (< 1.0mA) Idle (3–40mA) Call (140–320mA)
Active (200–380mA) 200–380mA 203–420mA 340mA–700mA
Standby (35–65mA) 35–45mA 38–85mA 175–365mA
Suspended (2–4mA) 2–3mA 5–43mA 142–323mA
Reset <1.0mA 3–40mA 140–320mA
Note1: CMT peak current consumption might be 5x more than is specified above.
Finding faulty module
CMT mode (CMT current)
Then you define the faulty module. Normally this isn’t difficult because
the RAE–2 device has three quite independent modules; CMT, PDA and
UI.
If you can’t conclude which is the faulty module, try to program new software to the RAE–2. Usually when a module has a real fault also its programming fails. If programming succeeds, it means that the CMT and
Original 02/99
Page 7 – 5
RAE–2
PAMS
Troubleshooting
PDA modules basically work and the fault might be in UI module or flex
connectors between PDA and UI module. Before CMT programming
check that PDA goes to the ReLink mode (use BBS–5 service battery).
After that you can replace the faulty module with the reference (Golden
Sample) module and be sure that module is really faulty. Alternatively
you can change the suspected faulty module to the reference RAE–2 device. After this cross–checking you should have found certainty about the
faulty module(s) and you can start to study module level problems.
Technical Documentation
Page 7 – 6
Original 02/99
PAMS
RAE–2
Technical Documentation
CMT Troubleshooting
The following hints should facility finding the cause of the problem when
the CMT circuitry seems to be faulty. This troubleshooting instruction is
divided in main level to BaseBand and RF faults.
The first thing to do is carry out a through visual check of the module. Ensure in particular that there are not any mechanical damages and soldered joints are OK. If the CMT module is able to communicate with WinTesla software, you can use it to find out faulty circuits from CMT module.
Selftest checks all CMT baseband Asics and memory components and
reports the result as passed or failed. If every test is passed, you can
perform different kind of calibration and tuning operations and deduce
which is the faulty circuit.
Baseband faults
At least the following measurement devices are needed for fault debugging in BaseBand section:
Troubleshooting
– PC for the Wintesla with software protection key (dongle)
– RS–232 cable (DAU –9C)
– Repairing jig MJS–4
– Flashing Tools FLA–7, FPS–4 and TDF–4
– Service Battery BBS–5
– Calibration Unit JBE–1
– power supply, digital multimeter and oscilloscope
Original 02/99
Page 7 – 7
RAE–2
PAMS
Troubleshooting
CMT is totally dead
Phone is totally dead
YES
J111
VBAT is 3.6 V
YES
J113 (PWRONx) 3.6 V
NO
Failure in VBAT line
Check X160,L103
Check shortcircuits
NO
Technical Documentation
This means that CMT doesn’t take current at all when
the power switch is pressed or when the Watchdog
Disable signal (J113) is rounded. Used battery voltage must be at least the nominal, 3.6 V.
Faulty circuit N110
YES
J109 (VBB) 2.8 V
N110 pin 25 (VXO) 2.8 V
when PWR switch is pressed
or watchdog disable pin is grounded
YES
See section: Power Doesn’t Stay On
Figure 1. Trouble Shooting Diagram for Phone is totally dead failure
PWRONX level (J113) low when
NO
PWR switch is pressed or
watchdog disable pin is (J100)
grounded
Faulty circuit N110
YES
Check V195, R195
NO
Check UI module
Page 7 – 8
Original 02/99
PAMS
RAE–2
Technical Documentation
Power doesn’t stay on or phone is jammed
Normally the power will be switched off by CCONT (N110) after 30 seconds, 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 (or J113) to ground.
Power doesn’t stay on or phone is jammed
YES
CCONT watchdog is served?
(pin 50 pulses 1 –> 0)
NO
YES
Troubleshooting
software is able to run
check UI module
If power is switched off
after few seconds, check
BSI and BTEM lines
connect the shortcircuit wire from J113 to ground (watchdog)
OK
check C213, R213
YES
J706 (RFC) 13 MHz
800 mV min
NO
check buffer V702 and
VCXO G690
J109 (VBB) 2.8V
J704 (VXO) 2.8V
YES
J240 master reset (Purx) =”1” (2.8V)
YES
NO
J219: 13MHz sine wave
clock signal: 500 mVpp min.
YES
Open pins or faulty circuit:
D200, D210, D221, N110
NO
VBAT is correct
3.6 V
NO J241 sleep clock (SLCK)
square wave 32 kHz
Faulty circuit N110
or over loaded PURX line
YES
YES
N110 is faulty
N110 is faulty
YES
NO
32 kHz in J100?
check PDA 32kHz
circuit and its
connections to
Figure 2. Trouble Shooting Diagram for Power Doesn’t Stay On or phone is jammed failures
NO
CMT
Original 02/99
Page 7 – 9
RAE–2
PAMS
Troubleshooting
Technical Documentation
Display Information: Contact Service
This fault means that software is able to run and thus the watchdog of
CCONT (N110) can be served. Selftest functions are run when power is
switched on and the software is started to execute from flash. If any of the
self–tests fails, Contact Service text will be shown on the display. Find
out which circuit is faulty using the WinTesla software (select from Testing
menu item Self Tests... and WinTesla shows which circuit are not passed
selftests).
The phone doesn’t register to the network or phone doesn’t make a call
If the phone does not register to the network or the phone does not 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 measurements).
The control lines for RF part are supplied both the System Asic (MAD2;
D200) and the RFI (Cobba; N250). MAD2 handles the digital control lines
(like synthe, TxP etc.) and Cobba handles the analog control lines (like
AFC, TxC etc.).
The DSP software is constructed so that the operation states of DSP
(MAD2) can be seen in external flag (DSPXF) output pin (J222). After
power up, the DSP signals all completed functions by changing the state
of the XF pin.
1. DSP initialization done
2.Synchronization to network
done
3. Registrarition to network
done.
1 2 3
Page 7 – 10
MAD2 (DSPXF)
J222
Original 02/99
PAMS
RAE–2
Technical Documentation
init
initialize
1
patch code
download
2
dsp
constants
download
initialization
done
Troubleshooting
MAD2 (DSPXF)
J222
channel
scan starts
PSW
search last PSW
OK
3
send RACH
RACH OK
go SDCCH
imediate assigment
OK
synchronization
OK
MAD2 (DSPXF)
J222
MAD2 (DSPXF)
J222
Original 02/99
Figure 3. The states of DSP after power on
Page 7 – 11
RAE–2
PAMS
Troubleshooting
Phone doesn’t register to the network
or
phone doesn’t make a call
YES
Analog supply voltage VCOBBA is >2.7 V)
at testpad J110
YES
Analog reference voltage Vref is 1.5 V
at J107
YES
Supply voltage VCP (N110 pin 32) > 4.8 V
Supply voltage VRX (N110 pin 9) > 2.7 V
Supply voltage VSYN_1 (N1 10 pin 15) > 2.7 V
Supply voltage VSYN_2 (N1 10 pin 4) > 2.7 V
during the receiving slot
Supply voltage VTX (N110 pins 11, 20) > 2.7 V
during the transmitting slot
NO
Check VCOBBA line
and N110 (CCONT)
NO
Check
R251
NO
Technical Documentation
Fault in N110 (CCONT)
or D200 (MAD2)
YES
Synthesizer lines: SEna (N690 pin 7),
SClk (N690 pin 5)
SData (N690 pin 6)
pulses 0 –> 1 during receiving slot
YES
NO
Fault in
D200 (MAD2)
RF control lines: RxC (N690 pin 36) 0 –> 2.3 Vmax during receiving slot
AFC (R547) 0 – 1.2 V typ. during receiving slot
YES
Analog data signal RxIP (N690 pin 24) 0–> 1.5 V DC during receiving slot
Analog data signal RxIN (N690 pin 23) 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 (J254) pulses 1 –> 0 during receiving slot
YES
RF control lines: TxC (N690 pin 34) 0 –> 2.3 Vmax during transmit slot
TxP (N690 pin 32) 0–>1 (2.8 V) during transmit slot
YES
NO
Fault in
N250 (COBBA)
NO
Fault in
N250 if DC is failed
Check
RF part if benefit signal is failed
Fault in
N250 (COBBA)
Fault in
NO
N250 if TxC is failed
Check
D200 if TxP is failed
Page 7 – 12
Analog data signals: TxIN (N690 pin 3) 0–> 0.8 V DC during transmit slot
TxIP (N690 pin 4) 0 –>0.8 V DC during transmit slot
TxQN (N690 pin 1) 0 –>0.8 V DC during transmit slot
TxQP (N690 pin 2) 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
Figure 4. The phone doesn’t register or doesn’t make a call
NO
N250 (COBBA)
YES
Check
RF part
Original 02/99
Fault in
PAMS
RAE–2
Technical Documentation
SIM card is out of order
The hardware of the SIM interface from the MAD2 (D200) to the SIM connector (X150) can be tested without SIM card. When the power is
switched on and if the BSI line (X160;2) is grounded by resistor, all the
used lines (VSIM, RST, CLK, DATA) rise up to 5 V four times. Thus ”In-
sert SIM card” faults can be found without SIM card. The fault information ”Card rejected” means that the ATR message (the first message is
always sent from card to phone) is sent from card to phone but the message is somehow corrupted, data signal levels are wrong etc. or factory
set values (stored to the EEPROM) are not correct.
Card Rejected fault
YES
VSIM is according the specification
VSIM = 2.8 V min (with 3 V SIM card)
VSIM = 4.5 V min (with 5 V SIM card)
NO
N110 (CCONT)
Troubleshooting
faulty circuit
YES
The ATR data can be seen at pin 43
(CCONT, N110)
YES
The ATR data can be seen
at pin 44 (CCONT, N110)
YES
SIMIOControl line (N110 pin 39)
is ”1”during the ATR message
YES
Check D200
NO
Fault in
NO
N110 (CCONT)
NO
Fault in
D200 (MAD2)
Check X302, R124,
X150 and shorcircuit
in V140, R141
Insert SIM card fault
YES
Voltage level < 1.5 V
at pin 2 of D100 when
BSI resistor is connected
YES
VSIM, DATA, RESET and CLOCK lines
rises up to 5 V after power on at pins
of SIM card
NO
VSIM(36), DATAO(43),SIMRSTO(42) and SIMCLKO(38) lines
rises up to 5 V after power on at pins of N110 (CCONT)
NO
SIMPWR(30), DATAA(44), SIMRSTA(40), SIMCLK(41) and
SIMIOC(39) lines rises up to 2.8V after power on pins of N110
NO
NO
Check
R120, R122, X160
YES
Check
SIM card and SIM
reader connectors
YES
Check X105,
R124, R125,
R128, V140,
R141
YES
faulty circuit
N110 (CCONT)
Original 02/99
Check again that voltage level at pin 2 (SIMCardDetX) of D110 is lower than 1.5V
If it is, change D200
Figure 5. Troubleshooting for SIM card faults
Page 7 – 13
RAE–2
PAMS
Troubleshooting
Audio fault
Troubleshooting tree for Audio fault:
Uplink (microphone) and downlink (earphone) are broken
Voltage at resistor R260 is 2.8 V
(without external audio devices)
HOOKDET
Voltage at resistor R261 is 2.8 V
(without external audio devices)
HEADDET
Frequency at J256 is 1 MHz, square
wave 2.8 Vpp
YES
YES
YES
Technical Documentation
NO
Check
R259, R260
NO
NO
Check
R257, R256, R261
Fault in
N250 (Cobba)
YES
Frequency at J257 is 8 kHz, square
wave 2.8 Vpp
Uplink (microphone) is broken
YES
Voltage at pin 1 of V271 is 1.8 V
Voltage at pin 3 of V271 is 0.3 V
during a call
YES
DC voltage at capacitors C273 and
C274 is 1.4 V during a call
YES
Analog audio signal (few millivolts) at capacitors C273
and C274 during a call
YES
Digital PCM data at J255 during a call
NO
NO
NO Fault in
Fault in
N250 (Cobba)
Check microphone, mic connections to
PCB and micbias components V250...
If OK, check that micbias control line
is (V270 base) 2.8 V during a call.
If no there is fault in D200 (MAD)
N250 (Cobba)
NO
NO
Check
C273, C274 and PCB
routings
Fault in
N250 (Cobba)
Page 7 – 14
Figure 6. Trouble Shooting Diagram for Audio Failure
Original 02/99
PAMS
RAE–2
Technical Documentation
Digital PCM data at J258 during a call
DC voltage at capacitors C252
and C256 is 1.4 V during a call
Analog audio signal (some ten millivolts) at C252 and
C256 during a call
Check earpeace connections to PDA module and
earpiece signal routing from CMT to PDA.
Downlink (earphone) is broken
YES
YES
YES
YES
NO
NO
N250 (Cobba)
Fault in
D200 (MAD2)
Fault in
NO
Troubleshooting
Fault in
N250 (Cobba)
Figure 7. Trouble Shooting Diagram for Audio Failure
Original 02/99
Page 7 – 15
RAE–2
PAMS
Troubleshooting
Charging fault
When you are charging totally empty battery, remember that start–up
charging might take 2 minutes with ACP–9 charger and several minutes
with ACP–7 charger. During this time display is blank.
If charger is not
NMP approved type
then the software
doesn’t start charging.
Remove and reconnect battery and
charger few times
before you start to
measure module.
This check ensure if
module fault really
exist.
Display Information: Not charging
YES
Technical Documentation
Nothing happens when charger is connected
YES
Voltage level at pin 60 of CCONT (N110)
is higher than 0.4 V when charger is connected
YES
Check with WinTesla software if SW has
detected charger and measured charger
current and voltage properly.
YES
Perform Energy Management
Calibration with WinTesla software and JBE–1 set and recheck
charger detection. If still fails
(CHAPS or CCONT) is broken.
NO
NO
Check
X170, F170
L170 and R170
Fault in N110
(CCONT)
Voltage level at pin 62 of CCONT (N110)
is about 0.45 V when power is connected.
BSI resistor value should be 33 k
YES
Voltage level at pin 63 of CCONT (N110)
is about 0.5 V when power is connected
BTEMP resistor value should be 47 k
YES
Check with WinTesla software if SW is
detected approved charger and measured
charger current and voltage properly.
YES
32 Hz square wave frequency at pin 7 of CHAPS (N120)
YES
Voltage levels at pins 5 and 12 of CHAPS (N120)
are same as VB
YES
Voltage levels at pins 5 and 12 of CHAPS (N120)
rises when charger is connected
NO
NO Check
NO
Check
X160, R121, R122,
D100, R123 and
VSYS = 2.8V
X160, R121, R122
Perform Energy Management
Calibration with WinTesla software and JBE–1 set and recheck charger detection, charger voltage and current. OK?
YES
NO
NO
NO
Charging?
Check
R131, N120
(CHAPS)
Fault in
N120 (CHAPS)
NO
Fault in N110
(CCONT) or
SW corrupted
Fault in
N110 (CCONT)
Page 7 – 16
Figure 8. Trouble Shooting Diagram for Charging Failure
Original 02/99
PAMS
RAE–2
Technical Documentation
Flash programming doesn’t work
The flash programming is done over the system connector X170.
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.
Troubleshooting
The test procedure is following:
1. Connect the short circuit wire between the test points J229 and ground.
2. Switch power on
3. If the voltage level in testpoint J203 is 2.8 V (”1”), the interface is OK. If
there is a short circuit, the voltage level in testpoint J203 stays low and
32kHz square wave signal can be seen in the lines which are already tested.
One must be noticed that this test can be found only short circuits, not
open pins. Also upper data lines (15:8) of flash circuit D210 are not included to this test.
Original 02/99
Page 7 – 17
RAE–2
PAMS
Troubleshooting
passed
Technical Documentation
CCONT pin 54
J240
MAD pin N3
SRAM pin 20
MAD pin B15
J203
(PURX)
(MCUAD0)
(FlashRP)selftest
Figure 9. MAD selftest indication after power on (passed)
Page 7 – 18
Original 02/99
PAMS
RAE–2
Technical Documentation
Flash programming doesn’t work
If the fault information from the prommer is:
Note:
When
Relink
OK,
PDA display
shows text
”Relink enabled”.
connect the short circuit wire J113 (WDOG) to ground
EEPROM (D240) pin 8 (VBB) 2.8 V
YES
a) MCU doesn’t boot
b) serial data line failure
c) serial clock line failure
Check ReLink
OK
OK
J704 (VXO) 2.8 V
YES
NOT OK
NO
PDA fault
VBAT is correct
3.6 V
Troubleshooting
YES
N110 is faulty
check C213, R213, V702 ...
YES
J706 (RFC) 13 MHz
800 mV min
NO
check
VCXO G690
NO J100 sleep clock (clk32k)
J240 master reset (PURX) = ’1’ (2.8 V)
YES
NO
check also pullup and pulldown resistors: R216, R215, R201
Enable the selftest function of D200 by connecting
shortcircuit between testpoints J229 and ground
Connect an oscilloscope to testpoint J203 and switch
Voltage level rises to ”1” after power on at testpoint J203
J219: 13 MHz sine wave
clock signal: 500 mVpp min.
YES
Check that following lines are correct:
FCLK (MBUS) line: X170 pin 7 –> J208
FTX (fbus_tx) line: X190 pin 38 –> J207
FRX (fbus_rx) line: X190 pin 37 –> J206
and series resistors R240
GND : X170 pin 1 –> GND
OK
power on
YES
or overloaded PurX line
square wave 32 kHz
YES
Faulty circuit N110
NO
There is a shortcircuit
somewhere in memory control
lines or MCU address lines or
MCU lower (7:0) data lines
NO
pin 14 –> J100
Check 32kHz
clock line
X173 pin 9
or
C190 pin 14
There could be open pins in circuits D200 (D210, D230)
If not, the PCB or D200 (D210, D230) is faulty
Figure 10. Trouble Shooting Diagram for flash programming doesn’t work (via system connector X170)
Original 02/99
Page 7 – 19
RAE–2
PAMS
Troubleshooting
Flash programming doesn’t work
YES
If the fault information from the prommer is:
External RAM fault
YES
Check pins of SRAM (D220)
Check control lines of SRAM:
RAMSelX ...
Flash programming doesn’t work
YES
Technical Documentation
If the fault information from the prommer is:
Algorithm file or alias ID don’t find, ID is unknown etc.
Faulty component D210 or faulty lines
Flash programming doesn’t work
YES
If the fault information from the prommer is:
MCU flash Vpp error
YES
Vpp > 4.5 V in C212
YES
Check components C212, R211
OK
NO
YES
Vpp > 4.5 V in C131
NO
Check C131, C132, V116, N110...
YES
Check regulator N201
Faulty component D210
Figure 11. Trouble shooting Diagram for Flash programming doesn’t work (via system connector X170)
Page 7 – 20
Original 02/99
Loading...