NXP Semiconductors OM12001100 User Manual

Page 1

OM12001 - Automotive Telematics On-board unit Platform

Road Pricing - ECall

Rev. 0.75 — 14th August 2012 Preliminary Specification

Document information

Info Content Title OM12001 - Automotive Telematics On-board unit Platform Short title (1 line) OM12001 (ATOP) Subtitle Road Pricing - ECall Short subtitle (1 line) Telematics Document ID ATOP Preliminary Specification Document type Preliminary Specification Revision number 0.75 Keywords Telematics, Pay as you drive, eCall Abstract An Automotive T elematics On Board Unit Platform for Road pricing, eCall

and Telematics added value services

Page 2

NXP Semiconductors

OM12001 (ATOP)

Telematics

Revision history

Rev Date Description

0.75 9th August 2012 Numerous typos corrected

0.74 6th August 2012 Updated spec for “minus” version, ie. without NFC and security components.

0.73 1st February 2012 Added RHF indication description to label

0.72 8th December 2011 Revision history added!

Reference links updated

Updated label Added IC statement

NFC EMC section updated 2D barcode info added

Preliminary Specification Rev. 0.75 — 14th August 2012 2 of 42

Page 3

NXP Semiconductors

1. Introduction

OM12001 (ATOP) is the NXP Semiconductors platform for automotive telematics on-board units (OBU's) for applications such as road pricing and eCall, based upon the following technologies:

• GS M for communication

• GPS for localization service

• NFC for short range communication, e.g. configuration and law enforcement

• SmartMX smartcard with Java card JCOP OS for security

• J9 Virtual Machine for application portability and easy creation

• Dedicated processor for Real-Time and connection to system via Ethernet, USB,

• Targeting 10 years lifetime

Thanks to on board ATOP security resources, product developer s and manufacturers can offer products which guarantee fraud prevention and tamper evidence without extra effort for additional security precautions. These products can be used in end-to-end transa ction systems requiring Common Criteria level 4+.

ADC, CAN, UART, ...

in automotive conditions

OM12001 (ATOP)

Telematics

OM12001 (ATOP) can be used by itself as a complete solution for GPS-GSM based road pricing and eCall applications. In this case OM12001 (ATOP) just needs to be complemented with a power supply, speaker, microphone, some knobs, and an optional display. OM12001 (ATOP) provides the processing power and SW application environment resources on board to complement road pricing and eCall with some other added value telematics services.

OM12001 (ATOP) can also be applied as a 'front end' for more elaborate telematics products, by making its resources, i.e. GNSS, mobile communication, Security (ID authentication) available for use by other resources in the OBU.

2 different versions are available

• OM12001/100: Implements all the features described in this document

• OM12001/000: For market where security is not paramount, such as eCall, it does not

2. Product profile

2.1 Features

 Utility processor for interfacing with external world and house-keeping

 Application processor to run customer application code

include NFC short range communication, nor SmartMX security element

 ARM Cortex M3 micro-controller with Ethernet, CAN, USB Host and device, UART,

SPI, I2C Bus, ADCs, DAC, GPIOs, and PWMs

 Internal temperature sensor, and heating element

1. in accordance with NXP's "Knowledge-Based Qualification" ("KBQ", based upon ZVEI's Robustness Validation AEC-Q100-defined qualification tests

2. Heating element present only in OM12001/100

Preliminary Specification Rev. 0.75 — 14th August 2012 3 of 42

[1]

), using

Page 4

NXP Semiconductors

OM12001 (ATOP)

 Virtual Machine for customer application  Communication coprocessor with Quad-band GSM/GPRS terminal  Localization coprocessor with GPS receive r  Near Field Communication (NFC) controller to connect to external vignette, smart

card, mobile phone

 Security processor for providing a source of trust

 SmartMX smartcard running JCOP 2.4.1

 Mandatory and voluntary certification

 R&TTE and FCC passed for safety, EMC and RF  Pre-certification for GCF, including field test  Certification for PTCRB

 Automotive certification

 -40 to +85°C operating range  Targeting 10 years lifetime in automotive conditions

2.2 Applications

OM12001 (ATOP) can be used for Telematics applications where tamper-resistance, confidentiality, integrity, and authenticity of end-user information are required, e.g.:

 Road pricing  Pay as you drive insurance  Stolen vehicles tracking  Emergency call  ...

Telematics

2.3 Quick reference data

OM12001 (ATOP) is available with quad-band support in 2 versions

Table 1. ATOP versions

Name Description

OM12001/100 Quad-band GPRS/GSM with antenna switch, GPS, NFC, SMX,

OM12001/000 Quad-band GPRS/GSM with antenna switch, GPS, Cortex M3

3. General description

Figure 1 represents OM12001 (ATOP) connections in a typical application, with its

connection to batteries, antennas, and SIM. For communication with external world, ser ial link, GPIOs, and ADCs will connect to screen, keys, and sensors. UART, CAN or USB can be used to connect to on board computer.

Cortex M3 microcontroller with Ethernet

microcontroller with Ethernet

3. Only for OM12001/100

Preliminary Specification Rev. 0.75 — 14th August 2012 4 of 42

Page 5

NXP Semiconductors

OM12001 (ATOP)

Telematics

Fig 1. A TOP module connections

Figure 2 represents a more conceptual view of OM12001 (ATOP) from a system point of

view.

Preliminary Specification Rev. 0.75 — 14th August 2012 5 of 42

Page 6

NXP Semiconductors

Application Processor

Localization

Security Processor

NFC GPRS

Utility Processor

Fig 2. ATOP conceptual view

OM12001 (ATOP)

Telematics

4. Features

4.1 Utility processor

Three main components can be seen in Figure 2:

• Application processor: This processor will run code specific to the application

(roadtolling, insurance, ...) which is portable from one platform to another one in order to avoid recertification:

– A localization coprocessor provides accurate location information to the application – A NFC coprocessor provides connection to an external vignette to increase

application security

– A Communication coprocessor allows the application to connect to servers and

receive update and notifications, receive or generate voice call or SMS

• Security processor which provides a root of trust for signing messages to servers,

authenticate the presence of an external vignette, and run secure multiple security applications

• Utility processor: This processor takes care of all housekeeping tasks such as

connecting to external interfaces, displays, but also of power management, waking-up and booting-up the system, i.e. all support tasks which are not part of the high lev el applications but are required to make the system wor k.

A LPC1768 micro-controller is available for interfacing to external world and user interface.

 ARM Cortex M3 core running up to 100 MHz

 512 kB on-chip flash memory  64 kB SRAM memory  Dual AHB system that provides for simulta neous DMA and program execution fr om

on-chip flash with no contention between those functions.

 General Purpose DMA controller (GPDMA) on AHB that can be used with the SSP

Preliminary Specification Rev. 0.75 — 14th August 2012 6 of 42

Page 7

NXP Semiconductors

 Serial Interfaces

 High speed serial interfaces

 Analog interfaces

 Debug

OM12001 (ATOP)

Telematics

serial interfaces, the I2S port, ADCs, DAC as well as for memory transfers

 3 UARTs  2 I2Cs  1 SSP (Synchronous Serial Port) and 1 SPI  I2S output/input  PWM/Capture unit  GPIOs (multiplexed)

 Ethernet MAC with RMII interface and dedicated DMA controller  Full Speed USB 2.0 Host/Device controller with integrated PHY  2 CAN channels

 7 12 bit ADCs (successive approximation)  1 internal temperature sensor (12 bit ADC)  1 10 bit DAC

 ETJAG  Serial Wire Debug

4.2 Application processor

The application processor is actually a Virtual Machine (VM) running on the main CPU of the GSM/GPRS baseband. Using a Virtual Machine offers numerous advantages:

 portability to numerous platforms  maintainability via secure download and update mechanisms  large virtualized feature set, such as:

 secure network access (https)  cryptography  Near Field Communication (NFC)

VM has the following features:

 CDC Foundation Profile including following additional API's

 Wireless Messaging  Mobile playback  Location  Contactless Communication  Telephony  Power management

 Connection to micro-controller via message passing

4.3 Localization coprocessor

GPS reception is used for localization.

 Best in class acquisition and tracking sensitivity

 Internal separate LNA for improved sensitivity

Preliminary Specification Rev. 0.75 — 14th August 2012 7 of 42

Page 8

NXP Semiconductors

 Advanced proprietary multipath algorithms for robust low dropout tracking in very low

 SW upgradable  1 Pulse per Second (1PPS) output for synchronization with GPS system clock

4.4 GSM/GPRS coprocessor

