Service Manual comprising
RH-48 Series Transceiver booklet comprising
Foreword
General
Parts
Service Software Instructions
Service Tools
Disassembly/Assembly
Troubleshooting - Antennas
Troubleshooting - Baseband
Troubleshooting - RF
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.
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
Windows 95Limited, no USB support
Windows 98
Windows NT 4.0no USB support
Windows 2000Professional version
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.
Systems
Notes
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.
Supported Operating
Systems
Notes
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 StationMJF-17 Docking Station Adapter
07702980774282
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 docking station adapter enables tuning, testing,
and flashing.
CPL-8 RF CouplerRJ-32 Rework Jig
07704750770757
CPL-8 allows antenna testing at AMS locations.
Shield Box JSX-1A is required.
The rework jig is a PWB component that allows de-soldering and soldering.
This cable is used for bottom connector flashing using
FLS-4S or FLC-20.
This jig allows phone PWB-level service and troubleshooting for authorized service centers.
PKD-1 SW Security DeviceFLA-30 Flash Adapter
07500180770472
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!
FLA-30 allows power and flash connection through the
battery compartment.
SS-13 is used with the MJF-x/DA-x flashing adapters
(shown with MJF-17).
This is a general-purpose RF cable.
Flashing, Testing, and Tuning
Tightened performance specifications require more precise equipment and methods for
testing and alignment. Manual tuning can’t provide accurate results for the RH-48,
which means that this test has to be automated.
XRS-6 RF Test Cable
These setups are intended to be with with the Phoenix Service Software. Both manual
testing and automated tuning are permitted with Phoenix Service Software.
This troubleshooting guide addresses potential failures that will affect antenna performance of the RH-48 phone, and discusses methods for correction of these failures.
Relevant Documents
C-Max Antenna RF Specifications and Plan (DHS02726-EN-1.0)
If the internal antenna is missing, install one. If the radiator looks obviously damaged,
then replace the internal antenna.
If no internal antenna is installed, the antenna gain will be degraded by more than
25dB.
Damaged RF Feed Pin or Ground Pin
Figure 4: Top and bottom views of the RH-48 internal antenna
If either the RF feed pin or ground pin are broken or bent such that either pin will not
touch the PWB, then the internal antenna must be replaced. If the springs for the RF or
ground pin appear damaged, then the internal antenna must be replaced. If the slot in
the radiator has a significantly different shape, then the correct internal antenna must
be installed. If there is any other obvious damage to the radiator (dents, corrosion), then
the antenna should be replaced. If the pin gets stuck or has excessive friction in the plastic tube/guiding feature, then the spring will not work properly and the antenna should
be replaced.
If the RF feed doesn’t touch the PWB, then the antenna gain will degrade by more than
25dB. If the ground pin doesn’t touch the PWB, then the antenna gain may degrade
about 5 to 10dB.
If either of the IHF speaker pins is damaged or if the IHF speaker is nonfunctioning, then
the antenna module should be replaced.
Wrong Internal Antenna Installed
RH-48antenna
RH-19 antenna
RH-48antenna
RH-48 antenna
Figure 5: Top views of the RH-19 and RH-48 antennas
RH-19 antenna
Figure 6: Bottom views of RH-19 and RH-48 antennas
RH-48 antenna
The RH-48 and RH-19 antennas are similar in appearance. The important visual difference in the antennas is that the slot pattern is very different. Also, the RH-48 antenna is
thicker than the RH-19 antenna and also has a spacer on its back side.
If the wrong antenna is installed, install the correct one.
Obstructed RF Feed or Ground Pads for Internal Antenna, or IHF Speaker Pads
Pad for ground pin
Pad for RF pin
IHF speaker pads
Figure 7: PWB layout of RF feed and ground pads and IHF speaker pads
If the RF feed pad is obstructed, removed, or covered, then the RF feed pin will not touch
the PWB and the antenna gain will degrade by more than 25dB. If the ground pad is
obstructed, removed, or covered, then the ground pin will not touch the PWB and the
antenna gain may degrade by about 5 to 10dB. If corrosion is present or the pad is missing, 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 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, 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.
Note that the display frame is grounded to the PWB through the two top screws. The
grounding of the display frame will impact the radiation performance 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.
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 this happens, then 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 the figure above. If the conductive sticker is missing or ripped, it needs to be replaced.
If the sticker is damaged or missing, then the radiated sensitivity could be reduced
by 4-8dB.
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 25dB. 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
inserted, the RF input is connected to the RF connector. The location is shown in
Figure 6.
RF input — connector to duplexor
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, the RF connector must be
replaced.
The Baseband module of the RH-48 transceiver is a CDMA single-band engine. The baseband architecture is based on the DCT4 Apollo engine.
RH-48 cellular baseband consists of three ASICs: Universal Energy Management (UEM),
Universal Phone Processor (UPP), and a 128/8 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.
RH-48 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 three-wire charger is ignored. UEM ASIC and EM SW control charging.
BL-5C Li-ion battery is used as main power source for RH-48. BL-5C has nominal capacity of 850 mAh.
• By 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
its 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 Power Up Reset (PURX ) line is held low for 20 ms. This reset, PURX, is sent to
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 Vflash2. 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 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 timing 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 notice 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 cases 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 (V
controlled by START_UP charge circuitry. Connecting a charger forces VCHAR input to
rise above charger detection threshold, VCH
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 higher
than master reset threshold limit (V
MSTR-
. By detection start-up charging is
DET+
) is detected START_UP charge is terminated.
MSTR+
), charging is
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>V
during start-up charging, charging is cancelled. It
MSTR
will restart if new rising edge on VCHAR input is detected (VCHAR rising above VCH
RTC alarm power up
If phone is in POWER_OFF mode when RTC alarm occurs the wake-up procedure. After
baseband is powered on, an interrupt is given to MCU. When RTC alarm occurs during
ACTIVE mode, the interrupt for MCU is generated.
Power off
The Baseband switch power-off mode if any of following statements is true:
• Power key is pressed
• Battery voltage is too low (VBATT < 3.2 V)
• Watchdog timer register expires
The Power-down procedure is controlled by the UEM.
Power Consumption and Operation modes
DET+
).
In the POWER-OFF mode, the 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.
In the SLEEP mode, both processors, MCU and DSP, are in stand-by mode. Phone will go
to sleep mode only when both processors make 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, VCTCXO is shut down and 32 kHz sleep clock oscillator is used as reference clock for the baseband.
The average current consumption of the phone in sleep mode can vary depending mainly
on SW state (e.g., 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 of the phone 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. 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 request to be in sleep mode.
In the CHARGING mode, the charging 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. 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, and keyboard lights.
The heart of the power distribution to the phone is the power control block inside UEM.
It includes all the voltage regulators and feeds the power to the whole system. UEM handles hardware functions of power up so that regulators are not powered and power up
reset (PURX) are not released if battery voltage is less than 3 V.
RH-48 Baseband is powered from five different UEM regulators (VANA, VIO, VFLASH1,
VFLASH2, and VCORE (DC/DC) See Table 1.
UEM supplies also voltages VR1A, VR1B, VR2, VR3, VR4, VR5, VR6, and VR7 for RF. See
Table 2.
VCORE3001.5Output voltage selectable 1.0V/1.3V/1.5V/1.8V
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
Regulator
VR1A104.75Enabled when cell transmitter is on
VR1B104.75Enabled when the transmitter is on
Maximum current
(mA)
Table 2: RH-48 RF regulators
Maximum current
(mA)
Vout (V)Notes
Power up default 1.5V
during sleep and power off-modes)
Vout (V)Notes
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 UEM. The charge pump
works with Cbus (1.2 MHz) oscillator and gives a 4.75 V regulated output voltage to RF.
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). Yoda then converts the analog sine waveform to a digital waveform with swing voltage of 0 tot 1.8V and sends it to the UPP
from pin 16 at Yoda (19.2 Out) to the UPP pin M5 (RFCLK). (See Figure 4 for waveform.)
Figure 4: Waveform of 19.2MHz clock (VCTCXO) going to the Yoda ASIC
The UPP distributes the 19.2MHz internal clock to the DSP and MCU, where SW multiplies this clock by seven for the DSP and by two for the MCU. (See Figure 6.)
A 1.2 MHz clock signal is use for CBUS, which is used by the MCU to transfer data
between UEM and UPP. (See the following figure for Cbus data transfer.)
DBUS Clk Interface
A 9.6 MHz clock signal is use for DBUS, which is used by the DSP to transfer data
between UEM and UPP. (See the following figure.)
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 UPP.
SleepCLK (Digital)
The UEM provides a 32kHz sleep clock for internal use and to UPP, where it is used for
the sleep mode timing. (Figure 9.)
However, 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. (Figure 10.)
Figure 10: 32kHz analog waveform at 32KHz 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 are corresponding to 2.7V. Power
is supplied using the battery contacts.
Baseband Power Up
The baseband power is controlled by the flash prommer in production and in re-programming situations. Applying supply voltage to the battery terminals the baseband will
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, 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.
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 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.
• Flash programming is done through VPP, FBUSTX, FBUSRX, MBUS, and BSI signals.
• When phone has entered the flash programming mode, the prommer indicates to UEM
that flash programming will take place by writing 8-bit password to UEM. The prommer sets BSI to “1” and then uses FBUSRX for writing and MBUS for clocking. After
that, BSI is set back to “0”.
• MCU indicates to prommer that it has been noticed, by using the FBUSTX signal. After
this, it reports UPP type ID and is ready to receive secondary boot code to its internal
SRAM.
Measure points
Produc tio n te s t pa tter n
(J396)
Data transfer has
started (Fbus_Rx)
Charging operation
Battery
In RH-48, a Lithium-Ion cell battery with a capacity of 850 mAh is used. Reading a resistor inside the battery pack on the BSI line indicates the battery size. With an NTC resistor
on PWB, the phone measures the approximate temperature of the battery on the BTEMP
line.
Temperature and capacity information are needed for charge control. These resistors are
connected to BSI pin of the battery connector and BTEMP of the phone. Phone has
100 kΩ pull-up resistors for this line so that they can be read by A/D inputs in the phone.
Figure 15: Interconnection diagram inside the battery pack
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 RH-48 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. See
Figure 16 for details.
Connecting a charger creates voltage on VCHAR input of the UEM. When VCHAR input
voltage level is detected to rise above 2 V (VCHdet+ threshold) by UEM charging starts.
VCHARDET signal is generated to indicate the presence of the charger for the SW. The
charger identification/acceptance is controlled by EM SW.
The charger recognition is initiated when the EM SW receives a ”charger connected”
interrupt. The algorithm basically consists of the following three steps:
1Check that the charger output (voltage and current) is within safety limits.
2Identify the charger as a two-wire or three-wire charger.
3Check 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 UEM’s digital part. Charging voltage and current monitoring is used to limit charging into safe area. For that reason UEM has programmable charging cut-off limits:
VBATLim1=3.6 V (Default)
VBATLim2L=5.0 V and
VBATLim2H=5.25 V.
VBATLim1, 2L, 2H are designed with hystereses. When the voltage rises above VBATLim1,
2L, 2H+ charging is stopped by turning charging switch OFF. No change in operational
mode is done. After voltage has decreased below VBATLim- charging re-starts.
F100
1.5A
L1002
________
42R/100MHz
Figure 17: 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: two-wire
charger uses a 1Hz and a three-wire charger uses a 32Hz. Duty cycle range is 0% to
100%. Maximum charging current is limited to 1.2 A.
The audio control and processing in RH-48 is provided by UEM, which contains the audio
codec, and UPP — which contains the MCU and DSP blocks, handling and processing 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 RH-48, the internal microphone (MIC1) and external microphone (MIC2) for Tomahawk accessory detection are both differential. The microphone signals from different
sources are connected to separate inputs at UEM. Inputs for the microphone signals are
differential type. Also, MICBIAS1 is used for MIC1 and MICBIAS2 is used for MIC2.
VBAT
Display and Keyboard
LEDs are used for LCD and keypad illumination in RH-48. There are two LEDs for LCD and
four LEDs for keypad. The signal used to drive the LED driver for the LCD and keyboard is
KLIGHT. This signal turns on the LED driver (N302).
Color LCD is used in RH-48. Interface is using 9-bit data transfer. The interface is quite
similar to DCT3 type interface, except Command/Data information is transferred
together with the data.
The following figure is the waveform for LCD interface.
RH-48 supports Tomahawk and Universal Headset accessories, differential and singleended, respectively. Detection of Tomahawk accessories is done through the ACI signal
where the Universal Headset is detected on GenIO (12). The following graphic shows the
pin out of the Tomahawk connector.
The pin out on the Tomahawk connector is as follows:
1. Charger
2. Charger GND
3. ACI
4. Vout
5. USB Vbus
6. USB D+ / Fbus Rx
7. USB D- / Fbus Tx
8. Data GND
9. XMic N
10. XMic P
11. H S e a r N
12. HSear P
13. HSear R N
14. HSear R P
In Tomahawk accessories, the following functions may be performed: charging, accessory
detection, FBUS communication, USB communication, and fully differential audio interface for mono- and stereo outputs.
Charging
Charging through the Tomahawk is accomplished in the same manner as through the
charger connector. Pin 1 of the Tomahawk 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.
The actual charging sequence is illustrated in the following diagram. The channels on the
diagram are:
CH1 = Charging current across the .22 Ohm (R200) resistor on UEMK