this document in any form withou t the prior written permis sion of Nokia is prohibited.
Nokia, Nokia Connecting People, X and Y are trademarks or reg istered trademarks of Nokia Corporation. Other product and company names mentioned
herein may be trademarks or tradenames of their respective owners.
Nokia operates a policy of continuous development. Noki a reserves the right
to make changes and improvements t o any of the pro duct s descri bed in thi s
document without prior notice.
Under no circumstances shall Nokia be responsible for any loss of data or income or any special, inc idental, consequenti al or indirect d amages howsoever caused.
The contents of this doc ument are provided "as is". Except as required by applicable law, no warranties of any kind, either express or implied, including,
but not limited to, the implied warr anties of merchantability and fitness for a
particular purpose, ar e made in relation to the accura cy, reliability or conten ts
of this document. Nokia reserves the right to revise this document or withdraw it at any time without prior notice.
The availability of particular products may vary by region.
IMPORTANT
This document is intended for use by qualified service personne l
only.
Please refer to the product’s user guide for instructions re l ating
to operation, care and maintenance including important safety
information. Note also the following:
Warnings:
1. IF THE DEVICE CAN BE INSTALLED IN A VEHICLE, 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 NECESS ARY, CONSULT THE VE HICLE
DEALER/MANUFACTURER TO DETERMINE THE IMMUNITY
OF VEHICLE ELECTRONIC SYSTEMS TO RF ENERGY.
Nokia Customer Care
Warnings and Cautions
2. THE product MUST NOT BE OPERATED IN AREAS LIKE LY TO
CONTAIN POTENTIALLY EXPLOSIVE ATMOSPHERES EG
PETROL STATIONS (SERVICE STATIONS), BLASTING
AREAS ETC.
3. OPERATION OF ANY RADIO TRANSMITTING EQUIPMENT,
INCLUDING CELLULAR TELEPHONES, MAY INTERFERE
WITH THE FUNCTIONALITY OF INADEQUATELY PROTECTED MEDICAL DEVICES. CONSULT A PHYSICIAN OR
THE MANUFACTURER OF THE MEDICAL DEVICE IF YOU
HA VE AN Y QUESTIONS. OTHER ELECTRONIC EQU IPMENT
MAY ALSO BE SUBJEC T TO INTERFERENCE.
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 anti-static wrist strap is worn.
3. Ensure solder, wire, or foreign matter does not enter the telephone as damage may result.
4. Use only approved components as specified in the parts list.
5. Ensure all components, modules screws and insulators are correctly re-fitted after s ervicing and alignmen t. Ensure all cables
and wires are repositioned correctly.
QUALIFIED SERVICE
Only qualified personnel may install or repair phone equipment.
ACCESSORIES AND BATTERIES
Use only approved accessories and batteries. Do not connect incompatible
products.
CONNECTING TO OTHER DEVICES
When connecting to any other device, read its user’ s guide for detailed safety
instructions. Do not connect incompatible products.
ESD protection
Nokia requires that product ser v ice points have sufficient
ESD protection (against static electricity) when servicing
products.
Any product of which the covers are removed must be han dled with ESD protection. The SIM card can be replaced
without ESD protection if the product is otherwise ready for
use.
To replace the covers ESD protection must be applied.
All electronic parts of the product are susceptible to ESD.
Resistors, too, can be damaged by static electricity discharge.
All ESD sensitive parts must be packed in metallized protective bags during ship ping and handl ing out side any ESD
Protected Area (EPA).
Every repair action involving opening the product or handling the product components must be done under ESD
protection.
ESD protected spare part packages MUST NOT be
opened/closed out of an ESD Protected Area.
For more information and local requirements about ESD
protection and ESD Protected Area, contact your local
Nokia After Market Services representative.
Note that a new battery's full performance is achieved only aft er two or three
complete charge and discharge cycles!
The battery can be charged and discharged hundreds of times but it will
eventually wear out. When th e operatin g ti me (talk- time and s tandby time) i s
noticeably shorter than normal, it is time to buy a new battery.
Use only batteries approved by the phone manufacturer and recharge the
battery only with the chargers approved by the manufacturer. Unplug the
charger when not in use. Do not leave the batte ry connected to a charger for
longer than a week, since overchargi ng may shorten its lifetime. If l eft unused
a fully charged battery will discharge itself over time.
Temperature extremes can affect the ability of your battery to charge.
For good operation times with Ni-Cd/NiMh batteries, discharge the battery
from time to time by leaving the produc t switched on unt il it t urns itsel f off (or
by using the battery discharge facility of any approved accessory available
for the product). Do not atte mpt to discharge t he batt ery by any othe r means.
Use the battery only for its intended purpose.
Never use any charger or battery which is damaged.
Do not short-circuit the ba ttery. Acc idental short-ci rcuiting can occur when a
metallic object (coin, clip or pen) ca uses direct connection of t he + and - terminals of the battery ( metal strips on the battery) fo r example when you c arry
a spare battery in your pocket or purse. Short- circuiting the terminals may
damage the battery or the connecting object.
Leaving the battery in hot or cold places, such as in a closed car in summer
or winter conditions, will reduce the capacity and lifetime of the battery. Always try to keep the battery between 15°C and 25°C (59°F and 77°F). A
phone with a hot or c old battery may temporari ly not work, even when th e battery is fully charged. Batt eries' per formance is par ticular ly limit ed in temperatures well below freezing.
Do not dispose of batteries in a fire!
Dispose of batteries according to l ocal regulations (e.g. recycling). Do not dis-
The product is a product of superior design and cr aftsmanship and should be
treated with care. The suggestions belo w will help you to fulfil any warranty
obligations and to enjoy this product for many years.
Keep the phone and all its parts and accessories out of the reach of small
children.
Keep the phone dry. Precipitation, humidity and all types of liquids or moisture can contain minerals that will corrode electronic circuits.
Do not use or store the phone in dusty, dirty areas. Its moving parts can be
damaged.
Do not store the phone in hot areas. High temperatur es can shorten t he lif e
of electronic devices, damage batteries, and warp or melt certain plastics.
Do not store the phone in cold areas. When it warms up (to its normal temperature), moisture can form inside, which may damage electronic circuit
boards.
Do not drop, knock or shake the phone. Rough handling can break internal
circuit boards.
Do not use harsh chemicals, cl eaning solvents, or strong detergents to clean
the phone.
Do not paint the phone. Paint can clog the moving parts and prevent proper
operation.
Use only the supplied or an approved replacement antenna. Unauthorised
antennas, modifications or att achments could damage the phone and may violate regulations governing radio devices.
All of the above sug gestions apply equal ly to the produc t, battery, ch arger or
any accessory.
Our policy is of continuous devel opment; 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
MOBILE PHONES Business Group should be notified in writing.
Please state:
Title of the Document + Issue Number/Date of publication
Latest Amendment Number (if applicabl e)
Page(s) and/or Figure(s) in error
Please se nd to :
NOKIA CORPORATION
Nokia Mobile Phones Business Group
Nokia Customer Care
1- General Information
2- Parts Lists and Exploded View
3- Service So ftware Instru ctions
4- Service Tools
5- Disassembly/Reassembly Instr uctions
6- BB Description and Troubleshooting
7- RF Description and Troubleshooting
8- Schematics
Module List .................................................................................................................................................... 4
Assembly Parts ............................................................................................................................................. 3
Parts List............................................................................................................................................................ 5
Software Support Bundles ........................................................................................................................ 5
Starting a Phoenix Session ....................................................................................................................... 5
Initial Session with Phoenix .................................................................................................................. 6
Scanning for a Product ........................................................................................................................... 7
Using Components ................................................................................................................................... 7
Using Profiles ............................................................................................................................................. 8
Uninstalling a Phoenix Version ............................................................................................................. 8
Diego User’s Guide ......................................................................................................................................... 9
Installing Diego ..........................................................................................................................................10
Software Support Bundles ......................................................................................................................11
Starting a Diego Session .........................................................................................................................11
Initial Session with Diego and FLS-4S Dongle .............................................................................. 11
Scanning for a Product ........................................................................................................................ 13
Using Components ................................................................................................................................ 13
Uninstalling Diego .....................................................................................................................................14
Uninstalling a Diego Version .............................................................................................................. 14
This section briefly describes how to install Phoenix and includes some basic information
on how to use the program. More detailed information can be found in the Phoenix Help
files. Each feature in Phoenix has its own Help file, which can be activated while running
Phoenix. To activate a Help file while Phoenix is running, press the F1 key or the specific
feature’s Help button.
General Setup Procedure
Initial installation of Phoenix requires the complete Phoenix installation package, which
is around 30 MB. Because of its large size, Phoenix is provided on a CD rather than on a
3.5" floppy or as a download. To install Phoenix, follow the steps as outlined in the
material that comes with the CD.
Note: You MUST have a Nokia dongle installed on the computer prior to beginning the software
installation.
The Phoenix software is packaged into an executable bundle that allows you to doubleclick the executable to access the automatic installation program. Standard installation
(i.e., selecting all of the default choices) is highly recommended. You may do a custom
installation and place Phoenix into a special location on your hard drive, but this is only
recommended for experienced users.
The installation process requires that you reboot the computer after installing the
software. Phoenix is not usable until a reboot is completed. After the reboot, the Phoenix
icon appears on the desktop. Double-click this icon to start the program.
Before installing the software, verify the following:
•The dongle is attached to the parallel port for PKD version dongles, or an FLS-4
version dongle is attached on either the parallel port or the USB port (if the
computer supports USB).
•Ensure that if the computer supports administrator rights (typically on Windows
NT and Windows 2000 installations) that access is enabled for the user
performing the Phoenix installation.
•If a previous version of Phoenix has been installed, it may be necessary to first
properly remove that program prior to installing the new version. If installation is
performed, be sure to reboot the computer prior to continuing. See the
"Uninstalling Phoenix" section for instructions on how to uninstall.
2. Navigate to the CD-ROM drive, and double-click the Phoenix software package.
3. Follow the on-screen prompts.
4. Reboot the computer when the installation is complete.
Software Support Bundles
The Phoenix installation is auto-executable. You must obtain Software Support Bundles
to load software upgrade files to customer-specific phone models. These bundles are
created by Nokia Customer Care and made available by Nokia After Market Services
(AMS) on the Partners Web Page http://americas.partners.nokia.com. This web page is
password-controlled; if you have not registered as a user, contact Nokia Central Service
in Melbourne, Florida.
Similar to the Phoenix installation, these Software Support Bundles are InstallShield
executable packages. Double-click on the package and it will install automatically.
No rebooting of the computer is required.
Starting a Phoenix Session
When referring to Phoenix, Product is the cellular phone attached to the computer. More
specifically, it is the particular type of phone.
Connection is the type of cable used to attach the phone and the port on the computer
where it is attached. Refer to the Service Tools chapter for additional information.
The first time Phoenix is used, certain connection configurations must be made.
Subsequent uses will rely on these selections and they will not need to be made again.
3. Choose one of the following on the Select mode dialog box:
•Select Wizard, which allows Phoenix to auto-detect your connection
configuration.
•Select Manual, which allows you to manually select options to create the
connection.
4. Once a connection is defined, make sure that the connection you want to use
appears at the top of the list. If it does not, use the up and down arrows on the
Manage Connections dialog box to move the connection to the top, and click
Apply.
5. Close the window when you are finished.
You can now proceed with the normal initiation of a session by selecting a
product or scanning for a product.
Scanning for a Product
Many features of this program are product-specific. Therefore it is necessary to configure
Phoenix for the product on which you will be working at the beginning of the session.
Choose Scan Product from the drop-down menu list and Phoenix automatically scans
for the product and selects the necessary configurations. The status bar at the bottom
indicates if the product was found and its type.
Using Components
When working with Phoenix, tasks are generally managed by specific software
components. From the menu, select the desired component or task to be performed.
Figure 5: Select Mode dialog box
“Opening a component” is defined as opening a tool window within Phoenix. When this
window is opened, Phoenix also opens a toolbar for it and adds component-specific
menu items in the Window menu.
Phoenix’s Profile feature allows product, connection, and currently open components to
be stored into permanent storage by creating a profile file with a name of your choice
followed by an .nmp file extension for later retrieval.
Saved profiles makes it easy to configure Phoenix into a desired configuration with
favorite windows already opened and ready to go.
Opening and saving profiles is done via the Open Profile and Save Profile options in the
File menu.
Profiles are stored into a disk file with user-defined names. As a result, there can be
multiple profiles for different repeated tasks or user preferences.
Uninstalling Phoenix
As mentioned in the "Installing Phoenix" section, it may be necessary or desirable to
remove Phoenix. Care must be taken to follow this procedure. Failure to remove the
program properly causes misconfiguration of the computer’s registry.
Uninstalling a Phoenix Version
Use the following steps to uninstall a version of Phoenix:
1. Navigate to the computer's Control Panel, which is accessible from the Start
button or by double-clicking the “My Computer” desktop icon.
2. Double-click the “Add/Remove Programs” icon.
3. Select the Phoenix version that you want to remove, and click Add/Remove.
4. Click OK to begin the removal process.
5. Follow the on-screen instructions.
6. When the removal is complete, reboot the computer.
Diego was designed as an easy to use, minimal decision-making application for point of
sale locations. This section briefly describes how to install Diego and includes some basic
information about how to use the program. See the Diego Help files for more detailed
information. To activate a Help file while Diego is running, either press the F1 key or click
the specific feature's Help button.
General Setup Procedure
Initial installation of Diego requires the complete Diego installation package, which is
around 18 MB. Because of its large size, Diego is provided on a CD rather than on a 3.5"
floppy or as a download. To install Diego, follow the steps as outlined in the material that
comes with the CD.
Note: You MUST have a Nokia dongle installed on the computer prior to beginning the software
installation.
The Diego software is packaged into an executable bundle that allows you to doubleclick the executable to access the automatic installation program. Standard installation
(i.e., selecting all of the default choices) is highly recommended. You may do a custom
installation and place Diego into a special location on your hard drive, but this is only
recommended for experienced users.
The installation process requires that you reboot the computer after installing the
software. Diego is not usable until a reboot is completed. After the reboot, the Diego icon
appears on the desktop. Double-click this Icon to start the program.
Be sure to check the following items before installing Diego:
•An FLS-4 version dongle is attached to either the parallel port or the USB port
(if the computer supports USB). An FLS-2D may be used; however, the FLS-2D
does not support the new generation DCT-4 version phones.
•If the computer supports administrator rights (typically on NT and Windows 2000
installations), ensure that access is enabled for the user performing the
installation.
•If a previous version of Diego has been installed, remove that program prior to
installing the new version. Once removal is performed, be sure to reboot the
computer prior to continuing. (See the "Uninstalling Diego" section for
instructions on how to uninstall.)
Installing
Use the following steps to install Diego:
1. Insert the CD into the computer.
2. Navigate to the CD-ROM drive, and double-click the Diego software package.
3. Follow the on-screen prompts.
4. Reboot the computer when the installation is complete.
The Diego installation program is a generic software load. In order to support specific
custom transceivers (customer-specific phone models), it is necessary to also obtain
Software Support Bundles. These bundles are created by Nokia Customer Care and made
available by Nokia After Market Services (AMS) for the Americas region on the Partners
Web Page (http://americas.partners.nokia.com). This Web page is password-controlled.
Contact Nokia Central Service in Melbourne, Florida, if you have not registered as a user.
Similar to the Diego installation, these bundles are executables. Double-click the
executable file to automatically install the bundle. No re-booting of the computer is
necessary.
Starting a Diego Session
When referring to Diego, product is the cellular phone attached to the computer. More
specifically, product refers to the particular type of phone.
Connection is the type of cable used to attach the phone to the computer, and also
includes the port to which the cable is attached.
The first time Diego is used, certain connection configurations must be made.
Subsequent uses rely on these selections and do not need to be made again.
Initial Session with Diego and FLS-4S Dongle
You must configure the Virtual Port Connection in Diego the first time Diego is launched.
The FLS-4 dongle uses virtual port, which eliminates the need to use the serial port (as
the FLS-2D does). During the installation of the FLS-4 drivers (included in the Diego
installation package), a virtual COM port is set to the next available COM port number.
This port selection must be put into the Diego configuration.
1. Select “My Computer” desktop icon, and click the “FLS Virtual Port” icon.
Figure 8: The FLS Virtual Port icon
2. Make note of the value in the Virtual Port Assignment field (COM 2 in this
example).
3. Click Add to create a new connection.
Figure 9: diego - Phone Settings dialog box
Note: COM port settings can only be entered or changed if the auto-connection feature of
Diego is disabled (as indicated in the grey Status box). To disable the auto-connect feature,
click on this icon in the toolbar.
6. Proceed with the normal initiation of a session.
Scanning for a Product
Many features of this program are product specific. Therefore, it is necessary to
configure Diego at the beginning of the session for the product on which you will be
working.
Scanning of the product can be done manually or automatically. The default setting is
automatic scanning. In automatic scan mode, Diego automatically scans for a product at
a periodic rate. The default rate is every 5 seconds, but you can change to a different
frequency in the setup menu.
You can change the scan setting to manual scanning on the General tab on the Settings
dialog box. To manually scan for a product, click the “Connect” icon.
Using Components
When working with Diego, tasks are generally managed by specific software
components. Select the desired component or "task" to be performed from the icons
displayed in the pane on the left side of the window.
Figure 10: Serial Port tab on the Settings dialog box
Opening a component refers to opening a tool window within Diego. When this window
is opened, Diego also opens a task box, which includes component-specific menu items.
Model 3125 Service Tools ............................................................................................................................ 3
Flashing, Testing, and Tuning ................................................................................................................... 7
High-volume Flashing and EM Calibration ....................................................................................... 7
Covers-Off Troubleshooting Using Service Jig (MJ-23)................................................................. 8
Automated Tuning and Alignment....................................................................................................... 9
JBV-1 Docking StationMJF-17 Docking Station Adapter
07702980774282
The JBV-1 docking station connects flash prommers
and works in conjunction with the MJF-17 for flashing,
testing, an dan EM calibration. The docking station can
be powered by the FPS-8 or an external power supply.
Note: You must update your JBV-1s to the latest
firmware to properly operate Lynx handsets.
Note: Use the PCS-1 DC power and XRS-4 cables when
using the FPS-8 prommer box.
The MJF-17 works in conjunction with the JBV-1 docking station and the FPS-8 prommer to enable tuning,
testing, and flashing. The docking station adapter supports the LYNX batter interface, which does not require
BTEMP, and also has a built-in R-UIM card reader.
FPS-8 Flash PrommerRJ-32 Rework Jig
00803210770757
The FPS-8 flash prommer is used for high-volume
flashing at authorized service centers.
Note: You must register the FPS-8 in order to activate it.
(See the sales package for registration information.)
The rework jig is a PWB component that allows
de-soldering and soldering.
The XCS-4 Service Cable is a general purpose cable for
flashing and communicating with the phone. This is
used to connect the FPS-8 box to the docking station
adapter or the service jig.
CA-5S is used for EM calibration with the JBV-1. This
cable replaces the SCB-3 DC Cable (0730114).
Note: Required by the MJF-28 Docking Station Adapter.
PCS-1 Power CablePKD-1 SW Security Device
07300120750018
The Power Cable PCS-1 is used to connect the service
tools (JBV-1, MJS-82) to an external power supply.
SW security device (PKD-1) is a hardware device that,
when connected to the parallel (LPT) port of the PC,
enables the use of service software. It is not possible to
use the service software without the dongle. 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. Also, do not
connect the PKD-1 to the serial port. You may damage
your PKD-1.
Note: PKD-1RD dongles are restricted to Nokai Product
Creation Centers only.
The Point of Sale (POS) flash is a low-cost software
upgrade tool. (This requires the XCS-1 cable [0730218],
NOT included.)
FBUS cable DAU-9T provides a connection from the
serial port of the computer to the system connector of
the phone. This cable is used for diagnostic purposes.
Note: This cable does not support M-BUS.
DAU-9S (MBUS) CableCA-25RS RF Test Cable
07301080730316
This is a general-purpose cable to support F / MBUS
communication between a Mod-10 device and a PC.
This cable is used for diagnostic purposes.
The CA-25RS test cable is used for CDMA RF engine
testing and tuning. This cable snaps directly on the
phone’s RF connector and converts the output to an
SMA connector. Removal of the A-cover is required.
This cable is used for bottom connector flashing using
FLS-4S or FLC-20.
The MJ-23 secures and allows easy access to critical
areas of the handset’s PWB during troubleshooting. It
supports regulated and unregulated DC input voltages,
Local and Normal mode operations, a R-UIM card
reader, and a second DC input for VCHAR used in EM
tuning. The Jig also supports simultaneous RF connections to the CDMA engine. A completely functional UI
module is also provided on the right side.
Note: The MJ-23 is for use with the CA25RS RF cable.
SS-13 Tuning Docking Station (CDMA)XRS-6 RF Cable
00808520730231
SS-13 is used with the MJF-x/DA-x flashing adapters
(shown with MJF-17).
The XRS-6 cable is used to connect service tools to RF
measuring equipment.
Tightened performance specifications require more precise equipment and methods for
testing and alignment. Manual tuning can not provide accurate results for the 3125,
which means that this test has to be automated.
These setups are intended to be with the Phoenix Service Software. Both manual testing
and automated tuning are permitted with Phoenix Service Software.
High-volume Flashing and EM Calibration
5
1
3
2
ItemNameTypeCode
1Flash prommer box (sales pack)
Included in FPS-8 sales pack:
Service cable
Serial cable
Power supply
3125 (RH-61)
Disassembly/Reassembly InstructionsNokia Customer Care
scratches.
9. Remove the earpiece. Note the guiding pin when re-assembling.
10. The shielding is attached with hooks at its backside. To remove the shielding from
the B-cover, first expand the B-cover, then push the shielding upwards.
Nokia Customer CareAntenna Description and Troubleshooting
Introduction
This troubleshooting guide addresses potential failures that can affect antenna
performance of the 3125 phone, and discusses methods for correction of these failures.
Internal Antenna Missing
IHF speaker
pins
If no internal antenna is installed, the antenna gain will degrade by more than 25 dB.
Figure 1: Front view of the 3125
RF feed
Figure 2: 3125 chassis assembly
Ground pin
RF shield
•If the internal antenna is missing, install a new one.
•If the radiator looks obviously damaged, replace the internal antenna.
3125 (RH-61)
Antenna Description and TroubleshootingNokia Customer Care
Damaged RF Feed Pin or Ground Pin
RF pinGround pin
Spacer
IHF speaker
pins
Figure 3: Bottom (left) and top (right) views of the 3125 internal antenna
If the RF feed does not touch the PWB, then the antenna gain will degrade by more than
25dB. If the ground pin does not touch the PWB, then the antenna gain may degrade
from 5—10 dB.
Replace the internal antenna if any of the following situations apply:
IHF speaker
port
Ground pinRF pin
Radiator
•Either the RF feed pin or ground pin are broken or bent such that either pin will
not touch the PWB
•The springs for the RF or ground pin appear damaged
•The slot in the radiator has a significantly different shape
•Obvious damage to the radiator (e.g., dents, corrosion)
•The pin is stuck or has excessive friction in the plastic tube/guiding feature
resulting in the spring not working properly
•Either of the IHF speaker pins is damaged or if the IHF speaker is not functioning
Wrong Internal Antenna Installed
Figure 4: Top views of the 3100 (RH-19) (left) and 3125 (RH-61) (right) antennas
The 3100 and 3125 antennas are similar in appearance. The important visual difference
in the antennas is the slot pattern. Also, the 3125 antenna is thicker than the 3100
antenna and has a spacer on its back side.
•If the wrong antenna is installed, install the correct one.
Nokia Customer CareAntenna Description and Troubleshooting
Figure 5: Bottom views of the 3100 (RH-19) (left) and 3125 (RH-61) (right) antennas
Obstructed RF Feed or Ground Pads for Internal Antenna, or IHF Speaker Pads
Pad for ground pinPad for RF pin
IHF speaker pads
Figure 6: PWB layout of RF feed and ground pads and IHF speaker pads
If the RF feed pad is obstructed, removed, or covered, the RF feed pin will not touch the
PWB and the antenna gain will degrade by more than 25 dB. If the ground pad is
obstructed, removed, or covered, the ground pin will not touch the PWB and the antenna
gain may degrade by about 5—10 dB.
•If corrosion is present or the pad is missing, replace the PWB and the phone.
•If either pad is obstructed or covered, clear or clean the pad.
If the Internal Hands Free (IHF) speaker pads are obstructed, removed, or covered, the IHF
speaker will not produce sound.
•If corrosion is present or the pad is missing, replace the PWB and the phone.
•If either pad is obstructed or covered, clear or clean the pad.
3125 (RH-61)
Antenna Description and TroubleshootingNokia Customer Care
Grounding of Display Frame
Ungrounded screw
Grounded screw
RF connector
Grounded screw
Figure 7: Display assembly
Ungrounded screw
Note that the display frame is grounded to the PWB through the two top screws. The
grounding of the display frame impacts the radiation performance of the phone.
•If the screws are loose, then tighten them.
•If the screw bosses are stripped, replace the chassis.
•If the screws are missing, install new ones.
The middle screws should not touch the metal in the LCD frame, the metal shield over
the keypad, the PWB, or the RF shield. When driving in these screws, be sure to drive
them in straight. If the screws are driven in at an angle, it is much more likely that the
screws will touch the PWB or the RF shield. If the screws touch, the antenna
performance could change by about 1dB.
The RUIM card flap needs to be grounded to the RF shield with a conductive sticker. The
shape and location of the conductive sticker is shown in Figure 8. If the sticker is
damaged or missing, then the radiated sensitivity could be reduced by 4—8 dB.
•If the conductive sticker is missing or ripped, replace the sticker.
RF Connector Failure
The RF connector could fail by not connecting the RF input to the RF output of the RF
connector. If this happens, then the antenna gain will degrade by about 25 dB. Check for
this by testing for DC conductivity between the RF input and RF output of the RF
connector. Note the DC conductivity test must be done without any cable attached to
the RF connector. Because the RF connector is also a switch, the RF output will be
disconnected from the RF input when a cable is inserted into the RF connector. When a
cable is inserted, the RF input is connected to the RF connector.
•RF input — connector to duplexer
•RF output — connects to antenna pad through vias
•RF connector — connects to coaxial cable
If the RF input is not connected properly to the RF output, replace the RF connector.
Baseband and RF Architecture ................................................................................................................ 4
Power Up and Reset ....................................................................................................................................4
Power Up - Power Key............................................................................................................................. 7
Power Up - Charger ................................................................................................................................. 7
Power Up - RTC Alarm............................................................................................................................. 8
Power Off ....................................................................................................................................................... 8
Power Consumption and Operation Modes ......................................................................................... 8
Power Distribution ...................................................................................................................................... 9
Clock Distribution ......................................................................................................................................11
Charge Control ....................................................................................................................................... 22
Accessory Detection Through ACI..................................................................................................... 27
SIM CAR .......................................................................................................................................................29
Test Points ...................................................................................................................................................30
Nokia Customer CareBB Description and Troubleshooting
Baseband Overview
The baseband module of the 3125 transceiver is a CDMA single-band engine.
The cellular baseband consists of three ASICs: Universal Energy Management (UEM),
Universal Phone Processor (UPP), and a 128/16 megabit combo FLASH.
The baseband architecture supports a power-saving function called sleep mode. This
sleep mode shuts off the VCTCXO, which is used as system clock source for both RF and
baseband. During the sleep mode, the system runs from a 32 kHz crystal and all the RF
regulators (VR1A, VR1B, VR2, … VR7) are off. The sleep time is determined by network
parameters. Sleep mode is entered when both the MCU and the DSP are in standby mode
and the normal VCTCXO clock is switched off. The phone is waken up by a timer running
from this 32 kHz clock supply. The period of the sleep/wake up cycle (slotted cycle) is
1.28N seconds, where N= 0, 1, 2, depending on the slot cycle index.
The 3125 supports standard Nokia 2-wire and 3-wire chargers (ACP-x and LCH-x).
However, the 3-wire chargers are treated as 2-wire chargers. The PWM control signal for
controlling the 3-wire charger is ignored. The UEM ASIC and the EM SW control
charging.
A BL-5C Li-ion battery is used as main power source, which has nominal capacity
of 850 mAh.
Nokia Customer CareBB Description and Troubleshooting
After receiving one of the above signals, the UEM counts a 20 ms delay and then enters
reset mode. The watchdog starts, and if the battery voltage is greater than Vcoff+, a
200 ms delay is started to allow references (etc.) to settle. After this delay elapses, the
VFLASH1 regulator is enabled. Then, 500 us later, the VR3, VANA, VIO, and VCORE are
enabled. Finally, the Power Up Reset (PURX) line is held low for 20 ms. This reset (PURX)
is sent to the UPP. Resets are generated for the MCU and the DSP.
During this reset phase, the UEM forces the VCTCXO regulator on regardless of the status
of the sleep control input signal to the UEM. The FLSRSTx from the UPP is used to reset
the flash during power up and to put the flash in power down during sleep. All baseband
regulators are switched on at the UEM power on, except for the SIM regulator and the
Vflash2. The Vsim and Vflash2 are not used. The UEM internal watchdogs are running
during the UEM reset state with the longest watchdog time selected. If the watchdog
expires, the UEM returns to the power-off state. The UEM watchdogs are internally
acknowledged at the rising edge of the PURX signal to always give the same watchdog
response time to the MCU.
The following timing diagram represents the UEM start-up sequence from reset to
power-on mode.
Nokia Customer CareBB Description and Troubleshooting
Power Up - Power Key
When the Power key is pressed, the UEM enters the power-up sequence. Pressing the
Power key causes the PWRONX pin on the UEM to be grounded. The UEM PWRONX
signal is not part of the keypad matrix. The Power key is only connected to the UEM. This
means that when pressing the power key an interrupt is generated to the UPP that starts
the MCU. The MCU then reads the UEM interrupt register and notices that it is a
PWRONX interrupt. The MCU reads the status of the PWRONX signal using the UEM
control bus (CBUS). If the PWRONX signal stays low for a certain time the MCU accepts
this as a valid power-on state and continues with the SW initialization of the baseband.
If the Power key does not indicate a valid power-on situation, the MCU powers off the
baseband.
Power Up - Charger
In order to be able to detect and start charging in cases where the main battery is fully
discharged (empty) and the UEM has no supply (NO_SUPPLY or BACKUP mode of UEM),
charging is controlled by start-up charging circuitry.
Whenever the VBAT level is detected to be below the master reset threshold (V
charging is controlled by start-up charging circuitry. Connecting a charger forces the
VCHAR input to rise above the charger detection threshold (VCH
start-up charging is initiated. The UEM generates 100 mA constant output current from
the connected charger’s output voltage. The battery’s voltage rises at it charges, and
when the VBAT voltage level is detected to be higher than the master reset threshold
limit (V
), the start-up charge is terminated.
MSTR+
Monitoring the VBAT voltage level is done by a charge control block (CHACON). A
MSTRX=‘1’ output reset signal (internal to the UEM) is given to the UEM’s RESET block
when the VBAT>V
If the VBAT is detected to fall below V
cancelled. It will restart if a new rising edge on the VCHAR input is detected (VCHAR
rising above VCH
Power Up - RTC Alarm
If the phone is in power-off mode when an RTC alarm occurs, the wake-up procedure
occurs. After the baseband is powered on, an interrupt is given to the MCU. When an RTC
alarm occurs during active mode, the interrupt is generated to the MCU.
Power Off
MSTR+
DET+
and the UEM enters into the reset sequence.
during start-up charging, charging is
MSTR
).
) and by detection,
DET+
The baseband switches to power-off mode if any of following occurs:
•Power key is pressed
•Battery voltage is too low (VBATT < 3.2 V)
•Watchdog timer register expires
The UEM controls the power-down procedure.
Power Consumption and Operation Modes
In POWER-OFF mode, the power (VBAT) is supplied to the UEM, buzzer, vibra, LED, PA,
and PA drivers. During this mode, the current consumption is approximately 35 uA.
In Sleep Mode, both processors (MCU and DSP) are in stand-by mode. The phone enters
sleep mode only when both processors make this request. When the SLEEPX signal is
detected low by the UEM, the phone enters SLEEP mode. The VIO and VFLASH1
regulators are put into low quiescent current mode, VCORE enters LDO mode, and the
VANA and VFLASH2 regulators are disabled. All RF regulators are disabled during SLEEP
mode. When the SLEEPX signal is detected high by the UEM, the phone enters ACTIVE
mode and all functions are activated.
Sleep mode is exited either by the expiration of a sleep clock counter in the UEM or by
some external interrupt (generated by a charger connection, key press, headset
connection, etc.).
In sleep mode, the VCTCXO is shut down and the 32 kHz sleep clock oscillator is used as
a reference clock for the baseband.
Nokia Customer CareBB Description and Troubleshooting
The average current consumption of the phone in sleep mode can vary depending mainly
on the SW state (e.g., slot cycle 0, 1, or 2) and if the phone is working on IS95 or IS2000
for CDMA. However, the average consumption is about 6 mA in slot cycle 0 on IS95.
In the Active Mode, the phone is in normal operation, scanning for channels, listening to
a base station, transmitting and processing information. There are several sub-states in
the active mode depending on the present state of the phone, such as burst reception,
burst transmission, if the DSP is working, etc.
In active mode, SW controls the VR1A and VR1B UEM RF regulators, which can be
enabled or disabled. VSIM can be enabled or disabled and its output voltage can be
programmed to be 1.8 V or 3.3 V. VR2 and VR4—VR7 can be enabled, disabled, or forced
into low quiescent current mode. VR3 is always enabled in active mode and disabled
during sleep mode and cannot be controlled by SW in the same way as the other
regulators. VR3 will only turn off if both processors request to be in sleep mode.
Charging Mode can be performed in parallel with any other operating mode. A BSI
resistor inside the battery pack indicates the battery type/size. The resistor value
corresponds to a specific battery capacity. This capacity value is related to the battery
technology.
The battery voltage, temperature, size, and charging current are measured by the UEM
and the charging software running in the UPP controls it.
The charging control circuitry (CHACON) inside the UEM controls the charging current
delivered from the charger to the battery and phone. The battery voltage rise is limited
by turning the UEM switch off when the battery voltage has reached 4.2 V. The charging
current is monitored by measuring the voltage drop across a 220 mOhm resistor.
Power Distribution
In normal operation, the baseband is powered from the phone‘s battery. The battery
consists of one Lithium-Ion cell capacity of 850 mAh and some safety and protection
circuits to prevent harm to the battery.
The UEM ASIC controls the power distribution to the whole phone through the BB and RF
regulators excluding the power amplifier (PA), which has a continuous power rail directly
from the battery. The battery feeds power directly to the following parts of the system:
•UEM
•PA
•Buzzer
•Vibra
•Display
•Keyboard lights
The heart of the power distribution to the phone is the power control block inside the
UEM. It includes all the voltage regulators and feeds the power to the whole system. The
UEM handles hardware power-up functions so the regulators are not powered and the
power up reset (PURX) is not released if the battery voltage is less than 3 V.
The baseband is powered from five different UEM regulators.
Table 1: Baseband Regulators
Regulator
VCORE300
VIO1501.8Enabled always except during power-off mode
VFLASH1702.78Enabled always except during power-off mode
VFLASH2402.78Enabled only when data cable is connected
VANA802.78Enabled only when the system is awake (Off
VSIM253.0Enabled only when SIM card is used
Maximum
Current (mA)
400
Vout (V)Notes
1.5
1.35
Output voltage selectable 1.0V/1.3V.
Power up default value is 1.35V.
during sleep and power off-modes)
Table 2 includes the UEM regulators for the RF.
Table 2: RF Regulators
Regulator
VR1A104.75Enabled when cell transmitter is on
Maximum
Current (mA)
Vout (V)Notes
VR1B104.75Enabled when the transmitter is on
VR21002.78Enabled when the transmitter is on
VR3202.78Enabled when SleepX is high
VR4502.78Enabled when the receiver is on
VR5502.78Enabled when the receiver is on
VR6502.78Enabled when the transmitter is on
VR7452.78Enabled when the receiver is on
The charge pump that is used by VR1A is constructed around the UEM. The charge pump
works with the Cbus (1.2 MHz) oscillator and gives a 4.75 V regulated output voltage to
the RF.
Nokia Customer CareBB Description and Troubleshooting
Clock Distribution
RFClk (19.2 MHz Analog)
The main clock signal for the baseband is generated from the voltage and temperature
controlled crystal oscillator VCTCXO (G500). This 19.2 MHz clock signal is generated at
the RF and is fed to Yoda pin 18 (TCXO_IN) at C711. Yoda then converts the analog sine
waveform to a digital waveform with a swing voltage of 0 tot 1.8 V and sends it to the
UPP from pin 16 at Yoda (19.2 Out) to the UPP pin M5 (RFCLK).
Figure 4: Waveform of the 19.2 MHz clock (VCTCXO) going to the Yoda ASIC
A 1.2 MHz clock signal is used for CBUS, which is used by the MCU to transfer data
between the UEM and UPP.
DBUS Clk Interface
A 9.6 MHz clock signal is used for DBUS, which is used by the DSP to transfer data
between the UEM and UPP.
Figure 7: Cbus Data Transfer
Figure 8: Dbus data transferring
The system clock is stopped during sleep mode by disabling the VCTCXO power supply
(VR3) from the UEM regulator output by turning off the controlled output signal SleepX
from the UPP.
When the system enters sleep mode or power off mode, the external 32 KHz crystal
provides a reference to the UEM RTC circuit to turn on the phone during power off or
sleep mode.
Figure 10: 32 kHz analog waveform at 32 KHz crystal input
Flash Programming
Connections to Baseband
The flash programming equipment is connected to the baseband using test pads for
galvanic connection. The test pads are allocated in such a way that they can be accessed
when the phone is assembled. The flash programming interface uses the VPP, FBUSTX,
FBUSRX, MBUS, and BSI connections for the connection to the baseband. The connection
is through the UEM, which means that the logic levels corresponding to 2.7 V. Power is
supplied using the battery contacts.
Baseband Power Up
The baseband power is controlled by the flash prommer in production and in
reprogramming situations. The baseband powers up by applying supply voltage to the
battery terminals. Once the baseband is powered, flash programming indication begins
(see the following "Flash Programming Indication" section).
Flash Programming Indication
Flash programming is indicated to the UPP using the MBUSRX signal between the UPP
and UEM. The MBUS signal from the baseband to the flash prommer is used as a clock
for the synchronous communication. The flash prommer keeps the MBUS line low during
UPP boot to indicate that the flash prommer is connected. If the UPP MBUSRX signal is
low on UPP, the MCU enters flash programming mode. In order to avoid accidental entry
to the flash-programming mode, the MCU waits for a specified time to get input data
from the flash prommer. If the timer expires without any data being received, the MCU
Nokia Customer CareBB Description and Troubleshooting
continues the boot sequence. The MBUS signal from the UEM to the external connection
is used as a clock during flash programming. This means that the flash-programming
clock is supplied to the UPP on the MBUSRX signal.
The flash prommer indicates flash programming/reprogramming to the UEM by writing
an 8-bit password to the UEM. The data is transmitted on the FBUSRX line and the UEM
clocks the data on the FBUSRX line into a shift register. When the 8 bits have been
shifted in the register, the flash prommer generates a falling edge on the BSI line. This
loads the shift register content in the UEM into a compare register. If the 8 bits in the
compare register matches with the default value preset in the UEM, the flash prommer
pulls the MBUS signal to UEM low in order to indicate to the MCU that the flash
prommer is connected. The UEM reset state machine performs a reset to the system,
PURX low, for 20 ms. The UEM flash programming mode is valid until the MCU sets a bit
in the UEM register that indicates the end of flash programming. Setting this bit also
clears the compare register in the UEM, which was loaded at the falling edge of the BSI
signal. The UEM watchdogs are disabled during the flash programming mode. Setting the
bit indicating the end of flash programming enables and resets the UEM watchdog timer
to its default value. Clearing the flash programming bit also causes the UEM to generate
a reset to the UPP.
Flashing
The BSI signal is used to load the value into the compare register. In order to avoid
spurious loading of the register, the BSI signal is gated during UEM master reset and
during power on when PURX is active. The BSI signal should not change states during
normal operation unless the battery is extracted. In this case, the BSI signal will be
pulled high. Note that a falling edge is required to load the compare register.
Flash programming is done through the VPP, FBUSTX, FBUSRX, MBUS, and BSI signals.
When the phone enters the flash programming mode, the prommer indicates to the UEM
that flash programming will take place by writing an 8-bit password to the UEM. The
prommer sets the BSI value to “1” and then uses FBUSRX for writing and MBUS for
clocking. The BSI is then set back to “0”.
The MCU uses the FBUSTX signal to indicates to the prommer that it has been noticed.
After this, it reports the UPP type ID and is ready to receive the secondary boot code to
its internal SRAM.
Figure 11: Flashing starts by BSI being pulled up and password being sent to UEM
This boot code asks the MCU to report the phone’s configuration information to the
prommer, including the flash device type. The prommer can then select and send
algorithm code to the MCU SRAM (and SRAM/Flash self-tests can be executed).
Nokia Customer CareBB Description and Troubleshooting
FLASH_3
CH1 = PURX
CH2 = MBUS
CH3 = FBUSTX
CH4 = FBUSRX
Measure points
Produc tion test pa ttern
(J396)
Data transfer has
started (Fbus_Rx)
Figure 13: Flashing, continued 2
Flash Programming Error Codes
The following characteristics apply to the information in Table 3.
•Error codes can be seen from the test results or from Phoenix's flash-tool.
•Underlined information means that the connection under consideration is being
used for the first time.
Table 3: Flash Programming Error 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."
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.
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->Prommer
Nokia Customer CareBB Description and Troubleshooting
Charging Operation
Battery
The 3125 uses a Lithium-Ion cell battery with a capacity of 850 mAh. A resistor reading
inside the battery pack on the BSI line indicates the battery size. An NTC resistor close to
the SIM connector measures the phone’s temperature on the BTEMP line.
Temperature and capacity information are needed for charge control. These resistors are
connected to the BSI pins on the UEM. The phone has 100KΏ pull-up resistors for these
lines so that they can be read by A/D inputs in the phone.
Figure 14: BL-5C battery pack pin order
Charging Circuitry
The UEM ASIC controls charging depending on the charger being used and the battery
size. External components are needed for EMC, reverse polarity, and transient protection
of the input to the baseband module. The charger connection is through the system
connector interface. The 3125 baseband is designed to support DCT3 chargers from an
electrical point of view. Both 2- and 3-wire type chargers are supported. For the 3-wire
charger, the control line is not supported and not connected to the baseband ASICs.
Connecting a charger creates voltage on the VCHAR input of the UEM. Charging starts
when the UEM detects the VCHAR input voltage level above 2 V (VCHdet+ threshold).
The VCHARDET signal is generated to indicate the presence of the charger for the SW.
The EM SW controls the charger identification/acceptance.
The charger recognition is initiated when the EM SW receives a ”charger connected”
interrupt. The algorithm basically consists of the following three steps:
1. Check that the charger output (voltage and current) is within safety limits
2. Identify the charger as a 2- or 3-wire charger
3. Check that the charger is within the charger window (voltage and current)
If the charger is accepted and identified, the appropriate charging algorithm is initiated.
X102
1
Charge Control
In active mode, charging is controlled by the UEM’s digital part. Charging voltage and
current monitoring is used to limit charging into safe area. For this reason, the UEM has
the following programmable charge cut-off limits:
•VBATLim1=3.6 V (Default)
•VBATLim2L=5.0 V
•VBATLim2H=5.25 V
VBATLim1, 2L, 2H are designed with hystereses. When the voltage rises above VBATLim1,
2L, 2H+ charging is stopped by turning the charging switch off. No change is done in
operational mode. After the voltage has decreased below VBATLim-, charging restarts.
F100
1.5A
L1002
________
42R/100MHz
Figure 16: Charging circuit
V100
"VCHARIN"
C106
1n0
0
2
CHARGER(4:0)
There are two PWM frequencies in use depending on the type of the charger. A 2-wire
charger uses a 1 Hz, while a 3-wire charger uses a 32Hz. The duty cycle range is 0% to
100%. The maximum charging current is limited to 1.2 A.
Nokia Customer CareBB Description and Troubleshooting
Audio
The audio control and processing in the 3125 is provided by the UEM, which contains the
audio codec, and the UPP, which contains the MCU and DSP blocks. These blocks handle
and process the audio data signals.
The baseband supports three microphone inputs and two earpiece outputs. The
microphone inputs are MIC1, MIC2, and MIC3. MIC1 input is used for the phone's
internal microphone; MIC2 input is used for headsets (HDB-4). MIC3 is not used. Every
microphone input can have either a differential or single-ended AC connection to UEM
circuit. In 3125 (RH-61), the internal microphone (MIC1) and external microphone
(MIC2) for Pop-PortTM accessory detection are both differential. The microphone signals
from different sources are connected to separate inputs at the UEM. Inputs for the
microphone signals are differential types. Also, MICBIAS1 is used for MIC1 and
MICBIAS2 is used for MIC2.
Display and Keyboard
The 3125 uses LEDs for the color LCD and keypad illumination. There are two LEDs for the
LCD and four LEDs for the keypad. KLIGHT is the signal used to drive the LED driver for
the LCD and keyboard. This signal turns on the LED driver. The interface uses a 9-bit data
transfer and is quite similar to the DCT3 type interface, except the Command/Data
information is transferred together with the data.
The 3125 supports Pop-Port and Universal Headset accessories, differential and singleended, respectively. Detection of the Pop-Port accessories is done through the ACI signal
where the Universal Headset is detected on GenIO (12).
Figure 19: Pop-Port connector pin out
The pin out on the Pop-Port connector is as follows:
•Charger
•Charger GND
•ACI
•Vout
•USB Vbus
•USB D+ / Fbus Rx
•USB D- / Fbus Tx
•Data GND
•XMic N
•XMic P
•HSear N
•HSear P
•HSear R N
•HSear R P
You can perform the following in Pop-Port accessories:
•Charging
•Accessory detection
•FBUS communication
•USB communication
•Fully differential audio interface for mono- and stereo outputs
Nokia Customer CareBB Description and Troubleshooting
Charging
Charging through Pop-Port is accomplished in the same manner as through the charger
connector. Pin 1 of the Pop-Port is physically connected to the charger connector. When
the phone is connected to a desktop charger (e.g., DCV-15), it charges in the same
manner as it does with the charger connector.
Figure 20 shows the actual charging sequence. The channels on the diagram are:
•CH1 = Charging current across the .22 Ohm (R200) resistor on UEMK
•CH2 = Charger voltage measure at V100
•CH3 = Battery voltage measure at R200
•CH4 = PURX
Figure 20: Charging sequence
In Channel 4, PURX is released, which indicates when the phone operation goes from
RESET mode to POWER ON mode.