Connection to mobile networks is provided by a certified comm un ica tio ns pr ot oc ol stack that is field tested worldwide. It runs on a single monolithic IC integrating analog and digital basebands, RF transceiver, power management, and audio codec with best-in-class RF performance and power consumption.

 32-bit ARM926EJ-S™ control processor, up to 156 MHz  Communication engine

 Audio subsystem

 SIM card interface

OM12001 (ATOP)

Telematics

signals environment

 Support for 2 antennas with internal switch  Quad-band support: GSM 850, PCS 1900, E-GSM 900, and DCS 1800  GPRS multislot class 10, class B

 HR / FR / EFR / AMR Vocoders  Noise suppression and echo cancellation  Microphone amplifier with differential input  High-performance 8 driver (500mW output power, 1% THD typ)  Digital PCM IO

 1.8/2.9V power generation  Compliant with SIM card interface in accordance with GSM11.11  Compliant with ISO7816-3 requirements

4.5 Near Field Communication coprocessor

To connect to a external device, such as vignette, mobile phone, or personalization station for a road pricing public scheme, a NFC communication link with the following features is present:

 Reader mode

 Allows simultaneous access up to two external cards  Offers baud rate up to 424 kbps  Complete NFC framing and error detection  Supports ISO14443A&B/Mifare

 Virtual Card mode

 Direct connection to battery allowing operation with the rest of system is switched

off

 Access to SmartMX in Mifare emulation mode

4.6 Smartcard & JCOP operating system

For telematics and other high value applications, it is paramount to protect against data tampering, loading of unauthorized applications, ID stealing, as well as to protect end user privacy. For this, a secured component such as a smartcard is required to be used as a root of trust.

Preliminary Specification Rev. 0.75 — 14th August 2012 8 of 42

Page 9

NXP Semiconductors

OM12001 (ATOP) relies on a SmartMX component with the following features:

 Common criteria CC EAL5+ certification according to BSI-PP-0002 protection profile  Latest built-in security features to avoid power (SPA/DPA), timing, and fault attacks  80 KB EEPROM

 6144 B RAM  200 KB ROM

 Secure cryptographic processor

For portability and to allow multiple secure application (cardlets) to run in complete isolation, OM12001 (ATOP) offers a Java Card Open Platform operating system (JCOP). V2.4.1 based on independent, third party specifications, i.e. by Sun Microsystems, the Global Platform consortium, the International Organization for Standards (ISO), EMV (Europay, MasterCard, and VISA) and others.

OM12001 (ATOP)

Telematics

 EEPROM with typical 500000 cycles endurance and minimum 20 years retention

time

 75+ KB available for customer applications

 High-performance secured Public Key Infrastructure (PKI)  Secured dual/triple-DES coprocessor  Secured AES coprocessor

SmartMX family was designed to service high volume, single- and multi-application markets such as eGovernment e.g. Smart Passport, banking/finance, mobile communications, public transportation, pay TV, conditional access, network access, and digital rights management, thus ensuring applications running on OM12001 (ATOP) can rely on the highest level of security available.

4.7 Debug and Security

For application development, but also field return analysis, debug capabilities are a must. However the observability, test and control capabilities given by debug could be used for device tampering.

That is why ATOP debug capabilities are locked until proper authentication. Additionally, security features are present to ensure that only signed SW is executed.

For debug, the following features are present:

 LPC1768 MCU

 CPU debug via JTAG or Serial Wire Debug interface  Unique Serial Number  Core Read Protection with multiple levels

For security, the following features will protect against unauthorized debug, code tampering, and insertion:

 Observability

 JTAG access locked down until authentication is performed  All sensitive bus are buried down in the PCB

 Code authentication and integrity

 Code is signed with RSA to ensure authentication and checked at boot

Preliminary Specification Rev. 0.75 — 14th August 2012 9 of 42

Page 10

NXP Semiconductors

4.8 Battery and Power management

Thanks to its integration, OM12001 (ATOP) can be connected directly to a mobile phone battery. All voltage conversion and battery charging management will be handled by OM12001 (ATOP).

 Direct connection to mobile phone type battery

 Battery charging management

 Support large voltage range

 Integration of all required LDO and DC/DC conve rt er s

OM12001 (ATOP)

Telematics

 Optional connection to coin cells for RTC

 Full HW and SW support of single cell Li-Ion, Li-Ion polymer battery with voltage,

temperature and charge current monitoring

 3.1V to 5.5V for Application processor and coprocessors whenever no connection

to GSM network is active (Airplane mode)

 3.4 to 4.8V for Application processor and coprocessors when connection to

network is active

 3V to 5.5V for Utility processor

Thanks to its use of highly integrated components, optimized for power co nsumptio n, in a typical application battery charge.

Separate power supply pins are provided for microcontroller, RTC, and the rest of the system, so that each part can be separately disabled.

The utility micro-controller can be programmed to wake up OM12001 (ATOP) on external (CAN, GPIO, ...) or RTC events. In this mode, less than 150 µA of current will be drawn.

1 µA are drawn by RTC if functionality is required. For the rest of the system, a 50-100 µA leakage current can be expected (assuming

charger input is not active).

5. Ordering information

Please refer to OM12001 release note for ordering information.

6. Functional description

6.1 LPC1768 Micro-controller

LPC1768 will be responsible for tasks such as:

, OM12001 (A TO P) can function for about 30 days on a single 70 0 mAh

• booting up the system

• handling RTC and regular wake-up

• interfacing with external sensors, display, buttons via I2C, SPI, UART, ...

• communicating with others car’s units via CAN, UART, Ethernet, ...

• controlling operator access for firmware upgrade, data retrieval via USB, UART, ...

4. Car being driven for 1h per day.

Preliminary Specification Rev. 0.75 — 14th August 2012 10 of 42

Page 11

NXP Semiconductors

Except for a few services provided by NXP to handle communication between the application running on Virtual Machine and virtualized external devices, Utility processor will be completely available to the system integrator.

6.1.1 General features

• ARM Cortex-M3 microcontroller, running up to 100 MHz

• 512 kB on-chip Flash Program Memory with In-System Programming (ISP) and

• 32 kB Static RAM with local code/data bus for high-performance CPU access

• Two 16 kB Static RAM blocks with separate access paths for higher throughput, for

• Multilayer AHB matrix interconnect with separate bus for each AHB master

• Advanced Vectored Interrupt Controller, supporting up to 32 vectored interrupts

• Eight channel General Purpose DMA controller (GPDMA) on the AHB multilayer

• Serial interfaces available externally

• Other APB Peripherals

OM12001 (ATOP)

Telematics

In-Application Programming (IAP) capabilities. Single Flash sector or full-chip erase in 400 ms and 256 bytes programming in 1 ms. Flash program memory is on the ARM local bus for high performance CPU access

– 10000 erase cycles – 10 years retention powered on, 20 years powered off – First 8 erase block are 4 KB large, others are 32 KB large

Ethernet, USB, DMA memory as well as for CPU code and data. These SRAM blocks may be used for Ethernet, USB, and DMA memory, as well as for general purpose CPU instruction and data storage for general purpose SRAM

matrix that can be used with the SSP, serial interfaces, the I2S port, as well as for memory-to-memory transfers

– USB 2.0 Full-speed Device/Host controller with on-chip PHY and associated DMA

controller

– Three UARTs with fractional baud rate generation, one with modem control I/O,

one with IrDA support, all with FIFO. These reside on the APB bus

– One SSP controller with FIFO and multi-protocol capabilities, as well as a SPI port,

sharing its interrupt. The SSP controller can be used with the GPDMA controller and reside on the APB bus

– Tw o I2C interfaces reside on the APB bus. The second and third I2C interfaces are

expansion I2C interfaces with stan dard port pins rather tha n special open-drain I2C pins

– I2S (Inter-IC Sound) interface for digital audio input or output, residing on the APB

bus. The I2S interface can be used with the GPDMA

– Tw o channels with Acceptance Filter/FullCAN mode residing on the APB bus

– 12 bit A/D converter with input multiplexing among 7 external pins – 10 bit D/A converter with DMA support – Four general purpose timers with a total of 8 capture inputs and ten compare

output pins each. Each timer block has an external count input

Preliminary Specification Rev. 0.75 — 14th August 2012 11 of 42

Page 12

NXP Semiconductors

• Standard ARM Test/Debug interface for compatibility with existing tools

• Three reduced power modes: Idle, Sleep, and Power-down

• Four external interrupt inputs. In addition every PORT0/2 pin can be configu red as an

• Processor wake-up from Power-down mode via any interrupt able to operate during

• Two independent power domains allow fine tuning of power consumption based on

• Brownout detect with separate thresholds for interrupt and forced reset

• On-chip Power On Reset

• On-chip crystal oscillator with an operating range of 1 MHz to 24 MHz

• On-chip PLL allows CPU operation up to the maximu m CPU rate witho ut the nee d for

• Versatile pin function selections allow more possibilities for using on-chip peripheral

OM12001 (ATOP)

Telematics

– One PWM/Timer block with su pport for three-phase motor control – Real-Time Clock (RTC) with separate power pin; clock source can be the RTC

oscillator or the APB clock oscillator

– Watchdog Timer. The watchdog timer can be clocked from the internal RC

oscillator, the RTC oscillator, or the APB clock

edge sensing interrupt

Power-down mode (includes external interrupts, RTC interrupt)

needed features

– For CAN and USB, a clock generated internally to OM12001 (ATOP) is provided,

or an external crystal can be used

a high-frequency crystal. May be run from the main oscillator, the internal RC oscillator, or the RTC oscillator

functions

Preliminary Specification Rev. 0.75 — 14th August 2012 12 of 42

Page 13

NXP Semiconductors

6.1.2 Block diagram

OM12001 (ATOP)

Telematics

Fig 3. LPC1768 block diagram

Preliminary Specification Rev. 0.75 — 14th August 2012 13 of 42

Page 14

NXP Semiconductors

6.1.3 Ethernet

Ethernet block supports bus clock rates of up to 100 MHz. The Ethernet block contains a full featured 10 Mbit/s or 100 Mbit/s Ethernet MAC designed to provide optimized performance through the use of DMA hardware acceleration. Featur es include a generous suite of control registers, half or full duplex operation, flow control, control frames, hardware acceleration for transmit retry, receive packet filtering and wake-up on LAN activity. Automatic frame transmission and reception with scatter-gather DMA off-loads many operations from the CPU.

The Ethernet block and the CPU share the ARM Cortex-M3 D-code and system bus through the AHB-multilayer matrix to access the various on-chip SRAM blocks for Ethernet data, control, and status information.

The Ethernet block interfaces between an off-chip Ethernet PHY using the Reduced MII (RMII) protocol and the on-chip Media Independent Interface Management (MIIM) serial bus.

6.1.4 USB

LPC1768 features an USB interface with a device and host controller with on-chip PHY.

OM12001 (ATOP)

Telematics

6.1.4.1 USB device controller

The device controller enables Full Speed (12 Mbit/s) data exchange with a USB Host controller. It co nsists of a register interface, serial interface engine, endpoint buffer memory, and a DMA controller . Th e ser ial interfa ce en gine de codes th e USB da ta stream and writes data to the appropriate endpoint buf fer. The status of a completed USB transfer or error condition is indicated via status registers. An interrupt is also generated if enabled. When enabled, the DMA controller transfers data between the endpoint buffer and the on-chip SRAM.

6.1.4.2 USB host controller

The host controller enables full- and low-speed dat a exchange with USB devices attached to the bus. It consists of a register interface, a serial interface engine, and a DMA controller. The register interface complies with the OHCI specification.

6.1.5 CAN

6.1.5.1 Description

The Controller Area Network (CAN) is a serial communications protocol which efficiently supports distributed real-time control with a very high level of security. Its domain of application ranges from high-speed networks to low cost multiplex wiring. The CAN block is intended to support multiple CAN buses simultaneously, allowing the device to be used as a gateway, switch, or router among a number of CAN buses in industrial or automotive applications.

6.1.5.2 Features

• Two CAN controllers and buses

• Data rates to 1 Mbit/s on each bus

• 32-bit register and RAM access

• Compatible with CAN specification 2.0B, ISO 11898-1

Preliminary Specification Rev. 0.75 — 14th August 2012 14 of 42

Page 15

NXP Semiconductors

• Global Acceptance Filter recognizes 11-bit and 29-bit receive identifiers for all CAN

• Acc ep tance Filter can pr ov ide FullC AN- s tyle automatic reception for selected

• Full CAN messages can generate interrupts

6.1.6 Power saving modes

6.1.6.1 Peripheral and clock control

As shown in Figure 4 clock sources, re-configuring PLL values, and/or altering the CPU clock divider value. This allows a trade-off of power versus processing speed based on application requirements. In addition, Peripheral Power Control allows shutting down the clocks to individual on-chip peripherals, allowing fine tuning of power consumption by eliminating all dynamic power use in any peripherals that are not required for th e application.

The LPC1768 include three independent oscillators. These are the main oscillator, the IRC oscillator, and the RTC oscillator. Each oscillator can be used for more than one purpose as required in a particular application. Any of the three clock sources can be chosen by software to drive the main PLL and ultimately the CPU.

OM12001 (ATOP)

Telematics

buses

Standard Identifiers

, the CPU clock rate can also be controlled as needed by changing

Following reset, the LPC1768 will operate from the Internal RC oscillator until switched by software. This allows systems to operate without any external crystal and the bootloader code to operate at a known frequency. Main oscillator will be driven by an optional

external crystal on customer board. Its presence might be required if an accurate clock is necessary, for instance for USB or HS CAN compliancy.

Fig 4. LPC1768 clock generation

Preliminary Specification Rev. 0.75 — 14th August 2012 15 of 42

Page 16

NXP Semiconductors

6.1.6.2 Power modes

The LPC1768 support a variety of power control features. There are four special mode s of processor power reduction:

• Sleep

• Deep-sleep

• Power-down

• Deep power-down

The CPU clock rate may also be controlled as needed by changing clock sources, reconfiguring PLL values, and/or altering the CPU clock divider value. This allows a trade-off of power versus processing speed based on application requirements. In addition, Peripheral Power Control allows shutting down the clocks to individual on-chip peripherals, allowing fine tuning of power consumption by eliminating all dynamic power use in any peripherals that are not required for th e application. Each of the peripherals has its own clock divider which provides even better power control.

Integrated PMU (Power Management Unit) automatically adjust internal regulators to minimize power consumption during Sleep, Deep sleep, Power-down, and Deep power-down modes.

OM12001 (ATOP)

Telematics

The LPC1768 also implement a separate power domain to allo w turning off power to the bulk of the device while maintaining operation of the RTC and a small set of registers for storing data during any of the power-down modes.

Sleep mode: When Sleep mode is entered, the clo ck to th e cor e is stopped. Resum ption

from the Sleep mode does not need any special sequence but re-enabling the clock to the ARM core.

In Sleep mode, execution of instructions is suspended until either a Reset or interrupt occurs. Peripheral functions continue operation during Sleep mode and may generate interrupts to cause the processor to resume execution. Sleep mode eliminates dynamic power used by the processor itself, memory systems and related controllers, and internal buses.

Deep-sleep mode: In Deep-sleep mode, the oscillator is shut down and the chip receives

no internal clocks. The processor state and registers, peripheral registers, and internal SRAM values are preserved throughout Deep-sleep mode and the lo gic levels of chip pins remain static. The output of the IRC is disabled but the IRC is not powered down for a fast wake-up later.

The RTC oscillator is not stopped because the RTC interrupts may be used as the wake-up source. The PLL is automatically turned off and disconnected.

The Deep-sleep mode can be terminated and normal operation resumed by either a Reset or certain specific interrupts that are able to function without clocks. Since all dynamic operation of the chip is suspended, Deep-sleep mode reduces chip power consumption to a very low value. Power to the flash memory is left on in Deep-sleep mode, allowing a very quick wake-up.

Preliminary Specification Rev. 0.75 — 14th August 2012 16 of 42

Page 17

NXP Semiconductors

Power-down mode: Power-down mode does everything th at Deep-sleep mode does, but

also turns off the power to the IRC oscillator and the flash memory. This saves more power but requires waiting for resumption of flash operation before execution of code or data access in the flash memory can be accomplished.

Deep power-down mode: The Deep power-down mode can only be entered fr om the

RTC block. In Deep power-down mode, power is shut off to the entire chip with the exception of the RTC module and the RESET pin. The LPC1768 can wake up from Deep power-down mode via the RESET pin or an alarm match event of the RTC.

Wake-up interrupt controller: The Wake-up Interrupt Controller (WIC) allows the CPU to

automatically wake up from any enabled priority interrupt that can occur while the clocks are stopped in Deep sleep, Power-down, and Deep power-down modes.

The WIC works in connection with the Nested Vectored Interrupt Controller (NVIC) . When the CPU enters Deep sleep, Power-down, or Deep power-down mode, the NVIC sends a mask of the current interrupt situation to the WIC.This mask includes all of the interrupts that are both enabled and of sufficient priority to be serviced immediately. With this information, the WIC simply notices when one of the interrupts has occurred and then it wakes up the CPU.

