Text preview for : 08_Troub.pdf part of Nokia 9210 Service Manual Cellular Phone/Personal Digital Assistant - (9,32Mb) Part 1/5 - File 14



Back to : RAE-3_cellular_®_.part1.r | Home

PAMS Technical Documentation RAE-3 Series PDA

8. Troubleshooting

Issue 1 06/01

Copyright E 2001. Nokia Mobile Phones. All Rights Reserved.

RAE-3 8. Troubleshooting

PAMS Technical Documentation

AMENDMENT RECORD SHEET
Amendment Number Date Inserted By OJuntunen Comments

06/01

Page 8 ­ 2

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

CONTENTS ­Troubleshooting Page No
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RAE­3 System HW / UI Troubleshooting . . . . . . . . . . . . . . . . Tools needed for troubleshooting: . . . . . . . . . . . . . . . . . . . . General guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System HW / UI Troubleshooting Cases . . . . . . . . . . . . . . . . . . . Nominal Current Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 System HW / UI Troubleshooting Cases . . . . . . . . . . . . . . . . . . 1.1 Dead Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Keypad problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 BL8 System HW related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Flash programming troubleshooting . . . . . . . . . . . . . . . . . 2.1.1 Flashing does not start . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.2 Flash memory fault indicated . . . . . . . . . . . . . . . . . . . 2.1.3 Flash VPP Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.4 Flash Erasing /Programming Error . . . . . . . . . . . . . . . 2.2 General Power Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.3 Device does not stay ON . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4 Charging checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5 Backup Battery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.1 Backup battery troubleshooting . . . . . . . . . . . . . . . . . 2.6 Accessory Power Output Troubleshooting . . . . . . . . . . . . 2.6.1 No Accessory Voltage when needed . . . . . . . . . . . . . 2.6.2 Accessory Voltage ON all the time . . . . . . . . . . . . . . . 2.7 Clocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.1 Clocks Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . 2.8 Memory Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8.1 Test in boot up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8.2 Test in PTS/WinTesla flashing . . . . . . . . . . . . . . . . . . . 2.9 Memory Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9.1 Memory fails In Boot Up tests . . . . . . . . . . . . . . . . . . . 2.9.2 CMT display backlight blinking 2 times in a loop . . . 2.9.3 CMT display backlight blinking 3 times in a loop . . . 2.9.4 CMT display backlight blinking 4 times in a loop . . . 2.9.5 Memory fails in PTS/WinTesla flashing . . . . . . . . . . . 2.9.6 Serial Flash id read test fails . . . . . . . . . . . . . . . . . . . . 2.10 Serial Interface Troubleshooting . . . . . . . . . . . . . . . . . . . . 2.11 CONTACT SERVICE in CMT display . . . . . . . . . . . . . . . 2.12 CCONT Serial interface Troubleshooting . . . . . . . . . . . . 2.13 SIM Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.13.1 SIM Card Error Troubleshooting . . . . . . . . . . . . . . . 2.13.2 SIM Card Rejected . . . . . . . . . . . . . . . . . . . . . . . . . . . 8­6 8­6 8­6 8­6 8­8 8­9 8 ­ 10 8 ­ 10 8 ­ 11 8 ­ 13 8 ­ 13 8 ­ 13 8 ­ 14 8 ­ 15 8 ­ 16 8 ­ 17 8 ­ 19 8 ­ 20 8 ­ 22 8 ­ 22 8 ­ 24 8 ­ 25 8 ­ 26 8 ­ 27 8 ­ 27 8 ­ 29 8 ­ 29 8 ­ 30 8 ­ 31 8 ­ 31 8 ­ 32 8 ­ 33 8 ­ 36 8 ­ 38 8 ­ 40 8 ­ 41 8 ­ 44 8 ­ 46 8 ­ 48 8 ­ 48 8 ­ 49

Issue 1 06/01

Page 8 ­ 3

RAE-3 8. Troubleshooting

PAMS Technical Documentation 8 ­ 51 8 ­ 53 8 ­ 53 8 ­ 55 8 ­ 56 8 ­ 56 8 ­ 58 8 ­ 60 8 ­ 62 8 ­ 65 8 ­ 65 8 ­ 67 8 ­ 68 8 ­ 69 8 ­ 71 8 ­ 73 8 ­ 73 8 ­ 74 8 ­ 75 8 ­ 79 8 ­ 84 8 ­ 86 8 ­ 86 8 ­ 86 8 ­ 87 8 ­ 100 8 ­ 105 8 ­ 106 8 ­ 106 8 ­ 107 8 ­ 108 8 ­ 108 8 ­ 109 8 ­ 109 8 ­ 110 8 ­ 111 8 ­ 111 8 ­ 112 8 ­ 113 8 ­ 113 8 ­ 113 8 ­ 114 8 ­ 115 8 ­ 115 8 ­ 117 Issue 1 06/01

2.13.3 Insert SIM card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.14 Memory Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.14.1 Memory Card Interface Troubleshooting . . . . . . . . 2.14.2 Memory card switch troubleshooting: . . . . . . . . . . . 2.15 Lid Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.15.1 Lid Switch Troubleshooting . . . . . . . . . . . . . . . . . . . . 2.16 Battery Removal Switch troubleshooting . . . . . . . . . . . . 2.17 COBBA Control Interface troubleshooting . . . . . . . . . . . 2.18 COBBA PCM Interface Troubleshooting . . . . . . . . . . . . . 2.19 Audio troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.19.1 Both Mic and Earpiece/PHF faulty . . . . . . . . . . . . . . 2.19.2 Mic faulty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.19.3 Earpiece faulty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.19.4 PHF Speaker faulty . . . . . . . . . . . . . . . . . . . . . . . . . . 2.19.5 Headset out of order . . . . . . . . . . . . . . . . . . . . . . . . . . 2.20 RF Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.20.1 Phone doesn't register to the network l . . . . . . . . . . 2.21 IR Interface Troubleshooting diagram . . . . . . . . . . . . . . . 2.22 BL8 related Keyboard problems . . . . . . . . . . . . . . . . . . . . 2.23 BL8 related PDA UI problems . . . . . . . . . . . . . . . . . . . . . . 2.24 BL8 related CMT UI problems . . . . . . . . . . . . . . . . . . . . . 3 DL2 UI Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 CMT and keypad illumination problems . . . . . . . . . . . . . . 3.2 CMT LCD Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 No picture on PDA LCD or picture is faulty . . . . . . . . . . . . 3.4 Backlight troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5 DL2 related keyboard problems . . . . . . . . . . . . . . . . . . . . . 4 UL 8 FLEX related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Audio troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Display problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Battery Removal Switch problem . . . . . . . . . . . . . . . . . . . . 4.4 UL8 related keyboard problems . . . . . . . . . . . . . . . . . . . . . 5 RF related . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introduction to troubleshooting . . . . . . . . . . . . . . . . . . . . . . . RF Key Component Placement . . . . . . . . . . . . . . . . . . . . . . 5.1 EGSM Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Instructions for troubleshooting . . . . . . . . . . . . . . . 5.1.1 Troubleshooting diagram for EGSM Receiver . . . . . 5.1.2 EGSM Signal Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.3 RX/TX Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.4 Front end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1.5 Hagar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 PCN Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Instructions for troubleshooting . . . . . . . . . . . . . . . 5.2.1 PCN Signal Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Page 8 ­ 4

PAMS Technical Documentation 5.2.2 RX/TX Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.3 Front end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.4 Hagar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 EGSM Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General troubleshooting instructions . . . . . . . . . . . . . . . . . . 5.3.1 Path of transmitted EGSM signal . . . . . . . . . . . . . . . . 5.3.2 Troubleshooting diagram for EGSM Transmitter . . . 5.4 PCN Transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General troubleshooting instructions . . . . . . . . . . . . . . . . . . 5.4.1 Path of the transmitted PCN signal . . . . . . . . . . . . . . 5.4.2 Troubleshooting diagram for PCN Transmitter . . . . . 5.5 Synthesizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General troubleshooting instructions . . . . . . . . . . . . . . . . . . 5.5.1 26 MHz reference oscillator ( VCTCXO ) . . . . . . . . . 5.5.2 VCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.3 Troubleshooting diagram for PLL Synthesizer . . . . . 5.5.4 PLL Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6 Frequency lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Diagrams of Test Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

