Nokia 3520 Service Manual 7 rh21 trouble

Nokia Customer Care

RH-21 Series Transceivers

Troubleshooting

Issue 2 07/2004  2004 Nokia Corporation. Page 1

Company Confidential

RH-21 Company Confidential Troubleshooting Nokia Customer Care

Page 2  2004 Nokia Corporation. Issue 2 07/2004

Company Confidential RH-21

Nokia Customer Care Troubleshooting

Contents

Page No

Troubleshooting ............................................................................................................. 5

Baseband Troubleshooting ..........................................................................................5

General testing information....................................................................................... 5

Troubleshooting ........................................................................................................ 6

Phone does not start up normally or does not stay on............................................... 8

Flash Programming does not work.......................................................................... 10

Charging .................................................................................................................. 12

Audio failures.......................................................................................................... 13

Accessory detection................................................................................................. 15

Sleep Clock ............................................................................................................. 16

User Interface .......................................................................................................... 18

Receiver Troubleshooting ..........................................................................................20

General Instructions for RX troubleshooting .......................................................... 20

Path of the received signal ...................................................................................... 20

Fault-finding charts for receiver chain .................................................................... 21

Transmitter fault-finding ...........................................................................................29

General instructions for TX troubleshooting .......................................................... 29

Path of the transmitted signal .................................................................................. 29

Fault-finding charts for transmitter ......................................................................... 29

Power control loop .................................................................................................. 32

Synthesizer fault-finding ...........................................................................................35

19.44 MHz reference oscillator............................................................................... 35

RX VHF VCO......................................................................................................... 37

TX VHF VCO ......................................................................................................... 38

UHF Synthesizer ..................................................................................................... 38

Issue 2 07/2004  2004 Nokia Corporation. Page 3

RH-21 Company Confidential Troubleshooting Nokia Customer Care

Page 4  2004 Nokia Corporation. Issue 2 07/2004

Company Confidential RH-21

Nokia Customer Care Troubleshooting

Troubleshooting

The first thing to do when a problem is encountered 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 testing information

There are three different modes for testing and/or repairing the phone. The mode can be selected with suitable resistors connected to BSI- and BTEMP- lines as illustrated in the following table:

Table 1: Phone operating mode

Mode BSI- resistor

Nor-

68k 75k

BTEMP resistor

Remarks

mal

Local 560_(<1k_) Whatever

Test > 1k 560_(<1k_) 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 Using the 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.

Issue 2 07/2004  2004 Nokia Corporation. Page 5

RH-21 Company Confidential Troubleshooting Nokia Customer Care

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.

The baseband troubleshooting instructions include the following topics:

1Power up

2 Flash programming

3Audio

•Earpiece

•Microphone

4 Charging

5 Accessory detection

6 Sleep clock

7 User interface

•Display

•Lights

•MIDI

•Vibra

• Keyboard

Power-up faults

Power-up sequence

1 The UEM acts as a HW master during start up

• 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

Page 6  2004 Nokia Corporation. Issue 2 07/2004

Company Confidential RH-21

Nokia Customer Care Troubleshooting

• 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

• 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 Bootstrap 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.44MHz because of a too low oscilloscope sampling frequency (2kS/s).

Figure 1: Power-up sequence

Issue 2 07/2004  2004 Nokia Corporation. Page 7

RH-21 Company Confidential Troubleshooting Nokia Customer Care

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 SleepClk (32 KHz) starts running.

3 Software running

• Default value for Vcore is 1.5 volts and, if software is running, Vcore will rise to

1.8 volts

• Cbus (1.08MHz) and Dbus clocks start running

Phone does not start up normally or does not stay on

Note: In the 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  2004 Nokia Corporation. Issue 2 07/2004

Company Confidential RH-21

Nokia Customer Care Troubleshooting

Figure 2: Fault tree, phone does not power up

Issue 2 07/2004  2004 Nokia Corporation. Page 9

RH-21 Company Confidential Troubleshooting Nokia Customer Care

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 connec- tor)

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 The prommer then sends the Algorithm Code corresponding to the HW parame-

ters, 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.

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

Page 10  2004 Nokia Corporation. Issue 2 07/2004

Company Confidential RH-21

Nokia Customer Care Troubleshooting

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 means 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."

Vflash1 VBatt BSI and FbusRX from prommer to UEM. FbusTx from UPP->UEM->Prommer(SA0)

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."

PURX(also to Safari) VR3 Rfclock(VCTCXO->Safari->UPP) Mbus from Prommer->UEM>UPP(MbusRx)(SA0) FbusTx from UPP->UEM->Prommer(SA1) BSI and FbusRX from prommer to UEM.

C103 "Boot serial line fail." Mbus from Prommer->UEM-

>UPP(MbusRx)(SA1) FbusRx from Prommer->UEM>UPP FbusTx from UPP->UEM->Prommer

C104 "MCU ID message sending failed in the Phone." FbusTx from UPP->UEM->Prom-

mer

C105 "The Phone has not received Secondary boot

codes length bytes correctly."

Mbus from Prommer->UEM>UPP(MbusRx) FbusRx from Prommer->UEM>UPP FbusTx from UPP->UEM->Prommer

C106 "The Phone has not received Secondary code

bytes correctly."

Mbus from Prommer->UEM>UPP(MbusRx) FbusRx from Prommer->UEM>UPP FbusTx from UPP->UEM->Prommer

Issue 2 07/2004  2004 Nokia Corporation. Page 11

RH-21 Company Confidential Troubleshooting Nokia Customer Care

C107 "The Phone MCU can not start Secondary code

correctly."

C586 "The erasing status response from the Phone

informs about fail."

C686 "The programming status response from the

Phone informs about fail."

Cx81 "The Prommer has detected a checksum error in

the message, which it has received from the Phone."

Cx82 "The Prommer has detected a wrong ID byte in

the message, which it has received from the Phone."

A204

"The flash manufacturer and device IDs in the existing Algorithm files do not match with the IDs received from the target phone."

Cx83

"The Prommer has not received Phone acknowledge to the message."

Cx84

"The Phone has generated NAK signal during data block transfer."

Cx85

"Data block handling timeout"

UPP

Flash

FbusTx from UPP->UEM->Prommer

Flash UPP VIO/VANA? Signals between UPP-Flash Mbus from Prommer->UEM>UPP(MbusRx) FbusRx from Prommer->UEM>UPP FbusTx from UPP->UEM->Prommer

Cx87 "Wrong MCU ID." RFClock

UPP(Vcore)

Startup for

Required startup for flashing Vflash1

VBatt flashing

Charging

Note: The charging voltage and current can be checked by connecting the phone to 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, but 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  2004 Nokia Corporation. Issue 2 07/2004

+ 28 hidden pages