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.