• SPI SSEL line conditioning added (see Table 12–159 “SPI pin description”).
2.020070123
• Details on LPC2210/01 device added into the document.
• The format of this data sheet has been redesigned to comply with the new identity
guidelines of NXP Semiconductors.
• Legal texts have been adapted to the new company name where appropriate.
1.020051012Moved the UM document into the new structured FameMaker template. Many changes were
made to the format throughout the document. Here are the most important:
• UART0 and UART1 description updated (fractional baudrate generator and hardware
handshake features added - auto-CTS/RTS)
• ADC chapter updated with the dedicated result registers
• GPIO chapter updated with the descri ption of the Fast IOs
Contact information
For additional information, please visit: http://www.nxp.com
For sales office addresses, please send an email to: salesaddresses@nxp.com
The LPC2210/2220 and LPC2210/01 microcontrollers are based on a 16/32 bit
ARM7TDMI-S CPU with real-time emulation and embedded trace support. For critical
code size applications, the alternative 16-bit Thumb Mode reduces code by more than
30 % with minimal performance penalty.
With a 144 pin package, low power consumption, various 32 bit timers, 8 Channel 10 bit
ADC, PWM channels and up to nine external interrupt pins this microcontroller is
particularly suitable for industrial control, medical systems, access control and
point-of-sale. LPC2210/2220 and LPC2210/01 can provide up to 76 GPIO depending on
bus configuration. With a wide range of serial communications interfaces, it is also very
well suited for communication gateways, protocol converters a nd embedded sof t modems
as well as many other general-purpose applications.
2.Features introduced with LPC2210/01 and LPC2220 over LPC2210
• CPU clock up to 75 MHz.
• Fast IO registers are located on the ARM local bus for the fastest possible I/O timing.
• All GPIO registers are byte addressable.
• Entire port value can be written in one instruction.
• Mask registers allow single instruction to set or clear any number of bits in one port.
• TIMER0/1 can be driven by an external clock/can count external events
• Powerful Fractional baud rate generator with autobauding capabilities provides
standard baud rates such as 115200 with any crystal frequency above 2 MHz.
• UART1 is equipped with auto-CTS/RTS flow-control fully implemented in hardware.
• SSP serial controller supporting SPI/4-wire SSI and Microwire buses
• Every analog input has a dedicated result regis te r to re du ce inte rr up t ov er he ad .
• Every analog input can generate an interrupt once the conversion is completed.
3.Features
• 16/32-bit ARM7TDMI-S microcontroller in a LQFP144 and TFBGA144 package
• 16 kB (LPC2210 and LPC2210/01) or 64 kB (LPC2220) of on-chip static RAM.
• Serial boot-loader using UART0 provides in-system download and programming
capabilities.
• EmbeddedICE-RT and Embedded T race interface s offer real-tim e debugging with the
on-chip RealMonitor software and high speed tracing of instruction execution.
• Eight channel 10-bit A/D converter with a dedicated result register for every channel
and conversion time as low as 2.44 μs.
• Two 32-bit timers/external event counters with four capture and four compare
channels each, PWM unit (six outputs), Real-Time Clock (RTC) and watchdog.
• Serial interfaces include two UARTs (16C550), Fast I
2
C (400 kbit/s), and two SPIs.
• Vectored Interrupt Controller (VIC) with configurable priorities and vector addresses.
• Configurable external memory interface with up to four banks, each up to 16 MB and
8/16/32 bit data width.
• Up to 76 general purpose Fast I/O pins (5 V tolerant) capable of toggling a GPIO pin
at 15 MHz. Up to nine edge or level sensitive external interrupt pins available.
• Up to 60 MHz (LPC2210) and 75 MHz (LPC2210/01 and LPC2220) maximum CPU
clock available from programmable on-chip Phase-Locked Loop (PLL) with settling
time of 100 μs.
• On-chip integrated oscillator operates with an external crystal in range of 1 MHz to
30 MHz and with external oscillator up to 50 MHz.
• Power saving modes include Idle and Power-down.
• Processor wake-up from Power-down mode via external interrupt.
• Individual enable/disable of peripheral functions for power optimization.
• Dual power supply:
– CPU operating voltage range of 1.65 V to 1.95 V (1.8 V ±0.15 V).
– I/O power supply range of 3.0 V to 3.6 V (3.3 V ±10 %) with 5 V tolerant I/O pads.
LPC2210/20 and LPC2210/01 consist of an ARM7TDMI-S CPU with emulation support,
the ARM7 Local Bus for interface to on-chip memory controllers and Fast GPIO, the
AMBA Advanced High-performance Bus (AHB) for interface to the interrupt controller, and
the VLSI Peripheral Bus (APB, a compatible superset of ARM’s AMBA Advanced
Peripheral Bus) for connection to on-chip peripheral functions. The LPC2210/2220 and
LPC2210/01 microcontroller configure the ARM7TDMI-S processor in little-endian byte
order and this can not be altered by user.
AHB peripherals are allocated a 2 megabyte range of addresses at the very top of the
4 gigabyte ARM memory space. Each AHB peripheral is allocated a 16 kB address space
within the AHB address space. LPC2210/2220 and LPC2210/01 peripheral functions
(other than the interrupt controller) are connected to the APB bus. The AHB to APB bridge
interfaces the APB bus to the AHB bus. APB peripherals are also allocated a 2 megabyte
range of addresses, beginning at the 3.5 gigabyte address point. Each APB peripheral is
allocated a 16 kB address space within the APB address space.
The connection of on-chip peripherals to device pins is controlled by a Pin Connect Block,
see Section 7–4
requirements for the use of peripheral functions and pins.
UM10114
Chapter 1: LPC2210/20 Introductory information
. This must be configured by software to fit specific application
7.ARM7TDMI-S Processor
The ARM7TDMI-S is a general purpose 32-bit microprocessor, 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 microprogrammed Complex
Instruction Set Computers. This simplicity results in a high instruction throughput and
impressive real-time interrupt response from a small and cost-effective processor core.
Pipeline techniques are employed so that all part s of the pro cessing and memory systems
can operate continuously. Typically, while one instruction is being executed, its successor
is being decoded, and a third instruction is being fetched from memory.
The ARM7TDMI-S processor also employs a unique architectural strategy known as
THUMB, which makes it ideally suited to high-volume applications with memory
restrictions, or applications where code density is an issue.
The key idea behind THUMB is that of a super-reduced instruction set. Essentially, the
ARM7TDMI-S processor has two instruction sets:
• The standard 32-bit ARM instruction set.
• A 16-bit THUMB instruction 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 processor using 16-bit registers. This is possible because THUMB code
operates on the same 32-bit register set as ARM code.
THUMB code is able to provide up to 65% of the code size of ARM, and 160% of the
performance of an equivalent ARM processor connected to a 16-bit memory system.
The ARM7TDMI-S processor is described in detail in the ARM7TDMI-S Datasheet that
can be found on official ARM website.
8.On-Chip bootloader
The microcontroller incorporates an on-chip serial boot-loader located in a 8 kB ROM.
Using UART0, this utility enables the loading an application into the microcontroller’s RAM
for execution. Typically, an application loaded and executed from RAM would take care of
programming of off-chip Flash memory with user’s code.
9.On-Chip Static RAM
On-Chip Static RAM (SRAM) may be used for code and/or data storage. The on-chip
SRAM may be accessed as 8-bits, 16-bits, and 32-bits. The LPC2210 and LPC2210/01
provide 16 kB of static RAM while LPC2220 provides 64 kB of static RAM.
The microcontroller’s SRAM is designed to be accessed as a byte-addressed memory.
Word and halfword accesses to the memory ignore the alignment of the address and
access the naturally-aligned value that is addressed (so a memory access ignores
address bits 0 and 1 for word accesses, and ignores bit 0 for halfword accesses).
Therefore valid reads and writes require data accessed as halfwords to originate from
addresses with address line 0 being 0 (addresses ending with 0, 2, 4, 6, 8, A, C, and E in
hexadecimal notation) and data accessed as words to originate from addresses with
address lines 0 and 1 being 0 (addresses ending with 0, 4, 8, and C in hexadecimal
notation). This rule applies to both off and on-chip memory usage.
UM10114
Chapter 1: LPC2210/20 Introductory information
The SRAM controller incorporates a write-back buffer in order to prevent CPU stalls
during back-to-back writes. The write-back buffer always holds the last data sent by
software to the SRAM. This data is only written to the SRAM when another write is
requested by software (the data is only written to the SRAM when software does another
write). If a chip reset occurs, actual SRAM contents will not reflect the most recent write
request (i.e. after a "warm" chip reset, the SRAM does not reflect the last wr ite operation).
Any software that checks SRAM contents after reset must take this into account. Two
identical writes to a location guarantee that the data will be present after a Reset.
Alternatively, a dummy write operation before entering idle or power-down mode will
similarly guarantee that the last data written will be present in SRAM after a subsequent
Reset.
(1) When debug interface is used, GPIO/other functions sharing these pins are not available.
(2) Shared with GPIO.
Fig 1. LPC2210/2220 and LPC2210/01 block diagram
AHB PERIPHERALS
APB PERIPHERALS
RESERVED ADDRESS SPACE
BOOT BLOCK (RE-MAPPED FROM
ON-CHIP ROM MEMORY
RESERVED ADDRESS SPACE
64 KBYTE ON-CHIP STATIC RAM (LPC2220)
16 KBYTE ON-CHIP STATIC RAM
(LPC2210, LPC2210/01)
RESERVED ADDRESS SPACE
0xFFFF FFFF
0xF000 0000
0xEFFF FFFF
0xE000 0000
0xDFFF FFFF
0x8400 0000
0x7FFF FFFF
0x7FFF E000
EXTERNAL MEMORY BANK 3
0x83FF FFFF
0x8300 0000
EXTERNAL MEMORY BANK 2
0x82FF FFFF
0x8200 0000
EXTERNAL MEMORY BANK 1
0x81FF FFFF
0x8100 0000
EXTERNAL MEMORY BANK 0
0x80FF FFFF
0x8000 0000
0x7FFF DFFF
0x4000 4000
0x4000 3FFF
0x4001 0000
0x4000 FFFF
0x4000 0000
0x3FFF FFFF
4.0 GB
3.75 GB
3.5 GB
3.0 GB
2.0 GB
1.0 GB
0x0000 0000
0.0 GB
002aaa795
1.Memory maps
The LPC2210/2220 and LPC2210/01 incorporate several d istinct memory r egions, shown
in the following figures. Figure 2–2
from the user program viewpoint following reset. The interrupt vector area supports
address remapping, which is described later in this section.
Figures 3 through 4 and Table 2–2 show different views of the peripheral address space.
Both the AHB and APB peripheral areas are 2 megabyte sp aces which are divided up into
128 peripherals. Each peripheral space is 16 kilobytes in size. This allows simplifying the
address decoding for each peripheral. All peripheral register addresses are word aligned
(to 32-bit boundaries) regardless of their size. This eliminates the need for byte lane
mapping hardware that would be required to allow byte (8-bit) or half-wor d (16-bit)
accesses to occur at smaller boundaries. An implication of this is that word and half-word
registers must be accessed all at once. For example, it is not possible to read or write the
upper byte of a word register separately.
UM10114
Chapter 2: LPC2210/20 Memory map
AHB section is 128 x 16 kB blocks (totaling 2 MB).
APB section is 128 x 16 kB blocks (totaling 2MB).
230xE005 C000SSP (LPC2210/01 and LPC2220 only)
24 - 1260xE006 0000
1270xE01F C000System Control Block
0xE005 8000
0xE01F 8000
2
C
Not used
Not used
UM10114
Chapter 2: LPC2210/20 Memory map
2.LPC2210/2220 Memory re-mapping and boot block
2.1Memory map concepts and operating modes
The basic concept on the LPC2210/2220 and L PC2210 /0 1 is that ea ch memor y a rea ha s
a "natural" location in the memory map. This is the address range for which code residing
in that area is written. The bulk of each memory space remains permanently fixed in the
same location, eliminating the need to have portions of the code designed to run in
different address ranges.
Because of the location of the interrupt vectors on the ARM7 processor (at addresses
0x0000 0000 through 0x0000 001C, as shown in Table 2–3
Boot Block and SRAM spaces need to be re-mapped in order to allow alternative uses of
interrupts in the different operating modes described in Table 2–4
interrupts is accomplished via the Memory Mapping Control features.
Table 4.LPC2210/2220 and LPC2210/01 Memory Mapp ing Modes
ModeActivationUsage
Boot
Loader
mode
User RAM
mode
User
External
mode
Hardware
activation by
any Reset
Software
activation by
User program
Activated by
BOOT1:0
pins
UM10114
Chapter 2: LPC2210/20 Memory map
Note: Identified as reserved in ARM documentation.
The Boot Loader always executes after any reset. The Boot Block
interrupt vectors are mapped to the bottom of memory to allow
handling exceptions and using interrupts during the Boot Loading
process.
Activated by a User Program as desired. Interrupt vectors are
re-mapped to the bottom of the Static RAM.
Activated by Boot Loader when P0.14 is not LOW at the end of
RESET LOW. Interrupt vectors are re-mapped from the bottom of the
external memory map.
2.2Memory re-mapping
In order to allow for compatibility with future derivatives, the entire Boot Block is mapped
to the top of the on-chip memory space. Memory spaces other than the interrupt vectors
remain in fixed locations. Figure 2–5
defined above.
The portion of memory that is re-mapped to allow interrupt processing in different modes
includes the interrupt vector area (32 bytes) and an additional 32 bytes, for a total of
64 bytes. The re-mapped code locations overlay addresses 0x0000 0000 through
0x0000 003F. The vector contained in the SRAM, external memory, and Boot Block must
contain branches to the actual interrupt handlers, or to other instructions that accomplish
the branch to the interrupt handlers.
There are two reasons this configuration was chosen:
1. Minimize the need for the SRAM and Boot Block vectors to deal with arbitrary
boundaries in the middle of code space.
2. To provide space to store constants for jumping beyond the range of single word
branch instructions.
Re-mapped memory areas, including the Boot Block and interrupt vectors, continue to
appear in their original location in addition to the re-mapped address.
Details on re-mapping and examples can be found in Section 4–7 “
Fig 5. Map of lower memory is showing re-mapped and re-ma p pable areas
User manualRev. 02 — 27 April 2007 13 of 290
NXP Semiconductors
3.Prefetch abort and data abort exceptions
The LPC2210/2220 and LPC2210/01 generate the appropriate bus cycle abort exception
if an access is attempted for an address that is in a reserved or unassigned address
region. The regions are:
• Areas of the memory map that are not implemented for a specific ARM derivative. Fo r
the LPC2210/2220 and LPC2210/01, this is:
– Address space between the re-mapped interrupt vector area and an On-Chip
SRAM, labelled "Reserved Address Space" in Figure 2–2
an address range from 0x0000 0040 to 0x3FFF FFFF.
– Address space between On-Chip Static RAM and Boot Block. Labelled "Reserved
Address Space" in Figure 2–2
range from 0x4000 4000 to 0x7FFF DFFF and for LPC2220 this is an address
range from 0x4001 0000 to 0x7FFF DFFF.
– Address space between 0x8400 0000 to 0xDFFF FFFF, labelled "Reserved
Address Space".
– Reserved regions of the AHB and APB spaces. See Figure 2–3
• Unassigned AHB peripheral spaces. See Figure 2–4.
• Unassigned APB peripheral spaces. See Table 2–2.
. For LPC2210 and LPC2210/01 this is an address
UM10114
Chapter 2: LPC2210/20 Memory map
and Figure 2–5. This is
and Table 2–2.
For these areas, both attempted data acce ss and in struction fetch genera te an exception.
In addition, a Prefetch Abort exception is generated for any instruction fetch that maps to
an AHB or APB peripheral address.
Within the address space of an existing APB peripheral, a data abort exception is not
generated in response to an access to an undefined address. Address decoding within
each peripheral is limited to that needed to distinguish defined registers within the
peripheral itself. For example, an access to address 0xE000 D000 (an undefined address
within the UART0 space) may result in an access to the register defined at address
0xE000 C000. Details of such address aliasing within a peripheral space are not defined
in the LPC2210/2220 and LPC2210/01 documentation and are not a supported feature.
Note: The ARM core stores the Prefetch Abort flag along with the associated instruction
(which will be meaningless) in the pipeline and processes the abort only if an attempt is
made to execute the instruction fetched from the illegal address. This prevents accidental
aborts that could be caused by prefetches that occur when code is executed very near a
memory boundary.
• Support for various static memory-mapped devices including RAM, ROM, flash, burst
ROM, and some external I/O devices
• 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 four banks, each up to 16 M Bytes
• Programmable bus turnaround (idle) cycles (1 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 read byte lane enable control
2.Description
The external Static Memory Controller is an AMBA AHB slave module which provides an
interface between an AMBA AHB system bus and external (off-chip) memory devices. It
provides support for up to four independently configurable memory banks simult aneously.
Each memory bank is capable of supporting SRAM, ROM, Flash EPROM, Burst ROM
memory, or some external I/O devices .
Each memory bank may be 8, 16, or 32 bits wide.
Since the LPC2210/20 144 pin package pins out addre ss line s A[23:0] only, the decoding
among the four banks uses address bits A[25:24]. The native lo catio n of th e four ban ks is
at the start of the External Memory area identified in Figure 2–2 on page 8
be used for initial booting under control of the state of the BOOT[1:0] pins.
Table 5.Address ranges of the external memory banks
Table 6.Exter nal Me mory Controller pin description
Pin nameTypePin description
D[31:0]Input/OutputExternal memory Data lines
A[23:0]OutputExternal memory Address lines
OEOutputLow-active Output Enable signal
BLS[3:0]OutputLow-active Byte Lane Select signals
WEOutputLow-active Write Enable signal
CS[3:0]OutputLow-active Chip-Select signals
4.Register description
The external memory controller contains 4 registers as shown in Table 3–7.
Table 7.Exter nal Me mory Controller register map
NameDescriptionAccess Reset value,
BCFG0 Configuration register for memory bank 0R/W0x0000 FBEF0xFFE0 0000
BCFG1 Configuration register for memory bank 1R/W0x2000 FBEF0xFFE0 0004
BCFG2 Configuration register for memory bank 2R/W0x1000 FBEF0xFFE0 0008
BCFG3 Configuration register for memory bank 3R/W0x0000 FBEF0xFFE0 000C
UM10114
Chapter 3: LPC2210/20 EMC
Address
see Table 9.
Each register selects the following options for its memory bank:
• The number of idle clock cycles inserted between read and write accesses in this
bank, and between an access in another bank and an access in this bank, to avoid
bus contention between devices (1 to 17 clocks)
• The length of read accesses, except for subsequent reads from a burst ROM (3 to 35
Table 8.Bank Con f iguration Registers 0-3 (BCFG0-3 - 0xFFE0 0000 to 0xFFE0 000C)
BCFG0-3 NameFunctionReset
3:0IDCYThis field controls the minimum number of “idle” CCLK cycles
4-Reserved, user software should not write ones to reserved bits.
9:5WST1This field controls the length of read accesses (except for
10RBLEThis bit should be 0 for banks composed of byte-wide or
15:11WST2For SRAM banks, this field controls the length of write accesses,
23:16-Reserved, user software should not write ones to reserved bits.
24BUSERR The only known case in which this bit is set is if the EMC detects
25WPERRThis bit is set if software attempts to write to a bank that has the
26WPA 1 in this bit write-protects the bank.0
27BMA 1 in this bit identifies a burst-ROM bank.0
29:28MWThis field controls the width of the data bus for this bank:
31:30ATAlways write 00 to this field.00
address description
that the EMC maintains between read and write accesses in this
bank, and between an access in another bank and an access in
this bank, to avoid bus contention between devices. The number
of idle CCLK cycles between such accesses is the value in this
field plus 1.
The value read from a reserved bit is not defined.
subsequent reads from a burst ROM). The length of read
accesses, in CCLK cycles, is this field value plus 3.
non-byte-partitioned devices, so that the EMC drives the BLS3:0
lines High during read accesses. This bit should be 1 for banks
composed of 16-bit and 32-bit wide devices that include byte
select inputs, so that the EMC drives the BLS3:0 lines Low
during read accesses.
which consist of:
One CCLK cycle of address setup with CS, BLS, and WE high
This value plus 1, CCLK cycles with address valid and CS, BLS,
and WE low
AND
One CCLK cycle with address valid, CS low, BLS and WE high.
For burst ROM banks, this field controls the length of subsequent
accesses, which are (this value plus 1) CCLK cycles long.
The value read from a reserved bit is not defined.
an AMBA request for more than 32 bits of data. The
ARM7TDMI-S will not make such a request.
WP bit 1. Write a 1 to this bit to clear it.
00=8 bit, 01=16 bit, 10=32 bit, 11=reserved
UM10114
Chapter 3: LPC2210/20 EMC
value
1111
NA
11111
0
11111
NA
0
0
See
Table 3–
9
The table below shows the state of BCFG0[29:28] after the Boot Loader has run. The
hardware reset state of these bits is 10.
The External Memory Controller (EMC) generates byte lane control signals BLS[3:0]
according to:
• External memory bank data bus wid th , de fined within each configuration register (see
• External memory bank type, being either byte (8 bits), halfword (16 bits) or word (32
UM10114
Chapter 3: LPC2210/20 EMC
MW field in BCFG register)
bits) (see RBLE field in BCFG register)
Each memory bank can either be 8, 16 or 32 bits wide. The type of memory used to
configure a particular memory bank determines how the WE and BLS signals are
connected to provide byte, halfword and word access. For read accesses, it is necessary
to control the BLS signals by driving them either all HIGH, or all LOW.
This control is achieved by programming the Read Byte Lane Enable (RBLE) bit within
each configuration register. The following two sections explain why different connections
in respect of WE and BLS[3:0] are needed for different memory configurations.
4.3Accesses to memory banks constructed from 8-bit or non
byte-partitioned memory devices
For memory banks constructed from 8-bit or non byte-partitioned memory devices, it is
important that the RBLE bit is cleared to zero within the respective memory bank
configuration register. This forces all BLS[3:0] lines HIGH during a read access to that
particular bank.
Figure 3–6
memory banks that are 8, 16 and 32 bits wide. In each of these configurations, the
BLS[3:0] signals are connected to write enable (WE) inputs of each 8-bit memory.
Note: The WE signal from the EMC is not used. For write transfers, the relevant BLS[3:0]
byte lane signals are asserted LOW and steer the data to the addressed bytes.
For read transfers, all of the BLS[3:0] lines are deasserted HIGH, which allows the
external bus to be defined for at least the width of the accessed memory.
(a), Figure 3–7 (a) and Figure 3–8 show 8-bit memory being used to configure
4.4Accesses to memory banks constructed from 16 or 32 bit memory
devices
For memory banks constructed from 16 bit or 32-bit memory devices, it is important that
the RBLE bit is set to one within the respective memory bank configuraton register. This
asserts all BLS[3:0] lines LOW during a read access to that particular bank. For 16 and
32-bit wide memory devices, byte select signals exist and must be appropriately
controlled as shown in Figure 3–6
5.External memory interface
External memory interfacing depends on the bank width (32, 16 or 8 bit selected via MW
bits in corresponding BCFG register). Furthermore, the memory chip(s) require an
adequate setup of RBLE bit in BCFG register. Memory accessed with an 8-bit wide data
bus require RBLE = 0, while memory banks capable of accepting 16 or 32 bit wide data
require RBLE = 1.
If a memory bank is configured to be 32 bits wide, address lines A0 and A1 can be used
as non-address lines. If a memory bank is configured to 16 bits wide, A0 is not required.
However, 8 bit wide memory banks do require all address lines down to A0. Configuring
A1 and/or A0 line(s) to provide address or non-address function is accomplished using
bits 23 and 24 in Pin Function Select Register 2 (PINSEL2 register, see Section 7–4.3
Symbol "a_b" in the following figures refers to the highest order address line in the data
bus. Symbol "a_m" refers to the highest order address line of the me mory chip used in the
external memory interface.
a. 32 bit wide memory bank interfaced to 8 bit memory chips (RBLE = 0)
UM10114
Chapter 3: LPC2210/20 EMC
b. 32 bit wide memory bank interfaced to 16 bit memory chips (RBLE = 1)
c. 32 bit wide memory bank interfaced to 8 bit memort chips (RBLE = 1)
Fig 6. 32 bit bank external memory interfaces (BGFGx Bits MW = 10)
a. 16 bit wide memory bank interfaced to 8 bit memory chips (RBLE = 0)
UM10114
Chapter 3: LPC2210/20 EMC
b. 16 bit wide memory bank interfaced to 16 bit memory chips (RBLE = 1)
Fig 7. 16 bit bank external memory interfaces (BCFGx bits MW = 01)
Fig 8. 8 bit bank external memory interface (BCFGx bits MW = 00 and RBLE = 0)
6.Typical bus sequences
The following figures show typical external read and write access cycles. XCLK is the
clock signal available on P3.23. While not necessarily used by external memory, in these
examples it is used to provide time reference (XCLK and CCLK are set to have the same
Fig 10. E xternal memory write access (WST2 = 0 and WST2 = 1 examples)
Figure 3–9 and Figure 3–10 show typical read and write accesses to external memory.
Dashed lines on Figure 3–9
having BLS lines connected to UB/LB or B[3:0] (see Section 3–4.4
Figure 3–7
correspond to memory banks using 16/32 bit memory chips
and Figure 3–6 ,
).
NXP Semiconductors
Address AAd.A+1Ad.A+2Address A+3
D(A)D(A+1)D(A+2)Data(A+3)
2 wait states
XCLK
addr
data
CS
OE
0 wait states
f
MAX
2WST1+
t
RAM
20ns+
------------------------------
≤
WST1
t
RAM
20ns+
t
CYC
------------------------------
≥2–
t
RAMtCYC
2WST1+()×20ns–≤
It is important to notice that some variations from Figure 3–9 and Figure 3–10 do exist in
some particular cases.
For example, when the first read access to the memory bank that has just been selected
is performed, CS and OE lines may become low one XCLK cycle earl ier than it is shown in
Figure 3–10
Likewise, in a sequence of several consecutive write accesses to SRAM, the last write
access will look like those shown in Figure 3–10
in that case will have data valid one cycle longer. Also, isolated write access will be
identical to the one in Figure 3–10
The EMC supports sequential access burst reads of up to four consecutive lo ca tions in 8 ,
16 or 32-bit memories. This feature supports burst mode ROM devices and increases the
bandwidth by using reduced (configurable) ac cess time for three sequential reads
following a quad-location boundary read. Figure 3–11
read transfer. The first burst read access has two wait states and subsequent accesses
have zero wait states.
Based on the description of the EMC operation and external memory in general
(appropriate read and write access times t
can be constructed and used for extern a l mem o ry se lect ion . t
CCLK cycle (see Figure 3–9
cycle). f
is the maximum CCLK frequency achievable in the system with selected
max
and Figure 3–10 where one XCLK cycle equals one CCLK
The System Control Block includes several system features and control registers for a
number of functions that are not related to specific peripheral devices. These include:
• Crystal Oscillator
• External Interrupt Inputs
• Miscellaneous System Controls and Status
• Memory Mapping Control
• PLL
• Power Control
• Reset
• APB Divider
• Wakeup Timer
Each type of function has its own register(s) if any are required and unneeded bits are
defined as reserved in order to allow future expansion. Unrelated functions never share
the same register addresses
2.Pin description
Table 4–11 shows pins that are associated with System Control block functions.
Table 11.Pin summary
Pin namePin
XTAL1InputCrystal Oscillator Input - Input to the oscillator and internal clock
XTAL2OutputCrystal Oscillator Output - Output from the oscillator amplifier
EINT0InputExternal Interrupt Input 0 - An active low/high level or
EINT1InputExternal Interrupt Input 1 - See the EINT0 description above.
Pin description
direction
generator circuits
falling/rising edge general purpose interrupt input. This pin may be
used to wake up the processor from Idle or Power-down modes.
Pins P0.1 and P0.16 can be selected to perform EINT0 function.
Pins P0.3 and P0.14 can be selected to perform EINT1 function.
Important: LOW level on pin P0.14 immediately after reset is
considered as an external hardware request to start the ISP
command handler. More details on ISP and Serial Boot Loader can
be found in "On-chip Serial Bootloader" chapter on page 242.
While an input signal of 50-50 duty cycle within a frequency range from 1 MHz to 50 MHz
can be used by the LPC2210/2220 and LPC2210/01 if supplied to its input XTAL1 pin, this
microcontroller’s onboard oscillator circuit supports external crystals in the range of 1 MHz
to 30 MHz only. If the on-chip PLL system or the boot-loader is used, the input clock
frequency is limited to an exclusive range of 10 MHz to 25 MHz.
UM10114
Chapter 4: LPC2210/20 System control
The oscillator output frequency is called F
referred to as CCLK for purposes of rate equations, etc. elsewhere in this document. F
and the ARM processor clock frequency is
OSC
OSC
and CCLK are the same value unless the PLL is running and connected. Refer to the
Section 4–8 “
Phase Locked Loop (PLL)” on page 35 for details and frequency limitations.
The onboard oscillator in the LPC2210/2220 and LPC2210/01 can operate in one of two
modes: slave mode and oscillation mode.
In slave mode the input clock signal should be coupled by means of a capacitor of 100 pF
(C
in Figure 4–12, drawing a), with an amplitude of at least 200 mVrms. The X2 pin in
C
this configuration can be left not connected. If slave mode is selected, the F
signal of
OSC
50-50 duty cycle can range from 1 MHz to 50 MHz.
External components and models used in oscillation mode are shown in Figure 4–12
drawings b and c, and in Table 4–13
only a crystal and the capacitances C
. Since the feedback resistance is integrated on chip,
and CX2 need to be connected externally in case
X1
of fundamental mode oscillation (the fundamental frequency is represented by L, C
R
). Capacitance CP in Figure 4–12, drawing c, repr e sen ts the parallel package
S
capacitance and should not be larger than 7 pF. Parameters F
, CL, RS and CP are
C
,
and
L
supplied by the crystal manufacturer.
Choosing an oscillation mode as an on-board oscillator mode of operation limits F
OSC
clock selection to 1 MHz to 30 MHz.
Fig 12. Oscillator modes and models: a) slave mode of operation, b) oscillation mode of operation, c) external
The LPC2210/2220 and LPC2210/01 include four External Interrupt Inputs as select able
pin functions. The External Interrupt Inputs can optionally be used to wake up the
processor from Power-down mode.
5.1Register description
The external interrupt function has four registers associated with it. The EXTINT register
contains the interrupt flags, and the EXTWAKE register cont ains bits that enable individual
external interrupts to wake up the microcontroller from Power-down mode. The
EXTMODE and EXTPOLAR registers specify the level and edge sensitivity parameters.
Table 14.External interrupt registers
NameDescriptionAccess Reset
EXTINTThe External Interrupt Flag Register contains
interrupt flags for EINT0, EINT1, EINT2 and
EINT3. See Table 4–15
EXTWAKEThe External Interrupt Wakeup Register
contains four enable bits that control whether
each external interrupt will cause the processor
to wake up from Power-down mode. See
which level or edge on each pin will cause an
interrupt.
UM10114
Chapter 4: LPC2210/20 System control
Address
[1]
value
R/W00xE01F C140
.
R/W00xE01F C144
.
R/W00xE01F C148
R/W00xE01F C14C
[1] Reset value reflects the data stored in used bits only. It does not include reserved bits content.
5.2External Interrupt Flag register (EXTINT - 0xE01F C140)
When a pin is selected for its external interrupt function, the level or edge on that pin
(selected by its bits in the EXTPOLAR a nd EXTMODE registers) will set its interrupt fla g in
this register. This asserts the corresponding interrupt request to the VIC, which will cause
an interrupt if interrupts from the pin are enabled.
Writing ones to bits EINT0 through EINT3 in EXTINT register clears the corre sp onding
bits. In level-sensitive mode this action is efficacious only when the pin is in its inactive
state.
Once a bit from EINT0 to EINT3 is set and an appropriate code star ts to execute (hand ling
wakeup and/or external interrupt), this bit in EXTINT register must be cleared. Otherwise
the event that was just triggered by activity on the EINT pin will not be recognized in the
future.
Important: whenever a change of externa l interrupt operating mode (i.e. active
level/edge) is performed (including the initialization of an external interrupt), the
corresponding bit in the EXTINT register must be cleared! For details see Section
For example, if a system wakes up from power-down using a low level on external
interrupt 0 pin, its post-wakeup code must reset the EINT0 bit in order to a llow future entry
into the power-down mode. If the EINT0 bit is left set to 1, subsequent attempt(s) to invoke
power-down mode will fail. The same goes for external interrupt handling.
More details on power-down mode will be discussed in the following chapters.
Table 15.External Interrupt Flag register (EXTINT - address 0xE01F C140) bit description
BitSymbolDescriptionReset
0EINT0In level-sensitive mode, this bit is set if the EINT0 function is selected for its pin, and the pin is in
1EINT1In level-sensitive mode, this bit is set if the EINT1 function is selected for its pin, and the pin is in
2EINT2In level-sensitive mode, this bit is set if the EINT2 function is selected for its pin, and the pin is in
3EINT3In level-sensitive mode, this bit is set if the EINT3 function is selected for its pin, and the pin is in
7:4-Reserved, user software should not write ones to reserved bits. The value read from a reserved
value
0
its active state. In edge-sensitive mode, this bit is set if the EINT0 function is selected for its pin,
and the selected edge occurs on the pin.
Up to two pins can be selected to perform the EINT0 function (see P0.1 and P0.16 description in
"Pin Configuration" chapter page 63.)
This bit is cleared by writing a one to it, except in level sensitive mode when the pin is in its
active state (e.g. if EINT0 is selected to be low level sensitive and a low level is present on the
corresponding pin, this bit can not be cleared; this bit can be cleared only when the signal on the
pin becomes high).
0
its active state. In edge-sensitive mode, this bit is set if the EINT1 function is selected for its pin,
and the selected edge occurs on the pin.
Up to two pins can be selected to perform the EINT1 function (see P0.3 and P0.14 description in
"Pin Configuration" chapter on page 63.)
This bit is cleared by writing a one to it, except in level sensitive mode when the pin is in its
active state (e.g. if EINT1 is selected to be low level sensitive and a low level is present on the
corresponding pin, this bit can not be cleared; this bit can be cleared only when the signal on the
pin becomes high).
0
its active state. In edge-sensitive mode, this bit is set if the EINT2 function is selected for its pin,
and the selected edge occurs on the pin.
Up to two pins can be selected to perform the EINT2 function (see P0.7 and P0.15 description in
"Pin Configuration" chapter on page 63.)
This bit is cleared by writing a one to it, except in level sensitive mode when the pin is in its
active state (e.g. if EINT2 is selected to be low level sensitive and a low level is present on the
corresponding pin, this bit can not be cleared; this bit can be cleared only when the signal on the
pin becomes high).
0
its active state. In edge-sensitive mode, this bit is set if the EINT3 function is selected for its pin,
and the selected edge occurs on the pin.
Up to three pins can be selected to perform the EINT3 function (see P0.9, P0.20 and P0.30
description in "Pin Configuration" chapter on page 63.)
This bit is cleared by writing a one to it, except in level sensitive mode when the pin is in its
active state (e.g. if EINT3 is selected to be low level sensitive and a low level is present on the
corresponding pin, this bit can not be cleared; this bit can be cleared only when the signal on the
pin becomes high).
Enable bits in the EXTWAKE register allow the external interrupts and other sources to
wake up the processor if it is in Power-down mode. The related EINTn function must be
mapped to the pin in order for the wakeup process to take place. It is not nece ssary for the
interrupt to be enabled in the Vectored Interrupt Controller for a wakeup to take place.
This arrangement allows additional capabilities, such as having an external interrupt input
wake up the processor from Power-down mode without causing an interrupt (simply
resuming operation), or allowing an interrupt to be enabled during Power-down without
waking the processor up if it is asserted (eliminating the need to disable the interrupt if the
wakeup feature is not desirable in the application).
For an external interrupt pin to be a source that would wake up the microco ntroller from
Power-down mode, it is also necessary to clear the corresponding bit in the External
Interrupt Flag register (Section 4–5.2 on page 29
The bits in this register select whether each EI NT pin is le vel- or edge- sensitive. Only pins
that are selected for the EINT function (see chapter Pin Connect Block on page 75) and
enabled via the VICIntEnable register (Section 5–4.4 “
(VICIntEnable - 0xFFFF F010)” on page 53) can cause interrupts from the External
Interrupt function (though of course pins selected for other functions may cause i nterrupt s
from those functions).
Note: Software should only change a bit in this register when its interrupt is
disabled in the VICIntEnable register, and should write the corresponding 1 to the
EXTINT register before enabling (initializing) or re-enabling the interrupt, to clear
the EXTINT bit that could be set by changing the mode.
In level-sensitive mode, the bits in this register select whether the corresponding pin is
high- or low-active. In edge-sensitive mode, they select whether the pin is rising- or
falling-edge sensitive. Only pins that are selected for the EINT function (see "Pin Connect
Block" chapter on page 76) and enabled in the VICIntEnable register (Section 5–4.4
“Interrupt Enable Register (VICIntEnable - 0xFFFF F010)” on page 53) can cause
interrupts from the External Interrupt function (though of course pins selected for other
functions may cause interrupts from those functions).
UM10114
Chapter 4: LPC2210/20 System control
description
value
1EINT2 is edge sensitive.
1EINT3 is edge sensitive.
NA
bits. The value read from a reserved bit is not defined.
Note: Software should only change a bit in this register when its interrupt is
disabled in the VICIntEnable register, and should write the corresponding 1 to the
EXTINT register before enabling (initializing) or re-enabling the interrupt, to clear
the EXTINT bit that could be set by changing the polarity.
Software can select multiple pins for each of EINT3:0 in the Pin Select registers, which
are described in chapter Pin Connect Block on page 75. The external interrupt logic for
each of EINT3:0 receives the state of all of its associated pins from the pins’ receivers,
along with signals that indicate whether each pin is selected for the EINT function. The
external interrupt logic handles the case when m ore than one pin is so selected, dif ferently
according to the state of its Mode and Polarity bits:
• In Low-Active Level Sensitive mode, the states of all pins selected for the same EINTx
• In High-Active Level Sensitive mode, the states of all pins selected for the same
• In Edge Sensitive mode, regardless of polarity, the pin with the lowest GPIO port
The signal derived by this logic processing multiple external interrupt pins is the EINTi
signal in the following logic schematic Figure 4–14
UM10114
Chapter 4: LPC2210/20 System control
functionality are digitally combined using a positive logic AND gate.
EINTx functionality are digitally combined using a positive logic OR gate.
number is used. (Selecting multiple pins for an EINTx in edge-sensitive mode could
be considered a programming error.)
.
For example, if the EINT3 function is selected in the PINSEL0 and PINSEL1 registers for
pins P0.9, P0.20 and P0.30, and EINT3 is configured to be low level sensitive, the inputs
from all three pins will be logically ANDed. When more than one EINT pin is logically
ORed, the interrupt service routine can read the states of the pins from the GPIO port
using the IO0PIN and IO1PIN registers, to determine which pin(s) caused the interrupt.
Some aspects of controlling LPC2210/2220 and LPC2210/01 operat ion that do not fit into
peripheral or other registers are grouped here.
6.1System Control and Status flags register (SCS - 0xE01F C1A0)
Remark: This feature is available in LPC2210/01 and LPC2220 only.
Table 19. System Control and Status flags register (SCS - address 0xE01F C1A0) bit description
BitSymbolValueDescriptionReset
0GPIO0MGPIO port 0 mode selection.0
1GPIO1MGPIO port 1 mode selection.0
31:2-Reserved, user software should not write ones to reserved bits. The value read from
value
0GPIO port 0 is accessed via APB addresses in a fashion compatible with previous
LCP2000 devices.
1High speed GPIO is enabled on GPIO port 0, accessed via addresses in the on-chip
memory range. This mode includes the port masking feature described in the GPIO
chapter on page page 83.
0GPIO port 1 is accessed via APB addresses in a fashion compatible with previous
LCP2000 devices.
1High speed GPIO is enabled on GPIO port 1, accessed via addresses in the on-chip
memory range. This mode includes the port masking feature described in the GPIO
chapter on page page 83.
NA
a reserved bit is not defined.
7.Memory mapping control
The Memory Mapping Control alters the mapping of the interrupt vectors that appear
beginning at address 0x0000 0000. This allows code running in different memory spaces
to have control of the interrupts.
7.1Memory Mapping control register (MEMMAP - 0xE01F C040)
Whenever an exception handling is necessary , the microcontroller will fetch an instruction
residing on the exception corresponding address as described in Table 2–3 “
Exception Ve ctor Locations ” on page 11. The MEMMAP register determines the source of
Table 20.Memory Mapping control register (MEMMAP - address 0xE01F C040) bit
BitSymbol ValueDescriptionReset
1:0MAP00Boot Loader Mode. Interrupt vectors are re-mapped to Boot
7:2--Reserved, user software should not write ones to reserved
[1] The hardware reset value of the MAP1:0 bits is 00 for LPC2210/2220 and LPC2210/01 parts. The apparent
UM10114
Chapter 4: LPC2210/20 System control
description
value
[1]
00
Block.
01Reserved. Do not use this option.
10User RAM Mode. Interrupt vectors are re-mapped to Static
RAM.
1 1User External memory Mode. Interrupt vectors are re-mapped
to external memory.
Warning: Improper setting of this value may result in incorrect
operation of the device.
NA
bits. The value read from a reserved bit is not defined.
reset value that the user will see will be altered by the Boot Loader code, which always runs initially at reset.
7.2Memory mapping control usage notes
The Memory Mapping Control simply selects one out of three available sources of data
(sets of 64 bytes each) necessary fo r handling ARM exceptions (interrupts).
For example, whenever a Software Interrupt request is generated, the ARM core will
always fetch 32-bit data "residing" on 0x0000 0008 see Table 2–3 “
Locations” on page 11. This means that when MEMMAP[1:0]=10 (User RAM Mode), a
read/fetch from 0x0000 0008 will provide data stored in 0x4000 0008. In case of
MEMMAP[1:0]=00 (Boot Loader Mode), a read/fetch from 0x0000 0008 will provide data
available also at 0x7FFF E008 (Boot Block remapped from on-chip Bootloader).
MEMMAP[1:1]=11 (User External Memory Mode) will result in fetching data from off-chip
memory at location 0x8000 0008.
8.Phase Locked Loop (PLL)
The PLL accepts an input clock frequency in the range of 10 MHz to 25 MHz only. The
input frequency is multiplied up the range of 10 MHz to 60 MHz (LPC2210) or 75 MHz
(LPC2210/01 and LPC2220) for the CCLK clock using a Current Controlled Oscillators
(CCO). The multiplier can be an integer value from 1 to 32 (in practice, the multiplier value
cannot be higher than 7 due to the upper frequency limit of the CPU). The CCO operates
in the range of 156 MHz to 320 MHz, so there is an additional divider in the loop to keep
the CCO within its frequency range while the PLL is providing the desired output
frequency. The output divider may be set to divide by 2, 4, 8, or 16 to produce the output
clock. Since the minimum output divider value is 2, it is insured that the PLL output has a
50% duty cycle. A block diagram of the PLL is shown in Figure 4–15
ARM Exception Vector
.
PLL activation is controlled via the PLLCON register. The PLL multiplier and divider
values are controlled by the PLLCFG register. These two registers are protected in order
to prevent accidental alteration of PLL parameters or deactivation of the PLL. Since all
chip operations, including the Watchdog Timer, are dependent on the PLL when it is
providing the chip clock, accidental changes to the PLL setup could result in unexpected
behavior of the microcontroller. The protection is accomplished by a feed sequence
similar to that of the Watchdog Timer. Details are provided in the description of the
PLLFEED register.
The PLL is turned off and bypassed following a chip Reset and when by en tering
Power-down mode. The PLL is enabled by software only. The program must configure
and activate the PLL, wait for the PLL to Lock, then connect to the PLL as a clock source.
8.1Register description
The PLL is controlled by the registers shown in Table 4–21. More detailed descriptions
follow.
Warning: Improper setting of the PLL values may result in incorre ct operation of the
device!
Table 21. PLL registers
NameDescriptionAccess Reset
PLLCONPLL Control Register. Holding register for updating PLL control bits.
Values written to this register do not take effect until a valid PLL feed
sequence has taken place.
PLLCFGPLL Configuration Register. Holding register for updating PLL
configuration values. Values written to this register do not take effect
until a valid PLL feed sequence has taken place.
PLLSTATPLL Status Register. Read-back register for PLL control and
configuration information. If PLLCON or PLLCFG have been written
to, but a PLL feed sequence has not yet occurred, they will not
reflect the current PLL state. Reading this register provides the
actual values controlling the PLL, as well as the status of the PLL.
PLLFEEDPLL Feed Register. This register enables loading of the PLL control
and configuration information from the PLLCON and PLLCFG
registers into the shadow registers that actually affect PLL operation.
value
R/W00xE01F C080
R/W00xE01F C084
RO00xE01F C088
WONA0xE01F C08C
UM10114
Address
[1]
[1] Reset value reflects the data stored in used bits only. It does not include reserved bits content.
The PLLCON register contains the bits that enable and connect the PLL. Enabling the
PLL allows it to attempt to lock to the current settings of the multiplier and divider values.
Connecting the PLL causes the processor and all chip functions to run from the PLL
output clock. Changes to the PLLCON register do not take effect until a correct PLL feed
sequence has been given (see Section 4–8.7 “
PLL Feed register (PLLFEED 0xE01F C08C)” and Section 4–8.3 “PLL Configuration register (PLLCFG - 0xE01F C084)”
on page 38).
Table 22.PLL Control register (PLLCON - address 0xE01F C080) bit description
BitSymbolDescriptionReset
0PLLEPLL Enable. When one, and after a valid PLL feed, this bit will
1PLLCPLL Connect. When PLLC and PLLE are both set to one, and after a
7:2-Reserved, user software should not write ones to reserved bits. The
The PLL must be set up, enabled, and Lock established before it may be used as a clock
source. When switching from the oscillator clock to the PLL output or vice versa, internal
circuitry synchronizes the operation in order to ensure that glitches are not generate d.
Hardware does not insure that the PLL is locked before it is connected or automatically
disconnect the PLL if lock is lost during operation. In the event of loss of PLL lock, it is
likely that the oscillator clock has become unstable and disconnecting the PLL will not
remedy the situation.
UM10114
Chapter 4: LPC2210/20 System control
activate the PLL and allow it to lock to the requested frequency. See
PLLSTAT register, Table 4–24
valid PLL feed, connects the PLL as the clock source for the
microcontroller. Otherwise, the oscillator clock is used directly by the
microcontroller. See PLLSTAT register, Table 4–24
The PLLCFG register contains the PLL multiplier and divider values. Changes to the
PLLCFG register do not take ef fect until a correct PLL fee d sequence has been give n (see
for the PLL frequency, and multiplier and divider values are found in the PLL Frequency
Calculation section on page 40.
Table 23.PLL Configuration register (PLLCF G - add ress 0xE01F C084) bit descriptio n
BitSymbolDescriptionReset
4:0MSELPLL Multiplier value. Supplies the value "M" in the PLL frequency
calculations.
Note: For details on selecting the right value for MSEL see Section
4–8.9 “PLL frequency calculation” on page 40.
6:5PSELPLL Divider value. Supplies the value "P" in the PLL frequency
calculations.
Note: For details on selecting the right value for PSEL see Section
4–8.9 “PLL frequency calculation” on page 40.
7-Reserved, user software should not write ones to reserved bits. The
value read from a reserved bit is not defined.
8.4PLL Status register (PLLSTAT - 0xE01F C088)
value
0
0
NA
The read-only PLLSTAT register provides the actual PLL parameters that are in effect at
the time it is read, as well as the PLL status. PLLSTAT may disa gree with values found in
PLLCON and PLLCFG because changes to those registers do not take effect until a
proper PLL feed has occurred (see Section 4–8.7 “
T able 24. PLL Status register (PLLSTAT - address 0xE01F C088) bit description
BitSymbolDescriptionReset
4:0MSELRead-back for the PLL Multiplier value. This is the value currently
6:5PSELRead-back for the PLL Divider value. This is the value currently
7-Reserved, user software should not write ones to reserved bits. The
8PLL ERead-back for the PLL Enable bit. When one, the PLL is currently
9PLLCRead-back for the PLL Connect bit. When PLLC and PLLE are both
10PLOCKReflects the PLL Lock status. When zero, the PLL is not locked.
15:11-Reserved, user software should not write ones to reserved bits. The
UM10114
Chapter 4: LPC2210/20 System control
value
0
used by the PLL.
0
used by the PLL.
NA
value read from a reserved bit is not defined.
0
activated. When zero, the PLL is turned off. This bit is automatically
cleared when Power-down mode is activated.
0
one, the PLL is connected as the clock source for the
microcontroller. When either PLLC or PLLE is zero, the PLL is
bypassed and the oscillator clock is used directly by the
microcontroller. This bit is automatically cleared when Power-down
mode is activated.
0
When one, the PLL is locked onto the requested frequency.
NA
value read from a reserved bit is not defined.
8.5PLL Interrupt
The PLOCK bit in the PLLSTAT register is connected to the interrupt controller. This
allows for software to turn on the PLL and continue with other functions witho ut having to
wait for the PLL to achieve lock. When the interrupt occurs (PLOCK = 1), the PLL may be
connected, and the interrupt disabled. For details on how to enable and disabl e the PLL
interrupt, see Section 5–4.4 “
Interrupt Enable Register (VICIntEnable - 0xFFFF F010)” on
page 53 and Section 5–4.5 “Interrupt Enable Clear Register (VICIntEnClear 0xFFFF F014)” on page 53.
8.6PLL Modes
The combinations of PLLE and PLLC are shown in Table 4–25.
Table 25.PLL Control bit combinations
PLLCPLLEPLL Function
00PLL is turned off and disconnected. The CCLK equals (system runs from) the
unmodified clock input.
01The PLL is active, but not yet connected. The PLL can be connected after
PLOCK is asserted.
10Same as 00 combination. This prevents the possibility of the PLL being
connected without also being enabled.
11The PLL is active and has been connected as the system clock source.
CCLK/system clock equals the PLL output.
8.7PLL Feed register (PLLFEED - 0xE01F C08C)
A correct feed sequence must be written to the PLLFEED register in order for changes to
the PLLCON and PLLCFG registers to take effect. The feed sequence is:
The two writes must be in the correct sequence, and must be consecutive APB bus
cycles. The latter requirement implies that interrupts must be disabled for the duration of
the PLL feed operation. If either of the feed values is incorrect, or one of the previously
mentioned conditions is not met, any changes to the PLLCON or PLLCFG register will not
become effective.
7:0PLLFEED The PLL feed sequence must be written to this register in order for
8.8PLL and Power-down mode
Power-down mode automatically turns off and disconnects activated PLL. Wakeup from
Power-down mode does not automatically restore the PLL settings, this must be done in
software. Ty pically, a routine to activate the PLL, wait for lock, and then connect the PLL
can be called at the beginning of any interrupt service routine that might be called due to
the wakeup. It is important not to attempt to restart the PLL by simply feeding it when
execution resumes after a wakeup from Power-down mode. This would enable and
connect the PLL at the same time, before PLL lock is established.
UM10114
Chapter 4: LPC2210/20 System control
value
0x00
PLL configuration and control register changes to take effect.
8.9PLL frequency calculation
The PLL equations use the following parameters:
T able 27. Elements determining PLL’s frequency
ElementDescription
F
OSC
F
CCO
CCLKthe PLL output frequency (also the processor clock frequency)
MPLL Multiplier value from the MSEL bits in the PLLCFG register
PPLL Divider value from the PSEL bits in the PLLCFG register
The PLL output frequency (when the PLL is both active and connected) is given by:
CCLK = M × F
The CCO frequency can be computed as:
= CCLK × 2 × P or F
F
CCO
The PLL inputs and settings must meet the following:
the frequency from the crystal oscillator/external oscillator
the frequency of the PLL current controlled oscillator
microcontroller - determined by the system microcontroller is embedded in).
• F
is in the range of 156 MHz to 320 MHz.
CCO
8.10Procedure for determining PLL settings
If a particular application uses the PLL, its configuration may be determined as follows:
1. Choose the desired processor operating frequency (CCLK). This may be based on
processor throughput requirements, need to support a specific set of UART baud
rates, etc. Bear in mind that peripheral devices may be running from a lower clock
than the processor (see Section 4–11 “
2. Choose an oscillator frequency (F
multiple of F
OSC
.
3. Calculate the value of M to configure the MSEL bits. M = CCLK / F
the range of 1 to 32. The value written to the MSEL bits in PLLCFG is M − 1 (see
Table 4–29
.
4. Find a value for P to configure the PSEL bits, such that F
frequency limits. F
is calculated using the equation given above. P must have one
CCO
of the values 1, 2, 4, or 8. The value written to the PSEL bits in PLLCFG is 00 for
P = 1; 01 for P = 2; 10 for P = 4; 11 for P = 8 (see Table 4–28
Table 28.PLL Divider values
PSEL Bits (PLLCFG bit s [6:5])Value of P
001
012
104
118
APB divider” on page 45).
). CCLK must be the whole (non-fractional)
OSC
. M must be in
OSC
is within its defined
CCO
).
Table 29.PLL Multiplier values
MSEL Bits (PLLCFG bits [4:0])Value of M
000001
000012
000103
000114
......
1111031
1111132
8.11PLL configuring examples
Example: System design asks for F
Based on these specifications, M = CCLK / Fosc = 60 MHz / 10 MHz = 6. Consequently,
M - 1 = 5 will be written as PLLCFG[4:0].
V alue for P can be d erived from P = F
in range of 156 MHz to 320 MHz. Assuming the lowest allowed frequency for
F
CCO
produces P = 2.67. The only solution for P that satisfies both of these requirements and is
listed in Table 4–28
9.Power control
The LPC2210/2220 and LPC2210/01 support two reduced power modes: Idle mode and
Power-down mode. In Idle mode, execution of instructions is suspended until either a
Reset or interrupt occurs. Peripheral functions continue operation during Idle mode and
may generate interrupts to cause the processor to resume execution. Idle mode
eliminates power used by the processor itself, memory systems and related controllers,
and internal buses.
In Power-down mode, the oscillator is shut down and the chip receives no internal clocks.
The processor state and registers, peripheral registers, and internal SRAM values are
preserved throughout Power-down mode and the logic levels of chip pins remain static.
The Power-down mode can be terminated and normal operation resumed by either a
Reset or certain specific interrupts that are able to function without clocks. Since all
dynamic operation of the chip is suspended, Power-down mode reduces chip power
consumption to nearly zero.
Entry to Power-down and Idle modes must be coordinated with program execution.
Wakeup from Power-down or Idle modes via an interrupt resumes program execution in
such a way that no instructions are lost, incomplete, or repeated. Wake up from
Power-down mode is discussed further in Section 4–12 “
/ (CCLK x 2), using condition that F
CCO
= 156 MHz, P = 156 MHz / (2 x 60 MHz) = 1.3. The highest F
is P = 2. Therefore, PLLCFG[6:5] = 1 will be used.
Wakeup timer” on page 47.
CCO
frequency criteria
CCO
must be
A Power Control for Peripherals feature allows individual peripherals to be turned off if
they are not needed in the application, resulting in additional power savings.
9.1Register description
The Power Control function contains two registers, as shown in Table 4–30. More detailed
descriptions follow.
Table 30.Power control registers
NameDescriptionAccess Reset
PCONPower Control Register. This register contains
control bits that enable the two reduced power
operating modes of the microcontroller. See
Table 4–31
PCONP Power Control for Peripherals Register. This
register contains control bits that enable and
disable individual peripheral functions,
Allowing elimination of power consumption by
peripherals that are not needed.
[1]Reset value reflects the data stored in used bits only. It does not include reserved bits content.
The PCON register contains two bits. Writing a one to the corresponding bit causes entry
to either the Power-down or Idle mode. If both bits are set, Power-down mode is entered.
Table 31.Power Control register (PCON - address 0xE01F COCO) bit description
BitSymbolDescriptionReset
0IDLIdle mode - when 1, this bit causes the processor clock to be stopped,
1PDPower-down mode - when 1, this bit causes the oscillator and all
7:2-Reserved, user software should not write ones to reserved bits. The
9.3Power Control for Peripherals register (PCONP - 0xE01F COC4)
UM10114
Chapter 4: LPC2210/20 System control
value
0
while on-chip peripherals remain active. Any enabled interrupt from a
peripheral or an external interrupt source will cause the processor to
resume execution.
0
on-chip clocks to be stopped. A wakeup condition from an external
interrupt can cause the oscillator to restart, the PD bit to be cleared, and
the processor to resume execution.
NA
value read from a reserved bit is not defined.
The PCONP register allows turning off selected peripheral functions for the purpose of
saving power. This is accomplished by gating off the clock source to the specified
peripheral blocks. A few peripheral functions cannot be turned off (i.e. the Watchdog timer,
GPIO, the Pin Connect block, and the System Control block). Some peripherals,
particularly those that include analog functions, may consume power that is not clock
dependent. These peripherals may contain a separate disable control that turns off
additional circuitry to reduce power. Each bit in PCONP controls one of the peripherals.
The bit numbers correspond to the related peripheral number as shown in the APB
peripheral map Table 2–2 “
APB peripheries and base addresses” in the "Memory
Addressing" chapter.
If a peripheral control bit is 1, that peripheral is enabled. If a periph er al bit is 0, that
peripheral is disabled to conserve power. For example if bit 19 is 1, the I
enabled. If bit 19 is 0, the I
2
C1 interface is disabled.
2
C1 interface is
Important: valid read from a peripheral register and valid write to a peripheral
register is possible only if that peripheral is enabled in the PCONP register!
Table 32.Power Control for Peripherals register (PCONP - address 0xE01F C0C4) bit
description
BitSymbolDescriptionReset
value
0-Reserved, user software should not write ones to reserved bits. The
value read from a reserved bit is not defined.
1PCTIM0Timer/Counter 0 power/clock control bit.1
2PCTIM1Timer/Counter 1 power/clock control bit.1
3PCUART0 UART0 power/clock control bit.1
4PCUART1 UART1 power/clock control bit.1
5PCPWM0 PWM0 power/clock control bit.1
6-Reserved, user software should not write ones to reserved bits. The
Table 32.Power Control for Peripherals register (PCONP - address 0xE01F C0C4) bit
BitSymbolDescriptionReset
7PCI2CThe I2C interface power/clock control bit.1
8PCSPI0The SPI0 interface power/clock control bit.1
9PCRTCThe RTC power/clock control bit.1
10PCSPI1The SPI1 interface power/clock control bit.1
11PCEMCThe External Memory Controller power/clock control bit.1
12PCADA/D Converter (ADC) power/clock control bit.
20:13 -Reserved, user software should not write ones to reserved bits. The
21PCSSPThe SSP power/clock control bit. This bit is available in LPC2210/01
31:22 -Reserved, user software should not write ones to reserved bits. The
UM10114
Chapter 4: LPC2210/20 System control
description
value
1
Note: Clear the PDN bit in the ADCR before clearing this bit, and set
this bit before setting PDN.
NA
value read from a reserved bit is not defined.
0
and LPC2220 only.
Note: bits PCSPI1 and PCSSP can not be 1 at the same time. Built-in
hardware mechanism makes sure that at least one of them is 0. In
case attempt is made to have both of these bits set to 1, this will result
in PCSPI1 being 1 and PCSSP becoming 0.
NA
value read from a reserved bit is not defined.
10. Reset
9.4Power control usage notes
After every reset, the PCONP register contains the value that en ables all interfaces and
peripherals controlled by the PCONP to be enabled. Therefore, apart from proper
configuring via peripheral dedicated registers, the user’s application has no need to
access the PCONP in order to start using any of the on-board peripherals.
Power saving oriented systems should have 1s in the PCONP register only in positions
that match peripherals really used in the application. All other bits, declared to be
"Reserved" or dedicated to the peripherals not used in the current application, must be
cleared to 0.
Reset has two sources on the LPC2210/2220 and LPC2210/01: the RESET pin and
Watchdog Reset. The RESET
filter. Assertion of chip Reset by any sour ce starts the Wakeup Timer (see description in
Section 4–12 “
Wakeup timer” in this chapter), causing reset to remain asserted until the
external Reset is de-asserted, the oscillator is running, a fixed number of clocks have
passed, and the on-chip circuitry has completed its initialization. The relationship between
Reset, the oscillator, and the Wakeup Timer are shown in Figure 4–16
The Reset glitch filter allows the processor to ignore exte rn al re se t puls es that are very
short, and also determines the minimum duration of RESET
order to guarantee a chip reset. Once asserted, RESET
crystal oscillator is fully running and an adequate signal is present on the X1 pin of the
microcontroller. Assuming that an external crystal is used in the crystal oscillator
pin is a Schmitt trigger input pin with an additional glitch
subsystem, after power on, the RESET pin should be asserted for 10 ms. For all
subsequent resets when crystal oscillator is already running and stable signal is on the X1
pin, the RESET
When the internal Reset is removed, the processor begins executing at address 0, which
is initially the Reset vector mapped from the Boot Block. At that point, all of the processor
and peripheral registers have been initialized to predetermined values.
External and internal Resets have some small differences. An external Reset causes the
value of certain pins to be latched to configure the part. External circuitry cannot
determine when an internal Reset occurs in order to allow setting up those special pins,
so those latches are not reloaded during an internal Reset. Pins that are examined during
an external Reset for various purposes are: P1.20/TRACESYNC, P1.26/RTCK (see
chapters "Pin Configuration" on page 63 and "Pin Connect Block" on page 75). Pin P0.14
(see "On-chip Serial Bootloader" chapter on p age 242) is examined by on-chip bootloader
when this code is executed after every Reset.
UM10114
Chapter 4: LPC2210/20 System control
pin needs to be asserted for 300 ns only.
Fig 16. Reset block diagram including the wakeup timer
11. APB divider
The APB Divider determines the relationship between the processor clock (CCLK) and the
clock used by peripheral devices (PCLK). The APB Divider serves two purposes.
The first is to provides peripherals with desired PCLK via APB bus so that they can
operate at the speed chosen for the ARM processor. In order to achieve this, the APB bus
may be slowed down to one half or one fourth of the processor clock rate. Because the
APB bus must work properly at power up (and its timing cannot be altered if it does not
work since the APB divider control registers reside on the APB bus), the default condition
at reset is for the APB bus to run at one quarter speed.
The second purpose of the APB Divider is to allow power savings when an application
does not require any peripherals to run at the full processor rate.
The connection of the APB Divider relative to the oscillator and the processor clock is
shown in Figure 4–17
remains active (if it was running) during Idle mode.
1 1.1 Register description
Only one register is used to control the APB Divider.
Table 33.APB divider register map
NameDescriptionAccess Reset
APBDIVControls the rate of the APB clock in relation to
. Because the APB Divider is connected to the PLL output, the PLL
the processor clock.
UM10114
Chapter 4: LPC2210/20 System control
Address
[1]
value
R/W0x000xE01F C100
[1] Reset value reflects the data stored in used bits only. It does not include reserved bits content.
11.2APBDIV register (APBDIV - 0xE01F C100)
The APB Divider register contains two bits, allowing three divide r values, as shown in
Table 4–34
T able 34. APB Divider register (APBDIV - address 0xE01F C100) bit description
BitSymbol ValueDescriptionReset
1:0APBDIV 00APB bus clock is one fourth of the processor clock.00
7:2--Reserved, user software should not write ones to reserved
.
01APB bus clock is the same as the processor clock.
10APB bus clock is one half of the processor clock.
11Reserved. If this value is written to the APBDIV register, it
has no effect (the previous setting is retained).
bits. The value read from a reserved bit is not defined.
The purpose of the wakeup timer is to ensure that the oscillator and other analog
functions required for chip operation are fully functional before the processor is allowed to
execute instructions. This is important at power on, all types of Rese t, an d when e ve r any
of the aforementioned functions are turned off for any reason. Since the oscillator and
other functions are turned off during Power-down mode, any wakeup of the processor
from Power-down mode makes use of the Wakeup Timer.
The Wakeup T i mer monitors the crystal oscillator as the means of checking whether it is
safe to begin code execution. When power is applied to the chip, or some event caused
the chip to exit Power-down mode, some time is required for the oscillator to produce a
signal of sufficient amplitude to drive the clock logic. The amount of time depends on
many factors, including the rate of V
and its electrical characteristics (if a quartz crystal is used), as well as any other external
circuitry (e.g. capacitors), and the characteristics of the oscillator itself under the existing
ambient conditions.
Once a clock is detected, the Wake up T imer counts 4096 clocks, then enables the on-chip
circuitry to initialize. When the onboard modules initialization is complete, the processor is
released to execute instructions if the external Reset has been deasserted. In the case
where an external clock source is used in the system (as opposed to a crystal connected
to the oscillator pins), the possibility that there could be little or no delay for oscillator
start-up must be considered. The Wakeup Timer design then ensures that any other
required chip functions will be operational prior to the beginning of program execution.
UM10114
Chapter 4: LPC2210/20 System control
ramp (in the case of power on), the type of crystal
DD
Any of the various Resets can bring the microcontroller out of power-down mode, as can
the external interrupts EINT3:0. When one of these interrupts is enabled for wakeup and
its selected event occurs, an oscillator wakeup cycle is started. The actual interrupt (if
any) occurs after the wakeup timer expires, and is handled by the Vectored Interrupt
Controller.
However, th e pin multiplexing on the LPC2210/2220 and LPC2210/01 (see chapters "Pin
Configuration" on page 63 and "Pin Connect Block" on page 75) was designed to allow
other peripherals to, in effect, bring the device out of Power-down mode. The following
pin-function pairings allow interrupt s from eve nts relating to UART0 or 1, SPI 0 or 1, or the
EINT2, SSEL1 / EINT3.
To put the device in Power-down mode and allow activity on one or more of these buses
or lines to power it back up, software should reprogram the pin function to External
Interrupt, select the appropriate mode and polarity for the Interrupt, and then select
Power-down mode. Upon wakeup software should restore the pin multiplexing to the
peripheral function.
All of the bus- or line-activity indications in the list above happen to be low-active. If
software wants the device to come out of power -down mode in response to activity on
more than one pin that share the same EINTi channel, it should progr am low-level
sensitivity for that channel, because only in level mode will the channel logically OR the
signals to wake the device.
The only flaw in this scheme is that the time to restart the oscillator prevents the
LPC2210/2220 and LPC2210/01 from capturing the bus or line activity that wakes it up.
Idle mode is more appropriate than power-down mode for devices that must capture and
respond to external activity in a timely manner.
To summarize: on the LPC2210/2220 and LPC2210/01, the Wakeup Timer enforces a
minimum reset duration based on the crystal oscillator, and is activated whenever there is
a wakeup from Power-down mode or any type of Reset.
• 16 priority levels dynamically assigned to interrupt requests
• Software interrupt generation
The Vectored Interrupt Controller (VIC) takes 32 interrupt request inputs and
programmably assigns them into 3 categories, FIQ, vectored IRQ, and non-vectored IRQ.
The programmable assignment scheme means that priorities of interrupts from the
various peripherals can be dynamically assigned and adjusted.
Fast Interrupt reQuest (FIQ) requests have the high est priority. If more than one request is
assigned to FIQ, the VIC ORs the requests to produce the FIQ signal to the ARM
processor. The fastest po ssible FIQ latency is achieved when only one request is
classified as FIQ, because then the FIQ service routine can simply start dealing with that
device. But if more than one request is assigned to the FIQ class, the FIQ service routine
can read a word from the VIC that identifies which FIQ source(s) is (are) requesting an
interrupt.
Vectored IRQs have th e midd le pr iority, but only 16 of the 32 requests can be assigned to
this category . Any of the 32 reque sts can be as signed to any of the 16 vectored IRQ slot s,
among which slot 0 has the highest priority and slot 15 has the lowest.
Non-vectored IRQs have the lowest priority.
The VIC ORs the requests from all the vectored and non-vectored IRQs to produce the
IRQ signal to the ARM processor. The IRQ service routine can start by reading a register
from the VIC and jumping there. If any of the vectored IRQs are requesting, the VIC
provides the address of the highest-priority req ue sting IRQs service routine, otherwise it
provides the address of a default routine that is shared by all the non-vectored IRQs. The
default routine can read another VIC register to see what IRQs are active.
All registers in the VIC are word registers. Byte and halfword reads and write are not
supported.
Additional information on the Vectored Interrupt Controller is available in the ARM
PrimeCell Vectored Interrupt Controller (PL190) documentation.
3.Register description
The VIC implements the registers shown in Table 5–35. More detailed descriptions follow.
VICVectCntl1Vector control 1 register.R/W00xFFFF F204
VICVectCntl2Vector control 2 register.R/W00xFFFF F208
VICVectCntl3Vector control 3 register.R/W00xFFFF F20C
VICVectCntl4Vector control 4 register.R/W00xFFFF F210
VICVectCntl5Vector control 5 register.R/W00xFFFF F214
VICVectCntl6Vector control 6 register.R/W00xFFFF F218
VICVectCntl7Vector control 7 register.R/W00xFFFF F21C
VICVectCntl8Vector control 8 register.R/W00xFFFF F220
VICVectCntl9Vector control 9 register.R/W00xFFFF F224
VICVectCntl10Vector control 10 register.R/W00xFFFF F228
VICVectCntl11Vector control 11 register.R/W00xFFFF F22C
VICVectCntl12Vector control 12 register.R/W00xFFFF F230
VICVectCntl13Vector control 13 register.R/W00xFFFF F234
VICVectCntl14Vector control 14 register.R/W00xFFFF F238
VICVectCntl15Vector control 15 register.R/W00xFFFF F23C
Registers 0-15 each control one of the 16
vectored IRQ slots. Slot 0 has the highest
priority and slot 15 the lowest.
UM10114
Chapter 5: LPC2210/20 VIC
Address
[1]
value
R/W00xFFFF F200
[1] Reset Value refers to the data stored in used bits only. It does not include reserved bits content.
4.VIC registers
The following section describes the VIC registers in the order in which they are used in the
VIC logic, from those closest to the interrupt request inputs to those most abstracted for
use by software. For most people, this is also the best order to read about the registers
when learning the VIC.
00Writing a 0 leaves the corresponding bit in VICSoftInt
Value Description
unchanged.
1Writing a 1 clears the corresponding bit in the Software
Interrupt register, thus releasing the forcing of this request.
4.3Raw Interrupt Status Register (VICRawIntr - 0xFFFF F008)
This is a read only register. This register reads out the state of the 32 interrupt requests
and software interrupts, rega rdless of enabling or classification.
Table 41.Raw Interrupt Status Register (VICRawIntr - address 0xFFFF F008) b it description
VICRawIntr DescriptionReset
value
31:01: the interrupt request or software interrupt with this bit number is
asserted.
0: the interrupt request or software interrupt with this bit number is
This is a read/write accessible register. This register classifies each of the 32 interrupt
requests as contributing to FIQ or IRQ.
T able 44. Interrupt Select Register (VICIntSelect - address 0xFFFF F00C) bit description
VICIntSelectDescriptionReset
31:01: the interrupt request with this bit number is assigned to the FIQ
UM10114
Chapter 5: LPC2210/20 VIC
description
value
0
register, thus disabling interrupts for this request.
0: writing a 0 leaves the corresponding bit in VICIntEnable unchanged.
value
0
category.
0: the interrupt request with this bit number is assigned to the IRQ
category.
4.7IRQ Status Register (VICIRQStatus - 0xFFFF F000)
This is a read only register. This register reads out the state of those interrupt requests
that are enabled and classified as IRQ. It does not differentiate between vectored and
non-vectored IRQs.
Table 45.IRQ Status Register (VICIRQStatus - address 0xFFFF F000) bit description
VICIRQStatus DescriptionReset
31:01: the interrupt request with this bit number is enabled, classified as
IRQ, and asserted.
4.8FIQ Status Register (VICFIQStatus - 0xFFFF F004)
This is a read only register. This register reads out the state of those interrupt requests
that are enabled and classified as FIQ. If more than one request is classified as FIQ, the
FIQ service routine can read this register to see which request(s) is (are) active.
Table 46.FIQ Status Register (VICFIQStatus - address 0xFFFF F004) bit description
VICFIQStatus DescriptionReset
31:01: the interrupt request with this bit number is enabled, classified as
FIQ, and asserted.
value
0
value
0
4.9Vector Control Registers 0-15 (VICvectCntl0-15 - 0xFFFF F200-23C)
These are a read/write accessible registers. Each of these registers controls one of the 16
vectored IRQ slots. Slot 0 has the highest priority and slot 15 the lowest. Note that
disabling a vectored IRQ slot in one of the VICVectCntl registers does not disable the
interrupt itself, the interrupt is simply changed to the non-vectored form.
These are a read/write accessible registers. These registers hold the addresses of the
Interrupt Service routines (ISRs) for the 16 vectored IRQ slots.
T able 48. Vector Address Registers (VICVectAddr0-15 - addresses 0xFFFF F100-13C) bit
VICVectAddr0-15 DescriptionReset
31:0When one or more interrupt request or software interrupt is (are)
description
this vectored IRQ slot. As a matter of good programming practice,
software should not assign the same interrupt number to more than
one enabled vectored IRQ slot. But if this does occur, the lower
numbered slot will be used when the interrupt request or software
interrupt is enabled, classified as IRQ, and asserted.
address when its assigned interrupt request or software interrupt is
enabled, classified as IRQ, and asserted.
value read from a reserved bit is not defined.
description
enabled, classified as IRQ, asserted, and assigned to an enabled
vectored IRQ slot, the valu e from this register for the highest-priority
such slot will be provided when the IRQ service routine reads the
Vector Address register -VICVectAddr (Section 5–4.10
01: the VIC registers can only be accessed in privileged mode.
31:1Reserved, user software should not write ones to reserved bits. The
UM10114
Chapter 5: LPC2210/20 VIC
value
0
to a vectored IRQ slot is (are) enabled, classified as IRQ, and
asserted, reading from this register returns the address in the Vector
Address Register for the highest-priority such slot (lowest-numbered)
such slot. Otherwise it returns the address in the Default Vector
Address Register.
Writing to this register does not set the value for future reads from it.
Rather, this register should be written near the end of an ISR, to
update the priority hardware.
value
0
0: VIC registers can be accessed in User or privileged mode.
NA
value read from a reserved bit is not defined.
5.Interrupt sources
Table 5–52 lists the interrupt sources for each peripheral function. Each perip heral device
has one interrupt line connected to the V ectored In terrupt Controller , but may have several
internal interrupt flags. Individual interrupt flags may also represent more than one
interrupt source.
Table 52.Connection of interrupt sources to the Vectored Interrupt Controller
BlockFlag(s)VIC
WDTWatchdog Interrupt (WDINT)00x0000 0001
-Reserved for software interrupts only10x0000 0002
ARM CoreEmbedded ICE, DbgCommRx20x0000 0004
ARM CoreEmbedded ICE, DbgCommTX30x0000 0008
TIMER0Match 0 - 3 (MR0, MR1, MR2, MR3)
System ControlExternal Interrupt 0 (EINT0)140x0000 4000
ADCA/D Converter end of conversion180x0004 0000
ReservedReserved19-31NA
UM10114
Chapter 5: LPC2210/20 VIC
VIC Channel #
Hex
and Mask
60x0000 0040
Transmit Holding Register Empty (THRE)
Rx Data Available (RDA)
Character Time-out Indicator (CTI)
Auto-Baud Time-Out (ABTO)
End of Auto-Baud (ABEO)
70x0000 0080
Transmit Holding Register Empty (THRE)
Rx Data Available (RDA)
Character Time-out Indicator (CTI)
Modem Status Interrupt (MSI)
Auto-Baud Time-Out (ABTO)
End of Auto-Baud (ABEO)
100x0000 0400
Mode Fault (MODF)
110x0000 0800
SPI Interrupt Flag (SPIF)
Mode Fault (MODF)
Source: SSP (in LPC2210/01 and LPC2220 only)
TX FIFO at least half empty (TXRIS)
Rx FIFO at least half full (RXRIS)
Receive Timeout condition (RTRIS)
Receive overrun (RORRIS)
Fig 18. Block diagram of the Vectored Interrupt Controller (VIC)
6.Spurious interrupts
Spurious interrupts are possible in the ARM7TDMI based microcontrollers such as the
LPC2210/2220 and LPC2210/01 due to asynchronous interrupt handling. The
asynchronous character of the interrupt processing has its roots in the interaction of the
core and the VIC. If the VIC state is changed between the moment s when the core detect s
an interrupt, and the core actually processes an interrupt, problems may be gene rated.
Real-life applications may experience the following scenarios:
1. VIC decides there is an IRQ interrupt and sends the IRQ signal to the core.
2. Core latches the IRQ state.
3. Processing continues for a few cycles due to pipelining.
Furthermore, It is possible that the VIC state has changed during step 3. For example,
VIC was modified so that the interrupt that triggered the sequence starting with step 1) is
no longer pending -interrupt got disabled in the executed code. In this case, the VIC will
not be able to clearly identify the interrupt that generated the interrupt request, and as a
result the VIC will return the default interrupt VicDefVectAddr (0xFFFF F034).
This potentially disastrous chain of events can be prevented in two ways:
1. Application code should be set up in a way to prevent the spurious interrupts from
2. VIC default handler should be set up and tested properly.
6.1Details and case studies on spurious interrupts
This chapter contains details that can be obtained from the official ARM website (FAQ
section under the "Technical Support" link):
What happens if an interrupt occurs as it is being disabled?
UM10114
Chapter 5: LPC2210/20 VIC
occurring. Simple guarding of changes to the VIC may not be enough since, for
example, glitches on level sensitive interrupts can also cause spurious interrupts.
Applies to: ARM7TDMI
If an interrupt is received by the core during execution of an instruction that disables
interrupts, the ARM7 family will still take the interrupt. This occurs for both IRQ and FIQ
interrupts.
For example, consider the following instruction sequence:
If an IRQ interrupt is received during execut ion of the MSR instruction, then the behavior
will be as follows:
• The IRQ interrupt is latched.
• The MSR cpsr, r0 executes to completion setting both the I bit and the F bit in the
CPSR.
• The IRQ interrupt is taken because the core was committed to taking the interrupt
exception before the I bit was set in the CPSR.
• The CPSR (with the I bit and F bit set) is moved to the SPSR_IRQ.
This means that, on entry to the IRQ interrupt service routine, you can see the unusual
effect that an IRQ interrupt has just been taken while the I bit in the SPSR is set. In the
example above, the F bit will also be set in both the CPSR and SPSR. This means that
FIQs are disabled upon entry to the IRQ service routine, and will remain so until explicitly
re-enabled. FIQs will not be reenabled automatically by the IRQ return sequence.
Although the example shows both IRQ and FIQ interrupts be ing disabled, similar behavior
occurs when only one of the two interrupt types is being disabled. The fact that the core
processes the IRQ after completion of the MSR instruction which disables IRQs does not
normally cause a problem, since an interrupt arriving just one cycle earlier would be
expected to be taken. When the interrupt routine returns with an instruction like:
The SPSR_IRQ is restored to the CPSR. The CPSR will now have the I bit and F bit set,
and therefore execution will continue with all interrupts disabled. However, this can cause
problems in the following cases:
Problem 1: A particular routine maybe called as an IRQ handler, or as a regular
subroutine. In the latter case, the system guarantees that IRQs would have been disabled
prior to the routine being called. The routine exploits this restriction to determine how it
was called (by examining the I bit of the SPSR), and returns using the appropriate
instruction. If the routine is entered due to an IRQ being received during execution of the
MSR instruction which disables IRQs, then the I bit in the SPSR will be set. The routine
would therefore assume that it could not have been entered via an IRQ.
Problem 2: FIQs and IRQs are both disabled by the same write to the CPSR. In this case,
if an IRQ is received during the CPSR write, FIQs will be disabled for the execution time of
the IRQ handler. This may not be acceptable in a system where FIQs must not be
disabled for more than a few cycles.
6.2Workaround
UM10114
Chapter 5: LPC2210/20 VIC
There are 3 suggested workarounds. Which of these is most applicable will depend upon
the requirements of the particular system.
6.3Solution 1: Test for an IRQ received during a write to disable IRQs
Add code similar to the following at the start of the interrupt routine.
SUB lr, lr, #4 ; Adjust LR to point to return
STMFD sp!, {..., lr} ; Get some free regs
MRS lr, SPSR ; See if we got an interrupt while
TST lr, #I_Bit ; interrupts were disabled.
LDMNEFD sp!, {..., pc}^ ; If so, just return immediately.
; The interrupt will remain pending since we haven’t
; acknowledged it and will be reissued when interrupts
; are next enabled.
; Rest of interrupt routine
This code will test for the situation where the IRQ was received during a write to disable
IRQs. If this is the case, the code returns immediately - resulting in the IRQ not being
acknowledged (cleared), and further IRQs being disabled.
Similar code may also be applied to the FIQ handler, in order to resolve the first issue.
This is the recommended workaround, as it overcomes both problems mentioned above.
However, in the case of p roblem two, it do es add several cycles to the maximu m length of
time FIQs will be disabled.
6.4Solution 2: Disable IRQs and FIQs using separate writes to the CPSR
This is the best workaround where the maximum time for which FIQs are disabled is
critical (it does not increase this time at all). However, it does not solve problem one, and
requires extra instructions at every point where IRQs and FIQs are disabled together.
6.5Solution 3: Re-enable FIQs at the beginning of the IRQ handler
As the required state of all bits in the c field of the CPSR are known, this can be most
efficiently be achieved by writing an immediate value to CPSR_C, for example:
MSR cpsr_c, #I_Bit:OR:irq_MODE ;IRQ should be disabled
;FIQ enabled
;ARM state, IRQ mode
This requires only the IRQ handler to be modified, and FIQs may be re-enabled more
quickly than by using workaround 1. However, this should only be used if the system can
guarantee that FIQs are never disabled while IRQs are enabled. It does not address
problem one.
UM10114
Chapter 5: LPC2210/20 VIC
7.VIC usage notes
If user code is running from an on-chip RAM and an application uses interrupts, interrupt
vectors must be re-mapped to on-chip address 0x0. This is necessary because all th e
exception vectors are located at addresse s 0x 0 an d ab o ve. Th is is easily achieved by
configuring the MEMMAP register (see Section 4–7.1 “
(MEMMAP - 0xE01F C040)” on page 34) to User RAM mode. Application code should be
linked such that at 0x4000 0000 the Interrupt Vector Table (IVT) will reside.
Although multiple sources can be selected (VICIntSelect) to generate FIQ request, only
one interrupt service routine should be dedicated to service all available/present FIQ
request(s). Therefore, if more than one interrupt sources are classified as FIQ the FIQ
interrupt service routine must read VICFIQStatus to decide based on this content what to
do and how to process the interrupt request. However, it is recommended that only one
interrupt source should be classified as FIQ. Classifying more than one interrupt sources
as FIQ will increase the interrupt latency.
Following the completion of the desired interrupt service routine, clearing of the interrupt
flag on the peripheral level will propagate to corresponding bits in VIC registers
(VICRawIntr, VICFIQStatus and VICIRQStatus). Also, before the next interrupt can be
serviced, it is necessary that write is performed into the VICVectAddr register before the
return from interrupt is executed. This write will clear the respective interrupt flag in the
internal interrupt priority hardware.
Memory Mapping control register
In order to disable the interrupt at the VIC you need to clear corresponding bit in the
VICIntEnClr register, which in turn clears the related bit in the VICIntEnable register. This
also applies to the VICSoftInt and VICSoftIntClear in which VICSoftIntClear will clear the
respective bits in VICSoftInt. For example, if VICSoftInt = 0x0000 0005 and bit 0 has to be
cleared, VICSoftIntClear = 0x0000 0001 will accomplish this. Before the new clear
operation on the same bit in VICSoftInt using writing into VICSoftIntClear is performed in
the future, VICSoftIntClear = 0x0000 0000 must be assigned. Therefore writing 1 to any
bit in Clear register will have one-time-effect in the destination register.
If the watchdog is enabled for interrupt on underflow or invalid feed sequence only then
there is no way of clearing the interrupt. The only way you could perform return from
interrupt is by disabling the interrupt at the VIC (using VICIntEnClr).
Example: Assuming that UART0 and SPI0 are generating interrupt requests that are
classified as vectored IRQs (UART0 being on the higher level than SPI0), while UART1
and I
setup:
VICIntSelect = 0x0000 0000 ; SPI0, I2C, UART1 and UART0 are IRQ =>
; bit10, bit9, bit7 and bit6=0
VICIntEnable = 0x0000 06C0 ; SPI0, I2C, UART1 and UART0 are enabled interrupts =>
; bit10, bit9, bit 7 and bit6=1
VICDefVectAddr = 0x... ; holds address at what routine for servicing
; non-vectored IRQs (i.e. UART1 and I2C) starts
VICVectAddr0 = 0x... ; holds address where UART0 IRQ service routine starts
VICVectAddr1 = 0x... ; holds address where SPI0 IRQ service routine starts
VICVectCntl0 = 0x0000 0026 ; interrupt source with index 6 (UART0) is enabled as
; the one with priority 0 (the highest)
VICVectCntl1 = 0x0000 002A ; interrupt source with index 10 (SPI0) is enabled
; as the one with priority 1
UM10114
Chapter 5: LPC2210/20 VIC
2
C are generating non-vectored IRQs, the following could be one possibility for VIC
After any of IRQ requests (SPI0, I2C, UART0 or UART1) is made, microcontroller will
redirect code execution to the address specified at location 0x0000 0018. For vectored
and non-vectored IRQ’s the following instruction could be placed at 0x0000 0018:
LDR pc, [pc,#-0xFF0]
This instruction loads PC with the address that is present in VICVectAddr register.
In case UART0 request has been made, VICVectAddr will be identical to VICVectAddr0,
while in case SPI0 request has been made value from VICVectAddr1 will be found here. If
neither UART0 nor SPI0 have generated IRQ request but UART1 and/or I
reason, content of VICVectAddr will be identical to VICDefVectAddr.
xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxx x x x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xx xx xxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx x x
xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx
xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxx x x x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xx xx xxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx x x
xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx
Pin description for LPC2210/2220 and LPC2210/01 and a brief explanation of
corresponding functions are shown in the following table.
(LQFP)
[1]
42
[2]
49
[3]
50
[3]
58
[1]
59
[1]
61
[1]
68
[2]
69
[1]
75
Pin
(TFBGA)
L4
K6
L6
M8
L8
N9
N11
M11
L12
Type Description
for each bit. The operation of port 0 pins depends upon the pin function
selected via the Pin Connect Block.
Pins 26 and 31 of port 0 are not available.
[1]
I/OP0.0 — General purpose digital input/output pin.
OTXD0 — Transmitter output for UART0
OPWM1 — Pulse Width Modulator output 1
[2]
I/OP0.1 — General purpose digital input/output pin.
IRxD0 — Receiver input for UART0
OPWM3 — Pulse Width Modulator output 3
IEINT0 — External interrupt 0 input
[3]
I/OP0.2 — General purpose digital input/output pin.
2
I/OSCL — I
C clock input/output. Open drain output (for I2C compliance)
ICAP0.0 — Capture input for Timer 0, chan nel 0
[3]
I/OP0.3 — General purpose digital input/output pin.
2
I/OSDA — I
C data input/output. Open drain output (for I2C compliance)
OMAT0.0 — Match output for Timer 0, channel 0
IEINT1 — External interrupt 1 input
[1]
I/OP0.4 — General purpose digital input/output pin.
I/OSCK0 — Serial clock for SPI0. SPI clock output from master or input to slave
ICAP0.1 — Capture input for Timer 0, chan nel 0
[1]
I/OP0.5 — General purpose digital input/output pin.
I/OMISO0 — Master In Slave OUT for SPI0. Data input to SPI master or data
output from SPI slave
OMAT0.1 — Match output for Timer 0, channel 1
[1]
I/OP0.6 — General purpose digital input/output pin.
I/OMOSI0 — Master Out Slave In for SPI0. Data output from SPI master or data
input to SPI slave
ICAP0.2 — Capture input for Timer 0, chan nel 2
[2]
I/OP0.7 — General purpose digital input/output pin.
ISSEL0 — Slave Select for SPI0. Selects the SPI interface as a slave
OPWM2 — Pulse Width Modulator output 2
IEINT2 — External interrupt 2 input
[1]
I/OP0.8 — General purpose digital input/output pin.
OTXD1 — Transmitter output for UART1
OPWM4 — Pulse Width Modulator output 4
Table 54. Pin description
SymbolPin
P0.0 to P0.31I/OPort 0: Port 0 is a 32-bit bidirectional I/O port with individual direction controls
I/OP0.9 — General purpose digital input/output pin.
IRxD1 — Receiver input for UART1
OPWM6 — Pulse Width Modulator output 6
IEINT3 — External interrupt 3 input
I/OP0.10 — General purpose digital input/output pin.
ORTS1 — Request to Send output for UART1.
ICAP1.0 — Capture input for Timer 1, chan nel 0
I/OP0.11 — General purpose digital input/output pin.
ICTS1 — Clear to Send input for UART1.
ICAP1.1 — Capture input for Timer 1, chan nel 1.
I/OP0.12 — General purpose digital input/output pin.
IDSR1 — Data Set Ready input for UART1.
OMAT1.0 — Match output for Timer 1, channel 0.
I/OP0.13 — General purpose digital input/output pin.
ODTR1 — Data Terminal Ready output for UART1.
OMAT1.1 — Match output for Timer 1, channel 1.
I/OP0.14 — General purpose digital input/output pin.
IDCD1 — Data Carrier Detect input for UART1.
IEINT1 — External interrupt 1 input
Note: LOW on this pin while RESET is LOW forces on-chip boot-loader to
take over control of the part after reset.
I/OP0.15 — General purpose digital input/output pin.
IRI1 — Ring Indicator input for UART1.
IEINT2 — External interrupt 2 input.
I/OP0.16 — General purpose digital input/output pin.
IEINT0 — External interrupt 0 input.
OMAT0.2 — Match output for Timer 0, channel 2.
ICAP0.2 — Capture input for Timer 0, chan nel 2.
I/OP0.17 — General purpose digital input/output pin.
ICAP1.2 — Capture input for Timer 1, chan nel 2.
I/OSCK1 — Serial Clock for SSP. Clock output from master or input to slave
(available in LPC2210/01 and LPC2220 only).
OMAT1.2 — Match output for Timer 1, channel 2.
I/OP0.18 — General purpose digital input/output pin.
ICAP1.3 — Capture input for Timer 1, chan nel 3.
I/OMISO1 — Master In Slave Out for SSP. Data input to SPI master or data
output from SSP slave (available in LPC2210/01 and LPC2220 only).
OMAT1.3 — Match output for Timer 1, channel 3.
I/OP0.19 — General purpose digital input/output pin.
OMAT1.2 — Match output for Timer 1, channel 2.
Table 54. Pin description
SymbolPin
(LQFP)
P0.19/MAT1.2/
122
MOSI1/CAP1.2
I/OMOSI1 — Master Out Slave In for SSP. Dat a output from SSP master or data
input to SSP slave (available in LPC2210/01 and LPC220 only).
ICAP1.2 — Capture input for Timer 1, chan nel 2.
P0.20/MAT1.3/
SSEL1/EINT3
123
[2]
B8
[2]
I/OP0.20 — General purpose digital input/output pin.
OMAT1.3 — Match output for Timer 1, channel 3.
ISSEL1 — Slave Select for SSP. Selects the SSP interface as a slave
(available in LPC2210/01 and LPC220 only).
IEINT3 — External interrupt 3 input.
P0.21/PWM5/
CAP1.3
[1]
4
C1
[1]
I/OP0.21 — General purpose digital input/output pin.
OPWM5 — Pulse Width Modulator output 5.
ICAP1.3 — Capture input for Timer 1, chan nel 3.
P0.22/
CAP0.0/MAT0.0
[1]
5
D4
[1]
I/OP0.22 — General purpose digital input/output pin.
ICAP0.0 — Capture input for Timer 0, chan nel 0.
OMAT0.0 — Match output for Timer 0, channel 0.
P0.236
P0.248
P0.2521
P0.27/AIN0/
23
CAP0.1/MAT0.1
[1]
[1]
[1]
[4]
D3
D1
H1
H3
[1]
[1]
[1]
[4]
I/OP0.23 — General purpose digital input/output pin.
I/OP0.24 — General purpose digital input/output pin.
I/OP0.25 — General purpose digital input/output pin.
I/OP0.27 — General purpose digital input/output pin.
IAIN0 — A/D converter input 0.
ICAP0.1 — Capture input for Timer 0, chan nel 1.
OMAT0.1 — Match output for Timer 0, channel 1.
P0.28/AIN1/
CAP0.2/MAT0.2
25
[4]
J1
[4]
I/OP0.28 — General purpose digital input/output pin.
IAIN1 — A/D converter input 1.
ICAP0.2 — Capture input for Timer 0, chan nel 2.
OMAT0.2 — Match output for Timer 0, channel 2.
P0.29/AIN2/
CAP0.3/MAT0.3
32
[4]
L1
[4]
I/OP0.29 — General purpose digital input/output pin.
IAIN2 — A/D converter input 2.
ICAP0.3 — Capture input for Timer 0, Channel 3.
OMAT0.3 — Match output for Timer 0, channel 3.
P0.30/AIN3/
EINT3/CAP0.0
33
[4]
L2
[4]
I/OP0.30 — General purpose digital input/output pin.
IAIN3 — A/D converter input 3.
IEINT3 — External interrupt 3 input.
ICAP0.0 — Capture input for Timer 0, chan nel 0.
P1.0 to P1.31I/OPort 1: Port 1 is a 32-bit bidirectional I/O port with individual direction controls
for each bit. The operation of port 1 pins depends upon the pin function
I/OP2.18 — General purpose digital input/output pin.
I/OD18 — External memory data line 18.
I/OP2.19 — General purpose digital input/output pin.
I/OD19 — External memory data line 19.
I/OP2.20 — General purpose digital input/output pin.
I/OD20 — External memory data line 20.
I/OP2.21 — General purpose digital input/output pin.
I/OD21 — External memory data line 21.
I/OP2.22 — General purpose digital input/output pin.
I/OD22 — External memory data line 22.
I/OP2.23 — General purpose digital input/output pin.
I/OD23 — External memory data line 23.
I/OP2.24 — General purpose digital input/output pin.
I/OD24 — External memory data line 24.
I/OP2.25 — General purpose digital input/output pin.
I/OD25 — External memory data line 25.
I/OP2.26 — General purpose digital input/output pin.
I/OD26 — External memory data line 26.
IBOOT0 — While RESET
is LOW, together with BOOT1 controls booting and
internal operation. Internal pull-up ensures HIGH state if pin is left
unconnected.
I/OP2.27 — General purpose digital input/output pin.
I/OD27 — External memory data line 27.
IBOOT1 — While RESET
is LOW, together with BOOT0 controls booting and
internal operation. Internal pull-up ensures HIGH state if pin is left
unconnected.
BOOT1:0 selects one of the following options:
- 00 selects 8-bit memory on CS0 for boot.
- 01 selects 16-bit memory on CS0 for boot.
- 10 selects 32-bit memory on CS0 for boot.
- 11 selects 16-bit memory on CS0 for boot.
I/OP2.28 — General purpose digital input/output pin.
I/OD28 — External memory data line 28.
I/OP2.29 — General purpose digital input/output pin.
I/OD29 — External memory data line 29.
I/OP2.30 — General purpose digital input/output pin.
I/OD30 — External memory data line 30.
IAIN4 — A/D converter, input 4.
I/OP2.31 — General purpose digital input/output pin.
I/OD31 — External memory data line 31.
IAIN5 — A/D converter, input 5.
I/OP3.19 — General purpose digital input/output pin.
OA19 — External memory address line 19.
I/OP3.20 — General purpose digital input/output pin.
OA20 — External memory address line 20.
I/OP3.21 — General purpose digital input/output pin.
OA21 — External memory address line 21.
I/OP3.22 — General purpose digital input/output pin.
OA22 — External memory address line 22.
I/OP3.23 — General purpose digital input/output pin.
OA23 — External memory address line 23.
OXCLK — Clock output.
I/OP3.24 — General purpose digital input/output pin.
OCS3 — LOW-active Chip Select 3 signal.
(Bank 3 addresses range 0x8300 0000 to 0x83FF FFFF)
I/OP3.25 — General purpose digital input/output pin.
OCS2 — LOW-active Chip Select 2 signal.
(Bank 2 addresses range 0x8200 0000 to 82FF FFFF)
I/OP3.26 — General purpose digital input/output pin.
OCS1 — LOW-active Chip Select 1 signal.
(Bank 1 addresses range 0x8100 0000 to 0x81FF FFFF)
I/OP3.27 — General purpose digital input/output pin.
OWE — LOW-active Write enable signal.
I/OP3.28 — General purpose digital input/output pin.
OBLS3 — LOW-active Byte Lane Select signal (External Memory Bank 3).
IAIN7 — A/D converter, input 7.
I/OP3.29 — General purpose digital input/output pin.
OBLS2 — LOW-active Byte Lane Select signal (External Memory Bank 2).
IAIN6 — A/D converter, input 6.
I/OP3.30 — General purpose digital input/output pin.
OBLS1 — LOW-active Byte Lane Select signal (External Memory Bank 1).
I/OP3.31 — General purpose digital input/output pin.
OBLS0 — LOW-active Byte Lane Select signal (External Memory Bank 0).
Not connected. This pin MUST NOT be pulled LOW or the device might not
operate properly.
IExternal reset input: A LOW on this pin resets the device, causing I/O ports
and peripherals to take on their default states, and processor execution to
begin at address 0. TTL with hysteresis, 5 V tolerant.
IInput to the oscillator circuit and internal clock genera to r circui ts.
OOutput from the oscillator amplifier.
VSS, but should be isolated to minimize noise and error.
voltage as VSS, but should be isolated to minimize noise and error.
circuitry.
internal circuitry. This should be nominally the same voltage as V
should be isolated to minimize noise and error.
I3.3 V pad power supply: This is the power supply voltage for the I/O ports.
as V
but should be isolated to minimize noise and error. This voltage is
DD(V3)
used to power the ADC.
DD(V18)
but
[1] 5 V tolerant pad providing digital I/O functions with TTL levels and hysteresis and 10 ns slew rate control.
[2] 5 V tolerant pad providing digital I/O functions with TTL levels and hysteresis and 10 ns slew rate control. If configured for an input
function, this pad utilizes built-in glitch filter that blocks pulses shorter than 3 ns.
2
[3] Open drain 5 V tolerant digital I/O I
functionality.
[4] 5 V tolerant pad providing digital I/O (with TTL levels and hysteresis and 10 ns slew rate control) and analog input function. If configured
for a digital input function, this pad utilizes built-in glitch filter that blocks pulses shorter than 3 ns. When configured as an ADC input,
digital section of the pad is disabled.
[5] 5 V tolerant pad with built-in pull-up resistor providing digital I/O functions with TTL levels and hysteresis and 10 ns slew rate control.
The pull-up resistor’s value ranges from 60 kΩ to 300 kΩ.
[6] 5 V tolerant pad providing digital input (with TTL levels and hysteresis) function only.
[7] Pad provides special analog functionality.
C-bus 400 kHz specification compatible pad. It requires external pull-up to provide an output
1.Features
Allows individual pin configuration.
2.Applications
The purpose of the Pin Connect Block is to configure the microcontroller pins to the
desired functions.
3.Description
The pin connect block allows selected pins of the microcontroller to have more than one
function. Configuration registers control the multiplexers to allow connection between the
pin and the on chip peripherals.
UM10114
Chapter 7: Pin connect block
Rev. 02 — 27 April 2007User manual
Peripherals should be connected to the appropri ate pins prior to being activated, and prior
to any related interrupt(s) being enabled. Activity of any enabled peripheral function that is
not mapped to a related pin should be considered undefined.
Selection of a single function on a port pin completely excludes all other functions
otherwise available on the same pin.
The only partial exception from the above rule of exclusion is the case of inputs to the A/D
converter. Regardless of the function that is selected for the port pin that also hosts the
A/D input, this A/D input can be read at any time and var iations of the vol t age level on this
pin will be reflected in the A/D readings. However, valid analog reading(s) can be obtained
if and only if the function of an analog input is selected. Only in this case proper interface
circuit is active in between the physical pin and the A/D module. In all other cases, a par t
of digital logic necessary for the digital function to be performed will be active, and will
disrupt proper behavior of the A/D.
4.Register description
The Pin Control Module contains 2 registers as shown in Table 7–55 below.
. The direction control bit in the IO0DIR register is effective only when the
01TXD (UART0)
10PWM1
11Reserved
01RxD (UART0)
10PWM3
11EINT0
2
01SCL (I
10Capture 0.0 (Timer 0)
11Reserved
01SDA (I
10Match 0.0 (Timer 0)
11EINT1
01SCK0 (SPI0)
10Capture 0.1 (Timer 0)
11Reserved
01MISO0 (SPI0)
10Match 0.1 (Timer 0)
11Reserved
01MOSI0 (SPI0)
10Capture 0.2 (Timer 0)
11Reserved
01SSEL0 (SPI0)
10PWM2
11EINT2
01TXD UART1
10PWM4
11Reserved
C)
2
C)
NXP Semiconductors
UM10114
Chapter 7: LPC2210/20 Pin connect block
Table 56.Pin Function Select Register 0 (PINSEL0 - address 0xE002 C000) bit description
BitSymbolValueFunctionValue after reset
19:18P0.900GPIO Port 0.90
01RxD (UART1)
10PWM6
11EINT3
21:20P0.1000GPIO Port 0.100
01RTS (UART1)
10Capture 1.0 (Timer 1)
11Reserved
23:22P0.1100GPIO Port 0.110
01CTS (UART1)
10Capture 1.1 (Timer 1)
11Reserved
25:24P0.1200GPIO Port 0.120
01DSR (UART1)
10Match 1.0 (Timer 1)
11Reserved
27:26P0.1300GPIO Port 0.130
01DTR (UART1)
10Match 1.1 (Timer 1)
11Reserved
29:28P0.1400GPIO Port 0.140
01CD (UART1)
10EINT1
11Reserved
31:30P0.1500GPIO Port 0.150
01RI (UART1)
10EINT2
11Reserved
4.2Pin Function Select Register 1 (PINSEL1 - 0xE002 C004)
The PINSEL1 register controls the functions of the pins as per the settings listed in
following tables. The direction control bit in the IO0DIR register is effective only when the
GPIO function is selected for a pin. For other functions direction is controlled
automatically.
Table 57.Pin Function Select Register 1 (PINSEL1 - address 0xE002 C004) bit description
4.3Pin Function Select Register 2 (PINSEL2 - 0xE002 C014)
The PINSEL2 register controls the functions of the pins as per the settings listed in
Table 7–58
only when the GPIO function is selected for a pin. For other functions direction is
controlled automatically.
Warning: Use read-modify-write ope ra tion when accessing PINSEL2 register. Accidental
write of 0 to bit 2 and/or bit 3 results in loss of debug and/or trace functionality! Changing
of either bit 4 or bit 5 from 1 to 0 may cause an incorrect code execution!
Table 58. Pin Function Select Register 2 (PINSEL2 - 0xE002 C014) bit description
BitSymbolValue FunctionValue after reset
1:0-NAReserved, user software should not write ones to reserved bits. The
2GPIO/
DEBUG
3GPIO/
TRACE
Controls the use of P1.31-26 pin s.
0Pins P1.31-26 are used as GPIO pins.P1.26
1Pins P1.31-26 are used as a Debug port.
Controls the use of P1.25-16 pin s .P1.20
0Pins P1.25-16 are used as GPIO pins.
1Pins P1.25-16 are used as a Trace port.
. The direction control bit in the IO1DIR/IO2DIR/IO3DIR register is effective
Table 58. Pin Function Select Register 2 (PINSEL2 - 0xE002 C014) bit description
BitSymbolValue FunctionValue after reset
5:4CTRLDBPControls the use of the data bus and strobe pins. At a reset triggered via the
RESET pin, these bits are loaded with the content from lines BOOT1:0; if a
watchdog reset occurs, these two bits are loaded with the BOOT10_SAVE
register content (see Section 7–5 “
Functions available based on PINSEL2[5:4] values
Pins
P1.1OEP1.1
P2.7:0D7:0P2.7:0
P2.15:8D15:8P2.15:8
P2.27:16D27:16P2.27:16
P2.29:28D29:28P2.29:28 or reser v ed (s ee bi t 20 )
P2.30D30P2.30 or AIN4 (see bit 21)
P2.31D31P2.31 or AIN5 (see bit 22)
P1.0CS0P1.0
P3.31BLS0P3.31
P3.30BLS1P3.30
P3.28BLS2P3.28 or AIN6 (see bit 7)
P3.29BLS3P3.29 or AIN7 (see bit 6)
10010011
Boot control” on page 82).
…continued
BOOT1:0 or
BOOT10_SAVE
6CTRLP329If bits 5:4 are not 10, controls the use of pin P3.29:1
0P3.29 is a GPIO pin.
1P3.29 is an ADC input pin (AIN6).
7CTRLP328If bits 5:4 are not 10, controls the use of pin P3.28:1
0P3.28 is a GPIO pin.
1P3.28 is an ADC input pin (AIN7).
8CTRLP327Controls the use of pin P3.27:0
0P3.27 is a GPIO pin.
1P3.27 is a Write Enable pin (WE).
10:9-Reserved11CTRLP326Controls the use of pin P3.26:0
0P3.26 is a GPIO pin.
1P3.26 is a chip/memory bank select pin (CS1).
12-NAReserved13CTRLP323If bits 25:23 are not 111, controls the use of pin P3.23/A23/XCLK:0
0P3.23 is a GPIO/address line pin (see bits 27:25).
1P3.23 is XCLK output pin.
15:14CTRLP325Controls the use of pin P3.25:00
00P3.25 is a GPIO pin.
01P3.25 is a chip/memory bank select pin (CS2).
10Reserved
11Reserved
Table 58. Pin Function Select Register 2 (PINSEL2 - 0xE002 C014) bit description
BitSymbolValue FunctionValue after reset
17:16CTRLP324Controls the use of pin P3.24:00
00P3.24 is a GPIO pin.
01P3.24 is a chip/memory bank select pin (CS3).
10Reserved
11Reserved
19:18-NAReserved20CTRLP229_28If bits PINSEL2[5:4] are not 10, controls the use of pin P2.29:28:0
0P2.29 and P2.28 are GPIO pins.
1Reserved
21CTRLP230If bits PINSEL2[5:4] are not 10, controls the use of pin P2.30:1
0P2.30 is a GPIO pin.
1P2.30 is an ADC input pin (AIN4).
22CTRLP231If bits PINSEL2[5:4] are not 10, controls the use of pin P2.31:1
0P2.31 is a GPIO pin.
1P2.31 is an ADC input pin (AIN5).
23CTRLP300Controls P3.0/A0 (if it is a port pin or an address line):1 if BOOT1:0 = 00
0P3.0/A0 is a GPIO pin.
1P3.0/A0 is an address line.
24CTRLP301Controls 3.1/A1 (if it is a port pin or an address line):BOOT1
03.1/A1 is a GPIO pin.
13.1/A1 is an address line.
27:25CTRLABControls the number of pins among P3.23/A23/XCLK and P3.22:2/A2.22:2 that
are address lines:
000None
001A3:2 are address lines.
010A5:2 are address lines.
011A7:2 are address lines.
100A11:2 are address lines.
101A15:2 are address lines.
1 10A19:2 are address lines.
1 11A23:2 are address lines.
31:28-NAReserved, user software should not write ones to reserved bits. The
value read from a reserved bit is not defined.
…continued
at RESET = 0, 0
otherwise
during
Reset
000 if
BOOT1:0 = 11 at
Reset;
111 otherwise
00
4.4Pin function select register values
The PINSEL registers control the functions of device pins as shown below. Pairs of bits in
these registers correspond to specific device pins.
PINSEL0 & PINSEL1 values FunctionValue after reset
00Primary (default) function, typically GPIO port00
01First alternate function
10Second alternate function
11Reserved
The direction control bit in the IO0DIR/IO1DIR register is effective only when the GPIO
function is selected for a pin. For other functions, direction is controlled automatically.
Each derivative typically has a different pinout and theref or e a different set of fu nct ion s
possible for each pin. Details for a specific derivative may be found in the appropriate data
sheet.
5.Boot control
The state of the BOOT1:0 pins, while RESET is low, controls booting and initial operation.
Internal pullups in the receivers ensure high state if a pin is left unconnected. Board
designers can connect weak pulldown resistors (10 kΩ) or transistors that drive low while
RESET is low, to these pins to select among the following options:
Table 60.Boot control on BOOT1:0
P2.27/D27/BOOT1 P2.26/D26/BOOT0 Boot from
008 bit memory on CS0
0116 bit memory on CS0
1032 bit memory on CS0
1116 bit memory on CS0
UM10114
Chapter 7: LPC2210/20 Pin connect block
When LPC2210/2220 and LPC2210/01 hardware detects a rising edge on the Reset pin,
it latches content from BOOT[1:0] pins and stores it into bits 5 and 4 of the
BOOT10_SAVE register (0x3FFF 8030). Once this register is written, it is accessible for
reading only.
Whenever the bootloader is executed, it reads the content of the BOOT10_SAVE register,
and configures the PINSEL2 (address and data bus structure) together with other
resources. For the bootloader flowchart details, see Figure 19–63 “
• Every physical GPIO port is accessible via either the group of registers providing an
enhanced features and accelerated port access or the legacy group of registers
• Accelerated GPIO functions (available in LPC2210/01 and LPC2220 only):
– GPIO registers are relocated to the ARM local bus so that the fastest possible I/O
timing can be achieved
– Mask registers allow treating sets of port bits as a group, leaving other bits
unchanged
– All registers are byte and half-word addressable
– Entire port value can be written in one instruction
• Bit-level set and clear registers allow a single instruction set or clear of an y number of
bits in one port
• Direction control of individual bits
• All I/O default to inputs after reset
• Backward compatibility with other earlier devices is maintained with legacy registers
appearing at the original addresses on the APB bus
2.Applications
• General purpose I/O
• Driving LEDs, or other indicators
• Controlling off-chip devices
• Sensing digital inputs
3.Pin description
Table 61.GPIO pin description
PinTypeDescription
P0.0-P.31
P1.16-P1.31
P2.0-P2.31
P3.0-P3.31
4.Register description
LPC2210/2220 and LPC2210/01 have two 32-bit General Purpose I/O ports. Total of 30
out of 32 pins are available on PORT0. PORT1 has up to 16 pins available for GPIO
functions. PORT0 and PORT1 are controlled via two groups of 4 registers as shown in
Table 8–62
and Table 8–63. Apart from them, LPC2210/2220 and LPC2210/01 have two
Input/
Output
Input/
Output
General purpose input/output. The number of GPIOs actually available
depends on the use of alternate functions.
External bus data/address lines shared with GPIO, digital and analog
functions. The number of GPIOs/digital and analog functions actually
available depends on the selected bus structure.
additional 32-bit ports, PORT2 and PORT3, and they are configured to be used either as
external memory data address and data bus, or as GPIOs sharing pin s wit h a hand fu l of
digital and analog functions. Details on PORT2 and PORT3 usage can be found in Pin
Configuration chapter on page 63 and Pin Connect Block chapter on page 75.
UM10114
Chapter 8: LPC2210/20 GPIO
Legacy registers shown in Table 8–62
devices, using existing code. The functions an d rela tive timin g of olde r GPI O
implementations is preserved.
The registers in Table 8–63
PORT0 and PORT1 only. All of thes e re gis te rs ar e located directly on the local bus of the
CPU for the fastest possible read and write timing. An additional feature has been added
that provides byte addressability of all GPIO registers. A mask register allows treating
groups of bits in a single GPIO port separately from other bits on the same port.
When PORT0 and/or PORT1 are used, user must select whether a these ports will be
accessed via registers that provide enhanced features or a legacy set of registers (see
Section 4–6.1 “
34). While both of a port’s fast and legacy GPIO registers are controlling the same
physical pins, these two port control branches are mutually exclusive and operate
independently. For example, changing a pin’s output via a fast register will not be
observable via the corresponding legacy register.
The following text will refer to the legacy GPIO as "the slow" GPIO, while GPIO equipped
with the enhanced features will be referred as "the fast" GPIO.
While the legacy registers are available on LPC2210/2220 and LPC2210/01 devices,
registers controlling the enhanced features are available on LPC2210/01 and LPC2220
devices only.
System Control and Status flags register (SCS - 0xE01F C1A0)” on page
represent the enhanced GPIO features available on the
IO0PIN
GPIO configured port pins
can always be read from this
register, regardless of pin
direction.
IOSETGPIO Port Output Set
register. This register
R/W0x0000
0000
0xE002 8004
IO0SET
controls the state of output
pins in conjunction with the
IOCLR register. Writing ones
produces highs at the
corresponding port pins.
Writing zeroes has no effect.
IODIRGPIO Port Direction control
register. This register
R/W0x0000
0000
0xE002 8008
IO0DIR
individually controls the
direction of each port pin.
IOCLRGPIO Port Output Clear
register. This register
WO0x0000
0000
0xE002 800C
IO0CLR
controls the state of output
pins. Writing ones produces
lows at the corresponding
port pins and clears the
corresponding bits in the
IOSET register. Writing
zeroes has no effect.
PORT1
Address &
Name
0xE002 8010
IO1PIN
0xE002 8014
IO1SET
0xE002 8018
IO1DIR
0xE002 801C
IO1CLR
PORT2
Address &
name
0xE002 8020
IO2PIN
0xE002 8024
IO2SET
0xE002 8028
IO2DIR
0xE002 802C
IO2CLR
PORT3
Address &
name
0xE002 8030
IO3PIN
0xE002 8034
IO3SET
0xE002 8038
IO3DIR
0xE002 803C
IO3CLR
[1] Reset value reflects the data stored in used bits only. It does not include reserved bits content.
Table 63. GPIO register map (local bus accessible registers - enhanced features in LPC2210/01 and LPC220 only)
Generic
DescriptionAccess Reset
Name
FIODIRFast GPIO Port Direction control register.
This register individually controls the
[1]
value
Address & Name
R/W0x0000 0000 0x3FFF C000
FIO0DIR
PORT0
PORT1
Address & Name
0x3FFF C020
FIO1DIR
direction of each port pin.
FIOMASKFast Mask register for port. Writes, sets,
clears, and reads to port (done via writes to
R/W0x0000 0000 0x3FFF C010
FIO0MASK
0x3FFF C030
FIO1MASK
FIOPIN, FIOSET , and FIOCLR, and reads of
FIOPIN) alter or return only the bits enabled
by zeros in this register.
Table 63. GPIO register map (local bus accessible registers - enhanced features in LPC2210/01 and LPC220 only)
Generic
Name
FIOPINFast Port Pin value register using FIOMASK.
FIOSETFast Port Output Set register using
FIOCLRFast Port Output Clear register using
DescriptionAccess Reset
value
R/W0x0000 0000 0x3FFF C014
The current state of digital port pins can be
read from this register, regardless of pin
direction or alternate function selection (as
long as pins is not configured as an input to
ADC). The value read is masked by ANDing
with FIOMASK. Writing to this register
places corresponding values in all bits
enabled by zeroes in FIOMASK.
R/W0x0000 0000 0x3FFF C018
FIOMASK. This register controls the state of
output pins. Writing 1s produces highs at the
corresponding port pins. Writing 0s has no
effect. Reading this register returns the
current contents of the port output register.
Only bits enabled by zeroes in FIOMASK
can be altered.
WO0x0000 0000 0x3FFF C01C
FIOMASK0. This register controls the state
of output pins. Writing 1s produces lows at
the corresponding port pins. Writing 0s has
no effect. Only bits enabled by zeroes in
FIOMASK0 can be altered.
[1]
PORT0
Address & Name
FIO0PIN
FIO0SET
FIO0CLR
PORT1
Address & Name
0x3FFF C034
FIO1PIN
0x3FFF C038
FIO1SET
0x3FFF C03C
FIO1CLR
[1] Reset value reflects the data stored in used bits only. It does not include reserved bits content.
This word accessible register is used to control the direction of the pins when they are
configured as GPIO port pins. Direction bit for any pin must be set according to the pin
functionality.
Legacy registers are the IO0DIR, IO1DIR, IO2DIR and IO3DIR while the enhanced GPIO
functions are supported via the FIO0DIR and FIO1DIR registers.
Table 64. GPIO port 0 Direction register (IO0DIR - address 0xE002 8008) bit description
BitSymbolValue DescriptionReset value
31:0P0xDIR
Table 65. GPIO port 1 Direction register (IO1DIR - address 0xE002 8018) bit description
BitSymbolValue DescriptionReset value
31:0P1xDIR
Slow GPIO Direction control bits. Bit 0 controls P0.0 ... bit 30 controls P0.30.
0
1Controlled pin is output.
0
1Controlled pin is output.
Controlled pin is input.
Slow GPIO Direction control bits. Bit 0 in IO1DIR controls P1.0 ... Bit 30 in
IO1DIR controls P1.30.
Table 66. GPIO port 2 Direction register (IO2DIR - address 0xE002 8028) bit description
BitSymbolValue DescriptionReset value
31:0P2xDIR
Slow GPIO Direction control bits. Bit 0 in IO2DIR controls P2.0 ... Bit 30 in
0x0000 0000
IO2DIR controls P2.30.
0
Controlled pin is input.
1Controlled pin is output.
Table 67. GPIO port 3 Direction register (IO3DIR - address 0xE002 8038) bit description
BitSymbolValue DescriptionReset value
31:0P3xDIR
Slow GPIO Direction control bits. Bit 0 in IO3DIR controls P3.0 ... Bit 30 in
0x0000 0000
IO3DIR controls P3.30.
0
Controlled pin is input.
1Controlled pin is output.
Table 68. Fast GPIO port 0 Direction register (FIO0DIR - address 0x3FFF C000) bit description
BitSymbolValue DescriptionReset value
31:0FP0xDIR
Fast GPIO Direction control bits. Bit 0 in FIO0DIR controls P0.0 ... Bit 30 in
0x0000 0000
FIO0DIR controls P0.30.
0
Controlled pin is input.
1Controlled pin is output.
Table 69. Fast GPIO port 1 Direction register (FIO1DIR - address 0x3FFF C020) bit description
BitSymbolValue DescriptionReset value
31:0FP1xDIR
Fast GPIO Direction control bits. Bit 0 in FIO1DIR controls P1.0 ... Bit 30 in
0x0000 0000
FIO1DIR controls P1.30.
0
Controlled pin is input.
1Controlled pin is output.
Aside from the 32-bit long and word only accessible FIODIR register, every fast GPIO port
can also be controlled via several byte and half-word accessible registers listed in
Table 8–70
and Table 8–71, too. Next to providing the same functions as the FIOD IR
register, these additiona l registers allow easie r and faster access to the physical port pins.
Table 70. Fast GPIO port 0 Direction control byte and half-word accessible register description
Register
name
Register
length (bits)
& access
FIO0DIR08 (byte)0x3FFF C000 Fast GPIO Port 0 Direction control register 0. Bit 0 in FIO0DIR0
FIO0DIR18 (byte)0x3FFF C001 Fast GPIO Port 0 Direction control register 1. Bit 0 in FIO0DIR1
FIO0DIR28 (byte)0x3FFF C002 Fast GPIO Port 0 Direction control register 2. Bit 0 in FIO0DIR2
This register is used to produce a HIGH level output at the port pins configured as GPIO in
an OUTPUT mode. Writing 1 produces a HIGH level at the corresponding port pins.
Writing 0 has no effect. If any pin is configured as an input or a se condary functio n, writing
1 to the corresponding bit in the IOSET has no effect.
value
0x00
0x00
0x00
0x00
0x0000
0x0000
Reading the IOSET register returns the value of this register, as determined by previous
writes to IOSET and IOCLR (or IOPIN as noted above). This value does not reflect the
effect of any outside world influence on the I/O pins.
Legacy registers are the IO0SET, IO1SET, IO2SET and IO3SET while the enhanced
GPIOs are supported via the FIO0SET and FIO1SET registers. Access to a port pins via
the FIOSET register is conditioned by the corresponding FIOMASK register (see Section
Table 73. GPIO port 1 output Set register (IO1SET - address 0xE002 8014) bit description
BitSymbolDescriptionReset value
31:0P1xSETSlow GPIO output value Set bits. Bit 0 in IO1SET corresponds to P1.0 ... Bit 30
0x0000 0000
in IO1SET corresponds to P1.30.
Table 74. GPIO port 2 output Set register (IO2SET - address 0xE002 8024) bit description
BitSymbolDescriptionReset value
31:0P2xSETSlow GPIO output value Set bits. Bit 0 in IO2SET corresponds to P2.0 ... Bit 30
0x0000 0000
in IO2SET corresponds to P2.30.
Table 75. GPIO port 3 output Set register (IO3SET - address 0xE002 8034) bit description
BitSymbolDescriptionReset value
31:0P3xSETSlow GPIO output value Set bits. Bit 0 in IO3SET corresponds to P3.0 ... Bit 30
0x0000 0000
in IO3SET corresponds to P3.30.
Table 76. Fast GPIO port 0 output Set register (FIO0SET - address 0x3FF F C018) bit description
BitSymbolDescriptionReset value
31:0FP0xSETFast GPIO output value Set bits. Bit 0 in FIO0SET corresponds to P0.0 ... Bit 31
0x0000 0000
in FIO0SET corresponds to P0.31.
Table 77. Fast GPIO port 1 output Set register (FIO1SET - address 0x3FF F C038) bit description
BitSymbolDescriptionReset value
31:0FP1xSETFast GPIO output value Set bits. Bit 0 Fin IO1SET corresponds to P1.0 ... Bit
0x0000 0000
31 in FIO1SET corresponds to P1.31.
Aside from the 32-bit long and word only accessible FIOSET register, every fast GPIO
port can also be controlled via several byte and half-word accessible registers listed in
Table 8–78
and Table 8–79, too. Next to providing the same functions as the FIOSE T
register, these additiona l registers allow easie r and faster access to the physical port pins.
Table 78. Fast GPIO port 0 output Set byte and half-word accessible register description
Register
name
Register
length (bits)
& access
FIO0SET08 (byte)0x3FFF C018 Fast GPIO Port 0 output Set register 0. Bit 0 in FIO0SET0 register
FIO0SET18 (byte)0x3FFF C019 Fast GPIO Port 0 output Set register 1. Bit 0 in FIO0SET1 register
FIO0SET28 (byte)0x3FFF C01A Fast GPIO Port 0 output Set register 2. Bit 0 in FIO0SET2 register
FIO0SET38 (byte)0x3FFF C01B Fast GPIO Port 0 output Set register 3. Bit 0 in FIO0SET3 register
FIO0SETL16
(half-word)
FIO0SETU16
(half-word)
AddressDescriptionReset
corresponds to P0.0 ... bit 7 to P0.7.
corresponds to P0.8 ... bit 7 to P0.15.
corresponds to P0.16 ... bit 7 to P0.23.
corresponds to P0.24 ... bit 7 to P0.31.
0x3FFF C018Fast GPIO Port 0 output Set Lower half-word register. Bit 0 in
FIO0SETL register corresponds to P0.0 ... bit 15 to P0.15.
0x3FFF C01A Fast GPIO Port 0 output Set Upper half-word register. Bit 0 in
FIO0SETU register corresponds to P0.16 ... bit 15 to P0.31.
This register is used to produce a LOW level output at port pins configured as GPIO in an
OUTPUT mode. Writing 1 produces a LOW leve l at the cor respond ing po rt pin a nd cle ars
the corresponding bit in the IOSET register. Wr iting 0 has no effect. If any pin is configured
as an input or a secondary function, writing to IOCLR has no effect.
value
0x00
0x00
0x00
0x00
0x0000
0x0000
Legacy registers are the IO0CLR, IO1CLR, IO2CLR and IO3CLR while the enhanced
GPIOs are supported via the FIO0CLR and FIO1CLR registers. Access to a port pins via
the FIOCLR register is conditioned by the corresponding FIOMASK register (see Section
Table 83. GPIO port 3 output Clear register 3 (IO3CLR - address 0xE002 803C) bit description
BitSymbolDescriptionRe set value
31:0P3xCLRSlow GPIO output value Clear bits. Bit 0 in IO3CLR corresponds to P1.0 ... Bit
0x0000 0000
30 in IO3CLR corresponds to P2.30.
Table 84. Fast GPIO port 0 output Clear register 0 (FIO0CLR - address 0x3FFF C01C) bit descrip tion
BitSymbolDescriptionReset value
31:0FP0xCLRFast GPIO output value Clear bits. Bit 0 in FIO0CLR corresponds to P0.0 ... Bit
0x0000 0000
31 in FIO0CLR corresponds to P0.31.
Table 85. Fast GPIO port 1 output Clear register 1 (FIO1CLR - address 0x3FFF C03C) bit descrip tion
BitSymbolDescriptionRe set value
31:0FP1xCLRFast GPIO output value Clear bits. Bit 0 in FIO1CLR corresponds to P1.0 ... Bit
0x0000 0000
31 in FIO1CLR corresponds to P1.31.
Aside from the 32-bit long and word only accessible FIOCLR register, every fast GPIO
port can also be controlled via several byte and half-word accessible registers listed in
Table 8–86
and Table 8–87, too. Next to providing the same functions as the FIOC LR
register, these additiona l registers allow easie r and faster access to the physical port pins.
Table 86. Fast GPIO port 0 output Clear byte and half-word accessible register description
Register
name
Register
length (bits)
& access
FIO0CLR08 (byte)0x3FFF C01C Fast GPIO Port 0 output Clear register 0. Bit 0 in FIO0CLR0 register
FIO0CLR18 (byte)0x3FFF C01D Fast GPIO Port 0 output Clear register 1. Bit 0 in FIO0CLR1 register
FIO0CLR28 (byte)0x3FFF C01E Fast GPIO Port 0 output Clear register 2. Bit 0 in FIO0CLR2 register
FIO0CLR38 (byte)0x3FFF C01F Fast GPIO Port 0 output Clear register 3. Bit 0 in FIO0CLR3 register
FIO0CLRL16
(half-word)
FIO0CLRU 16
(half-word)
AddressDescriptionReset
corresponds to P0.0 ... bit 7 to P0.7.
corresponds to P0.8 ... bit 7 to P0.15.
corresponds to P0.16 ... bit 7 to P0.23.
corresponds to P0.24 ... bit 7 to P0.31.
0x3FFF C01C Fast GPIO Port 0 output Clear Lower half-word register. Bit 0 in
FIO0CLRL register corresponds to P0.0 ... bit 15 to P0.15.
0x3FFF C01E Fast GPIO Port 0 output Clear Upper half-word register. Bit 0 in
FIO0SETU register corresponds to P0.16 ... bit 15 to P0.31.
value
0x00
0x00
0x00
0x00
0x0000
0x0000
Table 87. Fast GPIO port 1 output Clear byte and half-word accessible register description
Register
name
Register
length (bits)
AddressDescriptionReset
value
& access
FIO1CLR08 (byte)0x3FFF C03C Fast GPIO Port 1 output Clear register 0. Bit 0 in FIO1CLR0 register
0x00
corresponds to P1.0 ... bit 7 to P1.7.
FIO1CLR18 (byte)0x3FFF C03D Fast GPIO Port 1 output Clear register 1. Bit 0 in FIO1CLR1 register
0x00
corresponds to P1.8 ... bit 7 to P1.15.
FIO1CLR28 (byte)0x3FFF C03E Fast GPIO Port 1 output Clear register 2. Bit 0 in FIO1CLR2 register
This register provides the value of port pins that are configured to perform only digital
functions. The register will give the logic value of the pin regardless of whether the pin is
configured for input or output, or as GPIO or an alternate digital function. As an example,
a particular port pin may have GPIO input, GPIO output, UART receive, and PWM output
as selectable functions. Any configuration of that pin will allow its current logic state to be
read from the corresponding IOPIN register.
value
0x00
0x0000
0x0000
If a pin has an analog function as one of its options, the pin state cannot be r ead if the
analog configuration is selected. Selecting the pin as an A/D input disconnect s the digital
features of the pin. In that case, the pin value read in the IOPIN register is not valid.
Writing to the IOPIN register stores the value in the port output register, bypassing the
need to use both the IOSET and IOCLR registers to obtain the entire written value. This
feature should be used carefully in an application since it affects the entire port.
Legacy registers are the IO0PIN, IO1PIN, IO2PIN and IO3PIN while the enhanced GPIOs
are supported via the FIO0PIN and FIO1PIN registers. Access to a port pins via the
FIOPIN register is conditioned by the corresponding FIOMASK register (see Section
Table 90. GPIO port 2 Pin value register (IO2PIN - address 0xE002 8020) bit description
BitSymbolDescriptionReset value
31:0P2xVALSlow GPIO pin value bits. Bit 0 in IO2PIN corresponds to P1.0 ... Bit 30 in IO2PIN
NA
corresponds to P2.30.
Table 91. GPIO port 3 Pin value register (IO3PIN - address 0xE002 8030) bit description
BitSymbolDescriptionReset value
31:0P3xVALSlow GPIO pin value bits. Bit 0 in IO3PIN corresponds to P3.0 ... Bit 30 in IO3PIN
NA
corresponds to P3.30.
Table 92. Fast GPIO port 0 Pin value register (FIO0PIN - address 0x3FFF C014) bit description
BitSymbolDescriptionReset value
31:0FP0xVALFast GPIO pin value bits. Bit 0 in FIO0PIN corresponds to P0.0 ... Bit 30 in FIO0PIN
NA
corresponds to P0.30.
Table 93. Fast GPIO port 1 Pin value register (FIO1PIN - address 0x3FFF C034) bit description
BitSymbolDescriptionReset value
31:0FP1xVALFast GPIO pin value bits. Bit 0 in FIO1PIN corresponds to P1.0 ... Bit 30 in FIO1PIN
NA
corresponds to P1.30.
Aside from the 32-bit long and word only acce ssible FIOPIN register , every fast GPIO port
can also be controlled via several byte and half-word accessible registers listed in
Table 8–94
and Table 8–95, too. Next to providing the same functions as the FIOPIN
register, these additiona l registers allow easie r and faster access to the physical port pins.
Table 94. Fast GPIO port 0 Pin value byte and half-word accessible register description
Register
name
Register
length (bits)
& access
FIO0PIN08 (byte)0x3FFF C014Fast GPIO Port 0 Pin value register 0. Bit 0 in FIO0PIN0 register
FIO0PIN18 (byte)0x3FFF C015Fast GPIO Port 0 Pin value register 1. Bit 0 in FIO0PIN1 register
FIO0PIN28 (byte)0x3FFF C016Fast GPIO Port 0 Pin value register 2. Bit 0 in FIO0PIN2 register
FIO0PIN38 (byte)0x3FFF C017Fast GPIO Port 0 Pin value register 3. Bit 0 in FIO0PIN3 register
FIO0PINL16
(half-word)
FIO0PINU16
(half-word)
AddressDescriptionReset
corresponds to P0.0 ... bit 7 to P0.7.
corresponds to P0.8 ... bit 7 to P0.15.
corresponds to P0.16 ... bit 7 to P0.23.
corresponds to P0.24 ... bit 7 to P0.31.
0x3FFF C014Fast GPIO Port 0 Pin value Lower half-word register. Bit 0 in
FIO0PINL register corresponds to P0.0 ... bit 15 to P0.15.
0x3FFF C016Fast GPIO Port 0 Pin value Upper half-word register. Bit 0 in
FIO0PINU register corresponds to P0.16 ... bit 15 to P0.31.
This register is available in the enhanced group of registers only. It is used to select port’s
pins that will and will not be affected by a write accesses to the FIOPIN, FIOSET or
FIOSLR register. Mask register also filters out port’s content when the FIOPIN register is
read.
value
0x00
0x00
0x00
0x00
0x0000
0x0000
A zero in this register’s bit enables an access to the corresponding physical pin via a read
or write access. If a bit in this register is one, corresponding pin will not be changed with
write access and if read, will not be reflected in the updated FIOPIN register. For software
examples, see Section 8–5 “
Table 96. Fast GPIO port 0 Mask register (FIO0MASK - address 0x3FFF C010) bit description
BitSymbolValue DescriptionReset value
31:0FP0xMASK
Table 97. Fast GPIO port 1 Mask register (FIO1MASK - address 0x3FFF C030) bit description
BitSymbolValue DescriptionReset value
31:0FP1xMASK
Fast GPIO physical pin access control.
0
1Physical pin is unaffected by writes into the FIOSET, FIOCLR and FIOPIN
0
1Physical pin is unaffected by writes into the FIOSET, FIOCLR and FIOPIN
Pin is affected by writes to the FIOSET, FIOCLR, and FIOPIN registers.
Current state of the pin will be observable in the FIOPIN register.
registers. When the FIOPIN register is read, the coresponding physical pin will
be represented as 0.
Fast GPIO physical pin access control.
Pin is affected by writes to the FIOSET, FIOCLR, and FIOPIN registers.
Current state of the pin will be observable in the FIOPIN register.
registers. When the FIOPIN register is read, the coresponding physical pin will
be represented as 0.
Aside from the 32-bit long and word only accessible FIOMASK register, every fast GPIO
port can also be controlled via several byte and half-word accessible registers listed in
Table 8–98
and Table 8–99, too. Next to providing the same functions as the FIOMASK
register, these additiona l registers allow easie r and faster access to the physical port pins.
Table 98. Fast GPIO port 0 Mask byte and half-word accessible register description
Register
name
FIO0MASK0 8 (byte)0x3FFF C010Fast GPIO Port 0 Mask register 0. Bit 0 in FIO0MASK0 register
FIO0MASK1 8 (byte)0x3FFF C011Fast GPIO Port 0 Mask register 1. Bit 0 in FIO0MASK1 register
FIO0MASK2 8 (byte)0x3FFF C012Fast GPIO Port 0 Mask register 2. Bit 0 in FIO0MASK2 register
FIO0MASK3 8 (byte)0x3FFF C013Fast GPIO Port 0 Mask register 3. Bit 0 in FIO0MASK3 register
FIO0MASKL 16
FIO0MASKU 16
Register
length (bits)
& access
(half-word)
(half-word)
AddressDescriptionReset
corresponds to P0.0 ... bit 7 to P0.7.
corresponds to P0.8 ... bit 7 to P0.15.
corresponds to P0.16 ... bit 7 to P0.23.
corresponds to P0.24 ... bit 7 to P0.31.
0x3FFF C010Fast GPIO Port 0 Mask Lower half-word register. Bit 0 in
FIO0MASKL register corresponds to P0.0 ... bit 15 to P0.15.
0x3FFF C012Fast GPIO Port 0 Mask Upper half-word register. Bit 0 in
FIO0MASKU register corresponds to P0.16 ... bit 15 to P0.31.
value
0x00
0x00
0x00
0x00
0x0000
0x0000
Table 99. Fast GPIO port 1 Mask byte and half-word accessible register description
Register
name
FIO1MASK0 8 (byte)0x3FFF C010Fast GPIO Port 1 Mask register 0. Bit 0 in FIO1MASK0 register
FIO1MASK1 8 (byte)0x3FFF C011Fast GPIO Port 1 Mask register 1. Bit 0 in FIO1MASK1 register
FIO1MASK2 8 (byte)0x3FFF C012Fast GPIO Port 1 Mask register 2. Bit 0 in FIO1MASK2 register
FIO1MASK3 8 (byte)0x3FFF C013Fast GPIO Port 1 Mask register 3. Bit 0 in FIO1MASK3 register
FIO1MASKL 16
FIO1MASKU 16
Register
length (bits)
& access
(half-word)
(half-word)
AddressDescriptionReset
corresponds to P1.0 ... bit 7 to P1.7.
corresponds to P1.8 ... bit 7 to P1.15.
corresponds to P1.16 ... bit 7 to P1.23.
corresponds to P1.24 ... bit 7 to P1.31.
0x3FFF C010Fast GPIO Port 1 Mask Lower half-word register. Bit 0 in
FIO1MASKL register corresponds to P1.0 ... bit 15 to P1.15.
0x3FFF C012Fast GPIO Port 1 Mask Upper half-word register. Bit 0 in
FIO1MASKU register corresponds to P1.16 ... bit 15 to P1.31.
5.GPIO usage notes
5.1Example 1: sequential accesses to IOSET and IOCLR affecting the
same GPIO pin/bit
value
0x00
0x00
0x00
0x00
0x0000
0x0000
State of the output configured GPIO pin is determined by writes into the pin’s port IOSET
and IOCLR registers. Last of these accesses to the IOSET/IOCLR register will determine
the final output of a pin.
In case of a code:
IO0DIR = 0x0000 0080 ;pin P0.7 configured as output
pin P0.7 is configured as an output (write to IO0DIR register). After this, P0.7 output is set
to low (first write to IO0CLR register). Short high pulse follows on P0.7 (write access to
IO0SET), and the final write to IO0CLR register sets pin P0.7 back to low level.
5.2Example 2: an immediate output of 0s and 1s on a GPIO port
Write access to port’s IOSET followed by write to the IOCLR register results with pins
outputting 0s being slightly later then pins outputting 1s. There are systems that can
tolerate this delay of a valid output, but for some applications simultaneous output of a
binary content (mixed 0s and 1s) within a group of pins on a single GPIO port is required.
This can be accomplished by writing to the port’s IOPIN register.
Following code will preserve existing output on PORT0 pins P0.[31:16] and P0.[7:0] and
at the same time set P0.[15:8] to 0xA5, regardless of the previous value of pins P0.[15:8]:
IO0PIN = (IO0PIN && 0xFFFF00FF) || 0x0000A500
UM10114
Chapter 8: LPC2210/20 GPIO
The same outcome can be obtained using the fast port access.
Solution 1: using 32-bit (word) accessible fast GPIO registers
FIO0MASK = 0xFFFF00FF;
FIO0PIN = 0x0000A500;
Solution 2: using 16-bit (half-word) accessible fast GPIO registers
FIO0MASKL = 0x00FF;
FIO0PINL = 0xA500;
Solution 3: using 8-bit (byte) accessible fast GPIO registers
FIO0PIN1 = 0xA5;
5.3Writing to IOSET/IOCLR .vs. IOPIN
Write to the IOSET/IOCLR register allows easy change of the port’s selected output pin(s)
to high/low level at a time. Only pin/bit(s) in the IOSET/IOCLR written with 1 will be set to
high/low level, while those written as 0 will remain unaffected. However, by just writing to
either IOSET or IOCLR register it is not possible to instantaneously output arbitrary binary
data containing mixture of 0s and 1s on a GPIO port.
Write to the IOPIN register enables instantaneous output of a desired content on the
parallel GPIO. Binary data written into the IOPIN register will affect all output configured
pins of that parallel port: 0s in the IOPIN will produce low level pin outputs and 1s in IOPIN
will produce high level pin outputs. In order to change output of only a group of port’s pins,
application must logically AND readout from the IOPIN with mask containing 0s in bits
corresponding to pins that will be changed, and 1s for all others. Finally, this result has to
be logically ORred with the desired content and stored back into the IOPIN register.
Example 2 from above illustrates output of 0xA5 on PORT0 pins 15 to 8 while preserving
all other PORT0 output pins as they were before.
5.4Output signal frequency considerations when using the legacy and
enhanced GPIO registers
This section is related to LPC2210/01 and LPC2220 only.
The enhanced features of the fast GPIO ports available on this microcontroller make
GPIO pins more responsive to the code that has task of controlling them. In particular,
software access to a GPIO pin is 3.5 times faster via the fast GPIO registers than it is
when the legacy set of registers is used. As a result of the access speed increase, the
maximum output frequency of the digital pin is increased 3 .5 times, too. This tremendous
increase of the output frequency is not always that visible when a plain C code is used,
and a portion of an application handling the fast port output might have to be written in an
assembly code and executed in the ARM mode.
Here is a code where the pin control section is written in assembly language for ARM. It
illustrates the difference between the fast and slow GPIO port output capabilities. For the
best performances, compile this code in the ARM mode and execute from the on-chip
SRAM memory.
loop: bloop
UM10114
Chapter 8: LPC2210/20 GPIO
ldrr0,=0xe01fc1a0/*register address--enable fast port*/
movr1,#0x1
strr1,[r0] /*enable fast port0*/
ldrr1,=0xffffffff
ldrr0,=0x3fffc000 /*direction of fast port0*/
strr1,[r0]
ldrr0,=0xe0028018/*direction of slow port 1*/
strr1,[r0]
ldrr0,=0x3fffc018/*FIO0SET -- fast port0 register*/
ldrr1,=0x3fffc01c/*FIO0CLR0 -- fast port0 register*/
ldrr2,=0xC0010000/*select fast port 0.16 for toggle*/
ldrr3,=0xE0028014/*IO1SET -- slow port1 register*/
ldrr4,=0xE002801C/*IO1CLR -- slow port1 register*/
ldrr5,=0x00100000/*select slow port 1.20 for toggle*/
/*Generate 2 pulses on the fast port*/
strr2,[r0]
strr2,[r1]
strr2,[r0]
strr2,[r1]
/*Generate 2 pulses on the slow port*/
strr5,[r3]
strr5,[r4]
strr5,[r3]
strr5,[r4]
Figure 8–21 illustrates the code from above executed from the LPC2210/01 or LPC2220
on-chip SRAM. The PLL generated F
APBDIV = 1 (PCLK = CCLK).
• Register locations conform to ‘550 industry standard.
• Receiver FIFO trigger points at 1, 4, 8, and 14 bytes.
• Built-in fractional baud rate generator with autobauding capabilities.
• Mechanism that enables software and hardware flow control implementation.
Powerful Fractional baud rate generator with autobauding capabilities provides standard
baud rates such as 115200 with any crystal frequency above 2 MHz.
2.Pin description
Table 100: UART0 pin description
PinTypeDescription
RXD0InputSerial Input. Serial receive data.
TXD0OutputSerial Output. Serial transmit data.
3.Register description
UART0 contains register s organized as shown in Table 9–101. The Divisor Latch Access
Bit (DLAB) is contained in U0LCR[7] and enables access to the Diviso r Latches.
xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxx x x x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xx xx xxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx x x
xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx