A/DAnalog to Digital
ACIAccessory Interface
AFCAutomatic Frequency Control
APEApplication Program Engine
ASICApplication Specific Integrated Circuit
BSIBattery Size Indicator
BTBluetooth
BTEMPBattery Temperature
CBUSNokia Proprietary Serial Interface for MCU
CDMACode Division Multiple Access
CMTCellular Mobile Telephone
D/ADigital to Analogue
DACDigital to Analogue Converter
DAIDigital Audio Interface
DBUSNokia Proprietary Serial Interface for DSP
DCDirect Current
DCTDigital Core Technology
DMADirect Memory Access
DSPDigital Signal Processor
EMCElectro Magnetic Compatibility
FBUSNokia Proprietary Serial Interface
FMFrequency Modulation
FMEAFailure Mode and Effect Analysis
GSMG lobal System for Mobile Communications
HelenP rocessor from Texas Instruments (also called OMAP1510)
HFHands Free
HFCMHands Free Common Mode
HWHardware electronics including Audio, Energy Management, UIHW and BB
I2CInter-IC Control bus
ICIntegrated Circuit
IF Interface
IHFIntegrated Hands Free
IMEIInternational Mobile Equipment Identity
IO, I/OInput Output
LCDLiquid Crystal Display
LDOLow Drop Out
LEDLight Emitting Diode
LSBLeast Significant Bit
LTPSiLow Temperature Poly Silicon
MBUSNokia Proprietary Serial Interface
MCUMicro Controller Unit
MMCMulti Media Card
MMUMemory Management Unit
MPUMicro Processing Unit
MSBMost Significant Bit
NTCNegative Temperature Coefficient
PSPower Save signal
PURXPower Up Reset
PWBPrinted Wiring Board
PWMPulse Width Modulation
RFRadio Frequency
RTC Real Time Clock
SDRAM Synchronous Dynamic Random Access Memory
SIMSubscriber Identity Module
SMPSSwitch Mode Power Supply
SWSoftware
TFTThin Film Transistor
TITexas Instruments
uBGAMicro Ball Grid Array package
UEMUniver sal En ergy Management
UI User Interface
UPPUniversal Ph one Processor
USBUniver sal Serial Bus
VBATBattery Volt age
VCTCXOVoltage Controlled
VGAVideo Graphics Array
XBUSProprietary Nokia serial communication bus
NHL-12 is an imaging category (IP2.5) phone introducing a high-quality colour LCD, improved
camera and EDGE for Americas. NHL-12 operates on triple-band GSM (850/1800/1900) and
E-GPRS networks, and supports enhanced interfaces for connectivity with BT (Bluetooth) and
USB (Universal Serial Bus).
The NHL-12 baseband consists of a dual-processor engine and some product specific blocks,
such as IrDA and S60-display.
NHL-12 hardware and baseband consist of two parts: application part APE and phone part
CMT.
The APE part is constructed around an OMAP 1510 processor with SDRAM and NAND flash
memory as the core. Other major parts for APE are power, UI, audio, Bluetooth and camera.
APE and CMT parts are connected by serial communication buses and by a few control lines.
APE part reset and power control comes from the CMT side. Audio control is mostly performed
on the APE side, and phone audio is routed from the CMT side.
■ Baseband block diagram
The below system block shows the main BB function blocks.
The CMT architecture is based on DCT4 Common Baseband.
The main functionality of the CMT baseband is implemented into two ASICs: UPP (Universal
Phone Processor) and UEM (Universal Energy Management).
System clock for the CMT is derived from the RF circuits. For the CDMA system, the RF clock
is 19.2 MHz and for GSM it is 26 MHz. The low frequency sleep clock is generated in the UEM
using an external 32.768kHz crystal. The I/O voltage of the CMT baseband is 1.8V. The analogue parts are powered from 2.8V power rails. The core voltage of UPP can be altered with
SW, depending on the prevailing processing power requirements.
UEM is a dual voltage circuit. The digital parts are running from the baseband supply (1.8V)
and the analogue parts are running from the analogue supply (2.8V). Some of th e UEM blocks
are also connected directly to the battery voltage (VBAT). UEM includes 6 linear LDO (low
drop-out) regulator for baseband and 7 regulators for RF. It also includes 4 current sources for
biasing purposes and internal usage. Some parts of the SIM interface have been integrated into
UEM. The SIM interface supports 1.8V and 3V SIM cards. Data transmission between the UEM
and UPP is handled via two serial buses: DBUS for DSP and CBUS for MCU. There are also
separate signals for PDM coded audio. Digital speech processing is handled by the DSP inside
UPP and the audio codec is in UEM.
The analogue interface between the baseband and the RF sections is implemented into UEM.
UEM provides A/D and D/A conversion of the in-phase and quadrature receive and transmit
signal paths and supplies the analogue TXC and AFC signals to the RF section under the UPP
DSP control. The digital RF-BB interface, consisting of a dedicated RFIC control bus and a
group of GenIO pins, is located in UPP.
The baseband supports both internal and external microphone inputs and speaker outputs. Input and output signal source selection and gain control is done in the UEM according to control
messages from the UPP. Keypad tones, DTMF and other audio tones are generated and encoded by the UPP and transmitted to UEM for decoding.
NHL-12 has two galvanic serial control interfaces for CMT: FBUS and MBUS.
Communication between the APE and CMT parts is handled through two serial buses: XBUS
and XABUS. XBUS is the main communication channel for general use, and XABUS is for audio data transfer. Also the system reset (PURX) and SleepClk for APE are coming from the
CMT side. The PURX is delayed approximately 130ms to fulfil OMAP1510 reset timing requirements and one of UEM’s IR level shifters is used for SleepClk level shifting.
The memory interface supports 16-bit burst mode NOR FLASH with multiplexed add ress/data
bus, standard asynchronous 8-bit SRAM and 16-bit address/data multiplexed SRAM. The UPP
has two dedicated CS pins for FLASH and one GenIO that can be used as RAM CS.
The maximum amount of 16-bit SRAM with multiplexed address/data bus that can be connected to UPP is 2MBytes.
Memory configuration
The maximum amount of memory supported by UPP is 2*16MBytes of FLASH plus 2MBytes
of external SRAM.
CMT memory configuration includes 32Mbits of 54MHz NOR FLASH. The flash has readwhile-write capabilities.
The functionality of the APE engine is based on the OMAP1510 processor and memories. APE
has a total of 32 Mbytes of NAND type flash memory and 64 Mbytes of SDRAM.
The application engine has two separate clock sources: one for the system clock (12MHz) and
one for the sleep clock (32.768kHz), which is called Clk32k. The Clk32k is not generated by
the application engine, but is derived from the CMT SleepClk using a level shifter. The Clk32k
is always running when the engine is powered.
The 12MHz system clock is generated by OMAP1510. The crystal driver and related circuitry
is internal to the processor and an external quartz crystal is used as a frequency reference. The
Bluetooth clock is also derived from this clock using a clock buffer. Note that the system clock
is switched off during sleep mode.
The APE reset (MPU_nReset) is controlled by the CMT reset (PURX) generated by UEM.
PURX and MPU_nReset have different logic levels, but the latter is not simply a level shifted
version of the former. There is also an external delay circuit connected between the PURX and
MPU_nReset lines that keeps the APE reset active circa 130ms after CMT reset is released.
OMAP1510 consists of:
•DSP megamodule with internal program and data memory, instruction cache,
DMA controller and hardware accelerator
•ARM925T based processor megamodule with memory management unit (MMU),
instruction and data cache
•local bus with MMU
•multi-channel system DMA controller
•peripherals (local and shared) that support glueless system interface
•connecting modules that facilitate communication between these megamodules
and system memory (external and internal), and enhance system’s throughput and
software development.
OMAP 1510 is optimized for various multimedia and wireless applicat ions such as wireless video and image processing, wireless audio applications, graphics and video display acceleration.
APE memories
APE memory system consists of a 64Mbyte(32Mx16) SDRAM device connected to the
OMAP1510 fast external memory interface (EMIFF) and a 32Mbytes(32Mx8) of NAND-flash
device connected via Seija Flash-Interface Adapter ASIC to the OMAP1510 slow external
memory interface, EMIFS. The memory interface is shown in Figure 3, “APE external memories,” on page 14. NAND-flash is used as a boot the device and mass memory. User data is
stored in NAND. The operating voltage of all memory components is 1.8V, supplied from V18.
The energy management of NHL-12 is based on BB 4.0 architecture. BL-5C battery supplies
power primarily to the UEM ASIC and the RF PA. UEM includes several regulators to supply
RF and baseband. It provides the energy management including power up/down procedure.
Power supply modes
The state machine in UEM controls mainly the operating modes of the eng ine. State transitions
are enabled by signals taken from UEM, UPP and OMAP1510. In general, the state transitions
are based on the following information:
•Power key status (in NHL-12 engine power key connected to PWRONX pin of
UEM)
•Delays generated by the state machines
•Real time clock (RTC) alarms
•Watchdogs
•Thermal shutdowns
•SLEEPX signal from UPP
•LOW_PWR signal from OMAP1510
The functional behaviour of the UEM can be divided into 6 different states. Since the UEM controls the regulated power distribution of the phone, each of these states affects the general
functionality of the phone:
•No supply
•Backup
•Power off
•Reset
•Power on
•Sleep
Brief description of operating modes
•NO_SUPPLY mode means that the main battery is not present or its voltage is
too low (below UEM master reset threshold limit) and back-up battery voltage is too
low.
•In BACK_UP mode the main battery is disconnected or empty but back-up battery
has sufficient charge in it
•IN POWER_OFF mode the main battery is present and its voltage is over UEM
master threshold limit. All regulators are disabled.
•RESET mode is a synonym for start-up sequence and contains in fact several
modes. In this mode certain regulators and system oscillators are enabled and after
they have stabilized, the system reset (PURX) is released and PWR ON mode entered.
•In POWER_ON mode SW is running and controlling the system.
•SLEEP mode is entered only from PWR ON mode when system activity is low.
CMT and APE sides can be in sleep mode independent of each other.
For controlling transitions between modes, UEM includes:
•digital circuitry
These are used for generating limits and time delays.
Controlled powering off is done when the user requests it or when the battery voltage is fallin g
too low. Complete power down is done, if SW does not write to the watchdog register anymore
and a defined time after previous writing is elapsed. As this happen s, PURX is forced low and
all regulators are disabled. If the battery voltage falls below the very last SW–cutoff level, SW
will power off the system by letting the UEM’s watchdog elapse. If a thermal shutdown limit in
UEM regulator block is exceeded, the system is powered off. System reset PURX is forced low.
Uncontrolled powering off happens, when the battery is suddenly removed. This is problematic
as data may corrupt in memories, if the removal takes place during the access phase to these
devices. UEM’s state machine notices battery removal after battery voltage has been below
VCOFF– for 5 us and enters PWR_OFF mode. PURX is set low and all UEM’s regulators are
disabled.
There are three watchdogs in UEM. First one is for controlling system power-on and powerdown sequences. The initial time for this watchdog after reset is 32s. The time can be set using
a register. This watchdog is used for powering the system off in a controlled manner. The second one is for security block and is used during IMEI code setting. The third one is a power key
watchdog. It is used to power off the system in case SW is stuck and the user presses the power key. This watchdog, if not acknowledged by the SW, shuts down the system after a predefined delay (2–15 seconds). The feature is enabled as default and can be disabled by SW.
OMAP1510 also includes a hardware watchdog. This resets OMAP1510, BT and Seija at the
same time. It is possible to disable this watchdog with the help of SW.
Table 4: Reset thresholds and cutoff limits
VMSTR+ Master reset threshold 2.1 V
VMSTR– Master reset threshold 1.9 V
VCOFF+ Hardware cutoff 3.1 V
VCOFF– Hardware cutoff 2.8 V
VCHAR+VCHAR detection threshold2.0 V
VCHAR-VCHAR detection threshold1.8 V
SW
CUTOFF
SW cutoff limitSystem dependent
VBUCOFF+ Backup battery cutoff 2.1 V
VBUCOFF– Backup battery cutoff2.0 V
Battery BL-5C
The main battery of NHL-12 is a lithium ion battery BL-5C with the capacity of 850mA.
The battery interface has three pins: VBAT, GND and BSI. Temperature indication is located
on the engine PWB. Temperature measurement is performed using an NTC resistor (47k nom)
on the engine PWB.
Current gauge (Zocus)
The NHL-12 engine supports HW for phone and charging current measuring. The current
measurement chip that is used is LM3820. Current gauge is also supported by the ISA EM
Core SW. It can be used to estimate the battery charge level presented as batt ery bars on the
display.
Current is measured from the positive battery terminal using a sense resistor, so that all
phone’s consumed current flows through that resistor. Correspondingly, when charging, all current to phone’s battery flows through this resistor, but the direction is reversed. The sense resistor is formed from PWB tracks arranged as a 4-terminal resistor. LM3820 senses voltage
across the resistor. The maximum current depends on the sense resistor value.
RTC capacitor
Real Time Clock (RTC), crystal oscillator and backup battery circuitry are located inside the
UEM. Two regulators are used to provide needed voltages for external backup supply and
backup battery charging: VRTC for internal clock circuitry and VBU for backup battery charging.
The backup battery has voltage range VBACK = 2.0V
and discharged down to 2.0V).
min
– 3.2V
– 3.3V
typ
(charged to 3.2V
max
Charging the backup battery is controlled by the UEM’s digital block by enabling VBU regulator
and backup battery is charged with constant voltage up to 3.2V. By default, VBU regulator is
disabled in reset and it is reset always when PURX='0'.
The transceiver baseband section has a multi-function analogue ASIC, UEM, which contains
six pieces of 2.78 V linear regulators and a 4.8 V switching regulator. All the regulators can be
controlled individually by the 2.78 V logic directly or through a control register.
The seven regulators are named VR1 to VR7. VrefRF01 and VrefRF02 are used as the reference voltages for Helgo, VrefRF01 (1.35V) for the bias reference and VrefRF02 (1.35V) for the
Rx ADC (analog-to-digital converter) reference.
The regulators (except VR7) are connected to Helgo. Different modes of operation can be selected inside Helgo according to the control information coming through the RFBus. UEM’s internal regulators are used for the powering of the baseband module. In addition to this, VIO and
VFLASH1 regulators of UEM are used to enable/disable APE side regulators.
VCORE and VSIM are programmable linear regulators. Default state for VCORE voltage is
1.57V.
There are also internal regulators in UEM. They are used for the powering of the CMT BB. In
addition to this, VIO and VFLASH1 regulators of UEM are used to enable/disable APE side regulators. BB4.0 supports only UEMKEdge or UEMC with UPP8Mv3.
NHL-12 APE energy management uses two switch mode power supplies: LM2608 and
LM2708, generating 1.57V and 1.8V to OMAP1510 and memories. In addition, the APE side
EM HW consists of several other discrete regulators:
•One linear regulator for 2.8V APE side logic (LP3981)
•One 2.8V linear regulator (LP3985) for powering the MMC card.
•One 3.3V linear regulator (LP2985) for powering the USB block of OMAP1510.
LM2608 is used to generate 1.8V for I/O’s OMAP1510 processor and APE side memories. Normally, LM2608 works in constant frequency PWM mode. But in the case of light loads, it is possible to control LM2608 via SYNC/MODE pin to low quiescent current mode. In this mode,
LM2608 works as a linear regulator and the output current capacity is only 3mA. LM2608 ne eds
an external 1.35V reference voltage. In the case of NHL-12 engine, this reference voltage is
taken from VrefRF01 of the UEM.
LM2708 is used to generate 1.57V for the core of OMAP1510 processor. LM2708 does not
need external reference voltage. Pin (Isel) can be used to adjust the current limit external coil.
NHL-12 engine has a higher current limit, which allows 400mA output current capacity.
In NHL-12 engine, LOW_PWR signal of OMAP1510 (multiplexed on pin ARMIO_5) is used to
control LM2708/LM2608 to linear mode when processor goes to deep sleep mode. The functionality of the LOW_PWR signal is the following: when OMAP1510 is in a low power state
(deep sleep mode), this signal is high. At reset and when in normal func tional mode, this signal
is low. Because the polarity SYNC/MODE pin is reverse, an additional inverter is used in this
control line.
Charging control and charge switch are located in the UEM.
There is a thermal protection circuitry in the UEM to protect the chip. If temperature rises above
the threshold(150×C typ.), a charge switch is opened immediately and charging is stopped.
When the chip cools down, charging is continued normally.
HW supports all DCT4 chargers. 3-wire chargers are supported, but 3-wire charging is not. In
practice this means that the 3-wire chargers are internally connected (charger control wire connected to GND) as 2-wire chargers.
■ Audio circuitry
This section describes the audio HW of the engine. External audio components and acoustics
are not considered in detail in this section.
As this engine is based on dual-processor architecture, also audio is divided into separate APE
and CMT parts. Audio control is mostly on the APE side; phone audio is routed from the CMT
side to APE in analogue form, except Bluetooth which is in digital form. On the CMT side, audio
HW is integrated into the UEM ASIC. On the APE side, the most important parts are
OMAP1510, audio DAC and audio power amplifier.
The stereo output of this amplifier is designed for use with the ext ended Pop-port
It also has a differential mono output for driving the handsfree speaker.
The battery voltage (VBATT) is used directly as supply voltage for audio amp lifier. The nominal
battery voltage is 3.6V.
The type of DAC used is TLV320AIC23B and the supply voltage for this is coming from V28.
NHL-12 uses an earpiece which is a 32 ohm speaker with a diameter of 8 mm. The supply voltage is 2.7V. The earpiece is driven differentially directly by the UEM. The ca psule is mou nted
into the LCD frame assembly.
Internal microphone
The internal microphone is mounted in the B-cover. The microphone is omnidirectional and it
is connected to the UEM microphone input MIC1P/N. The microphon e input is asymmetric and
the UEM (MICB1) provides the bias voltage. Nominal impedance of the microphone is
1.8kOhms. The microphone input to UEM is ESD protected. Spring contacts are used to connect the microphone to the main PWB.
Integrated hands-free
Integrated hands-free speaker (IHF), 16mm, is used to generate alertin g and warning tones in
NHL-12. The IHF speaker is driven with audio amplifier. The speaker capsule is mounted in the
antenna module. Spring contacts are used to connect the IHF speaker contacts to the main
PWB.
Audio accessory receive path
In NHL-12 the accessory receive path is directly driven from the UEM HF / HFCM differential
audio outputs. The output signal complies with the Pop-port accessory interface.
For EMC protection, ferrites are connected in series to the earpiece and for ESD protection bizener is used.
The HEADINT signal is needed for recognizing the external device (e.g. headset) connected
to the system. The recognition is based on the ACI-pin on the system connector.
The button of the external device generates HOOKINT. This is used, for example, to answer or
to end a phone call.
■ Acoustics
Earpiece acoustics
The earpiece is a PSS 8mm element. The earpiece is placed inside the plastic UI frame. It is
sealed to UI support frame with a foam ring. This cavity is ported to a second cavity formed
between the UI support frame and A-cover with Bezel. Sound holes vent this cavity out of the
UI support flame. All holes are shielded to prevent dust and small particles from entering the
phone.
IHF speaker acoustics
In NHL-12, the IHF speaker is used for integrated hands-free and ringing tone applications. It
has a structure, which consists of two cavities: one back cavity and one front cavity.
When using the phone in the IHF mode, speech is fed to the IHF-speaker.Ringing tones are
optimized according to bandwidth and frequency response. The sound holes are placed in the
B-cover. Sound holes are shielded to prevent dust and small particles from entering the phone.
Figure 6:Exploded view of antenna assembly.
Microphone acoustics
NHL-12 has a standard microphone module. The module is embedded into a so-called "rubber
boot" and connected to the system module by spring contacts.
The microphone is placed close to the system connector. The sound port of the microphone is
located towards the bottom of the phone.
Vibra motor
A vibra alerting device is used to generate a vibration signal for an incoming call. It is located
in the middle part of the phone and it is connect ed to the main PWB with spring contacts. The
vibra is controlled by a PWM signal coming from UEM. The vibra motor is mounted in the Bcover assembly.
■ Audio modes
This section describes NHL-12’s engine audio modes. The following audio modes are supported:
•Hand portable
•Integrated hands-free
•Accessory audio mode
•APE audio mode
•Bluetooth audio mode
Hand portable
Hand portable mode is the basic audio mode. This is entered when no audio accessories are
connected and the hands-free mode is not selected.
In the hand portable mode, earpiece path and internal microphone path are in use.
A call is created by the CMT. The uplink signal is generated by the microphone and transferred
to MIC1P/N differential inputs. The internal microphone is enabled using the MICB1 bias voltage O/P on UEM. The signal is amplified at least by 20 dB, low pass filtered, converted into
digital domain and then postponed through UPP to transducer equalizer and finally to APE for
speech encoding.
The EAR output on the UEM is selected for Rx audio via the internal earpiece. The UEM sets
the audio uplink gain and downlink attenuation. Different downlink attenuation levels function
as the volume control.
The internal earpiece is driven by the CMT engine for voice calls. The internal microphone is
driven by the CMT for voice calls and voice recording.
All volume controls are handled by the UEM.
Integrated hands-free audio mode (IHF)
This mode is entered by user selection.
A call is created by the CMT. The uplink signal is generated by the microphone and transferred
to MIC1P/N differential inputs. The internal microphone is enabled using the MICB1 bias voltage O/P on the UEM.
The downlink audio is processed in the UPP and transferred to the UEM. Then the downlink
signal is amplified in the single-ended XEAR Output driver in the UEM. The mono XEAR output
is connected to the MICIN input of the APE Audio DAC via a low-pass filter. The signal is then
routed through the line output of DAC (LHPOUT), high pass filtered and routed to the
Phone_In_IHF input. This drives the internal speaker via the SPKRout driver.
This mode is entered when an audio accessory (mono/ stereo headset, loopset, basic ca r kit)
is connected to the system connector. The routing of the audio signal is identical for all accessories (except for the stereo headset), but gain control depends on the accessory used.
The call is created by the CMT. The uplink signal is generated by the external microphone and
transferred to the UEM MIC2 input, after which the MIC2B bias voltage and MIC2P/N inputs
are enabled on the UEM.
The downlink audio signal is routed through the single-ended XEAR output driver by the UEM.
The mono XEAR output is connected to the MICIN input of the DAC via a lo pes filter. Then signal is routed through L
Accessories are driven via the system connector using the L
stereo headset is used also the R
OUT
and R
drivers of DAC to the L
OUT
driver is connected. Both channels play the same mono
OUT
and RIN inputs of the LM4855.
IN
driver of LM4855. When a
OUT
audio signal.
APE audio mode
This mode is entered when a user starts a multimedia application (e.g. MP3, AAC etc.) or in
the case of ringing tones/ other notification tones played via the IHF speaker or the system connector.
When an MP3 is played, encoded data is read from the MMC card and the decoding is performed by OMAP1510. After decoding, the raw linear data is sent to the external audio DAC as
a 16-bit PCM audio through the I2S connection. The DAC performs the digital-to-analogue-audio conversion.
For playback and streaming of digital audio, synthesized ring tones, miscellaneous tones, and
game sounds, the APE side can be selected to drive either the IHF speaker or the system connector.
For playback via the internal speaker, the LHPOUT output on the audio DAC is used. The signal is routed to Phone_in_IHF input on LM4855.
For playback via the stereo/ mono headset or other accessories, the L
of the Audio DAC are used. These are routed to the L
/RIN inputs of the LM4855. In the case
IN
OUT
and R
OUT
outputs
of mono accessory, OMAP1510 produces a monophonic signal to DAC.
Bluetooth audio mode
Bluetooth audio data is transferred using a separate interface, MCSI.
MCSI is a serial (voice) interface with multi-channels transmission capability. There are two in-
dependent MCSI interfaces in OMAP1510 and one of them, MCSI1, is connected to the PCM
interface of BC02. The MCSI1 is a half-duplex interface and it can work as either master or
slave. This 4-wire interface has a bi-directional serial clock and frame synchronization. MCSI
has a programmable word length (from 3 to 16 bits) and frame configuration.
4. Baseband External and Internal Signals and Connections
This section describes some of the external and internal electrical connections and interface
levels on both CMT and APE side. The electrical interface specifications are collected into tables that cover a connector or a defined interface.
The interface between the baseband and the RF section is mainly handled by the UEM ASIC.
UEM provides A/D and D/A conversion of the in-phase and quadrature receive and transmit
signal paths and also A/D and D/A conversions of the received and transmitted audio signals
to and from the user interface.
The UEM supplies the analogue TXC and AFC signals to the RF section according to the UPP
DSP digital control. Data transmission between the UEM and the UPP is implemented using
two serial busses: DBUS for DSP and CBUS for MCU. There are also separate signals for PDM
coded audio. Digital speech processing is handled by the DSP inside UPP ASIC. UEM is a dual
voltage circuit: the digital parts are running from the baseband supply 1.8V and the analogue
parts are running from the analogue supply 2.78V; also VBAT is directly used.
The table below describes all the analogue signals from the baseband block to the RF block
and back. The signal names are based on the schematics.
Table 13: Analogue signals between BB and RF
Signal
Name
VCTCXOVCTCXO UPPFrequency26MHzHigh stability
FromToParameterMinTypMaxUnitFunction
clock signal for
the logic circuits,
AC coupled. Distorted sinewave
e.g. sawtooth.
The row and column lines of the UI are controlled by OMAP1510 and backlights by UEM.
Figure 7, “BB UI connections,” describes the BB user interface connections:
Figure 7:BB UI connections
Keyboard
LCD
Display
IR Link
Earpiece
IHF
speaker
Baseband
Microphone
Vibra
Pop-Port
System Connector
■ S60 - LCD interface
The user interface features a 176x208 pixel active matrix colour TFT display with 65536 colours.
The backlight voltage is generated using a regulator (D4451). Figure 8, “Interface connections.,” shows the LCD interface connections:
In NHL-12, white LEDs are used for LCD lighting and blue for keypad lighting. There are four
blue LEDs for keypad backlight. All LEDs have their own series resistors. A step-up DC-DC
converter is used as a LED driver.
Table 14: DC characteristics and PIN assignments
Pin no.Symboli/ODescription
1GNDGround
2
3
4
5D1Bi-directionalData bus
6D2Bi-directionalData bus
7D3Bi-directionalData bus
8GNDGround
9
10
11
12LEDinPower supplyLED anode
13LEDoutPower supplyLED cathode
14L_GNDGroundGuard ring ground for LEDs
15ICSInputChip select (low active)
16
17
18
IWR
GND
D0
VDDI
VDD
LGND
DAC
GND
D7
Input
Ground
Bi-directional
Power supply
Power supply
Ground
Input
Ground
Bi-directional
Memory write enable (low active
Data bus
Supply voltage for digital circuits
Supply voltage for analogue circuits
Guard ring ground for LEDs
Data/command information signal
Data bus
19D6Bi-directionalData bus
20D5Bi-directionalData bus
21D4Bi-directionalData bus
22TFOutputTearing effect
23
NHL-12 features a built-in VGA camera.
The camera control interface operates by I2C bus.
The camera module itself is assembled into the metal frame and connected to the PWB via a
20-pin spring connector.
Camera powering voltages, V28&V18, are routed through the X4450 connector.
The keyboard interface of OMAP1510 is a 6x5 matrix interface. The keyboard interface pins
are normal IOs with 30/70 decision limits at 2,8 operating voltage: 1.96V high level an d 0,84V
low level.
Bluetooth provides a fully digital link for communication between master unit and one or more
slave units. The system provides a radio link that offers a high degree of flexibility to support
various applications. Data and control interface for a low power RF module is provided. Data
is regulated between the master and the slave.
The Bluetooth system in NHL-12 is compliant with the Bluetooth specification V1 .1. The system
is based on single chip Bluetooth solution, BC02. The chip contains radio and baseband parts
as well as MCU and on-chip ROM memory. Together with some external components (matching components, filter, balun etc.) and an antenna, it forms the Bluetooth system, which can be
attached to the host (OMAP1510). Bluetooth components are mounted directly to the PWB.
UEM contains the SIM interface logic level shifting. SIM interface supports 3V and 1.8V SIMs.
SIM supply voltage is selected by a register in the UEM. It is only allowed to change the SIM
supply voltage when the SIM IF is powered down.
The SIM interface is powered up when the SIMCardDet signal indicates "card in". This signal
is derived from the BSI signal.
connector. It consists of a charging plug
socket and system connector. The Pop-Port is a feature-based interface. The accessory contains information about its features (ACI ASIC) and it is detected with a fully digital detection
procedure.
TM
Four new functions are introduced with the Pop-Port
system connector interface:
•Accessory control interface (ACI)
•Power out
•Stereo audio output
•Universal serial bus (USB)
Table 20: Pop-port
TM
functions
FunctionNote
ChargingPads for 2-wire charging in cradles
Audio4-wire fully differential stereo audio output
Power supply for
2.78V/70mA output to accessories
accessories
ACI (Accessory Con-
Accessory detection/removal & controlling
trol Interface)
FBUSStandard FBUS, Fast FBUS
Note! NHL-12 does not support accessories using
FBUS serial interface.
USB (default)USB v.2.0 device mode (full speed 12M)
9XMIC NNegative audio in signal
10XMIC PPositive audio in signal
11HSEAR NNegative audio out signal.
Max bandwidth from the phone
12HSEAR PPositive audio out signal.
Max bandwidth from the phone
13HSEAR R NNot connected or grounded in mono.
14HSEAR R PNot connected or grounded in mono.
■ Universal Serial Bus (USB)
The USB interface of OMAP1510 supports the implementation of a full speed device, fully compliant to USB2.0 standard. NHL-12 uses an integrated USB transceiver.
OMAP1510 can provide a maximum of three sets of USB ports. One set is an integrated USB
transceiver and the other two sets are LVCMOS I/O pins that implement interfaces to external
transceivers. However, only the first set is available by default and used in the NHL-12 engine.
■ Accessory Control Interface (ACI)
ACI (Accessory Control Interface) is a point-to-point, bi-directional serial bus. ACI has two main
features: 1) detecting the insertion and/or removal of an accessory device and 2) acting as a
data bus.
Third feature provided by ACI is to identify and authenticate a specific accessory which is connected to the system connector interface.
All accessories cause headint interrupt when connected to or disconnected from the system
connector. The insertion of an accessory generates a headint interrupt by pulling the ACI line
down. When no accessory is present, the UEM’s internal headint pull-up resistor keeps the line
.
high
All accessories have a common detection start sequence, when phone gets headint interrupt
from high to low transition in the ACI pin.
Figure 12:Principle schematics of ACI accessory and engine
VOUT (Accessory Voltage Regulator)
An external LDO Regulator is needed for accessory power supply purposes. All ACI accessories require this power supply. Regulator input is connected to the battery voltage VBAT and
output is connected to the Vout pin. The regulator is controlled via UPP (On/Off-function).
The hookInt signal is generated by creating a short circuit between the headset microphone
signals. An LP filter is needed on the hookInt input to filter the audio signal. In this mode, the
earpiece signal on the HF and HFCM pins is in the opposite phase. The earpiece is driven differentially.
When no accessory is present, the hookInt signal is pulled up with the UEM resistor. When the
accessory is inserted and the microphone path is biased, the hookInt signal decreases to 1.8V
due to the microphone bias current flowing through the resistor. When the microphone button
is pressed, the microphone signals are connected together, and the hookInt input will get half
of micbias dc value 1.1 V. This change in DC level causes the hookInt comparator output to
change state, in this case from 0 to 1. The button can be used for answering incoming calls but
not to initiate outgoing calls.
Table 23: HookInt signals
SignalMinNomMaxUnit
VFLASH12.72.782.86V
MICB22.02.12.25
600VuA
Vhook11.251.351.45V
■ Charging
NHL-12 can be charged via a DC-plug or charging pins on the system connector. Only 2-wire
charging is supported.
NHL-12 uses a 3.5mm DC-plug. 3-wire chargers are supported, but 3-wire charging is not. In
practice this means that the 3-wire chargers are internally connected (charger control wire connected to GND) as 2-wire chargers. 1Hz PWM signal is used to control UEM's charge switch.
VCHAR pins of system connector
The VCHAR and ChargeGND pin are directly connected to the normal charger lines of the DCplug.
XBUS is the main communication interface between the CMT and APE engines. This 6-pin interface is a combination of a general 4-pin UART based interface and two wake-up signals.
XBUS has no test points and the signals are routed in the inner layers of the PWB.
XABUS
XABUS is a synchronous serial interface used for uncompressed PCM audio data transfer between the DSPs of UPP (CMT) and OMAP1510 (APE).
■ External serial interfaces
MMC interface
The MMC interface consists of a control block in OMAP1510, MMC regulator and EMC protection ASIP (R5200). MMC interface is a serial bus with three wires: data, command and clock
run at 16MHz. The regulator (N5200) output is VMMC.
IrDA interface
NHL-12 uses a TDFU5103 IR-module (V4451). It is compatible with 1.152Mbit IrDA 1.3.
Speeds up to 115kbits/sec are supported. Operating voltages are VBAT and V28.
USB interface
Pop-Port
compliant access. The interface consists of a USB regulator (N2001) supplying V33 to
OMAP1510 USB control block, and USB ASIP (R2003) for EMC protection.
TM
system connector has pins for USB interface, for a USB 2.0 full speed (12Mb/s)
This section is a guide for localizing and repairing electrical faults in NHL-12 baseband.
Before any service operation you must be familiar with the NHL-12 product and module level
architecture. You have to be also familiar with the NHL-12 specific service tools such as the
Phoenix service software and flashing tools.
When the phone is powered on, self-test functions are executed and if one or more self-test
functions fails, the message “Contact Service” is shown on the display.
This fault means that the phone software is able to run and thus the watchdog of UEM can be
served.
MCU self-test cases can be split into two categories: the ones that are executed during power
up and the ones that are executed only with a PC connected. These tests and the items included are as follows:
Figure 14:MCU self-tests
If some self-test failed, kindly refer to the relevant chapter in this troubleshooting document.
NHL-12 has three memory components installed on the main PWB. SDRAM and NAND components are interfaced with OMAP1510, while CMT flash is interfaced with the UPP8M ASIC.
You can flash the phone to find which one is causing problems. The necessary steps are described below. Phoenix error messages displayed during the flashing process help on defining
what is wrong. To be able to flash the device, the majority of device BB area components must
function properly.
If the device turns off without any visible reason, there may be problems in the following areas:
•UEM watchdog (WD) problem (WD is not updated by SW)
•BSI line problem (BSI line is floating => contact failure)
•Battery line problem
•Soldering problem
The most likely reason is UEM WD, which turns the device off after about 32 seconds if SW is
jammed.
This may caused by a software problem, UPP8M problem (Not served by SW), UEM or memory malfunctions.
The following tests are recommended:
•General power checking
•Clocks
•Memory testing
•Serial Interface
If there is something wrong in the BSI line, the device seems to be dead after the power key is
pressed. However the regulators of the device are on a few seconds before the power down
mode.
This mode can easily be detected from the current consumption of the device. After a few seconds the current consumption drops almost to 0 mA.
In this case check the following components and/or their soldering:
•Battery connector X2020
•BSI pull up R2201 and series resistor R2202
•UEM D2200 (pin number C2)
If the phone boots to TEST or LOCAL mode with a normal battery, BSI is short circuited to
ground. Check EMI-filter and filtering capacitors, which are located in the BSI.
General power checking
For power checking, use service tool SF-8.
Battery voltage should be at least 3.6V.
After disassembling the phone, use module jig MJ-13.
If ADC Offset is over limits: Inspect the BSI line and its components (R2202, Pull-up resistor
R2201). If these are OK, change the UEM.
If BSI Gain is over limits: Inspect the BSI line and its components (R2202, Pull-up resistor
R2201). If these are OK, change the UEM.
If Vbatt Offset and Gain are over limits: Inspect Vbatt lines and its components.
If Vchar is over limits: Inspect components, which are connected to the Vchar line: V2020,
F2020 and L2020
If Ichar is over limits: Inspect components which are connected at Vchar line. If those are OK,
First change current sense resistor (R2200), if calibration is not successful, change the UEM.
You can check calibration by using ADC-readings. Known voltages, currents and resistance
are fed and read by ADC-readings. These read values and known values can be compared.
ADC-reading
Divided and scaled battery voltage, Charger voltage, Charger current, BSI and Btemp values
can be read by this tool. Read values a few times before you can be sure that results are accurate.
NOTE: IF Vbatt Scaled and Divided unit results are different default calibration valu es are used.
In this case perform EM-calibration to get full performance of the phone.
Always check the backup battery visually for any leakage or any other visual defect.
Check that the backup battery is correctly mounted in the device before closing the cover.
Check with Phoenix that backup battery is OK.
Measure the voltage of backup battery:
•Normal operation when the voltage is > 2.0V
•Fully charged when the voltage is about 3.2V (because of large internal impedance voltage won’t stay above 3.0V a long time after charging is disabled)
Enable backup battery charging (start to charge main battery or boot de vice to LOCAL or TEST
mode).
Measure the voltage of the backup battery during charging. It should rise, if it is not 3.2V, yet.
When the voltage is over 2.0V for sure, check the backup b attery with Phoenix. If not OK, then
D2200 is probably faulty.
Ensure that the RTC is running.
■ Charging troubleshooting
Use the BL5-C battery and JBV-1 calibration set to test charging.
NOTE: power supply cannot be charged, if it does not have a current sinking capability.
When you are charging a totally empty battery, remember that start-up charging might take a
little bit longer time than normally. During this time the display is blank.
If a charger is not of Nokia approved type and its current and voltage are not within Nokia charger window, software does not start charging and “NOT CHARGING” is displayed. The voltage
should be between 5.3V - 9.5V and current between 200mA – 900mA
Remove and reconnect the battery and charger a few times before you start to measure the
device. This check ensures that the fault really exists.
The main clock signal for the CMT is generated from the voltage controlled crystal oscillator
VCTCXO. This 26 MHz triangle wave clock signal is supplied to OSC_IN pin of Helgo and out
to UPP8M. Inside the UPP8M, the clock frequency is divided to 13 MHz and then fed to RFCLK.
In SLEEP mode, the VCTCXO is off. UEM generates a low frequency clock signal (32.768 kHz)
that is fed to UPP8M and ZOCUS.
When the flashing of the device does not succeed, but powering is OK, follow these instructions.
Note: The absence of clocks may indicate that the device (set phone to LOCAL mo de when the
sleep is not allowed or press buttons so that phone is not in sleep mode) is in sleep mode. Make
sure that the device is not in sleep during clocks measuring.
IMPORTANT: Clock signals have to be measured with 1MW (or greater) probes!
•Measure signal from G7200. This should be 26Mhz clock signal.
•Check that the crystal oscillator (B2200) is oscillating at 32.768kHz frequency. If
not, change B2200. If OK, measure sleepclk from test point J2802. Frequency
should be the same, 32.678kHz. If not, change the UEM.
The main clock signal for the CMT is generated from the voltage controlled crystal oscillator
VCTCXO. This 26 MHz triangle wave clock signal is supplied to OSC_IN pin of Helgo and out
to UPP8M. Inside the UPP8M, the clock frequency is divided to 13 MHz and then fed to RFCLK.
In SLEEP mode, the VCTCXO is off. UEM generates a low frequency clock signal (32.768 kHz)
that is fed to UPP8M and ZOCUS.
When the flashing of the device does not succeed, but powering is OK, follow these instructions.
Note: The absence of clocks may indicate that the device (set phone to LOCAL mo de when the
sleep is not allowed or press buttons so that phone is not in sleep mode) is in sleep mode. Make
sure that the device is not in sleep during clocks measuring.
IMPORTANT: Clock signals have to be measured with 1MW (or greater) probes!
•Measure signal from G7200. This should be 26Mhz clock signal.
•Check that the crystal oscillator (B2200) is oscillating at 32.768kHz frequency. If
not, change B2200. If OK, measure sleepclk from test point J2802. Frequency
should be the same, 32.678kHz. If not, change the UEM.
CBUS is a three wire serial interface between the main baseband components. The bus consists of data, clock and bus_enable signals. In NHL-12 the bus is connected from UPP8M to
ZOCUS and UEM. UPP8M takes care of controlling the traffic on the bus. If needed, CBUS can
also be controlled by DSP. The CBUS electrical interface consists of a clock pin (CBusClk) , a
serial data input/output pin (CBusDa) and an enable pin (CBusEnX).
The transmission protocol used on CBUS is simple. One frame consists of an address byte,
read/write flag (write = low) and 1 to 32 data bits (MSB first). Actually, the address byte is a
combination of a 3-bit device address and a 5-bit register address. UPP writes data to and
reads data from CBUS at the falling edge of CBusClk, while the slave device (UEM) uses the
rising edges for both operations.
If you are able to get the phone to boot up and can reach Phoenix BB self tests, it is possible
to test the functionality of each component attached to Cbus.
Use:
•ST_CURRENT_GAUGE_IF TEST
•ST_UEM_CBUS_IF_TEST to test UEM Cbus interface
If an error is found while testing any of the above components, you should replace the failing
component.
FBUS
FBUS is a two wire Rx and Tx interface between the UPP and flash/test interface. Th e bus goes
through the UEM which adjusts the voltage levels to suit UPP8M. The interface voltage level
on the phone flash/test pad pattern is 2.78V and on the UPP8M end it is 1.8V. The functionality
of this interface should not affect the device boot in NORMAL, LOCAL or TEST modes. Phoenix tests can be performed through MBUS interface in the case of a failure in FBUS interface.
Flashing is not possible if there is a problem with FBUS.
MBUS
MBUS is a two wire Rx and Tx interface between the UPP and UEM. From the UEM, the MBUS
interface continues to flash/test interface as a one wire interface. The UEM also adjusts the
voltage levels. The interface voltage level on the phone flash/test pad pattern is 2.78V and on
the UPP8M end it is 1.8V. MBUS traffic between the UPP8M and UEM can be tested with
PHOENIX (ST_MBUS_RX_TX_LOOP_TEST). Flashing is not possible, if there is a problem
with MBUS.