OM12001 (ATOP)

Telematics

The WIC eliminates the need to periodically wake up the CPU and poll the interrupts resulting in additional power savings.

6.1.7 RTC

The RTC on the LPC1768 is designed to have extre mely low power consumption, i.e. less than 1 µA. The RTC will typically run from the main chip power supply, conserving battery power while the rest of the device is powered up. When operating from a battery, the RTC will continue working down to 2.1 V. Battery power can be provided from a standard 3 V Lithium button cell.

An ultra-low power 32 kHz oscillator will provide a 1 Hz clock to the time counting portion of the RTC, moving most of the power consumption out of the time counting function. The RTC contains a small set of backup registers (20 bytes) for holding data while the

main part of the LPC1768 is powered off. The RTC includes an alarm function that can wake up the LPC1768 from all reduced

power modes with a time resolution of 1 s.

7. Application design-in information

7.1 Battery charging

OM12001 (ATOP) natively handles Lithium Ion battery technology. There are 3 distinct modes for battery charging, depending on the battery voltage:

• trickling mode: In this mode, ATOP will detect whether battery is dead (i.e. voltage

drop as soon as a small current is applied). If that is not the case, a small curr en t of 1 mA will be applied until the voltage is higher than 1.5V, and then ATOP will switch to pre-charge mode

Preliminary Specification Rev. 0.75 — 14th August 2012 17 of 42

Page 18

NXP Semiconductors

• precharge mode: Precharge mode is completely under HW control and will continue

• fast charge: If battery level is higher than 3.1V (i.e. enough for baseba nd to boot) and

OM12001 (ATOP)

Telematics

until the battery voltage is high enough so tha t baseband can boot. During precharge, A TOP will provide a 200 mA current. As SW is not yet booted, temperature will not be controlled, i.e. precharge will occur even if battery is outside of advised range for a battery

there is voltage on Vcharge for more than 10 ms, then OM12001 (ATOP) will switch to SW charge mode. SW will initiate a fast charge with Constant Current - Constant Volt age (CC-CV) method as described in Figure 5 on the charger falls below 50 mA or whenever overvoltage/overcurrent is detected or temperature is outside of allowed range (typically 0-50°C). Limiting and dynamic values can be found in Table 4

. It will stop when the current drawn

and Table 26

Fig 5. Constant Current - Constant Voltage charging method

Figure 6 presents a typical implementation of the charging circuitry. A 0.1 Ohm resistor is used as a shunt to measure charge current. 2 PMOS transistors are used respectively to enable charging, avoid reverse leakage from battery to charger, and regulate current. They should be properly dimensioned for power dissipation.

Preliminary Specification Rev. 0.75 — 14th August 2012 18 of 42

Page 19

NXP Semiconductors

OM12001 (ATOP)

Telematics

Fig 6. Charging circuitry

Additionally other pins should be connected as follows:

• VBAT_SENSE_P must be connected to the battery

• VBAT_SENSE_N must be connected to ground

• BB_BAT_THERM must be connected to a 10 kOhm pull-down, or to the battery

7.2 Application without rechargable battery

If no rechargable battery is used in the application, charging control pins must be connected as follows:

• VCHG_SNK must be connected to ground

• BB_CHARGE_[SW|REG]_CTL must be left unconnected

• BB_ICHG_[P|N] must be connected together

• VBAT_SENSE_P must be connected to VBAT_SNK

• VBAT_SENSE_N must be connected to ground

• BB_BAT_THERM must be connected to a 10 kOhm pull-down

thermistor

Preliminary Specification Rev. 0.75 — 14th August 2012 19 of 42

Page 20

NXP Semiconductors

OM12001 (ATOP)

VBAT_MC_SNK

VDD_3V0_SRC_ENA

VDD_3V0_SRC

Utility processor

LDO

7.3 Current source

OM12001 (ATOP) handles internally all its voltage conversion. For Utility Processor, a separate input, VBAT_MC_SNK, is used. Internally, a LDO, controlled by VDD_3V0_SRC_ENA (active high, with internal pull-up), will convert it to the 3V required by the Utility Processor. As described in Figure 7 externally to power external component, up to a maximum of 100 mA can b e drawn. Other limiting values can be found in Table 13

OM12001 (ATOP)

Telematics

, the output of the LDO is also available

Fig 7. VDD_3V0 current source

7.4 RTC

MCU RTC is internally supplied by the output of the LDO described in Figure 7. It can also be supplied by a separate battery such as a coin cell via VBAT_RTC_SNK so that RTC is kept in case of power loss. If this feature is not required it is advised to connect VBAT_RTC_SNK and VDD_3V0_SRC.

8. Application information

8.1 NFC antenna design

For NFC antenna design, please refer to Ref. [6] for antenna design and Ref. [7] if application requires to boost NFC signal.

Figure 8

describes the internal setup of NFC_ANT pins.

Preliminary Specification Rev. 0.75 — 14th August 2012 20 of 42

Page 21

NXP Semiconductors

OM12001 (ATOP)

Telematics

Fig 8. Internal setup of NFC antennas

R1 = 1 K, R2 = 2.7 K, CRX = 1 nF, C

= 100 NF

vmid

9. Recommended operating conditions

Table 2. Temperature

Allowed temperature range

Symbol Parameter Min Typ Max Unit Note

Module storage temperature range

Module limited operation temperature range

Module operating temperature range

-40 85 °C Before final reflow, stored in drypack

-40 85 °C All functions, except for NFC and Secure processor

-25 85 °C

Table 7 presents in more details the tests performed to guarantee module lifetime.

Preliminary Specification Rev. 0.75 — 14th August 2012 21 of 42

Page 22

NXP Semiconductors

10. Limiting values

OM12001 (ATOP)

Telematics

Table 3. Power supply

Symbol Parameter Min Typ Max Unit Note

bat_rf

Battery voltage for application processor

3.4

[1]

4.2 4.8 V Voltage range allowed in case of connection and transmission to GSM network

bat_no_rf

Battery voltage for application processor

3.1 4.2 5.5 V Voltage range allowed without connection to GMS network (i.e. airplane mode)

bat_mc

Battery voltage for

3.1 4.2 5.5 V

utility processor

bat_rtc_mc

Battery voltage for

2.0 3.3 3.6 V

utility processor RTC

bat_rtc_bb

Battery voltage for

2.0 3.0 3.15 V

[3]

application processor RTC

bat

Battery current 1800

[2]

mA Peak current to be used to

dimension decoupling capacitors (on VBAT_SNK)

[1] Note this minimum voltage should take into account the voltage drop due to the high current during transmission, i.e. for a typical battery

with a drop of 200 mV, minimum voltage is 3.6V [2] Occurs only during transmission slot (577 µs) in case of poor reception [3] It is not mandatory to connect V

active when V

is disconnected

bat

bat_rtc_pnx

as internal connection is provided, unless it is required to keep application processor RTC

Table 4. Battery charging

Handled by baseband integrated battery charging unit

Symbol Parameter Min Typ Max Unit Note

Charge

bat_empty

PreCharge

FastCharge

Charge voltage 3.2 4.8 7.5 V Empty battery current 1 mA for V Pre-charge current 160 200 240 mA pre-charge current, i.e. for

Fast charge current 200 1400 mA For V

[1]

BAT_SNK

< 3.35V

BAT_SNK

< 1.5V

> 3.35V, Settable with 100mA steps, with additional step at 450 mA

FastCharge

Fast Charge Voltage 3.45 4.2 5.5 V Settable with 50 mV step

between 3.45 to 4.9V and 2 additional points at 5.25 and

5.55V

SW_CTL

Maximum voltage allowed

--V

BAT_SNK

on BB_CHARGE_SW_CTL

SW_REG

Maximum voltage allowed

--V

CHG_SNK

on BB_CHARGE_SW_REG

[1] Charge voltage should obviously be higher than Vbat. Voltage drop into external transistors and resistors should be taken into account

Preliminary Specification Rev. 0.75 — 14th August 2012 22 of 42

Page 23

NXP Semiconductors

OM12001 (ATOP)

Telematics

Table 5. Limiting values for micro-controller pins

Symbol Parameter Conditions Min Typ Max Unit

IAmc

Imc

imc_xtal1

omc_xtal2

[1] 5V tolerant pins, i.e. all I/O with MC prefix, except for oscillator IOs [2] V

bat_mc

[3] 3-state outputs go into 3-state mode when V

