Advertisement
Customer Care Europe, Middle East & Africa
SCCE Training Group
CHAPTER 8: CONTACT SERVICE
This failure is easy to detect, because it appears on LCD as text and no more application are possible.
Anyway the phone software is running and thus the watchdog of CCONT N201can be served.
Each time when the power is switched on, the selftest process begins to run.
The software for it is executed from FLASH. If finally any selftest fails, "Contact Service" is shown on LCD.
Most common faults:
MCU ROM Checksum failed
Try to flash the phone. If fault persists after flashing, probably D301 faulty. Change D301 (keep in mind procedure
as described on page 14!) with µBGA soldering machine and try to update once more.
CCONT Interface failed
Probably faulty CCONT N201 or broken solderings under it.
Replace CCONT with µBGA soldering machine and run the energy management calibration.
If not ok after reworking the CCONT, MAD or PCB faulty in all probability.
COBBA parallel/serial failed
Check VBB 2.8 VDC at C119, VCOBBA 2.8 VDC at C116/117 and VREF 1.5 VDC at C109,
also check COBBACLK at J317:
Figure 8-1
Probably COBBA N100 faulty or broken solderings under it – change COBBA and retune RX/TX-values.
If fault remains after changing COBBA, MAD or PCB faulty.
DSP Alive Test failed
In most of all DSP alive selftest failures MAD is faulty, which is not changeable.
EEPROM sec/tune checksum failed
Use WinTesla to check if phone data like IMEI, product-code or PSN are corrupted.
If phone data is ok, try to reset the phone. If phone data is not ok or fault remains
after reset, change D301 as described on page 14.
© NMP 2002
CONFIDENTIAL
NHM—2/5/6
3410
Date 20.11.2002
Checked by:
Customer Care E&A
27 (44)
Repairhints
Version 4.0 Approved
Approved by:
SCCE Training Group
Advertisement
