Rev. 1.01 — 15 November 2007Preliminary data sheet
This document lists detailed information about the LPC2917/19 device. It focuses on
factual information like pinning, characteristics etc. Short descriptions are used to outline
the concept of the features and functions. More details and background on developing
applications for this device are given in the LPC2917/19 User Manual (see Ref. 1
explicit references are made to the User Manual.
This document is written for engineers evaluating and/or developing systems, hardand/or software for the LPC2917/19. Some basic knowledge of ARM processors and
architecture and ARM968E-S in particular is assumed (see Ref. 2
).
F
T DRAFT DRAFT DRAFT DRA
DRA
). No
DR
AFT
DRAFT
DR
F
T DRAF
2.General description
2.1Architectural overview
The LPC2917/19 consists of:
• An ARM968E-S processor with real-time emulation support
• An AMBA multi-layer Advanced High-performance Bus (AHB) for interfacing to the
on-chip memory controllers
• Two DTL buses (a universal NXP interface) for interfacing to the interrupt controller
and the Power, Clock and Reset Control cluster (also called subsystem)
• Three VLSI Peripheral Buses (VPB - a compatible superset of ARM's AMBA
advanced peripheral bus) for connection to on-chip peripherals clu stered in
subsystems.
The LPC2917/19 configures the ARM968E-S processor in little-endian byte order. All
peripherals run at their own clock frequency to optimize the total system power
consumption. The AHB2VPB bridge used in the subsystems contains a write-ahead buffer
one transaction deep. This implies that when the ARM968E-S issues a buffered write
action to a register located on the VPB side of the bridge, it continues even though the
actual write may not yet have taken place. Completion of a second write to the same
subsystem will not be executed until the first write is finished.
NXP Semiconductors
2.2ARM968E-S processor
The ARM968E-S is a general purpose 32-bit RISC processor, which offers high
performance and very low power consumption. The ARM architecture is based on
Reduced Instruction Set Computer (RISC) principles, and the instruction set and related
decode mechanism are much simpler than those of micro-programmed Complex
Instruction Set Computers (CISC). This simplicity results in a high instruction throughput
and impressive real-time interrupt respon se from a sm all an d co st- effective contr olle r
core.
Amongst the most compelling features of the ARM968E-S are:
• Separate directly connected instruction and data Tightly Coupled Memory (TCM)
• Write buffers for the AHB and TCM buses
• Enhanced 16 x 32 multiplier capable of single-cycle MAC operations and 16-bit fixed-
DRAFT
ARM9 microcontroller with CAN and LIN
interfaces
point DSP instructions to accelerate signal-processing algorithms and applications.
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DRAFT
DRA
F
DR
AFT
DR
T DRAF
Pipeline techniques are employed so that all part s of the pro cessing and memory systems
can operate continuously. The ARM968E-S is based on the ARMv5TE five-stage pipeline
architecture. Typically, in a three-stage pipeline architecture, while one instruction is being
executed its successor is being decoded and a third instruction is being fetched from
memory. In the five-stage pipeline additional stages are added for memory access and
write-back cycles.
The ARM968E-S processor also employs a unique architectural strategy known as
THUMB, which makes it ideally suited to high-volume applications with memory
restrictions or to applications where code density is an issue.
The key idea behind THUMB is that of a super-reduced instruction set. Essentially, the
ARM968E-S processor has two instruction sets:
• Standard 32-bit ARMv5TE set
• 16-bit THUMB set
The THUMB set's 16-bit instruction length allows it to approach twice the density of
standard ARM code while retaining most of the ARM's performance advantage over a
traditional 16-bit controller using 16-bit registers. This is possible because THUMB code
operates on the same 32-bit register set as ARM code.
THUMB code can provide up to 65 % of the code size of ARM, and 160 % of the
performance of an equivalent ARM controller connected to a 16-bit memory system.
The ARM968E-S processor is described in detail in the ARM968E-S data sheet Ref. 2
.
2.3On-chip flash memory system
The LPC2917/19 includes a 512 kB or 768 kB flash memory system. This memory can be
used for both code and data storage. Programming of the flash memory can be
accomplished in several ways. It may be programmed in-system via a serial port; e.g.
CAN.
Preliminary data sheetRev. 1.01 — 15 November 2007 2 of 68
NXP Semiconductors
2.4On-chip static RAM
In addition to the two 16 kB TCMs the LPC2917/19 includes two static RAM memories:
one of 32 kB and one of 16 kB. Both may be used for code and/or data storage. Each
internal SRAM has its own controller, so both me mo r ies ca n be acce ssed simultaneously
from different AHB system bus layers.
3.Features
3.1General
ARM968E-S processor at 80 MHz maximum
Multi-layer AHB system bus at 80 MHz with three separate layers
On-chip memory:
Two-channel CAN controller supporting Full-CAN and extensive message filtering
Two LIN master controllers with full hardware support for LIN communication
Two 550 UARTs with 16-byte Tx and Rx FIFO depths
Three full-duplex Q-SPIs with four slave-select lines; 16 bits wide; 8 locations deep; Tx
Four 32-bit timers each containing four capture-and-compare registers linked to I/Os
32 - bit wa tch d og with tim er cha nge pr ot ection, running on safe clock.
Up to 108 general-purpose I/O pins with programmable pull-up, pull-down or bus
Vectored Interrupt Controller (VIC) with 16 priority levels
Two 8-channel 10-bit ADCs provide a total of up to 16 analog inputs, with conversion
Up to 24 level-sensitive external interrupt pins, including CAN and LIN wake- up
External Static Memory Controller (SMC) with eight memory banks; up to 32-bit data
Processor wake-up from power-down via external interrupt pins; CAN or LIN activity
Flexible Reset Generator Unit (RGU) able to control resets of individual modules
Flexible Clock-Generation Unit (CGU) able to control clock frequency of individual
DRAFT
ARM9 microcontroller with CAN and LIN
Two Tightly Coupled Memories (TCM), 16 kB Instruction (ITCM), 16 kB Data TCM
(DTCM)
Two separate internal Static RAM (SRAM) instances; 32 kB SRAM and 16 kB
SRAM
Up to 768 kB flash-program memory
FIFO and Rx FIFO
keeper
times as low as 2.44 μs per channel. Each channel provides a compare function to
minimize interrupts
features
bus; up to 24-bit address bus
modules
On-chip very low-power ring oscillator; fixed frequency of 0.4 MHz; always on to
provide a Safe_Clock source for system monitoring
On-chip crystal oscillator with operating range from 10 MHz to 50 MHz - max. PLL
input 15 MHz
On-chip PLL allows CPU operation up to a maximum CPU rate of 80 MHz
Generation of up to 10 base clocks
Seven fractional dividers
Preliminary data sheetRev. 1.01 — 15 November 2007 3 of 68
NXP Semiconductors
Highly configurable system Power Management Unit (PMU),
clock control of individual modules
allows minimization of system operating power consumption in any configuration
Standard ARM test and debug interface with real-time in-circuit emulator
Boundary-scan test supported
Du al po we r sup p ly:
CPU operating voltage: 1.8 V ± 5%
I/O operating voltage: 2.7 V to 3.6 V; inputs tolerant up to 5.5 V
14 4 -p i n LQ F P package
−40 °C to 85 °C ambient operating temperature range
4.Ordering information
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DR
F
T DRAF
Table 1.Ordering information
Type numberPackage
LPC2917FBD144LQFP144plastic low profile quad flat package; 144 leads; body 20 × 20 × 1.4 mm, pin
LPC2919FBD144LQFP144plastic low profile quad flat package; 144 leads; body 20 × 20 × 1.4 mm, pin
Preliminary data sheetRev. 1.01 — 15 November 2007 5 of 68
NXP Semiconductors
LPC2917FBD144
LPC2919FBD144
108
37
72
144
109
73
1
36
144PINS
6.Pinning information
6.1Pinning
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DR
F
T DRAF
Fig 2. Pin configuration for SOT486-1 (LQFP144)
6.2Pin description
6.2.1General description
The LPC2917/19 has up to four ports: two of 32 pins each, one of 28 pins and one of 16
pins. The pin to which each function is assigned is controlled by the SFSP registers in the
SCU. The functions combined on each port pin are shown in the pin description tables in
this section.
P0.23142GPIO 0, pin 23ADC2 IN7PWM2 MAT5EXTBUS A19
P2.20143GPIO 2, pin 20-PWM2 CAP0EXTBUS D18
TDI144IEEE 1149.1 data in, pulled up internally.
141ground for I/O
…continued
DR
AFT
DRAFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
7.Functional description
7.1Reset, debug, test and power description
7.1.1Reset and power-up behavior
The LPC2917/19 contains external reset input and internal power-up reset circuits. This
ensures that a reset is extended internally until the oscillators and flash have reached a
stable state. See Section 11
Section 12
the reset pin.
Table 4.Reset pin
SymbolDirectionDescription
RSTNinexternal reset input, active LOW; pulled up internally
At activation of the RSTN pin the JTAGSEL pin is sensed as logic LOW. If this is the case
the LPC2917/19 is assumed to be connected to debug hardware, and internal circuits
re-program the source for the BASE_SYS_CLK to be the crystal oscillator instead of the
Low-Power Ring Oscillator (LP_OSC). This is required because the clock rate when
running at LP_OSC speed is too low for the external debugging environment.
7.1.2Reset strategy
The LPC2917/19 contains a central module, the Reset Generator Unit (RGU) in the
Power, Clock and Reset Control Subsystem (PCRSS), which controls all internal reset
signals towards the peripheral modules. The RGU provides individua l reset control as well
as the monitoring functions needed for tracing a reset back to source.
for characteristics of the several start-up and initialization times. Table 4 shows
for trip levels of the internal power-up reset circuit1. See
The LPC2917/19 contains boundary-scan test logic according to IEEE 1149.1, also
referred to in this document as Joint Test Action Group (JTAG). The boundary-scan test
pins can be used to connect a debugger probe for the embedded ARM processor. Pin
JTAGSEL selects between boundary-scan mode and debug mode. Table 5
boundary- scan test pins.
Table 5.IEEE 1149.1 boundary-scan test and debug interfa ce
SymbolDescription
JTAGSELTAP controller select input. LOW level selects ARM debug mode and HIGH level
TRSTNtest reset input; pulled up internally (active LOW)
TMStest-mode select input; pulled up internally
TDItest data input, pulled up internally
TDOtest data output
TCKtest clock input
DRAFT
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
ARM9 microcontroller with CAN and LIN
F
selects boundary scan and flash programming; pulled up internally
D
RAFT
DR
DRAFT
T DRAFT DRAFT DRAFT DRA
AFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
shows the
7.1.4Power supply pins description
Table 6 shows the power supply pins.
Table 6.Power supplies
SymbolDescription
V
DD(CORE)
V
SS(CORE)
V
DD(IO)
V
SS(IO)
V
DD(OSC)
V
SS(OSC)
V
DD(A3V3)
V
SS(PLL)
digital core supply 1.8 V
digital core ground (digital core, ADC 1)
I/O pins supply 3.3 V
I/O pins ground
oscillator and PLL supply
oscillator ground
ADC 3.3 V supply
PLL ground
7.2Clocking strategy
7.2.1Clock architecture
The LPC2917/19 contains several different internal clock areas. Peripherals like Timers,
SPI, UART, CAN and LIN have their own individual clock sources called Base Clocks. All
base clocks are generated by the Clock Generator Unit (CGU). They may b e unre lated in
frequency and phase and can have different clock sources within the CGU.
The system clock for the CPU and AHB Multilayer Bus infrastructure has its own base
clock. This means most peripherals are clocked independently from the system clock. See
Figure 3
for an overview of the clock areas within the device.
Within each clock area there may be multiple branch clocks, which offers very flexible
control for power-management purposes. All branch clocks are outputs of the Power
Management Unit (PMU) and can be controlled independently. Branch clocks derived
from the same base clock are synchronous in frequency and phase. See Section 8.8
for
more details of clock and power control within the device.
Preliminary data sheetRev. 1.01 — 15 November 2007 12 of 68
NXP Semiconductors
7.2.2Base clock and branch clock relationship
The next table contains an overview of all the base blocks in the LPC2917/19 and their
derived branch clocks. A short description is given of the hardware parts that are clocked
with the individual branch clocks. In relevant cases more detailed information can be
found in the specific subsystem description. Some branch clocks have special protection
since they clock vital system parts of the device and shou ld (for example) not be switched
off. See Section 8.8.6
T able 7.Base clock and branch clock overview
Base clockBranch clock nameParts of the device clocked by
BASE_SAFE_CLKCLK_SAFEWatchdog Timer
BASE_SYS_CLKCLK_SYS_CPUARM968E-S and TCMs
BASE_PCR_CLKCLK_PCR_SLOWPCRSS, CGU, RGU and PMU
BASE_IVNSS_CLKCLK_IVNSS_VPBVPB side of the IVNSS
DRAFT
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
DRAFT
ARM9 microcontroller with CAN and LIN
F
T DRAFT DRAFT DRAFT DRA
for more details of how to control the individual branch clocks.
Remark
this branch clock
[1]
CLK_SYS_SYSAHB Bus infrastructure
CLK_SYS_PCRSSAHB side of bridge in PCRSS
CLK_SYS_FMCFlash-Memory Controller
CLK_SYS_RAM0Embedded SRAM Controller 0
(32 KByte)
CLK_SYS_RAM1Embedded SRAM Controller 1
(16 KByte)
CLK_SYS_SMCExternal Static-Memory
Controller
CLK_SYS_GESSGeneral Subsystem
CLK_SYS_VICVectored Interrupt Controller
CLK_SYS_PESSPeripheral Subsystem
CLK_SYS_GPIO0GPIO bank 0
CLK_SYS_GPIO1GPIO bank 1
CLK_SYS_GPIO2GPIO bank 2
CLK_SYS_GPIO3GPIO bank 3
CLK_SYS_IVNSS_AAHB side of bridge of IVNSS
Preliminary data sheetRev. 1.01 — 15 November 2007 13 of 68
NXP Semiconductors
T able 7.Base clock and branch clock overview
Base clockBranch clock nameParts of the device clocked by
BASE_MSCSS_CLKCLK_MSCSS_VPBVPB side of the MSCSS
BASE_UART_CLKCLK_UART0UART 0 interface clock
BASE_SPI_CLKCLK_SPI0SPI 0 interface clock
BASE_TMR_CLKCLK_TMR0Timer 0 clock for counter part
BASE_ADC_CLKCLK_ADC1Control of ADC 1, capture sample
BASE_CLK_TESTSHELLCLK_TESTSHELL_IP
DRAFT
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
ARM9 microcontroller with CAN and LIN
F
T DRAFT DRAFT DRAFT DRA
…continued
this branch clock
CLK_MSCSS_MTMR0Timer 0 in the MSCSS
CLK_MSCSS_MTMR1Timer 1 in the MSCSS
CLK_MSCSS_PWM0PWM 0
CLK_MSCSS_PWM1PWM 0
CLK_MSCSS_PWM2PWM 0
CLK_MSCSS_PWM3PWM 0
CLK_MSCSS_ADC1_VPBVPB side of ADC 1
CLK_TMR1Timer 1 clock for counter part
CLK_TMR2Timer 2 clock for counter part
CLK_TMR3Timer 3 clock for counter part
result
CLK_ADC2Control of ADC 2, capture sample
result
DR
AFT
DRAFT
DRA
Remark
DR
AFT
DRAFT
DR
F
T DRAF
[1] This clock is always on (cannot be switched off for system safety reasons)
[2] In the peripheral subsystem parts of the Timers, Watchdog Timer, SPI and UART have their own clock
source. See Section 8.4
[3] In the Power Clock and Reset Control subsystem parts of the CGU, RGU PMU have their own clock
source. See Section 8.8
[4] The clock should remain activated w hen system wake-up on timer or UART is required.
for details.
for details.
8.Block description
8.1Flash memory controller
8.1.1Overview
The Flash Memory Controller (FMC) interfaces to the embedded flash memory for two
tasks:
• Providing memory data transfer
• Memory configuration via triggering, programming and erasing
Preliminary data sheetRev. 1.01 — 15 November 2007 14 of 68
NXP Semiconductors
The flash memory has a 128-bit wide data interface and the flash controller offers two
128-bit buffer lines to improve system performance. The flash has to be programmed
initially via JTAG. In-system programming must be supported by the boot loader.
In-application programming is possible. Flash memory contents can be protected by
disabling JTAG access. Suspension of burning or erasing is not supported.
The key features are:
• Programming by CPU via AHB
• Programming by external programmer via JTAG
• JTAG access protection
• Burn-finished and erase-finished interr up t
8.1.2Description
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
After reset flash initialization is started, which takes t
initialization flash access is not possible and AHB transfers to flash are stalled, blocking
the AHB bus.
During flash initialization the index sector is read to identify the status of the JTAG access
protection and sector security. If JTAG access protection is active the flash is not
accessible via JTAG. ARM debug facilities are disabled to protect the flash-memory
contents against unwanted reading out externally. If sector security is active only the
concerned sections are read.
Flash can be read synchronously or asynchronously to the system clock. In synchronous
operation the flash goes into standby after returning the read data. Started reads cannot
be stopped, and speculative reading and dual buff ering are therefore not supported.
With asynchronous reading, transfer of the address to the flash and of read da ta from the
flash is done asynchronously , giving the fastest possib le response time. S t arted reads can
be stopped, so speculative reading and dual buffering are supported.
Buffering is offered because the flash has a 128-bit wide data interface while the AHB
interface has only 32 bits. With buffering a buffer line holds the complete 128-bit flash
word, from which four words can be read. Without buffering every AHB data port read
starts a flash read. A flash read is a slow process compare d to the minimum AHB cycle
time, so with buffering the average read time is reduced. This can improve system
performance.
time, see Section 12. During this
init
With single buffering the most recently read flash word remains availabl e until the next
flash read. When an AHB data-port read transfer requires data from the same flash word
as the previous read transfer , no ne w flash read is done and the read dat a is given without
wait cycles.
When an AHB data-port read transfer requires data from a different flash word to that
involved in the previous read transfer, a new flash read is done and wait states are given
until the new read data is available.
With dual buffering a secondary buffer line is used, the output of the flash being
considered as the primary buffer. On a primary buffer hit data can be copied to the
secondary buffer line, which allows the flash to start a speculative read of the next flash
word.
Preliminary data sheetRev. 1.01 — 15 November 2007 15 of 68
NXP Semiconductors
Both buffer lines are invalidated after:
• Initialization
• Configuration-register access
• Data-latch reading
• Index-sector reading
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DR
F
T DRAF
The modes of operation are listed in Table 8
Table 8.Flash read modes
Synchronous timing
No buffer linefor single (non-linear) reads; one flash-word read per word read
Single buffer linedefault mo de of operation; most recently read flash word is kept until
another flash word is required
Asynchronous timing
No buffer lineone flash-word read per word read
Single buffer linemost recently read flash word is kept until another flash word is
required
Dual buffer line, single
speculative
Dual buffer line, always
speculative
on a buffer miss a flash read is done, followed by at most one
speculative read; optimized for execution of code with small loops
(less than eight words) from flash
most recently used flash word is copied into second buffer line; next
flash-word read is started; highest performance for linear reads
.
8.1.3Flash memory controller pin description
The flash memory controller has no extern al pins. However, the flash can be programmed
via the JTAG pins, see Section 7.1.3
.
8.1.4Flash memory controller clock description
The flash memory controller is clocked by CLK_SYS_FMC, see Section 7.2.2.
8.1.5Flash layout
The ARM processor can program the flash for ISP (In-System Programming) a nd IAP (InApplication Programming). Note that the flash always has to be programmed by ‘flash
words’ of 128 bits (four 32-bit AHB bus words, hence 16 bytes).
The flash memory is organized into eight ‘small’ sectors of 8 kB each and up to 11 ‘large’
sectors of 64 kB each. The number of large sectors depends on the device type. A sector
must be erased before data can be written to it. The flash memory also has sector-wise
protection. Writing occurs per page which consists of 4096 bits (32 flash words). A small
sector contains 16 pages; a large sector contains 128 pages.
[1] Availability of sector 15 to sector 18 depends on device type, see Section 4 “Ordering information”.
The index sector is a special sector in which the JTAG access protection and sector
security are located. The address space becomes visible by setting the FS_ISS bit and
overlaps the regular flash sector’s address space.
Note that the index sector cannot be erased, and that acce ss to it ha s to be pe rformed via
code outside the flash.
8.1.6Flash bridge wait-states
To eliminate the delay associated with synchronizing flash-read data, a predefined
number of wait-states must be programmed. These depend on flash-memory response
time and system clock period. The minimum wait-states value can be calculated with the
following formulas:
Preliminary data sheetRev. 1.01 — 15 November 2007 17 of 68
NXP Semiconductors
Remark: If the programmed number of wait-states is more than three, flash-data reading
cannot be performed at full speed (i.e. with zero wait-states at the AHB bus) if speculative
reading is active.
8.2External static memory controller
8.2.1Overview
The LPC2917/19 contains an external Static Memory Controller (SMC) which provides an
interface for external (off-chip) memory devices.
Key features are:
• Supports static memory-mapped devices including RAM, ROM, flash, burst ROM and
• Asynchronous page-mode read operation in non-clocked memory subsystems
• Asynchronous burst-mode read access to burst-mode ROM devices
• Independent configuration for up to eight banks, each up to 16 MB
• Programmable bus-turnaround (idle) cycles (one to 16)
• Programmable read and write wait states (up to 32), for static RAM devices
• Programmable initial and subsequent burst-read wait state for burst-ROM devices
• Programmable write protection
• Programmable burst-mode operation
• Programmable external data width: 8-bit, 16-bit or 32-bit
• Programmable read-byte lane enable control
external I/O devices
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
8.2.2Description
The SMC simultaneously supports up to eigh t independently configurable memory banks.
Each memory bank can be 8, 16 or 32 bits wide and is capable of supporting SRAM,
ROM, burst-ROM memory or external I/O devices.
A separate chip-select output is available for each bank. The chip-select lines are
configurable to be active HIGH or LOW. Memory-bank selection is controlled by memory
addressing. Table 10
memory base addresses, chip selects and bank internal addresses.
Table 10.External memory-bank address bit description
32 bit
System
Address Bit
field
31 to 29BA[2:0]external static-memory base address (three most significant bits);
28 to 26CS[2:0]chip-select address space for eight memory banks; see
25 and 24-always ’00’; other values are ’mirrors’ of the 16 MByte bank address
23 to 0A[23:0]16-MByte memory banks address space
shows how the 32-bit system address is mapped to the external bus
SymbolDescription
the base address can be found in the memory map; see Ref. 1
field contains ’010’ when addressing an external memory bank.
The external static-memory controller module in the LPC2917/19 has the following pins,
which are combined with other functions on the port pins of the LPC2917/19. Table 12
shows the external memory controller pins.
Table 12.External memory controller pins
SymbolDirectionDescription
EXTBUS CSxoutmemory-bank x select, x runs from 0 to 7
EXTBUS BLSyoutbyte-lane select input y, y runs from 0 to 3
EXTBUS WE_Noutwrite enable (active LOW)
EXTBUS OE_Noutoutput enable (active LOW)
EXTBUS A[23:0] outaddress bus
EXTBUS D[31:0] in/outdata bus
Preliminary data sheetRev. 1.01 — 15 November 2007 20 of 68
NXP Semiconductors
OE_N
CLK(SYS)
CS
ADDR
DATA
WSTOEN
WST1
WSTWEN
WST2
WE_N / BLS
IDCY
Usage of the idle/turn-around time (IDCY) is de mon str ated In Figure 6. Extra wait states
are added between a read and a write cycle in the same external memory device.
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DR
F
T DRAF
WSTOEN=5, WSTWEN=5, WST1=7, WST2=6, IDCY=5
Fig 6. Reading/writing external memory
Address pins on the device are shared with other functions. When connecting external
memories, check that the I/O pin is programmed for the correct function. Control of these
settings is handled by the SCU.
Preliminary data sheetRev. 1.01 — 15 November 2007 21 of 68
NXP Semiconductors
8.3General subsystem
8.3.1General subsystem clock description
The general subsystem is clocked by CLK_SYS_GESS, see Section 7.2.2.
8.3.2Chip and feature identification
8.3.2.1Overview
The key features are:
• Identification of product
• Identification of features enabled
8.3.2.2Description
The Chip/Feature ID (CFID) module contains registers which show and control the
functionality of the chip. It contains an ID to identify the silicon, and also registers
containing information about the features enabled or disabled on the chip.
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
8.3.2.3CFID pin description
The CFID has no external pins.
8.3.3System Control Unit (SCU)
8.3.3.1Overview
The system control unit takes care of system-related functions.The key feature is
configuration of the I/O port-pins multiplexer.
8.3.3.2Description
The system control unit defines the function of each I/O pin of the LPC2917/19. The I/O
pin configuration should be consistent with peripheral function usage.
8.3.3.3SCU pin description
The SCU has no external pins.
8.3.4Event router
8.3.4.1Overview
The event router provides bus-controlled routing of input events to the vectored interrupt
controller for use as interrupt or wake-up signals.
Key features:
• Up to 24 level-sensitive external interrupt pins, including CAN, LIN and RxD wake-up
features plus three internal event sources
• Input events can be used as interrupt source either directly or latched (edge-detected)
• Direct events disappear when the event becomes inactive
• Latched events remain active until they are explicitly cleared
Preliminary data sheetRev. 1.01 — 15 November 2007 22 of 68
NXP Semiconductors
• Event detection is fully asynchronous, so no clock is required
8.3.4.2Description
The event router allows the event source to be defined, its polarity and activation type to
be selected and the interrupt to be masked or enabled. The event router can be used to
start a clock on an external event.
The vectored interrupt-controller inputs are active HIGH.
8.3.4.3Event-router pin description and mapping to register bit positions
The event router module in the LPC2917/19 is connected to the pins listed below. The
pins are combined with other functions on the port pins of the LPC2917/19. Table 13
shows the pins connected to the event router, and also the corresponding bit position in
the event-router registers and the default polarity.
Preliminary data sheetRev. 1.01 — 15 November 2007 23 of 68
NXP Semiconductors
• CLK_SAFE see Section 7.2.2
8.4.2Watchdog timer
8.4.2.1Overview
The purpose of the watchdog timer is to reset the ARM9 processor within a reasonable
amount of time if the processor enters an error state. The watchdog generates a system
reset if the user program fails to trigger it correctly within a predetermined amount of time.
Key features:
• Internal chip reset if not periodically triggered
• Timer counter register runs on always-on safe clock
• Optional interrupt generation on watchdog timeout
• Debug mode with disabling of reset
• Watchdog control register change-protected with key
• Programmable 32-bit watchdog timer period with programmable 32-bit prescaler.
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
8.4.2.2Description
The watchdog timer consists of a 32-bit counter with a 32-bit prescaler.
The watchdog should be programmed with a time-out value and then periodically
restarted. When the watchdog times out it generates a reset through the RGU.
To generate watchdog interrupts in watchdog debug mode the interr upt has to be enable d
via the interrupt enable register. A watchdog-overflow interrupt can be cleared by writing
to the clear-interrupt register.
Another way to prevent resets during debug mod e is via the Pause feature of the
Watchdog Timer. The watchdog is stalled when the ARM9 is in debug mode and the
PAUSE_ENABLE bit in the Watchdog Timer Control register is set.
The Watchdog Reset output is fed to the Reset Gener ator Unit (RGU). The RGU cont ains
a reset source register to identify the reset source when the device has gone through a
reset. See Section 8.8.5
8.4.2.3Pin description
The watchdog has no external pins.
8.4.2.4Watchdog timer clock description
The Watchdog Timer is clocked by two different clocks; CLK_SYS_PESS and
CLK_SAFE, see Section 7.2.2
by CLK_SYS_PESS. The timer and prescale counters are clocked by CLK_SAFE which
is always on.
.
. The register interface towards the system bus is clocked
8.4.3Timer
8.4.3.1Overview
The LPC2917/19 contains six identical timers: four in the peripheral subsystem and two in
the Modulation and Sampling Control SubSystem (MSCSS) located at d iffer ent peripher al
base addresses. This section describes the four timers in the peripheral subsystem. Each
Preliminary data sheetRev. 1.01 — 15 November 2007 24 of 68
NXP Semiconductors
timer has four capture inputs and/or match output s. Connection to device pins depends on
the configuration programmed into the port function-select registers. The two timers
located in the MSCSS have no external capture or match pins, but the memory map is
identical, see Section 8.7.7
function.
The key features are:
• 32-bit timer/counter with programm ab le 32 -b it pr es ca ler
• Up to four 32-bit capture channels per timer . These ta ke a snapshot of the time r value
• Four 32-bit match registers per timer that allow:
• Up to four external outputs per timer corresponding to match registers, with the
• Pause input pin (MSCSS timers only)
DRAFT
ARM9 microcontroller with CAN and LIN
. One of these timers has an external input for a pause
when an external signal connected to the TIMERx CAPn input changes state. A
capture event may also optionally generate an interrupt
– Continuous operation with optional interrupt generation on match
– Stop timer on match with optional interrupt generation
– Reset timer on match with optional interrupt generation
following capabilities:
– Set LOW on match
– Set HIGH on match
– Toggle on match
– Do nothing on match
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
DRAFT
AFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
8.4.3.2Description
The timers are designed to count cycles of the clock and optionally generate interr upts or
perform other actions at specified timer values, based on four match registers. They also
include capture inputs to trap the timer value when an input sign al changes state,
optionally generating an interrupt. The core function of the timers consists of a 32 bit
‘prescale counter’ trig g er ing the 32 bit ‘timer cou nt er’. Both counters run on cl oc k
CLK_TMRx (x runs from 0 to 3) and all time references are related to the period of this
clock. Note that each timer has its individual clock source within the Peripheral
SubSystem. In the Modulation and Sampling SubSystem each timer also has its own
individual clock source. See section Section 8.8.6
clocks.
8.4.3.3Pin description
The four timers in the peripheral subsystem of the LPC2917/19 have the pins described
below. The two timers in the modulation and sampling subsystem have no external pins
except for the pause pin on MSCSS timer 1. See Section 8.7.7
timers and their associated pins. The timer pins are combined with other functions on the
port pins of the LPC2917/19, see Section 8.3.3
runs from 0 to 3).
Preliminary data sheetRev. 1.01 — 15 November 2007 25 of 68
NXP Semiconductors
Table 14.Timer pins
SymbolDirectionDescription
TIMERx CAP[0]INTIMER x capture input 0
TIMERx CAP[1]INTIMER x capture input 1
TIMERx CAP[2]INTIMER x capture input 2
TIMERx CAP[3]INTIMER x capture input 3
TIMERx MAT[0]OUTTIMER x match output 0
TIMERx MAT[1]OUTTIMER x match output 1
TIMERx MAT[2]OUTTIMER x match output 2
TIMERx MAT[3]OUTTIMER x match output 3
8.4.3.4Timer clock description
The timer modules are clocked by two different clocks; CLK_SYS_PESS and CLK_TMRx
(x = 0-3), see Section 7.2.2
power management. The frequency of all these clocks is identical as they are derived
from the same base clock BASE_CLK_TMR. The register interface towards the system
bus is clocked by CLK_SYS_PESS. The timer and prescale counters are clocked by
CLK_TMRx.
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
. Note that each timer has its own CLK_TMRx branch clock for
DR
AFT
DRAFT
DR
F
T DRAF
8.4.4UARTs
8.4.4.1Overview
The LPC2917/19 contains two identical UARTs located at different peripheral base
addresses. The key features are:
• 16-byte receive and transmit FIFOs
• Registers conform to industry standard 550
• Receiver FIFO trigger points at 1 byte, 4 bytes, 8 bytes and 14 bytes
• Built-in baud-rate generator
8.4.4.2Description
The UART is commonly used to implement a serial interface such as RS232. The
LPC2917/19 contains two industry-st andard 550 UAR Ts with 16-byte transmit and receive
FIFOs, but they can also be put into 450 mode without FIFOs.
8.4.4.3UART pin description
The two UARTs in the LPC2917/19 have the following pins. The UAR T p ins are combine d
with other functions on the port pins of the LPC2917/19. Table 15
runs from 0 to 1).
Table 15.UART pins
SymbolDirectionDescription
UARTx TXDoutUART channel x transmit data output
UARTx RXDinUART channel x receive data input
Preliminary data sheetRev. 1.01 — 15 November 2007 26 of 68
NXP Semiconductors
8.4.4.4UART clock descrip tio n
The UART modules are clocked by two different clocks; CLK_SYS_PESS and
CLK_UARTx (x = 0-1), see Section 7.2.2
branch clock for power management. The frequency of all CLK_UAR Tx clocks is identical
since they are derived from the same base clock BASE_CLK_UART. The register
interface towards the system bus is clocked by CLK_SYS_PESS. The baud generator is
clocked by the CLK_UARTx.
8.4.5Serial peripheral interface
8.4.5.1Overview
The LPC2917/19 contains three Serial Peripheral Interface modules (SPIs) to allow
synchronous serial communication with slave or master peripherals.
The key features are:
• Master or slave operation
• Supports up to four slaves in sequential multi-slave operation
• Supports timer-triggered operation
• Programmable clock bit rate and prescale based on SPI source clock
• Separate transmit and receive FIFO memory buffers; 16 bits wide, 32 locations deep
• Programmable choice of interface operation: Motorola SPI or Texas Instruments
• Programmable data-frame size from 4 to 16 bits
• Independent masking of transmit FIFO, receive FIFO and receive overrun interrupts
• Serial clock-rate master mode: fserial_clk ≤ f
• Serial clock-rate slave mode: fserial_clk = f
• Internal loopback test mode
ARM9 microcontroller with CAN and LIN
. Note that each UART has its own CLK_UARTx
(BASE_SPI_CLK), independent of system clock
Synchronous Serial Interfaces
CLK(SPI)*
CLK(SPI)*
DRAFT
/2
/4
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
DRAFT
AFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
8.4.5.2Functional description
The SPI module is a master or slave interface for synchronous serial communication with
peripheral devices that have either Motorola SPI or Texas Instruments Synchronous
Serial Interfaces.
The SPI module performs serial-to-parallel conversion on data received from a peripheral
device. The transmit and receive paths are buffered with FIFO memories (16 bits wide x
32 words deep). Serial data is transmitted on SPI_TxD and received on SPI_RxD.
The SPI module includes a programmable bit-rate clock divider and pre scaler to ge nerate
the SPI serial clock from the input clock CLK_SPIx.
The SPI module’s operating mode, frame format, and word size are programmed thr ough
the SLVn_S ETTINGS registers.
A single combined interrupt request SPI_INTREQ output is asserted if any of the
interrupts are asserted and unmasked.
Preliminary data sheetRev. 1.01 — 15 November 2007 27 of 68
NXP Semiconductors
Depending on the operating mode selected, the SPI_CS_OUT outputs operate as an
active-HIGH frame synchronization output for Texas Instruments synchronous serial
frame format or an active-LOW chip select for SPI.
Each data frame is between four and 16 bits long, depending on the size of words
programmed, and is transmitted starting with the MSB.
There are two basic frame types that can be selected:
• Texas Instruments synchronous serial
• Motorola Serial Peripheral Interface
8.4.5.3Modes of operation
The SPI module can operate in:
• Master mode:
• Slave mode
– Normal transmission mode
– Sequential slave mode
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DR
F
T DRAF
8.4.5.4SPI pin description
The three SPI modules in the LPC2917/19 have the pins listed below. The pins are
combined with other functions on the port pins of the LPC2917/19, see Section 8.3.3
Table 16
Table 16.SPI pins
SymbolDirectionDescription
SPIx SCSyin/outSPIx chip select
SPIx SCKin/outSPIx clock
SPIx SDIinSPIx data input
SPIx SDOoutSPIx data output
[1] Direction of SPIx SCS and SPIx SCK pins depends on master or slave mode. These pins are output in
[2] In slave mode there is only one chip-select input pin, SPIx SCS0. The other chip selects have no function in
shows the SPI pins (x runs from 0 to 2; y runs from 0 to 3).
master mode, input in slave mode.
slave mode.
8.4.5.5SPI clock description
The SPI modules are clocked by two different clocks; CLK_SYS_PESS and CLK_SPIx (x
= 0-2), see Section 7.2.2
power management. The frequency of all clocks CLK_SPIx is identical as they ar e derived
from the same base clock BASE_CLK_SPI. The register interface towards the system bus
is clocked by CLK_SYS_PESS. The serial-clock rate divisor is clocked by CLK_SPIx.
.
[1][2]
[1]
. Note that each SPI has its own CLK_SPIx branch clock for
The SPI clock frequency can be controlled by the CGU. In master mode the SPI clock
frequency (CLK_SPIx) must be set to at least twice the SPI serial clock rate on the
interface. In slave mode CLK_SPIx must be set to four times the SPI serial clock rate on
the interface.
Preliminary data sheetRev. 1.01 — 15 November 2007 28 of 68
NXP Semiconductors
8.4.6General-purpose I/O
8.4.6.1Overview
The LPC2917/19 contains four general-purpose I/O ports located at different peripheral
base addresses. In the 144-pin package all four ports are av ailable. All I/O pins are
bi-directional, and the direction can be programmed individually. The I/O pad behavior
depends on the configuration programmed in the port function-select registers.
The key features are:
• General-purpose parallel inputs and outputs
• Direction control of individual bits
• Synchronized input sampling for stable input-data values
• All I/O defaults to input at reset to avoid any possible bus conflicts
8.4.6.2Description
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
The general-purpose I/O provides individual control over each bi-directio nal port pin.
There are two registers to control I/O direction and output level. The inputs are
synchronized to achieve stable read-levels.
To generate an open-drain output, set the bit in the output register to the desired value.
Use the direction register to control the signal. When set to output, the output driver
actively drives the value on the output: when set to input the signal floats and can be
pulled up internally or externally.
8.4.6.3GPIO pin description
The five GPIO ports in the LPC2917/19 have the pins listed below. The GPIO pins are
combined with other functions on the port pins of the LPC2917/19. Table 17
GPIO pins.
Table 17.GPIO pins
SymbolDirectionDescription
GPIO0 pin[31:0]in/outGPIO port x pins 31 to 0
GPIO1 pin[31:0]in/outGPIO port x pins 31 to 0
GPIO2 pin[27:0]in/outGPIO port x pins 27 to 0
GPIO3 pin[15:0]in/outGPIO port x pins 15 to 0
8.4.6.4GPIO clock descri p tio n
The GPIO modules are clocked by several clocks, all of which are derived from
BASE_SYS_CLK; CLK_SYS_PESS and CLK_SYS_GPIOx (x = 0-3), see Section 7.2.2
Note that each GPIO has its own CLK__SYS_GPIOx branch clock for power
management. The frequency of all clocks CLK_SYS_GPIOx is identical to
CLK_SYS_PESS since they are derived from the same base clock BASE_SYS_CLK.
Preliminary data sheetRev. 1.01 — 15 November 2007 29 of 68
NXP Semiconductors
8.5CAN gateway
8.5.1Overview
Controller Area Network (CAN) is the definition of a high-performance communication
protocol for serial data communication. The two CAN controllers in the LPC2917/19
provide a full implementation of the CAN protocol according to the CAN specification version 2.0B. The gateway concept is fully scalable with the number of CAN controllers,
and always operates together with a separate powerful and flexible hardware acce ptance
filter.
The key features are:
• Supports 11-bit as well as 29-bit identifiers
• Double receive buffer and triple transmit buffer
• Programmable error-warning limit and error counters with read/write access
• Arbitration-lost capture and error-code capture with detailed bit position
• Single-shot transmission (i.e. no re-transmission)
• Listen-only mode (no acknowledge; no active error flags)
• Reception of ‘own’ messages (self-reception request)
• Full CAN mode for message reception
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
8.5.2Global acceptance filter
The global acceptance filter provides look-up of received identifiers - called acceptance
filtering in CAN terminology - for all the CAN controllers. It includes a CAN ID look-up table
memory, in which software maintains one to five sections of identifiers. The CAN ID
look-up table memory is 2 kB large (512 words, each of 32 bit s). It can contain up to 1024
standard frame identifiers (SFF) or 512 extended frame identifiers (EFF) or a mixture of
both types. It is also possible to define identifier groups for standard and extended
message formats.
8.5.3CAN pin description
The two CAN controllers in the LPC2917/19 have the p ins listed below. The CAN pins are
combined with other functions on the port pins of the LPC2917/19. Table 18
CAN pins (x runs from 0 to 1).
Table 18.CAN pins
SymbolDirectionDescription
CANx TXDCoutCAN channel x transmit data output
CANx RXDC inCAN channel x receive data input
8.6LIN
8.6.1Overview
shows the
The LPC2917/19 contain two LIN 2.0 master con trollers. These can be used as dedicated
LIN 2.0 master controllers with additional support for sync break generation and with
hardware implementation of the LIN protocol according to spec 2.0.
Preliminary data sheetRev. 1.01 — 15 November 2007 30 of 68
NXP Semiconductors
• Complete LIN 2.0 message handling and transfer
• One interrupt per LIN message
• Slave response time-out detection
• Programmable sync-break length
• Automatic sync-field and sync-break generation
• Programmable inter-byte space
• Hardware or software parity generation
• Automatic checksum generation
• Fault confinement
• Fractional baud-rate generator
8.6.2LIN pin description
The two LIN 2.0 master controllers in the LPC2917/19 have the pins listed be low. The LIN
pins are combined with other functions on the port pins of the LPC2917/19. Table 19
shows the LIN pins. For more information see Ref. 1
controller.
Table 19.LIN controller pins
SymbolDirectionDescription
LIN0/1 TXDL outLIN channel 0/1 transmit data output
LIN0/1 RXDL inLIN channel 0/1 receive data input
DRAFT
ARM9 microcontroller with CAN and LIN
subsection 3.43, LIN master
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
8.7Modulation and sampling control subsystem
8.7.1Overview
The Modulation and Sampling Control Subsystem (MSCSS) in the LPC2917/19 includes
four Pulse-Width Modulators (PWMs), three10-bit successi ve approximation
Analog-to-Digital Converters (ADCs) and two timers.
The key features of the MSCSS are:
• Two 10-bit, 400 ksamples/s, 8-channel ADCs with 3.3 V inputs and various trigger-
start options
• Four 6-channel PWMs (Pulse-Width Modulators) with capture and trap functionality
• Two dedicated timers to schedule and synchronize the PWMs and ADCs
8.7.2Description
The MSCSS contains Pulse-Width Modulators (PWMs), Analog-to-Digital Converters
(ADCs) and timers.
Figure 7
communication with the AHB system bus. Two internal timers are dedicated to this
subsystem. MSCSS timer 0 can be used to generate start pulses for the ADCs and the
first PWM. The second timer (MSCSS timer 1) is used to generate ‘carrier’ signals for the
PWMs. These carrier patterns can be used, for example, in applications requiring current
provides an overview of the MSCSS. An AHB-to-VPB bus bridge takes care of
Preliminary data sheetRev. 1.01 — 15 November 2007 31 of 68
NXP Semiconductors
002aad348
PWM0 MAT[5:0]
PWM1 MAT[5:0]
PWM2 MAT[5:0]
PWM3 MAT[5:0]
ADC
1
3.3 V
ADC
2
3.3 V
PWM
0
MSCSS
TIMER 1
PWM
CONTROL
CARRIERS
MSCSS
TIMER 0
ADC
CONTROL
SYNCS
AHB2VPB
BRIDGE
PWM
1
PWM
2
PWM
3
AHB
system bus
VPB sub system bus
(to all sub blocks)
ADC2 IN[7:0]
ADC2_EXT_START
ADC1 IN[7:0]
ADC1_EXT_START
ADC clock
PWM0 TRAP
PWM0 CAP[2:0]
PWM1 TRAP
PWM1 CAP[2:0]
PWM2 TRAP
PWM2 CAP[2:0]
PWM3 TRAP
PWM3 CAP[2:0]
control. Several other trigger possibilities are provided for the ADCs (external, cascaded
or following a PWM). The capture inputs of both timers can also be used to capture the
start pulse of the ADCs.
The PWMs can be used to generate waveforms in which the frequency, duty cycle and
rising and falling edges can be controlled very precisely. Capture inputs are provided to
measure event phases compared to the main counte r. Depending on the applications,
these inputs can be connected to digital sens or motor outputs or digital external signals.
Interrupt signals are generated on several events to closely interact with the CPU.
The ADCs can be used for any application needing accurate digitized data from analog
sources. To support applications like motor control, a mechanism to synchronize several
PWMs and ADCs is available (sync_in and sync_out).
Note that the PWMs run on the PWM clock and the ADCs on the ADC clock, see
Section 8.8.4
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
DRAFT
F
T DRAFT DRAFT DRAFT DRA
AFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
.
Fig 7. Modulation and sampling control subsystem block diagram
8.7.2.1Synchronization and trigger features of the MSCSS
The MSCSS contains two internal timers to generate synchronization and carrier pulses
for the ADCs and PWMs. Figure 8
Preliminary data sheetRev. 1.01 — 15 November 2007 32 of 68
PWM modules.
shows how the timers are connected to the ADC and
NXP Semiconductors
Each ADC module has four start inputs. An ADC conversion is started when one of the
start ADC conditions is valid:
• start 0: ADC external start input pin; can be triggered at a positive or negative edge.
• start 1: If the ‘preceding’ ADC conversion is ended, the sync_out signal starts an ADC
• start 2: The PWM sync_out can start an ADC conversion. The sync_out signal is
• start 3: The match outputs from MSCSS timer 0 are connected to the start 3 inputs of
The PWM_sync and trans_enable_in of PWM 0 are connected to the 4th match output of
MSCSS timer 0 to start the PWM after a pre-programmed delay. This sync signal is
cascaded through all PWMs, allowing a programmable delay offset between subsequent
PWMs. The sync delay of each PWM can be programmed synchronously or with a
different phase for spreading the power load.
DRAFT
ARM9 microcontroller with CAN and LIN
Note that this signal is captured in the ADC clock domain
conversion. This signal is captured in the MSCSS subsystem clock domain, see
Section 8.7.5.2
start 1 input of ADC2 and the sync_out of ADC2 is connected to the start 1 input of
ADC1.
synchronized to the ADC clock in the ADC module. This signal is captured in the
MSCSS subsystem clock domain.
the ADCs. This signal is captured in the ADC clock domain.
. As can be seen in Figure 8, the sync_out of ADC1 is connected to the
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DRAFT
DRA
F
DR
AFT
DR
T DRAF
The match outputs of MSCSS timer 1 (PWM control) are connected to the corresponding
carrier inputs of the PWM modules. The carrier signal is modulated with the PWMgenerated waveforms.
The pause input of MSCSS timer 1 (PWM Control) is connected to an external input pin.
Generation of the carrier signal is stopped by asserting the pause of this timer.
The pause input of MSCSS timer 0 (ADC Control) is connected to a ‘NOR’ of the
PWM_sync outputs (start 2 input on the ADCs). If the pause feature of this timer is
enabled the timer only counts when one of the PWM_sync outputs is active HIGH. This
feature can be used to start the ADC once every x PWM cycles, where x corresponds to
the value in the match register of the timer. In this case the start 3 input of the ADC should
be enabled (start on match output of MSCSS timer 0).
The signals connected to the capture inputs of the timers (both MSCSS timer 0 and
MSCSS timer 1) are intended for debugging.
Fig 8. Modulation and sampling-control subsystem synchronization and triggering
8.7.3MSCSS pin description
The pins of the LPC2917/19 MSCSS associated with the two ADC modules are de scribed
in Section 8.7.5.3
Section 8.7.6.5
Section 8.7.7.3
8.7.4MSCSS clock description
The MSCSS is clocked from a number of different sources:
. Pins directly connected to the four PWM modules are described in
: pins directly connected to the MSCSS timer 1 module are described in
.
NXP Semiconductors
• CLK_SYS_MSCSS_A clocks the AHB side of the AHB-to-VPB bus bridge
• CLK_MSCSS_VPB clocks the subsystem VPB bus
• CLK_MSCSS_MTMR0/1 clocks the timers
• CLK_MSCSS_PWM0..3 clocks the PWMs.
Each ADC has two clock areas; a VPB part clocked by CLK_MSCSS_ADCx_VPB (x = 1
or 2) and a control part for the analog section clocked by CLK_ADCx = 1 or 2), see
Section 7.2.2
All clocks are derived from the BASE_MSCSS_CLK, except for CLK_SYS_MSCSS_A
which is derived form BASE_SYS_CLK, and the CLK_ADCx clocks which are derived
from BASE_CLK_ADC. If specific PWM or ADC modules are not used their corresponding
clocks can be switched off.
8.7.5Analog-to-digital converter
8.7.5.1Overview
DRAFT
ARM9 microcontroller with CAN and LIN
.
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
DRAFT
AFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
The MSCSS in the LPC2917/19 includes two 10-bit successive-approximation
analog-to-digital converters.
The key features of the ADC interface module are:
• ADC1 and ADC2: Eight analog inputs; time-multiplexed; measurement range up to
3.3 V
• External reference-level inputs
• 400 ksamples per second at 10-bit resolu tion up to 1500 ksamples per second at 2-bit
resolution
• Programmable resolution from 2-bit to 10-bit
• Single analog-to-digital conversion scan mode and continuous analog-to-digital
conversion scan mode
• Optional conversion on transition on external start input, timer capture/match signal,
PWM_sync or ‘previous’ ADC
• Converted digital values are stored in a register for each channel
• Optional compare condition to generate a ‘less than’ or an ‘equal to or greater than’
compare-value indication for each channel
• Power-down mode
8.7.5.2Description
The ADC block diagram, Figure 9
functionality is divided into two major parts; one part running on the MSCSS Subsystem
clock, the other on the ADC clock. This split into two clock domains affects the behavior
from a system-level perspective. The actual analog-to-digital conversions take place in the
ADC clock domain, but system control takes place in the system clock domain.
, shows the basic architecture of each ADC. The ADC
A mechanism is provided to modify configuration of the ADC and control the moment at
which the updated configuration is transferred to the ADC domain.
Preliminary data sheetRev. 1.01 — 15 November 2007 35 of 68
NXP Semiconductors
ADC
control
&
registers
ADC
control
&
registers
VPB
system
bus
update
Conversion data
Config data
IRQ
Start 0Start 2Start 1Start 3
CLK_ADCx_VPB
(MSCSS SubSystem clock)
CLK_ADCx
(ADC clock)
(upto 4.5 MHz)
Analog
inputs
ADC1: 8
ADC2: 8
Sync_out
ADC
IRQ
3.3 V
Analog
to
Digital
convertor
Analog
mux
ADC domain
VPB SubSystem
domain
001aad331 **
The ADC clock is limited to 4.5 MHz maximum frequency and should always be lower
than or equal to the system clock frequency. To meet this constraint or to select the
desired lower sampling frequency the clock generation unit provides a programmable
fractional system-clock divider dedicated to the ADC clock. Conversion rate is determined
by the ADC clock frequency divided by the number of resolution bits plus one. Accessing
ADC registers requires an enabled ADC clock, which is controllable via the clock
generation unit, see Section 8.8.4
Each ADC has four start inputs. Note that start 0 and start 2 are captured in the system
clock domain while start 1 and start 3 are captured in the ADC domain. The start inputs
are connected at MSCSS level, see Section 8.7.2.1
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
DRAFT
F
T DRAFT DRAFT DRAFT DRA
AFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
.
for details.
Fig 9. ADC block diagram
8.7.5.3ADC pin description
The two ADC modules in the MSCSS have the pins described below. The ADCx input
pins are combined with other functions on the port pins of the LPC2917/19. The VREFN
and VREFP pins are common for both ADCs. Table 20
Preliminary data sheetRev. 1.01 — 15 November 2007 36 of 68
Table 20.Analog to digital converter pins
SymbolDirectionDescription
ADCn IN[7:0]inanalog input for ADCn, channel 7 to channel 0 (n is 1 or 2)
ADCn_EXT_STARTinADC external start-trigger input (n is 1 or 2)
VREFNinADC LOW reference level
VREFPinADC HIGH reference level
shows the ADC pins.
NXP Semiconductors
8.7.5.4ADC clock description
The ADC modules are clocked from two different sources; CLK_MSCSS_ADCx_VPB and
CLK_ADCx (x = 1 or 2), see Section 7.2.2
and CLK_MSCSS_ADCx_VPB branch clocks for power management. If an ADC is
unused both its CLK_MSCSS_ADCx_VPB and CLK_ADCx can be switched off.
The frequency of all the CLK_MSCSS_ADCx_VPB clocks is identical to
CLK_MSCSS_VPB since they are derived from the same base clock
BASE_MSCSS_CLK. Likewise the frequency of all the CLK_ADCx clocks is identical
since they are derived from the same base clock BASE_ADC_CLK.
The register interface towards the system bus is clocked by CLK_MSCSS_ADCx_VPB.
Control logic for the analog section of the ADC is clocked by CLK_ADCx, see also
Figure 9
8.7.6PWM
DRAFT
ARM9 microcontroller with CAN and LIN
. Note that each ADC has its own CLK_ADCx
.
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
DRAFT
AFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
8.7.6.1Overview
The MSCSS in the LPC2917/19 includes four PWM modules with the following features.
• Six pulse-width modulated output signals
• Double edge features (rising and falling edges programmed individually)
• Optional interrupt generation on match (each edge)
• Different operation modes: continuous or run-once
• 16-bit PWM counter and 16-bit prescale counter allow a large range of PWM periods
• A protective mode (TRAP) holding the output in a sof tware-contro llable st ate and with
optional interrupt generation on a trap event
• Three capture registers and capture trigger pins with optional interrupt generation on
a capture event
• Interrupt generation on match event, capture event, PWM counter overflow or trap
event
• A burst mode mixing the external carrier signal with internally generated PWM
• Programmable sync-delay output to trigger other PWM modules (master/slave
behavior)
8.7.6.2Description
The ability to provide flexible waveforms allows PWM blocks to be used in multiple
applications; e.g. automotive dimmer/lamp control and fan control. Pulse-width
modulation is the preferred method for regulating power since no additional heat is
generated and it is energy-efficient when compared with linear-regulating voltage control
networks.
The PWM delivers the waveforms/pulses of the desired duty cycles and cycle periods. A
very basic application of these pulses can be in controlling the amount of power
transferred to a load. Since the duty cycle of the pulses can be controlled, the desired
amount of power can be transferred for a controlled duration. Two examples of such
applications are:
Preliminary data sheetRev. 1.01 — 15 November 2007 37 of 68
NXP Semiconductors
PWM
control
&
registers
PWM
Counter,
prescale
counter
&
shadow
registers
VPB system bus
update
Capture data
Config data
IRQ’s
Sync_in
Capture inputs
IRQ capt_match
PWM domain
VPB domain
IRQ pwm
Match outputs
PWM counter value
Transfer_enable_in
Transfer_enable_outSync_out
Carier inputs
Trap input
• Automotive dimmer controller: The flexibility of providing waves of a desired duty
• Motor controller: The PWM provides multi-phase outputs, an d these outputs can be
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
cycle and cycle period allows the PWM to control the amount of power to be
transferred to the load. The PWM functions as a dimmer controller in this application
controlled to have a certain pattern sequence. In this way the force/torque of the
motor can be adjusted as desired. This makes the PWM function as a motor drive.
DR
AFT
DRAFT
DR
F
T DRAF
Fig 10. PWM block diagram
The PWM block diagram in Figure10 shows the basic architecture of each PWM. PWM
functionality is split into two major parts, a VPB domain and a PWM domain, both of which
run on clocks derived from the BASE_MSCSS_CLK. This split into two domains affects
behavior from a system-level perspective. The actual PWM and prescale counters are
located in the PWM domain but system control takes place in the VPB domain.
The actual PWM consists of two counters; a 16-bit prescale counter and a 16-bit PWM
counter. The position of the rising and falling edges of the PWM outputs can be
programmed individually. The prescale counter allows high system bus frequencies to be
scaled down to lower PWM periods. Registers are available to capture the PWM counter
values on external events.
Note that in the Modulation and Sampling SubSystem, each PWM has its individual clock
source CLK_MSCSS_PWMx (x runs from 0 to 3). Both the prescale and the timer
counters within each PWM run on this clock CLK_MSCSS_PWMx, and all time references
are related to the period of this clock. See Section 8.8
for information on generation of
these clocks.
8.7.6.3Synchronizing the PWM counters
A mechanism is included to synchronize the PWM period to other PWMs by providing a
sync input and a sync output with programmable delay. Several PWMs can be
Preliminary data sheetRev. 1.01 — 15 November 2007 38 of 68
synchronized using the trans_enable_in/trans_enable_out and sync_in/sync_out ports.
See Section 8.7.2.1
in the LPC2917/19. PWM 0 can be master over PWM 1; PWM 1 can be master over
PWM 2, etc.
for details of the connections of the PWM m odules within the MSCSS
NXP Semiconductors
8.7.6.4Master and slave mode
A PWM module can provide synchronization signals to other modules (also called Ma ster
mode). The signal sync_out is a pulse of one clock cycle generated when the internal
PWM counter (re)starts. The sign al trans_enable_ou t is a pulse synchronous to sync_out,
generated if a transfer from system registers to PWM shadow register s occurred when the
PWM counter restarted. A delay may be inserted between the counter start and
generation of trans_enable_out and sync_out.
A PWM module can use input signals trans_enable_in and sync_in to synchronize its
internal PWM counter and the transfer of shadow registers (Slave mode).
8.7.6.5PWM pin description
Each of the four PWM modules in the MSCSS has the following pins. These are combined
with other functions on the port pins of the LPC2917/19. Table 21
PWM3 pins.
Table 21.PWM pins
SymbolDirectionDescription
PWMn CAP[0]inPWM n capture input 0
PWMn CAP[1]inPWM n capture input 1
PWMn CAP[2]inPWM n capture input 2
PWMn MAT[0]outPWM n match output 0
PWMn MAT[1]outPWM n match output 1
PWMn MAT[2]outPWM n match output 2
PWMn MAT[3]outPWM n match output 3
PWMn MAT[4]outPWM n match output 4
PWMn MAT[5]outPWM n match output 5
PWMn TRAPinPWM n trap input
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
shows the PWM0 to
DR
AFT
DRAFT
DR
F
T DRAF
8.7.6.6PWM clock description
The PWM modules are clocked by CLK_MSCSS_PWMx (x = 0-3), see Section 7.2.2
.
Note that each PWM has its own CLK_MSCSS_PWMx branch clock for power
management. The frequency of all these clocks is identical to CLK_MSCSS_VPB since
they are derived from the same base clock BASE_MSCSS_CLK.
Also note that unlike the timer modules in the Peripheral SubSystem, the actual timer
counter registers of the PWM modules run at the same clock as the VPB system interface
CLK_MSCSS_VPB. This clock is independent of the AHB system clock.
If a PWM module is not used its CLK_MSCSS_PWMx branch clock can be switched off.
8.7.7Timers in the MSCSS
8.7.7.1Overview
The two timers in the MSCSS are functionally identical to the timers in the peripheral
subsystem, see Section 8.4.3
the timers in the peripheral subsystem, but the capture inputs and match outputs are not
available on the device pins. These signals are instead connected to the ADC and PWM
modules as outlined in the description of the MSCSS, see Section 8.7.2
Preliminary data sheetRev. 1.01 — 15 November 2007 39 of 68
. The features of the timers in the MSCSS are the same as
.
NXP Semiconductors
8.7.7.2Description
See section Section 8.4.3.2
8.7.7.3MSCSS timer-pin description
MSCSS timer 0 has no external pins.
MSCSS timer 1 has a PAUSE pin available as external pin. The PAUSE pin is combined
with other functions on the port pins of the LPC2917/19. Table 22
timer 1 external pin.
Table 22.MSCSS timer 1 pin
SymbolDirectionDescription
MSCSS PAUSEinpause pin for MSCSS timer 1
8.7.7.4MSCSS timer-clock description
The Timer modules in the MSCSS are clocked by CLK_MSCSS_MTMRx (x = 0-1), see
Section 7.2.2
power management. The frequency of all these clocks is identical to CLK_MSCSS_VPB
since they are derived from the same base clock BASE_MSCSS_CLK.
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
for a description of the timers.
shows the MSCSS
. Note that each timer has its own CLK_MSCSS_MTMRx branch clock for
DR
AFT
DRAFT
DR
F
T DRAF
Note that, unlike the timer modules in the Peripheral SubSystem, the actual timer counter
registers run at the same clock as the VPB system interface CLK_MSCSS_VPB. This
clock is independent of the AHB system clock.
If a timer module is not used its CLK_MSCSS_MTMRx branch clock can be switched off.
8.8Power, clock and reset control subsystem
8.8.1Overview
The Power, Clock and Reset Control Subsystem (PCRSS) in the LPC2917/19 includes a
Clock Generator Unit (CGU), a Reset Generator Unit (RGU) and a Power Man a ge m ent
Unit (PMU).
8.8.2Description
Figure 11 provides an overview of the PCRSS. An AHB-to-DTL bridge takes care of
Preliminary data sheetRev. 1.01 — 15 November 2007 40 of 68
NXP Semiconductors
Power, Clock & Reset
RGU
CGU
RGU
registers
Input Deglitch/
Sync
POR
Reset Output
Delay Logic
branch
clocks
FDIV[6:0]
PLL
out0
out1
…
out9
Low Power
Ring Oscillator
(Ringo)
base
clocks
PMU
Clock
Gates
wakeup_a
AHB Master
Disable Grant
AHB Master
Disable Req
WARM_RST
COLD_RST
PCR_RST
RGU_RST
POR_RST
PMU _reg
Clock Ena ble
Control
RSTN (device pin)
Reset from Watchdog counter
AHB_RST
...
...
SCU_RST
AHB2DTL
Bridge
CGU
registers
Xtal Oscillator
xo 50m _out
xo50m_in
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DR
F
T DRAF
Fig 11. PCRSS block diagram
8.8.3PCR subsystem clock description
The PCRSS is clocked by a number of different clocks. CLK_SYS_PCRSS clocks the
AHB side of the AHB to DTL bus bridge and CLK_PCR_SLOW clocks the CGU, RGU and
PMU internal logic, see Section 7.2.2
BASE_SYS_CLK, which can be switched off in low-power modes. CLK_PCR_SLOW is
derived from BASE_PCR_CLK and is always on in order to be able to wake up from
low-power modes.
Preliminary data sheetRev. 1.01 — 15 November 2007 42 of 68
NXP Semiconductors
LP_OSC
Xtal
Oscilator
PLL
Clock Source Bus
Frequency
Monitor
Clock
Detection
DTL MMIO Interface
FDIV0
FDIV1
FDIV6
OUT 0
OUT 1
OUT 9
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DR
F
T DRAF
Fig 12. Block diagram of the CGU
There are two primary clock generators: a low-power ring oscillator (LP_OSC) and a
crystal oscillator. See Figure 12
LP_OSC is the source for the BASE_PCR_CLK that clocks the CGU itself and for
BASE_SAFE_CLK that clocks a minimum of other logic in the device (like the watchdog
.
timer). To prevent the device from losing its clock source LP_OSC cannot be put into
power-down. The crystal oscillator can be used as source for high-frequency clocks or as
an external clock input if a crystal is not connected.
Secondary clock generators are a PLL and seven fractional dividers (FDIV0..6). The PLL
has three clock outputs: normal, 120° phase-shifted and 240° phase-shifted.
Configuration of the CGU: For every output generator - generating the base clocks - a
choice can be made from the primary and secondary clock generators according to
Preliminary data sheetRev. 1.01 — 15 November 2007 43 of 68
.
NXP Semiconductors
PLL160M
FDIV0..6
XO50M
OSC1M
Clock
outputs
clkout /
clkout120 /
clkout240
Output
Control
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DR
F
T DRAF
Fig 13. Structure of the clock generation scheme
Any output generator (except for BASE_SAFE_CLK and BASE_PCR_CLK) can be
connected to either a fractional divider (FDIV0..6) or to one of the outputs of the PLL or to
LP_OSC/crystal oscillator directly . BASE_SAFE_CLK and BASE_PCR_CLK can use only
LP_OSC as source.
The fractional dividers can be connected to one of the outputs of the PLL or directly to
LP_OSC/crystal Oscillator.
The PLL can be connected to the crystal oscillator.
In this way every output generating the base clocks can be configured to get the required
clock. Multiple output generators can be connected to the same primary or secondary
clock source, and multiple secondary clock sources can be connected to the same PLL
output or primary clock source.
Invalid selections/programming - connecting the PLL to an FDIV or to one of the PLL
outputs itself for example - will be blocked by hardware. The control register will not be
written, the previous value will be kept, although all other fields will be written with new
data. This prevents clocks being blocked by incorrect programming.
Default Clock Sources: Every secondary clock generator or output generator is
connected to LP_OSC at reset. In this way the device runs at a low frequency after reset.
It is recommended to switch BASE_SYS_CLK to a high-frequency clock generator as
(one of) the first step(s) in the boot code after verifying that the high-frequency clock
generator is running.
Preliminary data sheetRev. 1.01 — 15 November 2007 44 of 68
NXP Semiconductors
Clock Activity Detection: Clocks that are inactive are automatically regarded as invalid,
and values of ’CLK_SEL ’ that would select those clocks are masked and not written to the
control registers. This is accomplished by adding a clock detector to every clock
generator . The RDET register keep s track of which clocks ar e active and inactive, and the
appropriate ‘CLK_SEL’ values are masked and unmasked accordingly. Each clock
detector can also generate interrupts at clock activation and deactivation so that the
system can be notified of a change in internal clock status.
Clock detection is done using a counter running at the BASE_PCR_CLK frequency. If no
positive clock edge occurs before the counter has 32 cycles of BASE_PCR_CLK the clock
is assumed to be inactive. As BASE_PCR_CLK is slower than any of the clocks to be
detected, normally only one BASE_PCR_CLK cycle is needed to detect activity. After
reset all clocks are assumed to be ‘non-present’, so the RDET status register will be
correct only after 32 BASE_PCR_CLK cycles.
Note that this mechanism cannot protect against a currently-selected clock going from
active to inactive state. Therefore an inactive clock may still be sent to the system under
special circumstances, although an interrupt can still be generated to notify the system.
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
Glitch-Free Switching: Provisions are included in the CGU to allow clocks to be
switched glitch-free, both at the output generator stage and also at secondary source
generators.
In the case of the PLL the clock will be stopped and held low for long enough to allow the
PLL to stabilize and lock before being re-enabled. For all non-PLL Generators the switch
will occur as quickly as possible, although there will always be a period when the clock is
held low due to synchronization requirements.
If the current clock is high and does not go low within 32 cycles of BASE_PCR_CLK it is
assumed to be inactive and is asynchronously forced low. This prevents deadlocks on the
interface.
8.8.4.3PLL functional description
A block diagram of the PLL is shown in Figure 14
analog section. This block compares the ph ase and frequency of the input s and generates
the main clock
to create the output clock, or sent directly to the output. The main output clock is then
divided by M by the programmable feedback divider to generate the feedback clock. The
output signal of the analog section is also moni to re d by th e loc k det ec to r to sign a l when
the PLL has locked onto the input clock.
2
. These clocks are either divided by 2 *P by th e pro grammable post divider
. The input clock is fed directly to the
2.Generation of the main clock is restricted by the frequency range of the PLL clock input. See Table31, Dynamic characteristics.
Preliminary data sheetRev. 1.01 — 15 November 2007 45 of 68
NXP Semiconductors
P23CCO
/ MDIV
clkout120 /
clkout240
/ 2PDIV
MSEL
PSEL
P23EN
Input clock
Bypass
Direct
clkout
Fig 14. PLL block diagram
Triple output phases
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DR
F
T DRAF
For applications that require multiple clock phases two additional clock outputs can be
enabled by setting register P23EN to ’1’, thus giving three clocks with a 120° phase
difference. In this mode all three clocks generated by the analog section are sent to the
output dividers. When the PLL has not yet achieved lock the second and third phase
output dividers run unsynchronized, which means that the phase relation of the output
clocks is unknown. When the PLL LOCK register is set the second and third phase of the
output dividers are synchronized to the main output clock CLKOUT PLL, thus giving three
clocks with a 120° phase difference.
Direct output mode
In normal operating mode (with DIRECT set to ’0’) the CCO clock is divided by 2, 4, 8 or
16 depending on the value on the PSEL[1:0] input, giving an output clock with a 50% duty
cycle. If a higher output frequency is needed the CCO clock can be sent directly to the
output by setting DIRECT to ’1’. Since the CCO does not directly generate a 50% duty
cycle clock, the output clock duty cycle in this mode can deviate from 50%.
Power-down control
A power-down mode has been incorporated to reduce power consumption when the PLL
clock is not needed. This is enabled by setting the PD control register bit. In this mo de the
analog section of the PLL is turned off, the oscillator and the phase-frequency detector are
stopped and the dividers enter a reset state. While in power-down mod e the LOCK output
is low, indicating that the PLL is not in lock. When power-down mode is terminated by
clearing the PD control-register bit the PLL resumes normal operation, and makes the
LOCK signal high once it has regained lock on the input clock.
8.8.4.4CGU pin description
The CGU module in the LPC2917/19 has the pins listed in Table 24
Preliminary data sheetRev. 1.01 — 15 November 2007 46 of 68
XIN_OSCinOscillator crystal input or external clock input
below.
DRAFT
NXP Semiconductors
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
8.8.5Reset Generation Unit (RGU)
8.8.5.1Overview
The key features of the Reset Generation Unit (RGU) are:
• Reset controlled individually per subsystem
• Automatic reset stretching and release
• Monitor function to trace resets back to source
• Register write-protection mechanism to prevent unintentional resets
8.8.5.2Description
The RGU controls all internal resets.
Each reset output is defined as a (combination of) reset input sources including the
external reset input pins and internal power -o n rese t, see Table 25
listed in this table form a sort of cascade to provide the multiple levels of impact that a
reset may have. The combined input sources are logically OR-ed together so that
activating any of the listed reset sources causes the output to go active.
Table 25.Reset output configuration
Reset OutputReset Sourceparts of the device reset when activated
POR_RSTpower-on reset moduleLP_OSC; is source for RGU_RST
RGU_RSTPOR_RST, RSTN pinRGU internal; is source for PCR_RST
PCR_RSTRGU_R ST, WATCHDOG PCR internal; is source for COLD_RST
COLD_RSTPCR_RSTparts with COLD_RST as reset source below
WARM_RSTCOLD_RSTparts with WARM_RST as reset source below
SCU_RSTCOLD_RSTSCU
CFID_RSTCOLD_RSTCFID
FMC_RSTCOLD_RSTembedded Flash-Memory Controller (FMC)
EMC_RSTCOLD_RSTembedded SRAM-Memory Controller
SMC_RSTCOLD_ RSTexternal Static-Memory Controller (SMC)
GESS_A2V_RSTWARM_RSTGeSS AHB-to-VPB bridge
PESS_A2V_RSTWARM_RSTPeSS AHB-to-VPB bridge
GPIO_RSTWARM_RSTall GPIO modules
UART_RSTWARM_RSTall UART modules
TMR_RSTWARM_RSTall Timer modules in PeSS
SPI_RSTWARM_RSTall SPI modules
IVNSS_A2V_RSTWARM_RSTIVNSS AHB-to-VPB bridge
IVNSS_CAN_RSTWARM_RSTall CAN modules including Acceptance filter
IVNSS_LIN_RSTWARM_RSTall LIN modules
MSCSS_A2V_RSTWARM_RSTMSCSS AHB to VPB bridge
MSCSS_PWM_RSTWARM_RSTall PWM modules
MSCSS_ADC_RSTWARM_RSTall ADC modules
MSCSS_TMR_RSTWARM_RSTall Timer modules in MSCSS
VIC_RSTWARM_RSTVectored Interrupt Controller (VIC)
AHB_RSTWARM_RSTCPU and AHB Multilayer Bus infrastructure
Preliminary data sheetRev. 1.01 — 15 November 2007 47 of 68
. The first five resets
DR
AFT
DRAFT
DR
F
T DRAF
NXP Semiconductors
8.8.5.3RGU pin description
The RGU module in the LPC2917/19 has the following pins. Table 26
pins.
Table 26.RGU pins
SymbolDirectionDescription
RSTNINexternal reset input, Active LOW; pulled up internally
8.8.6Power Management Unit (PMU)
8.8.6.1Overview
This module enables software to actively control the system’s power consumption by
disabling clocks not required in a particular operating mo de .
Using the base clocks from the CGU as input, the PMU generates branch clocks to the
rest of the LPC2917/19. Output clocks branched from the same base clock are phaseand frequency-related. These branch clocks can be individually controlled by software
programming.
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
shows the RGU
DR
AFT
DRAFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
The key features are:
• Individual clock control for all LPC2917/19 sub-modules
• Activates sleeping clocks when a wake-up event is detected
• Clocks can be individually disabled by software
• Supports AHB master-disable protocol when AUTO mode is set
• Disables wake-up of enabled clocks when power-down mode is set
• Activates wake-up of enabled clocks when a wake-up event is received
• Status r egister is available to indicate if an input base clock can be safely switch ed of f
(i.e. all branch clocks are disabled)
8.8.6.2Description
The PMU controls all internal clocks of the device for power-mode management. With
some exceptions, each branch clock can be switched on or of f individually under control of
software register bits located in its individual configuration register. Some branch clocks
controlling vital parts of the device operate in a fixed mode. Table 27
control bits are supported by each branch clock.
By programming the configuration register the user can control which clocks are switched
on or off, and which clocks are switched off when entering power-down mode.
Note that the standby-wait-for-interrupt instructions of the ARM968E- S pr ocessor (p utting
the ARM CPU into a low-power state) are not supported. Instead putting the ARM CPU
into power-down should be controlled by disabling the branch clock for the CPU.
shows which mode-
Remark: For any disabled branch clocks to be re-activated their corresponding base
clocks must be running (controlled by the CGU).
Table 27
Every branch clock is related to one particular base clock: it is not possible to switch the
source of a branch clock in the PMU.
Preliminary data sheetRev. 1.01 — 15 November 2007 48 of 68
shows the relation between branch and base clocks, see also Section 7.2.1.
NXP Semiconductors
Table 27.Branch clock overview
Legend:
"1" Indicates that the related register bit is tied off to logic HIGH, all writes are ignored
"0" Indicates that the related register bit is tied off to logic LOW, all writes are ignored
“+” Indicates that the related register bit is readable and writable
Preliminary data sheetRev. 1.01 — 15 November 2007 49 of 68
NXP Semiconductors
Table 27.Branch clock overview
Legend:
"1" Indicates that the related register bit is tied off to logic HIGH, all writes are ignored
"0" Indicates that the related register bit is tied off to logic LOW, all writes are ignored
“+” Indicates that the related register bit is readable and writable
The LPC2917/19 contains a very flexible and powerful Vectored Interrupt Controller (VIC)
to interrupt the ARM processor on request.
The key features are:
• Level-active interrupt request with programmable polarity
• 56 interrupt-request inputs
• Software-interrupt request capability associated with each request input
• Observability of interrupt-request state before masking
• Software-programmable priority assignments to interrupt requests up to 15 levels
• Software-programmable routing of interrupt requests towards the ARM-processor
inputs IRQ and FIQ
• Fast identification of interrupt requests through vector
• Support for nesting of interrupt service routines
8.9.2Description
The Vectored Inter rupt Controller routes incoming interrupt requests to the ARM
processor. The interrupt target is configured for each interrupt request input of the VIC.
The targets are defined as follows:
• Target 0 is ARM processor FIQ (fast interrupt service)
• Target 1 is ARM processor IRQ (standard interrupt service)
Preliminary data sheetRev. 1.01 — 15 November 2007 50 of 68
NXP Semiconductors
Interrupt-request masking is perfor me d indiv idually per interrupt target by comparing the
priority level assigned to a specific interrupt request with a target-specific priority
threshold. The priority levels are defined as follows:
• Priority level 0 corresponds to ‘masked’ (i.e. interrupt requests with priority 0 never
• Priority 1 corresponds to the lowest priority
• Priority 15 corresponds to the highest priority
Software interrupt support is provided and can be supplied for:
• Testing RTOS interrupt handling without using device-specific interrupt service
• Software emulation of an interrupt-requesting device, including interrupts
8.9.3VIC pin description
The VIC module in the LPC2917/19 has no external pins.
lead to an interrupt)
routines
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
DR
AFT
DRAFT
DR
F
T DRAF
8.9.4VIC clock description
The VIC is clocked by CLK_SYS_VIC, see Section 7.2.2.
9.Limiting values
Table 28.Limiting values
In accordance with the Absolute Maximum Rating System (IEC 60134).
SymbolParameterConditionsMinMaxUnit
Supply pins
P
tot
V
DD(CORE)
V
DD(OSC_PLL)
V
DD(ADC3V3)
V
DD(IO)
I
DD
I
SS
Input pins and I/O pins
V
XIN_OSC
V
XIN_RTC
V
I(IO)
V
I(ADC)
V
VREFP
V
VREFN
I
I(ADC)
Output pins and I/O pins configured as output
Total power dissipation.
Core supply voltage.−0.5+2.0V
Oscillator and PLL supply
voltage.
3.3 V ADC supply voltage.−0.5+4.6V
I/O digital supply voltage.−0.5+4.6V
Supply current.Average value per supply
Ground current.Average value per ground
Voltage on pin XIN_OSC.−0.5+2.0V
Voltage on pin XIN_RTC.−0.5+2.0V
I/O input voltage.
ADC input voltage.I/O port 0.
Voltage on pin VREFP.−0.5+3.6V
Voltage on pin VREFN.−0.5+3.6V
ADC input current.Average value per input pin.
Endurance of flash memory.-100000cycle
Flash memory retention
time.
Electrostatic discharge
V
esd
Electrostatic discharge
voltage.
…continued
Drive HIGH, output shorted
[9]
-−33mA
to VSS(IO).
Drive LOW, output shorted
[9]
-+38mA
to VDD(IO).
[6]
−40+125°C
-20year
On all pins.
[7]
Human body model.
Machine model.
−2000+2000V
[8]
−200+200V
Charged device model.−500+500V
On corner pins.
Charged device model.-750+750V
AFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
[1] Based on package heat transfer, not device power consumption.
[2] Peak current must be limited at 25 times average current.
[3] For I/O Port 0, the maximum input voltage is defined by V
[4] Only when V
[5] Note that pull-up should be off. With pull-up do not exceed 3.6 V.
[6] In accordance with IEC 60747-1. An alternative definition of the virtual junction temperature is: T
a fixed value; see Section 10
[7] Human-body model: discharging a 100 pF capacitor via a 10 kΩ series resistor.
[8] Machine model: discharging a 200 pF capacitor via a 0.75 μH series inductance and 10 Ω resistor.
[9] 112 mA per V
DD(IO)
DD(IO)
is present.
or V
SS(IO)
. The rating for Tvj limits the allowable combinations of power dissipation and ambient temperature.
Preliminary data sheetRev. 1.01 — 15 November 2007 54 of 68
DRAFT
NXP Semiconductors
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
DRAFT
ARM9 microcontroller with CAN and LIN
F
T DRAFT DRAFT DRAFT DRA
Table 30. Static characteristics
V
DD(CORE)=VDD(OSC_PLL)
; V
measured with respect to ground; positive currents flow into the IC; unless otherwise specified.
SymbolParameterConditionsMinTypMaxUnit
Oscillator
R
C
s(xtal)
i
Crystal series resistance.f
Input capacitance of
XIN_OSC.
Power-up reset
V
trip(high)
V
trip(low)
V
trip(dif)
High trip-level voltage.
Low trip-level voltage.
Difference between high
and low trip-level
voltages.
…continued
= 2.7 V to 3.6 V; V
DD(IO)
DD(A3V3)
= 10 MHz to 15 MHz
osc
C
=10pF;
xtal
C
=18pF
ext
=20pF;
C
xtal
C
=39pF
ext
= 15 MHz to 20 MHz
f
osc
C
=10pF;
xtal
=18pF
C
ext
= 3.0 V to 3.6 V; Tvj=-40°Cto+125°C; all voltages are
[1]
[5]
--160Ω
--60Ω
[5]
--80Ω
[9]
-2pF
[6]
1.21.41.6V
[6]
1.11.31.5V
[6]
50120180mV
AFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
[1] All parameters are guaranteed over the virtual junction temperature range by design. Pre-testing is performed at T
level. Cased products are tested at T
the specified temperature and power-supply voltage range.
[2] Leakage current is exponential to temperature; worst-case value is at 125 C Tvj. All clocks off. Analog modules and FLASH powered
down.
[3] For Port 0, pin 0 to pin 15 add maximum 1.5 pF for input capacitance to ADC. For Port 0, pin 16 to pin 31 add maximum 1.0 pF for input
capacitance to ADC.
[4] This value is the minimum d rive capability. Maximum short-circuit output current is 33 mA (drive HIGH-level, shorted to ground) or
−38 mA. (drive LOW-level, shorted to V
[5] C
[6] The power-up reset has a time filter: V
[7] Not 5 V-tolerant when pull-up is on.
[8] For I/O Port 0, the maximum input voltage is defined by V
[9] This parameter is not part of production testing or final testing, hence only a typical value is stated. Maximum and minimum values are
is crystal load capacitance and C
xtal
V
for 11 μs before internal reset is asserted.
trip(low)
based on simulation results.
=25 °C (final testing). Both pre-testing and final testing use correlated test conditions to cover
amb
). The device will be damaged if multiple outputs are shorted.
DD(IO)
are the two external load capacitors.
ext
DD(CORE)
must be above V
I(ADC)
.
for 2 μs before reset is de-asserted; V
trip(high)
= 125 °C on wafer
amb
DD(CORE)
must be below
12. Dynamic characteristics
Table 31. Dynamic characteristics
V
DD(CORE)=VDD(OSC_PLL)
respect to ground; positive currents flow into the IC; unless otherwise specified.
SymbolParameterConditionsMinTypMaxUnit
I/O pins
t
THL
t
TLH
; V
DD(IO)
HIGH-to-LOW
transition time.
LOW-to-HIGH
transition time.
= 2.7 V to 3.6 V; V
CL= 30 pF4-13.8ns
CL= 30 pF4-13.8ns
DD(A3V3)
= 3.0 V to 3.6 V; Tvj=−40 °C; all voltages are measured with
Preliminary data sheetRev. 1.01 — 15 November 2007 56 of 68
DRAFT
NXP Semiconductors
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
ARM9 microcontroller with CAN and LIN
F
T DRAFT DRAFT DRAFT DRA
Table 31. Dynamic characteristics
V
DD(CORE)=VDD(OSC_PLL)
; V
DD(IO)
respect to ground; positive currents flow into the IC; unless otherwise specified.
SymbolParameterConditionsMinTypMaxUnit
t
a(W)int
Internal write-access
time.
UART
f
UART
UART frequency.
SPI
f
SPI
SPI operating
frequency.
Jitter Specification
CANt
jit(cc)(p-p)
CAN TXD pin
Cycle-to-cycle jitter
(peak-to-peak value).
…continued
= 2.7 V to 3.6 V; V
Master operation.
Slave operation.
[2]
DD(A3V3)
= 3.0 V to 3.6 V; Tvj=−40 °C; all voltages are measured with
--24.9ns
1
⁄
65024fclk(uart)
1
⁄
65024fclk(spi)
1
⁄
65024fclk(spi)
-
-
-
1
⁄
2fclk(uart)
1
⁄
2fclk(spi)
1
⁄
4fclk(spi)
MHz
MHz
MHz
-0.41ns
DR
AFT
DRAFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
[1] All parameters are guaranteed over the virtual junction temperature range by design. Pre-testing is performed at T
temperature on wafer level. Cased products are tested at T
test conditions to cover the specified temperature and power supply voltage range.
[2] This parameter is not part of production testing or final testing, hence only a typical value is stated.
[3] Oscillator start-up time depends on the quality of the crystal. For most crystals it takes about 1000 clock pulses until the clock is fully
stable.
[4] Duty cycle clock should be as close as possible to 50%.
=25°C (final testing). Both pre-testing and final testing use correlated
Preliminary data sheetRev. 1.01 — 15 November 2007 58 of 68
NXP Semiconductors
14. Soldering
14.1Introduction
There is no soldering method that is ideal for all surface mount IC packages. Wave
soldering can still be used for certain surface mount ICs, but it is not suitable for fine pitch
SMDs. In these situations reflow soldering is recommended.
14.2Through-hole mount packages
14.2.1Soldering by dipping or by solder wave
Typical dwell time of the leads in the wave ranges from 3 seconds to 4 seconds at 250 °C
or 265 °C, depending on solder material applied, SnPb or Pb-free respectively.
The total contact time of successive solder waves must not exceed 5 seconds.
The device may be mounted up to the seating plane, but the temperature of the plastic
body must not exceed the specified maximum storage temperature (T
printed-circuit board has been pre-heated, forced cooling may be necessary immediately
after soldering to keep the temperature within the permissible limit.
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
F
T DRAFT DRAFT DRAFT DRA
stg(max)
DR
AFT
DRAFT
DRA
). If the
DR
AFT
DRAFT
DR
F
T DRAF
14.2.2Manual soldering
Apply the soldering iron (24 V or less) to the lead(s) of the package, either below the
seating plane or not more than 2 mm above it. If the temperature of the soldering iron bit is
less than 300 °C it may remain in contact for up to 10 seconds. If the bit temperature is
between 300 °C and 400 °C, contact may be up to 5 seconds.
14.3Surface mount packages
14.3.1Reflow soldering
Key characteristics in reflow soldering are:
• Lead-free versus SnPb soldering; note that a lead-free reflow process usually lea ds to
higher minimum peak temperatures (see Figure 16
reducing the process window
• Solder paste printing issues including smearing, release, and adjusting the process
window for a mix of large and small components on one board
• Reflow temperature profile; this profile includes preheat, reflow (in which the board is
heated to the peak temperature) and cooling down. It is imperative that the peak
temperature is high enough for the solder to make reliable solder joint s (a solder paste
characteristic). In addition, the peak temperature must be low enough that the
packages and/or boards are not damaged. The peak temperature of the package
depends on package thickness and volume and is classified in accordance with
Preliminary data sheetRev. 1.01 — 15 November 2007 59 of 68
NXP Semiconductors
001aac844
temperature
time
minimum peak temperature
= minimum soldering temperature
maximum peak temperature
= MSL limit, damage level
peak
temperature
Table 32.SnPb eutectic process (from J-STD-020C)
Package thickness (mm)Package reflow temperature (°C)
< 2.5235220
≥ 2.5220220
Table 33.Lead-free process (from J-ST D-020C)
Package thickness (mm)Package reflow temperature (°C)
< 1.6260260260
1.6 to 2.5260250245
> 2.5250245245
DRAFT
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
ARM9 microcontroller with CAN and LIN
F
Volume (mm3)
< 350≥ 350
Volume (mm3)
< 350350 to 2000> 2000
D
RAFT
DR
DRAFT
T DRAFT DRAFT DRAFT DRA
AFT
DRA
DR
AFT
DRAFT
DR
F
T DRAF
Moisture sensitivity precautions, as indicated on the packing, must be respected at all
times.
Studies have shown that small packages reach higher temperatures during reflow
soldering, see Figure 16
Fig 16. Temperature profiles for large and small components
For further information on temperature profiles, refer to Application Note AN10365
“Surface mount reflow soldering description”.
.
MSL: Moisture Sensitivity Level
14.3.2Wave soldering
Conventional single wave soldering is not recommended for surface mount devices
(SMDs) or printed-circuit boards with a high component density, as solder bridging and
non-wetting can present major problems.
Preliminary data sheetRev. 1.01 — 15 November 2007 60 of 68
NXP Semiconductors
To overcome these problems the double-wave soldering method was specifically
developed.
If wave soldering is used the following conditions must be observed for optim al re su lts:
• Use a double-wave soldering method comprising a turbulent wave with high upwar d
• For packages with leads on two sides and a pitch (e):
• For packages with leads on four sides, the footprint must be placed at a 45° angle to
DRAFT
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
pressure followed by a smooth laminar wave.
– larger than or eq ua l to 1.2 7 mm, the footprint longitudinal axis is preferred to be
parallel to the transport direction of the printed-circuit board;
– smaller than 1.27 mm, the footprint longitudinal axis must be parallel to the
transport direction of the printed-circuit board.
The footprint must incorporate solder thieves at the downstream end.
the transport direction of the printed-circuit board. The footprint must incorporate
solder thieves downstream and at the side corne r s.
DR
AFT
DRAFT
DR
F
T DRAF
During placement and before soldering, the package must be fixed with a droplet of
adhesive. The adhesive can be applied by screen printing, pin transfer or syringe
dispensing. The package can be soldered after the adhesive is cured.
Typical dwell time of the leads in the wave ranges from 3 seconds to 4 seconds at 250 °C
or 265 °C, depending on solder material applied, SnPb or Pb-free respectively.
A mildly-activated flux will eliminate the need for removal of corrosive residues in most
applications.
14.3.3Manual soldering
Fix the component by first soldering two diagona lly-opposite end leads. Use a low voltag e
(24 V or less) soldering iron applied to the flat part of the lead. Contact time must be
limited to 10 seconds at up to 300 °C.
When using a dedicated tool, all other leads can be soldered in one operation within
2 seconds to 5 seconds between 270 °Cand320°C.
14.4Package related soldering information
Table 34. Suitability of IC packages for wave, reflow and dipping soldering methods
[1] For more detailed information on the BGA packages refer to the (LF)BGA Application Note (AN01026); order a copy from your NXP
Semiconductors sales office.
[2] All surface mount (SMD) packages are moisture sensitive. Depending upon the moisture content, the maximum temperature (with
respect to time) and body size of the package, there is a risk that internal or external package cracks may occur due to vaporization of
the moisture in them (the so called popcorn effect).
[3] For SDIP packages, the longitudinal axis must be parallel to the transport direction of the p rinted-circuit board.
[4] Hot bar soldering or manual soldering is suitable for PMFP packages.
[5] These transparent plastic packages are extremely sensitive to reflow soldering conditions and must on no account be processed
through more than one soldering cycle or subjected to infrared reflow soldering with peak temperature exceeding 217 °C ± 10 °C
measured in the atmosphere of the reflow oven. The package body peak temperature must be kept as low as possible.
[6] These packages are not suitable for wave soldering. On versions with the heatsink on the bottom side, the solder cannot penetrate
between the printed-circuit board and the heatsink. On versions with the heatsink on the top side, the solder might be deposited on the
heatsink surface.
[7] If wave soldering is considered, then the package must be placed at a 45° angle to the solder wave direction. The package footprint
must incorporate solder thieves downstream and at the side corners.
[8] Wave soldering is suitable for LQFP, QFP and TQFP packages with a pitch (e) larger than 0.8 mm; it is definitely not suitable for
packages with a pitch (e) equal to or smaller than 0.65 mm.
[9] Wave soldering is suitable for SSOP, TSSOP, VSO and VSSOP p ackages with a pitch (e) equal to or larger than 0.65 mm; it is definitely
not suitable for packages with a pitch (e) equal to or smaller than 0.5 mm.
[10] Image sensor packages in principle should not be soldered. They are mounted in sockets or delivered pre-mounted on flex foil.
However, the image sensor package can be mounted by the client on a flex foil by using a hot bar soldering process. The appropriate
Preliminary data sheetRev. 1.01 — 15 November 2007 62 of 68
NXP Semiconductors
15. Abbreviations
Table 35.Abbreviations list
AbbreviationDescription
AHBAdva nced High-performance Bus
BCLBuffer Control List
BDLBuffer Descriptor List
CISCComplex Instruction Set Computer s
DTLDevice Transaction Level
SFSPSCU Function Select Port x,y (use without the P if there are no x,y)
SCLSlot Control List
BELBuffer Entry List
CCOCurrent Controlled Oscillator
BISTBuilt-In Self Test
RISCReduced Instruction Set Computer
UARTUniversal Asynchronous Receiver Transmitter
VPBVLSI Peripheral bus
Preliminary data sheetRev. 1.01 — 15 November 2007 65 of 68
DRAFT
NXP Semiconductors
ARM9 microcontroller with CAN and LIN
D
RAFT DRAFT DRAFT DRAFT DRAFT D
D
LPC2917/19
RAFT DRA
D
RAFT
DR
AFT
DRAFT
DRA
F
T DRAFT DRAFT DRAFT DRA
18. Legal information
18.1Data sheet status
Document status
Objective [short] data sheetDevelopmentThis document contains data from the objective specification for product development.
Preliminary [short] data sheet QualificationThis document contains data from the pre liminary specification.
Product [short] data sheetProductionThis document contains the product specification.
[1] Please consult the most recently issued document before initiating or completing a design.
[2] The term ‘short data sheet’ is explained in section “Definitions”.
[3] The product status of device(s) described in this docu ment may have changed si nce this d ocument was pub lished and may dif fer in case of multiple devices. The latest product st atus
information is available on the Internet at URL http://www.nxp.com.
[1][2]
Product status
[3]
Definition
DR
AFT
DRAFT
DR
F
T DRAF
18.2Definitions
Draft — The document is a draft version only. The content is still under
internal review and subject to formal approval, 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 u pon to co nt ain det ailed and
full information. For detailed and full information see the relevant full data
sheet, which is available on request via the local NXP Semiconductors sales
office. In case of any inconsistency or conflict with the short data sheet, the
full data sheet shall prevail.
18.3Disclaimers
General — Information in this document is believed to be accurate and
reliable. However, NXP Semiconduct ors does not give any repr esentatio ns 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.
Right to make changes — NXP Semiconductors reserves the right to make
changes to information published 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 a NXP Semiconductors product can reasonably be expected t o
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.
Limiting values — Stress above one or more limiting values (as defined in
the Absolute Maximum Ratings System of IEC60134) may cause permanent
damage to the device. Limiting values are stress ratings only and operation of
the device at these or any other conditions above those given in the
Characteristics sections of this document is not implied. Exposure to limiting
values for extended periods may affect device reliability.
Terms and conditions of sale — NXP Semiconductors products are sold
subject to the general terms and conditions of commercial sale, as published
at http://www.nxp.com/profile/terms
intellectual property rights infringement and limitation of liability, unless
explicitly otherwise agreed to in writing by NXP Semiconductors. In case of
any inconsistency or conflict between information in this document and such
terms and conditions, the latter will prevail.
No offer to sell or license — Nothing in this document may be interpreted or
construed as an offer to sell product s that is ope n for accept ance or the gr ant,
conveyance or implication of any license under any copyrights, patents or
other industrial or intellectual property rights.
, including those pertaining to warranty,
18.4Trademarks
Notice: All referenced brands, prod uct names, service names and trad emarks
are the property of their respective owners.
2
I
C-bus — logo is a trademark of NXP B.V.
19. Contact information
For additional information, please visit: http://www.nxp.com
For sales office addresses, send an email to: salesaddresses@nxp.com
Please be aware that important notices concerning this docum ent and the product(s)
described herein, have been included in section ‘Legal information’.