Table 6. Limiting values for GSM baseband interfaces

Analog input voltage on ADC related pins -0.5 5.1 V Input voltage 5V tolerant I/O pins

other I/O pins

[1][2][3]

[2]

-0.5 5.5 V

-0.5 3.6 V Input voltage for XTAL1 Internal oscillator input 0 - 1.8 V Output voltage Internal oscillator output 0 - 1.8 V

must be present

is grounded

bat_mc

SIM interface, analog audio and PCM interface

Symbol Parameter Conditions Min Typ Max Unit

Ibb

Obb

Table 7. Limiting values for GSM antennas

Input voltage -0.4 3.2 V Input current 20 mA Output current 20 mA

Due to their ESD protection implementation GSM antennas are DC grounded

Symbol Parameter Conditions Min Typ Max Unit

IDC

maxDC

Input resistance DC voltage 1.96  Maximum current DC current 140 mA Load mismatch for all phase angles, before

20:1 VSWR permanent degradation or damage

Spurious (low bands) for all phase angles, no parasitic

12:1 VSWR oscillations > -30 dbm

Spurious (high bands) for all phase angles, no parasitic

8:1 VSWR oscillations > -30 dbm

Table 8. Limiting values for GPS passive antenna input

Due to its ESD protection implementation GPS antenna is DC grounded

Symbol Parameter Conditions Min Typ Max Unit

IDC

maxDC

Table 9. Limiting values for GPS active antenna input and antenna bias

Input resistance DC voltage 0.14  Maximum current DC current 540 mA

Symbol Parameter Conditions Min Typ Max Unit

maxDC

Preliminary Specification Rev. 0.75 — 14th August 2012 23 of 42

Maximum voltage DC voltage -25 25 V Maximum current DC current 70 mA

Page 24

NXP Semiconductors

OM12001 (ATOP)

Telematics

11. Characteristics

12. Static characteristics

12.1 Pins

Table 10. Characteristics for micro-controller pins

Symbol Parameter Conditions Min Typ Max Unit

Omc

IHmc

ILmc

IHmc

OHmc

OLmc

OHmc

OLSmc

OHSmc

Output voltage 0 3.0 V High level input voltage 2.0 V Low level input voltage 0.8 V Low level input current VI=0 V; no pull-up 3 µA High level input current VI=3.0 V; no pull-down 3 µA High level output voltage I Low level output voltage I Low level output current VOL=0.4 V 4 mA High level output current VOH=2.6 V -4 mA Low level short circuit output current VI=3.0 V High level short circuit output

current

OZmc

pdmc

pumc

Ilatchmc

Off state output current VO=3.0 or 0V; no pull - up /d own 3 µA Pull-down current VI=5 V 10 50 150 µA Pull-up current VI=0 V; -15 -50 -85 µA

I/O latchup current -1.5<VI<4.5V; Tj<125°C 100 mA

=-4 mA 2.6 V

OHmc

=-4 mA 0.4 V

OLmc

[1]

VI=0 V

<5 V 0 0 0 µA

3.0 <V

-45 mA 50 mA

[1] Only allowed for a short time period

Table 11. Characteristic for baseban d digital interface

namely SIM interface, PCM, UART, JTAG

Symbol Parameter Conditions Min Typ Max Unit

IHbb

ILbb

IHbb

ILbb

OHbb

OLbb

pubb

pdbb

iLbb

Preliminary Specification Rev. 0.75 — 14th August 2012 24 of 42

High level input voltage 2.4 V Low level input voltage 0.4 V High level input current -10 +10 µA Low level input current -10 +10 µA High level output voltage 2.7 V Low level output voltage 0.1 V Pull-up resistance 100 k Pull-down resistance 100 k Input capacitance 0.1 pF

Page 25

NXP Semiconductors

OM12001 (ATOP)

Telematics

Table 12. Characteristic for GPS digital interface

namely JTAG and GPS_UART2_RXD

Symbol Parameter Conditions Min Typ Max Unit

V V I

IHbb

ILbb

V V R R I

IHbb ILbb

OHbb OLbb pubb pdbb

High level input voltage 1.7 V Low level input voltage 0.7 V High level input current -10 +10 µA Low level input current -10 +10 µA High level output voltage 1.7 V Low level output voltage 0.7 V Pull-up resistance 60 k Pull-down resistance 75 k Output current 6 mA

12.2 Current sources

Table 13. V

dd_3v0_src

Can be used to supply external components

Symbol Parameter Min Typ Max Unit Note

dd_3v0

vdd3v0_max

V

dd_3v0

V

dd_3v0

on_dd_3v0

Output voltage 2.9 3.0 3.1 V For Tj=-40 to 125°C maximum current 100 mA Load regulation 0.0008 0.004 %/mA Line regulation -0.1 0.1 %/V For V Turn on time 240 µS Measured from the time

current source

variation

bat

VDD_3V0_SRC_ENA exceeds 1.4V

Table 14. V

sim_src

To be only used to supply SIM cards

current source

[1]

Symbol Parameter Min Typ Max Unit Note

sim_src

Output voltage 2.75 2.90 3.00 V Appropriate SIM card voltage is

1.65 1.80 1.95 V

automatically detected and selected by the software

Output current 80 mA Full power mode

3 mA Sleep mode

V

o/Vo

on_dd_3v0

Relative output voltage 50 mV/V For V Settling time 10 µS from power-down

[1] Voltage is dynamically controlled to reduce power consumption when SIM card is not accessed

12.3 Voltage references

Table 15. V

io_ref

To be used as a reference to connect to BB_* test pins (JTAG)

Symbol Parameter Min Typ Max Unit Note

V V

io_ref

o/Vo

Output voltage 2.70 2.80 2.95 V Relative output voltage 50 mV/V For V

voltage reference

variation

bat

variation

bat

Preliminary Specification Rev. 0.75 — 14th August 2012 25 of 42

Page 26

NXP Semiconductors

OM12001 (ATOP)

Telematics

Table 16. V

perm_ref

voltage reference

To be used as a reference to connect to BB_* functional pins

Symbol Parameter Min Typ Max Unit Note

perm_ref

Table 17. V

Output voltage 2.82

[1] For VBAT_SNK = 3.1V [2] For VBAT_SNK = 3.6V [3] For VBAT_SNK = 5.5V

voltage reference

adc_ref

[1]

3.0

[2]

3.18

[3]

V Follows VBAT_SNK if <3V

used as power supply reference for internal ADCs

Symbol Parameter Min Typ Max Unit Note

adc_ref

Output voltage 2.9 3.0 3.1 V For Tj=-40 to 125°C

V/V Line regulation -0.1 0.1 %/V F o r V

12.4 Clocks

Table 18. 1PPS

This pulse is synchronized with GPS system clock

Symbol Parameter Min Typ Max Unit Note

Pulse width 125 µs Jitter -50 3 50 ns Stationary and receiving 4 or more

satellites

variation

bat

Table 19. BB_EXT_CLK

This clock is coupled to GSM network

Symbol Parameter Min Typ Max Unit Note

bb_ext_clk

frequency 26/N MHz for N= 1, 2, ..., 8

156/M MHz for M=9, 10, .., 16

f/f

Table 20. Micro-controller clock

frequency drift 0.7 1 ppm

External crystal required for high speed CAN, for all other purposes, internal RC oscillator is sufficient

Symbol Parameter Min Typ Max Unit Note

mc_xtal

Crystal frequency 1 - 24 MHz In case of externally oscillator, connected

to MC_XTAL_(1|2)

(rms)mc_xtal

hmc_xtal

lmc_xtal

rmc_xtal

fmc_xtal

mc_ircl

Oscillation amplitude 0.2 - V (RMS) Clock High time t Clock Low time t

x 0.4 - ns

cycle

x 0.4 - ns

cycle

Clock rise time 5 ns Cock fall time 5 ns Oscillator frequency 3.96 4 4.04 MHz Frequency of internal RC oscillator

Preliminary Specification Rev. 0.75 — 14th August 2012 26 of 42

Page 27

NXP Semiconductors

OM12001 (ATOP)

13. Dynamic characteristics

13.1 Power consumption

All measured current consumption have been measured at 25°C with a power supply at

3.7V

Table 21. Utility processor po wer consumption

Includes LDO

Symbol Parameter Min Typ Max Unit Note

Cortex M3 at 12 MHz 7 7

[1]

mA at 25°C, code

Telematics

while(1){}

Cortex M3 at 100 MHz 42

Powerdown mode 150 µA

[1]

[2]

RTC active 1 µA backup registers saved