RAE-3 8. Troubleshooting 8 ­ 117 8 ­ 117 8 ­ 117 8 ­ 119 8 ­ 119 8 ­ 119 8 ­ 120 8 ­ 122 8 ­ 122 8 ­ 122 8 ­ 123 8 ­ 125 8 ­ 125 8 ­ 125 8 ­ 125 8 ­ 126 8 ­ 128 8 ­ 129 8 ­ 143

Issue 1 06/01

Page 8 ­ 5

RAE-3 8. Troubleshooting

PAMS Technical Documentation

Introduction
This document is intend to be a guide for localizing and repairing electrical faults in the RAE­3 device. First there is a brief guide for fault localizing. Then fault repairing is divided into troubleshooting paths. Before any service operation you must be familiar with the RAE-3 product and module level architecture. You must also be familiar with the RAE-3 specified service tools such as the WinTesla service software, Flashing tools and software. Basic skills of using RF measurement devices are required when starting to follow the RF troubleshooting paths.

RAE­3 System HW / UI Troubleshooting
Tools needed for troubleshooting:
S S S S Service tools defined in RAE­3 manual "Service Tools" section Laboratory power supply with current indicator Oscilloscope Digital multimeter . .

General guidelines
General notes about the RAE­3 product: S RAE­3 has only one common engine ­ BL8 system HW, . . . . . comprising CMT (phone) and PDA (computer) S There are separate CMT and PDA displays and keyboards ....

S CMT display/keyboard and PDA display are on the UI module . . . . . DL2 S PDA QWERTY­keyboard UI is on UL8 flex module S Audio connections for the handsfree speaker and earpiece are . . . . . on the UL8 flex module When you have a faulty RAE-3 device and you start to troubleshoot it, check first the following items: S If the RAE-3 cannot be turned on by any means, see "dead . . . . . . . device" troubleshooting S Blinking CMT display means that a memory fault is preventing . . . . . normal boot up (­> Memory tests) S Current consumption (missing consumption) gives an idea . . . . . . . . whether the device able to start up S Dropping supply voltage indicates a short circuit S Check whether the connection with Wintesla works and what can . . . . . be discovered with Wintesla S Check self tests with Wintesla if "CONTACT SERVICE" is shown . . . . . on the CMT display Issue 1 06/01

Page 8 ­ 6

PAMS Technical Documentation S S Check visual display faults Check that all connectors make good contacts

RAE-3 8. Troubleshooting

­ this might be the problem if the displays are dark or partially dark or if there are keyboard problems. Locate failed module (BL8, UL8, DL2) with the MJS­14 test jig. This is the basis of further troubleshooting. S Check the failed module(s) visually: ­ mechanical damages? ­ solder joints OK? Continue with the specific troubleshooting procedure for the module: S S If there is an obvious fault, repair it before reflashing the device Flash first if a fault is not obvious ­ Flashing troubleshooting leads to power checking and serial interface checking if flashing does not start. ­ At the beginning of flash programming, all memory interfaces are first tested ­ If flashing is aborted and error(s) return, refer to Memory testing section. Due to CSP packages short­circuits or broken solder joints are not easily seen. If the examined signal seems to be continuously in low or high level, then measure for possible short­circuit to ground (signal low) or to supply voltage (signal high). Note that if a problem is not found from any visible contact/component it can be under the CSPs where the signal is connected. If there is no short circuit and the signal level is continuously at a low level, then the following faults are possible: ­ contact problem in output soldering (output active) ­ contact problem in soldering of pin having internal pull­up (tri­stated signals) Care must be taken when assembling and disassembling the transceiver. Refer to the instructions in this manual. Failure to do this may result in unnecessary damage to the device. The PDA display must be calibrated after the following actions have been taken: ­ RAE­3 has been flashed ­ PDA display or DL2 module has been replaced

Note: The last step in service before returning the RAE-3 to the customer is to set the RTC running time to 10 hours.
­ Service battery BBL-3B does that automatically. ­ Always use only the BBL-3B service battery with Wintesla.

Issue 1 06/01

Page 8 ­ 7

RAE-3 8. Troubleshooting

PAMS Technical Documentation

System HW / UI Troubleshooting Cases
1. Troubleshooting of System HW/UI is divided to following cases: . . . . . . . . 1.1 . . . . . . . . 1.2 . . . . . . . . 2.1 . . . . . . . . 2.2 . . . . . . . . 2.3 . . . . . . . . 2.4 . . . . . . . . 2.5 . . . . . . . . 2.6 . . . . . . . . 2.7 . . . . . . . . 2.8 . . . . . . . . 2.9 . . . . . . . . 2.10 . . . . . . . . 2.11 . . . . . . . . 2.12 . . . . . . . . 2.13 . . . . . . . . 2.14 . . . . . . . . 2.15 . . . . . . . . 2.16 . . . . . . . . 2.17 . . . . . . . . 2.18 . . . . . . . . 2.19 . . . . . . . . 2.20 . . . . . . . . 2.21 . . . . . . . . 2.22 . . . . . . . . 2.23 . . . . . . . . 2.24 3. DL2 UI Related: . . . . . . . . 3.1 . . . . . . . . 3.2 . . . . . . . . 3.3 . . . . . . . . 3.4 . . . . . . . . 3.5 CMT and keypad illumination problems CMT LCD Troubleshooting No picture on PDA LCD or picture is faulty Backlight troubleshooting DL2 related keyboard problems Issue 1 06/01 Dead Device Keypad problem Flash programming troubleshooting General Power Checking Device does not stay ON Charging checking Backup Battery Accessory Power Output Troubleshooting Clocks Memory Tests Memory Troubleshooting Serial Interface Troubleshooting CONTACT SERVICE in CMT display CCONT Serial interface Troubleshooting SIM Card Memory Card Lid Switch Battery Removal Switch troubleshooting COBBA Control Interface troubleshooting COBBA PCM Interface Troubleshooting Audio troubleshooting RF Interface IR Interface Troubleshooting diagram BL8 related Keyboard problems BL8 related PDA UI problems BL8 related CMT UI problems

2. BL8 System HW related:

Page 8 ­ 8

PAMS Technical Documentation 4. UL8 Flex Related: . . . . . . . . 4.1 . . . . . . . . 4.2 . . . . . . . . 4.3 . . . . . . . . 4.4 Audio troubleshooting Display problem Battery Removal Switch problem UL8 related keyboard problems

RAE-3 8. Troubleshooting

Nominal Current Consumption
The following power consumption values (ref.Table 1 ) are measured from a complete RAE-3. Vbattery = 3.7 V. Measured nominal currents are drawn from the main battery. Measurements have been made with a current proble connected to an oscilloscope.
Table 1. Nominal current consumption in different operating modes State Lid closed CMT OFF 2.4 mA CMT ON 5.6 mA 65 mA (running) 2W Call (TX5) 310 mA (Voice call) 365 mA (HF call) 445 mA (HF call) 0.2W Call (TX19) 120 mA (Voice call) 170 mA (HF call) 255 mA (HF call)

Lid Open 60 mA (running) (min. brightness on PDA display) Lid Open (max. brightness on PDA display) 140 mA (running)

145 mA (running)

Identify the failed module (UL8, DL2, BL8) using the MJS­19 jig.

Issue 1 06/01

Page 8 ­ 9

RAE-3 8. Troubleshooting

PAMS Technical Documentation

1
1.1

System HW / UI Troubleshooting Cases
Dead Device
Dark display

Check supply voltage

NO

Supply voltage drops ?

YES

Go to General Power Checking (short circuit possible)

Check serial connection with WinTesla

Go to Flashing troubleshooting/ general power check

NO

OK?

YES

Check connectors BL8/UL8, UL8/DL2, DL2/displays

Replace defective connector

NO

Connectors OK ?

YES

Identify failed module (BL8, UL8, DL2) with MJS-14 jig Go to UI related troubleshooting of failed module: ­ BL8 related CMT UI troubleshooting (BL8 failed) ­ BL8 related PDA UI troubleshooting (BL8 failed) ­ CMT LCD troubleshooting (DL2 failed) ­ No picture/faultly picture on PDA LCD (DL2 failed) ­ PDA backlight troubleshooting (DL2 failed) ­ UL8 keyboard module troubleshooting (UL8 failed) Figure 1.

Page 8 ­ 10

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

1.2

Keypad problems
1. 2. Connect the phone under test to Wintesla. Select Testing ­> User interface testing

