Text preview for : 07trbl2.pdf part of Nokia 9110 Nokia 9110 Service Manual
Back to : Nokia 9110 Service Manual | Home
PAMS Technical Documentation RAE2 Series
Chapter 7 Troubleshooting
Original 02/99
Copyright E 1999. Nokia Mobile Phones. All Rights Reserved.
RAE2 Troubleshooting
PAMS Technical Documentation
AMENDMENT RECORD SHEET
Amendment Date Number Inserted By Comments Original
02/99
Page 7 2
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
CONTENTS Troubleshooting Page No
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Current consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Finding faulty module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CMT Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Baseband faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CMT is totally dead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power doesn't stay on or phone is jammed . . . . . . . . . . . . Display Information: Contact Service . . . . . . . . . . . . . . . . . . The phone doesn't register to the network... . . . . . . . . . . . SIM card is out of order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audio fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Charging fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Flash programming doesn't work . . . . . . . . . . . . . . . . . . . . . RF Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Required Servicing Equipment: . . . . . . . . . . . . . . . . . . . . . . Test Points on BS8 Module . . . . . . . . . . . . . . . . . . . . . . . . . . Transmitter fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Receiver fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AFC Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1st IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2nd IF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UHF LO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VHF LO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDA Troubleshooting and Service . . . . . . . . . . . . . . . . . . . . . . . . . Required Servicing Equipment: . . . . . . . . . . . . . . . . . . . . . . . . . Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BS1 PDA Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BS1 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Poweron malfunction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Circuitry Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Diagram of the PLL clock . . . . . . . . . . . . Troubleshooting Diagram of the LCD . . . . . . . . . . . . . . . . . Troubleshooting Diagram of the PDA LCD Backlight . . . . Troubleshooting Diagram of the PDA Keyboard . . . . . . . . Troubleshooting Diagram of the serial connections . . . . . Troubleshooting Diagram of the IR connection . . . . . . . . . Troubleshooting Diagram of the lid switch . . . . . . . . . . . . . Troubleshooting Diagram of the HF Speaker . . . . . . . . . . . Troubleshooting Diagram of the Earphone . . . . . . . . . . . . . 7 5 7 5 7 5 7 5 7 7 7 7 7 8 7 9 7 10 7 10 7 13 7 14 7 16 7 17 7 21 7 21 7 21 7 24 7 26 7 27 7 28 7 29 7 30 7 31 7 32 7 32 7 32 7 34 7 35 7 37 7 39 7 40 7 44 7 45 7 46 7 47 7 49 7 50 7 51 7 52
Original 02/99
Page 7 3
RAE2 Troubleshooting
PAMS Technical Documentation
Troubleshooting Diagram of the Memory Card interface . POST BEEP Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UI Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mechanical Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . Keyboard Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CMT LCD Module Troubleshooting . . . . . . . . . . . . . . . . . . . . . PDA LCD Display Troubleshooting . . . . . . . . . . . . . . . . . . . . . . CMT Backlighting Circuit Troubleshooting . . . . . . . . . . . . . . . . PDA LCD Backlighting Circuit Troubleshooting . . . . . . . . . . .
7 7 7 7 7 7 7 7 7
53 54 55 55 55 56 59 63 64
Page 7 4
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Introduction
This document is intend to be a guide for localizing and repairing electrical faults in RAE2 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 RAE2 product and module level architecture. You must also be familiar with RAE2 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 RAE2 device and you are starting troubleshooting it, check first the following basics. 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
BBS5, if ReLink mode is disabled).
Current consumption
CMT mode (CMT current) PDA mode (PDA current) Active (200380mA) Standby (3565mA) Suspended (24mA) Reset Off (< 1.0mA) 200380mA 3545mA 23mA <1.0mA Idle (340mA) 203420mA 3885mA 543mA 340mA Call (140320mA) 340mA700mA 175365mA 142323mA 140320mA
Note1: CMT peak current consumption might be 5x more than is specified above.
Finding faulty module
Then you define the faulty module. Normally this isn't difficult because the RAE2 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 RAE2. 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
RAE2 Troubleshooting
PAMS Technical Documentation
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 BBS5 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 RAE2 device. After this crosschecking you should have found certainty about the faulty module(s) and you can start to study module level problems.
Page 7 6
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
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:
PC for the Wintesla with software protection key (dongle) RS232 cable (DAU 9C) Repairing jig MJS4 Flashing Tools FLA7, FPS4 and TDF4 Service Battery BBS5 Calibration Unit JBE1 power supply, digital multimeter and oscilloscope
Original 02/99
Page 7 7
RAE2 Troubleshooting
PAMS Technical Documentation
CMT is totally dead 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.
Phone is totally dead
YES
J111 VBAT is 3.6 V
YES
NO
Failure in VBAT line Check X160,L103 Check shortcircuits
NO
J113 (PWRONx) 3.6 V
YES
Faulty circuit N110
J109 (VBB) 2.8 V N110 pin 25 (VXO) 2.8 V when PWR switch is pressed or watchdog disable pin is grounded
YES
NO
PWRONX level (J113) low when PWR switch is pressed or watchdog disable pin is (J100) grounded
YES
NO
Check V195, R195 Check UI module
See section: Power Doesn't Stay On
Faulty circuit N110
Figure 1.
Trouble Shooting Diagram for Phone is totally dead failure
Page 7 8
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
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)
YES
software is able to run check UI module If power is switched off after few seconds, check BSI and BTEM lines
NO
connect the shortcircuit wire from J113 to ground (watchdog)
OK
J109 (VBB) 2.8V J704 (VXO) 2.8V
YES
NO
VBAT is correct 3.6 V
YES
N110 is faulty
N110 is faulty
YES NO
check C213, R213
YES
J240 master reset (Purx) ="1" (2.8V)
YES NO
J241 sleep clock (SLCK) square wave 32 kHz
YES
NO
32 kHz in J100?
NO
J706 (RFC) 13 MHz 800 mV min
NO
J219: 13MHz sine wave clock signal: 500 mVpp min.
YES
Faulty circuit N110 or over loaded PURX line
check PDA 32kHz circuit and its connections to CMT
check buffer V702 and VCXO G690
Open pins or faulty circuit: D200, D210, D221, N110
Figure 2. Trouble Shooting Diagram for Power Doesn't Stay On or phone is jammed failures
Original 02/99
Page 7 9
RAE2 Troubleshooting
PAMS 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 selftests 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
MAD2 (DSPXF) J222
Page 7 10
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
1
init initialize dsp constants download patch code download
initialization done
MAD2 (DSPXF) J222
2
PSW search
last PSW OK
channel scan starts
synchronization OK
MAD2 (DSPXF) J222
3
send RACH RACH OK
go SDCCH imediate assigment OK
MAD2 (DSPXF) J222
Figure 3. The states of DSP after power on
Original 02/99
Page 7 11
RAE2 Troubleshooting
PAMS Technical Documentation
Phone doesn't register to the network or phone doesn't make a call
YES NO
Analog supply voltage VCOBBA is >2.7 V) at testpad J110
YES
Check VCOBBA line and N110 (CCONT)
Analog reference voltage Vref is 1.5 V at J107
YES
NO
Check R251
Supply voltage VCP (N110 pin 32) > 4.8 V Supply voltage VRX (N110 pin 9) > 2.7 V Supply voltage VSYN_1 (N110 pin 15) > 2.7 V Supply voltage VSYN_2 (N110 pin 4) > 2.7 V during the receiving slot Supply voltage VTX (N110 pins 11, 20) > 2.7 V during the transmitting slot
YES
NO
Fault in N110 (CCONT) or D200 (MAD2)
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
NO
Fault in N250 (COBBA)
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
NO
Fault in N250 if DC is failed Check RF part if benefit signal is failed
DAX signal (J254) pulses 1 > 0 during receiving slot
YES
Fault in N250 (COBBA) Fault in N250 if TxC is failed Check D200 if TxP is failed
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
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
NO
Fault in N250 (COBBA)
YES
Check RF part
Figure 4. The phone doesn't register or doesn't make a call
Page 7 12
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
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 "Insert 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)
YES
NO
faulty circuit N110 (CCONT)
NO
The ATR data can be seen at pin 43 (CCONT, N110)
YES
Check X302, R124, X150 and shorcircuit in V140, R141
Insert SIM card fault The ATR data can be seen at pin 44 (CCONT, N110)
YES NO NO
Fault in N110 (CCONT)
YES
SIMIOControl line (N110 pin 39) is "1"during the ATR message
YES
Fault in D200 (MAD2)
Voltage level < 1.5 V at pin 2 of D100 when BSI resistor is connected
YES
NO
Check R120, R122, X160
Check D200
VSIM, DATA, RESET and CLOCK lines rises up to 5 V after power on at pins of SIM card
NO
YES
Check SIM card and SIM reader connectors
VSIM(36), DATAO(43),SIMRSTO(42) and SIMCLKO(38) lines rises up to 5 V after power on at pins of N110 (CCONT)
NO
YES
Check X105, R124, R125, R128, V140, R141
SIMPWR(30), DATAA(44), SIMRSTA(40), SIMCLK(41) and SIMIOC(39) lines rises up to 2.8V after power on pins of N110
NO
YES
faulty circuit N110 (CCONT)
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
Original 02/99
Page 7 13
RAE2 Troubleshooting
PAMS Technical Documentation
Audio fault Troubleshooting tree for Audio fault:
Uplink (microphone) and downlink (earphone) are broken
YES
Voltage at resistor R260 is 2.8 V (without external audio devices) HOOKDET
YES
NO
Check R259, R260
Voltage at resistor R261 is 2.8 V (without external audio devices) HEADDET
YES
NO
Check R257, R256, R261
Frequency at J256 is 1 MHz, square wave 2.8 Vpp
YES
NO
Fault in N250 (Cobba)
Frequency at J257 is 8 kHz, square wave 2.8 Vpp
NO
Fault in N250 (Cobba)
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
NO
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)
DC voltage at capacitors C273 and C274 is 1.4 V during a call
YES
NO
Fault in N250 (Cobba)
Analog audio signal (few millivolts) at capacitors C273 and C274 during a call
YES NO
NO
Check C273, C274 and PCB routings
Digital PCM data at J255 during a call
Fault in N250 (Cobba)
Figure 6. Trouble Shooting Diagram for Audio Failure
Page 7 14
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Downlink (earphone) is broken
YES
Digital PCM data at J258 during a call
YES
NO
Fault in D200 (MAD2)
DC voltage at capacitors C252 and C256 is 1.4 V during a call
YES
NO
Fault in N250 (Cobba)
Analog audio signal (some ten millivolts) at C252 and C256 during a call
YES
NO
Fault in N250 (Cobba)
Check earpeace connections to PDA module and earpiece signal routing from CMT to PDA.
Figure 7. Trouble Shooting Diagram for Audio Failure
Original 02/99
Page 7 15
RAE2 Troubleshooting
PAMS Technical Documentation
Charging fault When you are charging totally empty battery, remember that startup charging might take 2 minutes with ACP9 charger and several minutes with ACP7 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
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
NO
Check X170, F170 L170 and R170
Check with WinTesla software if SW has detected charger and measured charger current and voltage properly.
YES
NO
Fault in N110 (CCONT)
Perform Energy Management Calibration with WinTesla software and JBE1 set and recheck charger detection. If still fails (CHAPS or CCONT) is broken.
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
NO
Check X160, R121, R122, D100, R123 and VSYS = 2.8V
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
NO
Check X160, R121, R122
Check with WinTesla software if SW is detected approved charger and measured charger current and voltage properly.
YES
NO
Perform Energy Management Calibration with WinTesla software and JBE1 set and recheck charger detection, charger voltage and current. OK?
YES
NO
Fault in N110 (CCONT)
32 Hz square wave frequency at pin 7 of CHAPS (N120)
YES
NO
Charging?
Fault in N110 (CCONT) or SW corrupted
Voltage levels at pins 5 and 12 of CHAPS (N120) are same as VB
YES
NO
Check R131, N120 (CHAPS)
Voltage levels at pins 5 and 12 of CHAPS (N120) rises when charger is connected
NO
Fault in N120 (CHAPS)
Figure 8. Trouble Shooting Diagram for Charging Failure
Page 7 16
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
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 information 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 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
RAE2 Troubleshooting
PAMS Technical Documentation
CCONT pin 54 J240
(PURX)
MAD pin N3 SRAM pin 20
(MCUAD0)
selftest passed
MAD pin B15 J203
(FlashRP)
Figure 9.
MAD selftest indication after power on (passed)
Page 7 18
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Flash programming doesn't work
YES
Note: When Relink OK, PDA display shows text "Relink enabled".
If the fault information from the prommer is: a) MCU doesn't boot b) serial data line failure c) serial clock line failure
Check ReLink
NOT OK
PDA fault
OK
connect the short circuit wire J113 (WDOG) to ground
OK
EEPROM (D240) pin 8 (VBB) 2.8 V J704 (VXO) 2.8 V
YES
NO
VBAT is correct 3.6 V
YES
N110 is faulty
NO
check C213, R213, V702 ...
YES
J240 master reset (PURX) = '1' (2.8 V)
YES
J100 sleep clock (clk32k) square wave 32 kHz
YES
NO
J706 (RFC) 13 MHz 800 mV min
NO
NO
J219: 13 MHz sine wave clock signal: 500 mVpp min.
YES
Faulty circuit N110 or overloaded PurX line
Check 32kHz clock line X173 pin 9 or C190 pin 14 pin 14 > J100
check VCXO G690
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 check also pullup and pulldown resistors: R216, R215, R201 and series resistors R240 GND : X170 pin 1 > GND
OK
Enable the selftest function of D200 by connecting shortcircuit between testpoints J229 and ground
Connect an oscilloscope to testpoint J203 and switch power on
NO
Voltage level rises to "1" after power on at testpoint J203
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 (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
RAE2 Troubleshooting
PAMS Technical Documentation
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
If the fault information from the prommer is: Algorithm file or alias ID don't find, ID is unknown etc.
YES
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 NO YES
Vpp > 4.5 V in C212
YES
Vpp > 4.5 V in C131
NO
Check regulator N201
Check components C212, R211
OK
Check C131, C132, V116, N110...
Faulty component D210
Figure 11. Trouble shooting Diagram for Flash programming doesn't work (via system connector X170)
Page 7 20
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
RF Fault
Here is a block diagram for repairing the RF section. First select the fault and follow the diagram. Required Servicing Equipment:
PC for the Wintesla Power supply Digital multimeter Oscilloscope Spectrum analyzer GSM MS test set Signal generator RF probe Phone test jig
Test Points on BS8 Module Test points are placed on baseband for service and production trouble shooting purposes in some supply voltage and signal lines. Because some of baseband signal are routed totally inner layers (due to uBGA packages) some testpoints are added for these signals.
Original 02/99
Page 7 21
RAE2 Troubleshooting
PAMS Technical Documentation
D220 D210
MCUGenIO15 MCUGenIO14 MCUGenIO12 MCUGenIO13 MCUGenIO10 MCUGenIO11 MCUGenIO8 ExtSysRSTX MCUAD19 MCUAD18
Flash Chip Select
Flash Write Protection McuGenIO1 DSPXF MCUGenIO09
N120
RFClk
D200
AccRxData McuGenIO4 AccTXData ROW5LCDCD SLCLK COBBADAX PCMRxData COBBACKL PCMDCLK PCMTxData COBBAAd0 PCMSLCK GENSCLK CCONTINT COBBADa0 ResetX
VB 32kHz V5V
TestMode
PURX
DSPGenOut1
GENSIO
PWRONx
VBB
RFIRdX RFIWrX MBUS VCORE
N110
VCXOPwr VCOBBA
D250
VREF
The figure above describes and the next table lists the test points.
Page 7 22
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Test Point J100 J103 J105 J106 J107 J108 J109 J110 J111 J112 J113 J203 J204 J206 J207 J208 J209 J211J218 J219 J220 J221 J222 J223J224 J225 J226 J229 J232 J233 J240 J241 J243 J250 J251 J252 J253 J254 J255 J256 J257 J258 32kHz
Name 32kHz clock from BS1 module CCONT interrupt output Serial data clock Serial data Reference voltage
Description
CCONTINT GENSCLK GENSIO VREF V5V VBB VCOBBA VB VCORE PWRONx ExtSysRSTX VCXOPwr AccRxData AccTxData MBUS McuGenio4 MCUGenIO(8:15) RFClk TestMode DSPGenOut1 DSPXF MCUAD(18:19) Flash Chip Sel Flash Write Prot ROW5LCDCD COBBAAd0 COBBADa0 PurX SLCLK McuGenio1 RFIRdX RFIWrX ResetX COBBACLK COBBADAX PCMTxData PCMDCLK PCMSCLK PCMRxData
Supply voltage for flash programming (Vpp) and RF circuits. Supply voltage for digital circuits Supply voltage for analog circuits Battery voltage Supply voltage for MAD c07 core CCONT's PWRONx / Watchdog disable signal Testpoint for fault diagnostic. If missing, check power supply, PurX line and 13 MHz clock signal. Control line for VCXO module. If low, 13 MHz clock signal for baseband is disable. FBUS RX FBUS TX Serial data bus max 9600b/s. Flash programming clock General purpose out in MAD Test point for fault diagnostic. MCUDA(15:8) 13 Mhz System clock MAD test mode select input General purpose DSP out Test point for fault diagnostic. Memory address signals Flash chip select pin Flash write protection pin Selftest pin. If shortcircuit is made between testpoint J229 and J230, the selftest will be executed.
Reset line from CCONT to MAD. If low, the BB circuits are in reset state. 32 kHz clock from CCONT to MAD General purpose input in MAD COBBA paraller interface read strobe COBBA paraller interface write strobe COBBA master reset COBBA 13Mhz clock COBBA paraller interface data available strobe COBBA PCM bus transmit data COBBA bus data transfer clock COBBA bus 8kHz frame sync COBBA PCM bus receive data
Original 02/99
Page 7 23
RAE2 Troubleshooting
PAMS Technical Documentation
Transmitter fault
Troubleshooting tree for Transmitter fault:
Ref1
ref2
ref3
ref4
ref5
Figure 12.
Transmitter fault TX level 5
Page 7 24
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
ref6
ref7
ref8
ref9
ref10
ref11
ref12
Figure 13. Transmitter 1 TX level 5
Original 02/99
Page 7 25
RAE2 Troubleshooting
PAMS Technical Documentation
Receiver fault
Troubleshooting tree for Receiver fault:
Page 7 26
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
AFC Fault
Troubleshooting tree for AFC fault:
Figure 14.
AFC
Original 02/99
Page 7 27
RAE2 Troubleshooting
PAMS Technical Documentation
1st IF
Troubleshooting tree for First IF fault:
ref19
ref20
ref21
ref22
ref23
N690
ref24
Figure 15.
1st IF 71MHz
Page 7 28
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
2nd IF
Troubleshooting tree for Second IF fault:
ref25
ref26
ref27
ref28
ref29 ref30
ref31
900X910
Figure 16.
2nd IF 13MHz
Original 02/99
Page 7 29
RAE2 Troubleshooting
PAMS Technical Documentation
UHF LO
Troubleshooting tree for UHF LO fault:
Figure 17.
UHF LO
Page 7 30
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
VHF LO
Troubleshooting tree for VHF LO fault:
2.5V
1.2V
1.8V
Figure 18.
VHF LO
Original 02/99
Page 7 31
RAE2 Troubleshooting
PAMS Technical Documentation
PDA Troubleshooting and Service
The purpose of this sectionis to provide methods to find the component that is malfunctioning in the PDA module of the RAE2. Due to the large integration scale of used components, it is always not possible to point the faulty component for sure. However the flow diagram introduced here is made to fulfill the aim as well as it is possible.
Required Servicing Equipment:
PC for the Wintesla Service battery BBS5 Service cable DAU9C Combox TDC4 IR transceiver module JLP1 digital multimeter oscilloscope frequency counter (optional)
Block Diagram
The block diagram of the BS1 PDA is described in the next figure:
Page 7 32
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
PDALCD
GND
BS2
Softkeys
CMT Keypad
CMT LCD
CMTLCD(5:0)
Flex connector FLASH 1Mx16
control (6:0) VBACK
X800 FLASH 1Mx16
C(3:0), R(1:0) C(7:0), R(9:0)
LCD PWR IF(6:0) VSYS D6:0 SA1:0 Charging LCD(10:0)
FLASH 1Mx16
BS1
PWRU
VBATT V28_3 VPDA
MA(11:0) D(15:0)
PWRKEY C4:0,R3:0
io(3:0)
QWERTY Keyboard Audio
Earpiece HF
HF_IF(1:0), EAR(1:0)
Backupbattery
Am486 CPU
X32kHz out MMC(3:0) SD(15:0) SA(21:0) JTAG(4:0) sio(1:0) X32kHz in
io(1:0)
RS_IF(2:0)
IR transceiver
DRAM 1Mx16
Test pads
FBUS_RXD FBUS_TXD FBUS_TXD2 MBUS
io(5:0)
FBUS_TXD FBUS_RXD
MBUS
io(3:0)
x32
System connector X810
GND
BoBo Connector
X830
VBATT
GND
Memory Card
BS8
CMT BS 1 PDA block in RAE2 product
Figure 19.
Original 02/99
Page 7 33
RAE2 Troubleshooting
PAMS Technical Documentation
BS1 PDA Components
The following components of the BS1 have an dramatic effect to the functionality of the module, a fault in any of these may cause the module to appear totally `dead':
PDA power unit CPU PLL clock generation circuit UCS Flash chip
If the device has some functionality, then the following components, along with the ones above, can be tested:
DRAM chip CS1 and CS0 Flash chips Handsfree speaker circuitry Earpice circuitry IR transceiver keyboard LCD module Memory Card interface Serial connections (FBUS and system bus)
Page 7 34
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
BS1 Troubleshooting
The highest level of the RAE2 PDA troubleshooting diagram is shown in the following figure. All the diagrams are made assuming that there is no visible faults, such as shortcircuits or loose pins, on the PDA. The module check begins with connecting the supply voltage to the PDA. If the current consumption differs a great deal from the normal limits, it is good to proceed to the PowerOn check. During BIOS detects some error during POST it tries to beep the buzzer for further fault analysis for the user. The POST beep codes, number of beeps are in the Appendix A on p.54. If the current consumption is OK, it can be tried if the wintesla service software is able to get connection to the PDA. If the target PDA does not respond to the pings from the host, it is good to check the PowerOn procedure. When the PDA responds to the wintesla, further peripheral tests may be carried out. The execution order is not significant and it may be freely changed. Along with the actual tests, wintesla offers advanced methods for isolating the possible cause of the fault. After all the functional tests are working, the device under test should be rebooted, and the normal usability of the GEOS, along with the CMT module should be checked before the PDA can be considered to be fully functional.
Original 02/99
Page 7 35
RAE2 Troubleshooting
PAMS Technical Documentation
PDA MODULE CHECK
Connect VBatt
Current consumption OK? YES Respond to wintesla? YES POSTcode check PLL clock circuits check DRAM check
NO
See Power On malfunctions
NO
See Power On malfunctions
Flash memories check LCD check Backlight check keyboard check Serial connections check IR check Lid Switch check Handsfree speaker check Earphone check Memory card interface check OS BOOT GEOS Usage Test OK
Figure 20. The highest level of the PDA troubleshooting diagrams
Page 7 36
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Poweron malfunction
The following picture illustrates the troubleshooting diagram for Power On malfunctions.
Start
POST BEEP Code error? YES CPU related error? YES Memory fault
NO
Vsys OK? E312 YES
NO
NO
Memory fault
INT_PLL OK? J400 (1.4MHZ) YES Bus activity? D/A, R/W, CS J440J449 YES
NO
Check PLLcircuit
NO
Reset OK ? J449
Check PDA power unit
Program flash NO Valid boot code in Flash YES Check External RS NO
5. Reboot and ping from the wintesla while in TestMode
Respond to PING from host? YES Power On OK!
Figure 21. Troubleshooting of the poweron malfunction
Original 02/99
Page 7 37
RAE2 Troubleshooting
PAMS Technical Documentation
Power Circuitry Check
The following figure illustrates how to check power circuits. The upper part of the flowchart must be passed before the swicthable voltages (lower part of the flowchart) can be considered to be alright. The LCD temperature compensation affects the LCD bias voltage values. Because of this temperature compensation, the LCD bias voltages are different in different temperatures, but anyway bias voltage maximum and minimum values should differ 4 Volts from the typical value (DAC 63) in every temperature. Figure on the next page.
Page 7 38
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Power check
Check CMT YES
VBATT OK? YES VPDA OK? YES VBACK OK? YES VSYS OK? YES RESET OK? YES
NO
Board to board connector OK?
NO
Change connector
NO
Check Input filter
NO
Power ASIC fault Check R461 R463 R469 R493 R495 YES NO N496 OK? NO Change N496
NO NO NO BATTDET YES OK?
Power ASIC fault YES VCOMP1 OK?
SELECT TROUBLE RELATED BRANCH (If you can not enable some voltage, try enable some other to be sure that CPU and bus from/to it is OK) Select Select I/O functions/ I/O functions/ Phaser calibration Phaser calibration in WinTesla in WinTesla Select max. V17OUT Select I/O functions/ Signal control in WinTesla Enable LCD Select I/O functions/ Signal control in WinTesla Enable IR Select I/O functions/ Signal control in WinTesla Enable MMC power
LCDTEMP OK? NO Hinge flex OK? YES NTC OK on UI? YES Power ASIC fault
V17OUT NO MAX voltage? YES Power ASIC Select DAC value 63 fault V17OUT NO typical vol tage? YES PDA LCD bias voltage OK Figure 22.
V28_1 OK? PDA LCD locig voltage OK
V28_2 OK?
YES
V28_3 OK? NO
YES Memory card power OK
IR NO transceiver logic voltage OK
Power ASIC fault
Power unit troubleshooting diagram
Original 02/99
Page 7 39
RAE2 Troubleshooting
PAMS Technical Documentation
Troubleshooting Diagram of the PLL clock generation circuit
The following diagram illustrates how to check PLL clock generation circuits.
PLL Circuit check
X32_CLK OK? J401 YES NO 1.4MHZ OK? J400 YES PLLs OK
NO
Vback OK? E307 YES XTAL OK? 32kHz J434, J435
NO
Check power ASIC N450
NO
Check XTAL
PLL intermediate voltage 1.2V? J430 YES check XIP flashes
NO
Discrete components on PLL OK? YES
NO
Change faulty discrete component
XIPs OK?
YES
CPU fault
Figure 23. PLL clock generation circuit check
Page 7 40
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Troubleshooting Diagram of the DRAM
The following figure illustrates how to check DRAM. Open DRAM test in WInTesla and select RandomTest. If test passed DRAM should be alright. If the test is not passed, run test again and measure the data and control lines activity.
DRAM check
Start the DRAM Random test
DRAM test succesful? YES
NO
Bus activity? (R/W, CAS, RAS, ADD) J446J449 J4555,J456 YES
NO
CPU fault
DRAM OK
DRAM or CPU fault
Figure 24.
DRAM troubleshooting diagram
Original 02/99
Page 7 41
RAE2 Troubleshooting
PAMS Technical Documentation
Troubleshooting Diagram of the Flash memories
The PDA comprises two kind of flash memories, two XIP (eXecute In Place) flashes and one RFD flash. The XIP flash can be checked by comparing image checksum and calculated checksum. If you can read and write from/to RFD flash, it is likely to be OK.
Page 7 42
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
XIP Flashes check
Read image checksum Compare calculated checksum and image checksum Are Checksums equal? YES XIP flashes OK NO CPU fault CPU fault Bus activity ? (AD, D, CE, WE) J441, J442 J453, J454
Flash fault NO Flash status output STSx(J451 or J452) OK? YES
NO
YES
RFD flash check
Write to RFD flash
Read from RFD flash
Flash fault NO
write and read OK? YES RFD flash OK
NO
Bus activity ? (AD, D, CE, OE, WE, WP) J440, J442J444 J453, J454
YES
Flash status output STSx (J450) OK? YES
NO CPU fault Figure 25.
CPU fault
Flash memories troubleshooting diagrams
Original 02/99
Page 7 43
RAE2 Troubleshooting
PAMS Technical Documentation
Troubleshooting Diagram of the LCD
The idea of the following diagram of the LCD Check is to make the difference whether the LCD BS2 module or the PDA BS1 is broken. The case where the fault is in the BS2 module is beyond the scope of this document. The fix in that case is likely the change of the whole module.
0. Start
1. LCD ON? YES
NO
1.1 Disconnect UI flex
1.2 V28_1 OK? N450/22 YES
NO
1.2.1 V28_OUT active? N450/61 NO
1.2.2 CPU fault
1.3 V17 OK? E300 5. Testpatterns OK? YES YES NO
NO
NO 1.3.1 V17_OUT active? N450/60 1.3.2 Check PDA PWRU 1.5.2 CPU fault NO
YES
LCD OK!
1.4 UI flex OK? NO 1.4.1 UI flex fault
1.5 LCD control signals OK? J805J808 YES 1.5.1 LCD module fault
Figure 26. Troubleshooting of LCD signals
Page 7 44
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Troubleshooting Diagram of the PDA LCD Backlight
This troubleshooting diagram describe troubleshooting procedure on the PDA LCD backlight. If PDA is OK, look then backlight troubleshooting procedure from next chapter UI TROUBLESHOOTING.
PDA LCD Backlight check Check hinge flex connector NO Backlight OK? YES Backlihgt OK NO Disconnect hinge flex Backlight enable signal (X800/24) OK? NO CPU fault YES VPDA OK? (X800/51) YES Check backlight connections on UI module
Enable backlight
Figure 27.
PDA LCD backlight troubleshooting
Original 02/99
Page 7 45
RAE2 Troubleshooting
PAMS Technical Documentation
Troubleshooting Diagram of the PDA Keyboard
This section describe PDA keyboard troubleshooting procedure. Possible cause to keyboard faults are keyboard interface in CPU, broken keymat or keydomes (UI) . Also, dirty keymat or keypad area can cause the fault.
Keyboard check
Start the keyboard test Press a QWERTY/ softkey
Keypress regognized? YES NO All keys pressed YES keyboard OK
NO
Other same row or column keys regognized? NO CPU fault
YES
Was pressed key a lidkey YES Check hinge flex and softkey domes on UI
NO
Keypad or keymat fault
Figure 28.
Keypad troubleshooting diagram
Page 7 46
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Troubleshooting Diagram of the serial connections
External bus connection is alright if the device is PINGing, if not is good to check system connector and discrete components on RX and TX lines. External bus use RS232 data protocol, but signal voltage levels on PDA and system connector are only 2.8V digital voltage levels. External buffer cable needed (DLR2) for connecting to PC. Serial connection between CMT and PDA (FBUS) can be checked as following flow chart described.
FBUS check
Open RS test and run COM2 local loop test Remove CMT and connect RX and TX together on board to board connector
Check CMT side YES
COM2 local loop test OK? NO CPU fault
YES
Run COM2 external loop test
COM2 external loop OK? NO Check board to board connector
Figure 29.
FBUS troubleshooting diagram
Original 02/99
Page 7 47
RAE2 Troubleshooting
PAMS Technical Documentation
External RS check
PiNG target? NO Test connections OK? NO Repair test connections
YES
External RS OK
YES
RX signal OK? (X810/8) NO X810 V870, V871, R806 OK? YES
YES
TX signal OK? (X810/9) NO X810 and V870 OK?
CPU fault
YES
Figure 30.
External serial connection troubleshooting diagram
Page 7 48
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Troubleshooting Diagram of the IR connection
This section describe infrared connection troubleshooting procedure. IR test need Combox TDC4 with IR transceiver JLP1. Place PDA so that IR transceiver have clear light route to JLP1 and run the IR test. If test not passed follow flowchart to find out the fault. IR shutdown is not in use.
Check power ASIC N450 IR check Repair test connections NO NO IR test OK? YES IrDA OK CPU fault CPU fault NO COM1 local loop test OK? YES IR transceiver fault NO NO NO External test connections YES Ok? V28_2 OK? (N300/6) YES NO VPDA OK? (N300/1) YES TXD OK? (N300/3) YES RXD OK? (N300/4) YES Figure 31. IR connections troubleshooting diagram YES R301, C301 OK? Check R300, R302R304 C300
Original 02/99
Page 7 49
RAE2 Troubleshooting
PAMS Technical Documentation
Troubleshooting Diagram of the lid switch
The idea of this diagram is to find out whether the CPU or the reed relay circuit is not working. If CPU and reed relay circuit on PDA is alright, then possible cause of fault is magnet in lid.
Lid switch check
Open WinTesla Signal control YES Place magnet near the reed relay Select Refresh in WinTesla
Lid switch OK
LID OPEN? NO
LID CLOSED? NO
LID_SWITCH_IF high? J310 NO R310 OK? NO Change R310
YES
CPU fault
YES
LID_SWITCH_IF low? J310 NO Reed relay fault
Figure 32.
Lid switch troubleshooting diagram
Page 7 50
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Troubleshooting Diagram of the HF Speaker
The idea of this diagram is to find out whether the CPU, loudspeaker, or power amplifier or it circuitry is not working.
Start
VAMP OK? R855/R856 YES Signal from COBBA OK? J881 YES
NO
Check R891, R892 and C880 C882, C892
NO Check COBBA on CMT
PAEnabled? N880/1 NO
YES
Signal amplified? N880/5,8 YES
NO
HFPAFault
V880 OK?
NO
Change V880
Speaker fault Check CMT CPU
Figure 33.
HFSpeaker troubleshooting diagram
Original 02/99
Page 7 51
RAE2 Troubleshooting
PAMS Technical Documentation
Troubleshooting Diagram of the Earpiece
The following diagram illustrates how to check earpiece connections on the PDA side. Run the wintesla buzzer test. If the sound is not good then check earpiece connections as following flowchart illustrates.
Earpiece connection check
Start buzzer test
Buzzer sound Ok? NO BZR_IF signal OK? J854 YES
YES
Buzzer OK
NO Check PDA CPU
VAMP OK? (R855/R856) NO
YES
V872 and V873 OK? NO Change faulty component
YES
Check Earphone
Check R891, R892 and C880 C882, C892 Figure 34.
Earphone troubleshooting diagram
Page 7 52
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Troubleshooting Diagram of the Memory Card interface
To check the memory card interface: S Take a good memory card and place it in the memory card connector. S Run Wintesla MMC test. If test failed then take memory card out and run test again. S Measure memory card system voltage and bus signals when test running. If the signal and the card voltage are OK, then the interface is likely to be OK. If everything is not alright check interface connections as the flowchart illustrate.
Memory Card interface check
Run MMC test
Test OK? NO MMC_DAT, MMC_CMD and MMC_CLK OK? YES MMC_SYS OK? NO Enable MMC power in WinTesla Board to NO board and memory card connectors OK? YES YES CPU fault Change faulty connector
NO
V28_3 OK? (X830/46) YES Check CMT side
NO
Check Power ASIC N450
Figure 35.
Memory card interface troubleshooting diagram
Original 02/99
Page 7 53
RAE2 Troubleshooting
PAMS Technical Documentation
POST BEEP Codes 1 3 4 5 6 10 13 14 15 16 18 Memory refresh is not working. Memory failure in 1st 64kB of memory. Timer T1 not operational. CPU test failed. Gate A20 failure. CMOS shutdown register failed. Exhaustive low memory test failed. Exhaustive extended memory test failed. CMOS restart byte can't hold data. Address line test failed. Interrupt controller failure.
Page 7 54
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
UI Troubleshooting
Mechanical Troubleshooting
In mechanical failures it is better to replace a whole unit or module than try to fix it in service. The replaceable units or modules on BS2 UI module are: BC2 CMT LCD module PDA LCD display UI PCB EL backlight panels Keydome sheets
Keyboard Troubleshooting
Equipment: Resistance meter (multimeter) If CMT keyboard does not function when the lid is closed, it is possible that reed relay (in the BS1 module) is damaged. If text "Please close cover" comes to CMT LCD when a CMT key is pressed when lid is closed, the reed relay is probably damaged. Check that the dome sheets are properly placed. Improperly placed dome sheet may cause malfunction of some key(s) or power down of the CMT when a key is pressed.
Table 1. CMT keyboard checklist.
Nonfunctioning CMT keys 6, 9, # 1, 2, 3, Soft_left 4, 5, Send, Up 7, 8, End, Down 0, *, Mode, Soft_right 3, 6, Send, End, Mode 9, Soft_left, Soft_right, Up, Down 1, 4, 7, #, * 2, 5, 8, 0
Check components R704, C707 R705, C706 R705, C714 R705, C713 R706, C712 R706, C708 R707, C709 R707, C710 R708, C711
Original 02/99
Page 7 55
RAE2 Troubleshooting
PAMS Technical Documentation
CMT LCD Module Troubleshooting
Start Display shows unexpected characters What is the problem? Pixel line(s) missing.
Display does not work
No
Is display properly on its place? Yes
LCD glass is probably mechanically damaged. Inspect and replace.
Yes
Is display properly on its place?
No
Remove and put the display back to its place and test again.
Yes
Can Vout voltage be measured from J715 when display is on its place.It must be 6...9 volts.
No
Remove and put the display back to its place and test again.
Check C705 and in BS2_10 R709.
Is VBB (J713) OK? Press some phone key. Are GENSCLK (J706), GENSDIO (J707) OK and is LCDRSTx (J708) 'high'? No Remove LCD and check the elastomer. Clean contact pads on PCB and try again. Yes No
Yes
Problem might be some randomize behavior or unclean contact pads of CMT LCD. Clean contacts and try again.
Problem might be elastomer or misaligned hinge flex. Remove and connect hinge flex again. Check elastomer.
Does display work OK? Yes
No
End
Figure 36. Flow chart for the troubleshooting of CMT LCD module.
Testing equipment: Multimeter and oscilloscope. Original 02/99
Page 7 56
PAMS Technical Documentation
RAE2 Troubleshooting
Figure 37. GENSCLK (J706) and LCDCSx (pin 5/H700) , LCD active after pressing a key.
Figure 38. GENSCLK (J706) and LCDCSx (pin 5/H700), LCD inactive, serial bus used for communication between MAD and CCONT.
Original 02/99
Page 7 57
RAE2 Troubleshooting
PAMS Technical Documentation
Figure 39. GENSDIO (J707)
Page 7 58
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
PDA LCD Display Troubleshooting
START
Display does not work What is wrong? Large part of the display is black or dark blue or pixel line(s) is missing LCD is mechanically damaged. Replace the display.
Bad picture quality
Yes
Make sure that the flex of the display is properly connected to X730. Does the display work now? No
Yes
Check C740C744 and in BS2_10 R736R739. Does the display work now? No
No
Check C740C744 and in BS2_10 R736R739. Does the display work now? Yes
Make sure that the flex of the display is properly connected to X730. Does the display work now? No Yes
Are V28_1 (J700) and LCD_ON (J701) about 2.8V? Yes
No
Is V17_OUT (J709) as specified? No Yes Reason may be misaligned hinge flex. Remove and connect flex again and test display again. Does the display work OK now? Yes
No
Are FRM (J702), M (J703), LC (J704) and SCK (J705) as specified? Yes
No
Display is probably damaged. Replace it with a new display.
END
Figure 40. Flowchart for troubleshooting of the PDA LCD.
Testing equipment: Multimeter and oscilloscope.
Original 02/99
Page 7 59
RAE2 Troubleshooting
PAMS Technical Documentation
Figure 41. LCDD0 (J712)
Figure 42. LC (J704)
Page 7 60
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
Figure 43. M (J703)
Figure 44. SCK (J705)
Original 02/99
Page 7 61
RAE2 Troubleshooting
PAMS Technical Documentation
Figure 45. FRM (J702)
Page 7 62
Original 02/99
PAMS Technical Documentation
RAE2 Troubleshooting
CMT Backlighting Circuit Troubleshooting
When troubleshooting the CMT backlighting circuit, remember that backlighting goes off after a certain period from the last key pressing.
START
Yes
Check that EL panel contacts are OK. Does the backlight work now? No
Yes
Is VPDA voltage OK on UI board (J714)?
No
Is the voltage of pin 1/N700 higher than 3.0 V?
No
Is CMT_BL_ON signal voltage at J710 about 2.8V? Yes
No
Yes Is driver circuit's out put as specified (6,7/N700)? No Are coil L700, diode V701, capacitors C701C703 and resistors R700R702 (R703 in BS2_10) OK? No Yes Inverter is damaged. Replace with new circuit. Replace faulty com ponents. Does the backlight work now? No Yes Yes Try with a new EL panel. Does the backlight work now? Yes V702 or V703 is damaged. Replace them. No Reason may be misaligned hinge flex. Remove and connect flex again and test display again. Does the backlight work OK now? No Yes
END
Figure 46. Flowchart for troubleshooting of the CMT backlighting circuit.
Original 02/99
Page 7 63
RAE2 Troubleshooting
PAMS Technical Documentation
PDA LCD Backlighting Circuit Troubleshooting
For PDA backlighting troubleshooting you can use test mode and WinTesla SW to set the backlighting on all the time.
START
Yes
Check that EL panel contacts are OK. Does the backlight work now? No
Yes
Is VPDA voltage OK on UI board (J714)?
No
Is the voltage of pin 1/N730 higher than 3.0 V?
No
Is PDA_BL_ON signal voltage at J711 about 2.8V? Yes
No
Yes Is driver circuit's out put as specified (6,7/N730)? No Are coil L730, diode V730, capacitors C736C738 and resistors R730R732 (R733 in BS2_10) OK? No Yes Inverter is damaged. Replace with new circuit. Replace faulty com ponents. Does the backlight work now? No Yes Yes Try with a new EL panel. Does the backlight work now? Yes V731 or V732 is damaged. Replace them. No Reason may be misaligned hinge flex. Remove and connect flex again and test display again. Does the backlight work OK now? No Yes
END
Figure 47. Flowchart for troubleshooting of the PDA backlighting circuit.
Testing equipment: Multimeter and oscilloscope. Note that voltage rating of the oscilloscope and probe must be over 250 V peaktopeak. Original 02/99
Page 7 64
PAMS Technical Documentation
RAE2 Troubleshooting
Figure 48. Example of a typical EL driver output waveform, measured between pins 6 and 7 of the driver.
Original 02/99
Page 7 65
RAE2 Troubleshooting
PAMS Technical Documentation
Page 7 66
Original 02/99