[1] No peripherals enabled [2] Wake-up can be initiated by event on RTC, CAN, USB and most GPIOs [3] If a separate power source such as coin cell battery is connected to VBAT_RTC_SNK and no power is supplied via VBAT_MC_SNK

Table 22. Application processor consumption characteristics

Baseband ARM and memories power consumption additionally to GSM/GPRS function

Symbol Parameter Min Typ Max Unit Note

Application processor 0

[1] Leakage currents are included in Table 23

Table 23. Communication coprocessor consumption characteristics

[1]

20 60 mA

Covers baseband RF frontend as well as memories (PSRAM and flash)

Symbol Parameter Min Typ Max Unit Note

complete GSM function network attachment

115

[1]

µAh Energy consumption

equivalent to 300s of idle mode

complete GSM function active in idle mode

complete GSM function during voice call

complete GPRS function during data transfer (Class 10: 2T+3RX)

complete GSM function

1.085

[5]

140

[2]

[5]

1.31

[3]

2.05

[4]

mA Average consumption,

assuming typical setting

114

205

[6]

220

400

[7]

for mobile network. Peak consumption for GSM/GPRS at maximum power can reach up to 1600 mA during transfer slots (577 µs)

600 µA GSM function active

in sleep mode complete GSM function

50 µA

leakage current

[3]

[1] Network dependent, assumes a typical 7s radio measurement plus 0.5s network inscription [2] BS_PA_MFRMS = 9, i.e. paging from network will be checked every 2100 ms [3] BS_PA_MFRMS = 5, i.e. p aging from network will be checked every 1175 ms. This is typically the setting used by most mobile operators

Preliminary Specification Rev. 0.75 — 14th August 2012 27 of 42

Page 28

NXP Semiconductors

[4] BS_PA_MFRMS = 2, i.e. paging from network will be checked every 470 ms [5] PCL = 19, i.e. 4.9db amplification for GSM900 [6] PCL = 7, i.e. 29.2db amplification for GSM900 [7] PCL = 5, i.e. 33.1 db amplification for GSM900

OM12001 (ATOP)

Telematics

Table 24. Security processor power consumption

Symbol Parameter Min Typ Max Unit Note

Function switched off 0 µA included in NFC

coprocessor

Function active 6 mA

Table 25. NFC coproces sor power consumption

Covers NFC and SMX

Symbol Parameter Min Typ Max Unit Note

Function switched off 2 µA Power down 35 µA RF field detection on Function active 30 mA function active with RF

90 130 mA

transmission ongoing

13.2 Battery charging

Table 26. Battery charging

Measured at 3.7V, 25°C

Symbol Parameter Min Typ Max Unit Note

Battery overvoltage detection

Battery overcurrent detection

Fast charge stop 50 mA

V

Oreg/VOreg

Relative regulator output voltage variation

I

Oreg/IOreg

Relative regulator output current variation

qvchg

Quiescent current drawn from VCHG_SNK

qbb_ighgp

Quiescent current drawn from BB_ICHG_P

qbb_ighgn

Quiescent current drawn from BB_ICHG_P

qvbat_snk

Quiescent current drawn from VBAT_SENSE_[P|N]

60 90 130 mV Battery voltage in excess of

VFAST above which fast charge is automatically disabled

190 210 230 mA Battery current in excess of

programmed current above which fast charge is automatically disabled

-1 +1 %

-12 +12 %

3mA

40 µA during charge

60 µA during charge

200 µA during charge

Preliminary Specification Rev. 0.75 — 14th August 2012 28 of 42

Page 29

NXP Semiconductors

14. Thermal characteristics

OM12001 (ATOP)

Telematics

14.1 Internal heater

As described in Table 2, OM12001 (ATOP) can operate between -40 and +85°C, except for the NFC and Security processor which are limited to a -25 to +85°C temperature range.

To ensure that operating range can be rapidly reached, an internal heater is available to heat-up the device. The internal heater is controlled by internal micro-controller pin P2.5 (active high).

Internal temperature should be monitored when heater is used. It must not be enabled for more than a few seconds if current temperature is greater than 25°C as otherwise there is a risk of destruction for the heater.

Table 27. Internal heater charac teristics

Symbol Parameter Min Typ Max Unit Note

Current drawn 500 600 700 mA Power dissipated 1600 2500 3400 mW Dependant on V

14.2 Internal temperature sensor

OM12001 (ATOP) includes an internal temperature sensor. This sensor is used by GSM baseband to tune its VCXO to achieve network lock-on but is also accessible to the internal micro-controller which can use it to.

bat

Internal micro-controller (LPC1768) has also access to this sensor to adap t its beha vior to

conditions, i.e enabling internal heater in case of low temperature, ... .

Figure 9

presents accuracy of the internal temperature measurement depending on

ambient temperature.

Preliminary Specification Rev. 0.75 — 14th August 2012 29 of 42

Page 30

NXP Semiconductors

OM12001 (ATOP)

Telematics

Fig 9. Internal temperature accuracy

14.3 Battery temperature sensor

To improve lifetime, it is recommended to avoid charging batteries, outside of the temperature range specified by their manufacturers, typically 0 to 50°C. For Lithium-Ion battery, the charger circuit inside OM12001 (ATOP) will use by default the internal temperature sensor. However, in some cases, depending on implementation, it can be expected the temperature of the battery will be significantly different from module temperature. It is then recommended to use a battery with internal sensor. OM12001 (ATOP) supports the use of an external thermistor dedicated to battery. Note that even if a separate thermistor is not used, this input is used to detect battery presence.

Table 28. Battery tempe rature sensor

Symbol Parameter Min Typ Max Unit

thermin

tol

Internal pull-up 10 k input resistor tolerance accuracy -1 1 %

15. Handling information

16. Soldering

OM12001 (ATOP) is a laminate based module with a metal cover and a Land Grid Array (LGA) at the bottom side of the product. Th e OM12001 (ATOP) can be assembled using a standard Surface Mount Technology (SMT) reflow process in a convection oven.

Figure 10

The applied profile has to fit within these limits.

Preliminary Specification Rev. 0.75 — 14th August 2012 30 of 42

and Table 29I indicate the maximum and minimum limits of the solder profile.

Page 31

NXP Semiconductors

It is recommended to use a standard no-clean SAC solder paste for a lead free assembly process.

OM12001 (ATOP)

Telematics

Fig 10. Reflow profile

17. Mounting

17.1 PCB layout

Table 29. Reflow profile parameters

Symbol Parameter Min Unit

 Temperature gradient (ramp-up) < 3 °C/s  Temperature gradient (cool-down) < 5 °C/s

Min

Max

Preheat (soak) temperature 150 to 200 °C Preheat time 60 to 180 s Time to melting 6 to 35 s Reflow temperature > 217 °C Reflow time 60 to 150 s Minimum peak temperature 235 °C Maximum peak temperature 260 °C Maximum time above 250°C 10 s Maximum time 25°C to peak temperature 8 mn

The PCB footprint design is a copy of the metal LGA pattern at the bottom side of the ATOP package.

17.2 Stencil design

The dimensions of the solder stencil apertures can be found in Figure 11. In general there are 2 aperture sizes applied for the stencil:

• 0. 7 mm dia m ete r for th e inn er pads

Preliminary Specification Rev. 0.75 — 14th August 2012 31 of 42

Page 32

NXP Semiconductors

• 0.8 mm for the outer pads

The recommendation for the stencil thickness is 150 µm.

OM12001 (ATOP)

Telematics

Fig 11. Stencil design

18. Marking

Figure 12 shows label present on the module.

5.G7-G13, H7-H13, J7, J8, J12, J13, K7, K8, K12, K13, L7, L8, L12, L13, M7-M13, N7-N13

Preliminary Specification Rev. 0.75 — 14th August 2012 32 of 42

Page 33

NXP Semiconductors

OM12001 (ATOP)

Telematics

Fig 12. OM12001/100 labelling

Labelling can be decoded as follows:

• First line: Product name, ie OM12001/100 or OM12001/000

• Second line: Serial number

• Third line: Production info, including production site, RHF-2006 indicator

• Fourth line: BOM number

• Fifth line: FCC ID, ie XXMOM12001100 or XXMOM12001000 and Notified body for

CE certification

• Sixth line: IC ID, ie 8764A-OM12001100 or 8764A-OM12001000

• Seventh line: IMEI

DataMatrix 2D barcode includes the following information:

• Serial number

• EMS Internal product code

• Date code

• Product name, ie OM12001/100 or OM12001/000

• IMEI Type Allocation Code (TAC) iteration number

, date code