3. Select the CMT to be tested from the "Display" panel and click "Start key test" (figure 1). The test starts and the button text changes to "Stop key test". 4. Click the "Stop key test". Result window (Figure 2) appears. . . . . . . . . All letters under the key names should show "A". . . . . . . . . If there is "R", the key is stuck. Repeat the test. If the result is the same, use table 1 to find out the signals connected to the particular key(s). 5. Click "Start key test" again. . . . . . . . . This time, press and release all keys through, then stop the test. . . . . . . . . There should be "P" for every key. . . . . . . . . If "A" results are seen, repeat and press these keys again. If key presses are not registered, find out the signals connected to the key. 6. Change the keypad to be tested to PDA. Repeat test steps 4 and 5 for the PDA keyboard. The result window is shown in Figure 3. 7. Open the CMT side cover. Check the 50­way connector on UL2. . . . . . . . . Is it properly inserted, both parts of the connector properly soldered? Repair, retest 8. Check CMT key mat alignment and membrane switches on the mat. Replace key mat if broken. 9. Check 70­way connector on BL8. . . . . . . . . Is it properly inserted, both parts of the connector properly soldered? Repair, retest 10. Locate the faulty part by placing the parts into service jig and changing the parts one by one. Follow instructions in the proper section (2.23 for BL8 fault, 4.4 for UL8 flex fault, 3.5 for UL2 display module fault).
Table 1. Keyboard matrix (keys on UL2 module highlighted) ­ English keymat Col0 Col1 Col2 Col3 Col4 Col5 Col6 Col7 Col8 Col9 pda pda cmt cmt cmt Space Info < /> Soft 3 Soft 1 Soft1 Up Soft2 pda pda cmt cmt cmt Z Shift C B Soft 4 Soft 2 Send Down End cmt 1 cmt 2 cmt 3 cmt cmt Chr N M ,@ Profile Power cmt 4 cmt 5 cmt 6 cmt * cmt # Menu Up Right Down Left cmt 7 cmt 8 cmt 9 cmt 0 :; +­ BackEnter space ESC App1 App2 App3 app4 App6 App7 App8 Ctrl V X 6 App5 1 2 3 4 5 7 8 9 0 P Tab Q W E R T Y U I O Caps A S D F G H J K L

Row0 Row1 Row2 Row3 Row4 Row5 Row6 Row7 Row8 Row9

Issue 1 06/01

Page 8 ­ 11

RAE-3 8. Troubleshooting

PAMS Technical Documentation

Figure 2. User interface test dialog

Figure 3. CMT keypad test results

Figure 4. PDA keypad test results

Page 8 ­ 12

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2
2.1
2.1.1

BL8 System HW related
Flash programming troubleshooting
Flashing does not start
FLASH programming does not work
YES If the fault information from the prommer is: a) The Phone does not set Flashbus TXD line high after the startup b) The Phone does not set Flashbus TXD line low after the line has been high. The Prommer generates this error also when the Phone is not connected to the Prommer. c) The Phone MCU has not received the first dummy word correctly from the Prommer after the startup d) The Phone has not received Secondary code bytes correctly e) The Phone MCU can not start Secondary code correctly OK Check that Flashing equipment are functional and properly connected YES
a) C138 VBB 2.8 V, b) J304 (PURX) = '1' (= 2.8V) c) J303 (SLEEPCLK) 32 kHz square wave d) C303 13 MHz sine wave Note: testpoints are explained more detailed in General Power Checking ­ section

NO Jump to General Power Checking Powers OK Jump to Clocks Troubleshooting

YES

Check that following lines are correct:

NO

a) AccTxData line b) AccRxData line c) MBUS Note: testpoints are explained more detailed in Serial Interface troubleshooting ­ section

Jump to Serial Interface troubleshooting

Figure 5.

Issue 1 06/01

Page 8 ­ 13

RAE-3 8. Troubleshooting
YES

PAMS Technical Documentation

2.1.2

Flash memory fault indicated

YES

FLASH programming does not work
YES If the fault information from the prommer is: a) The flash manufacturer and the device IDs in the existing Algorithm files do not match with the IDs received from the phone. b) The External RAM test failed in the Phone. c) The Phone does not send acknowledge signal (ie. drop the Flashbus TXD line to low state) after the Prommer has sent the Algorithm code. d) The Prommer has detected a wrong ID byte in the MCU_ID_RESPONSE message, which it has received from the Phone. See Note.

YES Jump to Memory Tests

Figure 6.

Note: Wintesla shows the following Flash ID's for every flash device when programming is going on. If Flash ID bytes are correct the following bytes are shown: Flash ID 0089­8896, 0089­8896, 0089­8896, 0000­0030
=Flash 0 =Flash 1 =Flash 2 = SF

But if one or more of Flash ID bytes is/are wrong the Flash is faulty or there is short circuit in the flash interface.

Page 8 ­ 14

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.1.3

Flash VPP Error
FLASH programming does not work YES
If the fault information from the prommer is:
a) The erasing status response from the Phone informs about fail. The Prommer copies the Phone response contents to the preceeding FIASCO_GENERAL_INFO_IND message. b) The Prommer measures the PPD voltage level at flashing start. If the level is below the limit the Prommer returns the corresponding error code.* c) The programming status response from the Phone informs about fail. The Prommer copies the phone response contents to the preceding FIASCO_GENERAL_ INFO_IND message Note: A new error message will be shown with next coming Wintesla RAE­3 dll release

YES

* The VPP voltage level limit is 3 to 5 per cent below the set VPP voltage level.

Check that UL8 flex connector is properly connected to Board to board connector on BL8 (=X400) ; (pins 15 (FLVPP) and 16 (PROG_EN) are connected in UL8 flex)

OK
Check FLVPP voltage level (= 2.8 V) during programming. (See Memory tests measurement points C368) Note: By default tested with known good UL8 flex

NO

OK

Check voltage from Board to board adapter JC4 connector pin 16 (= 2.8 V) Note: By default tested with known good UL8 flex.

NOT OK NOT OK
Check that UL8 Flex connector (=X12) is not broken and flex is OK. Note: By default tested with known BL8 module.

Check BL8's connector X400

OK
Faulty MADLinda D300 (DSPGenOut2)

Faulty UL8 Flex

OK

Wintesla informs which memory address the erasing fails. See note which address corresponds which Flash components.

Erasing/programming fails
Faulty components D351, D352 or D353
Note: Flash 0 (=D351) erasing area starts 0x00000000 Flash 0 (=D351) erasing area stops 0x003FFFFF Flash 1 (=D352) erasing area starts 0x01000000 Flash 1 (=D352) erasing area stops 0x013FFFFF

Note: Flash 2 (=D353) erasing area starts 0x02000000 Flash 2 (=D353) erasing area stops 0x023FFFFF Serial Flash (=D354) erasing area starts 0x8000000 Serial Flash (=D354) erasing area stops 0x841FFFF

Figure 7.

Issue 1 06/01

Page 8 ­ 15

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.1.4

Flash Erasing /Programming Error

FLASH programming does not work

YES

If the fault information from the prommer is: a) The erasing status response from the Phone informs about failure. The Prommer copeies the contents of the response of the Phone into the preceeding FIASCO_GENERAL_INFO_IND message. b) The Phone has generated a NAK signal during data block transfer. c) The programming status response from the Phone informs about failure. The Prommer copies the contents of the response of the Phone into the preceeding FIASCO_GENERAL_INFO_IND message.

YES
Wintesla informs which memory address the erasing fails. See note which address corresponds which Flash components.

Erasing/Programming fails
Change faulty flash D351, D352, D353 or D354

