Service Manual comprising
RH-34 Series Transceiver booklet comprising
Foreword
General
Parts
Service Software Instructions
Service Tools
Disassembly/Assembly
Troubleshooting - Antennas
Troubleshooting - Baseband
Troubleshooting - FM Radio
Troubleshooting - GPS
Troubleshooting - RF (Part 1 and Part 2)
System Module
Schematics
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
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.
The Nokia 6585 (RH-34) offers a CDMA trimode (1900/800 MHz CDMA plus 800 AMPS
engine supporting 1XRTT. The RH-27 features an integrated FM radio, high-speed data
support, IR support, and RUIM.
RH-34 contains a 128 x 128 color display and has changeable display fonts. There is an
internal antenna, GPS (E-911) support, MIDI ringing tones, and an internal vibra.
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 whil 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. This
package, currently around 30 Megabytes in size, is provided on a CD-ROM disk. Because
of this large size, it is not recommended to download the file nor is it practical to provide
it on 3.5-inch floppy disks.
Install Phoenix by following the steps outlined on the material that comes with the disk.
It should be noted that installation of a Nokia dongle on the computer being loaded is
REQUIRED prior to beginning the installation of the software.
The software is packaged into an Installshield executable bundle. When the user doubleclicks on this file, the installation program provides on-screen instructions on how to
proceed. Standard installation, provided by selecting all 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.
It is necessary to reboot the computer after installing the software. The program will not
be usable until a reboot is performed. After reboot, the Phoenix icon is displayed on the
computer desktop. Double-clicking on this icon launches the program.
Service Software InstructionsCCS Technical Documentation
Hardware Requirements for using Phoenix
Minimum Hardware Requirements
Processor233 MHz
RAM164 MB
Disk space needed50-100 MB
Supported Operating
Systems
Windows 95Limited, no USB support
Windows 98
Windows NT 4.0no USB support
Windows 2000Professional version
Notes
Installing Phoenix
Before installing the software, verify:
• 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 section Uninstalling
Phoenix for instructions on how to uninstall.
Installation Directions
• Insert the CD-ROM disk into the computer drive
• Access the drive and double-click on the Phoenix software package found on the CD.
• Follow the on-screen prompts to conclusion.
Note that rebooting the computer may be necessary when completed.
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 CCS and made available by 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. Just double-click on the package and it will auto-install.
No rebooting of the computer is required.
Starting a Phoenix Session
Concepts
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.
Initial Session with Phoenix
It is necessary to create the connection the first time Phoenix is used. Follow these simple steps:
Select Manage Connections… from the “File” drop-down menu.
Service Software InstructionsCCS Technical Documentation
Next click the Add… button to create a new connection.
When the Select Mode dialog box appears, you may then select either Wizard, which will
auto-detect your connection configuration, or Manual, which allows you to manually
select options to create the connection.
Once a connection is defined, make sure that the one to be used is moved to the top of
the list (use the up down arrows on the Manage Connections dialog box. Then click on
the Apply button. Close the window when 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.
Scan Product – Choose Scan Product from the drop-down menu list and Phoenix will
automatically scan for product and select the necessary configurations. The status bar
at the bottom will indicate 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.
“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.
Using Profiles
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 menu commands found in the File drop-down
menu: Open Profile and Save Profile.
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 will cause misconfiguration of the computer’s registry.
Uninstalling Phoenix version
• Access the computer’s “Control Panel” section, selectable from the Start button or the
“My Computer” desktop icon
• Select the “Add/Remove Programs” icon
• Select the Phoenix version to be removed, and click the Add/Remove button
• Click on the OK button to begin the process of removal
Service Software InstructionsCCS Technical Documentation
Diego User’s Guide
Introduction
This section briefly describes how to install Diego and includes some basic information
on how to use the program. More detailed information can be found in the Diego Help
files. Each feature in Diego has its own Help file, which can be activated while running
Diego. To activate a Help file while Diego is running, press the F1 key or the specific feature’s Help button.
Diego is designed to be used by point of sales locations. Ease of use and minimal operator decision-making were key factors in the design. Additionally, this Diego version is
compatible with current-generation phones (DCT3 versions such as 5185i, 5170i, 5180i,
6185i, and 3285) and DCT4 versions such as the 6385.
General Setup Procedure
Initial installation of Diego requires the complete Diego installation package. This package, currently around 18 megabytes in size, is provided on a CD-ROM disk. Because of
this large size, it is not recommended to download the file nor is it practical to provide it
on 3.5-inch floppy disks.
Install Diego by following the steps as outlined on the material that comes with the disk.
It should be noted that installation of a Nokia dongle on the computer being loaded is
REQUIRED prior to beginning the installation of the software.
The software is packaged into an InstallShield executable bundle. When the user double-clicks on this file, the installation program provides on-screen instructions on how to
proceed. Standard installation, provided by selecting all default choices, is highly recommended. You may do a custom installation and place Diego into a special location on
your hard drive; however, this is only recommended for experienced users.
It is necessary to reboot the computer after installing the software. The program is not
usable until a reboot is performed. After reboot, the Diego icon is included on the computer desktop. Double-clicking on this icon launches the program.
• 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.
• 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
installation.
• If a previous version of Diego 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 Uninstalling Diego for
instructions on how to uninstall.
Installing
• Insert the CD-ROM disk into the computer drive.
• Access the drive and double-click on the Diego software package found on the CD.
Service Software InstructionsCCS Technical Documentation
Note that rebooting the computer will be necessary when completed.
Software Support Bundles
The Diego installation is auto-executable. You must obtain Software Support Bundles to
load software upgrade files to customer-specific models.
These bundles are created by CCS and made available by 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 Diego installation, these packages are executable packages. Just doubleclick on the package, and it will auto-install.
No re-booting of the computer is required.
Starting a Diego Session
Concepts
When referring to Diego, 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 more information.
The first time Diego is used, certain connection configurations must be made. Subsequent uses will rely on these selections and they will 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.
Select “My Computer” desktop icon and click on the “FLS Virtual Port” icon.
Make note of the Virtual Port Assignment (COM 2 in this example).
Next select “Add…” to create a new connection.
ote: COM port settings can
only be entered or changed if
the auto-connection feature of
Diego is disable (as indicated
by the grey Status box).
To disable the auto-connect
click on this icon in the tool
bar:
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.
Service Software InstructionsCCS Technical Documentation
Select the Virtual COM port setting. Then press the Apply button.
You can now 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 a 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. This setting can be changed to manual in the “settings” – “general” box. In
automatic mode, Diego will automatically scan for a product at a periodic rate. The scan
rate is defaulted to every 5 seconds, but it can be changed to a different frequency in the
Setup menu.
To manually scan for a product, click on the “Settings” icon as noted above.
Using Components
When working with Diego, tasks are generally managed by specific software components. From the icons displayed on the left side of the screen, select the desired component or task to be performed.
“Opening a component” is defined as opening a tool window within Diego. When this
window is opened, Diego also opens a task box for it, which includes component-specific menu items.
Uninstalling Diego
As mentioned in the Installing Diego section, it may be necessary or desirable to remove
Diego. Care must be taken to follow this procedure. Failure to remove the program
properly will cause misconfiguration of the computer’s registry.
JBV-1 Docking StationDA-12 Docking Station Adapter
07702980770603
The Docking Station and the Docking Station Adapter
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. The Docking
Station can be powered by FPS-8 or external power
supply.
The flash adapter allows FBUS/MBUS connections for
flashing.
JBA-12 Audio BoxCPL-8 GPS/RF Coupler
07705360770475
The JBA-12 is required for audio testing at authorized
service centers.
CPL-8 allows testing of the GPS antenna at AMS locations.
This cable is used with FLS-4S or FLC-20 for bottomconnector flashing.
PKD-1 SW Security Device
0750018
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. 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!
This jig allows phone PWB-level service and troubleshooting for authorized service centers.
Tightened performance specifications require more precise equipment and methods for
testing and alignment. Manual tuning can’t provide accurate results for the RH-34,
which means that this test has to be automated.
These setups are intended to be with with the Phoenix Service Software. Both manual
testing and automated tuning are permitted with Phoenix Service Software.
1Vector Signal AnalyzerAgilentE4406A1Options B78, BAC and BAE
2Signal GeneratorAgilentE4421B1Digital signal generator with
high stability oscillator and high
spectral purity
3Momentum SeriesAgilent8960C1CDMA tester for IS-95, IS-2000,
and AMPS protocols
4Power SupplyKeithlyK23062Programmable with sense wire
5Win2000 PCDell with Pentium III or above,
network card, 256M RAM, 20GB
HD, CD-ROM, etc.
6NI-GPIB InterfaceNIGPIB-USB-A2USB to GPIB adapter (184983G-
01)
7Docking StationNokiaJBV-11Consult your local Nokia After
Market Services office for more
information
8RF SwitchesGreen HillTVi99011Consult your local Nokia After
Market Services office for more
information
Note: A Test Sequence File is required to perform “Auto tune” on this phone. In addition, Phoe nix needs to have the Auto Tune function installed. Consult you local Nokia After Market Services office more information.
GPS Testing Engine
This setup will be used for testing of the GPS Engine at Nokia Authorized Service Centers.
Both Galvanic and Radiated tests will be supported. The GPS Test component in Phoenix
will provide functionality to perform these tests. Refer to the Troubleshooting - GPS section for more details regarding GPS Engine troubleshooting.
This troubleshooting guide addresses potential failures that will affect the antenna performance of the RH-34 phone, and discusses methods for correction of these failures.
Failures and Corrective Measures
Appearance of phone
Figure 1: Front and back views of the RH-34 (6585) phone
Missing internal antenna or antenna radiator
Antenna cap
Figure 2: RH-34 (6585) phone with and without antenna cap
Figure 3: RH-34 (6585) antenna cap with and without radiator
If the antenna cap is missing or there is a cap but it has no radiator, install a new
antenna cap with radiator. If the radiator looks obviously damaged (dents, corrosion) or
the slot in the radiator has a significantly different shape, then install a new antenna cap
with correct radiator.
If no antenna or no radiator is installed, the antenna gain will be degraded by more than
25 dB.
Missing GPS antenna
GPS antenna
Figure 4: Back view of RH-34 (6585) C-cover with GPS antenna assembled
If GPS antenna is missing, install a new GPS antenna. If the GPS antenna looks obviously
damaged, replace the antenna with a new one.
RF feed pin/ground pin, IHF speaker pins in C-cover missing or damaged
IHF speaker
ins
RF ground
in
GPS antenna
ground leg
RF feed
Figure 5: Inside view of the C-cover
Two pogo pins are inserted in the C-cover. One end of the pogo pin (in Figure 4) touches
the antenna, the other end (in Figure 5) touches the pad on the PWB. If either of the
pogo pins is missing, or either of the pogo pins is obviously damaged (stuck in the
C-cover plastic tube, lose the inside spring force), the antenna will lose the contact to
the PWB. Replace the whole C-cover assembly with a correct new one.
If the RF feed doesn't touch the PWB, then the antenna gain will degrade by more than
25 dB. If the ground pin doesn't touch the PW,B then the antenna gain may degrade
about 5 to 10 dB.
If either of the IHF speaker pins is damaged or missing, the speaker will not connect to
PWB. Antenna PCS gain will drop 2 dB. The C-cover assembly should be replaced.
Damaged GPS feed or ground pin
As shown in Figure 5, if either the GPS antenna feed or the ground leg is broken, or bent
such that either pin will not touch the PWB, then the GPS antenna should be replaced
with a new one.
GPS antenna
feed leg
Wrong internal antenna installed
Jacqueline
antenna
Figure 6: Top view of RH-34 (6585) antenna vs. Jacqueline antenna
The RH-34 (6585) antenna and the Jacqueline antenna caps are similar in appearance.
The radiators are totally different.
If the wrong antenna is installed, install the correct one.
Obstructed RF feed and ground pads, GPS feed and ground pads, IHF speaker pads
Internal Feed
ad
Internal
round pad
CDMA RF
connector
GPS RF
connector
GPS Feed
ad
GPS ground
ad
IHF speaker
ads
Figure 7: PWB layout of RF feed/ground pads, GPS feed/ground pads, and IHF speaker pads
If the RF feed pad is obstructed, removed, or covered, then the internal antenna feed
pogo pin will not touch the PWB and then the antenna gain will degrade by more than
25 dB. If the ground pad is obstructed, removed, or covered, then the ground pogo pin
will not touch the PWB and the antenna gain will degrade more than 5dB. If corrosion is
present or the pad is missing, then most likely the PWB and phone needs to be replaced.
If either pad is obstructed or covered, the pad should be cleared and/or cleaned.
If the GPS feed pad is obstructed, removed, or covered, then the GPS antenna feed leg
will not touch the PWB. If the ground pad is obstructed, removed, or covered, then the
ground spring clip will not touch the PWB.
If the Internal Hands Free (IHF) speaker pads are obstructed, removed, or covered, then
the IHF speaker will not produce sound. The antenna PCS gain will be degraded by about
2 dB. If corrosion is present or the pad is missing, then most likely the PWB and phone
needs to be replaced. If either pad is obstructed or covered, the pad should be cleared
and/or cleaned.
CDMA or GPS RF connector failure
CDMA and GPS use the same type of RF connector. The RF connector could fail by not
connecting the RF input to the RF output of the RF connector. If this happens to the
CDMA RF connector, then the antenna gain will degrade by about 25 dB. If this happens
to GPS RF connector, the GPS antenna gain will degrade by about 20 dB. This can be
checked 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. Since 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 not inserted, the RF input is connected to the RF connector. The locations of both RF
connectors are shown in Figure 7.
• CDMA RF input — connects to duplexor
• CDMA RF output — connects to antenna pad through vias
The display shield is connected to the display frame plated area (screw boss area) and
then to the PWB through the two top screws. The grounding of the display shield and
frame will impact the radiation performace of the phone. If the screws are loose, then
tighten them. If the screw bosses are stripped, then the chassis will need to be replaced.
If the screws are missing, install new ones.
If the display frame plated area is cracked or the metal plating has peeled off, then the
gounding of the display shield and frame will not be guaranteed. Replace the frame.
Figure 10: Side view of RH-34 and RH-27 display assembly
RH-27
Display
shield
RH-27 Display
frame plating
Figure 11: Back view of RH-34 and RH-27 display assembly
Display assemblies of RH-34 (6585) and RH-27 (6225) are very similar. However, the
RH-27 display shield is different on the side from the RH-34 shield, as shown in
Figure 10 inside the blue dashed line. Second, the metal plating at the top area of the
RH-27 frame is different from the top of the RH-34 frame, as shown in Figure 11 inside
the blue dashed line. For RH-34 frame, the screw boss area is plated but isolated from
the rest of the frame, and also there is no plating in the area inside the green dashed line
in Figure 11. For the RH-27 frame, the whole top area is fully plated.
If the wrong display shield or frame is installed, replace it with a correct one.
Baseband shield is part of the display assembly. If the baseband shield is missing or is
obviously damaged, the radiated phone performace will be impacted. Install a new baseband shield.
The Baseband module of the RH-34 transceiver is a trimode CDMA dual band engine. The
Baseband architecture is based on the DCT4 Apollo engine.
RH-34 Baseband consists of three main ASIC's: Universal Energy Management (UEM),
Universal Phone Processor (UPP), and a 128-Megabit 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. The phone
awakes by a timer running from this 32 kHz clock. 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 19.2MHz Clk (VCTCXO) is switched off.
RH-34 supports both two and three DCT3 type wire chargers. However, the three-wire
chargers are treated as two-type wire chargers. Charging is controlled by UEM ASIC and
EM SW.
BLD-3 Li-ion battery is used as main power source for RH-34. BLD-3 has nominal capacity of 780 mAh.
Power up and reset is controlled by the UEM ASIC. RH-34 baseband can be powered up
in the following ways:
1By the Power button, which means grounding the PWRONX pin of the UEM
2By connecting the charger to the charger input
3By the RTC Alarm, when the RTC logic has been programmed to give an alarm
After receiving one of the above signals, the UEM counts a 20ms delay and then enters in
reset mode. The watchdog starts up, and if the battery voltage is greater than Vcoff+, a
200ms delay is started to allow references, etc. to settle. After this delay elapses, the
VFLASH1 regulator is enabled. Then, 500us later VR3, VANA, VIO, and VCORE are enabled.
Finally, the PURX (Power Up Reset) line is held low for 20 ms. This reset, PURX, is fed to
the baseband ASIC 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 ASIC 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 when the UEM powers on. 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 power-off state. The UEM watchdogs are internally acknowledged at the rising edge of the PURX signal in order to always give the same watchdog
response time to the MCU.
The following diagram represents UEM start-up sequence from reset to power-on mode.
When the Power on 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 now 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 on key does not indicate a valid power on situation the MCU powers off the
baseband.
Power up when charger is connected
In order to be able to detect and start charging in the case where the main battery is
fully discharged (empty) and hence UEM has no supply (NO_SUPPLY or BACKUP mode of
UEM), charging is controlled by START-UP CHARGING circuitry.
Whenever VBAT level is detected to be below master reset threshold (VMSTR-), charging
starts and is controlled by START_UP charge circuitry. Connecting a charger forces
VCHAR input to rise above the charger detection threshold, VCHDET+, and by detection
charging is started. UEM generates 100mA constant output current from the connected
charger's output voltage. As battery charges, its voltage rises and when VBAT voltage
level is detected to be higher than the master reset threshold limit (VMSTR+), START_UP
charge is terminated.
Monitoring the VBAT voltage level is done by charge control block (CHACON). MSTRX='1'
output reset signal (internal to UEM) is given to UEM's RESET block when VBAT>VMSTR+
and UEM enters into reset sequence.
If VBAT is detected to fall below VMSTR- during start-up charging, charging is cancelled.
It will restart if new rising edge on VCHAR input is detected (VCHAR rising above VCHDET+).
RTC alarm power up
If phone is in POWER_OFF mode when RTC alarm occurs, a wake-up procedure occurs.
After baseband is powered ON, an interrupt is given to MCU. When RTC alarm occurs
during ACTIVE mode, an interrupt to MCU is generated.
Power Off
The Baseband switches into power off mode if any of following statements is true
• Power key is pressed
• Battery voltage is too low (VBATT < 3.2 V)
• Or if Watchdog timer register expires
The Power down procedure is controlled by the UEM.
Power Consumption and Operation Modes
During power off mode, power (VBAT) is supplied to UEM, BUZZER, VIBRA, LED, PA and
PA drivers (Tomcat and Hornet). During this mode, the current consumption on this mode
is approximately 35uA. This is the UEM leakage current.
In sleep mode, both processors, MCU and DSP, are in stand-by mode. Phone will go to
sleep mode only when by both processors made this request. When SLEEPX signal is
detected low by the UEM, the phone enters SLEEP mode. VIO and VFLASH1 regulators are
put into low quiescent current mode, VCORE enters LDO mode and VANA and VFLASH2
regulators are disabled. All RF regulators are disabled during SLEEP mode. When SLEEPX
signal is detected high by the UEM, the phone enters ACTIVE mode and all functions are
activated.
The 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 (19.2MHz Clk) is shut down and the 32 kHz sleep clock oscillator is used as reference clock for the baseband.
The average current consumption of the phone can vary depending mainly on SW state
like slot cycle 0, 1, or 2 and if the phone is working on IS95 or IS2000 for CDMA; however, on average 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 phone present state such as: burst reception, burst
transmission, if DSP is working etc.
In active mode, SW controls the UEM RF regulators: VR1A and VR1B can be enabled or
disabled. These regulators work of the UEM charge pump. VSIM can be enabled or disabled and its output voltage can be programmed to be 1.8V or 3.3V. VR2 and VR4 -VR7
can be enabled or disabled or forced into low quiescent current mode. VR3 is always
enabled in active mode and disabled during Sleep mode and cannot be control by SW in
the same way as the other regulators. VR3 will only turn off if both processors (DSP and
MCU) request to be in sleep mode.
CHARGING mode can be performed in parallel with any other operating mode. A BSI
resistor inside the battery indicates the battery type/size. The resistor value corresponds
to a specific battery type and capacity. This capacity value is related to the battery technology.
Power
The battery voltage, temperature, size and charging current are measured by the UEM,
and the EM charging algorithm controls it.
The charging control circuitry (CHACON) inside the UEM controls the charging current
delivered from the charger to the battery. The battery voltage rise is limited by turning
the UEM switch off, when the battery voltage has reached 4.2 V. Charging current is
monitored by measuring the voltage drop across a 220 mOhm resistor.
In normal operation, the baseband is powered from the phone's battery. The battery consists of one Lithium-Ion cell. In the case of Lancelot, the battery capacity is 850 mAh.
The UEM ASIC controls the power distribution to whole phone through the BB and RF
regulators excluding the power amplifier (PA) and the DC/DC, which have a continuous
power rail directly from the battery. The battery feeds power directly to following parts
of the system: UEM, PA, DC/DC, buzzer, Vibra, display- and keyboard lights.
The heart of the power distribution to the phone is the power control ASIC, called UEM.
It includes all the voltage regulators and feeds power to the whole system. UEM handles
hardware functions of power up so that regulators are not powered and power up reset
(PURX) is not released if the battery voltage is less than 2.8 V.
RH-34 Baseband is powered from five different UEM regulators: VANA, VIO, VFLASH1,
VFLASH2, and VCORE DC/DC. See Table 1.
UEM voltage regulators: VR1A, VR1B, VR2, VR3, VR4, VR5, VR6 and VR7 are used by RF.
See Table 2.
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 during sleep and
VSIM253.0
Regulator
VR1A104.75Enabled when the receiver is on
VR1B104.75Enabled when the transmitter is on
VR21002.78Enabled when the transmitter is on
3001.5Output voltage selectable 1.0V/1.3V/1.5V/1.8V
Default power at power-up is 1.5V
power-off modes)
Table 2: RH-34 RF Regulators
Maximum
current
(mA)
Vout (V)Notes
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
A charge pump used by VR1A is constructed around UEM. The charge pump works with
Cbus (1.2 MHz Clk) and gives a 4.75 V regulated output voltage to RF.
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 (G503). This 19.2 MHz clock signal is generated at
the RF and fed to RFCLK pin of UPP.
The UPP distributes the 19.2 MHz Clk to the internal processors, the DSP, and MCU,
where SW multiplies this clock by seven for the DSP and by two for the MCU.
A 1.2 MHz clock signal is used for CBUS, which is used by the MCU to transfer data
between 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 UEM and UPP.
The system clock can stopped during sleep mode by disabling the VCTCXO power supply
from the UEM regulator output (VR3) by turning off the controlled output signal SleepX
from UPP.
The UEM provides a 32kHz sleep clock for internal use and to UPP, where it is used for
the sleep mode timing.
SleepCLK (Analog)
When the system enters sleep mode or power off mode, the external 32KHz crystal provides a reference to the UEM RTC circuit to turn on the phone during power off or sleep
mode.
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 consist of the VPP,
FBUSTX, FBUSRX, MBUS, and BSI signals and use by the FPS8 to flash. The connection is
through the UEM which means that the logic voltage levels are corresponding to 2.78V.
Power is supplied to the phone using the battery contacts.
Baseband Power Up
The baseband power is controller by the flash prommer in production and in re-programming situations. Applying supply voltage to the battery terminals will cause the baseband to power up. Once the baseband is powered, flash programming indication is done
as described in the following section.
Flash Programming Indication
Flash programming is indicated to the UPP using MBUSRX signal between UPP and UEM.
The MBUS signal from the baseband to the flash prommer is used as 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 only waits for a specified time to get input data from
the flash prommer. If the timer expires without any data being received, the MCU will
continue the boot sequence. The MBUS signal from UEM to the external connection is
used as clock during flash programming. This means that flash-programming clock is
supplied to UPP on the MBUSRX signal.
The flash prommer indicates the UEM that flash programming/reprogramming 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 registers matches with the default value preset in the UEM, programming
starts. At this point the flash prommer shall pull 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 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 previously loaded at
the falling edge of the BSI signal. During the flash programming mode the UEM watchdogs are disabled. Setting the bit indicating 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.
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 will be gated during UEM master reset and during power on when PURX is active. The BSI signal should not change state during normal
operation unless the battery is extracted, in this case the BSI signal will be pulled high,
note a falling edge is required to load the compare register.
Flashing
Flash programming is done through VPP, FBUSTX, FBUSRX, MBUS, and BSI signals.
When phone has entered to flash programming mode, prommer will indicate to UEM
that flash programming will take place by writing 8-bit password to UEM. Prommer will
first set BSI to "1" and then uses FBUSRX for writing and MBUS for clocking. After that
BSI is set back to "0".
MCU will indicate to prommer that it has been noticed, by using FBUSTX signal. After
this it reports UPP type ID and is ready to receive secondary boot code to its internal
SRAM.
FLASH_1
CH1 = BSI
CH2 = MBUS
CH3 = FBUSTX
CH4 = FBUSRX
Measure points
Production test pattern
(J396)
Figure 1: Flashing start
This boot code asks MCU to report prommer phone’s configuration information, including flash device type. Now the prommer can select and send algorithm code to MCU
SRAM (and SRAM/Flash self-tests can be executed)