6. E standing for Exempted, ie. incorporates product containing exempted Lead that do contain Halogens/Antimony. For example products with eutectic solder die-attach (HSOP/SIL-P) packages and glass-diodes containing Lead

7. 1 stands for a TAC value of 35374505 for OM12001. IMEI can be computed by concatenating TAC, the 6 last digits of serial number and Check Digit, (CD) computed with Luhn formula

Preliminary Specification Rev. 0.75 — 14th August 2012 33 of 42

Page 34

NXP Semiconductors

19. Packing information

OM12001 (ATOP) modules are packed in trays. Before packing and shipping, trays have been dry baked for 16 hours at 125°C, according to IPC/JEDEC J-Std-033B.1.

OM12001 (A TO P) has been tested accord ing to IPC/JEDEC J-STD 020D and is classified as Moisture Sensitivity Level 3 (MSL3).

20. Package outline

A T OP present s itse lf as a 33x33x3.35 mm mo dule. Ball size is 0.8 m m with a 1.6mm pitch.

OM12001 (ATOP)

Telematics

Preliminary Specification Rev. 0.75 — 14th August 2012 34 of 42

Page 35

NXP Semiconductors

OM12001 (ATOP)

Telematics

Fig 13. OM12001 (ATOP) package outline and dimensions

Preliminary Specification Rev. 0.75 — 14th August 2012 35 of 42

Page 36

NXP Semiconductors

21. Support information

For support, please contact support.telematics@nxp.com

22. Test information

For production and end of line testing the following tools will be provided:

• SW tools to interface to module:

– parameters setting (e.g. battery settings, ...) – file download – flash update

23. Safety instructions

OM12001 (ATOP) is a class A digital device marketed for use in a commercial, industrial or business environment.

It has been tested to be conform to FCC as well as to R&TTE Articles 3.1(a) and (b), safety and EMC respectively, and relevant Article 3.2 requirements using NXP reference board. The manufacturer of the final product integrating OM12001 (A TOP) must asse ss its equipment against the Essential requirements of the R&TTE and FCC Directives

OM12001 (ATOP)

Telematics

OM12001 (ATOP) is compliant with the following standards:

• Mandatory european standards

– R&TTE Article 3.1a: Electrical safety (EN60950) – R&TTE Article 3.1a: SAR (EN62209-1): MPE calculation as distance > 20 cm – R&TTE Article 3.1b: EMC (EN301489-1 and -7 for GSM, EN301489-3 V1.4.1,

EN300440-2 for NFC and GPS)

– R&TTE Article 3.2: Radiated RF (EN301511 for GSM, EN302291-1-2 V1.1.1 for

NFC and GPS)

– Notified Body opinion according to Annex IV: Evaluation of compliance with

essential requirements

• Mandatory US and Canadian standards

– FCC EMC: part 15B – FCC RF: part 24 for PCS1900, part 22 for GSM850, part 15.225 for GPS and NFC – FCC certificate from Telecom Certification body

• Voluntary certification

– Global Certification Forum (GCF), including field tests – PCS-1900 Type Certification Review Board (PTCRB)

Reports are available upon requests

Preliminary Specification Rev. 0.75 — 14th August 2012 36 of 42

Page 37

NXP Semiconductors

SAR according to EN 62209-1 has not been checked and replaced by MPE calculation, hence the antenna(s) used in the final application must be installed to provide a separation distance of at least 20 centimeter s from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter. Additionally, for FCC compliance, the system antenna(s) gain must no t exceed 3 dBi for mobile and fixed or mobile operating configurations.

Manufacturer of the final product using OM12001 (ATOP) will have to provide instructions for antenna installation and transmitter operating conditions to satisfy to RF exposure compliance.

Manufacturer of the final product using OM120 01 (ATOP) should take care that OM12001 (ATOP) is always within the operating limits (such as temperature, power supply, …) described in the present document, in particular it must be supplied by a limited power source according to EN 60950-1. Physically, the clearance and creepage distances required by the end product must be withheld when the module is installed. The cooling of the end product shall not negatively be influenced by the installation of the module.

Manufacturers of devices incorporating this module are advised to clarify any regulatory questions and to have their complete product tested and approved for R&TTE, FCC compliance and all relevant regulations.

OM12001 (ATOP)

Telematics

23.1 FCC Caution

Any changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate this equipment.

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipm e nt generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this e quipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense

23.2 IC Caution

This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interfe rence, and (2) this device must accept any interference, including interference that ma y cause undesired operation of the device. This Class B digital apparatus complies with Canadian ICES-003.

Preliminary Specification Rev. 0.75 — 14th August 2012 37 of 42

Page 38