Note: Flash 0 (=D351) erasing area starts 0x00000000 Flash 0 (=D351) erasing area stops 0x003FFFFF Flash 1 (=D352) erasing area starts 0x01000000 Flash 1 (=D352) erasing area stops 0x013FFFFF Flash 2 (=D353) erasing area starts 0x02000000 Flash 2 (=D353) erasing area stops 0x023FFFFF Serial Flash (=D3534 erasing area starts 0x8000000 Serial Flash (=D3534 erasing area stops 0x841FFFF

Figure 8.

Page 8 ­ 16

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.2

General Power Checking
Use BBL-3B service battery. Battery voltage must be 3.7 V.

Switch power on Short circuit in VBAT, VBB or VCORE line. Switch power off and measure with multimeter which of these voltages have a short circuit. Check visually components which are connected to short circuited voltage line.

Supply voltage drops when the power is switched on
NO

YES

VB (C124) and VB_CCONT (C115) 3.7V?
YES

NO

Failure in battery line Check L100, L101 and X100

PURX (J304) 2.8V & SLEEPCLK (J303) 32kHz (typ. 32.768kHz)?

NO

Remove & Insert service battery

Drain of V106 low around 60­100ms when battery inserted (FIg. 10)
YES

NO

Faulty circuit D101, D102, V106, R102, R108 or V102 N100

YES

Faulty circuit N100 or faulty 32kHz clock circuit (B100, C120, C121, C122, R113, R114 or R115)
NO

VBB (C138) 2.8V?

V2V (C140) 2.65V?
NO

YES

Pin 5 of N102 0V?
NO

YES

Faulty circuit N102, C138 or C111

YES

Faulty circuit N100, C140 or R104

Faulty circuit V108 or R105

VCORE (C119) 1.8V?

NO

Faulty circuit L102, C131, V105, R118, L103, V104, R116, R119, C118, C119
Figure 9.

Oscilloscope screen shot (Figure 10) .

Issue 1 06/01

Page 8 ­ 17

RAE-3 8. Troubleshooting

PAMS Technical Documentation

Figure 10.

Drain of V106 when battery is inserted

Page 8 ­ 18

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.3

Device does not stay ON
If the device is switched off without any visible reason, there may be problems in the following areas: S S S S CCONT watch dog problem BSI or BTEMP line problem Battery line problem Soldering problem

The most likely reason is CCONT WD (watchdog) problem, which turns the device off after about 32 s. This may be caused by SW problem, MadLinda problem, CCONT problem or memory problems. The following tests are recommended: S S S S General Power Checking Clocks Memory testing CCONT serial interface

If there is something wrong in BSI and BTEMP lines, the device seems to be dead after battery insertion. However, the regulators in the device are on 10s before the powerdown. This mode can easily be detected from the current consumption of the device. After 10s the current consumption drops almost to 0mA. In this case check components C126, C127 R121, R122, R123, C103, C104, battery connector X100.

Issue 1 06/01

Page 8 ­ 19

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.4

Charging checking
Use the BLL­3 battery and the JBE-2 calibration unit to test charging. 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 and supported by phone then the software doesn't start charging and display 'NOT CHARGING'. Remove and reconnect battery and charger few times before you start to measure module. This check ensures if module fault really exists. See the diagram Figure 11 next page.

Page 8 ­ 20

Issue 1 06/01

PAMS Technical Documentation
Display information: NOT CHARGING Nothing happens when charger is connected

RAE-3 8. Troubleshooting

R121 voltage is ~1.1V when charger is connected YES

NO

Check BLL­3, BSI resistor, X100, R121, R122

NO V_in voltage at R111 >0.4 V ?

YES

Check BLL­3, X100, X450, F450, V450, L453. L454 R107, R111 C454, C455

R123 voltage is ~0.5V when charger is connected YES

NO

Check BLL­3, BTEMP NTC, X100, R122, R123

Perform Energy Management Calibration with WinTesla software and JBE­2 set

NO 1Hz or 32Hz square wave (CHRG_CTRL) when charger is connected * Calibration OK ? NO Check R451, R461, C456 Fault in N100 or N101

NO YES Charging OK? Fault in N100

Voltage over R101 > 0.1 V when charger is connected

NO Fault in N101

YES

* Note:No square wave if phone displays "NOT CHARGING"

Perform Energy Management Calibration with WinTesla software and JBE­2 set

NO Charging OK? Fault in N101

Figure 11.

Issue 1 06/01

Page 8 ­ 21

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.5

Backup Battery

CAUTION Danger of explosion if the battery is incorrectly replaced. Replace only with the same or equivalent type recommended by the equipment manufacturer. Discard used batteries according to the manufacturer's instructions.
Figure 12.

2.5.1

Backup battery troubleshooting Main power supply to the device must be 3.7 V when used. Symptom of Backup battery fault is: Real Time Clock loses the correct time when the main battery is not connected. The same symptom can also be seen when the backup battery is empty. About one week is needed to fully charge the backup battery in the device. Always check the backup battery visually for any leakage or any other visual defect. Check that the backup battery is correctly mounted in the device before closing the cover. KEEP IN MIND THAT THE BACKUP BATTERY DOES NOT TOLERATE EXCESS HEAT. WHENEVER HEAT BLOWER IS USED, FOR EXAMPLE TO REMOVE COMPONENTS, FIRST REMOVE THE BACKUP BATTERY AND PLACE IT TO ADEQUATE DISTANCE FROM THE WORKING LOCATION. 1. Remove the backup battery. 2. Measure the voltage of the backup battery: S S Normal operation when the voltage is >1.8V. Fully charged when voltage is about 3.1V.

3. Connect 3.7V power supply to the device. Issue 1 06/01

Page 8 ­ 22

PAMS Technical Documentation 4. Check the backup battery connector X102 visually. 5. Measure voltage at terminal 1 of X102. It must be 2.82 V to 3.3V. ­> if NOT OK, then N101 is faulty.

RAE-3 8. Troubleshooting

6. Insert the backup battery in the connector, make sure that the contact is good. 7. Measure voltage at terminal 2 of X102. It must be 1.8 V to 3.3V. This voltage increases because of charging if the battery is not fully charged. 8. Read the backup battery with WinTesla. ­> if not OK then N100 is faulty. 9. Ensure that the RTC running time is set to 10 hours setting. When the service battery BBL-3B is used, this is set automatically. (See General Guidelines)

Issue 1 06/01

Page 8 ­ 23

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.6

Accessory Power Output Troubleshooting
Accessory power output is connected to the system connector's DCE_DTR pin inside the device.Accessory power output can be tested with MJS­14 test jig and Wintesla SW. There is a pushbutton called ACC VOLTAGE in MJS­14 test jig which is used to connecting load to DCE_DTR pin of the system connector. Following Figure 13 shows the connection in MJS­14 test jig (load side).
Pushbutton: ACC VOLTAGE

DCE_DTR (pin 10) In system connector 47R

4.7µF 6.3V

Figure 13. ACC VOLTAGE test configuration in MJS­14 test jig

Figure 13 describes the ACC VOLTAGE test configuration in the MJS­14 test jig. Status of the DTR signal in MADLinda is read by Wintesla SW. Test sequence in use is roughly shown in the following Figure 14: .
VACC_CTRL control goes ON DTR signal

Press ACC VOLTAGE button

VACC_CTRL control goes OFF

Release ACC VOLTAGE button

Figure 14. Test sequence

Figure 14 describes the test sequence and status of DTR line during Accessory Power Output Testing . Accessory output voltage test in Wintesla asks the test person to press ACC VOLTAGE button and keep it pressed. After that SW automatically turns ON and OFF the accessory output voltage and gives the passed/fail information. Wintesla SW gives guidance during this test.

Page 8 ­ 24

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.6.1

No Accessory Voltage when needed
­ Power supply must be 3.7V. ­ MJS­14 Test Jig must be used. ­ Signals must be measured during Wintesla Accessory Power Output Test .

Fail in WinTesla accessory power out test

Check VACC = 3.3V ( Pin 5 of N104)

Yes

Check X450, V451, R454, R310, V489 and C459

No

Check VB=3.7V (pin 1 of N104), When VACC_CTRL=HIGH (pin 3 of N104) Yes

No

Fault in D300 or N104

Check N104, C129, C139, C116, R310, V489

Test again with Wintesla

Figure 15.

Issue 1 06/01

Page 8 ­ 25

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.6.2

Accessory Voltage ON all the time
­ Power supply must be 3.7V. ­ MJS­14 Test Jig must be used. ­ This fault can be seen also as serial interface problem. ­ Signals must be measured during Wintesla Accessory Power Output Test.

Fail in Wintesla accessory power out test Or Jump from Serial Interface Troubleshooting

Check VACC = 0V (pin 5 of N104) When VACC_CTRL=LOW (pin 3 of N104) While ACC VOLTAGE button pressed

Yes

Check X450, V451, R454, R310, V489 and C459

No Check N104, C129, C139, C116, R310, V489, D300

Test again with Wintesla

Figure 16.

Page 8 ­ 26

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.7
2.7.1

Clocks
Clocks Troubleshooting When the flashing of the device does not succeed, but the powering is OK, follow these instructions. Note: The absence of clocks may indicate that the device is in sleep mode. Move the magnet away from the sensor to simulate cover open situation. IMPORTANT: Clock signals must be measured with 1M (or greater) probe! New Tektronix P6249 probes (20k impedance) and similar cannot be used! 1 Measure RFC signal at C303. It should show 13.000 MHz sine wave, approximately 1.2Vp­p with about 950mV DC­offset (see Figure 17). Check the C303 capacitor. · If this is OK, the processor gets the clock signal. The processor may be faulty, or the fault is in the memories. Continue to "Memories" section. · If there is the clock signal, but there is no DC­offset (signal low level around 0V), check the probe used so that it is not loading the signal. If the probe is not responsible for missing DC­offset, try cycling the power a couple of times. If this does not help, the clock slicer circuitry in the MADLinda (D300) is faulty. · If there is no clock signal at all, continue at 2.

Figure 17. Clock signal

2. Check VXO power line at C553. It should be around 2.8V. If it is, move to 4. 3. · Check VCXOPwr (J302). It should be around 2.8V. If it is 2.8V, CCONT (N100) is faulty.

· If VCXOPwr is 0V, MADLinda (D300) has shut down the regulators (sleep) or it is faulty. Cycle the power and re­check.

Issue 1 06/01

Page 8 ­ 27

RAE-3 8. Troubleshooting

PAMS Technical Documentation

1. Open the smaller RF shield metal can. Check Hagar RFC­out signal at V800. It should show sine wave of 1.2V amplitude, 13MHz frequency (see Figure 18 ). · If this is OK, the problem is in V800 transistor or in R834, R830, C834, L800.

Figure 18. 13 MHz sine wave

2. Check VTCXO output at R833. This should be 26MHz sine wave (see Figure 19 ). · If this is OK, Check R835, C830 for shorts and bad connections. If they are OK, Hagar (N505) or C800 or R829 is faulty. · If this is not OK, R835, C830, R833 may be faulty. If they are OK, check VTCXO (G830).

Figure 19. 26 MHz sine wave

Page 8 ­ 28

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.8
2.8.1

Memory Tests
Test in boot up ­ manufacturer and device id are read from each of the flashes then compared to value stored in FLASH 0. ­ id read program code is executed from API RAM ­ If FLASH 0 is broken the phone will not boot up properly (user test code resides in FLASH 0) i.e. probably not even blink CMT backlights. ­ If one or more flash manufacturer and device id read fail CMT display backlights will blink 2 times in a loop.

FLASHes 0 (D351), 1 (D352) and 2 D(353):

SDRAM (D350): ­ Data bus test: · · · Test will detect if lines are stuck at high or low state Test will detect any bridging faults data is written to certain addresses and read back and verified

­ Address bus test: ­ tested lines: address bus, data bus, SDRRASX, SDRCASX, SDRWEX and SDRCLK ­ SDRDQMU, SDRDQML and SDRCKE functionality is tested only partly ­ If either of these tests fail CMT display backlights will blink 3 times in a loop Serial FLASH (D354): ­ Id is read and id bits (3­5) are compared to value 0x30 ­ If the test fails CMT display backlights will blink 4 times in a loop ­ tested lines: SEPI, SEPO and SEPClk SEPCSX (low) and EXT_SYS_RESETX (high) tested partly ­ problems found with test SW: · id read fails and CMT backlights blink but serial flash is ok problem is in MADLinda

Issue 1 06/01

Page 8 ­ 29

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.8.2

Test in PTS/WinTesla flashing These tests are in the beginning of device flashing. If any of these tests fail the flashing will be stopped and a notification will be shown on the monitor screen.

SDRAM (D350): ­ data is written to certain addresses, read back and compared FLASHes 0 (D351), 1 (D352) and 2 D(353): ­ device and manufacturer ids are read from each of the flashes and then the values are compared (same test as in boot up) Serial FLASH (D354): ­ device id is read and the value is compared (same test as in boot up)

Page 8 ­ 30

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.9
2.9.1

Memory Troubleshooting
Memory fails In Boot Up tests, CMT Backlight is blinking If the device won't boot up and CMT display backlight is blinking FLASH 0 (D351) probably ok ! To measure signals from D352, D353, D350 and D354 the device needs to rebooted up constantly since the lines are active only a short time in the beginning of the boot. Also CCONT WATCHDOG will shut the device off after 32 seconds ! Time between each memory device blinks is 1 second and time between different memory device blinks is 2 seconds. For example if FLASH1 and Serial Flash are broken the blinking sequence goes: 2 blinks with 1 sec interval (FLASH fault) 2 sec without blinks 4 blinks with 1 sec intervals (Serial Flash fault) 2 sec without blinks then to the beginning again

Issue 1 06/01

Page 8 ­ 31

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.9.2

CMT display backlight blinking 2 times in a loop CMT display backlight blinking 2 times in a loop ("Flash fault"): Manufacturer and device id read from FLASH 1 (D352) or FLASH 2 (D353) or from both fails.

ID read from FLASH1 or FLASH2 fails

Flash the device

D352 ID read fails during flashing

D353 ID read fails during flashing

Check: negative pulses on J339 (1.8V) OK? NO YES YES

Check: negative pulses on J340 (1.8v) OK? NO

Problem in D300 (MCU)

Change D352
Figure 20.

Change D353

Problem in D300 (MCU)

See FLASH signal pictures later.

Page 8 ­ 32

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.9.3

CMT display backlight blinking 3 times in a loop CMT display backlight blinking 3 times in a loop ("SDRAM fault"):

D350 SDRAM test fails

Check activity from SDRAM lilnes

SDRRASX (J312): negative pulses (2.8V) SDRCASX (J313): negative pulses (2.8V) SDRWEX (J314): negative pulses(2.8V) SDRCLK (J310): 13MHz clock (2.8V) SDRAd6 (J348): postive pulses (2.8V) SDRDQML (J315): negative pulses (2.8V)

SDRDQMU (J316): negative pulses (2.8V) SDRCKE (J311): high (2.8V) SDRDa8 (J349): positive pulses (data pulses driven by SDRAM have bigger over shoot spikes than data driven by MADLinda MCU, see figure 23) (2.8V)

Pulses on MADLinda control lines J312, J313, J314, J310, J348, J315, J316 or J349

OK

NO D300 faulty Replace D350 if J349 data pulses with big overshoot spikes are missing
Figure 21.

Issue 1 06/01

Page 8 ­ 33

RAE-3 8. Troubleshooting

PAMS Technical Documentation

SDRDa8 J349

Figure 22.

SDRAM (D350) driven data line SDRDa8 (J349)

SDRCLK J310 SDRRASX J312 SDRCASX J313 SDRWEX J314

Figure 23.

SDRAM signals and levels 1

Page 8 ­ 34

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

SDRCLK J310 SDRAd6 J348 SDRDQML J315 SDRCKE J311

Figure 24.

SDRAM signals and levels 2

Issue 1 06/01

Page 8 ­ 35

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.9.4

CMT display backlight blinking 4 times in a loop CMT display backlight blinking 4 times in a loop ("Serial Flash fault"):

D354 Serial Flash ID read test fails

Check activity in serial FLASH lines

SEPClk (J327):6.5MHz clock (2.8V) SEPO (J329): positive pulses (2.8V) SEPCSX (J337): long negative pulse (2.8V) EXT_SYS_RESETX (J301): high (2.8V) SER_FL_RBY(J346): high (D300 internal pull­up, use passive probe!) (2.8V) SEPI (J328): Positive pulses (D300 internal pull­up) (2.8V)

If no pulses found from J327, J328, J329 or from J337 problem is in D300

If J301 or J346 are low problem is D300

If J328 stays always high change D354

Figure 25.

Page 8 ­ 36

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

SEPCLK J327 SEPO J329 SEPI J328 SEPCSX J337

Figure 26.

Serial Flash (D354) id read sequence.

Issue 1 06/01

Page 8 ­ 37

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.9.5

Memory fails in PTS/WinTesla flashing Refer to the previous "SDRAM fault" chapter.

1. SDRAM id read test fails 2. Flash manufacturer and device id read fails a) If id read from all of the three flashes (D351, D352 and D353) fails most likely the problem is in D300. Check D300 and control lines: S S S S S S S S S FLDa7 (J351): positive pulses (1.8V) FLCS0X (J338): negative pulses (1.8V) FLOEX (J341): negative pulses (1.8V) FLCS1X (J339): negative pulses (1.8V) FLWEX (J342): negative pulses (1.8V) FLCS2X (J340): negative pulses (1.8V) FLAd5 (J350): positive pulses (1.8V) FLRPX (J343): high (1.8V) FLWPX (J347): low (1.8V)

If any of the signals is missing the problem is in D300. b) If id read from one or two flashes fails

