Issue 1 Copyright 2003 Nokia Corporation. Confidential. All Rights Reserved
Customer Care Solutions
Technical Documentation
Amendment Record Sheet
Amendment NoDateInserted ByComments
05/2003J FraserIssue 1
Issue 1 Copyright 2003 Nokia Corporation. Confidential. All Rights Reserved
Customer Care Solutions
Technical Documentation
Nokia 3560 (RH-14) Cellular Phones
Service Manual – Overall Manual Contents
Service Manual comprising
Nokia 3560 (RH-14) Transceiver booklet comprising
Foreword
General
Parts
Service Software Instructions
Service Tools
Disassembly/Assembly
Troubleshooting
System Module
Schematics
Issue 1 Copyright 2003 Nokia Corporation. Confidential. All Rights Reserved
This document is intended for use by qualified service personnel only.
Company Policy
Our policy is of continuous development; details of all technical modifications will be
included with service bulletins.
While every endeavour has been made to ensure the accuracy of this document, some
errors may exist. If any errors are found by the reader, Nokia Corporation should be notified in writing.
Please state:
Customer Care Solutions
Technical Documentation
IMPORTANT
Title of the Document + Issue Number/Date of publication
Latest Amendment Number (if applicable)
Page(s) and/or Figure(s) in error
Please send to: Nokia Corporation
CCS Technical Documentation
PO Box 86
FIN-24101 SALO
Finland
Issue 1 Copyright 2003 Nokia Corporation. Confidential. All Rights Reserved
Customer Care Solutions
Technical Documentation
Warnings and Cautions
Please refer to the phone's user guide for instructions relating to operation, care and
maintenance including important safety information. Note also the following:
Warnings:
1. CARE MUST BE TAKEN ON INSTALLATION IN VEHICLES FITTED WITH
ELECTRONIC ENGINE MANAGEMENT SYSTEMS AND ANTI-SKID BRAKING
SYSTEMS. UNDER CERTAIN FAULT CONDITIONS, EMITTED RF ENERGY CAN
AFFECT THEIR OPERATION. IF NECESSARY, CONSULT THE VEHICLE DEALER/
MANUFACTURER TO DETERMINE THE IMMUNITY OF VEHICLE ELECTRONIC
SYSTEMS TO RF ENERGY.
2. THE HANDPORTABLE TELEPHONE MUST NOT BE OPERATED IN AREAS LIKELY
TO CONTAIN POTENTIALLY EXPLOSIVE ATMOSPHERES EG PETROL STATIONS
(SERVICE STATIONS), BLASTING AREAS ETC.
3. OPERATION OF ANY RADIO TRANSMITTING EQUIPMENT, INCLUDING
Cautions:
1. Servicing and alignment must be undertaken by qualified personnel only.
2. Ensure all work is carried out at an anti-static workstation and that an
3. Ensure solder, wire, or foreign matter does not enter the telephone as
4. Use only approved components as specified in the parts list.
5. Ensure all components, modules screws and insulators are correctly
CELLULAR TELEPHONES, MAY INTERFERE WITH THE FUNCTIONALITY OF
INADEQUATELY PROTECTED MEDICAL DEVICES. CONSULT A PHYSICIAN OR
THE MANUFACTURER OF THE MEDICAL DEVICE IF YOU HAVE ANY
QUESTIONS. OTHER ELECTRONIC EQUIPMENT MAY ALSO BE SUBJECT TO
INTERFERENCE.
anti-static wrist strap is worn.
damage may result.
re-fitted after servicing and alignment. Ensure all cables and wires are
repositioned correctly.
Issue 1 Copyright 2003 Nokia Corporation. Confidential. All Rights Reserved
Customer Care Solutions
Technical Documentation
Issue 1 Copyright 2003 Nokia Corporation. Confidential. All Rights Reserved
RH-14 (Model 3560) phone is a dual-band, dual-mode radio transceiver unit for 800/
1900 MHz Time Division Multiple Access (TDMA) networks. The transceiver consists of
system/RF module, keypad module, LCD module, and assembly parts. The user interface
(UI) consists of normal number, talk, end, scroll key, and two selection keys in the keymat.
The antenna is internal; antenna connection is provided by spring from PWB to antenna.
This section briefly describes how to install the Phoenix software and includes some
basic information on how to use the program. For more detailed information, please refer
to the Phoenix Help files. Each feature in Phoenix has its own Help function, which can
be activated while running the program.
Setting up Phoenix
1Download the latest release. Please contact your regional Customer Care Solu-
tions contact for information on where to download the latest release.
2Install Phoenix by executing the Phoenix installation package and follow the
instructions on the screen.
Note: In some products, the setup may require you to reboot the computer. In either case, the
setup will register Phoenix components. This process can take several minutes.
3Download the latest data packages for the products you will be using.
By default, the program files are stored under C:\Program Files\Nokia\Phoenix
The Phoenix program has been built using component architecture. This means
that the actual program is very small and most of the program’s functionality is
divided into dynamically loaded modules (DLLs).
The data packages will create product-specific directories under the installation
directory.
Service Software InstructionsCCS Technical Documentation
HW requirements for using Phoenix
Table 1: HW requirements for AMS
Minimum HW requirements for AMS
Processor233 Mhz
RAM64 MB
Needed disk space50 - 100 MB
Table 2: Recommended HW for Windows 2000
Minimum HW requirements for Field Test
Processor700 Mhz
RAM512 MB
Needed disk space50 - 100 MB
Installing Phoenix
1Before you start installing the program, check that:
• the dongle is attached to parallel port. Contact your supervisor in
order to obtain a suitable dongle.
• you have administrator rights (Windo w s NT or Windows 2000). This
is required in order to be able to install P hoenix.
2 The installation checks that the latest supported dongle driver version is installed.
The dongle driver is installed if there is no previous installation of the dongle
driver or if the installed dongle driver is older than the latest supported version.
Table 3: Supported Operating Systems
Supported Operating Systems
Windows 95
Windows 98
Windows NT 4.0
Windows 2000
3Reboot your PC before using Phoenix, if you are requested to do so.
2Go to Control Panel and select Add/Remove Programs.
3Select TSS4 Phoenix Release xx.yy.zzz for uninstallation and click Add/Remove.
4Click OK to remove the application.
You may be required to reboot your PC after uninstallation.
Note: If you have different product packages installed, the components are uninstalled only if they are
not included in other product packages.
Data Packages
Data Packages (DP) is a name for a helpful feature in the Phoenix software. This feature
provides a flexible way of distributing and installing Phoenix and its data files.
All product-specific data is separated from the program code and installed separately.
This means that the installation is performed in at least two steps.
Each product has its own DP. The FPS-8 flashing equipment also has its own package.
Starting a session
Concepts
In the Phoenix context, Product means the cellular phone attached to a PC. More specifically, it is a particular type of phone.
Connection means the type of cable used to attach the phone to the port to which the
other end of the cable is attached.
Selecting a connection
The connection defines the cable and the communications port that will be used when
connecting to the phone.
1Active connections are listed in the toolbar’s Connection drop-down menu. You
should make sure that the connection is correct before using the software.
Change it, if necessary.
In case the connection is the wrong one, you need to create a new one.
2Select Settings from the drop-down menu.
3Select Add in the Connection List Dialog and fill in the relevant fields in the Con-
nection setup dialog.
Selecting a product
Many of Phoenix’s features are product-specific. It is, therefore, mandatory to choose the
product you will be working on at the beginning of the session.
Service Software InstructionsCCS Technical Documentation
1Select File - Scan Product (or hold the Ctrl key down and press R). Phoenix will
scan the connected product and load additional menus which are designed for
the product. If the product is not supported, then an error message will be displayed and a different Phoenix data package may be required.
2If you want to manually choose the product or if the phone is dead, select File -
Choose Product. You will be presented with a list of available products.
After the product selection, you will see an additional menu item on the main
menu. If you take a look at the available menu items, you will see that their
number has increased.
Phoenix environment
You can configure the program’s main toolbar and the product or tool-specific options to
your liking.
You can control which toolbars are visible by selecting View and Toolbars from the dropdown menu. The visible toolbars are marked with a check.
The rest of the options are product- or tool-specific. The tool-specific options are set
using the associated toolbar.
Using components
When working with Phoenix, each task generally has its own component that will perform the task. The first thing, therefore, is to open the desired component.
Opening a component means that you open a tool window within Phoenix.
and the Docking Station Adapter (MJF-23)
are needed for Mbus,
Fbus, RF, and audio
connections.
This setup allows connection between flash
prommers. When the
audio box is connected, it has to be
connected to the
phone’s audio connector.
MJF-23Docking Station
Adapter
CPL-1Coupler0770287The coupler has been
JBA-8Audio Box0770320The Audio Box is
0770489The Docking Station
can be powered by
FPS-8 or external
power supply.
NOTE: SEE USER
INSTRUCTIONS FOR
MJF-23 ON PAGE 13.
developed for antenna
go/no go testing.
needed for audio connections. The box
must support DCT4
Janette audios. JBA-8
provides an interconnection between the
phone’s system connector (XEAR, XMIC)
through a fixed audio
cable and audio tester
with a BNC-BNC
coax. Connection to a
PC can be made with
the service battery,
through a DAU-9
cable.
Cable is a modular
cable for flashing
DCT4 products.
PKD-1SW Security Device0750018SW security device
PKD-1 is hardware
device that, when
connected to the parallel (LPT) port of the
PC, enables the use of
the service software.
Without the dongle
present, it is not possible to use the service software. Printers
or other peripheral
devices can be connected to the PC
through the dongle, if
needed.
Caution: Make sure
that you have
switched off the PC
and the printer before
making connections!
Caution: Do not connect the PKD-1 to the
serial port. You may
damage your PKD-1!
SA-12
XRS-11
RF Probe Support
RF Probe
0770623
0770562
The RF Cable is used
for connection to the
RF output of the PWB.
The XRS-11 Cable is
used together with
the SA-12 to ensure a
good connection.
adapter is needed for
proper RF connection.
The adapter allows
galvanic connections
to assembled handset
RF switches. The
adapter permits the
handset to be connected to RF measuring and test
equipment during test
and repair and can be
used with covers on or
off.
Follow these instructions to avoid damage to the adapter or the phone.
Note: Using the adapter in any way other than described here may harm the important
pins and connectors of the adapter. It cannot be used like the FLA-13 for 3520/3560 products.
1Place the adapter in your left hand and the phone in your right hand.
2Align the battery connecter with the battery contacts of the adapter. Gently
press the phone onto the adapter (see following picture).
Follow these instructions to avoid causing any damage to the adapter or the phone.
Note: Using the adapter in any other way may harm the important pins and connectors of
the adapter. It cannot be used like the MJF-2 for 3520/3560 products.
1Place the adapter in your left hand and the phone in your right hand.
3Press down the upper end of the phone with your finger until the battery latch
locks the phone in place.
4To remove the phone from the adapter, push the bottom connector end of the
phone down to the hollow in the adapter. At the same time, push the upper end
of the phone until it detaches from its place. Detach the phone in inverse order
from installation.
Remove the RF Plug from RF connector opening in the antenna.
Remove A-cover
Place thumb under the edge of the A-cover and fingers on top of the A-cover, then pull
gently until it snaps. Once lifted, ensure that the keymat does not fall out of the A-cover.
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
ModeBSI- resistor
Normal68k75k
Local560_(<1k_)Whatever
Test> 1k560_(<1k_)Recommended for baseband testing. Same as local
BTEMP
resistor
Remarks
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/BTEMP lines and connecting
the battery voltage to the phone.
3Connecting a charger.
4Using 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.
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.
•After 20ms, UEM enters RESE T MODE if VBAT>Vmstr+
•VFLASH1, Vana, Vcore, Vio, and VR3 goes high
•VCTCXO enabled by VR3 -> RFClk 19.44 MHz running
2 Purx released
•Purx released by UEM, UEMINT goes high for 100 ms, SleepX
goes high, and SleepClk (32 KHz) starts running.
3Software 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.
1The phone communicates with the prommer via the production test pattern,
using the following signals:
•FBUSTX (serial data to phone)
•FBUSRX (serial da t a from phon e)
•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 are 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 command, 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 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.
8After 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.
9The 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
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.
ErrorDescriptionNot working properly
C101"The Phone does not set FbusTx line high after the star-
tup."
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-
C104"MCU ID message sending failed in the Phone."FbusTx from UPP->UEM->Prommer
C105"The Phone has not received Secondary boot codes
length bytes correctly."
Vflash1
VBatt
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)(SA0)
FbusTx from UPP->UEM->Prommer(SA1)
BSI and FbusRX from prommer to UEM.
>UPP(MbusRx)(SA1)
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
C106"The Phone has not received Secondary code bytes cor-
rectly."
C107"The Phone MCU can not start Secondary code cor-
rectly."
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 mes-
sage, which it has received from the Phone."
Mbus from Prommer->UEM>UPP(MbusRx)
FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
Cx82"The Prommer has detected a wrong ID byte in the mes-
sage, which it has received from the Phone."
A204
Cx83
Cx84
Cx85
Cx87"Wrong MCU ID."RFClock
Startup
for
flashing
"The flash manufacturer and device IDs in the existing
Algorithm files do not match with the IDs received from
the target phone."
"The Prommer has not received Phone acknowledge to
the message."
"The Phone has generated NAK signal during data block
transfer."
"Data block handling timeout"
Required startup for flashingVflash1
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
UPP(Vcore)
VBatt
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.
In case of audio failures, there are three possibilities to check the audio lines.
1Make a phone call against tester and check audios.
2If the earpiece/XMIC fails: Feed a 1Khz signal to the XMIC line and measure the
signal from the earpiece line. The Audio test box JBA-8 is needed. The Audio loop
(Audio test/Ext In Hp Out) must be switched on by the Phoenix service software.
This loop will connect audios only through the UEM. In this case, the UPP is not
used.
If the internal microphone/XEAR fails: Feed the tone to the microphone and measure the signal from the XEAR line. The Audio test box JBA-8 is needed. The
Audio loop (Audio test/Hp In Ext Out) must be switched on by the Phoenix service
software. This loop will connect audios only through the UEM. In this case, the
Check speaker B180 and the following components: N180, R100, R181, R182, R183,
R184, C183, C180, C184, C181, C182, C179, L180, and L181
•No sound: Try using a known good SAL T speaker instead. If there is still
no sound, change the UEM (D200)
•Weak sound: Use the Audio test in Phoenix to set the SALT speaker
parameters (frequency, strength). If it does not affect the sound level,
change the SALT speaker.
Vibra does not work
Check spring connectors and C307 and C308.
•No vibration: Try using a known good vibra instead. If there is still no
vibration, change the UEM (D 200)
•Weak vibration: Use the Vibra test in Phoenix to set the vibra’s parameters (frequency, duty cycle). If it does not affect the magnitude of the
vibration, change the vibra.
Keyboard does not work
Check that there is no dirt between the dome sheet and the PWB. If the keyboard still
does not operate normally, try to use the Keyboard test in Phoenix to see if the pressed
key is identified. If it is not identified, change the UPP (D400).
Receiver Troubleshooting
General Instructions for RX troubleshooting
Start the Phoenix software and use it to start the required RX mode of the mobile phone.
The troubleshooting flowchart is divided into three steps: (1) general checking, (2) local
checking, and (3) RX-chain checking. Always use an RF cable connected from an external
RF connector to the analyzer via (RF power) attenuator. This is important to protect the
analyzer against excessive RF power and to prevent leakage of undesired RF power into
the cellular frequencies.
1Start the Phoenix software and select the TX mode under Testing (AMPS, DAMPS,
or TDMA1900).
2It is useful to select the mid channel (383 for AMPS/DAMPS or 1000 for
TDMA1900) and the power level 2.
Note: Before changing ASICs or filters, all solderings and missing components must be checked visually. After any possible component changes, the phone must be tuned with the Phoenix autotune SW.
Since the same physical signal path is used for both analog and digital modes at the
lower band, there is no need for additional troubleshooting in the digital mode. So if the
digital mode at the lower band is not working properly, start the analog mode troubleshooting.
TDMA1900 (only dualband)
Only EXT RF connector –> 1
st IF needs separate troubleshoot at upper band. After down
conversion (RF –> 135.54 MHz), both lower and upper band use the same signal path.
Figure 11: Fault tree, TDMA1900 troubleshooting
Apply 1960.02 MH z =
ch 1000 -110 dBm
signal to external
RF-connector X900.
Y
Enable loop back BE R
using RF Test UI and
check sensitivity: -110
dBm BER < 3%
N
N
Check UHF Vc (from
C773) V: 2. 2 . ..2.6 V
Y
Y
N
N
TDMA1900
RX-chain is OK
Start synthesizer
troubleshooting
These tests are done
in local mode by usin
RF Test UI.
C101"The Phone does not set FbusTx line high after the star-
tup."
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-
C104"MCU ID message sending failed in the Phone."FbusTx from UPP->UEM->Prommer
C105"The Phone has not received Secondary boot codes
length bytes correctly."
Vflash1
VBatt
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)(SA0)
FbusTx from UPP->UEM->Prommer(SA1)
BSI and FbusRX from prommer to UEM.
>UPP(MbusRx)(SA1)
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