User Guide

CCS Technical Documentation
Company confidential RH-23
Issue 1 03/2004 Nokia Corporation. Page 39
Flash fault
In Table 1 you can see the signals/components related to each flashing error.
When the text is bolded the item is being used first time during the flashing procedure.
Table 1: Most common error messages
Error Description Used signals/components Points to check
C101 The Phone does not
set FlashbusTXD
line high after the
startup.
Vbat, Vcore, VIO, VFLASH1
BSI and FBUSRX from prommer to
UEM
FBUSTX from UPP->UEM-> Prommer
(Stuck at ‘0’)
SLEEPX from UEM to UPP
VBAT from C167
VCore from C208
VIO from C451
VFLASH from R202
BSI pulse at R206 and when flashing starts, FBUSRX
at R101
FBUSTX state at J411(UPP)->R100(UEM)
SLEEPX at J403
C102 The Phone does not
set Flashbus TXD
line low after the
line has been high.
The Prommer gen-
erates this error
also when the
Phone is not con-
nected to the
Prommer.
PURX, VR3
RFCLOCK (VCTCXO->Helgo-> UPP)
MBUS from Prommer->UEM -
>UPP(stuck at ‘1’)
FBUSTX from UPP->UEM-> Prommer
(Stuck at ‘1’)
PURX state transition ’0’ to ’1’ at J402
VR3 at C227 and L511
RFCLOCK at G501 and R420
MBUS pulse train at J410
FBUSTX state at J411(UPP)->R100(UEM)
C103 The Phone MCU
has not received
the first dummy
word correctly
from the Prommer
after the startup.
MBUS from Prommer->UEM->
UPP(Stuck at ‘0’)
FBUSRX from Prommer->UEM-> UPP
FBUSTX from UPP->UEM->Prommer
MBUS pulse train from J410
FBUSRX serial data from J412
FBUSTX state from J411(UPP)->R100(UEM)
C107 "The Phone MCU
can not start Sec-
ondary code cor-
rectly."
UPP
A204 The flash manufac-
turer and device
IDs in the existing
Algorithm files do
not match with the
IDs received from
the target phone.
Combo Flash
Signals between UPP and Combo Flash
Prommer SW
A387 The MCU ID in the
FIASCO_MCU_ID_I
NFO block of the
MCUSW file does
not match with the
ID received from
the target phone.
UPP Prommer SW
C583
C683
The Prommer has
not received Phone
acknowledge to
the message.
Combo Flash and UPP
Signals between UPP and Combo Flash