Page 8 ­ 38

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

ID read from FLASH fails D351 id read fails D352 id read fails D353 id read fails
Check if FLCS0X OK, J338

YES

NO

YES NO
Check if FLCS1X OK, J339

Problem with D300

Change D352
YES
Check if FLCS2X OK, J340

NO

Change D353
Figure 27.

Refer to the oscilloscope screen shots next page for what the signals should look like.

Issue 1 06/01

Page 8 ­ 39

RAE-3 8. Troubleshooting

PAMS Technical Documentation

FLCS0X J338 FLOEX J341 FLWEX J342

Figure 28.

Flash 0 (D351) manufacturer and device id read

FLAd5 J350 FLDa7 J351

Figure 29.

the Flash address and databus signals

2.9.6

Serial Flash id read test fails Refer to previous chapter "Serial Flash fault" 2.1.2

Page 8 ­ 40

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.10

Serial Interface Troubleshooting
Serial Interface problem 1. Check Serial connector X450 spring contacts YES Flashing successful? NO 2. Check and replace ESD protection device V451 3. Check DCE_Tx (AccRxData) comp. R452, C458, R300 Activate WinTesla, observe ADC­readings Check that "DTR Detection" state changes by pressing ACC_VOLTAGE switch in the service jig YES OK? Flashing successful? Check DCE_DTR line comp. R454, C459,V489, R310 YES NO 4. Check DCE_Rx (AccTxData) comp. R453, C457, R307 5. Check DCE_DCD (MBus) comp. R450, C453, R309 NO

