Troub l esh oot ing InstructionsPAMS Technica l Do cum en tation
Transceiver T roubleshooting
The first thing to do when you are encountered with a problem is to carry out a thorough
visual check of the module. Make sure that:
•there are no mechanical damages
•the solder joints are OK
Note: Before changing anything, ALL SUPPLY VOLTAGES AND THE SYSTEM
CLOCK / SLEEP CLOCK should be checked.
Baseband Troubleshooting
General about testing
The phone has three different modes for testing and/or r epairing the phone. The modes
can be selected with suitable resistors connected to BSI- and BTEMP- lines as illustrated
in the table below:
Table 1: Phone operating mode
ModeBSI-resistorBTEMP resisto rRemarks
Normal68k47k
Local560_
(<1k_)
Test> 1k560_ (<1k_)Recommended for baseband testing. Same as local
Whatever
mode, but making a phone call is possible.
If the corresponding resistors are connected, the MCU software automatically enters into
the local or test mode when the supply voltage is connected to the phone.
The power can be switched on by:
1Pressing the power key.
2Connecting the local/test mode resistors to the bsi/bt emp lines and connecting
the battery voltage to the phone.
3Connecting a charger.
4Phone’s internal functions (Real time clock alarm)
In the local and test mode, the baseband can be controlled through MBUS or FBUS (FBUS
is recommended) connections using Phoenix service software.
Troubleshooting
Note: Most of the baseband repair actions require removing the baseband shield.
The shield must not be removed unless separately authorized by the program.
•VCTCXO enabled by VR3 -> RFClk 19.44 MHz running.
2Purx released
•Purx released by UEM, UEMINT goes high for 100 ms, SleepX goes high and
UEM starts feeding SleepClk (32 KHz) to UPP.
Note: The sleepclock starts running in the crystal circuitry (B200) immediately when
the battery voltage is supplied.
3Software running
•Default value for Vcore is 1.5 volts and, if the software is running, Vcore will
rise to 1.8 volts.
Issue 1 10/01ãNokia CorporationPage 7
NPW-1
Troub l esh oot ing InstructionsPAMS Technica l Do cum en tation
•Cbus (1.08MHz) clock starts running.
Phone does not start up normally or does not stay on
Note: In case of power up faults, it is not possible to force the phone on by disabling
the watchdog. Instead, measurements should be taken immediately when the
power key is pressed or when the battery voltage is connected to the phone
(local/test mode).
The easiest way to check if the software is running when the phone takes an abnormal
amount of current is to measure the cbusclk and Vcore.
The Dbus clock (programmable 9.72MHz) is not automatically visible in the test and local
modes.
Troub l esh oot ing InstructionsPAMS Technica l Do cum en tation
Flash Programming does not work
Flash programming procedure
1The phone communicates with the prommer via the production test pattern,
using the following signals:
•FBUSTX(serial data to phone)
•FBUSRX(serial data from phone)
•MBUS(serial clock for FBUSRX)
•VPP(External flashing voltage for speed up flashing)
•The BSI line is also used when initializing flashing (battery connector).
2When the phone is powered (VBAT>3V), the MBUS and FBUSTX lines a re pulled
up internally by the phone.
3The prommer sends a command to the UEM, using FBUSRX, to enter the Flash-
mode. During the sending of this co mmand, the prommer keeps the BSI line high
and MBUS is used as a serial clock.
4When the Flash-mode command is acknowledged, UEM enters the Flash-mode
and releases reset (PURX) to MCU.
5After reset is released, UPP checks if there is a request for the Bootstrap code
(that resides in the UPP ROM).
6The request for Bootstrap is the MBUS pulled down by the prommer (if the boot-
strap is not requested, the bootstrap code jumps to FLASH SW).
7If the Bootstrap code is requested, UPP enters the Flash-mode and sets FbusTX to
'0' as an acknowledgement to the prommer. This is an indication that UPP can
run, at least, the fixe d Bootstra p c ode – although it is not abl e to r un t he FLASH
code. UPP then sends an UPP-ID to the prommer via the FBUSTX line.
8After the prommer has received the UPP-ID, it send s a corresponding Secondary
Boot Code to the phone via FBUSRX. The Secondary Boot Code, when run in UPP,
requests UPP to send information to the prommer about the flash type and other
HW-related parameters about the device to be flashed.
9Prommer then sends the Algorithm C ode corresponding to the HW parameters,
and this algorithm, when run in UPP, takes over handling the MCUSW transfer to
Flash.
10 12 volts can be supplied to Vpp (by the prommer) to speedup flashing .
11 The FLASH Program includes a package of MCU and DSP software and all default
parameters for the phone. The tuning values will be adde d/rewritten during the
Flash/Alignment phase.
Flash programming error codes
The various error codes can be seen from the "FPS-8 Flash" in Phoenix.
The underlined text in the table be low means t hat t he it em unde r consider ati on is bei ng
used for the first time in the flashing sequence.
Table 2: Table 2. Flash pr ogr am min g er ror codes.
ErrorDescriptionNot working properly
C101"The Phone does not set FbusTx line high
after the startup."
C102"The Phone does not set FbusTx line low
after the line has been high. The Prommer
generates this error also when the Phone
is not connected to the Prommer."
C103"Boot serial line fail."Mbus from Prommer->UEM->UPP(MbusRx)(SA0)
C104"MCU ID message sending failed in the
Phone."
C105"The Phone has not received Secondary
boot codes length bytes correctly."
C106"The Phone has not received Secondary
code bytes correctly."
Vbatt
Vflash1
Vcore
VIO
BSI and FbusRX from prommer to UEM.
FbusTx from UPP->UEM->Prommer(SA0)
PURX(also to Safari)
VR3
Rfclock(VCTCXO->Safari->UPP)
Mbus from Prommer->UEM->UPP(MbusRx)(SA1)
FbusTx from UPP->UEM->Prommer(SA1)
FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
FbusTx from UPP->UEM->Prommer
Mbus from Prommer->UEM->UPP(MbusRx)
FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
Mbus from Prommer->UEM->UPP(MbusRx)
FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
C10 7"The Phone MCU can not start Secondary
code correctly."
A204"The flash manuf acturer and device IDs in
the existing Algorithm files do not match
with the IDs received from the target
phone."
A387"The MC U ID in the MCUSW. ”UPP
C601"The prommer has detected that Vpp volt-
age level has dropped below the limit"
UPP
Flash
Signals between UPP-Flash
Vpp from prommer - >Flash
Issue 1 10/01ãNokia CorporationPage 11
NPW-1
Troub l esh oot ing InstructionsPAMS Technica l Do cum en tation
C383
C583
C683
C384
C584
C684
C585
C685
C586
C686
Charging
Note: The charging voltage and current can be checked by connecting the phone to
"The Prommer has not received Phone
acknowledge to the message."
(C383-during algorithm download to tar-
get phone)
(C583-during erasing)
(C683-during programming)
"The Phone has generated NAK signal dur-
ing data block transfer."
(C384-during algorithm download to tar-
get phone)
(C584-during erasing)
(C684-during programming)
Data block handling timeout"
(C585-during erasing)
(C685-during programming)
"The status response from the Phone
informs about fail."
(C586-during erasing)
(C686-during programming)
Flash
UPP
Signals between UPP-Flash
Flash
UPP
Signals between UPP-Flash
Flash
UPP
Signals between UPP-Flash
Flash
the service software and reading the ad- converter values of the vchar and
ichar.
If charging fails when the ACP-9 or the LCH-9 is used, and works with ACP-7, ACP-8 and
LCH-8, check that the charge control pin of the system connector is connected to the
ground.
Page 12ãNokia CorporationIssue 1 10/01
Loading...
+ 28 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.