Nokia rh41, 2260 Troubleshooting Instruction
CCS Technical Documentation
RH-41 Series Transceivers
Troubleshooting Instructions
Issue 2 09/2003 Confidential Nokia Corporation
RH-41
Troubleshooting Instructions CCS Technical Documentation
Page 2 Nokia Corporation Confidential Issue 2 09/2003
RH-41
CCS Technical Documentation Troubleshooting Instructions
Contents
Page No
Transceiver Troubleshooting ......................................................................................... 5
Baseband Troubleshooting ..........................................................................................5
General testing........................................................................................................... 5
Troubleshooting ........................................................................................................ 5
Power up faults.......................................................................................................... 6
Flash Programming does not work.......................................................................... 10
Charging .................................................................................................................. 12
Audio failures.......................................................................................................... 13
Accessory detection................................................................................................. 16
Sleep Clock ............................................................................................................. 17
Display/Keyboard lights do not work ..................................................................... 18
Display does not work............................................................................................. 19
Buzzer does not work.............................................................................................. 20
Keyboard does not work ......................................................................................... 20
Receiver Troubleshooting ..........................................................................................20
General instructions for RX troubleshooting .......................................................... 20
Path of the received signal ...................................................................................... 20
Fault-finding charts for receiver chain .................................................................... 21
Transmitter Troubleshooting .....................................................................................26
General instructions for TX troubleshooting .......................................................... 26
Path of the transmitted signall................................................................................. 27
Fault-finding charts for the transmitter ................................................................... 27
Synthesizer Troubleshooting .....................................................................................33
19.44 MHz reference oscillator............................................................................... 33
RX VHF .................................................................................................................. 34
Fault-finding chart for RX VHF VCO ................................................................... 35
TX VHF................................................................................................................... 35
UHF Synthesizer ..................................................................................................... 36
Issue 2 09/2003 Nokia Corporation Confidential Page 3
RH-41
Troubleshooting Instructions CCS Technical Documentation
Page 4 Nokia Corporation Confidential Issue 2 09/2003
RH-41
CCS Technical Documentation Troubleshooting Instructions
Transceiver Troubleshooting
First, 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 testing
The phone has three different modes for testing and/or repairing the phone. The modes
can be selected with suitable resistors connected to BSI- and BTEMP- lines as illustrated
in the following table:
Mode BSI-resistor BTEMP resistor Remarks
Local mode 0 - 1k 0 - 1k
Test mode >1k 0 - 1k
Normal mode 68k 47k Recommended for baseband
testing. Same as local 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:
1 Pressing the power key.
2 Connecting the local/test mode resistors to the bsi/btemp lines and connecting
the battery voltage to the phone.
3 Connecting a charger.
4 Phone’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.
Note: The phone’s ESN has to re-written to the UEM, if the UEM is replaced. This can be done only in
Central Service.
Issue 2 09/2003 Nokia Corporation Confidential Page 5
RH-41
Troubleshooting Instructions CCS Technical Documentation
The BB troubleshooting instructions consist of the following topics:
1Power up
2 Flash programming
3Audio
• Earpiece
• Microphone
4 Charging
5 Accessory detection
6 Sleep clock
7 User interface
Power up faults
Power up sequence
1 The UEM acts as a HW master during start up
• Display
• Lights
• Buzzer
• Keyboard
• Vbatt limits: 2.1V for internal state machine, 3V triggering whole startup
• Regulator sequencing
• HW "core" regulators "on": Vio, Vcore, VR3, Vflash1
These regulators supply the processors, memory, chip interfaces and clock source in RF
• Reset releasing delay
• Supply voltages stabilize to their UEM HW default values
• RFCLK grows to full swing
• The core is ready to run but waiting for the PURX release
Page 6 Nokia Corporation Confidential Issue 2 09/2003
RH-41
CCS Technical Documentation Troubleshooting Instructions
• Reset releasing
• The UPP releases the SLEEPX up to the "non sleep" -state to prevent the
UEM switching the regulators "OFF"
2 MCU starts running the Bootsrap Code
• Written in stone/ UPP internal ROM
• The program checks if there is any reason for the FDL mode (Flash Down Load)
• If there is an executable code in FLASH and there is no reason for FDL, the MCU
starts running the MCU program from FLASH.
3 MCU runs the FLASH MCU code
• The phone initialization, user interfaces, internal blocks etc.
• Core regulator voltage setting for required DSP speed
• Initializes the DSP and concerning HW
• Releases DSP reset -> DSP starts running
Note: In the following figure, the RF_Clk frequency appears to be lower than 19.44 MHz because of a
too low oscilloscope sampling frequency (2kS/s).
Figure 1: Power up sequence
Issue 2 09/2003 Nokia Corporation Confidential Page 7
RH-41
Troubleshooting Instructions CCS Technical Documentation
1 Power key pressed
• After 20ms UEM enters RESET MODE if VBAT>Vmstr+
• VFLASH1, Vana, Vcore, Vio and VR3 goes high.
• 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.
3 Software running
• Default value for Vcore is 1.5 volts when the software is running.
• 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.
Page 8 Nokia Corporation Confidential Issue 2 09/2003
RH-41
CCS Technical Documentation Troubleshooting Instructions
OK
Check
19.44MHz RF
clock from C420
FAIL
Try to start phone to
test or local mode
FAIL
Measure Vflash1,
Vana, Vio, Vcore, VR3
when pwr key pressed
VANA and VR3 missing
Check G790 (missing
or misaligned)
Check C420
OK
FAIL
OK
OK
Check the power key
OK
R206, R207,
C220, C240
Check R202, R206,
R207, C220, C240
OK
Check X101
FAIL
Measure VBAT from
C261
OK
Check that purx goes
up to 1.8V
OK
Measure J406 (it
should be 1.08MHz)
OK
Change
UPP (D400)
Check 19.44MHz from
G790
FAIL
FAIL
Programming OK but phone doesn't start
Reflash phone
FAIL
Check R792, C792,
C793
OKOK
Change G790Change N801
Change UEM
(D200)
Programming fails
Go to Flash
Failure flowchart
OK
Figure 2: Fault tree, phone does not power up
Issue 2 09/2003 Nokia Corporation Confidential Page 9
RH-41
Troubleshooting Instructions CCS Technical Documentation
Flash Programming does not work
Flash programming procedure
1 The 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).
2 When the phone is powered (VBAT>3V), the MBUS and FBUSTX lines are pulled
up internally by the phone.
3 The prommer sends a command to the UEM, using FBUSRX, to enter the Flash
mode. During the sending of this command, the prommer keeps the BSI line high
and MBUS is used as a serial clock.
4 When the Flash mode command is acknowledged, UEM enters the Flash mode
and releases reset (PURX) to MCU.
5 After reset is released, UPP checks if there is a request for the Bootstrap code
(that resides in the UPP ROM).
6 The 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).
7 If 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 fixed Bootstrap code – although it is not able to run the FLASH
code. UPP then sends an UPP-ID to the prommer via the FBUSTX line.
8 After the prommer has received the UPP ID, it sends 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.
9 Prommer then sends the Algorithm Code 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 speed up flashing.
Page 10 Nokia Corporation Confidential Issue 2 09/2003
RH-41
CCS Technical Documentation Troubleshooting Instructions
11 The FLASH Program includes a package of MCU and DSP software and all default
parameters for the phone. The tuning values will be added/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 following table indicates that the item under consideration is
being used for the first time in the flashing sequence.
Error Description Not 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 Taco)
VR3
Rfclock(VCTCXO->Taco->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
C107 "The Phone MCU can not start Secondary
code correctly."
A204 "The flash manufacturer and device IDs in
the existing Algorithm files do not match
with the IDs received from the target
phone."
A387 "The MCU ID in the MCUSW.” UPP
C601 "The prommer has detected that Vpp voltage
level has dropped below the limit"
UPP
Flash
Signals between UPP-Flash
Vpp from prommer - >Flash
Issue 2 09/2003 Nokia Corporation Confidential Page 11
Loading...