Serial I/O OK

OK? NO Refer to Accessory power output troubleshooting OK Faulty MAD (N300) or PWB fault Figure 30.

NOTE1:

Ensure that the customer's DLR­2L is OK.

NOTE2: Wintesla ADC­readings for 'DTR Detection': state "0" = DCE_DTR ­ line at 2.8 ­ 3.0V Wintesla ADC­readings for 'DTR Detection': state "1" = DCE_DTR ­ line at 0 ­ 0.3V NOTE3: Signal levels in practice: High 2.7V, Low 0.3V

Exception: Diode in DTR line causes voltage drop, see Figure 31 below:

Issue 1 06/01

Page 8 ­ 41

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.95V

2.8V

With DLR­2L C1, black: MAD end C5, green: syscon end

0.3V

0V

Using DLR­2: GRP1, black: MAD end GRP2: System connector end

Figure 31. DTH line voltage

Page 8 ­ 42

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

MBUS (clock) Signal during flashing (Figure 32):

GRP1, black: MAD­end GRP2: system connector end Approx. 0.2V difference results from MBUS pull­up resistor (R309, 4k7) & serial resistor (R450, 270R) voltage slicing.

Figure 32.

MBUS (clock) Signal during flashing

Issue 1 06/01

Page 8 ­ 43

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.11

CONTACT SERVICE in CMT display
CONTACT SERVICE in CMT display (Self-tests with WinTesla)

Display Information: "Contact Service" This fault means that software is able to run and thus the watchdog of CCONT (N100) can be served. Self­test functions are executed when power is switched on and software is started to execute from flash. If any one of the self­tests fails (except no. 3, 7, 8, and F), the text "Contact Service" is shown in the phone display. MCU Self­tests are divided into those executed while power up (tests: 1­5 and 9­I ) and the ones can be executed with the connected PC. The tests and included items are as follows (Figure 33, screendump from the WinTesla)

Figure 33.

The information can be used for diagnosis. Memory tests differ from normal DCT3 self­tests. They can not be executed in the ENOS because memory protection. There is no EEPROM. The EEPROM is emulated in the FLASH (part of CS2). All contents where EEPROM is mentioned refer to emulated EEPROM. Item no. 1; MCU ROM Checksum: Issue 1 06/01

Page 8 ­ 44

PAMS Technical Documentation

RAE-3 8. Troubleshooting

Calculates 16 bit checksum out of Flash code and compares it to the one found in Flash. Items being checked are MADLinda <­> Flash data­ and address lines FLDa0­15 and FLAd1­21, FLCS0X (CE0), FLCS1X (CE1), FLCS2X (CE2), FLWEX (WE), Vbb (Vcc), VCORE (Vccq), GND, and Flash internal functionality. Item no. 2 MCU EEPROM Interface: Checks current PMM error status. If this test FAILs, the PMM data is not valid anymore and should be formatted. Item no. D COBBA Serial This test tests Audio interface (PCM) of the COBBA_GJP. Item no. E COBBA Parallel This test tests the serial control/RF interface of the COBBA_GJP.

Issue 1 06/01

Page 8 ­ 45

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.12

CCONT Serial interface Troubleshooting
If there are problems in CCONT's serial control interface, self tests fail and there is "Contact service" shown on the display. Wintesla shows this fail as "CCONT Interface". NOTE: Low level means 0V, high level means approximately 2.8V.
Check GENSCLK line at J318 Square wave, Freq. 2.17 MHz ? (see note below?)

Check CCONTCSX line at J317 Activity? Signal active low

NO OK? YES
D300 or PWB faulty

Check GENSDIO line at R308 Activity? Signal active high

Check all three lines simultaneously, see fig. below

Figure 34.

(Note: Measurement should show 2.17MHz square wave. This interface is connected to CMT display also, so there is other activity too. The 3.1MHz clock is targeted for CMT display, do not worry about that. The clock signal is low when inactive.) 1. Measure all the three lines simultaneously (Figure 35). Set the trigger to CCONTCSX line falling edge. You should see the two cases, Figure 35 and Figure 36 . (Channel 1­GENSClk, Channel 2­CCONTCSX, Channel 3­GENSDIO). High level is about 2.8V

Figure 35.

Page 8 ­ 46

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

MADLinda writes to CCONT. The data at sixth bit is '0' as marked with the cursors. The data after the read/write bit varies, just like the address before the bit. If you can see this kind of traffic, MADLinda side of the interface is functioning correctly.

Figure 36.

MADLinda reads from CCONT. The data at sixth bit is '1', marked with the cursors. There should be data seen after the 'read' bit. All zero values may be read, but there should be other data seen, too. CCONT read cycles are fairly rare compared to write cycles. If there is not any non­zero reads from CCONT, the CCONT (N100) may be faulty.

Issue 1 06/01

Page 8 ­ 47

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.13
2.13.1

SIM Card
SIM Card Error Troubleshooting The fault information "SIM Card error" means most likely that the SIM locked phone has been inserted with a SIM which does not correspond to the lock code. Check the SIM lock status of the phone with WinTesla:

"SIM Card Error" message in display ?

Set the phone in NORMAL mode

View­> Quick/RF Info

See "SIM Lock Settings" field:

NO

Blank field?

YES

No SIM lock. Refer to "SIM Card Rejected" troubleshooting

SIM lock activated: inform customer

Customer contacts network operator to ask for lock reset

Figure 37.

Page 8 ­ 48

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.13.2

SIM Card Rejected The fault information "SIM Card rejected" means that the ATR message (Answer To Reset; the first message from SIM card to phone after SIM card power up) is sent, but it is corrupted somehow, eg. the dataline signal levels are wrong or factory set values (stored in the EEPROM) are not correct. NOTE1: CHECK THE MEASUREMENT POINT PICTURE BEFORE SERVICE ACTIONS SIM_xxx_Cardside ­ refers to signal which exists in SIM card contacts SIM_xxx_o ­ refers to signal which exists in CCONT(N100) side NOTE2: SIM Signals between CCONT (N100) and LindaMAD (D300) are not possible to measure in bl8­module because traces are running in inner layers of PWB.

Issue 1 06/01

Page 8 ­ 49

RAE-3 8. Troubleshooting

PAMS Technical Documentation

SIM CARD FAULT YES Check VSIM at SIM card pin

5V card:Check 5V charge pump components C107 V101 C110

NO

VSIM= 2,8V min. with 3V 4.5V min. with 5V card card YES Check V103 pins Pin_1: CLK Pin_6: DATA Pin_4: Reset

NO

3V card: Check N100 (CCONT) C112, C113 Replace if necessary