NXP Semiconductors

Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than that necessary for successful communication.

Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorisée aux deux conditions suivantes : (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptible d'en compromettre le fonctionnement.

Cet appareil numérique de la classe B est conforme à la norme NMB-003 du Canada . Conformément à la réglementation d'Industrie Canada, le présent émetteur radio peut fonctionner avec une antenne d'un type et d' un gain maximal ( ou inférieur) approu vé pour l'émetteur par Industrie Canada. Dans le but de réduire les risques de brouillage radioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonnée équivalente (p .i.r.e.) ne dépasse pas l'intensité nécessaire à l'établissement d'une communication satisfaisante.

OM12001 (ATOP)

Telematics

Preliminary Specification Rev. 0.75 — 14th August 2012 38 of 42

Page 39

NXP Semiconductors

24. Appendix

25. Abbreviations

Table 30. Abbreviations

Acronym Description

ADC Analog to Digital Converter AES Advanced Encryption Standard AHB AMBA High Performance Bus ATOP Automotive Telematic On-board unit Platform CLK Clock CPU Central Processing Unit DAC Digital to Analog Converter DCS Digital Cellular System DES Data Encryption Standard DMA Direct Memory Access DPA Differential Power Analysis DSP Digital Signal Processor EEPROM Electrically Erasable Programmable Read Only Memory GP General Purpose GPIO General Purpose Input Output IF Intermediate Frequency IRQ Interrupt ReQuest JCOP Java Card Open Platform LDO Low DropOut LNA Low Noise Amplifier MCU Micro-Controller Unit MIDP Mobile Informati on Device Profile NFC Near Field Communication NiMH Nickel Metal Hybrid OBU On Board Unit OS Operating System OTP One Time Programmable PA Power Amplifier PCB Printed Circuit Board PCM Pulse Code Modulatio n PKI Public Key Infrastructure PLL Phase Locked Loop PWM Pulse Width Modulation RF Radio Frequency ROM Read Only Memory

OM12001 (ATOP)

Telematics

Preliminary Specification Rev. 0.75 — 14th August 2012 39 of 42

Page 40

NXP Semiconductors

OM12001 (ATOP)

Telematics

26. Glossary

27. References

Table 30. Abbreviations

Acronym Description

RSA A public-key encryption technology develo ped by RSA Data Security, Inc. The

acronym stands for Rivest, Shamir, and Adelman, the inventors of the

technique RTC Real Time Clock RTOS Real Time Operating System SAW Surface Acoustic Wave SIM Subscriber Identification Module SNR Signal to Noise Ratio SPA Simple Power Analysis SPI Serial Peripheral Interface TCXO Temperature Controlled Crystal Oscillator UART Universal Asynchronous Receiver Transmitter

…continued

[1] ZVEI - Zentralverband Elektrotechnik- und Elektronikindustrie e.V. —

http://www.zvei.org/fachverbaende/electronic_components_and_systems/robustnes s_validation/druckansicht.html?type=1

[2] LPC1768 datasheet —

http://www.nxp.com/documents/data_sheet/LPC1769_68_67_66_65_64_63.pdf

[3] LPC1768 user manual —

http://www.nxp.com/documents/user_manual/UM10360.pdf

[4] LPC1768 errata sheet —

http://www.nxp.com/documents/errata_sheet/ES_LPC176X.pdf

[5] LPC1768 web page —

http://www.nxp.com/products/microcontrollers/cortex_m3/lpc1700/LPC1768FET100 .html#overview

[6] AN1445 Antenna design guide for MFRC52x, PN51x, PN53x

AN1444 RF Design Guideplus Excel Calculation —

http://www.nxp.com/documents/application_note/AN1445_An1444.zip

[7] AN1425 RF Amplifier for NFC Reader IC's

AN166510 Amplifier antenna matching calculation (Excel) —

http://www.nxp.com/documents/application_note/AN1425_AN166510.zip

Preliminary Specification Rev. 0.75 — 14th August 2012 40 of 42

Page 41

NXP Semiconductors

28. Legal information

28.1 Definitions

Draft — The document is a draft version only. The content is still unde r internal review an d subject to formal appr oval, which may

result in modifications or additions. NXP Semiconductors does not give any representations or warranties as to the accuracy or completeness of information included herein and shall have no liability for the consequences of use of such information.

Short data sheet — A short data sheet is an extract from a full data sheet with the same product type number(s) and title. A short data sheet is intended for quick reference only and should not be relied upon to contain detailed and full information. For detailed and full information see the relevant full data sheet, which is avail able on request via the local NXP Semiconductors sales office. In case of any inconsistency or conflict with the shor t data sheet, the full data sheet shall prevail.

Product specification — The information and data provided in a Product dat a sheet shall define the specificati on of the product as agreed between NXP Semiconductors and its customer, unless NXP Semiconductors and customer have explicitly agreed otherwise in writing. In no event however, shall an agreement be valid in which the NXP Semiconductors product is deemed to offer functions and qualities beyond those described in t he Product data sheet.

28.2 Disclaimers

Limited warranty and liability — Information in this document is believed to be accurate and reliable. However, NXP

Semiconductors does not give any representations or warranties, expressed or implied, as to the accuracy or completeness of such information and shall have no liability for the consequences of use of such information.

In no event shall NXP Semiconductors be liable for any indirect, in cidental, p unitive, special or consequential d amages (including

- without limitation - lost profits, lost savings, business interruption, cost s related to the removal or re placement of any pr oducts or rework charges) whether or not such damages are based on tort (including negligence) , warranty, breach of contract or any other legal theory.

Notwithstanding any damages that customer might incur for any reason whatsoever, NXP Semiconductors’ aggregate and cumulative liability towards customer for the products described herein shall be limited in accordance with the Terms and conditions of commercial sale of NXP Semiconductors.

Right to make changes — NXP Semiconductors reserves the right to make changes to information p ublished in this document, including without limitation specifications and product descriptions, at any time and without notice. This document supersedes and replaces all information supplied prior to the publication hereof.

Suitability for use — NXP Semiconductors products are not designed, authorized or warranted to be suitable for use in medical, military, aircraft, space or life support equipment, nor in applications where failure or malfunction of an NXP Semiconductors product can reasonably be expected to result in personal injury, death or severe property or environmental damage. NXP Semiconductors accepts no liability for inclusion and/or use of NXP Semiconductors products in such equipment or applications and therefore such inclusion and/or use is at the customer’s own risk.

Applications — Applications that are described herein for any of these products are for illustrative purposes only. NXP Semiconductors makes no representation or warranty that such applications will be suitable for the specified use without further testing or modification.

NXP Semiconductors does not accept any liability related to any default, damage, costs or problem which is based on a weakness or default in the customer application/use or the application/use of customer’s third party cu stomer(s) (hereinaf ter both referred to as “Application”). It is customer’s sole responsibility to check whether the NXP Semiconductors product is suitable and fit for the Application planned. Customer has to do all necessary testing for the Application in order to avoid a default of the Application and the product. NXP Semiconductors does not accept any liability in this respect.

Limiting values — Stress above one or more limiting values (as defined in the Absolute Maximum Ratings System of IEC 60134) will cause permanent damage to the device. Limiting values are stress ratings only and (proper) operation of the device at these or any other conditions above those given in the Recommended operating conditions section (if present) or the Characteristics sections of this document is not warranted. Constant or repeated exposu re to limiting values will permane ntly and irreversibly affect the quality and reliability of the device.

Terms and conditions of commercial sale — NXP Semiconductors products are sold su bject to the general terms and conditions of commercial sale, as published at http://www.nxp.com/profile/terms individual agreement. In case an individual agreement is concluded only the terms and conditions of the respective agreement shall apply. NXP Semiconductors hereby expressly objects to applying the customer’s general terms and conditions with regard to the purchase of NXP Semiconductors products by customer.

No offer to sell or license — Nothing in this document may be interpreted or construed as an offer to sell products that is open for acceptance or the grant, conveyance or implication of any license under any copyrights, patents or other industrial or intellectual property rights.

Export control — This document as well as the item(s) described herein may be subject to export control regulations. Export might require a prior authorization from national authorities.

Quick reference data — The Quick reference data is an extract of the product data given in the Limiting values and Characteristics sections of this document, and as such is not complete, exhaustive or legally binding.

OM12001 (ATOP)

Telematics

, unless otherwise agreed in a valid written

Preliminary Specification Rev. 0.75 — 14th August 2012 41 of 42

Page 42

NXP Semiconductors

Non-automotive qualified products — Unless this data sheet expressly states that this specific NXP Semicondu ctors product

is automotive qualified, the product is not suitable for automotive use. It is neither qualified nor tested in accordance with automotive testing or application requirements. NXP Semiconductors accepts no liability for inclusion and/or use of non-automotive qualified products in automotive equipment or applications.

In the event that customer uses the product for design-in and use in automotive applications to automotive specifications and standards, customer (a) shall use the product without NXP Semiconductors’ warranty of the product for such automotive applications, use and specifications, and (b) whenever customer uses the product for automotive applications beyond NXP Semiconductors’ specifications such use shall be solely at customer’s own risk, and (c) customer fully indemnifies NXP Semiconductors for any liability, damages or failed product claims resulting from customer design and use of the product for automotive applications beyond NXP Semiconductors’ standard warrant y and NXP Semiconductors’ product specifications.

28.3 Licenses

Purchase of NXP ICs with ISO/IEC 14443 type B functionality

This NXP semiconductors IC is ISO/IEC 14443 Type B software enabled and is licensed under Innovatron’s Contactless Card p atents license for ISO/IEC 14443 B. The license includes the right to use the IC in systems and/or end-user equipment.

Purchase of NXP ICs with NFC technology

Purchase of an NXP semiconductors IC that complies with one of the Near Filed Communications (NFC) standards ISO/IEC 18092 and IS O/IEC 21481 does not convey an implied license under any patent right infringed by implementation of any of those standards. A license for the pate nt portfolio of NXP B.V. for the NFC standards needs to be obtained at Via Licensing, the pool agent of the NFC Patent pool, e-mail: info@vialicensing.com.

Purchase of NXP ICs with DPA and SPA countermeasures

NXP ICs containing functionality implementing countermeasures to Differential Power Analysis and Simple Power Analysis are produced and sold under applicable license from Cryptography Research, Inc.

OM12001 (ATOP)

Telematics

28.4 Patents

Notice is herewith given that the subject device uses one or more of the following patents and that each of these patents may have corresponding patents in other jurisdictions.

<Patent ID> — owned by <Company name>

28.5 Trademarks

Notice: All referenced brands, product names, service names and trademarks are the property of their respective owners.

MIFARE — is a trademark of NXP B.V. I²C-bus — logo is a trademark of NXP B.V.

Preliminary Specification Rev. 0.75 — 14th August 2012 42 of 42

NXP Semiconductors OM12001100 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

1. Introduction

2. Product profile

2.1 Features

2.2 Applications

2.3 Quick reference data

3. General description

4. Features

4.1 Utility processor

4.2 Application processor

4.3 Localization coprocessor

4.4 GSM/GPRS coprocessor

4.7 Debug and Security

4.8 Battery and Power management

5. Ordering information

6. Functional description

6.1 LPC1768 Micro-controller

6.1.1 General features

6.1.2 Block diagram

6.1.3 Ethernet

6.1.4 USB

6.1.4.1 USB device controller

6.1.4.2 USB host controller

6.1.5 CAN

6.1.5.1 Description

6.1.5.2 Features

6.1.6 Power saving modes

6.1.6.1 Peripheral and clock control

6.1.6.2 Power modes

6.1.7 RTC

7. Application design-in information

7.1 Battery charging

7.2 Application without rechargable battery

7.3 Current source

7.4 RTC

8. Application information

9. Recommended operating conditions

10. Limiting values

11. Characteristics

12. Static characteristics

12.1 Pins

12.2 Current sources

12.3 Voltage references

12.4 Clocks

13. Dynamic characteristics

13.1 Power consumption

13.2 Battery charging

14. Thermal characteristics

14.2 Internal temperature sensor

14.3 Battery temperature sensor

15. Handling information

16. Soldering

17. Mounting

17.1 PCB layout

17.2 Stencil design

18. Marking

19. Packing information

20. Package outline

21. Support information

22. Test information

23. Safety instructions

23.1 FCC Caution

23.2 IC Caution

24. Appendix

25. Abbreviations

26. Glossary

27. References

28. Legal information

28.1 Definitions

28.2 Disclaimers

28.3 Licenses

28.4 Patents

28.5 Trademarks