Power Up and Reset ....................................................................................................................................7
Power Up - Power Key............................................................................................................................. 9
Power Up - Charger ................................................................................................................................. 9
Power Up - RTC Alarm.......................................................................................................................... 10
Power Off .....................................................................................................................................................10
Power Consumption and Operation Modes .......................................................................................10
Power Off ................................................................................................................................................. 10
Active Mode ............................................................................................................................................ 11
Power ............................................................................................................................................................11
Clock Distribution ......................................................................................................................................13
Charge Control ....................................................................................................................................... 23
Display and Keyboard ...............................................................................................................................24
BB Test Points .............................................................................................................................................24
Top View................................................................................................................................................... 25
GPS Test Points ..........................................................................................................................................28
Top Troubleshooting Map ........................................................................................................................29
Phone is Totally Dead ...............................................................................................................................31
Flash Programming Does Not Work .....................................................................................................32
Phone is Jammed .......................................................................................................................................34
Power Key ................................................................................................................................................ 43
The baseband module for the 6015/6015i/6015i/6019i, and 6012 transceivers include the
following:
ModelTypeTechnologyMemory
6012RM-20Analog and CDMA IS2000Discrete
Flash: 64 Mb
SRAM: 4 Mb
6015RH-55Analog and CDMA IS2000Discrete
Flash: 64 Mb
SRAM: 4 Mb
6015iRH-55Analog and CDMA IS2000Combo
Flash: 64 Mb
SRAM: 16 Mb
6016iRH-55Analog and CDMA IS2000Combo
Flash: 64 Mb
SRAM: 16 Mb
6019iRH-55Analog and CDMA IS2000Combo
Flash: 128 Mb
SRAM: 16 Mb
Frequency
(MHz)
800No
800/1900No
800/1900Yes
800/1900Yes
800/1900Yes
GPS Module
The baseband consists the following main Application Specific Integrated Circuits
(ASICs):
•Universal Energy Management (UEM)
•Universal Phone Processor (UPP)
•FLASH and SRAM memory
The baseband architecture is based on the DCT4 Universe engine and supports a powersaving function called sleep mode. Sleep mode shuts off the VCTCXO, which is used as a
system clock source for both the RF and the baseband. The phone awakens by a timer
running from this 32 kHz clock. The sleep time is determined by network parameters.
During the sleep mode, the system runs from a 32 kHz crystal. The phone enters sleep
mode when both the MCU and the DSP are in standby mode, and the 19.2 MHz Clk
(VCTCXO) is switched off.
The 6015/6015i/6015i/6019i, and 6012 support both 2- and 3-DCT3 type wire chargers.
However, the 3-type wire chargers are treated as 2-type wire chargers. The UEM ASIC
and EM SW control charging.
A BL-6C Li-ion battery is used as the main power source. The BL-6C has a nominal
capacity of 1070 mAh.
Power up and reset are controlled by the UEM ASIC. The baseband can be powered up in
the following ways:
•By the Power button, which means grounding the PWRONX pin of the UEM
•By connecting the charger to the charger input
•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 enters into
reset mode. The watchdog starts up, and if the battery voltage is greater than Vcoff+, a
200ms delay starts to allow references (etc.) to settle. After this delay elapses, the
VFLASH1 regulator is enabled. Then 500us later the 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
the 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.
Figure 2 represents the UEM start-up sequence from reset to power-on modes.
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,
which 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. Then the MCU reads the status of the PWRONX signal using the
UEM control bus (CBUS). If the PWRONX signal stays low for a specific duration, 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 - Charger
In order to be able to detect and start charging in the case where the main battery is
fully discharged (empty) and hence the UEM has no supply (NO_SUPPLY or BACKUP
mode of UEM), charging is controlled by START-UP CHARGING circuitry.
Whenever a VBAT level is detected to be below master reset threshold (V
charging starts and is controlled by START_UP charge circuitry. Connecting a charger
6015/6015i/6016i/6019i (RH-55), 6012 (RM-20)
Troubleshooting - BasebandNokia Customer Care
forces the VCHAR input to rise above the charger detection threshold (VCH
detection charging is started. The UEM generates 100 mA constant output current from
the connected charger's output voltage. The battery’s voltage rises as 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 the charge control block (CHACON). A
MSTRX='1' output reset signal (internal to the UEM) is given to UEM's RESET block when
VBAT>V
and the UEM enter into the reset sequence.
MSTR+
If VBAT is detected to fall below V
It will restart if new rising edge on the VCHAR input is detected (VCHAR rising above
DET+
).
VCH
Power Up - RTC Alarm
If phone is in POWER_OFF mode when an RTC alarm occurs, a wake-up procedure begins.
After the baseband is powered ON, an interrupt is given to the MCU. When an RTC alarm
occurs during ACTIVE mode, an interrupt is generated to the MCU.
Power Off
DET+
during start-up charging, charging is cancelled.
MSTR-
) and by
The baseband switches into 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
Power Off
During power off mode, power (VBAT) is supplied to the UEM, BUZZER, VIBRA, LED, PA
and PA drivers. During this mode, the current consumption is approximately 35 uA.
Sleep Mode
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 UEM detects a high SLEEPX signal, 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 (a charger connection, key press, headset connection, etc.).
In sleep mode, the VCTCXO (19.2 MHz Clk) is shut down and the 32 kHz sleep clock
oscillator is used as a reference clock for the baseband.
The average current consumption of the phone can vary depending mainly on the SW
state. However, the average consumption is about 6 mA in slot cycle 0.
Active Mode
In active mode, the phone is in normal operation; scanning for channels, listening to a
base station, and transmitting and processing information. There are several sub-states
in the active mode depending on the phone’s 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.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.
Charging 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.
The battery voltage, temperature, size and charging current are measured by the UEM,
and the UEM 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 reaches 4.2 V. The charging current is
monitored by measuring the voltage drop across a 220 mOhm resistor.
Power
In normal operation, the baseband is powered from the phone's battery. The battery
consists of one Lithium-Ion cell. The battery capacity is 1070 mAh.
The UEM ASIC controls the power distribution to the 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 the following
parts of the system:
6015/6015i/6016i/6019i (RH-55), 6012 (RM-20)
Troubleshooting - BasebandNokia Customer Care
•Vibra
•Display and keyboard lights
The UEM is the heart of the power distribution to the phone, which includes all the
voltage regulators. The UEM handles power-up hardware 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
VCORE
DC/DC
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
VSIM253.0Enabled during power-up mode and scanning for a SIM
Maximum
Current (mA)
3001.35The power-up default value is 1.35V. The output voltage is
Vout (V)Notes
selectable: 1.0V/1.3V/1.5V/1.8V.
and power-off modes)
card
Table 2 includes the UEM voltage regulators used by the RF.
Table 2: RF Regulators
Regulator
Maximum
Current (mA)
Vout (V)Notes
VR1A104.75Enabled when the receiver is on
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
A charge pump used by VR1A is constructed around the UEM. The charge pump works
with Cbus (1.2 MHz Clk) and gives a 4.75 V regulated output voltage to the RF.
The baseband’s main clock signal is generated from the VCTCXO (G501). This 19.2 MHz
clock signal is generated at the RF and fed to the UPP’s RFCLK pin and the GPS BB ASIC.
RFConvClk (19.2 MHz digital)
The UPP distributes the 19.2 MHz Clk to the internal processors, DSP, and MCU, where
SW multiplies this clock by seven for the DSP and by two for the MCU.
A 9.6 MHz clock signal is used for DBUS, which is used by the DSP to transfer data
between the UEM and the UPP.
Figure 7: 9.6 MHz DBUS clock signal
The system clock can be 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 the UPP.
6015/6015i/6016i/6019i (RH-55), 6012 (RM-20)
Troubleshooting - BasebandNokia Customer Care
SleepCLK (Digital)
The UEM provides a 32 kHz sleep clock for internal use and to the UPP, where it is used
for the sleep mode timing.
SleepCLK (Analog)
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.
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 consists of the VPP,
FBUSTX, FBUSRX, MBUS, and BSI connections to connection to the BB through the UEM,
which means that the logic voltage levels correspond to 2.78 V. Power is supplied to the
phone using the battery contacts.
Baseband Power Up
The baseband power is controlled by the flash prommer in production and in
reprogramming situations. Applying supply voltage to the battery terminals causes the
baseband to power up. 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 the 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
6015/6015i/6016i/6019i (RH-55), 6012 (RM-20)
Troubleshooting - BasebandNokia Customer Care
input data from the flash prommer. If the timer expires without any data being received,
the MCU 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. Programming starts if
the 8-bits in the compare register match with the default value preset in the UEM. At
this point 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 the 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 flash programming mode, the prommer indicates to the UEM
that flash programming will take place by writing an 8-bit password to the UEM. A
prommer first sets the BSI to "1", uses FBUSRX for writing, and uses the MBUS for
clocking. The BSI is then set back to "0".
The MCU uses the FBUSTX signal to indicate to the prommer that it has been noticed.
Then the MCU reports the UPP type ID and is ready to receive the secondary boot code in
its internal SRAM.
This boot code asks the MCU to report the prommer phone’s configuration information,
including the flash device type. Now the prommer can select and send the algorithm
code to the MCU SRAM (and SRAM/Flash self-tests can be executed).
FLASH_2
CH1 = PURX
CH2 = MBUS
CH3 = FBUSTX
CH4 = FBUSRX
Measure points
Production test pattern
(J396)
Figure 11: Flashing, continued 1
•Ch1-> PURX
•Ch2-> MBUS toggled three times for MCU initialization
•Ch3-> FBUS_TX low, MCU indicates that prommer has been noticed
6015/6015i/6016i/6019i (RH-55), 6012 (RM-20)
Troubleshooting - BasebandNokia Customer Care
FLASH_3
CH1 = PURX
CH2 = MBUS
CH3 = FBUSTX
CH4 = FBUSRX
Measure points
Produc tion test pattern
(J396)
Data transfer has
started (Fbus_Rx)
Figure 12: 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."
C103" Boot serial line fail."Mbus from Prommer->UEM->UPP(MbusRx)(SA1)
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.
FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
C104"MCU ID message sending failed in the Phone."FbusTx from UPP->UEM->Prommer
C105"The Phone has not received Secondary boot
codes length bytes correctly."
Mbus from Prommer->UEM->UPP(MbusRx)
FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
C106"The Phone has not received Secondary code
bytes correctly."
Mbus from Prommer->UEM->UPP(MbusRx)
FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
in the message, which it has received from the
Phone."
Cx82"The Prommer has detected a wrong ID byte in
the message, which it has received from the
Phone."
A204
Cx83
Cx84
"The flash manufacturer and device IDs in the
existing algorithm files do not match with the
IDs received from the target phone."
"The Prommer has not received phone
acknowledge to the message."
"The phone has generated NAK signal during
data block transfer."
UPP
Flash
Flash
FbusTx from UPP->UEM->Prommer
FbusTx from UPP->UEM->Prommer
Flash
UPP
VIO/VANA?
Signals between UPP-Flash
Mbus from Prommer->UEM->UPP(MbusRx)
FbusRx from Prommer->UEM->UPP
FbusTx from UPP->UEM->Prommer
Cx85
Cx87"Wrong MCU ID."RFClock
Startup
for
flashing
"Data block handling timeout"
UPP(Vcore)
Required startup for flashingVflash1
VBatt
Charging Operation
Battery
The phone uses a Lithium-Ion cell battery (BL-6C) with a capacity of 1070 mAh. Reading
a resistor 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.
6015/6015i/6016i/6019i (RH-55), 6012 (RM-20)
Troubleshooting - BasebandNokia Customer Care
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 13: BL-6C 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 baseband is designed to support DCT3 chargers from an
electrical point of view. Both two-wire and three-wire type chargers are supported.
However, 3-wire chargers are treated as 2-wire chargers.
Figure 14: Charging circuitry
Charger Detection
Connecting a charger creates voltage on the VCHAR input of the UEM. Charging starts
when the UEM detects that the VCHAR input voltage level is above 2 V
(VCHdet+ threshold). The 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:
1. Check that the charger output (voltage and current) is within safety limits
2. Identify the charger as a 2-wire 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.
Figure 15: Charging circuit
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 a safe area. For that reason, the UEM
has the following programmable, charging cut-off limits:
Audio
•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. There is no change in the
operational mode. Charging restarts after the voltage decreases below VBATLim-.
The audio control and processing is supported by the UEM and the UPP. The UEM
contains the audio codec. The UPP 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 = Used for the phone's internal microphone
•MIC2 = Used for pop-port audio accessories
•MIC3 = Used for the Universal Headset
Every microphone input can have either a differential or single-ended AC connection to
the UEM circuit. The internal microphone (MIC1) and external microphone (MIC2) are
both differential for Tomahawk accessory detection. However, the Universal Headset
interface is single-ended. The microphone signals from different sources are connected
6015/6015i/6016i/6019i (RH-55), 6012 (RM-20)
Troubleshooting - BasebandNokia Customer Care
to separate inputs at the UEM. Inputs for the microphone signals are differential types.
Also, the MICB1 is used for MIC1, and MICB2 is used for both MIC2 and MIC3 (Universal
Headset).
The HF single-ended output from the UEM is sent to the input of the MIDI audio
amplifier. VBAT supplies the voltage for driving the amplifier, which can be enabled or
disabled by the UPP using GenIO (10).
Display and Keyboard
The phone uses LEDs for LCD and keypad illumination. There are three white LEDs for the
LCD and two blue LEDs for the keypad, which is a separate board for the UI.
The phone also includes a 96X68 color LCD. The interface utilizes a 9-bit data transfer
and is similar to the DCT3-type interface, except the Command/Data information is
transferred together with the data.
Figure 16: D/C bit set during each transmitted byte
BB Test Points
Following are the top and bottom views of the BB test points, regulators, and BB ASICs.
The GPS circuitry utilizes RF signals from satellites stationed in geosynchronous orbit to
determine longitude and latitude of the handset. The GPS circuitry is completely separate
of the CE circuitry and is located almost exclusively on the secondary side of the PWB
underneath the display module.
Figure 17: GPS block diagram
To troubleshoot the GPS BB:
1. Perform a visual inspection on the GPS circuitry to see if the problem is physical
(dislodged parts, corrosion, poor solder joints, etc.).
2. Put the GE and CE in the proper mode.
3. Check to make sure that necessary inputs from the CE are good (power, clock,
etc.).
4. Ensure that the inputs produce the proper outputs. Because of the large level of
integration (most functionality is contained in the two ASIC chips), the amount
of diagnostics you can perform are limited.