Still problem? YES

Replace N100 (CCONT)

Lines rising 0V ­>3V/5V after power on ? YES Check ATR data at N100

NO

Check SIM card reader mechanical connections and eventual short circuits from CLK, DATA and RESET lines against GND

R112 at N100 (CCCONT) side /SIM_DATA_0 OK? YES Check N100 (CCONT)

NO

Check X101, V103, R109, R112 R125

D300 (MAD) faulty

YES

Still problem?

NO

N100 faulty

Figure 38.

Page 8 ­ 50

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.13.3

Insert SIM card The hardware of the SIM interface from the MADLinda (D300) to the SIM connector (X101) can be tested without SIM card. This leaves SIM connector (X101) contacts to be used as an measurement points. When the power is switched on and if the BSI line (X100:2) is grounded by resistor (which happens automatically in service jig), all the used lines (VSIM, RST, CLK & DATA) rise up to 3V and/or 5V four times (SW tries to ask SIM card four times). NOTE1: CHECK THE MEASUREMENT POINT PICTURE BEFORE SERVICE ACTIONS SIM_xxx_Cardside ­ refers to signal which exists in SIM card contacts SIM_xxx_o ­ refers to signal which exists in CCONT(N100) side NOTE2: SIM Signals between CCONT (N100) and LindaMAD (D300) are not possible to measure in BL8­module because traces are running in inner layers of PWB.

Issue 1 06/01

Page 8 ­ 51

RAE-3 8. Troubleshooting
Insert SIM card fault YES Check Voltage level between R121 and C126 When BSI resistor connected (included in service jig YES NO Check Volt.level R121, R122, <1.5V ? X100, C126 YES 5V card:Check 5V charge pump components C107 V101 C110 NO­5V
VSIM at SIM card pin 2.8V min. with 3V card 4.5V with 5V card

PAMS Technical Documentation

NO­ 3V

3V card: Check N100 (CCONT) C112, C113 Replace if necessary

YES Check VSIM, DATA, RESET, CLOCK lines at the pins of ASIM connector (X100) or SIM_xxx cardside signals at measurement points YES Lines rising 0V­>3V/5V after power on ? NO Check VSIM (V103 pin 3) DATA_0 (R109) SIMRST_0 (R125) at N100/CCONT side (ref. Measurement point diagram) NO Faulty PWB Faulty D300 Lines rising 0V­>3V/5V after power on ? NO Still problem? Replace N100 (CCONT) YES Check X100, V103 R109, R112 R125 YES Check SIM card, SIM card reader mechanical connections

Still problem? YES

Faulty N100 (CCONT)

NO Replace D300 (MAD)

Still problem?

YES

SIM I/O OK, N100 (CCONT) faulty

Figure 39.

Page 8 ­ 52

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.14
2.14.1

Memory Card
Memory Card Interface Troubleshooting Start with assembled device with a faultless memory card inserted. If necessary, proceed with tests in the jig with the faultless memory card inserted. Clk, Cmd and Data OK means that frequency, rise and fall timing are OK during various operating modes. Note: During initialization phase (MMCClk = lower frequency) the response via MMCCmd line from card to MAD is sent in open drain mode i.e. rise time is about 1us. Voltage of MMCCmd and MMCDa signals depends on direction of transfer (MAD I/O voltage is 2.8V and Card I/O is 3.0V). Test pads J10x are located on the JL4 board of the Module Jig. Troubleshooting diagram next page, Figure 40.

Issue 1 06/01

Page 8 ­ 53

RAE-3 8. Troubleshooting Memory card interface check
Run WinTesla Memory card test YES

PAMS Technical Documentation

Test OK?
NO Run Memory Card cover Switch fault test

A faulty Memory Card used before ? SW corruption ?

Assembled device Disassembled device in jig
YES Measure VMMC J104 while re­running the MemCard test NO 2.9 ­ 3.1V ? MAD I/O fault NO

Switch OK ?
NO

Ref Memory card cover switch fault tree

YES Measure MMCClk J105 while re­running the test NO

Check X001/4 Measure N103/1 Ctrl (control from OK? MAD while re­running the test YES

Clk OK ?
YES Measure MMCCmd J102 while re­running the test NO CMD OK ? YES Measure MMCDa J107 NO Data OK? YES Undefined CPU error

Check X001/5 R004 and V001/4

Check N103 C114 C123 C124 R007 C001

Parts OK?
YES

Check X001/2 R005, R002 V001/3
YES OK?

Check X001/7 R001, R003 and V001/6
YES Parts OK ? MAD I/O fault

Figure 40.

Page 8 ­ 54

Issue 1 06/01

PAMS Technical Documentation 2.14.2 Memory card switch troubleshooting:

RAE-3 8. Troubleshooting

NOTE1: Memory card switch pressed (lid closed) => ADC reading 'Memory Card Cover Detection' is in state "0" => MMC_Switch ­ line = 0V Memory card switch released (lid opened) => ADC reading 'Memory Card Cover Detection' is in state "1" => MMC_Switch ­ line = 2.8V
MMC Card cover switch problem YES Open WinTesla Testing­> ADC Readings OK Open RAE3 lid after boot

NO

MMC lid open according to * WinTesla ?

YES

Close MMC card cover and wait updated values from WinTesla

Check J001 (MMC switch) OK Check C002 and V001 OK?

Check mech. functionality of J001 check contact surfaces

NO

Lid closed according to * WinTesla ? YES MMC cover switch J001 OK

Faulty circuit D300 (MAD) or PWB Check R006

OK? NO MMC cover switch J001 broken

OK? * note: Cover opened MMC cover detection ="1" Cover closed MMC cover detection = "0"

R006 faulty Figure 41.

Issue 1 06/01

Page 8 ­ 55

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.15
2.15.1

Lid Switch
Lid Switch Troubleshooting NOTE1: Lid signal (MAD pin P2 gendet) : Lid closed = 'Cover Detection' from Wintesla ADC readings is state "0" => V301 (HALL) output = 2.8V Lid opened = 'Cover Detection' from Wintesla ADC readings is state "1" => V301 (HALL) output = 0V Troubleshooting diagram Figure 42 next page.

Page 8 ­ 56

Issue 1 06/01

PAMS Technical Documentation
Lid switch trouble­ shooting Open Wintesla Select Testing ­>ADC Readings Turn the phone power on Open the lid

RAE-3 8. Troubleshooting

Wintesla: Lid Open OK (cover detection state ASSEMBLED DEVICE 1) ? NO DEVICE IN JIG Check V301, C322 NO N301 pin 1 (Hall supply volt) 2.8V ? YES Use serv.jig magnet

Place magnet above the TAB key, note: pole toward the key ! then wait Refresh from Wintesla

Wintesla: Lid Closed OK (ADC reading Cover switch= "0" NO Check Hall supply volt. level at V301 pin 1 (VBB) 2.8V OK? YES Use serv.jig magnet

YES

Lid switch OK? Check/replace magnet in the lid

NO

Check V301, C322

Check V301, (solders) R302 If OK, replace V301

NO

Out­ put toggle of V301 pin 3 low state (<0.3V) ?

YES

Faulty circuit D300 (MAD) or Faulty PWB

YES

Out­ put toggle of V301 pin 3 high ?

NO

Check V301 solders

YES

Short circuit inC323 ? R302: high voltage level (2.8V) at both ends? NO

OK Replace V301

Check trace between V301 pin3 and R302

Figure 42.

Issue 1 06/01

Page 8 ­ 57

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.16

Battery Removal Switch troubleshooting
NOTE1: Switch itself is not possible to test in service jig. NOTE2: Switch FREE position = Wintesla ADC­readings 'Battery Removal Switch' is in state "0" =>BATT_REM ­ line = 2.8V Switch CONNECTED position = Wintesla ADC­readings 'Battery Removal Switch' is in state "1" => BATT_REM ­ line = 0V NOTE3: Battery removal switch (latch spring) gets connected when battery latch is pressed during battery release. Refer to the diagram Figure 43 next page.

Page 8 ­ 58

Issue 1 06/01

PAMS Technical Documentation
Battery removal switch problem YES Open WinTesla Testing­> PDC readings OK Latch "FREE" position

RAE-3 8. Troubleshooting

NO Short circuit in switch lines (BATT_REM) Check Z401 Reading "1" though latch position "FREE" ?

Battery removal switch state ="0" ?

YES

Keep latch in opposite position wait updated values from WinTesla

NO NO

State changes to "1" ? YES

YES

Check B­to­B adapter JC4 pin 42: BATT_REM line:

Battery removal switch OK

Faulty circuit D300 (MAD)

YES

Voltage high (=2.8V) ?

NO

1. Check latch spring and AF8 pads 2. Check B­to­B connector X400 of UL8 and flex FL1 3. Check filter Z401 BATT_REM line

Figure 43.

Issue 1 06/01

Page 8 ­ 59

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.17

COBBA Control Interface troubleshooting
NOTE: If there are problems in COBBA serial interface, self tests fail and there is "Contact service" shown on the display. Wintesla shows fails at "Cobba parallel".

Check COBBACLK line at J322 Square wave, Freq. 13MHz ? Signal rising/falling edge 3 to 5 ns? Signal duty cycle about 50per cent? Low when inactive?

Check COBBASDA line at J324 Activity? Signal rising/falling edge 3 to 5 ns? High when inactive ?

NO OK? YES
D300 or PWB faulty

Check COBBACSX line at J323 Activity? Signal rising/falling edge 3 to 5 ns? High when inactive ?

Check all lines simultaneously, see fig. below Check COBBARSTX a J321 High (about 2.8V) ?

Figure 44.

Figure 45.

Write sequence to COBBA.

Figure 45 is a write sequence to COBBA. There should be non­all­zero writes to COBBA. Issue 1 06/01

Page 8 ­ 60

PAMS Technical Documentation

RAE-3 8. Troubleshooting

Figure 46.

COBBA read

Figure 46 is a COBBA read. The MADLinda writes first the address to be read, deactivates the COBBACSX line and then activates the COBBACSX line again. Then the COBBA_GJP sends the requested data. There should be non­zero reads. If no non­zero reads from COBBA can be seen, COBBA (N200) may be faulty. If both reads and writes of non­zero values can be seen and the signal characteristics were good, the COBBA serial control interface is working correctly.

Issue 1 06/01

Page 8 ­ 61

RAE-3 8. Troubleshooting

PAMS Technical Documentation

2.18

COBBA PCM Interface Troubleshooting
PCM interface transfers digital audio data. Problems in this interface result in missing or flawed audio in either or both in uplink and downlink directions. If Wintesla shows errors in "COBBA serial interface", PCM interface is faulty.
Check PCMDClk signal at J309: 520 kHz square wave 50 per cent duty cycle Rising and falling edges about 3 to 5 ns Inactive state low? Ref. fig. 48

YES OK?

NO
N200 faulty

Check PCMSClk at J306 short pulse, rate 8.000kHz 1.52 per cent duty cycle Rise and fall times about 3 to 5 ns Ref. fig. 49 Inactive state low?

YES OK?

NO
N200 faulty

Check PCMRx Data signal at J308 Activity during call and voice recording If mic picks up sound, higher states at the cycle start Rise and fall times about 3 to 5 ns Signal idle state High with some 13MHz noise? Ref. fig. 50

YES OK?

NO
N200 faulty

Check PCMTx data signal at J307 Activity during call Rise and fall times about 4 to 7 ns Idle statle low? Ref. fig. 51

NO OK?
N200 faulty

Figure 47.

There is no traffic in PCM interface without a call or audio play (voice recorder, video player, etc). These signals can be measured with a call, which generates Issue 1 06/01

Page 8 ­ 62

PAMS Technical Documentation

RAE-3 8. Troubleshooting

traffic in both directions. Audio play generates traffic in one direction only. Recording audio (voice recorder) generates traffic in the other direction.

Figure 48.

PCMDClk signal at J309

Figure 49.

PCMSClk signal at J306.

Issue 1 06/01

Page 8 ­ 63

RAE-3 8. Troubleshooting

PAMS Technical Documentation

Figure 50.

PCMRxData signal at J308.

Figure 51.

PCMTxData signal at J307

PCMTxData signal at J307 (Figure 51). This signal comes from the other end's microphone or audio playing software (voice recorder, video player etc) and is targeted for the earpiece or hands free speaker. There should be activity during a call. Signal rise and fall times are around 4­7ns. Idle state is low.

Page 8 ­ 64

Issue 1 06/01

PAMS Technical Documentation

RAE-3 8. Troubleshooting

2.19
2.19.1

Audio troubleshooting
Both Mic and Earpiece/PHF faulty
MIC and Earpiece /PHF faulty

Check voltage at cap C208 HOOKDET without external audio devices

OK HOOKDET 2,8V?

NO

Check R206 and R207, C208

Check voltage at cap C202 HEADDET without external audio devices

OK

NO HEADDET 2,8V?

Check R203, R202, R200 C201, C202

Check frequency at J309 PCMDClk during a call

OK

520kHz square wave 2.8Vpp (ref.fig.53)

NO

Faulty N200 (COBBA) *

* refer to section 2.17 in this document

Check frequency at J306 PCMSClk during a call

8 kHz square wave 2.8Vpp (ref.fig.54)

NO

Faulty N200 (COBBA) *

Figure 52.

PCMDClk

Issue 1 06/01

Page 8 ­ 65

RAE-3 8. Troubleshooting

PAMS Technical Documentation

Figure 53.

PCDClk

Figure 54.

PCMSClk Issue 1 06/01

Page 8 ­ 66

PAMS Technical Documentation 2.19.2 Mic faulty
MIC faulty

RAE-3 8. Troubleshooting

Check microphone and mic connections to PWB Check digital PCM data atJ308 (PCMRxData) during a call

OK

Data OK? Check voltages : V202 pin 1 : 1.8V V202 pin 3: 0.17V during a call

NO

Faulty N200 (COBBA) Refer to COBBA control interface troubleshooting

OK Voltages OK?

NO Check R222, R218 C231, C224, C230 OK

DC voltage at C234 and C235 1.4V during call ? *

Mbias at R222 2.1V during call? NO

*

OK

Voltages OK?

NO

Check analog audio signal at C232 during a call *

Check C234, C235 OK Fault in N200 (COBBA) NO Check C225, C240, R219, R220 and PWB traces

Signal a few mV ?

Figure 55.

Note:* can not be measured in the service jig, because components are under the SIM connector. Use wire to measure them. After removing measurement wire, check that components are not defected. It is recommended to replace the components.

Issue 1 06/01

Page 8 ­ 67

RAE-3 8. Troubleshooting 2.19.3 Earpiece faulty

PAMS Technical Documentation

Earpiece faulty

Check assembly of earpiece and gasket

1)

Check connections from audio PWB to C229 and C228 OK NO Check Flex UL8 and B­to­B conn X400 pins 47, 48

Connection OK? Check digital PCM data at J307 (PCMTxData) during a call

OK Data OK?

NO

Faulty D300 (MAD) 2)

DC voltage at C228, C229 1.4V during call ?

OK

NO Voltages OK?

Check R215, R216 and connections. Check C228, C229

Check analog audio signal at C228, C229 during a call

OK?

Signal a few mV ?

NO

Faulty N200 (COBBA)

Figure 56.

Note: 1) If sound is distorted or too quiet fault is most probably in the gasket or in the earpiece diaphragm. 2) Refer to section 2.16 in this document. Issue 1 06/01

Page 8 ­ 68

PAMS Technical Documentation 2.19.4 PHF Speaker faulty

RAE-3 8. Troubleshooting

PHF Spealer faulty

Check assembly of HF speaker, springs and connection to flex UL8 Check connections from speaker pads to C236 and C237 NO Connection OK?

OK

Check Flex UL8 and B­to­B conn X400 pins 43 to 46

Check VAMP at R201, R204, R205, R221 *

OK VAMP about VBATT ?

NO Check R201, R204, R205, R221 C203, C204, C205, C206 *

AMP SHDN at V200 pin 2 2.8 V during a PHF call ?

OK

NO Voltages OK?

Faulty D300 (MAD)

Amplifier enabled? Check voltage at N201 pin 1

Faulty V200

NO OK Voltage low?

* (Note: R201, R221 only in BL8_18) Note: R204 and R205 havedifferent resistance values in BL8_17 and BL8_18

Continues next page

Figure 57.

Issue 1 06/01

Page 8 ­ 69

RAE-3 8. Troubleshooting

PAMS Technical Documentation

PHF speaker fault continued Check R208, C213 and XEAR traces from C220 to N200

Check analog audio input signal XEAR at C22