LPC2378 PDF

UM10211
LPC23XX User manual

Rev. 4.1 — 5 September 2012 User manual
Document information
Info Content
Keywords LPC2300, LPC2361, LPC2362, LPC2364, LPC2365, LPC2366, LPC2367,
LPC2368, LPC2377, LPC2378, LPC2387, LPC2388, ARM, ARM7, 32-bit,
USB, Ethernet, CAN, I2S, Microcontroller
Abstract LPC23XX User manual revision
NXP Semiconductors UM10211
LPC23XX User manual
Revision history
Rev Date Description
4.1 20120905 LPC23XX User manual
Modifications:
• Corrected cross references throughout.
4 20120726 LPC23XX User manual
Modifications:
• Updated numbering for CAN interfaces: CAN1 uses SCC = 0, CAN2 uses SCC = 1.
See Section 12.14 “ID look-up table RAM” and Section 12.16 “Configuration and search
algorithm”.
• Registers CANWAKEFLAGS and CANSLEEPCLR added. See Table 220 “CAN Wake
and Sleep registers”.
• CCR register bit description updated. See Table 505 “Clock Control Register (CCR -
address 0xE002 4008) bit description”.
• Flash erase time corrected in Section 1.3 “Features”.
• Reset value of the SCS register changed to 0x8 in Table 31.
• Write restriction for RTC register appended in Section 26.8 “RTC usage notes”.
• ADC self-test pin set-up removed. See Table 520 “A/D pin description”.
• Update RTC usage notes: Do not ground VBAT. See Table 501 and Section 26.8.
• Description of Ethernet initialization updated in Section 11.9.
• Glitch filter constant for EINTx pins changed to 10 ns in Table 97 to Table 100.
• Editorial updates.
Modifications:
• Deep power-down mode functionality added (see Section 4–8 “Power control” and
Section 26–26.7 “RTC Usage Notes”).
• Register containing device revision added (implemented starting with revision D, see
Section 29–7.11).
• Part id for part LPC2387 updated (Table 29–542).
• XTAL1 input selection and PCB layout guidelines added (see Section 4–4.2).
• Editorial updates throughout the user manual.
• LPC2361 flash sectors added in Table 29–526.
• ISP1301 replaced by ISP1302 in Section 15–7.
• Fractional baud rate generator disabled in UART0/1/2/3 auto baud mode.
UM10211 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2012. All rights reserved.
User manual Rev. 4.1 — 5 September 2012 2 of 708

LPC23XX User manual
Revision history …continued

Rev Date Description
Modifications:
• Parts LPC2361 and LPC2362 added.
• Numerous editorial updates.
• AHB configuration registers AHBCFG1 and AHBCFG2 added.
• UARTs: minimum setting for DLL value updated.
1 20080311 LPC2364/65/66/67/68/77/78/87/88 User manual
Contact information
For more information, please visit: http://www.nxp.com
For sales office addresses, please send an email to: [email protected]

UM10211
Chapter 1: LPC23xx Introductory information
1.1 Introduction
LPC23xx series are ARM-based microcontrollers for applications requiring serial
communications for a variety of purposes. These microcontrollers typically incorporate a
10/100 Ethernet MAC, USB 2.0 Full Speed interface, four UARTs, two CAN channels, an
SPI interface, two Synchronous Serial Ports (SSP), three I2C interfaces, an I2S interface,
and a MiniBus (8-bit data/16-bit address parallel bus).
1.2 How to read this manual

The term “LPC23xx“ in the following text will be used as a generic name for all parts
covered in this user manual:
• LPC2361/62
• LPC2364/65/66/67/68
• LPC2377/78
• LPC2387
• LPC2388
Only when needed, a specific device name will be used to distinguish the part. See
Table 1 to find information about a particular part.
Table 1. LPC23xx overview

Part Features Ordering info Ordering options Block diagram
LPC2361/62 Section 1.3.1, Table 3 Table 4 Figure 1
Section 1.3.2
LPC2364/65/66/67/68 Section 1.3.1 Table 3 Table 5 Figure 2
LPC2377/78 Section 1.3.1, Table 3 Table 6 Figure 3
Section 1.3.3
LPC2387 Section 1.3.1, Table 3 Table 7 Figure 4
Section 1.3.4
LPC2388 Section 1.3.1, Table 3 Table 8 Figure 5
Section 1.3.4
1.3 Features
1.3.1 General features

• ARM7TDMI-S processor, running at up to 72 MHz.
• Up to 512 kB on-chip Flash Program Memory with In-System Programming (ISP) and
In-Application Programming (IAP) capabilities. Single Flash sector or full-chip erase in
100 ms. Flash program memory is on the ARM local bus for high performance CPU
access.
• Up to 64 kB of SRAM on the ARM local bus for high performance CPU access.

• 16 kB Static RAM for Ethernet interface. Can also be used as general purpose SRAM.
• 8 kB Static RAM for general purpose or USB interface.
• Dual AHB system that provides for simultaneous Ethernet DMA, USB DMA, and
program execution from on-chip flash with no contention between those functions. A
bus bridge allows the Ethernet DMA to access the other AHB subsystem.
• Advanced Vectored Interrupt Controller, supporting up to 32 vectored interrupts.
• General Purpose DMA controller (GPDMA) on AHB that can be used with the SSP
serial interfaces, the I2S port, and the SD/MMC card port, as well as for
memory-to-memory transfers.
• Serial Interfaces:
– Ethernet MAC with associated DMA controller. These functions reside on an
independent AHB bus.
– On LPC2364/66/68, LPC2378, LPC2387, LPC2388: USB 2.0 device controller
with on-chip PHY and associated DMA controller.
– On LPC2388: USB Host/OTG controller.
– Four UARTs with fractional baud rate generation, one with modem control I/O, one
with IrDA support, all with FIFO. These reside on the APB bus.
– SPI controller, residing on the APB bus.
– Two SSP controllers with FIFO and multi-protocol capabilities. One is an alternate
for the SPI port, sharing its interrupt. The SSP controllers can be used with the
GPDMA controller and reside on the APB bus.
– Three I2C interfaces reside on the APB bus. The second and third I2C interfaces
are expansion I2C interfaces with standard port pins rather than special open-drain
I2C pins.
– I2S (Inter-IC Sound) interface for digital audio input or output, residing on the APB
bus. The I2S interface can be used with the GPDMA.
– On LPC2364/66/68, LPC2378, LPC2387, LPC2388: Two CAN channels with
Acceptance Filter/FullCAN mode residing on the APB bus.
• Other APB Peripherals:
– On LPC2367/68, LPC2377/78, LPC2387, LPC2388: Secure Digital (SD) /
MultiMediaCard (MMC) memory card interface.
– Up to 70 (100 pin packages) or 104 (144 pin packages) general purpose I/O pins.
– 10 bit A/D converter with input multiplexing among 6 pins (100 pin packages) or 8
pins (144 pin packages).
– 10 bit D/A converter.
– Four general purpose timers with two capture inputs each and up to four compare
output pins each. Each timer block has an external count input.
– One PWM/Timer block with support for three-phase motor control. The PWM has
two external count inputs.
– Real-Time Clock (RTC) with separate power pin; clock source can be the RTC
oscillator or the APB clock.
– 2 kB Static RAM powered from the RTC power pin, allowing data to be stored
when the rest of the chip is powered off.

– Watchdog Timer. The watchdog timer can be clocked from the internal RC
oscillator, the RTC oscillator, or the APB clock.
• Standard ARM Test/Debug interface for compatibility with existing tools.
• Emulation Trace Module.
• Support for real-time trace.
• Single 3.3 V power supply (3.0 V to 3.6 V).
• Four reduced power modes: Idle, Sleep, Power-down, and Deep power-down modes.
• Four external interrupt inputs. In addition every PORT0/2 pin can be configured as an
edge sensing interrupt.
• Processor wake-up from Power-down mode via any interrupt able to operate during
Power-down mode (includes external interrupts, RTC interrupt, and Ethernet walk-up
interrupt).
• Two independent power domains allow fine tuning of power consumption based on
needed features.
• Brownout detect with separate thresholds for interrupt and forced reset.
• On-chip Power On Reset (POR).
• On-chip crystal oscillator with an operating range of 1 MHz to 24 MHz.
• 4 MHz internal RC oscillator that can optionally be used as the system clock. For USB
and CAN application, the use of an external clock source is suggested.
• On-chip PLL allows CPU operation up to the maximum CPU rate without the need for
a high-frequency crystal. May be run from the main oscillator, the internal RC
oscillator, or the RTC oscillator.
• Boundary scan for simplified board testing is available in LPC2364FET100,
LPC2368FET100 (TFBGA packages), LPC2377/78, and LPC2388.
• Versatile pin function selections allow more possibilities for using on-chip peripheral
functions.
1.3.2 Features available on LPC2361/62

• Device/Host/OTG controller available.
• No Ethernet on LPC2361.
1.3.3 Features available in LPC2377/78 and LPC2388

External memory controller that supports static devices such as Flash and SRAM. An 8-bit
data/16-bit address parallel bus is available.
1.3.4 Features available in LPC2387 and LPC2388

• 64 kB of SRAM on the ARM local bus for high performance CPU access.
• 16 kB Static RAM for USB interface. Can also be used as general purpose SRAM.
1.3.5 Overview
The following table shows the differences between LPC23xx parts. Features that are the
same for all parts are not included.

Table 2. LPC23xx features overview

Part Local Flash EMC USB/ USB USB Ethernet Ethernet CAN SD/ ADC GPIO
bus (kB) GP device host/ GP channels MMC channels pins
SRAM SRAM OTG SRAM
(kB) (kB) (kB)
LPC2361 8 64 no 8 yes yes no 16 2 no 6 70
LPC2362 32 128 no 8 yes yes yes 16 2 no 6 70
LPC2364 8 128 no 8 yes no yes 16 2 no 6 70
LPC2365 32 256 no 8 no no yes 16 - no 6 70
LPC2366 32 256 no 8 yes no yes 16 2 no 6 70
LPC2367 32 512 no 8 no no yes 16 - yes 6 70
LPC2368 32 512 no 8 yes no yes 16 2 yes 6 70
LPC2377 32 512 Mini 8 no no yes 16 - yes 8 104
LPC2378 32 512 Mini 8 yes no yes 16 2 yes 8 104
LPC2387 64 512 no 16 yes yes yes 16 2 yes 6 70
LPC2388 64 512 Mini 16 yes yes yes 16 2 yes 8 104
1.4 Applications
• Industrial control
• Medical systems
1.5 Ordering information and options

For ordering information for all LPC23xx parts, see Table 3. For ordering options, see
• Table 4 for LPC2361/62 parts.

• Table 5 for LPC2364/65/66/67/68 parts.
• Table 6 for LPC2377/78.
• Table 7 for LPC2387.
• Table 8 for LPC2388.
Table 3. LPC23xx ordering information

Type number Package
Name Description Version
LPC2361FBD100 LQFP100 plastic low profile quad flat package; 100 leads; body 14  14  1.4 mm SOT407-1
LPC2364FET100 TFBGA100 plastic thin fine-pitch ball grid array package; 100 balls; body 9  9  0.7 mm SOT926-1
LPC2368FET100 TFBGA100 plastic thin fine-pitch ball grid array package; 100 balls; body 9  9  0.7 mm SOT926-1

Table 3. LPC23xx ordering information …continued

Type number Package
Name Description Version
Table 4. LPC2361/62 Ordering options

Type number Flash SRAM (kB) Ethernet USB GP Channels Temp range
(kB) device + DMA CAN ADC DAC
Ethernet buffer
4 kB
FIFO
Local bus
GP/USB
Total
RTC
LPC2361FBD100 64 8 16[1] 8 2 34 - yes yes 2 6 1 40 C to +85 C

LPC2362FBD100 128 32 16 8 2 58 RMII yes yes 2 6 1 40 C to +85 C
[1] Available as general purpose SRAM for the LPC2361.
Table 5. LPC2364/65/66/67/68 Ordering options

Type number Flash SRAM (kB) Ether USB SD/ GP Channels Temp
(kB) Local Ethernet GP/ RTC Total net device MMC DMA CAN ADC DAC range
bus buffers USB + 4 kB
FIFO
LPC2364FBD100 128 8 16 8 2 34 RMII yes no yes 2 6 1 40 C
to
+85 C
LPC2364FET100 128 8 16 8 2 34 RMII yes no yes 2 6 1 40 C
to
+85 C
LPC2365FBD100 256 32 16 8 2 58 RMII no no yes - 6 1 40 C
to
+85 C
LPC2366FBD100 256 32 16 8 2 58 RMII yes no yes 2 6 1 40 C
to
+85 C
LPC2367FBD100 512 32 16 8 2 58 RMII no yes yes - 6 1 40 C
to
+85 C
LPC2368FBD100 512 32 16 8 2 58 RMII yes yes yes 2 6 1 40 C
to
+85 C
LPC2368FET100 512 32 16 8 2 58 RMII yes yes yes 2 6 1 40 C
to
+85 C

Table 6. LPC2377/78 ordering options

Type number Flash SRAM (kB) External bus Ether USB SD/ GP Temp
(kB) net device MMC DMA range
Ethernet buffer
CAN channels
ADC channels
DAC channels
+ 4 kB
FIFO
Local bus
GP/USB
Total
RTC
LPC2377FBD144 512 32 16 8 2 58 MiniBus: 8 data, 16 RMII no - yes yes 8 1 40 C to
address, and 2 chip +85 C
select lines
LPC2378FBD144 512 32 16 8 2 58 MiniBus: 8 data, 16 RMII yes 2 yes yes 8 1 40 C to
select lines
Table 7. LPC2387 ordering options

Type number Flash SRAM (kB) Ether USB SD/ GP Channels Temp
(kB) Local Ethernet GP/ RTC Total net device MMC DMA CAN ADC DAC range
bus buffers USB OTG
host +
4 kB
FIFO
LPC2387FBD100 512 64 16 16 2 98 RMII yes yes yes 2 6 1 40 C
to
+85 C
Table 8. LPC2388 ordering options

Type number Flash SRAM (kB) External bus Ether USB SD/ GP Temp
(kB) net device MMC DMA range
Ethernet buffer
CAN channels
ADC channels
DAC channels
host
OTG+
Local bus
4 kB
GP/USB
FIFO
Total
RTC
LPC2388FBD144 512 64 16 16 2 98 MiniBus: 8 data, 16 RMII yes 2 yes yes 8 1 40 C to

select lines
1.6 Architectural overview

The LPC2300 consists of an ARM7TDMI-S CPU with emulation support, the ARM7 Local
Bus for closely coupled, high speed access to the majority of on-chip memory, the AMBA
Advanced High-performance Bus (AHB) interfacing to high speed on-chip peripherals and
external memory, and the AMBA Advanced Peripheral Bus (APB) for connection to other
on-chip peripheral functions. The microcontroller permanently configures the
ARM7TDMI-S processor for little-endian byte order.
The microcontroller implements two AHB buses in order to allow the Ethernet block to
operate without interference caused by other system activity. The primary AHB, referred
to as AHB1, includes the Vectored Interrupt Controller, General Purpose DMA Controller,
External Memory Controller, USB interface, and 8/16 kB SRAM primarily intended for use
by the USB.

The second AHB, referred to as AHB2, includes only the Ethernet block and an
associated 16 kB SRAM. In addition, a bus bridge is provided that allows the secondary
AHB to be a bus master on AHB1, allowing expansion of Ethernet buffer space into
off-chip memory or unused space in memory residing on AHB1.
In summary, bus masters with access to AHB1 are the ARM7 itself, the USB block, the
General Purpose DMA function, and the Ethernet block (via the bus bridge from AHB2).
Bus masters with access to AHB2 are the ARM7 and the Ethernet block.
AHB peripherals are allocated a 2 MB range of addresses at the very top of the 4 GB
ARM memory space. Each AHB peripheral is allocated a 16 kB address space within the
AHB address space. Lower speed peripheral functions 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 MB range of addresses, beginning at the 3.5 GB address point. Each APB
peripheral is allocated a 16 kB address space within the APB address space.
1.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 parts of the processing 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 Data sheet that
can be found on official ARM web site.

1.8 On-chip flash memory system

The LPC2300 includes a Flash memory system with up to 512 kB. This memory may be
used for both code and data storage. Programming of the Flash memory may be
accomplished in several ways. It may be programmed In System via the serial port. The
application program may also erase and/or program the Flash while the application is
running, allowing a great degree of flexibility for data storage field firmware upgrades, etc.
The Flash is 128 bits wide and includes pre-fetching and buffering techniques to allow it to
operate at SRAM speeds.
1.9 On-chip Static RAM

The LPC2300 includes a static RAM memory up to 64 kB in size, that may be used for
code and/or data storage.
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. The data is only written to the SRAM when software does another
write. After a "warm" chip reset, the SRAM does not reflect the last write operation. 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 after a subsequent Reset.

1.10 Block diagram
XTAL1
TMS TDI trace signals XTAL2
VDDA
TRST TCK TDO RESET VDD(3V3)
EXTIN0
LPC2361/62 VREF
SYSTEM VSSA, VSS
P0, P1, P2, 8/32 kB 64/128 kB PLL
TRACE MODULE
TEST/DEBUG FUNCTIONS
P3, P4 FLASH VDD(DCDC)(3V3)
EMULATION
SRAM INTERFACE
system INTERNAL RC
HIGH-SPEED clock
GPI/O INTERNAL OSCILLATOR
ARM7TDMI-S
70 PINS CONTROLLERS
TOTAL SRAM FLASH
VECTORED
INTERRUPT
CONTROLLER
AHB2 AHB1
AHB AHB
BRIDGE BRIDGE
MASTER AHB TO SLAVE USB WITH

ETHERNET 8 kB VBUS
16 kB PORT AHB BRIDGE PORT 4 kB RAM
RMII(8) MAC WITH SRAM USB port 1
SRAM AND DMA
DMA(1)
AHB TO
APB BRIDGE GP DMA
CONTROLLER
EINT3 to EINT0 I2SRX_CLK
EXTERNAL INTERRUPTS
P0, P2 I2STX_CLK
I2SRX_WS
2 × CAP0/CAP1/ I2S INTERFACE I2STX_WS
CAPTURE/COMPARE
CAP2/CAP3 I2SRX_SDA
4 × MAT2, TIMER0/TIMER1/
TIMER2/TIMER3 I2STX_SDA
2 × MAT0/MAT1/
MAT3 SCK, SCK0
MOSI, MOSI0
6 × PWM1 PWM1 SPI, SSP0 INTERFACE MISO, MISO0
2 × PCAP1 SSEL, SSEL0
SCK1
LEGACY GPI/O MOSI1
P0, P1 SSP1 INTERFACE
52 PINS TOTAL MISO1
SSEL1
6 × AD0 A/D CONVERTER TXD0, TXD2, TXD3

UART0, UART2, UART3 RXD0, RXD2, RXD3
AOUT D/A CONVERTER TXD1

RXD1
UART1 DTR1, RTS1
VBAT 2 kB BATTERY RAM
DSR1, CTS1, DCD1,
power domain
power domain 22 RI1
RTCX1 REAL- RD1, RD2
RTC CAN1, CAN2
RTCX2 TIME TD1, TD2
OSCILLATOR
CLOCK
SCL0, SCL1, SCL2
I2C0, I2C1, I2C2 SDA0, SDA1, SDA2
WATCHDOG TIMER
SYSTEM CONTROL
002aad964
(1) LPC2362 only.

Fig 1. LPC2361/62 block diagram

XTAL1
VDDA
EXTIN0
LPC2364/65/66/67/68 VREF
128/256/ SYSTEM
P0, P1, P2, PLL VSSA, VSS
8/32 kB
TRACE MODULE
512 kB TEST/DEBUG FUNCTIONS
P3, P4 VDD(DCDC)(3V3)
EMULATION
SRAM FLASH INTERFACE
system INTERNAL RC
HIGH-SPEED clock
ARM7TDMI-S
70 PINS CONTROLLERS
TOTAL SRAM FLASH
VECTORED
INTERRUPT
CONTROLLER
AHB2 AHB1
AHB AHB
BRIDGE BRIDGE
VBUS
ETHERNET 8 kB USB_D+, USB_D−
RMII(8) MAC WITH SRAM USB_CONNECT
SRAM AND DMA(2)
DMA USB_UP_LED
AHB TO
APB BRIDGE GP DMA
CONTROLLER
EXTERNAL INTERRUPTS
P0, P2 I2STX_CLK
I2SRX_WS
CAPTURE/COMPARE
CAP2/CAP3 I2SRX_SDA
2 × MAT0/MAT1/
MAT3 SCK, SCK0
MOSI, MOSI0
SCK1
LEGACY GPI/O MOSI1
52 PINS TOTAL MISO1
SSEL1
6 × AD0 A/D CONVERTER MCICLK, MCIPWR

SD/MMC CARD
INTERFACE(1) MCICMD,
MCIDAT[3:0]
AOUT D/A CONVERTER
TXD0, TXD2, TXD3
power domain
domain 22 TXD1
power
RXD1
RTCX1 REAL- UART1 DTR1, RTS1
RTC
RTCX2 TIME
OSCILLATOR DSR1, CTS1, DCD1,
CLOCK
RI1
RD1, RD2
WATCHDOG TIMER CAN1, CAN2(2)
TD1, TD2
SCL0, SCL1, SCL2

SYSTEM CONTROL I2C0, I2C1, I2C2 SDA0, SDA1, SDA2
002aac566
(1) LPC2367/68 only.

(2) LPC2364/66/68 only.
Fig 2. LPC2364/65/66/67/68 block diagram

XTAL1
TMS TDI trace signals XTAL2 VDD(3V3)
TRST TCK TDO RESET VDDA

EXTIN0 DBGEN
VREF
LPC2377/78 SYSTEM
P0, P1, P2, 32 kB 512 kB PLL VSSA, VSS
TRACE MODULE
P3, P4 VDD(DCDC)(3V3)
EMULATION
SRAM FLASH INTERFACE
system INTERNAL RC
HIGH-SPEED clock
INTERNAL OSCILLATOR
GPI/O ARM7TDMI-S
104 PINS CONTROLLERS
TOTAL SRAM FLASH D[7:0]
VECTORED EXTERNAL
INTERRUPT MEMORY A[15:0]
CONTROLLER CONTROLLER OE, CS0, CS1,
BLS0
AHB2 AHB1
AHB AHB
BRIDGE BRIDGE
VBUS
16 kB MASTER AHB TO SLAVE USB WITH
ETHERNET 8 kB
4 kB RAM 2 × USB_D+/USB_D−
SRAM PORT AHB BRIDGE PORT
RMII(8) MAC WITH SRAM
AND DMA(1) 2 × USB_CONNECT
DMA 2 × USB_UP_LED
AHB TO
APB BRIDGE GP DMA
CONTROLLER

EXTERNAL INTERRUPTS
P0, P2 I2STX_CLK
I2SRX_WS
CAPTURE/COMPARE
CAP2/CAP3 TIMER0/TIMER1/ I2SRX_SDA
4 × MAT2, TIMER2/TIMER3 I2STX_SDA
2 × MAT0/MAT1/
MAT3 SCK, SCK0
MOSI, MOSI0
SCK1
LEGACY GPI/O MOSI1
56 PINS TOTAL MISO1
SSEL1

SD/MMC CARD
INTERFACE MCICMD,
MCIDAT[3:0]
AOUT D/A CONVERTER
TXD0, TXD2, TXD3
power domain 2 TXD1
RXD1
RTC
RTCX2 TIME
CLOCK
RI1
ALARM
RD1, RD2
CAN1, CAN2(1)
WATCHDOG TIMER TD1, TD2
SCL0, SCL1, SCL2

I2C0, I2C1, I2C2 SDA0, SDA1, SDA2
SYSTEM CONTROL
002aac574
(1) LPC2378 only.

Fig 3. LPC2377/78 block diagram

XTAL1
VDDA
EXTIN0
LPC2387 VREF
SYSTEM VSSA, VSS
P0, P1, P2, 64 kB 512 kB PLL
TRACE MODULE
EMULATION
SRAM INTERFACE
system INTERNAL RC
HIGH-SPEED clock
GPIO INTERNAL OSCILLATOR
ARM7TDMI-S
70 PINS CONTROLLERS
TOTAL SRAM FLASH
VECTORED
INTERRUPT
CONTROLLER
AHB2 AHB1
AHB AHB
BRIDGE BRIDGE

ETHERNET 16 kB VBUS
RMII(8) MAC WITH SRAM USB port 1
SRAM AND DMA
DMA
AHB TO
APB BRIDGE GP DMA
CONTROLLER
EXTERNAL INTERRUPTS
P0, P2 I2STX_CLK
I2SRX_WS
CAPTURE/COMPARE
CAP2/CAP3 I2SRX_SDA
2 × MAT0/MAT1/
MAT3 SCK, SCK0
MOSI, MOSI0
SCK1
LEGACY GPI/O MOSI1
52 PINS TOTAL MISO1
SSEL1

SD/MMC CARD
INTERFACE MCICMD,
MCIDAT[3:0]
AOUT D/A CONVERTER
TXD0, TXD2, TXD3
power domain
domain 22 TXD1
power
RXD1
RTC
RTCX2 TIME
CLOCK
RI1
WATCHDOG TIMER RD1, RD2

CAN1, CAN2
TD1, TD2
SCL0, SCL1, SCL2

002aad328
Fig 4. LPC2387 block diagram

XTAL1
VDDA
EXTIN0
LPC2388 VREF
SYSTEM VSSA, VSS
P0, P1, P2, 64 kB 512 kB PLL
TRACE MODULE
EMULATION
SRAM INTERFACE
system INTERNAL RC
HIGH-SPEED clock
ARM7TDMI-S
104 PINS CONTROLLERS
TOTAL SRAM FLASH D[7:0]
VECTORED EXTERNAL
INTERRUPT MEMORY A[15:0]
CONTROLLER CONTROLLER OE, CS0, CS1,
BLS0
AHB2 AHB1
AHB AHB
BRIDGE BRIDGE
USB WITH VBUS

ETHERNET MASTER AHB TO SLAVE 16 kB
16 kB PORT AHB BRIDGE PORT 4 kB RAM USB port 1
RMII(8) MAC WITH SRAM
SRAM AND DMA USB port 2
DMA
AHB TO
APB BRIDGE GP DMA
CONTROLLER
EXTERNAL INTERRUPTS
P0, P2 I2STX_CLK
I2SRX_WS
CAPTURE/COMPARE
CAP2/CAP3 I2SRX_SDA
2 × MAT0/MAT1/
MAT3 SCK, SCK0
MOSI, MOSI0
SCK1
LEGACY GPI/O MOSI1
56 PINS TOTAL MISO1
SSEL1

SD/MMC CARD
INTERFACE MCICMD,
MCIDAT[3:0]
AOUT D/A CONVERTER
TXD0, TXD2, TXD3
power domain
domain 22 TXD1
power
RXD1
RTC
RTCX2 TIME
CLOCK
ALARM RI1
RD1, RD2
WATCHDOG TIMER CAN1, CAN2
TD1, TD2
SCL0, SCL1, SCL2

002aad332
Fig 5. LPC2388 block diagram

UM10211
Chapter 2: LPC23XX Memory addressing
2.1 Memory map and peripheral addressing

ARM processors have a single 4 GB address space. The following table shows how this
space is used on NXP embedded ARM devices. For memory option details see Table 2.
Table 9. LPC2300 memory usage

Address range General use Address range details and description
0x0000 0000 to on-chip 0x0000 0000 - 0x0007 FFFF flash memory (up to 512 kB)
0x3FFF FFFF NV memory 0x3FFF C000 - 0x3FFF FFFF fast GPIO registers
and fast I/O
0x4000 0000 to on-chip RAM 0x4000 0000 - 0x4000 7FFF RAM (up to 32 kB)
0x7FFF FFFF 0x4000 0000 - 0x4000 FFFF RAM (64 kB for LPC2387/88)
0x7FD0 0000 - 0x7FD0 1FFF USB RAM (8 kB)
0x7FD0 0000 - 0x7FD0 3FFF USB RAM (16 kB for LPC2387/88)
0x7FE0 0000 - 0x7FE0 3FFF Ethernet RAM (16 kB)
0x8000 0000 to off-chip memory Two static memory banks, 64 KB each (LPC2377/78 and LPC2388 only):
0xDFFF FFFF 0x8000 0000 - 0x8000 FFFF static memory bank 0, 64 KB
0x8100 0000 - 0x8100 FFFF static memory bank 1, 64 KB
0xE000 0000 to APB peripherals 0xE000 0000 - 0xE008 FFFF 36 peripheral blocks, 16 kB each (some unused),
0xEFFF FFFF see Table 10.
0xE01F C000 - 0xE01F FFFF System Control Block
0xF000 0000 to AHB peripherals 0xFFE0 0000 - 0xFFE0 3FFF Ethernet Controller (not LPC2361)
0xFFFF FFFF 0xFFE0 4000 - 0xFFE0 7FFF General Purpose DMA Controller
0xFFE0 8000 - 0xFFE0 BFFF External Memory Controller (EMC) (LPC2377/78,
LPC2388 only)
0xFFE0 C000 - 0xFFE0 FFFF USB Controller (LPC2361/62/64/66/68, LPC2378,
LPC2387, and LPC2388 only).
0xFFFF F000 - 0xFFFF FFFF Vectored Interrupt Controller (VIC)
2.2 Memory maps

The LPC2300 incorporates several distinct memory regions, shown in the following
figures. Figure 7, Figure 8, and Figure 9 show the overall map of the entire address space
from the user program viewpoint following reset. The interrupt vector area supports
address remapping, which is described later in this section.

4.0 GB 0xFFFF FFFF

AHB PERIPHERALS
3.75 GB 0xF000 0000
APB PERIPHERALS
3.5 GB 0xE000 0000
3.0 GB 0xC000 0000
RESERVED ADDRESS SPACE
2.0 GB 0x8000 0000

BOOT ROM AND BOOT FLASH
(BOOT FLASH REMAPPED FROM ON-CHIP FLASH)

0x7FE0 3FFF
ETHERNET RAM (16 kB)
0x7FE0 0000
0x7FD0 1FFF
GENERAL PURPOSE OR USB RAM (8 KB)
0x7FD0 0000

0x4000 8000
0x4000 7FFF
32 kB LOCAL ON-CHIP STATIC RAM (LPC2362)
0x4000 2000
0x4000 1FFF
1.0 GB 0x4000 0000
RESERVED FOR ON-CHIP MEMORY
0x0002 0000
0x0001 FFFF
TOTAL OF 128 kB ON-CHIP NON-VOLATILE MEMORY (LPC2362)
0x0001 0000
0x0000 FFFF
0.0 GB 0x0000 0000
002aae283
Fig 6. LPC2461/63 memory map

4.0 GB 0xFFFF FFFF

AHB PERIPHERALS
3.75 GB 0xF000 0000
APB PERIPHERALS
3.5 GB 0xE000 0000
3.0 GB 0xC000 0000
2.0 GB 0x8000 0000


0x7FE0 3FFF
0x7FE0 0000
0x7FD0 1FFF
GENERAL PURPOSE OR USB RAM (8 KB)
0x7FD0 0000

0x4000 8000
0x4000 7FFF
32 kB LOCAL ON-CHIP STATIC RAM (LPC2365/66/67/68)
0x4000 2000
0x4000 1FFF
1.0 GB 0x4000 0000
0x0008 0000
0x0007 FFFF
TOTAL OF 512 kB ON-CHIP NON-VOLATILE MEMORY (LPC2367/68)
0x0004 0000
0x0003 FFFF
TOTAL OF 256 kB ON-CHIP NON-VOLATILE MEMORY (LPC2365/66)
0x0002 0000
0x0001 FFFF
0.0 GB 0x0000 0000
002aac577
Fig 7. LPC2364/65/66/67/68 system memory map

4.0 GB 0xFFFF FFFF

AHB PERIPHERALS
3.75 GB 0xF000 0000
APB PERIPHERALS
3.5 GB 0xE000 0000

3.0 GB 0xC000 0000
0x8100 FFFF
EXTERNAL MEMORY BANK 1 (64 kB)
0x8100 0000
0x8000 FFFF
2.0 GB 0x8000 0000

0x7FE0 3FFF
0x7FE0 0000
0x7FD0 1FFF
GENERAL PURPOSE OR USB RAM (8 kB)
0x7FD0 0000
0x4000 8000
0x4000 7FFF
32 kB LOCAL ON-CHIP STATIC RAM
1.0 GB 0x4000 0000
0x0008 0000
0x0007 FFFF
TOTAL OF 512 kB ON-CHIP NON-VOLATILE MEMORY
0.0 GB 0x0000 0000
002aac585
Fig 8. LPC2377/78 system memory map

4.0 GB 0xFFFF FFFF

AHB PERIPHERALS
3.75 GB 0xF000 0000
APB PERIPHERALS
3.5 GB 0xE000 0000
3.0 GB RESERVED ADDRESS SPACE 0xC000 0000
0x8100 FFFF
0x8100 0000
0x8000 FFFF
2.0 GB EXTERNAL MEMORY BANK 0 (64 kB)
0x8000 0000

0x7FE0 3FFF
0x7FE0 0000
0x7FD0 3FFF
USB RAM (16 kB)
0x7FD0 0000
0x4001 0000
0x4000 FFFF
1.0 GB 0x4000 0000
0x0008 0000
0x0007 FFFF
0.0 GB 0x0000 0000
002aad331
Fig 9. LPC2387 memory map

4.0 GB 0xFFFF FFFF

AHB PERIPHERALS
3.75 GB 0xF000 0000
APB PERIPHERALS
3.5 GB 0xE000 0000
3.0 GB RESERVED ADDRESS SPACE 0xC000 0000
0x8100 FFFF
0x8100 0000
0x8000 FFFF
2.0 GB EXTERNAL MEMORY BANK 0 (64 kB)
0x8000 0000

0x7FE0 3FFF
0x7FE0 0000
0x7FD0 3FFF
USB RAM (16 kB)
0x7FD0 0000
0x4001 0000
0x4000 FFFF
1.0 GB 0x4000 0000
0x0008 0000
0x0007 FFFF
0.0 GB 0x0000 0000
002aad331
Fig 10. LPC2388 memory map

4.0 GB
0xFFFF FFFF
AHB PERIPHERALS
4.0 GB - 2 MB 0xFFE0 0000

0xFFDF FFFF
RESERVED
3.75 GB 0xF000 0000

0xEFFF FFFF
RESERVED
3.5 GB + 2 MB 0xE020 0000

0xE01F FFFF
APB PERIPHERALS
3.5 GB 0xE000 0000
Fig 11. Peripheral memory map
Figure 12 and Table 10 show different views of the peripheral address space. Both the
AHB and APB peripheral areas are 2 megabyte spaces 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-word (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.
VECTORED INTERRUPT CONTROLLER 0xFFFF F000 (4G - 4K)
0xFFFF C000
(AHB PERIPHERAL #126)
0xFFFF 8000
0xFFE1 8000
NOT USED
(AHB PERIPHERAL #5)
0xFFE1 4000
NOT USED
(AHB PERIPHERAL #4)
0xFFE1 0000
USB CONTROLLER
(AHB PERIPHERAL #3)
0xFFE0 C000
EXTERNAL MEMORY CONTROLLER
(AHB PERIPHERAL #2)
0xFFE0 8000
GENERAL PURPOSE DMA CONTROLLER
(AHB PERIPHERAL #1)
0xFFE0 4000
ETHERNET CONTROLLER
(AHB PERIPHERAL #0)
0xFFE0 0000
Fig 12. AHB peripheral map

2.3 APB peripheral addresses

The following table shows the APB address map. No APB peripheral uses all of the 16 kB
space allocated to it. Typically each device’s registers are "aliased" or repeated at multiple
locations within each 16 kB range.
Table 10. APB peripherals and base addresses

APB Peripheral Base Address Peripheral Name
0 0xE000 0000 Watchdog Timer
1 0xE000 4000 Timer 0
2 0xE000 8000 Timer 1
3 0xE000 C000 UART0
4 0xE001 0000 UART1
5 0xE001 4000 Not used
6 0xE001 8000 PWM1
7 0xE001 C000 I2C0
8 0xE002 0000 SPI
9 0xE002 4000 RTC
10 0xE002 8000 GPIO
11 0xE002 C000 Pin Connect Block
12 0xE003 0000 SSP1
13 0xE003 4000 ADC
14 0xE003 8000 CAN Acceptance Filter RAM[1]
15 0xE003 C000 CAN Acceptance Filter Registers[1]
16 0xE004 0000 CAN Common Registers[1]
17 0xE004 4000 CAN Controller 1[1]
18 0xE004 8000 CAN Controller 2[1]
19 to 22 0xE004 C000 to 0xE005 8000 Not used
23 0xE005 C000 I2C1
24 0xE006 0000 Not used
25 0xE006 4000 Not used
26 0xE006 8000 SSP0
27 0xE006 C000 DAC
28 0xE007 0000 Timer 2
29 0xE007 4000 Timer 3
30 0xE007 8000 UART2
31 0xE007 C000 UART3
32 0xE008 0000 I2C2
33 0xE008 4000 Battery RAM
34 0xE008 8000 I2S
35 0xE008 C000 SD/MMC Card Interface[2]
36 to 126 0xE009 0000 to 0xE01F BFFF Not used
127 0xE01F C000 System Control Block
[1] CAN interface is available in LPC2364/66/68, LPC2378, LPC2387, and LPC2388.


[2] The SD/MMC card interface is available in LPC2365/66, LPC2377/78, LPC2387, and LPC2388.
2.4 LPC2300 memory re-mapping and boot ROM
2.4.1 Memory map concepts and operating modes

The basic concept on the LPC2300 is that each memory area has 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 11 below), a small portion of the
Boot ROM and SRAM spaces need to be re-mapped in order to allow alternative uses of
interrupts in the different operating modes described in Table 12. Re-mapping of the
interrupts is accomplished via the Memory Mapping Control feature (Section 2.5 “Memory
mapping control” on page 27).
Table 11. ARM exception vector locations

Address Exception
0x0000 0000 Reset
0x0000 0004 Undefined Instruction
0x0000 0008 Software Interrupt
0x0000 000C Prefetch Abort (instruction fetch memory fault)
0x0000 0010 Data Abort (data access memory fault)
0x0000 0014 Reserved
Note: Identified as reserved in ARM documentation, this location is used

by the Boot Loader as the Valid User Program key. This is described in
detail in Section 29.3.1.1 .
0x0000 0018 IRQ
0x0000 001C FIQ
Table 12. LPC2300 Memory mapping modes

Mode Activation Usage
Boot Hardware The Boot Loader always executes after any reset. The Boot ROM
Loader activation by interrupt vectors are mapped to the bottom of memory to allow
mode any Reset handling exceptions and using interrupts during the Boot Loading
process. A sector of the Flash memory (the Boot Flash) is available to
hold part of the Boot Code.

Table 12. LPC2300 Memory mapping modes

Mode Activation Usage
User Software Activated by the Boot Loader when a valid User Program Signature is
Flash activation by recognized in memory and Boot Loader operation is not forced.
mode boot code Interrupt vectors are not re-mapped and are found in the bottom of the
Flash memory.
User RAM Software Activated by a User Program as desired. Interrupt vectors are
mode activation by re-mapped to the bottom of the Static RAM.
user program
User Software Activated by a User Program as desired. Interrupt vectors are
External activation by re-mapped to external memory bank 0[1].
Memory user code
mode
[1] See EMCControl register address mirror bit in Table 60 for address of external memory bank 0.
2.4.2 Memory re-mapping

In order to allow for compatibility with future derivatives, the entire Boot ROM is mapped
to the top of the on-chip memory space. In this manner, the use of larger or smaller flash
modules will not require changing the location of the Boot ROM (which would require
changing the Boot Loader code itself) or changing the mapping of the Boot ROM interrupt
vectors. Memory spaces other than the interrupt vectors remain in fixed locations.
Figure 13 shows the on-chip memory mapping in the modes 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, that facilitates branching to interrupt handlers at distant physical addresses. The
remapped code locations overlay addresses 0x0000 0000 through 0x0000 003F. A typical
user program in the Flash memory can place the entire FIQ handler at address
0x0000 001C without any need to consider memory boundaries. The vector contained in
the SRAM, external memory, and Boot ROM must contain branches to the actual interrupt
handlers, or to other instructions that accomplish the branch to the interrupt handlers.
There are three reasons this configuration was chosen:
1. To give the FIQ handler in the Flash memory the advantage of not having to take a
memory boundary caused by the remapping into account.
2. Minimize the need to for the SRAM and Boot ROM vectors to deal with arbitrary
boundaries in the middle of code space.
3. To provide space to store constants for jumping beyond the range of single word
branch instructions.
Re-mapped memory areas, including the Boot ROM 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 2.5 “Memory mapping
control” on page 27.

2.5 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.
2.5.1 Memory Mapping Control Register (MEMMAP - 0xE01F C040)

Whenever an exception handling is necessary, microcontroller will fetch an instruction
residing on exception corresponding address as described in Table 11 “ARM exception
vector locations” on page 25. The MEMMAP register determines the source of data that
will fill this table.
Table 13. Memory mapping control registers

Name Description Access Reset Address
value
MEMMAP Memory mapping control. Selects whether the R/W 0x00 0xE01F C040
ARM interrupt vectors are read from the Boot
ROM, User Flash, or RAM.
Table 14. Memory Mapping control register (MEMMAP - address 0xE01F C040) bit
description
Bit Symbol Value Description Reset
value
1:0 MAP 00 Boot Loader Mode. Interrupt vectors are re-mapped to Boot ROM. 00
01 User Flash Mode. Interrupt vectors are not re-mapped and reside
in Flash.
10 User RAM Mode. Interrupt vectors are re-mapped to Static RAM.
11 User External Memory Mode (available on LPC2377/78 and
LPC2388 only).
Warning: Improper setting of this value may result in incorrect operation of
the device.
7:2 - - Reserved, user software should not write ones to reserved bits. NA
The value read from a reserved bit is not defined.
2.5.2 Memory mapping control usage notes

Memory Mapping Control simply selects one out of three available sources of data (sets of
64 bytes each) necessary for handling ARM exceptions (interrupts).
For example, whenever a Software Interrupt request is generated, ARM core will always
fetch 32 bit data "residing" on 0x0000 0008 see Table 11 “ARM exception vector
locations” on page 25. This means that when MEMMAP[1:0] = 10 (User RAM Mode),
read/fetch from 0x0000 0008 will provide data stored in 0x4000 0008. In case of
MEMMAP[1:0] = 00 (Boot Loader Mode), read/fetch from 0x0000 0008 will provide data
available also at 0x7FFF E008 (Boot ROM remapped from on-chip Bootloader).

2.0 GB EXTERNAL MEMORY INTERRUPT VECTORS 0x8000 0000

8 kB BOOT ROM 0x7FFF FFFF
2.0 GB - 8 kB (BOOT ROM INTERRUPT VECTORS) 0x7FFF E000

2.0 GB - 64 kB 8 kB BOOT FLASH 0x7FFE FFFF
(RE-MAPPED FROM TOP OF FLASH MEMORY)
2.0 GB - 72 kB 0x7FFE E000
upper limit depends on

specific part number
STATIC RAM
1.0 GB (SRAM INTERRUPT VECTORS) 0x4000 0000

0x3FFF FFFF
FAST GPIO REGISTERS
0x3FFF C000
0x3FFF BFFF
PARTCFG REGISTERS
0x3FFF 8000
upper limit depends on

BOOT FLASH specific part number
FLASH MEMORY
ACTIVE INTERRUPT VECTORS

0.0 GB (FROM FLASH, SRAM, BOOT ROM, OR EXT MEMORY) 0x0000 0000
Fig 13. Map of lower memory is showing re-mapped and re-mappable areas

2.6 Prefetch abort and data abort exceptions

The LPC2300 generates 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. For
the LPC2300, this is:
– Address space between On-Chip Non-Volatile Memory and the Special Register
space. Labelled "Reserved for On-Chip Memory" in Figure 7, Figure 8, and
Figure 9.
– Address space between On-Chip Static RAM and the Boot ROM. Labelled
"Reserved Address Space" in Figure 7, Figure 8, and Figure 9.
– External Memory
– Reserved regions of the AHB and APB spaces. See Figure 11.
• Unassigned AHB peripheral spaces. See Figure 12.
• Unassigned APB peripheral spaces. See Table 10.
For these areas, both attempted data access and instruction fetch generate an exception.
In addition, a Prefetch Abort exception is generated for any instruction fetch that maps to
an AHB or APB peripheral address, or to the Special Register space located just below
the SRAM at addresses 0x3FFF8000 through 0x3FFFFFFF.
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 LPC2300 documentation and are not a supported feature.
If software executes a write directly to the Flash memory, the MAM generates a data abort
exception. Flash programming must be accomplished using the specified Flash
programming interface provided by the Boot Code.
Note that 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.

UM10211
Chapter 3: LPC23XX System control block
3.1 Introduction
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:
• Reset
• Brown-Out detection
• External interrupt inputs
• Miscellaneous system controls and status
• Code security vs. debugging
Each type of function has its own registers 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
3.2 Pin description

Table 15 shows pins that are associated with System Control block functions.
Table 15. Pin summary

Pin name Pin Pin description
direction
EINT0 Input External Interrupt Input 0 - An active low/high level or
falling/rising edge general purpose interrupt input. This pin may be
used to wake up the processor from Idle or Power-down modes.
EINT1 Input External Interrupt Input 1 - See the EINT0 description above.
RESET Input External Reset input - A LOW on this pin resets the chip, causing
I/O ports and peripherals to take on their default states, and the
processor to begin execution at address 0x0000 0000.
3.3 Register description

All registers, regardless of size, are on word address boundaries. Details of the registers
appear in the description of each function.
Table 16. Summary of system control registers

value
External interrupts
EXTINT External Interrupt Flag Register R/W 0x00 0xE01F C140
EXTMODE External Interrupt Mode register R/W 0x00 0xE01F C148
EXTPOLAR External Interrupt Polarity Register R/W 0x00 0xE01F C14C


value
Reset
RSID Reset Source Identification Register R/W see text 0xE01F C180
AHB configuration registers
AHBCFG1 Configures the AHB1 arbiter. R/W 0x0000 0xE01F C188
0145
AHBCFG2 Configures the AHB2 arbiter. R/W 0x0000 0xE01F C18C
0145
Syscon miscellaneous registers
SCS System Control and Status R/W 0x08 0xE01F C1A0
3.4 Reset
Reset has four sources on the LPC2300: the RESET pin, the Watchdog Reset, Power On
Reset (POR) and the Brown Out Detection circuit (BOD). The RESET pin is a Schmitt
trigger input pin. Assertion of chip Reset by any source, once the operating voltage attains
a usable level, starts the Wake-up Timer (see description in Section 4.9 “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 Flash controller has
completed its initialization. The reset logic is shown in the following block diagram (see
Figure 14).

external Reset to the

C on-chip circuitry
reset
Q
watchdog
reset S Reset to
PCON.PD
POR
BOD
WAKEUP TIMER
START
power
down
COUNT 2 n C
internal RC Q
EINT0 wakeup oscillator S
EINT1 wakeup
write “1”
EINT2 wakeup
from APB
EINT3 wakeup
RTC wakeup reset
BOD wakeup
Ethernet MAC wakeup
APB read of
USB need_clk wakeup
PDBIT
CAN wakeup
in PCON
GPIO0 port wakeup
GPIO2 port wakeup
FOSC
to other
blocks
Fig 14. Reset block diagram including the wakeup timer
On the assertion of any of reset sources (POR, BOD reset, External reset and Watchdog
reset), the IRC starts up. After the IRC-start-up time (maximum of 60 s on power-up) and
after the IRC provides stable clock output, the reset signal is latched and synchronized on
the IRC clock. Then the following two sequences start simultaneously :
1. The 2-bit IRC wake-up timer starts counting when the synchronized reset is
de-asserted. The boot code in the ROM starts when the 2-bit IRC wake-up timer times
out. The boot code performs the boot tasks and may jump to the Flash. If the Flash is
not ready to access, the MAM will insert wait cycles until the Flash is ready.
2. The Flash wake-up-timer (9-bit) starts counting when the synchronized reset is
de-asserted. The Flash wake-up-timer generates the 100 s Flash start-up time.
Once it times out, the Flash initialization sequence is started, which takes about 250
cycles. When it’s done, the MAM will be granted access to the Flash.
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.
Figure 15 shows an example of the relationship between the RESET, the IRC, and the
processor status when the LPC2300 starts up after reset. See Section 4.4.2 “Main
oscillator” for start-up of the main oscillator if selected by the user code.

IRC status
RESET
VDD(3V3)
valid threshold
GND
30 μs
1 μs; IRC stability count
supply ramp-up boot time user code

time
8 μs 170 μs 160 μs
processor status
flash read flash read boot code

starts finishes execution
finishes;
user code starts
002aad482
Fig 15. Example of start-up after reset
The various Resets have some small differences. For example, a Power On Reset causes
the value of certain pins to be latched to configure the part.
For more details on Reset, PLL and startup/boot code interaction see Section 4.6.2 “PLL
and startup/boot code interaction”.
3.4.1 Reset Source Identification Register (RSIR - 0xE01F C180)

This register contains one bit for each source of Reset. Writing a 1 to any of these bits
clears the corresponding read-side bit to 0. The interactions among the four sources are
described below.
Table 17. Reset Source Identification register (RSID - address 0xE01F C180) bit description
Bit Symbol Description Reset
value
0 POR Assertion of the POR signal sets this bit, and clears all of the other bits in See text
this register. But if another Reset signal (e.g., External Reset) remains
asserted after the POR signal is negated, then its bit is set. This bit is not
affected by any of the other sources of Reset.
1 EXTR Assertion of the RESET signal sets this bit. This bit is cleared by POR, See text
but is not affected by WDT or BOD reset.

Table 17. Reset Source Identification register (RSID - address 0xE01F C180) bit description
value
2 WDTR This bit is set when the Watchdog Timer times out and the WDTRESET See text
bit in the Watchdog Mode Register is 1. It is cleared by any of the other
sources of Reset.
3 BODR This bit is set when the 3.3 V power reaches a level below 2.6 V. See text
If the VDD(DCDC)(3V3) voltage dips from 3.3 V to 2.5 V and backs up, the
BODR bit will be set to 1.
If the VDD(DCDC)(3V3) voltage dips from 3.3 V to 2.5 V and continues to
decline to the level at which POR is asserted (nominally 1 V), the BODR
bit is cleared.
if the VDD(DCDC)(3V3) voltage rises continuously from below 1 V to a level
above 2.6 V, the BODR will be set to 1.
This bit is not affected by External Reset nor Watchdog Reset.
Note: Only in case when a reset occurs and the POR = 0, the BODR bit
indicates if the VDD(DCDC)(3V3) voltage was below 2.6 V or not.
7:4 - Reserved, user software should not write ones to reserved bits. The NA
value read from a reserved bit is not defined.
3.5 Brown-out detection

The LPC2300 includes 2-stage monitoring of the voltage on the VDD(DCDC)(3V3) pins. If this
voltage falls below 2.95 V, the Brown-Out Detector (BOD) asserts an interrupt signal to
the Vectored Interrupt Controller. This signal can be enabled for interrupt in the Interrupt
Enable Register in the VIC (see Section 6.5.4 “Interrupt Enable Register (VICIntEnable -
0xFFFF F010)”) in order to cause a CPU interrupt; if not, software can monitor the signal
by reading the Raw Interrupt Status Register (see Section 6.5.3 “Raw Interrupt Status
Register (VICRawIntr - 0xFFFF F008)”).
The second stage of low-voltage detection asserts Reset to inactivate the LPC2300 when
the voltage on the VDD(DCDC)(3V3) pins falls below 2.65 V. This Reset prevents alteration of
the Flash as operation of the various elements of the chip would otherwise become
unreliable due to low voltage. The BOD circuit maintains this reset down below 1 V, at
which point the Power-On Reset circuitry maintains the overall Reset.
Both the 2.95 V and 2.65 V thresholds include some hysteresis. In normal operation, this
hysteresis allows the 2.95 V detection to reliably interrupt, or a regularly-executed event
loop to sense the condition.
But when Brown-Out Detection is enabled to bring the LPC2300 out of Power-Down mode
(which is itself not a guaranteed operation -- see Section 4.8.7 “Power Mode Control
register (PCON - 0xE01F C0C0)”), the supply voltage may recover from a transient before
the Wake-up Timer has completed its delay. In this case, the net result of the transient
BOD is that the part wakes up and continues operation after the instructions that set
Power-Down Mode, without any interrupt occurring and with the BOD bit in the RSID
being 0. Since all other wake-up conditions have latching flags (see Section 3.6.2
“External Interrupt flag register (EXTINT - 0xE01F C140)” and Section 26.7.2), a wake-up
of this type, without any apparent cause, can be assumed to be a Brown-Out that has
gone away.

3.6 External interrupt inputs

The LPC2300 includes four External Interrupt Inputs as selectable pin functions. In
addition, external interrupts have the ability to wake up the CPU from Power-down mode.
This is controlled by the register INTWAKE, which is described in the Clocking and Power
Control chapter under the Power Control heading
3.6.1 Register description

The external interrupt function has four registers associated with it. The EXTINT register
contains the interrupt flags. The EXTMODE and EXTPOLAR registers specify the level
and edge sensitivity parameters.
Table 18. External Interrupt registers

value[1]
EXTINT The External Interrupt Flag Register contains R/W 0x00 0xE01F C140
interrupt flags for EINT0, EINT1, EINT2 and
EINT3. See Table 19.
EXTMODE The External Interrupt Mode Register controls R/W 0x00 0xE01F C148
whether each pin is edge- or level-sensitive.
See Table 20.
EXTPOLAR The External Interrupt Polarity Register controls R/W 0x00 0xE01F C14C
which level or edge on each pin will cause an
interrupt. See Table 21.
[1] Reset Value reflects the data stored in used bits only. It does not include reserved bits content.
3.6.2 External 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 and EXTMODE registers) will set its interrupt flag 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 corresponding
bits. In level-sensitive mode the interrupt is cleared only when the pin is in its inactive
state.
Once a bit from EINT0 to EINT3 is set and an appropriate code starts to execute (handling
wake-up and/or external interrupt), this bit in EXTINT register must be cleared. Otherwise
event that was just triggered by activity on the EINT pin will not be recognized in future.
Important: whenever a change of external 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 3.6.3 “External Interrupt Mode register (EXTMODE - 0xE01F C148)” and
Section 3.6.4 “External Interrupt Polarity register (EXTPOLAR - 0xE01F C14C)”.
For example, if a system wakes up from power-down using low level on external interrupt
0 pin, its post-wake-up code must reset EINT0 bit in order to allow future entry into the
power-down mode. If EINT0 bit is left set to 1, subsequent attempts 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 19. External Interrupt Flag register (EXTINT - address 0xE01F C140) bit description
value
0 EINT0 In level-sensitive mode, this bit is set if the EINT0 function is selected for its 0
pin, and the pin is in 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.
This bit is cleared by writing a one to it, except in level sensitive mode when
the pin is in its active state.[1]
the pin.
the pin.
the pin.
7:4 - Reserved, user software should not write ones to reserved bits. The value NA
read from a reserved bit is not defined.
[1] Example: e.g. if the EINTx is selected to be low level sensitive and low level is present on
corresponding pin, this bit can not be cleared; this bit can be cleared only when signal on the
pin becomes high.
3.6.3 External Interrupt Mode register (EXTMODE - 0xE01F C148)

The bits in this register select whether each EINT pin is level- or edge-sensitive. Only pins
that are selected for the EINT function (see Section 9.5) and enabled in the VICIntEnable
register (Section 6.5.4 “Interrupt Enable Register (VICIntEnable - 0xFFFF F010)”) can
cause interrupts from the External Interrupt function (though of course pins selected for
other functions may cause interrupts from those functions).
Note: Software should only change a bit in this register when its interrupt is
disabled in VICIntEnable, and should write the corresponding 1 to EXTINT before
enabling (initializing) or re-enabling the interrupt. An extraneous interrupts could
be set by changing the mode and not having the EXTINT cleared.

Table 20. External Interrupt Mode register (EXTMODE - address 0xE01F C148) bit
description
value
0 EXTMODE0 0 Level-sensitivity is selected for EINT0. 0
1 EINT0 is edge sensitive.
7:4 - - Reserved, user software should not write ones to reserved NA
bits. The value read from a reserved bit is not defined.
3.6.4 External Interrupt Polarity register (EXTPOLAR - 0xE01F C14C)

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 Section 9.5)
and enabled in the VICIntEnable register (Section 6.5.4 “Interrupt Enable Register
(VICIntEnable - 0xFFFF F010)”) can cause interrupts from the External Interrupt function
(though of course pins selected for other functions may cause interrupts from those
functions).
Note: Software should only change a bit in this register when its interrupt is
disabled in VICIntEnable, and should write the corresponding 1 to EXTINT before
enabling (initializing) or re-enabling the interrupt. An extraneous interrupts could
be set by changing the polarity and not having the EXTINT cleared.
Table 21. External Interrupt Polarity register (EXTPOLAR - address 0xE01F C14C) bit
description
value
0 EXTPOLAR0 0 EINT0 is low-active or falling-edge sensitive (depending on 0
EXTMODE0).
1 EINT0 is high-active or rising-edge sensitive (depending on
EXTMODE0).
EXTMODE1).
EXTMODE1).
EXTMODE2).
EXTMODE2).

Table 21. External Interrupt Polarity register (EXTPOLAR - address 0xE01F C14C) bit
description
value
EXTMODE3).
EXTMODE3).
3.7 Other system controls and status flags

Some aspects of controlling LPC2300 operation that do not fit into peripheral or other
registers are grouped here.
3.7.1 AHB Configuration

The AHB configuration register allows changing AHB scheduling and arbitration
strategies.
Table 22. AHB configuration register map

Name Description Access Reset value Address
AHBCFG1 Configures the AHB1 arbiter. R/W 0x0000 0145 0xE01F C188
AHBCFG2 Configures the AHB2 arbiter. R/W 0x0000 0145 0xE01F C18C
3.7.1.1 AHB Arbiter Configuration register 1 (AHBCFG1 - 0xE01F C188)

By default, the AHB1 access is scheduled round-robin (bit 0 = 1). For round-robin
scheduling, the default priority sequence will be CPU, DMA, AHB1, and USB.
The AHB1 access priority can be configured as priority scheduling (bit 0 = 0) and priority
of the each of the AHB1 bus masters can be set by writing the priority value (highest
priority = 4, lowest priority = 1).
Masters with the same priority value are scheduled on a round-robin basis.
Table 23. AHB Arbiter Configuration register 1 (AHBCFG1 - address 0xE01F C188) bit
description
value
0 scheduler 0 Priority scheduling. 1
1 Uniform (round-robin) scheduling.
2:1 break_burst 00 Break all defined length bursts (the CPU does not create 10
defined bursts).
01 Break all defined length bursts greater than four-beat.
10 Break all defined length bursts greater than eight-beat.
11 Never break defined length bursts.
3 quantum_type 0 A quantum is an AHB clock. 0
1 A quantum is an AHB bus cycle.

Table 23. AHB Arbiter Configuration register 1 (AHBCFG1 - address 0xE01F C188) bit
description
value
7:4 quantum_size Controls the type of arbitration and the number of quanta 0100
before re-arbitration occurs.
0000 Preemptive, re-arbitrate after 1 AHB quantum.
0001 Preemptive, re-arbitrate after 2 AHB quanta.
1111 Non- preemptive, infinite AHB quanta.
10:8 default_master nnn[1] Master 1 (CPU) is the default master. 001
11 - - Reserved. -
14:12 EP1 nnn[1] External priority for master 1 (CPU). 000
15 - - Reserved. -
18:16 EP2 nnn[1] External priority for master 2 (GPDMA). 000
19 - - Reserved. -
22:20 EP3 nnn[1] External priority for master 3 (AHB1). 000
23 - - Reserved. -
26:24 EP4 nnn[1] External priority for master 4 (USB). 000
31:27 - - Reserved. -
[1] Allowed values for nnn are: 100 (highest priority), 011, 010, 001 (lowest priority).
3.7.1.1.1 Examples of AHB1 settings

The following examples use the LPC2378 to illustrate how to select the priority of each
AHB1 master based on different system requirements.
Table 24. Priority sequence (bit 0 = 0): CPU, GPDMA, AHB1, USB
Bit Symbol Description Priority value nnn Priority sequence
14:12 EP1 CPU 100 (4) 1
18:16 EP2 GPDMA 011 (3) 2
22:20 EP3 AHB1 010 (2) 3
26:24 EP4 USB 001 (1) 4

Table 25. Priority sequence (bit 0 = 0): USB, AHB1, CPU, GPDMA
14:12 EP1 CPU 010 (2) 3
18:16 EP2 GPDMA 001 (1) 4
22:20 EP3 AHB1 011 (3) 2
26:24 EP4 USB 100 (4) 1
Table 26. Priority sequence (bit 0 = 0): GPDMA, AHB1, CPU, USB
14:12 EP1 CPU 010 (2) 3
18:16 EP2 GPDMA 011 (3) 1[1]
22:20 EP3 AHB1 011 (3) 2[1]
26:24 EP4 USB 001 (1) 4
[1] Sequence based on round-robin.
Table 27. Priority sequence (bit 0 = 0): USB, AHB1, CPU, GPDMA
14:12 EP1 CPU 000 3[1]
18:16 EP2 GPDMA 000 4[1]
22:20 EP3 AHB1 010 (2) 1
26:24 EP4 USB 001 (1) 2
3.7.1.2 AHB Arbiter Configuration register 2 (AHBCFG2 - 0xE01F C18C)

By default, the AHB2 access is scheduled round-robin (bit 0 = 1). For round-robin
scheduling, the default priority sequence will be Ethernet and CPU.
The AHB2 access priority can be configured as priority scheduling (bit 0 = 0) and priority
of the each of the AHB2 bus masters can be set by writing the priority value (highest
priority = 2, lowest priority = 1).
Masters with the same priority value are scheduled on a round-robin basis.
Table 28. AHB Arbiter Configuration register 2 (AHBCFG2 - address 0xE01F C18C) bit
description
value
0 scheduler 0 Priority scheduling. 1
1 Uniform (round-robin) scheduling.
2:1 break_burst 00 Break all defined length bursts (the CPU does not create 10
defined bursts).
01 Break all defined length bursts greater than four-beat.
10 Break all defined length bursts greater than eight-beat.
11 Never break defined length bursts.
3 quantum_type 0 A quantum is an AHB clock. 0
1 A quantum is an AHB bus cycle.

Table 28. AHB Arbiter Configuration register 2 (AHBCFG2 - address 0xE01F C18C) bit
description
value
7:4 quantum_size Controls the type of arbitration and the number of quanta 0100
before re-arbitration occurs.
0000 Preemptive, re-arbitrate after 1 AHB quantum.
1111 Non- preemptive, infinite AHB quanta.
9:8 default_master nn Master 2 (Ethernet) is the default master. 01
11:10 - - Reserved. -
13:12 EP1 nn External priority for master 1 (CPU). 00
15:14 - - Reserved. -
17:16 EP2 nn External priority for master 2 (Ethernet). 00
31:18 - - Reserved. User software should not write ones to NA
reserved bits. The value read from a reserved bit is not
defined.
[1] Allowed values for nn are: 10 (high priority) and 01 (low priority).
3.7.1.2.1 Examples of AHB2 settings
Table 29. Priority sequence (bit 0 = 0): Ethernet, CPU

Bit Symbol Description Priority value nn Priority sequence
13:12 EP1 CPU 10 (2) 1
17:16 EP2 Ethernet 01 (1) 2
Table 30. Priority sequence (bit 0 = 0): Ethernet, CPU

Bit Symbol Description Priority value nn Priority sequence
13:12 EP1 CPU 00 2[1]
17:16 EP2 Ethernet 00 1[1]

3.7.2 System Controls and Status register (SCS - 0xE01F C1A0)

Remark: The EMC is available in LPC2377/78 and LPC2388 only. The SD/MMC is
available in LPC2365/66, LPC2377/78, LPC2387, and LPC2388. Bits are reserved when
the peripheral is not present.
Table 31. System Controls and Status register (SCS - address 0xE01F C1A0) bit description
Bit Symbol Value Description Access Reset
value
0 GPIOM GPIO access mode selection. R/W 0
0 GPIO ports 0 and 1 are accessed via APB addresses in a fashion
compatible with previous LPC2000 devices.
1 High speed GPIO is enabled on ports 0 and 1, accessed via addresses in
the on-chip memory range. This mode includes the port masking feature
described in the GPIO chapter.
1 EMC Reset External Memory Controller Reset Disable. R/W 0
Disable[1][2] 0 Both EMC resets are asserted when any type of reset event occurs. In this
mode, all registers and functions of the EMC are initialized upon any reset
condition.
1 Many portions of the EMC are only reset by a power-on or brown-out event,
in order to allow the EMC to retain its state through a warm reset (external
reset or watchdog reset). If the EMC is configured correctly, auto-refresh can
be maintained through a warm reset.
2 EMC Burst External Memory Controller Burst Control (implemented on device R/W 0
Control[2] revisions C and higher).
0 Burst enabled.
1 Burst disabled.
3 MCIPWR MCIPWR pin control. R/W 1
Active 0 The MCIPWR pin is low.
Level[1]
1 The MCIPWR pin is high.
4 OSCRANGE Main oscillator range select. R/W 0
0 The frequency range of the main oscillator is 1 MHz to 20 MHz.
1 The frequency range of the main oscillator is 15 MHz to 24 MHz.
5 OSCEN Main oscillator enable. R/W 0
0 The main oscillator is disabled.
1 The main oscillator is enabled, and will start up if the correct external
circuitry is connected to the XTAL1 and XTAL2 pins.
6 OSCSTAT Main oscillator status. RO 0
0 The main oscillator is not ready to be used as a clock source.
1 The main oscillator is ready to be used as a clock source. The main
oscillator must be enabled via the OSCEN bit.
31:7 - - Reserved. User software should not write ones to reserved bits. The value - NA
[1] The state of this bit is preserved through a software reset, and only a POR or a BOD event will reset it to its default value.
[2] EMC available on parts LPC2388 and LPC2378/77.

3.8 Code security vs. debugging

Applications in development typically need the debugging and tracing facilities in the
LPC2300. Later in the life cycle of an application, it may be more important to protect the
application code from observation by hostile or competitive eyes. The Code Read
Protection (CRP) feature of the LPC2300 allows an application to control whether it can
be debugged or protected from observation.
Details about Code Read Protection can be found in Section 29.6.

UM10211
Chapter 4: LPC23XX Clocking and power control
4.1 How to read this chapter

This chapter describes the clocking and power control features for all LPC23XX parts.
Note that the CAN1/2 block and the USB block are available on LPC2364/66/68,
LPC2378, LPC2387, and LPC2388 (not available on LPC2365 and LPC2377). The MCI
is available on LPC2367/68, LPC2377/78, LPC2387, and LPC2388. The Ethernet
controller is not available on the LPC3161. All corresponding bits and register settings for
not implemented peripherals are reserved.
4.2 Introduction
This chapter describes the generation of the various clocks needed by the LPC2300 and
options of clock source selection, as well as power control and wake-up from reduced
power modes. Functions described in the following subsections include:
• Oscillators
• Clock source selection
• PLL
• Clock dividers
• Power control
• Wake-up timer
Figure 16 shows how the clocks for different blocks and peripherals on the LPC23xx are
generated.

EXTERNAL
ETHERNET
PHY
usbclk
USB (48 MHz)
MAIN CLOCK USB BLOCK
OSCILLATOR DIVIDER 25 or
PLL USB clock config
pllclk 50 MHz
(USBCLKCFG)
CPU cclk
system ARM7
clock CLOCK
BYPASS TDMI-S
select DIVIDER
SYNCHRO-
(CLKSRCSEL) CPU clock config ETHERNET
NIZER
(CCLKCFG) BLOCK
INTERNAL
RC EMC, DMA,
WATCHDOG
OSCILLATOR FAST I/O
TIMER
VIC
WDT
clock CCLK/8
select CCLK/6
(WDTCLKSEL) PERIPHERAL other peripherals
CLOCK CCLK/4
see PCLKSEL0/1
GENERATOR CCLK/2
CCLK
pclkWDT CAN1
pclkCAN1
PCLK
SEL0[1:0]
RTC
pclkRTC PCLK PCONP[13]
PRESCALER SEL0[27:26]
rtclk PCONP[9] PCLK

RTC REAL-TIME SEL0[19:18]
OSCILLATOR CLOCK
MCI(1)
RTC pclkBAT_RAM
clock 2 kB BATTERY
select RAM pclkMCI
(CCR)
PCLK
SEL1[1:0]
PCLK PCONP[28]
SEL1[25:24]
SYSTEM
CTRL
pclkSYSCON
PCLK
SEL1[29:28]
(1) LPC2368, LPC2378, LPC2387, and LPC2388 only

Fig 16. Clock generation for the LPC2300


All registers, regardless of size, are on word address boundaries. Details of the registers
appear in the description of each function.

Name Description Access Reset value Address
Clock source selection
CLKSRCSEL Clock Source Select Register R/W 0 0xE01F C10C
Phase Locked Loop
PLLCON PLL Control Register R/W 0 0xE01F C080
PLLCFG PLL Configuration Register R/W 0 0xE01F C084
PLLSTAT PLL Status Register RO 0 0xE01F C088
PLLFEED PLL Feed Register WO NA 0xE01F C08C
Clock dividers
CCLKCFG CPU Clock Configuration Register R/W 0 0xE01F C104
USBCLKCFG USB Clock Configuration Register R/W 0 0xE01F C108
IRCTRIM IRC Trim Register R/W 0xA0 0xE01FC1A4
PCLKSEL0 Peripheral Clock Selection register 0. R/W 0 0xE01F C1A8
PCLKSEL1 Peripheral Clock Selection register 1. R/W 0 0xE01F C1AC
Power control
PCON Power Control Register R/W 0 0xE01F C0C0
INTWAKE Interrupt Wakeup Register R/W 0 0xE01F C144
PCONP Power Control for Peripherals Register R/W 0x03BE 0xE01F C0C4
4.4 Oscillators
The LPC2300 includes three independent oscillators. These are the Main Oscillator, the
Internal RC Oscillator, and the RTC oscillator. Each oscillator can be used for more than
one purpose as required in a particular application.
Following Reset, the LPC2300 will operate from the Internal RC Oscillator until switched
by software. This allows systems to operate without any external crystal, and allows the
Boot Loader code to operate at a known frequency. When Boot Block will branch to a user
program, there could be an option to activate the main oscillator prior to entering user
code.
4.4.1 Internal RC oscillator

The Internal RC Oscillator (IRC) may be used as the clock source for the watchdog timer,
and/or as the clock that drives the PLL and subsequently the CPU. The precision of the
IRC does not allow for use with the USB interface, which requires a much more precise
time base. Also, do not use the IRC for the CAN1/2 block if the CAN baud rate is higher
than 100 kbit/s. The nominal IRC frequency is 4 MHz.
Upon power up or any chip reset, the LPC2300 uses the IRC as the clock source.
Software may later switch to one of the other available clock sources.

4.4.2 Main oscillator

The main oscillator can be used as the clock source for the CPU, with or without using the
PLL. The main oscillator operates at frequencies of 1 MHz to 24 MHz. This frequency can
be boosted to a higher frequency, up to the maximum CPU operating frequency, by the
PLL. The oscillator output is called OSCCLK. The clock selected as the PLL input is
PLLCLKIN and the ARM processor clock frequency is referred to as CCLK for purposes of
rate equations, etc. elsewhere in this document. The frequencies of PLLCLKIN and CCLK
are the same value unless the PLL is active and connected. Refer to the PLL description
in this chapter for details.
The on-board oscillator in the LPC2300 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
(Cg in Figure 17, drawing a), with an amplitude of at least 200 mV(RMS). The XTAL2 pin
in this configuration can be left not connected.
External components and models used in oscillation mode are shown in Figure 17,
drawings b and c, and in Table 33 and Table 34. Since the feedback resistance is
integrated on chip, only a crystal and the capacitances CX1 and CX2 need to be connected
externally in case of fundamental mode oscillation (the fundamental frequency is
represented by L, CL and RS). Capacitance CP in Figure 17, drawing c, represents the
parallel package capacitance and should not be larger than 7 pF. Parameters FC, CL, RS
and CP are supplied by the crystal manufacturer.
LPC23xx LPC23xx
XTAL1 XTAL2 XTAL1 XTAL2
<=>
Ci Cg CL CP
Xtal
Clock CX1 CX2
RS
a) b) c)
Fig 17. Oscillator modes and models: a) slave mode of operation, b) oscillation mode of operation, c) external
crystal model used for CX1/X2 evaluation

Table 33. Recommended values for CX1/X2 in oscillation mode (crystal and external
components parameters) low frequency mode (OSCRANGE = 0, see Table 31)
Fundamental Crystal load Maximum crystal External load
oscillation frequency capacitance CL series resistance RS capacitors CX1, CX2
FOSC
1 MHz - 5 MHz 10 pF < 300  18 pF, 18 pF
20 pF < 300  39 pF, 39 pF
30 pF < 300  57 pF, 57 pF
5 MHz - 10 MHz 10 pF < 300  18 pF, 18 pF
20 pF < 200  39 pF, 39 pF
30 pF < 100  57 pF, 57 pF
10 MHz - 15 MHz 10 pF < 160  18 pF, 18 pF
20 pF < 60  39 pF, 39 pF
15 MHz - 20 MHz 10 pF < 80  18 pF, 18 pF
Table 34. Recommended values for CX1/X2 in oscillation mode (crystal and external
components parameters) high frequency mode (OSCRANGE = 1, see Table 31)
Fundamental Crystal load Maximum crystal External load
oscillation frequency capacitance CL series resistance RS capacitors CX1, CX2
FOSC
15 MHz - 20 MHz 10 pF < 180  18 pF, 18 pF
20 pF < 100  39 pF, 39 pF
20 MHz - 25 MHz 10 pF < 160  18 pF, 18 pF
20 pF < 80  39 pF, 39 pF
Since chip operation always begins using the Internal RC Oscillator, and the main
oscillator may never be used in some applications, it will only be started by software
request. This is accomplished by setting the OSCEN bit in the SCS register, as described
in Table 31. The main oscillator provides a status flag (the OSCSTAT bit in the SCS
register) so that software can determine when the oscillator is running and stable. At that
point, software can control switching to the main oscillator as a clock source. Prior to
starting the main oscillator, a frequency range must be selected by configuring the
OSCRANGE bit in the SCS register.
4.4.2.1 XTAL1 input

The input voltage to the on-chip oscillators is limited to 1.8 V. If the oscillator is driven by a
clock in slave mode, it is recommended that the input be coupled through a capacitor with
Ci = 100 pF. To limit the input voltage to the specified range, choose an additional
capacitor to ground Cg which attenuates the input voltage by a factor Ci/(Ci + Cg), see
Figure 17. In slave mode, a minimum of 200 mV(RMS) is needed.
4.4.2.2 Printed Circuit Board (PCB) layout guidelines

The crystal should be connected on the PCB as close as possible to the oscillator input
and output pins of the chip. Take care that the load capacitors Cx1 and Cx2, and Cx3 in
case of third overtone crystal usage, have a common ground plane. The external
components must also be connected to the ground plain. Loops must be made as small
as possible, in order to keep the noise coupled in via the PCB as small as possible. Also
parasitics should stay as small as possible. Values of Cx1 and Cx2 should be chosen
smaller accordingly to the increase in parasitics of the PCB layout.

4.4.3 RTC oscillator

The RTC oscillator can be used as the clock source for the RTC, and/or the watchdog
timer. The RTC oscillator can also be used to drive the PLL and the CPU.
4.5 Clock source selection multiplexer

Several clock sources may be chosen to drive the PLL and ultimately the CPU and
on-chip peripheral devices. The clock sources available are the main oscillator, the RTC
oscillator, and the Internal RC oscillator.
The clock source selection can only be changed safely when the PLL is not connected.
For a detailed description of how to change the clock source in a system using the PLL
see Section 4.6.14 “PLL setup sequence”.
Note the following restrictions regarding the choice of clock sources:
• The IRC oscillator cannot be used as clock source for the USB block.
• The IRC oscillator cannot be used as clock source for the CAN controllers if the CAN
baud rate is larger than 100 kbit/s.
4.5.1 Clock Source Select register (CLKSRCSEL - 0xE01F C10C)

The PCLKSRCSEL register contains the bits that select the clock source for the PLL.
Table 35. Clock Source Select register (CLKSRCSEL - address 0xE01F C10C) bit
description
value
1:0 CLKSRC Selects the clock source for the PLL as follows: 0
00 Selects the Internal RC oscillator as the PLL clock source
(default).
01 Selects the main oscillator as the PLL clock source.
10 Selects the RTC oscillator as the PLL clock source.
11 Reserved, user software should not write ones to reserved bits.
Warning: Improper setting of this value, or an incorrect sequence of
changing this value may result in incorrect operation of the device.
7:2 - 0 Unused, always 0. 0
4.6 PLL (Phase Locked Loop)

The PLL accepts an input clock frequency in the range of 32 kHz to 25 MHz . The input
frequency is multiplied up to a high frequency, then divided down to provide the actual
clock used by the CPU and the USB block.

4.6.1 PLL operation

The PLL input, in the range of 32 kHz to 25 MHz, may initially be divided down by a value
"N", which may be in the range of 1 to 256. This input division provides a greater number
of possibilities in providing a wide range of output frequencies from the same input
frequency.
Following the PLL input divider is the PLL multiplier. This can multiply the input divider
output through the use of a Current Controlled Oscillator (CCO) by a value "M", in the
range of 1 through 32768. The resulting frequency must be in the range of 275 MHz to
550 MHz. The multiplier works by dividing the CCO output by the value of M, then using a
phase-frequency detector to compare the divided CCO output to the multiplier input. The
error value is used to adjust the CCO frequency.
There are additional dividers at the PLL output to bring the frequency down to what is
needed for the CPU, USB, and other peripherals. The PLL output dividers are described
in the Clock Dividers section following the PLL description. A block diagram of the PLL is
shown in Figure 18
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, could be dependent on the PLL if so
configured (for example when it is providing the chip clock), accidental changes to the PLL
setup could result in unexpected or fatal 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 by entering Power-down
mode. PLL is enabled by software only.
It is important that the setup procedure described in Section 4.6.14 “PLL setup sequence”
is followed as is or the PLL might not operate at all!.
4.6.2 PLL and startup/boot code interaction

The boot code for the LPC2300 is a little different from those for the previous NXP ARM7
LPC2000 chips. When there's no valid code (determined by the checksum word) in the
user flash or the ISP enable pin (P2.10) is pulled low on startup, the ISP mode will be
entered and the boot code will setup the PLL with the IRC. Therefore it can not be
assumed that the PLL is disabled when the user opens a debug session to debug the
application code. The user startup code must follow the steps described in this chapter to
disconnect the PLL.
The boot code may also change the values for some registers when the chip enters ISP
mode. For example, the GPIOM bit in the SCS register is set in the ISP mode. If the user
doesn't notice it and clears the GPIOM bit in the application code, the application code will
not be able to operate with the traditional GPIO function on PORT0 and PORT1.

The PLL is controlled by the registers shown in Table 36. More detailed descriptions
follow. Writes to any unused bits are ignored. A read of any unused bits will return a logic
zero.

Warning: Improper setting of PLL values may result in incorrect operation of the
device!
Table 36. PLL registers

value[1]
PLLCON PLL Control Register. Holding register for R/W 0 0xE01F C080
updating PLL control bits. Values written to this
register do not take effect until a valid PLL feed
sequence has taken place.
PLLCFG PLL Configuration Register. Holding register for R/W 0 0xE01F C084
updating PLL configuration values. Values
written to this register do not take effect until a
valid PLL feed sequence has taken place.
PLLSTAT PLL Status Register. Read-back register for RO 0 0xE01F C088
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 PLL status.
PLLFEED PLL Feed Register. This register enables WO NA 0xE01F C08C
loading of the PLL control and configuration
information from the PLLCON and PLLCFG
registers into the shadow registers that actually
affect PLL operation.
USBSEL[3:0]
PLLC
PLLE
USB
PLOCK CLOCK
pd refclk = DIVIDER usbclk =
1.152 MHz pllclk = /6 48 MHz
pllclkin = 288 288 MHz
PHASE- MHz
18.432 MHz CPU
N-DIVIDER FREQUENCY FILTER CCO cclk =
/16 DETECTOR CLOCK
72 MHz
DIVIDER
NSEL[23:16] 1.152 MHz 144 MHz 288 MHz /4
M-DIVIDER /2
/125
MSEL[14:0]
CCLKSEL[7:0]
Fig 18. PLL block diagram (N = 16, M = 125, USBSEL = 6, CCLKSEL = 4)
4.6.4 PLL Control register (PLLCON - 0xE01F C080)

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.6.9 “PLL Feed register (PLLFEED -
0xE01F C08C)”).

Table 37. PLL Control register (PLLCON - address 0xE01F C080) bit description
value
0 PLLE PLL Enable. When one, and after a valid PLL feed, this bit will 0
activate the PLL and allow it to lock to the requested frequency. See
PLLSTAT register, Table 40.
1 PLLC PLL Connect. Having both PLLC and PLLE set to one followed by a 0
valid PLL feed sequence, the PLL becomes the clock source for the
CPU, as well as the USB subsystem and. Otherwise, the clock
selected by the Clock Source Selection Multiplexer is used directly
by the LPC2300. See PLLSTAT register, Table 40.
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 generated.
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.
4.6.5 PLL Configuration register (PLLCFG - 0xE01F C084)

The PLLCFG register contains the PLL multiplier and divider values. Changes to the
PLLCFG register do not take effect until a correct PLL feed sequence has been given (see
Section 4.6.9 “PLL Feed register (PLLFEED - 0xE01F C08C)”). Calculations for the PLL
frequency, and multiplier and divider values are found in the Section 4.6.11 “PLL
frequency calculation”.
Table 38. PLL Configuration register (PLLCFG - address 0xE01F C084) bit description
value
14:0 MSEL PLL Multiplier value. Supplies the value "M" in the PLL frequency 0
calculations. The value stored here is M - 1. Supported values for M
are 6 through 512 and those listed in Table 39
Note: Not all values of M are needed, and therefore some are not
supported by hardware. For details on selecting values for MSEL see
Section 4.6.11 “PLL frequency calculation”.
15 - Reserved, user software should not write ones to reserved bits. The NA
23:16 NSEL PLL Pre-Divider value. Supplies the value "N" in the PLL frequency 0
calculations. Supported values for N are 1 through 32.
Note: For details on selecting the right value for NSEL see
Section 4.6.11 “PLL frequency calculation”.

Table 39. Multiplier values for 32 kHz oscillator

Multiplier (M) Pre-divide (N) FCCO
4272 1 279.9698
4395 1 288.0307
4578 1 300.0238
4725 1 309.6576
4807 1 315.0316
5127 1 336.0031
5188 1 340.0008
5400 1 353.8944
5493 1 359.9892
5859 1 383.9754
6042 1 395.9685
6075 1 398.1312
6104 1 400.0317
6409 1 420.0202
6592 1 432.0133
6750 1 442.3680
6836 1 448.0041
6866 1 449.9702
6958 1 455.9995
7050 1 462.0288
7324 1 479.9857
7425 1 486.6048
7690 1 503.9718
7813 1 512.0328
7935 1 520.0282
8057 1 528.0236
8100 1 530.8416
8545 2 280.0026
8789 2 287.9980
9155 2 299.9910
9613 2 314.9988
10254 2 336.0031
10376 2 340.0008
10986 2 359.9892
11719 2 384.0082
12085 2 396.0013
12207 2 399.9990
12817 2 419.9875
12817 3 279.9916
13184 2 432.0133
13184 3 288.0089

Table 39. Multiplier values for 32 kHz oscillator

Multiplier (M) Pre-divide (N) FCCO
13672 2 448.0041
13733 2 450.0029
13733 3 300.0020
13916 2 455.9995
14099 2 461.9960
14420 3 315.0097
14648 2 479.9857
15381 2 504.0046
15381 3 336.0031
15564 3 340.0008
15625 2 512.0000
15869 2 519.9954
16113 2 527.9908
16479 3 359.9892
17578 3 383.9973
18127 3 395.9904
18311 3 400.0099
19226 3 419.9984
19775 3 431.9915
20508 3 448.0041
20599 3 449.9920
20874 3 455.9995
21149 3 462.0070
21973 3 480.0075
23071 3 503.9937
23438 3 512.0109
23804 3 520.0063
24170 3 528.0017
4.6.6 PLL Status register (PLLSTAT - 0xE01F C088)

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 disagree 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.6.9 “PLL Feed register (PLLFEED -
0xE01F C08C)”).

Table 40. PLL Status register (PLLSTAT - address 0xE01F C088) bit description
value
14:0 MSEL Read-back for the PLL Multiplier value. This is the value currently 0
used by the PLL, and is one less than the actual multiplier.
23:16 NSEL Read-back for the PLL Pre-Divider value. This is the value currently 0
used by the PLL, and is one less than the actual divider.
24 PLLE Read-back for the PLL Enable bit. When one, the PLL is currently 0
activated. When zero, the PLL is turned off. This bit is automatically
cleared when Power-down mode is activated.
25 PLLC Read-back for the PLL Connect bit. When PLLC and PLLE are both 0
one, the PLL is connected as the clock source for the LPC2300.
When either PLLC or PLLE is zero, the PLL is bypassed. This bit is
automatically cleared when Power-down mode is activated.
26 PLOCK Reflects the PLL Lock status. When zero, the PLL is not locked. 0
When one, the PLL is locked onto the requested frequency. See
text for details.
4.6.7 PLL Interrupt: PLOCK

The PLOCK bit in the PLLSTAT register reflects the lock status of the PLL. When the PLL
is enabled, or parameters are changed, the PLL requires some time to establish lock
under the new conditions. PLOCK can be monitored to determine when the PLL may be
connected for use. The value of PLOCK may not be stable when the PLL reference
frequency (FREF, the frequency of REFCLK, which is equal to the PLL input frequency
divided by the pre-divider value) is less than 100 kHz or greater than 20 MHz. In these
cases, the PLL may be assumed to be stable after a start-up time has passed. This time is
500 s when FREF is greater than 400 kHz and 200 / FREF seconds when FREF is less
than 400 kHz
PLOCK is connected to the interrupt controller. This allows for software to turn on the PLL
and continue with other functions without having to wait for the PLL to achieve lock. When
the interrupt occurs, the PLL may be connected, and the interrupt disabled.
4.6.8 PLL Modes

The combinations of PLLE and PLLC are shown in Table 41.
Table 41. PLL control bit combinations

PLLC PLLE PLL Function
0 0 PLL is turned off and disconnected. The PLL outputs the unmodified clock
input.
0 1 The PLL is active, but not yet connected. The PLL can be connected after
PLOCK is asserted.
1 0 Same as 00 combination. This prevents the possibility of the PLL being
connected without also being enabled.
1 1 The PLL is active and has been connected as the system clock source.

4.6.9 PLL 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:
1. Write the value 0xAA to PLLFEED.

2. Write the value 0x55 to PLLFEED.
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.
Table 42. PLL Feed register (PLLFEED - address 0xE01F C08C) bit description
value
7:0 PLLFEED The PLL feed sequence must be written to this register in order for 0x00
PLL configuration and control register changes to take effect.
4.6.10 PLL and Power-down mode

Power-down mode automatically turns off and disconnects the PLL. Wake-up from
Power-down mode does not automatically restore the PLL settings, this must be done in
software. Typically, 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 wake-up. It is important not to attempt to restart the PLL by simply feeding it when
execution resumes after a wake-up from Power-down mode. This would enable and
connect the PLL at the same time, before PLL lock is established.
4.6.11 PLL frequency calculation

The PLL equations use the following parameters:
Table 43. PLL frequency parameter

Parameter Description
FIN the frequency of PLLCLKIN from the Clock Source Selection Multiplexer.
FCCO the frequency of the SYSCLK (output of the PLL Current Controlled Oscillator)
N PLL Pre-divider value from the NSEL bits in the PLLCFG register (PLLCFG
NSEL field + 1). N is an integer from 1 through 32.
M PLL Multiplier value from the MSEL bits in the PLLCFG register (PLLCFG
MSEL field + 1). Not all potential values are supported. See below.
FREF PLL internal reference frequency, FIN divided by N.
The PLL output frequency (when the PLL is both active and connected) is given by:
FCCO = (2  M FIN) / N
The PLL inputs and settings must meet the following:
• FIN is in the range of 32 kHz to 50 MHz.

• FCCO is in the range of 275 MHz to 550 MHz.

The PLL equation can be solved for other PLL parameters:
M = (FCCO  N) / (2  FIN)
N = (2  M  FIN) / FCCO
FIN = (FCCO  N) / (2  M)
Allowed values for M:
At higher oscillator frequencies, in the MHz range, values of M from 6 through 512 are
allowed. This supports the entire useful range of both the main oscillator and the IRC.
For lower frequencies, specifically when the RTC is used to clock the PLL, a set of 65
additional M values have been selected for supporting baud rate generation, CAN/USB
operation, and attaining even MHz frequencies. These values are shown in Table 44
Table 44. Additional Multiplier Values for use with a Low Frequency Clock Input
Low Frequency PLL Multipliers
4272 4395 4578 4725 4807
5127 5188 5400 5493 5859
6042 6075 6104 6409 6592
6750 6836 6866 6958 7050
7324 7425 7690 7813 7935
8057 8100 8545 8789 9155
9613 10254 10376 10986 11719
12085 12207 12817 13184 13672
13733 13916 14099 14420 14648
15381 15564 15625 15869 16113
16479 17578 18127 18311 19226
19775 20508 20599 20874 21149
21973 23071 23438 23804 24170
4.6.12 Procedure for determining PLL settings

PLL parameter determination can be simplified by using a spreadsheet available from
NXP. To determine PLL parameters by hand, the following general procedure may be
used:
1. Determine if the application requires use of the USB interface. The USB requires a
50% duty cycle clock of 48 MHz within a very small tolerance, which means that FCCO
must be an even integer multiple of 48 MHz (i.e. an integer multiple of 96 MHz), within
a very small tolerance.
2. 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
frequency than that of the processor (see Section 4.7 “Clock dividers” on page 60 and
Section 4.8 “Power control” on page 63). Find a value for FCCO that is close to a
multiple of the desired CCLK frequency, bearing in mind the requirement for USB
support in [1] above, and that lower values of FCCO result in lower power dissipation.

3. Choose a value for the PLL input frequency (FIN). This can be a clock obtained from
the main oscillator, the RTC oscillator, or the on-chip RC oscillator. For USB support,
the main oscillator should be used.
4. Calculate values for M and N to produce a sufficiently accurate FCCO frequency. The
desired M value -1 will be written to the MSEL field in PLLCFG. The desired N value -1
will be written to the NSEL field in PLLCFG.
In general, it is better to use a smaller value for N, to reduce the level of multiplication that
must be accomplished by the CCO. Due to the difficulty in finding the best values in some
cases, it is recommended to use a spreadsheet or similar method to show many
possibilities at once, from which an overall best choice may be selected. A spreadsheet is
available from NXP for this purpose.
4.6.13 Examples of PLL settings

The following examples illustrate selecting PLL values based on different system
requirements.
Example 1)
Assumptions:
• The USB interface will be used in the application. The lowest integer multiple of
96 MHz that falls within the PLL operating range (288 MHz) will be targeted.
• The desired CPU rate = 60 MHz.
• An external 4 MHz crystal or clock source will be used as the system clock source.
Calculations:
M = (FCCO  N) / (2  FIN)
Start by assuming N = 1, since this produces the smallest multiplier needed for the PLL.
So, M = 288  106 / (2  4  106) = 36. Since the result is an integer, there is no need to
look further for a good set of PLL configuration values. The value written to PLLCFG
would be 0x23 (N - 1 = 0; M - 1 = 35 = 0x23).
The potential CPU clock rate can be determined by dividing FCCO by the desired CPU
frequency: 288  106 / 60  106 = 4.8. The nearest integer value for the CPU Clock
Divider is then 5, giving us 57.6 MHz as the nearest value to the desired CPU clock rate.
If it is important to obtain exactly 60 MHz, an FCCO rate must be found that can be divided
down to both 48 MHz and 60 MHz. The only possibility is 480 MHz. Divided by 10, this
gives the 48 MHz with a 50% duty cycle needed by the USB block. Divided by 8, it gives
60 MHz for the CPU clock. PLL settings for 480 MHz are N = 1 and M = 60.
Example 2)
Assumptions:
• The USB interface will not be used in the application.

• The desired CPU rate = 72 MHz
• The 32.768 kHz RTC clock source will be used as the system clock source
Calculations:

M = (FCCO  N) / (2  FIN)
The smallest frequency for FCCO that can produce our desired CPU clock rate and is
within the PLL operating range is 288 MHz (4  72 MHz). Start by assuming N = 1, since
this produces the smallest multiplier needed for the PLL.
So, M = 288  106 / (2  32,768) = 4,394.53125. This is not an integer, so the CPU
frequency will not be exactly 288 MHz with this setting. Since this case is less obvious, it
may be useful to make a table of possibilities for different values of N (see Table 45).
Table 45. Potential values for PLL example

N M M Rounded FREF (Hz) FCCO (Hz) Actual % Error
CCLK (Hz)
1 4394.53125 4395 32768 288.0307 72.0077 0.0107
2 8789.0625 8789 16384 287.9980 71.9995 -0.0007
3 13183.59375 13184 10922.67 288.0089 72.0022 0.0031
4 17578.125 17578 8192 287.9980 71.9995 -0.0007
5 21972.65625 21973 6553.6 288.0045 72.0011 0.0016
Beyond N = 7, the value of M is out of range or not supported, so the table stops there. In
the table, the calculated M value is rounded to the nearest integer. If this results in CCLK
being above the maximum operating frequency (72 MHz), it is allowed if it is not more than
½% above the maximum frequency.
In general, larger values of FREF result in a more stable PLL when the input clock is a low
frequency. Even the first table entry shows a very small error of just over 1 hundredth of a
percent, or 107 parts per million (ppm). If that is not accurate enough in the application,
the second case gives a much smaller error of 7 ppm.
Remember that when a frequency below about 1 MHz is used as the PLL clock source,
not all multiplier values are available. As it turns out, all of the rounded M values found in
Table 45 of this example are supported, as may be confirmed in Table 44.
If PLL calculations suggest use of unsupported multiplier values, those values must be
disregarded and other values examined to find the best fit. Multiplier values one count off
from calculated values may also be good possibilities.
The value written to PLLCFG for the second table entry would be 0x12254
(N - 1 = 1 = 0x1; M - 1 = 8788 = 0x2254).
4.6.14 PLL setup sequence

The following sequence must be followed step by step in order to have the PLL initialized
an running:
1. Disconnect the PLL with one feed sequence if PLL is already connected.
2. Disable the PLL with one feed sequence.
3. Change the CPU Clock Divider setting to speed up operation without the PLL, if
desired.
4. Write to the Clock Source Selection Control register to change the clock source.
5. Write to the PLLCFG and make it effective with one feed sequence. The PLLCFG can
only be updated when the PLL is disabled.

6. Enable the PLL with one feed sequence.

7. Change the CPU Clock Divider setting for the operation with the PLL. It's critical to do
this before connecting the PLL.
8. Wait for the PLL to achieve lock by monitoring the PLOCK bit in the PLLSTAT register,
or using the PLOCK interrupt, or wait for a fixed time when the input clock to PLL is
slow (i.e. 32 kHz). The value of PLOCK may not be stable when the PLL reference
frequency (FREF, the frequency of REFCLK, which is equal to the PLL input
frequency divided by the pre-divider value) is less than 100 kHz or greater than
20 MHz. In these cases, the PLL may be assumed to be stable after a start-up time
has passed. This time is 500 µs when FREF is greater than 400 kHz and 200 / FREF
seconds when FREF is less than 400 kHz.
9. Connect the PLL with one feed sequence.
It's very important not to merge any steps above. For example, don't update the PLLCFG
and enable the PLL simultaneously with the same feed sequence.
4.7 Clock dividers

The output of the PLL must be divided down for use by the CPU and the USB block.
Separate dividers are provided such that the CPU frequency can be determined
independently from the USB block, which always requires 48 MHz with a 50% duty cycle
for proper operation.
USB clock
PLLC usb
PLLE divider
clk
USBSEL
PLOCK
pllclk
individual
pd Phase- CPU .
cclk peripheral
Frequency Filter CCO clock .
Fosc N-divider clock
Detector divider .
CCLKSEL
divider
PCLKSEL
NSEL[7:0]
M-divider /2
MSEL[15:0]
Fig 19. PLL and clock dividers
4.7.1 CPU Clock Configuration register (CCLKCFG - 0xE01F C104)

The CCLKCFG register controls the division of the PLL output before it is used by the
CPU. When the PLL is bypassed, the division may be by 1. When the PLL is running, the
output must be divided in order to bring the CPU clock frequency (CCLK) within operating
limits. An 8 bit divider allows a range of options, including slowing CPU operation to a low
rate for temporary power savings without turning off the PLL.

Note: when the USB interface is used in an application, CCLK must be at least 18 MHz in
order to support internal operations of the USB block.
Table 46. CPU Clock Configuration register (CCLKCFG - address 0xE01F C104) bit
description
value
7:0 CCLKSEL Selects the divide value for creating the CPU clock (CCLK) from the 0x00
PLL output.
Only 0 and odd values (1, 3, 5, ..., 255) are supported and can be
used when programming the CCLKSEL bits.
Warning: Using an even value (2, 4, 6, ..., 254) when setting the
CCLKSEL bits may result in incorrect operation of the device.
The CCLK is derived from the PLL output signal, divided by CCLKSEL + 1. Having
CCLKSEL = 1 results in CCLK being one half the PLL output, CCLKSEL = 3 results in
CCLK being one quarter of the PLL output, etc..
4.7.2 USB Clock Configuration register (USBCLKCFG - 0xE01F C108)

The USBCLKCFG register controls the division of the PLL output before it is used by the
USB block. If the PLL is bypassed, the division may be by 1. In that case, the PLL input
frequency must be 48 MHz, with a 500 ppm tolerance. When the PLL is running, the
output must be divided in order to bring the USB clock frequency to 48 MHz with a 50%
duty cycle. A 4-bit divider allows obtaining the correct USB clock from any even multiple of
48 MHz (i.e. any multiple of 96 MHz) within the PLL operating range.
Remark: The Internal RC clock can not be used as a clock source for USB because a
more precise clock is needed (see Table 35).
Table 47. USB Clock Configuration register (USBCLKCFG - address 0xE01F C108) bit
description
value
3:0 USBSEL Selects the divide value for creating the USB clock from the PLL output. 0
Warning: Improper setting of this value will result in incorrect operation
of the USB interface.
The USB clock is derived from the PLL output signal, divided by USBSEL + 1. Having
USBSEL = 1 results in USB’s clock being one half the PLL output.
4.7.3 IRC Trim Register (IRCTRIM - 0xE01F C1A4)

This register is used to trim the on-chip 4 MHz oscillator.
Table 48. IRC Trim register (IRCTRIM - address 0xE01F C1A4) bit description
value
7:0 IRCtrim IRC trim value. It controls the on-chip 4 MHz IRC frequency. 0xA0[1]
15:8 - Reserved. Software must write 0 into these bits. NA
[1] Actual reset value depends on IRC factory trimming.

4.7.4 Peripheral Clock Selection registers 0 and 1 (PCLKSEL0 -

0xE01F C1A8 and PCLKSEL1 - 0xE01F C1AC)
A pair of bits in a Peripheral Clock Selection register controls the rate of the clock signal
that will be supplied to the corresponding peripheral as specified in Table 49, Table 50 and
Table 51. For details on the CCLK clock see Figure 19.
Table 49. Peripheral Clock Selection register 0 (PCLKSEL0 - address 0xE01F C1A8) bit
description
value
1:0 PCLK_WDT Peripheral clock selection for WDT. 00
3:2 PCLK_TIMER0 Peripheral clock selection for TIMER0. 00
7:6 PCLK_UART0 Peripheral clock selection for UART0. 00
11:10 - Unused, always read as 0. 00
13:12 PCLK_PWM1 Peripheral clock selection for PWM1. 00
15:14 PCLK_I2C0 Peripheral clock selection for I2C0. 00
17:16 PCLK_SPI Peripheral clock selection for SPI. 00
19:18 PCLK_RTC[1] Peripheral clock selection for RTC. 00
21:20 PCLK_SSP1 Peripheral clock selection for SSP1. 00
23:22 PCLK_DAC Peripheral clock selection for DAC. 00
25:24 PCLK_ADC Peripheral clock selection for ADC. 00
27:26 PCLK_CAN1[2] Peripheral clock selection for CAN1. 00
29:28 PCLK_CAN2[2] Peripheral clock selection for CAN2. 00
31:30 PCLK_ACF[2] Peripheral clock selection for CAN filtering. 00
[1] For PCLK_RTC only, the value ’01’ is illegal. Do not write ’01’ to the PCLK_RTC. Attempting to write ’01’
results in the previous value being unchanged.
[2] PCLK_CAN1/2 must be set to the same value as PCLK_ACF.
Table 50. Peripheral Clock Selection register 1 (PCLKSEL1 - address 0xE01F C1AC) bit
description
value
1:0 PCLK_BAT_RAM Peripheral clock selection for the battery supported RAM. 00
3:2 PCLK_GPIO Peripheral clock selection for GPIOs. 00
5:4 PCLK_PCB Peripheral clock selection for the Pin Connect block. 00
11:10 PCLK_SSP0 Peripheral clock selection for SSP0. 00

Table 50. Peripheral Clock Selection register 1 (PCLKSEL1 - address 0xE01F C1AC) bit
description
value
23:22 PCLK_I2S Peripheral clock selection for I2S. 00
25:24 PCLK_MCI Peripheral clock selection for MCI. 00
29:28 PCLK_SYSCON Peripheral clock selection for the System Control block. 00
Table 51. Peripheral Clock Selection register bit values

PCLKSEL0 and PCLKSEL1 Function Reset
individual peripheral’s clock value
select options
00 PCLK_xyz = CCLK/4 00
01 PCLK_xyz = CCLK[1]
10 PCLK_xyz = CCLK/2
11 Peripheral’s clock is selected to PCLK_xyz = CCLK/8
except for CAN1, CAN2, and CAN filtering when ’11’
selects PCLK_xyz = CCLK/6.
[1] For PCLK_RTC only, the value ’01’ is illegal. Do not write ’01’ to the PCLK_RTC. Attempting to write ’01’
results in the previous value being unchanged.
4.8 Power control

The LPC2300 supports a variety of power control features. There are four special modes
of processor power reduction: Idle mode, Sleep mode, Power-down mode, and Deep
power-down mode. The CPU clock rate may also be controlled as needed by changing
clock sources, re-configuring PLL values, and/or altering the CPU clock divider value. This
allows a trade-off of power versus processing speed based on application requirements.
In addition, Peripheral Power Control allows shutting down the clocks to individual on-chip
peripherals, allowing fine tuning of power consumption by eliminating all dynamic power
use in any peripherals that are not required for the application.
The LPC2300 also implements a separate power domain in order to allow turning off
power to the bulk of the device while maintaining operation of the Real Time Clock and a
small static RAM, referred to as the Battery RAM. This feature is described in more detail
in Section 4.8.11 and in Section 26.8.
4.8.1 Idle mode

When Idle mode is entered, the clock to the core is stopped. Resumption from the Idle
mode does not need any special sequence but re-enabling the clock to the ARM core.
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 dynamic
power used by the processor itself, memory systems and related controllers, and internal
buses.

4.8.2 Sleep mode

When the chip enters the Sleep mode, the main oscillator is powered down and all clocks
are stopped. The output of the IRC is disabled but the IRC is not powered down for a fast
wake-up later. The 32 kHz RTC oscillator is not stopped because the RTC interrupts may
be used as the wake-up source. The flash is left in the standby mode allowing a very quick
wake-up. The PLL is automatically turned off and disconnected. The CCLK and USBCLK
clock dividers automatically get reset to zero.
The processor state and registers, peripheral registers, and internal SRAM values are
preserved throughout Sleep mode and the logic levels of chip pins remain static. The
Sleep mode can be terminated and normal operation resumed by either a Reset or certain
specific interrupts that are able to function without clocks. Since all dynamic operation of
the chip is suspended, Sleep mode reduces chip power consumption to a very low value.
On the wake-up of sleep mode, if the IRC was used before entering sleep mode, the 2-bit
IRC timer starts counting and the code execution and peripherals activities will resume
after the timer expires (4 cycles). If the main external oscillator was used, the 12-bit main
oscillator timer starts counting and the code execution will resume when the timer expires
(4096 cycles). The PLL and the clock dividers must be reconfigured after wakeup.
4.8.3 Power-down mode

Power-down mode does everything that Sleep mode does, but also turns off the flash
memory. This saves more power, but requires waiting for resumption of flash operation
before execution of code or data access in the flash memory can be accomplished.
When the chip enters Power-down mode, the IRC, the main oscillator, and all clocks are
stopped. The 32kHz RTC oscillator is not stopped because the RTC interrupts may be
used as the wakeup source. The flash is forced into Power-down mode. The PLL is
automatically turned off and disconnected. The CCLK and USBCLK clock dividers
automatically get reset to zero.
On the wakeup from Power-down mode, if the IRC was used before entering power-down
mode, after IRC-start-up time (60 s), the 2-bit IRC timer starts counting and expires in 4
cycles. The code execution can then be resumed immediately upon the expiration of the
IRC timer if the code was running from SRAM. In the meantime, the flash wakeup-timer
generates flash start-up time 100 s. When it times out, access to the flash is enabled.
The PLL and clock dividers must be reconfigured after wakeup.
4.8.4 Deep power-down mode

Deep power-down mode is like Power-down mode, but the on-chip regulator that supplies
power to internal logic is also shut off. This produces the lowest possible power
consumption without actually removing power from the entire chip. Since Deep
power-down mode shuts down the on-chip logic power supply, there is no register or
memory retention, and resumption of operation involves the same activities as a full-chip
reset.
If power is supplied to the LPC2300 during Deep power-down mode, wakeup can be
caused by the RTC alarm or external reset.
While in Deep power-down mode, external device power may be removed. In this case,
the LPC2300 will start up when external power is restored.

Essential data may be retained through Deep power-down mode (or through complete
powering off of the chip) by storing data in the battery RAM, as long as the external power
to the VBAT pin is maintained.
4.8.5 Peripheral power control

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. This is
detailed in the description of the PCONP register.

The Power Control function uses registers shown in Table 52. More detailed descriptions
follow.
Table 52. Power Control registers

value[1]
PCON Power Control Register. This register R/W 0x00 0xE01F C0C0
contains control bits that enable the two
reduced power operating modes of the
LPC2300. See Table 53.
INTWAKE Interrupt Wakeup Register. Controls which R/W 0x00 0xE01F C144
interrupts will wake the LPC2300 from
power-down mode. See Table 55
PCONP Power Control for Peripherals Register. This R/W 0xE01F C0C4
register contains control bits that enable and
disable individual peripheral functions,
allowing elimination of power consumption by
peripherals that are not needed.
4.8.7 Power Mode Control register (PCON - 0xE01F C0C0)

Reduced power modes are controlled via the PCON register, as described in Table 53.
Table 53. Power Mode Control register (PCON - address 0xE01F C0C0) bit description
value
0 PM0 (IDL) Power mode control bit 0. See text and table below for details. 0
1 PM1 (PD) Power mode control bit 1. See text and table below for details. 0
2 BODPDM Brown-Out Power-down mode. When BODPDM is 1, the Brown-Out 0
Detect circuitry will turn off when chip Power-down mode is entered,
resulting in a further reduction in power usage. However, the possibility
of using Brown-Out Detect as a wakeup source from Power-down mode
will be lost.
When 0, the Brown-Out Detect function remains active during
Power-down mode.
See the System Control Block chapter for details of Brown-Out
detection.

Table 53. Power Mode Control register (PCON - address 0xE01F C0C0) bit description
value
3 BOGD Brown-Out Global Disable. When BOGD is 1, the Brown-Out Detect 0
circuitry is fully disabled at all times, and does not consume power.
When 0, the Brown-Out Detect circuitry is enabled.
detection.
4 BORD Brown-Out Reset Disable. When BORD is 1, the second stage of low 0
voltage detection (2.6 V) will not cause a chip reset.
When BORD is 0, the reset is enabled. The first stage of low voltage
detection (2.9 V) Brown-Out interrupt is not affected.
detection.
7 PM2 Power mode control bit 2. See text and table below for details. 0
Encoding of reduced power modes

The PM2, PM1, and PM0 bits in PCON allow entering reduced power modes as needed.
The encoding of these bits allows backward compatibility with devices that previously only
supported Idle and Power-down modes. Table 54 below shows the encoding for the four
reduced power modes supported by the LPC2300.
Table 54. Encoding of reduced power modes

PM2, PM1, PM0 Description
000 Normal operation
001 Idle mode. Causes the processor clock to be stopped, while on-chip peripherals
remain active. Any enabled interrupt from a peripheral or an external interrupt
source will cause the processor to resume execution. See Section 4.8.1 for
details.
101 Sleep mode. This mode is similar to Power-down mode (the oscillator and all
on-chip clocks are stopped), but the flash memory is left in Standby mode. This
allows a more rapid wakeup than Power-down mode because the flash
reference voltage regulator start-up time is not needed. See Section 4.8.2 for
details.
010 Power-down mode. Causes the oscillator and all on-chip clocks to be stopped.
A wakeup condition from an external interrupt can cause the oscillator to
re-start, the PD bit to be cleared, and the processor to resume execution. See
Section 4.8.3 for details.
110 Deep power-down mode. This is the most extreme power saving mode. As in
Power-down mode, Deep power-down mode causes the oscillator and all
on-chip clocks to be stopped, but also turns off the on-chip DC-DC converter
that supplies power to internal circuitry. See Section 4.8.4 for details.
Others Reserved, not currently used.
4.8.8 Interrupt Wakeup Register (INTWAKE - 0xE01F C144)

Enable bits in the INTWAKE register allow the external interrupts 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 necessary 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). Details of the wakeup operations are shown in
Table 55.
For an external interrupt pin to be a source that would wake up the microcontroller from
Power-down mode, it is also necessary to clear the corresponding interrupt flag (see
Section 3.6.2 “External Interrupt flag register (EXTINT - 0xE01F C140)”).
Table 55. Interrupt Wakeup register (INTWAKE - address 0xE01F C144) bit description
value
0 EXTWAKE0 When one, assertion of EINT0 will wake up the processor from 0
Power-down mode.
Power-down mode.
Power-down mode.
Power-down mode.
4 ETHWAKE When one, assertion of the Wake-up on LAN interrupt 0
(WakeupInt) of the Ethernet block will wake up the processor
from Power-down mode.
5 USBWAKE When one, activity on the USB bus will wake up the processor 0
from Power-down mode. Any change of state on the USB data
pins will cause a wakeup when this bit is set. For details on the
relationship of USB to Power-down mode and wakeup, see the
relevant USB chapter(s).
6 CANWAKE When one, activity of the CAN bus will wake up the processor 0
from Power-down mode. Any change of state on the CAN
receive pins will cause a wakeup when this bit is set.
7 GPIO0WAKE When one, specified activity on GPIO pins (port 0) enabled for 0
wakeup will wake up the processor from Power-down mode.
See the GPIO chapter for details.
8 GPIO2WAKE When one, specified activity on GPIO pins (port 2) enabled for 0
wakeup will wake up the processor from Power-down mode.
See the GPIO chapter for details.

Table 55. Interrupt Wakeup register (INTWAKE - address 0xE01F C144) bit description
value
13:9 - Reserved, user software should not write ones to reserved bits. NA
14 BODWAKE When one, Brown-Out Detect interrupt will wake up the 0
processor from Power-down mode.
Note: since there is a delay before execution begins, there is
no guarantee that execution will resume before VDD(DCDC)(3V3)
has fallen below the lower BOD threshold, which prevents
execution. If execution does resume, there is no guarantee of
how long the processor will continue execution before the lower
BOD threshold terminates execution. These issues depend on
the slope of the decline of VDD(DCDC)(3V3). High decoupling
capacitance (between VDD(DCDC)(3V3) and ground) in the vicinity
of the LPC2300 will improve the likelihood that software will be
able to do what needs to be done when power is in the process
of being lost.
15 RTCWAKE When one, assertion of an RTC interrupt will wake up the 0
processor from Power-down mode.
4.8.9 Power Control for Peripherals register (PCONP - 0xE01F C0C4)

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. Information on peripheral specific power
saving features may be found in the chapter describing that peripheral.
Each bit in PCONP controls one peripheral as shown in Table 56. The bit numbers
correspond to the related peripheral number as shown in the APB peripheral map
Table 10 “APB peripherals and base addresses”.
If a peripheral control bit is 1, that peripheral is enabled. If a peripheral bit is 0, that

peripheral’s clock is disabled (gated off) to conserve power. For example if bit 19 is 1, the
I2C1 interface is enabled. If bit 19 is 0, the I2C1 interface is disabled.
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 56. Power Control for Peripherals register (PCONP - address 0xE01F C0C4) bit
description
value
0 - Unused, always 0. 0
1 PCTIM0 Timer/Counter 0 power/clock control bit. 1
2 PCTIM1 Timer/Counter 1 power/clock control bit. 1
3 PCUART0 UART0 power/clock control bit. 1
4 PCUART1 UART1 power/clock control bit. 1

Table 56. Power Control for Peripherals register (PCONP - address 0xE01F C0C4) bit
description
value
5 - Unused, always 0. 1
6 PCPWM1 PWM1 power/clock control bit. 1
7 PCI2C0 The I2C0 interface power/clock control bit. 1
8 PCSPI The SPI interface power/clock control bit. 1
9 PCRTC The RTC power/clock control bit. 1
10 PCSSP1 The SSP1 interface power/clock control bit. 1
11 PCEMC External Memory Controller 1
12 PCAD A/D converter (ADC) power/clock control bit. 0
Note: Clear the PDN bit in the AD0CR (see Section 27.6.1) before
clearing this bit, and set this bit before setting PDN.
13 PCAN1 CAN Controller 1 power/clock control bit. 0
14 PCAN2 CAN Controller 2 power/clock control bit. 0
19 PCI2C1 The I2C1 interface power/clock control bit. 1
20 - Unused, always 0 0
21 PCSSP0 The SSP0 interface power/clock control bit. 1
22 PCTIM2 Timer 2 power/clock control bit. 0
23 PCTIM3 Timer 3 power/clock control bit. 0
24 PCUART2 UART 2 power/clock control bit. 0
25 PCUART3 UART 3 power/clock control bit. 0
26 PCI2C2 I2C interface 2 power/clock control bit. 1
27 PCI2S I2S interface power/clock control bit. 0
28 PCSDC SD card interface power/clock control bit. 0
29 PCGPDMA GP DMA function power/clock control bit. 0
30 PCENET Ethernet block power/clock control bit. 0
31 PCUSB USB interface power/clock control bit. 0
4.8.10 Power control usage notes

After every reset, the PCONP register contains the value that enables selected interfaces
and peripherals controlled by the PCONP to be enabled. Therefore, apart from proper
configuring via peripheral dedicated registers, the user’s application might have to access
the PCONP in order to start using some 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.

4.8.11 Power domains

The LPC2300 provides two independent power domains that allow the bulk of the device
to have power removed while maintaining operation of the Real Time Clock and the
Battery RAM.
The VBAT pin supplies power only to the RTC and the Battery RAM. These two functions
require a minimum of power to operate, which can be supplied by an external battery.
When the CPU and the rest of chip functions are stopped and power removed, the RTC
can supply an alarm output that may be used by external hardware to restore chip power
and resume operation. Details may be found in Section 26.3.
Remark: The RTC and the battery RAM operate independently from each other.
Therefore, the battery RAM can be accessed at any time, regardless of whether the RTC
is enabled or disabled via its dedicated bit in the PCONP register.
4.9 Wakeup timer

The LPC2300 begins operation at power-up and when awakened from Power-down mode
or Deep power-down mode by using the 4 MHz IRC oscillator as the clock source (see
Section 3.4). This allows chip operation to resume quickly. If the main oscillator or the PLL
is needed by the application, software will need to enable these features and wait for them
to stabilize before they are used as a clock source.
When the main oscillator is initially activated, the wakeup timer allows software to ensure
that the main oscillator is fully functional before the processor uses it as a clock source
and starts to execute instructions. This is important at power on, all types of Reset, and
whenever any of the aforementioned functions are turned off for any reason. Since the
oscillator and other functions are turned off during Power-down and Deep power-down
modes, any wakeup of the processor from these mode makes use of the Wakeup Timer.
The Wakeup Timer 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 VDD(3V3) ramp (in the case of power on), the type of
crystal 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 Wakeup timer counts a fixed number of clocks (4096), then
sets the flag (OSCSTAT bit in the SCS register) that indicates that the main oscillator is
ready for use. Software can then switch to the main oscillator and, if needed, start the
PLL. See Section 4.4.2 for details.

UM10211
Chapter 5: LPC23XX External Memory Controller (EMC)

This chapter describes the EMC controller for the following parts:
• LPC2377/78
• LPC2388
LPC2361/62, LPC2364/65/66/67/68, and LPC2387 do not have an EMC controller.
5.2 Basic configuration

The EMC is configured using the following registers:
1. Power: In the PCONP register (Table 56), set bit PCEMC.

Remark: The EMC is enabled on reset (PCEMC = 1). On POR and warm reset, the
EMC is enabled as well, see Section 5.11.1.
2. Clock: see Section 4.7.1.
3. Pins: Select data, address, and control pins and their modes in PINSEL6/8/9 and
PINMODE6/8/9 (see Section 9.5).
4. Configuration: see Table 62 and Table 64.
5.3 Introduction
The External Memory Controller (EMC) is an ARM PrimeCell MultiPort Memory Controller
peripheral offering support for asynchronous static memory devices such as RAM, ROM
and Flash. The EMC is an Advanced Microcontroller Bus Architecture (AMBA) compliant
peripheral.
5.4 Features
• Asynchronous static memory device support including RAM, ROM, and Flash, with or
without asynchronous page mode.
• Low transaction latency.
• Read and write buffers to reduce latency and to improve performance.
• 8-bit wide static memory support.
• Can be used as an interface to some external I/O devices.
• Two chip selects for static memory devices.
5.5 Functional overview

This chapter describes the major functional blocks of the EMC.

5.6 EMC functional description

Figure 20 shows a block diagram of the EMC.
EMC
A[15:0]
shared
D[7:0] signals
AHB SLAVE DATA
REGISTER BUFFERS
PAD INTERFACE
INTERFACE
AHB Bus
BLS0
MEMORY OE
AHB SLAVE CONTROLLER static
MEMORY STATE memory
INTERFACE MACHINE signals
CS0, CS1
Fig 20. EMC block diagram
The functions of the EMC blocks are described in the following sections:
• AHB slave register interface.

• AHB slave memory interfaces.
• Data buffers.
• Memory controller state machine.
• Pad interface.
5.7 AHB Slave register interface

The AHB slave register interface block enables the registers of the EMC to be
programmed. This module also contains most of the registers and performs the majority of
the register address decoding.
To eliminate the possibility of endianness problems, all data transfers to and from the
registers of the EMC must be 32 bits wide.
Note: If an access is attempted with a size other than a word (32 bits), it causes an
ERROR response to the AHB bus and the transfer is terminated.

5.7.1 AHB Slave memory interface

The AHB slave memory interface allows access to external memories.
5.7.1.1 Memory transaction endianness

The endianness of the data transfers to and from the external memories is determined by
the Endian mode (N) bit in the EMCConfig Register.
Note: The memory controller must be idle (see the busy field of the EMCStatus Register)
before endianness is changed, so that the data is transferred correctly.
5.7.1.2 Memory transaction size

For the LPC23xx, memory transactions must be 8 bits wide. Any access attempted with a
size greater than 8 bits causes an ERROR response to the AHB bus and the transfer is
terminated.
5.7.1.3 Write protected memory areas

Write transactions to write-protected memory areas generate an ERROR response to the
AHB bus and the transfer is terminated.
5.7.2 Data buffers

The AHB interface reads and writes via buffers to improve memory bandwidth and reduce
transaction latency. The EMC contains four 16-word buffers. The buffers can be used as
read buffers, write buffers, or a combination of both. The buffers are allocated
automatically.
They can be enabled or disabled for static memory using the EMCStaticConfig Registers.
5.7.2.1 Write buffers

Write buffers are used to:
• Merge write transactions so that the number of external transactions are minimized.
Buffer data until the EMC can complete the write transaction, improving AHB write
latency.
• Reduce external memory traffic. This improves memory bandwidth and reduces
power consumption.
Write buffer operation:
• If the buffers are enabled, an AHB write operation writes into the Least Recently Used
(LRU) buffer, if empty.
If the LRU buffer is not empty, the contents of the buffer are flushed to memory to
make space for the AHB write data.
• If a buffer contains write data it is marked as dirty, and its contents are written to
memory before the buffer can be reallocated.
The write buffers are flushed whenever:
• The memory controller state machine is not busy performing accesses to external
memory.

The memory controller state machine is not busy performing accesses to external
memory, and an AHB interface is writing to a different buffer.
Note: For static memory, the smallest buffer flush is a byte of data.
5.7.2.2 Read buffers

Read buffers are used to:
• Buffer read requests from memory. Future read requests that hit the buffer read the
data from the buffer rather than memory, reducing transaction latency.
• Reduce external memory traffic. This improves memory bandwidth and reduces
power consumption.
Read buffer operation:
• If the buffers are enabled and the read data is contained in one of the buffers, the read
data is provided directly from the buffer.
• If the read data is not contained in a buffer, the LRU buffer is selected. If the buffer is
dirty (contains write data), the write data is flushed to memory. When an empty buffer
is available the read command is posted to the memory.
A buffer filled by performing a read from memory is marked as not-dirty (not containing
write data) and its contents are not flushed back to the memory controller unless a
subsequent AHB transfer performs a write that hits the buffer.
5.7.3 Memory controller state machine

The memory controller state machine comprises a static memory controller.
5.7.4 Pad interface

The pad interface block provides the interface to the pads.
5.8 Memory bank select

Two independently-configurable memory chip selects are supported. Pins CS1 and CS0
are used to select static memory devices.
Static memory chip select ranges are each 64 kilobytes in size. Table 57 shows the
address ranges of the chip selects.
Table 57. Memory bank selection

Chip Select Pin Address Range Memory Type Size of Range
CS0 0x8000 0000 - 0x8000 FFFF Static 64 kB
CS1 0x8100 0000 - 0x8100 FFFF Static 64 kB

5.9 Reset
The EMC receives two reset signals. One is Power-On Reset (POR), asserted when chip
power is applied, and when a brown-out condition is detected (see Section 3.5 “Brown-out
detection” for details). The other reset is from the external Reset pin and the Watchdog
Timer.
A configuration bit in the SCS register, called EMC_Reset_Disable, allows control of how
the EMC is reset. The default configuration (EMC_Reset_Disable = 0) is that both EMC
resets are asserted when any type of reset event occurs. In this mode, all registers and
functions of the EMC are initialized upon any reset condition.
If EMC_Reset_Disable is set to 1, many portions of the EMC are only reset by a power-on
or brown-out event, in order to allow the EMC to retain its state through a warm reset
(external reset or watchdog reset). If the EMC is configured correctly, auto-refresh can be
maintained through a warm reset.
5.10 Pin description

Table 58 shows the interface and control signal pins for the EMC.
Table 58. Pad interface and control signal descriptions

Name Type Value on POR Description
reset
A[15:0] Output 0x0000 0000 External memory address output.
D[7:0] Input/ Data outputs = External memory data lines. These are inputs when
Output 0x0000 0000 data is read from external memory and outputs when
data is written to external memory.
OE Output 1 Low active output enable for static memory devices.
BLS0 Output 1 Low active Byte Lane select signal 0.
CS[1:0] Output 0x3 Static memory chip selects. Default active LOW.
Used for static memory devices.

This chapter describes the EMC registers and provides details required when
programming the microcontroller. The EMC registers are shown in Table 59.
Table 59. EMC register summary

Address Register Name Description Warm POR Type
Reset Reset
Value Value
0xFFE0 8000 EMCControl Controls operation of the memory controller. 0x1 0x3 R/W
0xFFE0 8004 EMCStatus Provides EMC status information. - 0x5 RO
0xFFE0 8008 EMCConfig Configures operation of the memory controller - 0x0 R/W
0xFFE0 8080 EMCStaticExtendedWait Time long static memory read and write transfers. - 0x0 R/W
0xFFE0 8200 EMCStaticConfig0 Selects the memory configuration for static chip select 0. - 0x0 R/W
0xFFE0 8204 EMCStaticWaitWen0 Selects the delay from chip select 0 to write enable. - 0x0 R/W

Table 59. EMC register summary

Address Register Name Description Warm POR Type
Reset Reset
Value Value
0xFFE0 8208 EMCStaticWaitOen0 Selects the delay from chip select 0 or address change, - 0x0 R/W
whichever is later, to output enable.
0xFFE0 820C EMCStaticWaitRd0 Selects the delay from chip select 0 to a read access. - 0x1F R/W
0xFFE0 8210 EMCStaticWaitPage0 Selects the delay for asynchronous page mode - 0x1F R/W
sequential accesses for chip select 0.
0xFFE0 8214 EMCStaticWaitWr0 Selects the delay from chip select 0 to a write access. - 0x1F R/W
0xFFE0 8218 EMCStaticWaitTurn0 Selects the number of bus turnaround cycles for chip - 0xF R/W
select 0.
0xFFE0 8220 EMCStaticConfig1 Selects the memory configuration for static chip select 1. - 0x0 R/W
0xFFE0 8224 EMCStatic\WaitWen1 Selects the delay from chip select 1 to write enable. - 0x0 R/W
0xFFE0 8228 EMCStaticWaitOen1 Selects the delay from chip select 1 or address change, - 0x0 R/W
whichever is later, to output enable.
0xFFE0 822C EMCStaticWaitRd1 Selects the delay from chip select 1 to a read access. - 0x1F R/W
0xFFE0 8230 EMCStaticWaitPage1 Selects the delay for asynchronous page mode - 0x1F R/W
sequential accesses for chip select 1.
0xFFE0 8234 EMCStaticWaitWr1 Selects the delay from chip select 1 to a write access. - 0x1F R/W
0xFFE0 8238 EMCStaticWaitTurn1 Selects the number of bus turnaround cycles for chip - 0xF R/W
select 1.
5.11.1 EMC Control Register (EMCControl - 0xFFE0 8000)

The EMCControl Register is a read/write register that controls operation of the memory
controller. The control bits can be altered during normal operation. Table 60 shows the bit
assignments for the EMCControl Register.
Table 60. EMC Control register (EMCControl - address 0xFFE0 8000) bit description
Bit Symbol Value Description POR
Reset
Value
0 E EMC Enable control. Indicates if the EMC is enabled or disabled: 1
0 Disabled
1 Enabled (POR and warm reset value).
Note: Disabling the EMC reduces power consumption. When the memory controller is
disabled the memory is not refreshed. The memory controller is enabled by setting the
enable bit or by reset.
This bit must only be modified when the EMC is in idle state.[1]
1 M Address mirror control. Indicates normal or reset memory map: 1
0 Normal memory map.
1 Reset memory map. Static memory chip select 1 is mirrored onto chip select 0 (POR
reset value).
Note: On POR, chip select 1 is mirrored to the chip select 0 memory area.

Table 60. EMC Control register (EMCControl - address 0xFFE0 8000) bit description
Reset
Value
2 L Low-power mode control. Indicates normal, or low-power mode: 0
0 Normal mode (warm reset value).
1 Low-power mode.
Note: Entering low-power mode reduces memory controller power consumption. The
memory controller returns to normal functional mode by clearing the low-power mode bit
(L), or by POR.
This bit must only be modified when the EMC is in idle state.[1]
31:3 - - Reserved, user software should not write ones to reserved bits. The value read from a NA
reserved bit is not defined.
[1] The external memory cannot be accessed in low-power or disabled state. If a memory access is performed an AHB error response is
generated. The EMC registers can be programmed in low-power and/or disabled state.
5.11.2 EMC Status Register (EMCStatus - 0xFFE0 8004)

The read-only EMCStatus Register provides EMC status information. Table 61 shows the
bit assignments for the EMCStatus Register.
Table 61. EMC Status register (EMCStatus - address 0xFFE0 8008) bit description
Reset
Value
0 B Busy. This bit is used to ensure that the memory controller enters the low-power or 1
disabled mode cleanly by determining if the memory controller is busy or not:
0 EMC is idle (warm reset value).
1 EMC is busy performing memory transactions, commands, auto-refresh cycles, or
is in self-refresh mode (POR reset value).
1 S Write buffer status. This bit enables the EMC to enter low-power mode or disabled 0
mode cleanly:
0 Write buffers empty (POR reset value)
1 Write buffers contain data.
2 SA Self-refresh acknowledge. This bit indicates the operating mode of the EMC: 1
0 Normal mode
1 Self-refresh mode (POR reset value).
31:3 - - Reserved, user software should not write ones to reserved bits. The value read NA
from a reserved bit is not defined.
5.11.3 EMC Configuration Register (EMCConfig - 0xFFE0 8008)

The EMCConfig Register configures the operation of the memory controller. It is
recommended that this register is modified during system initialization, or when there are
no current or outstanding transactions. This can be ensured by waiting until the EMC is
idle, and then entering low-power or disabled mode. This register is accessed with one
wait state. Table 62 shows the bit assignments for the EMCConfig Register.

Table 62. EMC Configuration register (EMCConfig - address 0xFFE0 8008) bit description
Reset
Value
0 Endian_mode Endian mode: 0
0 Little-endian mode (POR reset value).
1 Big-endian mode.
On power-on reset, the value of the endian bit is 0. All data must be flushed in the
EMC before switching between little-endian and big-endian modes.
7:1 - - Reserved, user software should not write ones to reserved bits. The value read from NA
a reserved bit is not defined.
8 - - Reserved, user software should not write ones to reserved bits. The value read from 0
5.11.4 Static Memory Extended Wait Register (EMCStaticExtendedWait -

0xFFE0 8080)
The EMCStaticExtendedWait register times long static memory read and write transfers
(which are longer that can be supported by the EMCStaticWaitRd[n] or
EMCStaticWaitWr[n] registers) when the EW bit of one of the EMCStaticConfig registers is
enabled. There is only a single EMCStaticExtendedWait Register. This is used by the
relevant static memory chip select if the appropriate ExtendedWait (EW) bit in the
EMCStaticConfig Register is set. It is recommended that this register is modified during
system initialization, or when there are no current or outstanding transactions. However, if
necessary, these control bits can be altered during normal operation. This register is
accessed with one wait state.
Table 70 shows the bit assignments for the EMCStaticExtendedWait register.
Table 63. Static Memory Extended Wait register (EMCStaticExtendedWait - address

0xFFE0 8080) bit description
Value
9:0 EXTENDEDWAIT External wait time out in terms of the CCLK clock 0x000
cycles. The delay is (EXTENDWAIT + 1) x 16 x tCCLK
0x0 16 CCLK clock cycles (POR reset value).
n (n+1) x 16 CCLK clock cycles.
0x3F (0x3F+1) x 16 CCLK clock cycles.
31:10 - - Reserved, user software should not write ones to NA
reserved bits. The value read from a reserved bit is
not defined.
For example, for a static memory read/write transfer time of 16 μs, and a CCLK frequency
of 50 MHz, the following value must be programmed into this register:
–6 6
16  10  50  10
-------------------------------------------------- – 1 = 49
16

5.11.5 Static Memory Configuration Registers (EMCStaticConfig0-1 -

0xFFE0 8200, 220)
The EMCStaticConfig0-1 Registers configure the static memory configuration. It is
recommended that these registers are modified during system initialization, or when there
are no current or outstanding transactions. This can be ensured by waiting until the EMC
is idle, and then entering low-power, or disabled mode. These registers are accessed with
one wait state.
Table 64 shows the bit assignments for the EMCStaticConfig0-1 Registers. Note that
synchronous burst mode memory devices are not supported.
Table 64. Static Memory Configuration registers (EMCStaticConfig0-1 - addresses 0xFFE0 8200, 0xFFE0 8220) bit
description
Reset
Value
1:0 MW Memory width. 00
00 8 bit (POR reset value).
01 Reserved.
10 Reserved.
11 Reserved.
2 - - Reserved, user software should not write ones to reserved bits. The value read from NA
3 PM Page mode. In page mode the EMC can burst up to four external accesses. 0
Therefore devices with asynchronous page mode burst four or higher devices are
supported. Asynchronous page mode burst two devices are not supported and must
be accessed normally.
0 Disabled (POR reset value).
1 Async page mode enabled (page length four).
6 PC Chip select polarity. The value of the chip select polarity on power-on reset is 0. 0
0 Active LOW chip select.
1 Active HIGH chip select.
7 - - Reserved, user software should not write ones to reserved bits. The value read from NA
8 EW Extended wait. Extended wait (EW) uses the EMCStaticExtendedWait Register to 0
time both the read and write transfers rather than the EMCStaticWaitRd and
EMCStaticWaitWr Registers. This enables much longer transactions.[1]
0 Extended wait disabled (POR reset value).
1 Extended wait enabled.
19 B[2] Buffer enable control. 0
0 Buffer disabled (POR reset value).
1 Buffer enabled.

Table 64. Static Memory Configuration registers (EMCStaticConfig0-1 - addresses 0xFFE0 8200, 0xFFE0 8220) bit
description
Reset
Value
20 P Write protect control. 0
0 Writes not protected (POR reset value).
1 Write protected.
[1] Extended wait and page mode cannot be selected simultaneously.

[2] EMC may perform burst read access even when the buffer enable bit is cleared.
5.11.6 Static Memory Write Enable Delay Registers (EMCStaticWaitWen0-1 -

0xFFE0 8204, 224)
The EMCStaticWaitWen0-1 Registers enable you to program the delay from the chip
select to the write enable. It is recommended that these registers are modified during
system initialization, or when there are no current or outstanding transactions. This can be
ensured by waiting until the EMC is idle, and then entering low-power, or disabled mode.
These registers are accessed with one wait state.
Table 65 shows the bit assignments for the EMCStaticWaitWen0-1 Registers.
Table 65. Static Memory Write Enable Delay registers (EMCStaticWaitWen0-1 - addresses
0xFFE0 8204,0xFFE0 8224) bit description
Bit Symbol Value Description POR Reset
Value
3:0 WAITWEN Wait write enable. Delay from chip select assertion 0
to write enable in terms of the CCLK clock cycles.
The delay is: (WAITWEN + 1) x tCCLK.
0 One CCLK cycle delay between assertion of chip
select and write enable (POR reset value).
n (n + 1) CCLK clock cycles delay.
0xF 16 CCLK cycle delay.
not defined.
5.11.7 Static Memory Output Enable Delay Registers (EMCStaticWaitOen0-1

- 0xFFE0 8208, 228)
The EMCStaticWaitOen0-1 Registers enable you to program the delay from the chip
select or address change, whichever is later, to the output enable. It is recommended that
these registers are modified during system initialization, or when there are no current or
outstanding transactions. This can be ensured by waiting until the EMC is idle, and then
entering low-power, or disabled mode. These registers are accessed with one wait state.
Table 66 shows the bit assignments for the EMCStaticWaitOen0-1 Registers.

Table 66. Static Memory Output Enable delay registers (EMCStaticWaitOen0-1 - addresses
0xFFE0 8208, 0xFFE0 8228) bit description
Value
3:0 WAITOEN Wait output enable. Delay from chip select assertion 0x0
to output enable in terms of the CCLK cycles. The
delay is: (WAITOEN x tCCLK).
0x0 No delay (POR reset value).
n n CCLK clock cycles delay.
0xF 15 CCLK clock cycles delay.
not defined.
5.11.8 Static Memory Read Delay Registers (EMCStaticWaitRd0-1 -

0xFFE0 820C, 22C)
The EMCStaticWaitRd0-1 Registers enable you to program the delay from the chip select
to the read access. It is recommended that these registers are modified during system
initialization, or when there are no current or outstanding transactions. This can be
ensured by waiting until the EMC is idle, and then entering low-power, or disabled mode. It
is not used if the extended wait bit is enabled in the EMCStaticConfig0-1 Registers. These
registers are accessed with one wait state.
Table 67 shows the bit assignments for the EMCStaticWaitRd0-1 Registers.
Table 67. Static Memory Read Delay registers (EMCStaticWaitRd0-1 - addresses

0xFFE0 820C, 0xFFE0 822C) bit description
Value
4:0 WAITRD Non-page mode read wait states or asynchronous page 0x1F
mode readfirst access wait state expressed in terms of
the CCLK clock cycles. Non-page mode read or
asynchronous page mode read, first read only wait state
time is: (WAITRD + 1) x tCCLK
0x0 1 CCLK clock cycle for read accesses.
n (n + 1) CCLK cycles for read accesses.
0x1F 32 CCLK cycles for read accesses (POR reset value).
defined.
5.11.9 Static Memory Page Mode Read Delay Registers

(EMCStaticwaitPage0-1 - 0xFFE0 8210, 230)
The EMCStaticWaitPage0-1 Registers enable you to program the delay for asynchronous
page mode sequential accesses. It is recommended that these registers are modified
during system initialization, or when there are no current or outstanding transactions. This
can be ensured by waiting until the EMC is idle, and then entering low-power, or disabled
mode. This register is accessed with one wait state.
Table 68 shows the bit assignments for the EMCStaticWaitPage0-1 Registers.


Table 68. Static Memory Page Mode Read Delay registers0-1 (EMCStaticWaitPage0-1 -
addresses 0xFFE0 8210, 0xFFE0 8230) bit description
Value
4:0 WAITPAGE Asynchronous page mode read after the first read wait 0x1F
states. Number of wait states for asynchronous page
mode read accesses after the first read is:
(WAITPAGE + 1) x tCCLK
0x0 1 CCLK cycle read access time.
n (n+ 1) CCLK cycle read access time.
0x1F 32 CCLK cycle read access time (POR reset value).
defined.
5.11.10 Static Memory Write Delay Registers (EMCStaticWaitwr0-1 -

0xFFE0 8214, 234)
The EMCStaticWaitWr0-1 Registers enable you to program the delay from the chip select
to the write access. It is recommended that these registers are modified during system
ensured by waiting until the EMC is idle, and then entering low-power, or disabled
mode.These registers are not used if the extended wait (EW) bit is enabled in the
EMCStaticConfig Register. These registers are accessed with one wait state.
Table 69 shows the bit assignments for the EMCStaticWaitWr0-1 Registers.
Table 69. Static Memory Write Delay registers0-1 (EMCStaticWaitWr - addresses

Value
4:0 WAITWR SRAM Write wait states. SRAM wait state time for write 0x1F
accesses after the first read in terms of the CCLK clock
cycles. The wait state time for write accesses after the
first read is (WAITWR + 2) x tCCLK:
0x0 2 CCLK cycles write access time.
n (n + 2) CCLK cycle write access time.
0x1F 33 CCLK cycle write access time (POR reset value).
defined.
5.11.11 Static Memory Extended Wait Register (EMCStaticExtendedWait -

0xFFE0 8080)
The EMCStaticExtendedWait register times long static memory read and write transfers
(which are longer that can be supported by the EMCStaticWaitRd[n] or
EMCStaticWaitWr[n] registers) when the EW bit of one of the EMCStaticConfig registers is
enabled. There is only a single EMCStaticExtendedWait Register. This is used by the
relevant static memory chip select if the appropriate ExtendedWait (EW) bit in the
EMCStaticConfig Register is set. It is recommended that this register is modified during

system initialization, or when there are no current or outstanding transactions. However, if

necessary, these control bits can be altered during normal operation. This register is
accessed with one wait state.
Table 70 shows the bit assignments for the EMCStaticExtendedWait register.
Table 70. Static Memory Extended Wait register (EMCStaticExtendedWait - address

Value
9:0 EXTENDEDWAIT External wait time out in terms of the CCLK clock 0x000
cycles. The delay is (EXTENDWAIT + 1) x 16 x tCCLK
0x0 16 CCLK clock cycles (POR reset value).
n (n+1) x 16 CCLK clock cycles.
0x3F (0x3F+1) x 16 CCLK clock cycles.
not defined.
For example, for a static memory read/write transfer time of 16 μs, and a CCLK frequency
of 50 MHz, the following value must be programmed into this register:
–6 6
16  10  50  10
-------------------------------------------------- – 1 = 49
16
5.11.12 Static Memory Turn Round Delay Registers (EMCStaticWaitTurn0-1 -

0xFFE0 8218, 238, 258, 278)
The EMCStaticWaitTurn0-1 Registers enable you to program the number of bus
turnaround cycles. It is recommended that these registers are modified during system
ensured by waiting until the EMC is idle, and then entering low-power, or disabled mode.
These registers are accessed with one wait state.
Table 71 shows the bit assignments for the EMCStaticWaitTurn0-1 Registers.
Table 71. Static Memory Turn Round Delay registers0-1 (EMCStaticWaitTurn0-1- addresses
Value
3:0 WAITTURN Bus turnaround cycles in terms of the CCLK clock cycles.
Bus turnaround time is (WAITTURN + 1) x tCCLK.
0 1 CCLK clock cycle turnaround cycles
n (n + 1) CCLK clock cycles turnaround cycle. 0xF
0xF 16 CCLK turnaround cycles (POR reset value).
defined.

To prevent bus contention on the external memory data bus, the WAITTURN field controls
the number of bus turnaround cycles added between static memory read and write
accesses. The WAITTURN field also controls the number of turnaround cycles between
static memory accesses.
5.12 External memory interface

Shown in Figure 21 is the external memory interfacing for an 8-bit bank width.
8 bit wide memory banks do require all address lines down to A0. See Section 9.5.9 for
configuring pins for address lines.
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 memory chip used in the
external memory interface.
CS
OE
CE
OE
BLS[0] WE
D[7:0] IO[7:0]
A[a_m:0]
A[a_b:0]
Fig 21. 8-bit bank external memory interface

UM10211
Chapter 6: LPC23XX Vectored Interrupt Controller (VIC)

See Table 2 for peripherals that are not implemented in all LPC23XX parts. The
corresponding interrupt signals are reserved.
6.2 Features
• ARM PrimeCell Vectored Interrupt Controller
• Mapped to AHB address space for fast access
• Supports 32 vectored IRQ interrupts
• 16 programmable interrupt priority levels
• Fixed hardware priority within each programmable priority level
• Hardware priority level masking
• Any input can be assigned as an FIQ interrupt
• Software interrupt generation
6.3 Description
The ARM processor core has two interrupt inputs called Interrupt Request (IRQ) and Fast
Interrupt reQuest (FIQ). The Vectored Interrupt Controller (VIC) takes 32 interrupt request
inputs and programmably assigns them as FIQ or vectored IRQ types. 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 highest 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 possible 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 sources are requesting an
interrupt.
Vectored IRQ’s, which include all interrupt requests that are not classified as FIQs, have a
programmable interrupt priority. When more than one interrupt is assigned the same
priority and occur simultaneously, the one connected to the lowest numbered VIC channel
(see Table 86 on page 92) will be serviced first.
The VIC ORs the requests from all of the 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 to the address supplied by that register.

The VIC implements the registers shown in Table 72. More detailed descriptions follow.

Table 72. VIC register map

value[1]
VICIRQStatus IRQ Status Register. This register reads out the state of those RO 0 0xFFFF F000
interrupt requests that are enabled and classified as IRQ.
VICFIQStatus FIQ Status Requests. This register reads out the state of those RO 0 0xFFFF F004
interrupt requests that are enabled and classified as FIQ.
VICRawIntr Raw Interrupt Status Register. This register reads out the state of RO - 0xFFFF F008
the 32 interrupt requests / software interrupts, regardless of
enabling or classification.
VICIntSelect Interrupt Select Register. This register classifies each of the 32 R/W 0 0xFFFF F00C
interrupt requests as contributing to FIQ or IRQ.
VICIntEnable Interrupt Enable Register. This register controls which of the 32 R/W 0 0xFFFF F010
interrupt requests and software interrupts are enabled to
contribute to FIQ or IRQ.
VICIntEnClr Interrupt Enable Clear Register. This register allows software to WO - 0xFFFF F014
clear one or more bits in the Interrupt Enable register.
VICSoftInt Software Interrupt Register. The contents of this register are R/W 0 0xFFFF F018
ORed with the 32 interrupt requests from various peripheral
functions.
VICSoftIntClear Software Interrupt Clear Register. This register allows software WO - 0xFFFF F01C
to clear one or more bits in the Software Interrupt register.
VICProtection Protection enable register. This register allows limiting access to R/W 0 0xFFFF F020
the VIC registers by software running in privileged mode.
VICSWPriorityMask Software Priority Mask Register. Allows masking individual R/W 0xFFFF 0xFFFF F024
interrupt priority levels in any combination.
VICVectAddr0 Vector address 0 register. Vector Address Registers 0-31 hold R/W 0 0xFFFF F100
the addresses of the Interrupt Service routines (ISRs) for the 32
vectored IRQ slots.
VICVectAddr1 Vector address 1 register. R/W 0 0xFFFF F104
VICVectAddr3 Vector address 3 register. R/W 0 0xFFFF F10C


value[1]
VICVectPriority0 Vector priority 0 register. Vector Priority Registers 0-31. Each of R/W 0xF 0xFFFF F200
these registers designates the priority of the corresponding
vectored IRQ slot.
VICVectPriority1 Vector priority 1 register. R/W 0xF 0xFFFF F204
VICVectPriority3 Vector priority 3 register. R/W 0xF 0xFFFF F20C


value[1]
VICAddress Vector address register. When an IRQ interrupt occurs, the R/W 0 0xFFFF FF00
Vector Address Register holds the address of the currently
active interrupt.
6.5 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.
6.5.1 Software Interrupt Register (VICSoftInt - 0xFFFF F018)

The VICSoftInt register is used to generate software interrupts. The contents of this
register are ORed with the 32 interrupt requests from the various peripherals, before any
other logic is applied.
Table 73. Software Interrupt register (VICSoftInt - address 0xFFFF F018) bit description
value
31:0 See Table 87 0 Do not force the interrupt request with this bit number. Writing zeroes to bits 0
“Interrupt sources in VICSoftInt has no effect, see VICSoftIntClear (Section 6.5.2).
bit allocation 1 Force the interrupt request with this bit number.
table”.
6.5.2 Software Interrupt Clear Register (VICSoftIntClear - 0xFFFF F01C)

The VICSoftIntClear register is a ’Write Only’ register. This register allows software to
clear one or more bits in the Software Interrupt register, without having to first read it.
Table 74. Software Interrupt Clear register (VICSoftIntClear - address 0xFFFF F01C) bit description
value
31:0 See Table 87 0 Writing a 0 leaves the corresponding bit in VICSoftInt unchanged. 0
“Interrupt sources 1 Writing a 1 clears the corresponding bit in the Software Interrupt register,
bit allocation table”. removing any interrupt that may have been generated by that bit.

6.5.3 Raw 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, regardless of enabling or classification.
Table 75. Raw Interrupt Status register (VICRawIntr - address 0xFFFF F008) bit description
value
31:0 See Table 87 0 Neither the hardware nor software interrupt request with this -
“Interrupt bit number are asserted.
sources bit 1 The hardware or software interrupt request with this bit
allocation number is asserted.
table”.
6.5.4 Interrupt Enable Register (VICIntEnable - 0xFFFF F010)

This is a read/write accessible register. This register controls which of the 32 combined
hardware and software interrupt requests are enabled to contribute to FIQ or IRQ.
Table 76. Interrupt Enable register (VICIntEnable - address 0xFFFF F010) bit description
value
31:0 See Table 87 When this register is read, 1s indicate interrupt requests or software 0
“Interrupt interrupts that are enabled to contribute to FIQ or IRQ.
sources bit When this register is written, ones enable interrupt requests or
allocation software interrupts to contribute to FIQ or IRQ, zeroes have no
table”. effect. See Section 6.5.5 “Interrupt Enable Clear Register
(VICIntEnClear - 0xFFFF F014)” on page 89 and Table 77 below for
how to disable interrupts.
6.5.5 Interrupt Enable Clear Register (VICIntEnClear - 0xFFFF F014)

This is a write only register. This register allows software to clear one or more bits in the
Interrupt Enable register (see Section 6.5.4 “Interrupt Enable Register (VICIntEnable -
0xFFFF F010)” on page 89), without having to first read it.
Table 77. Interrupt Enable Clear register (VICIntEnClear - address 0xFFFF F014) bit
description
value
31:0 See Table 87 0 Writing a 0 leaves the corresponding bit in VICIntEnable -
“Interrupt unchanged.
sources bit 1 Writing a 1 clears the corresponding bit in the Interrupt
allocation Enable register, thus disabling interrupts for this request.
table”.
6.5.6 Interrupt Select Register (VICIntSelect - 0xFFFF F00C)

This is a read/write accessible register. This register classifies each of the 32 interrupt
requests as contributing to FIQ or IRQ.

Table 78. Interrupt Select register (VICIntSelect - address 0xFFFF F00C) bit description
value
31:0 See Table 87 0 The interrupt request with this bit number is assigned to the 0
“Interrupt IRQ category.
sources bit 1 The interrupt request with this bit number is assigned to the
allocation FIQ category.
table”.
6.5.7 IRQ 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.
Table 79. IRQ Status register (VICIRQStatus - address 0xFFFF F000) bit description
value
31:0 See Table 87 A bit read as 1 indicates a corresponding interrupt request being 0
“Interrupt enabled, classified as IRQ, and asserted
sources bit
allocation
table”.
6.5.8 FIQ 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 80. FIQ Status register (VICFIQStatus - address 0xFFFF F004) bit description
value
31:0 See Table 87 A bit read as 1 indicates a corresponding interrupt request being 0
“Interrupt enabled, classified as IRQ, and asserted
sources bit
allocation
table”.
6.5.9 Vector Address Registers 0-31 (VICVectAddr0-31 - 0xFFFF F100 to

17C)
These are read/write accessible registers. These registers hold the addresses of the
Interrupt Service routines (ISRs) for the 32 vectored IRQ slots.
Table 81. Vector Address registers 0-31 (VICVectAddr0-31 - addresses 0xFFFF F100 to
0xFFFF F17C) bit description
Bit Symbol Description Reset value
31:0 VICVectAddr The VIC provides the contents of one of these registers in 0x0000 0000
response to a read of the Vector Address register (VICAddress
see Section 6.5.9). The contents of the specific VICVectAddr
register (one of the 32 VICVectAddr registers) that
corresponds to the interrupt that is to be serviced is read from
VICAddress whenever an interrupt occurs.

6.5.10 Vector Priority Registers 0-31 (VICVectPriority0-31 - 0xFFFF F200 to

27C)
These registers select a priority level for the 32 vectored IRQs. There are 16 priority
levels, corresponding to the values 0 through 15 decimal, of which 15 is the lowest priority.
The reset value of these registers defaults all interrupt to the lowest priority, allowing a
single write to elevate the priority of an individual interrupt.
Table 82. Vector Priority registers 0-31 (VICVectPriority0-31 - addresses 0xFFFF F200 to
0xFFFF F27C) bit description
value
3:0 VICVectPriority Selects one of 16 priority levels for the corresponding vectored 0xF
interrupt.
6.5.11 Vector Address Register (VICAddress - 0xFFFF FF00)

When an IRQ interrupt occurs, the address of the Interrupt Service Routine (ISR) for the
interrupt that is to be serviced can be read from this register. The address supplied is from
one of the Vector Address Registers (VICVectAddr0-31).
Table 83. Vector Address register (VICAddress - address 0xFFFF FF00) bit description
value
31:0 VICAddress Contains the address of the ISR for the currently active interrupt. This 0
register must be written (with any value) at the end of an ISR, to
update the VIC priority hardware. Writing to the register at any other
time can cause incorrect operation.
6.5.12 Software Priority Mask Register (VICSWPriorityMask - 0xFFFF F024)

The Software Priority Mask Register contains individual mask bits for the 16 interrupt
priority levels.
Table 84. Software Priority Mask register (VICSWPriorityMask - address 0xFFFF F024) bit
description
value
15:0 VICSWPriorityMask 0 Interrupt priority level is masked. 0xFFFF
1 Interrupt priority level is not masked.
not defined.
6.5.13 Protection Enable Register (VICProtection - 0xFFFF F020)

This is a read/write accessible register. This one bit register controls access to the VIC
registers by software running in User mode. The VICProtection register itself can only be
accessed in privileged mode.

Table 85. Protection Enable register (VICProtection - address 0xFFFF F020) bit description
value
0 VIC_access 0 VIC registers can be accessed in User or privileged mode. 0
1 The VIC registers can only be accessed in privileged mode.
6.6 Interrupt sources

Table 86 lists the interrupt sources for each peripheral function. Each peripheral device
may have one or more interrupt lines to the Vectored Interrupt Controller. Each line may
represent more than one interrupt source. There is no significance or priority about what
line is connected where, except for certain standards from ARM.
Table 86. Connection of interrupt sources to the Vectored Interrupt Controller

Block Flag(s) VIC Channel # and
Hex Mask
WDT Watchdog Interrupt (WDINT) 0 0x0000 0001
- Reserved for Software Interrupts only 1 0x0000 0002
ARM Core Embedded ICE, DbgCommRx 2 0x0000 0004
ARM Core Embedded ICE, DbgCommTX 3 0x0000 0008
TIMER0 Match 0 - 1 (MR0, MR1) 4 0x0000 0010
Capture 0 - 1 (CR0, CR1)
TIMER1 Match 0 - 2 (MR0, MR1, MR2) 5 0x0000 0020
Capture 0 - 1 (CR0, CR1)
UART0 Rx Line Status (RLS) 6 0x0000 0040
Transmit Holding Register Empty (THRE)
Rx Data Available (RDA)
Character Time-out Indicator (CTI)
End of Auto-Baud (ABEO)
Auto-Baud Time-Out (ABTO)
UART1 Rx Line Status (RLS) 7 0x0000 0080
Modem Control Change
PWM1 Match 0 - 6 of PWM1 8 0x0000 0100
Capture 0-1 of PWM1
I2C0 SI (state change) 9 0x0000 0200


Hex Mask
SPI, SSP0 SPI Interrupt Flag of SPI (SPIF) 10 0x0000 0400
Mode Fault of SPI0 (MODF)
Tx FIFO half empty of SSP0
Rx FIFO half full of SSP0
Rx Time-out of SSP0
Rx Overrun of SSP0
SSP 1 Tx FIFO half empty 11 0x0000 0800
Rx FIFO half full
Rx Timeout
Rx Overrun
PLL PLL Lock (PLOCK) 12 0x0000 1000
RTC Counter Increment (RTCCIF) 13 0x0000 2000
Alarm (RTCALF)
Subsecond Int (RTCSSF)
System External Interrupt 0 (EINT0) 14 0x0000 4000
Control External Interrupt 1 (EINT1) 15 0x0000 8000
(External
Interrupts) External Interrupt 2 (EINT2) 16 0x0001 0000
External Interrupt 3 (EINT3). 17 0x0002 0000
Note: EINT3 channel is shared with GPIO interrupts
ADC0 A/D Converter 0 end of conversion 18 0x0004 0000
BOD Brown Out detect 20 0x0010 0000
Ethernet[1] WakeupInt, SoftInt, TxDoneInt, TxFinishedInt, 21 0x0020 0000
TxErrorInt, TxUnderrunInt, RxDoneInt,
RxFinishedInt, RxErrorInt, RxOverrunInt.
USB[2] USB_INT_REQ_LP, USB_INT_REQ_HP, 22 0x0040 0000
USB_INT_REQ_DMA
CAN[2] CAN Common, CAN 0 Tx, CAN 0 Rx, CAN 1 Tx, 23 0x0080 0000
CAN 1 Rx
SD/ MMC RxDataAvlbl, TxDataAvlbl, RxFifoEmpty, TxFifoEmpty, 24 0x0100 0000
interface[3] RxFifoFull, TxFifoFull, RxFifoHalfFull, TxFifoHalfEmpty,
RxActive, TxActive, CmdActive, DataBlockEnd, StartBitErr,
DataEnd, CmdSent, CmdRespEnd, RxOverrun,
TxUnderrun, DataTimeOut, CmdTimeOut, DataCrcFail,
CmdCrcFail
GP DMA IntStatus of DMA channel 0, IntStatus of DMA channel 1 25 0x0200 0000
Timer 2 Match 0-3 26 0x0400 0000
Capture 0-1
Timer 3 Match 0-3 27 0x0800 0000
Capture 0-1


Hex Mask
UART 2 Rx Line Status (RLS) 28 0x1000 0000
UART 3 Rx Line Status (RLS) 29 0x2000 0000
I2S irq_rx 31 0x8000 0000
irq_tx
[1] Not on LPC2361.

[2] LPC2361/62/64/66/68, LPC2378, LPC2387, and LPC2388
[3] LPC2367/68, LPC2377/78, LPC2387, LPC2388
Table 87. Interrupt sources bit allocation table

Bit 31 30 29 28 27 26 25 24
Symbol I2S I2C2 UART3 UART2 TIMER3 TIMER2 GPDMA SD/MMC
Bit 23 22 21 20 19 18 17 16
Symbol CAN1&2 USB Ethernet BOD I2C1 AD0 EINT3 EINT2
Bit 15 14 13 12 11 10 9 8
Symbol EINT1 EINT0 RTC PLL SSP1 SPI/SSP0 I2C0 PWM1
Bit 7 6 5 4 3 2 1 0
Symbol UART1 UART0 TIMER1 TIMER0 ARMCore1 ARMCore0 - WDT

interrupt request, masking, and selection
SoftIntClear IntEnableClear
[31:0] [31:0]
status registers and FIQ generation

SoftInt IntEnable FIQStatus
[31:0] [31:0] [31:0] FIQStatus FIQ
VICINT
[31:0]
SOURCE
[31:0] IRQStatus
[31:0] IRQStatus
[31:0]
RawIntr IntSelect
[31:0] [31:0]
prioritization and vector generation

vectored interrupt 0
IRQStatus SWPriorityMask [31:0] SWPriorityMask
[0] [31:0]
D Q D Q HWPriorityMask [31:0]
PRIORITY
SWPriorityMask [0] VectIRQ0
MASKING
HWPriorityMask [0]
LOGIC
PRIORITY IRQ
VectPriority0 Vect Addr0
LOGIC
[3:0] VectAddr0 [31:0]
[31:0]
vector select
vectored interrupt 1 for highest priority
VectIRQ1 interrupt
IRQStatus
[1] Vect Addr1
[31:0] Vect
VectAddr AddrOut
[31:0]
vectored interrupt 31
VectIRQ31
IRQStatus
[31] Vect Addr31
[31:0]
Fig 22. Block diagram of the Vectored Interrupt Controller

UM10211
Chapter 7: LPC23XX Memory Acceleration Module (MAM)
7.1 Introduction
The MAM block in the LPC23XX maximizes the performance of the ARM processor when
it is running code in Flash memory using a single Flash bank.
7.2 Operation
Simply put, the Memory Accelerator Module (MAM) attempts to have the next ARM
instruction that will be needed in its latches in time to prevent CPU fetch stalls. The
LPC2300 uses one bank of Flash memory, compared to the two banks used on
predecessor devices. It includes three 128 bit buffers called the Prefetch buffer, the
Branch Trail Buffer and the data buffer. When an Instruction Fetch is not satisfied by either
the Prefetch or Branch Trail buffer, nor has a prefetch been initiated for that line, the ARM
is stalled while a fetch is initiated for the 128 bit line. If a prefetch has been initiated but not
yet completed, the ARM is stalled for a shorter time. Unless aborted by a data access, a
prefetch is initiated as soon as the Flash has completed the previous access. The
prefetched line is latched by the Flash module, but the MAM does not capture the line in
its prefetch buffer until the ARM core presents the address from which the prefetch has
been made. If the core presents a different address from the one from which the prefetch
has been made, the prefetched line is discarded.
The prefetch and Branch Trail buffers each include four 32 bit ARM instructions or eight
16 bit Thumb instructions. During sequential code execution, typically the prefetch buffer
contains the current instruction and the entire Flash line that contains it.
The MAM uses the LPROT[0] line to differentiate between instruction and data accesses.
Code and data accesses use separate 128 bit buffers. 3 of every 4 sequential 32 bit code
or data accesses "hit" in the buffer without requiring a Flash access (7 of 8 sequential
16 bit accesses, 15 of every 16 sequential byte accesses). The fourth (eighth, 16th)
sequential data access must access Flash, aborting any prefetch in progress. When a
Flash data access is concluded, any prefetch that had been in progress is re-initiated.
Timing of Flash read operations is programmable and is described later in this section.
In this manner, there is no code fetch penalty for sequential instruction execution when the
CPU clock period is greater than or equal to one fourth of the Flash access time. The
average amount of time spent doing program branches is relatively small (less than 25%)
and may be minimized in ARM (rather than Thumb) code through the use of the
conditional execution feature present in all ARM instructions. This conditional execution
may often be used to avoid small forward branches that would otherwise be necessary.
Branches and other program flow changes cause a break in the sequential flow of
instruction fetches described above. The Branch Trail buffer captures the line to which
such a non-sequential break occurs. If the same branch is taken again, the next
instruction is taken from the Branch Trail buffer. When a branch outside the contents of the
prefetch and Branch Trail buffer is taken, a stall of several clocks is needed to load the
Branch Trail buffer. Subsequently, there will typically be no further instruction fetch delays
until a new and different branch occurs.

If an attempt is made to write directly to the Flash memory, without using the normal Flash
programming interface, the MAM generates a data abort.
7.3 Memory Acceleration Module blocks

The Memory Accelerator Module is divided into several functional blocks:
• A Flash Address Latch and an incrementor function to form prefetch addresses

• A 128 bit prefetch buffer and an associated Address latch and comparator
• A 128 bit Branch Trail buffer and an associated Address latch and comparator
• A 128 bit Data buffer and an associated Address latch and comparator
• Control logic
• Wait logic
Figure 23 shows a simplified block diagram of the Memory Accelerator Module data
paths.
In the following descriptions, the term “fetch” applies to an explicit Flash read request from
the ARM. “Pre-fetch” is used to denote a Flash read of instructions beyond the current
processor fetch address.
7.3.1 Flash memory bank

There is one bank of Flash memory with the LPC2300 MAM.
Flash programming operations are not controlled by the MAM, but are handled as a
separate function. A “boot block” sector contains Flash programming algorithms that may
be called as part of the application program, and a loader that may be run to allow serial
programming of the Flash memory.
MEMORY ADDRESS
FLASH MEMORY BANK
BUS
ARM LOCAL BUS
INTERFACE
BUFFERS
Fig 23. Simplified block diagram of the Memory Accelerator Module

7.3.2 Instruction latches and data latches

Code and Data accesses are treated separately by the Memory Accelerator Module.
There is a 128 bit Latch, a 15 bit Address Latch, and a 15 bit comparator associated with
each buffer (prefetch, branch trail, and data). Each 128 bit latch holds 4 words (4 ARM
instructions, or 8 Thumb instructions).
Also associated with each buffer are 32 4:1 Multiplexers that select the requested word
from the 128 bit line.
7.3.3 Flash programming Issues

Since the Flash memory does not allow accesses during programming and erase
operations, it is necessary for the MAM to force the CPU to wait if a memory access to a
Flash address is requested while the Flash module is busy. (This is accomplished by
asserting the ARM7TDMI-S local bus signal CLKEN.) Under some conditions, this delay
could result in a Watchdog time-out. The user will need to be aware of this possibility and
take steps to insure that an unwanted Watchdog reset does not cause a system failure
while programming or erasing the Flash memory.
In order to preclude the possibility of stale data being read from the Flash memory, the
LPC2300 MAM holding latches are automatically invalidated at the beginning of any Flash
programming or erase operation. Any subsequent read from a Flash address will cause a
new fetch to be initiated after the Flash operation has completed.
7.4 Memory Accelerator Module Operating modes

Three modes of operation are defined for the MAM, trading off performance for ease of
predictability:
Mode 0: MAM off. All memory requests result in a Flash read operation (see note 2
below). There are no instruction prefetches.
Mode 1: MAM partially enabled. Sequential instruction accesses are fulfilled from the
holding latches if the data is present. Instruction prefetch is enabled. Non-sequential
instruction accesses initiate Flash read operations (see Table note 2). This means that
all branches cause memory fetches. All data operations cause a Flash read because
buffered data access timing is hard to predict and is very situation dependent.
Mode 2: MAM fully enabled. Any memory request (code or data) for a value that is
contained in one of the corresponding holding latches is fulfilled from the latch.
Instruction prefetch is enabled. Flash read operations are initiated for instruction
prefetch and code or data values not available in the corresponding holding latches.
Table 88. MAM responses to program accesses of various types

Program Memory Request Type MAM Mode
0 1 2
Sequential access, data in latches Initiate Fetch[2] Use Latched Use Latched
Data[1] Data[1]

Table 88. MAM responses to program accesses of various types

Program Memory Request Type MAM Mode
0 1 2
Sequential access, data not in latches Initiate Fetch Initiate Fetch[1] Initiate Fetch[1]
Non-sequential access, data in latches Initiate Fetch[2] Initiate Fetch[1][2] Use Latched
Data[1]
Non-sequential access, data not in Initiate Fetch Initiate Fetch[1] Initiate Fetch[1]
latches
[1] Instruction prefetch is enabled in modes 1 and 2.

[2] The MAM actually uses latched data if it is available, but mimics the timing of a Flash read operation. This
saves power while resulting in the same execution timing. The MAM can truly be turned off by setting the
fetch timing value in MAMTIM to one clock.
Table 89. MAM responses to data and DMA accesses of various types
Data Memory Request Type MAM Mode
0 1 2
Sequential access, data in latches Initiate Fetch[1] Initiate Fetch[1] Use Latched
Data
Sequential access, data not in latches Initiate Fetch Initiate Fetch Initiate Fetch
Non-sequential access, data in latches Initiate Fetch[1] Initiate Fetch[1] Use Latched
Data
Non-sequential access, data not in latches Initiate Fetch Initiate Fetch Initiate Fetch
[1] The MAM actually uses latched data if it is available, but mimics the timing of a Flash read operation. This
saves power while resulting in the same execution timing. The MAM can truly be turned off by setting the
fetch timing value in MAMTIM to one clock.
7.5 MAM configuration

After reset the MAM defaults to the disabled state. Software can turn memory access
acceleration on or off at any time. This allows most of an application to be run at the
highest possible performance, while certain functions can be run at a somewhat slower
but more predictable rate if more precise timing is required.

The MAM is controlled by the registers shown in Table 90. More detailed descriptions
follow. Writes to any unused bits are ignored. A read of any unused bits will return a logic
zero.

Table 90. Summary of Memory Acceleration Module registers

value[1]
MAMCR Memory Accelerator Module Control Register. R/W 0x0 0xE01F C000
Determines the MAM functional mode, that is, to
what extent the MAM performance enhancements
are enabled. See Table 91.
MAMTIM Memory Accelerator Module Timing control. R/W 0x07 0xE01F C004
Determines the number of clocks used for Flash
memory fetches (1 to 7 processor clocks).
7.7 MAM Control Register (MAMCR - 0xE01F C000)

Two configuration bits select the three MAM operating modes, as shown in Table 91.
Following any reset, MAM functions are disabled. Software can turn memory access
acceleration on or off at any time allowing most of an application to be run at the highest
possible performance, while certain functions can be run at a somewhat slower but more
predictable rate if more precise timing is required.
Changing the MAM operating mode causes the MAM to invalidate all of the holding
latches, resulting in new reads of Flash information as required. This guarantees
synchronization of the MAM to CPU operation.
Table 91. MAM Control Register (MAMCR - address 0xE01F C000) bit description
value
1:0 MAM_mode These bits determine the operating mode of the MAM. 0
_control 00 MAM functions disabled
01 MAM functions partially enabled
10 MAM functions fully enabled
11 Reserved. Not to be used in the application.
7:2 - - Unused, always 0. 0
7.8 MAM Timing Register (MAMTIM - 0xE01F C004)

The MAM Timing register determines how many CCLK cycles are used to access the
Flash memory. This allows tuning MAM timing to match the processor operating
frequency. Flash access times from 1 clock to 7 clocks are possible. Single clock Flash
accesses would essentially remove the MAM from timing calculations. In this case the
MAM mode may be selected to optimize power usage.

Table 92. MAM Timing register (MAMTIM - address 0xE01F C004) bit description
value
2:0 MAM_fetch_ These bits set the duration of MAM fetch operations. 07
cycle_timing 000 0 - Reserved
001 1 - MAM fetch cycles are 1 processor clock (CCLK) in
duration
010 2 - MAM fetch cycles are 2 CCLKs in duration
Warning: These bits set the duration of MAM Flash fetch operations
as listed here. Improper setting of this value may result in incorrect
operation of the device.
7:3 - - Unused, always 0 0

xFFE0 xFFE4 xFFE8 xFFEC

INCREMENTOR
30000 30004 30008 3000C
20000 20004 20008 2000C

MUX D Q
ENAL0 10000 10004 10008 1000C
EN
ADDR 0FFF0 0FFF4 0FFF8 0FFFC
cclk
[18:4] 00020 00024 00028 0002C

00010 00014 00018 0001C
00000 00004 00008 0000C
=
EQA0
128
ENP ENBT END

ADDR PREFETCH LATCH ADDR BT LATCH ADDR DATA LATCH
= = =
128 128 128
EQPREF EQBT EQD
LA[3:2] PREFETCH MUX BT MUX DATA MUX

32 32 32
FINAL MUX
DI[31:0] (to ARM core)
Fig 24. Block diagram of the Memory Accelerator Module
7.9 MAM usage notes

When changing MAM timing, the MAM must first be turned off by writing a zero to
MAMCR. A new value may then be written to MAMTIM. Finally, the MAM may be turned
on again by writing a value (1 or 2) corresponding to the desired operating mode to
MAMCR.
For a system clock slower than 20 MHz, MAMTIM can be 001. For a system clock
between 20 MHz and 40 MHz, flash access time is suggested to be 2 CCLKs, while in
systems with a system clock faster than 40 MHz, 3 CCLKs are proposed. For system
clocks of 60 MHz and above, 4CCLK’s are needed.

Table 93. Suggestions for MAM timing selection

system clock Number of MAM fetch cycles in MAMTIM
(see Table 92)
< 20 MHz 1 CCLK
20 MHz to 40 MHz 2 CCLK
40 MHz to 60 MHz 3 CCLK
> 60 MHz 4 CCLK

UM10211
Chapter 8: LPC23XX Pin configuration
8.1 Overview
Table 94. LPC23xx pinning overview
Part Package Pin configuration
LPC2361/62 LQFP: Figure 25 Table 95
LPC2364/65/66/67/68 LQFP: Figure 26 Table 97
TFBGA: Figure 27 Table 96, Table 97
LPC2377/78 LQFP: Figure 28 Table 98
LPC2387 LQFP: Figure 28 Table 99
LPC2388 LQFP: Figure 30 Table 100
8.2 LPC2361/62 100-pin packages 100
1 76 75
LPC2361FBD100
LPC2362FBD100
25 51
26
50
002aad965
Fig 25. LPC2361/62 pinning
Table 95. LPC2361/62 pin description

Symbol Pin Type Description
P0[0] to P0[31] I/O Port 0: Port 0 is a 32-bit I/O port with individual direction controls for each bit.
The operation of port 0 pins depends upon the pin function selected via the pin
connect block. Pins 12, 13, 14, and 31 of this port are not available.
P0[0]/RD1/TXD3/ 46[1] I/O P0[0] — General purpose digital input/output pin.
SDA1 I RD1 — CAN1 receiver input.
O TXD3 — Transmitter output for UART3.
I/O SDA1 — I2C1 data input/output (this is not an open-drain pin).
P0[1]/TD1/RXD3/ 47[1] I/O P0[1] — General purpose digital input/output pin.
SCL1 O TD1 — CAN1 transmitter output.
I RXD3 — Receiver input for UART3.
I/O SCL1 — I2C1 clock input/output (this is not an open-drain pin).
P0[2]/TXD0 98[1] I/O P0[2] — General purpose digital input/output pin.

Table 95. LPC2361/62 pin description …continued

P0[3]/RXD0 99[1] I/O P0[3] — General purpose digital input/output pin.
P0[4]/I2SRX_CLK/ 81[1] I/O P0[4] — General purpose digital input/output pin.
RD2/CAP2[0] I/O I2SRX_CLK — Receive Clock. It is driven by the master and received by the
slave. Corresponds to the signal SCK in the I2S-bus specification.
I RD2 — CAN2 receiver input.
I CAP2[0] — Capture input for Timer 2, channel 0.
P0[5]/I2SRX_WS/ 80[1] I/O P0[5] — General purpose digital input/output pin.
TD2/CAP2[1] I/O I2SRX_WS — Receive Word Select. It is driven by the master and received by
the slave. Corresponds to the signal WS in the I2S-bus specification.
O TD2 — CAN2 transmitter output.
P0[6]/I2SRX_SDA/ 79[1] I/O P0[6] — General purpose digital input/output pin.
SSEL1/MAT2[0] I/O I2SRX_SDA — Receive data. It is driven by the transmitter and read by the
receiver. Corresponds to the signal SD in the I2S-bus specification.
I/O SSEL1 — Slave Select for SSP1.
O MAT2[0] — Match output for Timer 2, channel 0.
P0[7]/I2STX_CLK/ 78[1] I/O P0[7] — General purpose digital input/output pin.
SCK1/MAT2[1] I/O I2STX_CLK — Transmit Clock. It is driven by the master and received by the
I/O SCK1 — Serial Clock for SSP1.
P0[8]/I2STX_WS/ 77[1] I/O P0[8] — General purpose digital input/output pin.
MISO1/MAT2[2] I/O I2STX_WS — Transmit Word Select. It is driven by the master and received by
I/O MISO1 — Master In Slave Out for SSP1.
P0[9]/I2STX_SDA/ 76[1] I/O P0[9] — General purpose digital input/output pin.
MOSI1/MAT2[3] I/O I2STX_SDA — Transmit data. It is driven by the transmitter and read by the
I/O MOSI1 — Master Out Slave In for SSP1.
P0[10]/TXD2/ 48[1] I/O P0[10] — General purpose digital input/output pin.
SDA2/MAT3[0] O TXD2 — Transmitter output for UART2.
P0[11]/RXD2/ 49[1] I/O P0[11] — General purpose digital input/output pin.
SCL2/MAT3[1] I RXD2 — Receiver input for UART2.


SCK0/SCK O TXD1 — Transmitter output for UART1.
I/O SCK0 — Serial clock for SSP0.
I/O SCK — Serial clock for SPI.
SSEL0/SSEL I RXD1 — Receiver input for UART1.
I/O SSEL — Slave Select for SPI.
P0[17]/CTS1/ 61[1] I/O P0[17] — General purpose digital input/output pin.
MISO0/MISO I CTS1 — Clear to Send input for UART1.
I/O MISO — Master In Slave Out for SPI.
P0[18]/DCD1/ 60[1] I/O P0[18] — General purpose digital input/output pin.
MOSI0/MOSI I DCD1 — Data Carrier Detect input for UART1.
I/O MOSI — Master Out Slave In for SPI.
P0[19]/DSR1/ 59[1] I/O P0[19] — General purpose digital input/output pin.
MCICLK/SDA1 I DSR1 — Data Set Ready input for UART1.
O MCICLK — Clock output line for SD/MMC interface.
P0[20]/DTR1/ 58[1] I/O P0[20] — General purpose digital input/output pin.
MCICMD/SCL1 O DTR1 — Data Terminal Ready output for UART1.
I MCICMD — Command line for SD/MMC interface.
P0[21]/RI1/ 57[1] I/O P0[21] — General purpose digital input/output pin.
MCIPWR/RD1 I RI1 — Ring Indicator input for UART1.
O MCIPWR — Power Supply Enable for external SD/MMC power supply.
P0[22]/RTS1/ 56[1] I/O P0[22] — General purpose digital input/output pin.
MCIDAT0/TD1 O RTS1 — Request to Send output for UART1.
O MCIDAT0 — Data line for SD/MMC interface.
P0[23]/AD0[0]/ 9[2] I/O P0[23] — General purpose digital input/output pin.
I2SRX_CLK/ I AD0[0] — A/D converter 0, input 0.
CAP3[0]
I/O I2SRX_CLK — Receive Clock. It is driven by the master and received by the


I2SRX_WS/ I AD0[1] — A/D converter 0, input 1.
CAP3[1]
I/O I2SRX_WS — Receive Word Select. It is driven by the master and received by
I2SRX_SDA/ I AD0[2] — A/D converter 0, input 2.
TXD3
I/O I2SRX_SDA — Receive data. It is driven by the transmitter and read by the
AOUT/RXD3 I AD0[3] — A/D converter 0, input 3.
O AOUT — D/A converter output.
P0[27]/SDA0 25[4] I/O P0[27] — General purpose digital input/output pin.
I/O SDA0 — I2C0 data input/output. Open-drain output (for I2C-bus compliance).
P0[28]/SCL0 24[4] I/O P0[28] — General purpose digital input/output pin.
I/O SCL0 — I2C0 clock input/output. Open-drain output (for I2C-bus compliance).
P0[29]/USB_D+ 29[5] I/O P0[29] — General purpose digital input/output pin.
I/O USB_D+ — USB bidirectional D+ line.
P0[30]/USB_D 30[5] I/O P0[30] — General purpose digital input/output pin.
I/O USB_D — USB bidirectional D line.
connect block. Pins 2, 3, 5, 6, 7, 11, 12, and 13 of this port are not available.
P1[0]/ENET_TXD0 95[1] I/O P1[0] — General purpose digital input/output pin.
O ENET_TXD0 — Ethernet transmit data 0.
P1[4]/ENET_TX_EN 93[1] I/O P1[4] — General purpose digital input/output pin.
O ENET_TX_EN — Ethernet transmit data enable.
P1[8]/ENET_CRS 92[1] I/O P1[8] — General purpose digital input/output pin.
I ENET_CRS — Ethernet carrier sense.
P1[9]/ENET_RXD0 91[1] I/O P1[9] — General purpose digital input/output pin.
I ENET_RXD0 — Ethernet receive data.
P1[14]/ 89[1] I/O P1[14] — General purpose digital input/output pin.
ENET_RX_ER I ENET_RX_ER — Ethernet receive error.
ENET_REF_CLK I ENET_REF_CLK/ENET_RX_CLK — Ethernet receiver clock.


P1[16]/ENET_MDC 87[1] I/O P1[16] — General purpose digital input/output pin.
O ENET_MDC — Ethernet MIIM clock.
P1[17]/ENET_MDIO 86[1] I/O P1[17] — General purpose digital input/output pin.
I/O ENET_MDIO — Ethernet MIIM data input and output.
USB_UP_LED/ O USB_UP_LED — USB GoodLink LED indicator. It is LOW when device is
PWM1[1]/ configured (non-control endpoints enabled). It is HIGH when the device is not
CAP1[0] configured or during global suspend.
O PWM1[1] — Pulse Width Modulator 1, channel 1 output.
USB_TX_E1/ O USB_TX_E1 — Transmit Enable signal for USB port 1 (OTG transceiver).
USB_PPWR1/
CAP1[1] O USB_PPWR1 — Port Power enable signal for USB port 1.
USB_TX_DP1/ O USB_TX_DP1 — D+ transmit data for USB port 1 (OTG transceiver).
PWM1[2]/SCK0
USB_TX_DM1/ O USB_TX_DM1 — D transmit data for USB port 1 (OTG transceiver).
PWM1[3]/SSEL0
USB_RCV1/ I USB_RCV1 — Differential receive data for USB port 1 (OTG transceiver).
USB_PWRD1/
MAT1[0] I USB_PWRD1 — Power Status for USB port 1 (host power switch).
USB_RX_DP1/ I USB_RX_DP1 — D+ receive data for USB port 1 (OTG transceiver).
PWM1[4]/MISO0
USB_RX_DM1/ I USB_RX_DM1 — D receive data for USB port 1 (OTG transceiver).
PWM1[5]/MOSI0
I/O MOSI0 — Master Out Slave in for SSP0.
USB_LS1/ O USB_LS1 — Low-speed status for USB port 1 (OTG transceiver).
USB_HSTEN1/
MAT1[1] O USB_HSTEN1 — Host Enabled status for USB port 1.


USB_SSPND1/ O USB_SSPND1 — USB port 1 bus suspend status (OTG transceiver).
PWM1[6]/
CAP0[0] O PWM1[6] — Pulse Width Modulator 1, channel 6 output.
USB_INT1/ I USB_INT1 — USB port 1 OTG transceiver interrupt (OTG transceiver).
USB_OVRCR1/
CAP0[1] I USB_OVRCR1 — USB port 1 Over-Current status.
P1[28]/USB_SCL1/ 44[1] I/O P1[28] — General purpose digital input/output pin.
PCAP1[0]/MAT0[0] I/O USB_SCL1 — USB port 1 I2C-bus serial clock (OTG transceiver).
I PCAP1[0] — Capture input for PWM1, channel 0.
P1[29]/USB_SDA1/ 45[1] I/O P1[29] — General purpose digital input/output pin.
PCAP1[1]/MAT0[1] I/O USB_SDA1 — USB port 1 I2C-bus serial data (OTG transceiver).
P1[30]/VBUS/AD0[4] 21[2] I/O P1[30] — General purpose digital input/output pin.
I VBUS — Monitors the presence of USB bus power.
Note: This signal must be HIGH for USB reset to occur.
I AD0[4] — A/D converter 0, input 4.
P1[31]/SCK1/AD0[5] 20[2] I/O P1[31] — General purpose digital input/output pin.
connect block. Pins 14 through 31 of this port are not available.
P2[0]/PWM1[1]/ 75[1] I/O P2[0] — General purpose digital input/output pin.
TXD1/TRACECLK O PWM1[1] — Pulse Width Modulator 1, channel 1 output.
O TRACECLK — Trace Clock.
RXD1/PIPESTAT0 O PWM1[2] — Pulse Width Modulator 1, channel 2 output.
O PIPESTAT0 — Pipeline Status, bit 0.
CTS1/PIPESTAT1 O PWM1[3] — Pulse Width Modulator 1, channel 3 output.
I CTS1 — Clear to Send input for UART1.


DCD1/PIPESTAT2 O PWM1[4] — Pulse Width Modulator 1, channel 4 output.
I DCD1 — Data Carrier Detect input for UART1.
DSR1/TRACESYNC O PWM1[5] — Pulse Width Modulator 1, channel 5 output.
I DSR1 — Data Set Ready input for UART1.
O TRACESYNC — Trace Synchronization.
DTR1/TRACEPKT0 O PWM1[6] — Pulse Width Modulator 1, channel 6 output.
O DTR1 — Data Terminal Ready output for UART1.
O TRACEPKT0 — Trace Packet, bit 0.
P2[6]/PCAP1[0]/RI1/ 67[1] I/O P2[6] — General purpose digital input/output pin.
TRACEPKT1 I PCAP1[0] — Capture input for PWM1, channel 0.
I RI1 — Ring Indicator input for UART1.
P2[7]/RD2/ 66[1] I/O P2[7] — General purpose digital input/output pin.
RTS1/TRACEPKT2 I RD2 — CAN2 receiver input.
O RTS1 — Request to Send output for UART1.
P2[8]/TD2/ 65[1] I/O P2[8] — General purpose digital input/output pin.
TXD2/TRACEPKT3 O TD2 — CAN2 transmitter output.
USB_CONNECT/ O USB_CONNECT — Signal used to switch an external 1.5 k resistor under
RXD2/EXTIN0 software control. Used with the SoftConnect USB feature.
I EXTIN0 — External Trigger Input.
P2[10]/EINT0 53[6] I/O P2[10] — General purpose digital input/output pin.
Note: LOW on this pin while RESET is LOW forces on-chip bootloader to take
over control of the part after a reset.
I EINT0 — External interrupt 0 input.
P2[11]/EINT1/ 52[6] I/O P2[11] — General purpose digital input/output pin.
MCIDAT1/ I EINT1 — External interrupt 1 input.
I2STX_CLK
I/O I2STX_CLK — Transmit Clock. It is driven by the master and received by the


I2STX_WS
I/O I2STX_WS — Transmit Word Select. It is driven by the master and received by
I2STX_SDA
I/O I2STX_SDA — Transmit data. It is driven by the transmitter and read by the
connect block. Pins 0 through 24, and 27 through 31 of this port are not
available.
P3[25]/MAT0[0]/ 27[1] I/O P3[25] — General purpose digital input/output pin.
PWM1[2] O MAT0[0] — Match output for Timer 0, channel 0.
O PWM1[2] — Pulse Width Modulator 1, output 2.
connect block. Pins 0 through 27, 30, and 31 of this port are not available.
TXD3 O MAT2[0] — Match output for Timer 2, channel 0.
RXD3 O MAT2[1] — Match output for Timer 2, channel 1.
TDO 1[1] O TDO — Test Data Out for JTAG interface.
TDI 2[1] I TDI — Test Data In for JTAG interface.
TMS 3[1] I TMS — Test Mode Select for JTAG interface.
TRST 4[1] I TRST — Test Reset for JTAG interface.
TCK 5[1] I TCK — Test Clock for JTAG interface. This clock must be slower than 16 of the
CPU clock (CCLK) for the JTAG interface to operate.
RTCK 100[1] I/O RTCK — JTAG interface control signal.
Note: LOW on this pin while RESET is LOW enables ETM pins (P2[9:0]) to
operate as trace port after reset.
RSTOUT 14 O RSTOUT — This is a 3.3 V pin. LOW on this pin indicates UM10211 being in
Reset state.
Note: This pin is available in LPC2387FBD100 devices only (LQFP100
package).


RESET 17[7] I External 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.
XTAL1 22[8] I Input to the oscillator circuit and internal clock generator circuits.
XTAL2 23[8] O Output from the oscillator amplifier.
RTCX1 16[8] I Input to the RTC oscillator circuit.
RTCX2 18[8] O Output from the RTC oscillator circuit.
VSS 15, 31, I ground: 0 V reference.
41, 55,
72, 97,
83[9]
VSSA 11[10] I analog ground: 0 V reference. This should nominally be the same voltage as
VSS, but should be isolated to minimize noise and error.
VDD(3V3) 28, 54, I 3.3 V supply voltage: This is the power supply voltage for the I/O ports.
71, 96[11]
VDD(DCDC)(3V3) 13, 42, I 3.3 V DC-to-DC converter supply voltage: This is the supply voltage for the
84[12] on-chip DC-to-DC converter only.
VDDA 10[13] I analog 3.3 V pad supply voltage: This should be nominally the same voltage
as VDD(3V3) but should be isolated to minimize noise and error. This voltage is
used to power the ADC and DAC.
VREF 12[13] I ADC reference: This should be nominally the same voltage as VDD(3V3) but
should be isolated to minimize noise and error. Level on this pin is used as a
reference for ADC and DAC.
VBAT 19[13] I RTC pin power supply: 3.3 V on this pin supplies the power to the RTC
peripheral.
[1] 5 V tolerant pad providing digital I/O functions with TTL levels and hysteresis.
[2] 5 V tolerant pad providing digital I/O functions (with TTL levels and hysteresis) and analog input. When configured as a DAC input,
digital section of the pad is disabled.
[3] 5 V tolerant pad providing digital I/O with TTL levels and hysteresis and analog output function. When configured as the DAC output,
[4] Open-drain 5 V tolerant digital I/O pad, compatible with I2C-bus 400 kHz specification. This pad requires an external pull-up to provide
output functionality. When power is switched off, this pin connected to the I2C-bus is floating and does not disturb the I2C lines.
Open-drain configuration applies to all functions on this pin.
[5] Pad provides digital I/O and USB functions. It is designed in accordance with the USB specification, revision 2.0 (Full-speed and
Low-speed mode only).
[6] 5 V tolerant pad with 10 ns glitch filter providing digital I/O functions with TTL levels and hysteresis
[7] 5 V tolerant pad with 20 ns glitch filter providing digital I/O function with TTL levels and hysteresis
[8] Pad provides special analog functionality.

8.3 LPC2364/65/66/67/68 100-pin packages
100
76
1 75
LPC2364FBD100
LPC2365FBD100
LPC2366FBD100
LPC2367FBD100
LPC2368FBD100
25 51
26
50
002aac576
Fig 26. LPC2364/65/66/67/68 LQFP100 packages
ball A1
LPC2364FET100/LPC2368FET100
index area
1 2 3 4 5 6 7 8 9 10
A
B
C
D
E
F
G
H
J
K
002aad225
Transparent top view
Fig 27. LPC2364/65/66/67/68 pinning TFBGA100 package
Pin descriptions for LPC2364/65/66/67/68 and a brief explanation of their corresponding

functions are shown in the following tables.
Table 96. LPC2364/68 pin allocation table

Pin Symbol Pin Symbol Pin Symbol Pin Symbol
Row A
1 TDO 2 P0[3]/RXD0 3 VDD(3V3) 4 P1[4]/ENET_TX_EN
5 P1[10]/ENET_RXD1 6 P1[16]/ENET_MDC 7 VDD(DCDC)(3V3) 8 P0[4]/I2SRX_CLK/
RD2/CAP2[0]
9 P0[7]/I2STX_CLK/ 10 P0[9]/I2STX_SDA/ 11 - 12 -
SCK1/MAT2[1] MOSI1/MAT2[3]
Row B
1 TMS 2 RTCK 3 VSS 4 P1[1]/ENET_TXD1

Table 96. LPC2364/68 pin allocation table …continued

5 P1[9]/ENET_RXD0 6 P1[17]/ 7 VSS 8 P0[6]/I2SRX_SDA/
ENET_MDIO SSEL1/MAT2[0]
9 P2[0]/PWM1[1]/ 10 P2[1]/PWM1[2]/ 11 - 12 -
TXD1/TRACECLK RXD1/PIPESTAT0
Row C
1 TCK 2 TRST 3 TDI 4 P0[2]/TXD0
5 P1[8]/ENET_CRS 6 P1[15]/ 7 P4[28]/MAT2[0]/ 8 P0[8]/I2STX_WS/
ENET_REF_CLK TXD3 MISO1/MAT2[2]
9 VSS 10 VDD(3V3) 11 - 12 -
Row D
1 P0[24]/AD0[1]/ 2 P0[25]/AD0[2]/ 3 P0[26]/AD0[3]/ 4 DBGEN
I2SRX_WS/CAP3[1] I2SRX_SDA/TXD3 AOUT/RXD3
5 P1[0]/ENET_TXD0 6 P1[14]/ENET_RX_ER 7 P0[5]/I2SRX_WS/ 8 P2[2]/PWM1[3]/
TD2/CAP2[1] CTS1/PIPESTAT1
9 P2[4]/PWM1[5]/ 10 P2[5]/PWM1[6]/ 11 - 12 -
DSR1/TRACESYNC DTR1/TRACEPKT0
Row E
1 VSSA 2 VDDA 3 VREF 4 VDD(DCDC)(3V3)
5 P0[23]/AD0[0]/ 6 P4[29]/MAT2[1]/ 7 P2[3]/PWM1[4]/ 8 P2[6]/PCAP1[0]/RI1/
I2SRX_CLK/CAP3[0] RXD3 DCD1/PIPESTAT2 TRACEPKT1
9 P2[7]/RD2/ 10 P2[8]/TD2/ 11 - 12 -
RTS1/TRACEPKT2 TXD2/TRACEPKT3
Row F
1 VSS 2 RTCX1 3 RESET 4 P1[31]/SCK1/
AD0[5]
5 P1[21]/PWM1[3]/ 6 P0[18]/DCD1/ 7 P2[9]/USB_CONNECT/ 8 P0[16]/RXD1/
SSEL0 MOSI0/MOSI RXD2/EXTIN0 SSEL0/SSEL
9 P0[17]/CTS1/ 10 P0[15]/TXD1/ 11 - 12 -
MISO0/MISO SCK0/SCK
Row G
1 RTCX2 2 VBAT 3 XTAL2 4 P0[30]/USB_D
5 P1[25]/MAT1[1] 6 P1[29]/PCAP1[1]/ 7 VSS 8 P0[21]/RI1/
MAT0[1] MCIPWR/RD1
9 P0[20]/DTR1/ 10 P0[19]/DSR1/ 11 - 12 -
MCICMD/SCL1 MCICLK/SDA1
Row H
1 P1[30]/VBUS/ 2 XTAL1 3 P3[25]/MAT0[0]/ 4 P1[18]/USB_UP_LED/
AD0[4] PWM1[2] PWM1[1]/CAP1[0]
5 P1[24]/PWM1[5]/ 6 VDD(DCDC)(3V3) 7 P0[10]/TXD2/ 8 P2[11]/EINT1/
MOSI0 SDA2/MAT3[0] MCIDAT1/I2STX_CLK
9 VDD(3V3) 10 P0[22]/RTS1/ 11 - 12 -
MCIDAT0/TD1
Row J
1 P0[28]/SCL0 2 P0[27]/SDA0 3 P0[29]/USB_D+ 4 P1[19]/CAP1[1]

Table 96. LPC2364/68 pin allocation table …continued

5 P1[22]/MAT1[0] 6 VSS 7 P1[28]/PCAP1[0]/ 8 P0[1]/TD1/RXD3/SCL1
MAT0[0]
9 P2[13]/EINT3/ 10 P2[10]/EINT0 11 - 12 -
MCIDAT3/I2STX_SDA
Row K
1 P3[26]/MAT0[1]/ 2 VDD(3V3) 3 VSS 4 P1[20]/PWM1[2]/
PWM1[3] SCK0
5 P1[23]/PWM1[4]/ 6 P1[26]/PWM1[6]/ 7 P1[27]/CAP0[1] 8 P0[0]/RD1/TXD3/SDA1
MISO0 CAP0[0]
9 P0[11]/RXD2/ 10 P2[12]/EINT2/ 11 - 12 -
SCL2/MAT3[1] MCIDAT2/I2STX_WS
Table 97. LPC2364/65/66/67/68 pin description

Symbol Pin Ball Type Description
P0[0] to P0[31] I/O Port 0: Port 0 is a 32-bit I/O port with individual direction controls for each
bit. The operation of port 0 pins depends upon the pin function selected via
the pin connect block. Pins 12, 13, 14, and 31 of this port are not available.
P0[0]/RD1/TXD3/ 46[1] K8[1] I/O P0[0] — General purpose digital input/output pin.
SDA1 I RD1 — CAN1 receiver input. (LPC2364/66/68 only)
P0[1]/TD1/RXD3/ 47[1] J8[1] I/O P0[1] — General purpose digital input/output pin.
SCL1 O TD1 — CAN1 transmitter output. (LPC2364/66/68 only)
P0[2]/TXD0 98[1] C4[1] I/O P0[2] — General purpose digital input/output pin.
P0[3]/RXD0 99[1] A2[1] I/O P0[3] — General purpose digital input/output pin.
P0[4]/ 81[1] A8[1] I/O P0[4] — General purpose digital input/output pin.
I2SRX_CLK/ I/O I2SRX_CLK — Receive Clock. It is driven by the master and received by
RD2/CAP2[0] the slave. Corresponds to the signal SCK in the I2S-bus specification.
I RD2 — CAN2 receiver input. (LPC2364/66/68 only)
P0[5]/ 80[1] D7[1] I/O P0[5] — General purpose digital input/output pin.
I2SRX_WS/ I/O I2SRX_WS — Receive Word Select. It is driven by the master and received
TD2/CAP2[1] by the slave. Corresponds to the signal WS in the I2S-bus specification.
O TD2 — CAN2 transmitter output. (LPC2364/66/68 only)
P0[6]/ 79[1] B8[1] I/O P0[6] — General purpose digital input/output pin.
I2SRX_SDA/ I/O I2SRX_SDA — Receive data. It is driven by the transmitter and read by the
SSEL1/MAT2[0] receiver. Corresponds to the signal SD in the I2S-bus specification.

Table 97. LPC2364/65/66/67/68 pin description …continued

I2STX_CLK/ I/O I2STX_CLK — Transmit Clock. It is driven by the master and received by
SCK1/MAT2[1] the slave. Corresponds to the signal SCK in the I2S-bus specification.
P0[8]/ 77[1] C8[1] I/O P0[8] — General purpose digital input/output pin.
I2STX_WS/ I/O I2STX_WS — Transmit Word Select. It is driven by the master and
MISO1/MAT2[2] received by the slave. Corresponds to the signal WS in the I2S-bus
specification.
I2STX_SDA/ I/O I2STX_SDA — Transmit data. It is driven by the transmitter and read by the
MOSI1/MAT2[3] receiver. Corresponds to the signal SD in the I2S-bus specification.
P0[10]/TXD2/ 48[1] H7[1] I/O P0[10] — General purpose digital input/output pin.
P0[11]/RXD2/ 49[1] K9[1] I/O P0[11] — General purpose digital input/output pin.
P0[15]/TXD1/ 62[1] F10[1] I/O P0[15] — General purpose digital input/output pin.
P0[16]/RXD1/ 63[1] F8[1] I/O P0[16] — General purpose digital input/output pin.
P0[17]/CTS1/ 61[1] F9[1] I/O P0[17] — General purpose digital input/output pin.
P0[18]/DCD1/ 60[1] F6[1] I/O P0[18] — General purpose digital input/output pin.


P0[19]/DSR1/ 59[1] G10[1] I/O P0[19] — General purpose digital input/output pin.
O MCICLK — Clock output line for SD/MMC interface. (LPC2367/68 only)
P0[20]/DTR1/ 58[1] G9[1] I/O P0[20] — General purpose digital input/output pin.
I MCICMD — Command line for SD/MMC interface. (LPC2367/68 only)
P0[21]/RI1/ 57[1] G8[1] I/O P0[21] — General purpose digital input/output pin.
(LPC2367/68 only)
I RD1 — CAN1 receiver input. (LPC2364/66/68 only)
P0[22]/RTS1/ 56[1] H10[1] I/O P0[22] — General purpose digital input/output pin.
O MCIDAT0 — Data line for SD/MMC interface. (LPC2367/68 only)
O TD1 — CAN1 transmitter output. (LPC2364/66/68 only)
P0[23]/AD0[0]/ 9[2] E5[2] I/O P0[23] — General purpose digital input/output pin.
CAP3[0]
I/O I2SRX_CLK — Receive Clock. It is driven by the master and received by
the slave. Corresponds to the signal SCK in the I2S-bus specification.
P0[24]/AD0[1]/ 8[2] D1[2] I/O P0[24] — General purpose digital input/output pin.
CAP3[1]
I/O I2SRX_WS — Receive Word Select. It is driven by the master and received
by the slave. Corresponds to the signal WS in the I2S-bus specification.
TXD3
P0[27]/SDA0 25[4] J2[4] I/O P0[27] — General purpose digital input/output pin. Output is open-drain.
I/O SDA0 — I2C0 data input/output. Open-drain output (for I2C-bus
compliance).
P0[28]/SCL0 24[4] J1[4] I/O P0[28] — General purpose digital input/output pin. Output is open-drain.
I/O SCL0 — I2C0 clock input/output. Open-drain output (for I2C-bus
compliance).


P0[29]/USB_D+ 29[5] J3[5] I/O P0[29] — General purpose digital input/output pin.
I/O USB_D+ — USB bidirectional D+ line. (LPC2364/66/68 only)
P0[30]/USB_D 30[5] G4[5] I/O P0[30] — General purpose digital input/output pin.
I/O USB_D — USB bidirectional D line. (LPC2364/66/68 only)
the pin connect block. Pins 2, 3, 5, 6, 7, 11, 12, and 13 of this port are not
available.
ENET_TXD0 O ENET_TXD0 — Ethernet transmit data 0.
ENET_TX_EN O ENET_TX_EN — Ethernet transmit data enable.
ENET_CRS I ENET_CRS — Ethernet carrier sense.
ENET_RXD0 I ENET_RXD0 — Ethernet receive data.
ENET_MDC O ENET_MDC — Ethernet MIIM clock.
ENET_MDIO I/O ENET_MDIO — Ethernet MIIM data input and output.
P1[18]/ 32[1] H4[1] I/O P1[18] — General purpose digital input/output pin.
PWM1[1]/ configured (non-control endpoints enabled). It is HIGH when the device is
CAP1[0] not configured or during global suspend. (LPC2364/66/68 only)
P1[19]/CAP1[1] 33[1] J4[1] I/O P1[19] — General purpose digital input/output pin.
P1[20]/PWM1[2]/ 34[1] K4[1] I/O P1[20] — General purpose digital input/output pin.
SCK0 O PWM1[2] — Pulse Width Modulator 1, channel 2 output.
P1[21]/PWM1[3]/ 35[1] F5[1] I/O P1[21] — General purpose digital input/output pin.
SSEL0 O PWM1[3] — Pulse Width Modulator 1, channel 3 output.


P1[22]/MAT1[0] 36[1] J5[1] I/O P1[22] — General purpose digital input/output pin.
MISO0 O PWM1[4] — Pulse Width Modulator 1, channel 4 output.
P1[24]/PWM1[5]/ 38[1] H5[1] I/O P1[24] — General purpose digital input/output pin.
MOSI0 O PWM1[5] — Pulse Width Modulator 1, channel 5 output.
P1[25]/MAT1[1] 39[1] G5[1] I/O P1[25] — General purpose digital input/output pin.
P1[27]/CAP0[1] 43[1] K7[1] I/O P1[27] — General purpose digital input/output pin.
P1[28]/ 44[1] J7[1] I/O P1[28] — General purpose digital input/output pin.
PCAP1[0]/ I PCAP1[0] — Capture input for PWM1, channel 0.
MAT0[0]
P1[29]/ 45[1] G6[1] I/O P1[29] — General purpose digital input/output pin.
MAT0[1]
P1[30]/VBUS/ 21[2] H1[2] I/O P1[30] — General purpose digital input/output pin.
AD0[4] I VBUS — Monitors the presence of USB bus power. (LPC2364/66/68 only)
P1[31]/SCK1/ 20[2] F4[2] I/O P1[31] — General purpose digital input/output pin.
AD0[5] I/O SCK1 — Serial Clock for SSP1.
the pin connect block. Pins 14 through 31 of this port are not available.
P2[0]/PWM1[1]/ 75[1] B9[1] I/O P2[0] — General purpose digital input/output pin.
TXD1/ O PWM1[1] — Pulse Width Modulator 1, channel 1 output.
TRACECLK
P2[1]/PWM1[2]/ 74[1] B10[1] I/O P2[1] — General purpose digital input/output pin.
RXD1/ O PWM1[2] — Pulse Width Modulator 1, channel 2 output.
PIPESTAT0


P2[2]/PWM1[3]/ 73[1] D8[1] I/O P2[2] — General purpose digital input/output pin.
CTS1/ O PWM1[3] — Pulse Width Modulator 1, channel 3 output.
PIPESTAT1
P2[3]/PWM1[4]/ 70[1] E7[1] I/O P2[3] — General purpose digital input/output pin.
DCD1/ O PWM1[4] — Pulse Width Modulator 1, channel 4 output.
PIPESTAT2
DSR1/ O PWM1[5] — Pulse Width Modulator 1, channel 5 output.
TRACESYNC
DTR1/ O PWM1[6] — Pulse Width Modulator 1, channel 6 output.
TRACEPKT0
P2[6]/PCAP1[0]/ 67[1] E8[1] I/O P2[6] — General purpose digital input/output pin.
RI1/ I PCAP1[0] — Capture input for PWM1, channel 0.
TRACEPKT1
P2[7]/RD2/ 66[1] E9[1] I/O P2[7] — General purpose digital input/output pin.
RTS1/ I RD2 — CAN2 receiver input. (LPC2364/66/68 only)
TRACEPKT2
P2[8]/TD2/ 65[1] E10[1] I/O P2[8] — General purpose digital input/output pin.
TXD2/ O TD2 — CAN2 transmitter output. (LPC2364/66/68 only)
TRACEPKT3
P2[9]/ 64[1] F7[1] I/O P2[9] — General purpose digital input/output pin.
RXD2/EXTIN0 software control. Used with the SoftConnect USB feature. (LPC2364/66/68
only)
P2[10]/EINT0 53[6] J10[6] I/O P2[10] — General purpose digital input/output pin.
Note: LOW on this pin while RESET is LOW forces on-chip bootloader to
take over control of the part after a reset.


P2[11]/EINT1/ 52[6] H8[6] I/O P2[11] — General purpose digital input/output pin.
I2STX_CLK
I/O I2STX_CLK — Transmit Clock. It is driven by the master and received by
the slave. Corresponds to the signal SCK in the I2S-bus specification.
P2[12]/EINT2/ 51[6] K10[6] I/O P2[12] — General purpose digital input/output pin.
I2STX_WS
I/O I2STX_WS — Transmit Word Select. It is driven by the master and
received by the slave. Corresponds to the signal WS in the I2S-bus
specification.
P2[13]/EINT3/ 50[6] J9[6] I/O P2[13] — General purpose digital input/output pin.
I2STX_SDA
the pin connect block. Pins 0 through 24, and 27 through 31 of this port are
not available.
P3[25]/MAT0[0]/ 27[1] H3[1] I/O P3[25] — General purpose digital input/output pin.
P3[26]/MAT0[1]/ 26[1] K1[1] I/O P3[26] — General purpose digital input/output pin.
the pin connect block. Pins 0 through 27, 30, and 31 of this port are not
available.
P4[28]/MAT2[0]/ 82[1] C7[1] I/O P4[28] — General purpose digital input/output pin.
P4[29]/MAT2[1]/ 85[1] E6[1] I/O P4[29] — General purpose digital input/output pin.
DBGEN - D4[1] I DBGEN — JTAG interface control signal. Also used for boundary scanning.
Note: This pin is available in LPC2364FET100 and LPC2368FET100
devices only (TFBGA package).
TDO 1[1] A1[1] O TDO — Test Data out for JTAG interface.
TDI 2[1] C3[1] I TDI — Test Data in for JTAG interface.
TMS 3[1] B1[1] I TMS — Test Mode Select for JTAG interface.
TRST 4[1] C2[1] I TRST — Test Reset for JTAG interface.


TCK 5[1] C1[1] I TCK — Test Clock for JTAG interface. This clock must be slower than 16 of
the CPU clock (CCLK) for the JTAG interface to operate
RTCK 100[1] B2[1] I/O RTCK — JTAG interface control signal.
RSTOUT 14 - O RSTOUT — This is a 3.3 V pin. LOW on this pin indicates LPC23xx being
in Reset state.
Note: This pin is available in LPC2364FBD100, LPC2365FBD100,
LPC2366FBD100, LPC2367FBD100, and LPC2368FBD100 devices only
(LQFP100 package).
RESET 17[7] F3[7] I External 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.
XTAL1 22[8] H2[8] I Input to the oscillator circuit and internal clock generator circuits.
XTAL2 23[8] G3[8] O Output from the oscillator amplifier.
RTCX1 16[8] F2[8] I Input to the RTC oscillator circuit.
RTCX2 18[8] G1[8] O Output from the RTC oscillator circuit.
VSS 15, 31, B3, B7, I ground: 0 V reference.
41, 55, C9, F1,
72, 97, G7, J6,
83[9] K3 [9]
VSSA 11[10] E1[10] I analog ground: 0 V reference. This should nominally be the same voltage
as VSS, but should be isolated to minimize noise and error.
VDD(3V3) 28, 54, A3, C10, I 3.3 V supply voltage: This is the power supply voltage for the I/O ports.
71, H9,
96[11] K2[11]
VDD(DCDC)(3V3) 13, 42, A7, E4, I 3.3 V DC-to-DC converter supply voltage: This is the supply voltage for
84[12] H6[12] the on-chip DC-to-DC converter only.
VDDA 10[13] E2[13] I analog 3.3 V pad supply voltage: This should be nominally the same
voltage as VDD(3V3) but should be isolated to minimize noise and error. This
voltage is used to power the ADC and DAC.
VREF 12[13] E3[13] I ADC reference: This should be nominally the same voltage as VDD(3V3) but
should be isolated to minimize noise and error. Level on this pin is used as
a reference for ADC and DAC.
VBAT 19[13] G2[13] I RTC pin power supply: 3.3 V on this pin supplies the power to the RTC
peripheral.
[5] Pad provides digital I/O and USB functions (LPC2364/66/68 only). It is designed in accordance with the USB specification, revision 2.0
(Full-speed and Low-speed mode only).
[6] 5 V tolerant pad with 10 ns glitch filter providing digital I/O functions with TTL levels and hysteresis.
[7] 5 V tolerant pad with 20 ns glitch filter providing digital I/O function with TTL levels and hysteresis.



8.4 LPC2377/78 144-pin package
144
109
1 108
LPC2377FBD144
LPC2378FBD144
36 73
37
72
002aac584
Fig 28. LPC2378 144-pin package
Pin descriptions for LPC2377/78 and a brief explanation of their corresponding functions
are shown in the following table.
Table 98. LPC2377/78 pin description

P0[0] to P0[31] I/O Port 0: Port 0 is a 32-bit I/O port with individual direction controls for each bit. The
operation of port 0 pins depends upon the pin function selected via the pin connect
block.
P0[0]/RD1/TXD/ 66[1] I/O P0[0] — General purpose digital input/output pin.
SDA1 I RD1 — CAN1 receiver input. (LPC2378 only)
SCL1 O TD1 — CAN1 transmitter output. (LPC2378 only)
I2SRX_CLK/ I/O I2SRX_CLK — Receive Clock. It is driven by the master and received by the slave.
RD2/CAP2[0] Corresponds to the signal SCK in the I2S-bus specification.
I RD2 — CAN2 receiver input. (LPC2378 only)
I2SRX_WS/ I/O I2SRX_WS — Receive Word Select. It is driven by the master and received by the
TD2/CAP2[1] slave. Corresponds to the signal WS in the I2S-bus specification.
O TD2 — CAN2 transmitter output. (LPC2378 only)


I2STX_CLK/ I/O I2STX_CLK — Transmit Clock. It is driven by the master and received by the slave.
SCK1/MAT2[1] Corresponds to the signal SCK in the I2S-bus specification.
I2STX_WS/ I/O I2STX_WS — Transmit Word Select. It is driven by the master and received by the
MISO1/MAT2[2] slave. Corresponds to the signal WS in the I2S-bus specification.
SDA2/MAT3 [0] O TXD2 — Transmitter output for UART2.
P0[12]/MISO1/ 29[2] I/O P0[12] — General purpose digital input/output pin.
AD0[6] I/O MISO1 — Master In Slave Out for SSP1.
USB_UP_LED2/ O USB_UP_LED2 — USB2 Good Link LED indicator. It is LOW when device is
MOSI1/AD0[7] configured (non-control endpoints enabled). It is HIGH when the device is not
configured or during global suspend. (LPC2378 only)
USB_CONNECT2/ O USB_CONNECT2 — USB2 Soft Connect control. Signal used to switch an external
SSEL1 1.5 k resistor under software control. Used with the SoftConnect USB feature.
(LPC2378 only)


P0[16]/RXD1/ 90[1] I/O P0 [16] — General purpose digital input/output pin.
I RD1 — CAN1 receiver input. (LPC2378 only)
O TD1 — CAN1 transmitter output. (LPC2378 only)
CAP3[0]
I/O I2SRX_CLK — Receive Clock. It is driven by the master and received by the slave.
Corresponds to the signal SCK in the I2S-bus specification.


CAP3[1]
I/O I2SRX_WS — Receive Word Select. It is driven by the master and received by the
slave. Corresponds to the signal WS in the I2S-bus specification.
TXD3
AOUT/RXD3 I AD0[3] — ]A/D converter 0, input 3.
P0[27]/SDA0 35[4] I/O P0[27] — General purpose digital input/output pin. Output is open-drain.
P0[28]/SCL0 34[4] I/O P0[28] — General purpose digital input/output pin. Output is open-drain.
P0[29]/USB_D+1 42[5] I/O P0[29] — General purpose digital input/output pin.
I/O USB_D+1 — USB1 port bidirectional D+ line. (LPC2378 only)
P0[30]/USB_D1 43[5] I/O P0[30] — General purpose digital input/output pin.
I/O USB_D1 — USB1 port bidirectional D line. (LPC2378 only)
I/O USB_D+2 — USB2 port bidirectional D+ line. (LPC2378 only)
block. Pins 2, 3, 5, 6, 7, 11, 12, and 13 of this port are not available.


ENET_MDIO I/O ENET_MDIO — Ethernet MIIM data input and output.
USB_UP_LED1/ O USB_UP_LED1 — USB1 port Good Link LED indicator. It is LOW when device is
CAP1[0] configured or during global suspend. (LPC2378 only)
P1[19]/CAP1[1] 47[1] I/O P1[19] — General purpose digital input/output pin.
SCK0 O PWM1[2] — Pulse Width Modulator 1, channel 2 output.
SSEL0 O PWM1[3] — Pulse Width Modulator 1, channel 3 output.
P1[22]/MAT1[0] 51[1] I/O P1[22] — General purpose digital input/output pin.
MISO0 O PWM1[4] — Pulse Width Modulator 1, channel 4 output.
MOSI0 O PWM1[5] — Pulse Width Modulator 1, channel 5 output.
P1[25]/MAT1[1] 56[1] I/O P1[25] — General purpose digital input/output pin.
P1[27]/CAP0[1] 61[1] I/O P1[27] — General purpose digital input/output pin.
MAT0[0]
MAT0[1]


VBUS/AD0[4] I VBUS — Monitors the presence of USB bus power. (LPC2378 only)
P1[31]/SCK1/ 28[2] I/O P1[31] — General purpose digital input/output pin.
AD0[5] I/O SCK1 — Serial Clock for SSP1.
P2[0] to P2[31] I/O Port 2: Port 2 is a 32 bit I/O port with individual direction controls for each bit. The
block. Pins 14 through 31 of this port are not available.
TRACECLK
PIPESTAT0
PIPESTAT1
PIPESTAT2
TRACESYNC
TRACEPKT0
P2[6]/PCAP1[0]/ 96[1] I/O P2[6] — General purpose digital input/output pin.
TRACEPKT1


RTS1/ I RD2 — CAN2 receiver input. (LPC2378 only)
TRACEPKT2
TXD2/ O TD2 — CAN2 transmitter output. (LPC2378 only)
TRACEPKT3
USB_CONNECT1/ O USB_CONNECT1 — USB1 Soft Connect control. Signal used to switch an external
RXD2/ 1.5 k resistor under the software control. Used with the SoftConnect USB feature.
EXTIN0 (LPC2378 only)
Note: LOW on this pin while RESET is LOW forces on-chip boot-loader to take over
control of the part after a reset.
I2STX_CLK
I/O I2STX_CLK — Transmit Clock. It is driven by the master and received by the slave.
I2STX_WS
I/O I2STX_WS — Transmit Word Select. It is driven by the master and received by the
I2STX_SDA
block. Pins 8 through 22, and 27 through 31 of this port are not available.
P3[0]/D0 137[1] I/O P3[0] — General purpose digital input/output pin.
I/O D0 — External memory data line 0.


P3[23]/CAP0[0]/ 45[1] I/O P3[23] — General purpose digital input/output pin.
PCAP1[0] I CAP0[0] — Capture input for Timer 0, channel 0.
PWM1[1] I CAP0[1] — Capture input for Timer 0, channel 1.
block. Pins 16 through 23, 26, and 27 of this port are not available.
P4[0]/A0 52[1] I/O P4[0] — ]General purpose digital input/output pin.
I/O A0 — External memory address line 0.
P4[1]/A1 55[1] I/O P4[1] — General purpose digital input/output pin.


P4[24]/OE 127[1] I/O P4[24] — General purpose digital input/output pin.
O OE — LOW active Output Enable signal.
P4[25]/BLS0 124[1] I/O P4[25] — General purpose digital input/output pin.
O BLS0 — LOW active Byte Lane select signal 0.
P4[28]/MAT2[0]/ 118[1] I/O P4 [28] — General purpose digital input/output pin.
P4[30]/CS0 130[1] I/O P4[30] — General purpose digital input/output pin.
O CS0 — LOW active Chip Select 0 signal.
ALARM 26[8] O ALARM — RTC controlled output. This is a 1.8 V pin. It goes HIGH when a RTC
alarm is generated.
USB_D2 37 I/O USB_D2 — USB2 port bidirectional D line. LPC2378 only. This pin is not
connected on the LPC2377.
DBGEN 6[1] I DBGEN — JTAG interface control signal. Also used for boundary scanning.
TDO 1[1] O TDO — Test Data out for JTAG interface.
TDI 3[1] I TDI — Test Data in for JTAG interface.


Note: LOW on this pin while RESET is LOW enables ETM pins (P2[9:0]) to operate
as Trace port after reset.
RSTOUT 20 O RSTOUT — This is a 3.3 V pin. LOW on this pin indicates LPC23xx being in Reset
state.
RESET 24[7] I external reset input: A LOW on this pin resets the device, causing I/O ports and
59, 65,
79, 103,
117,119,
139[9]
VSSA 15[10] I analog ground: 0 V reference. This should nominally be the same voltage as VSS,
but should be isolated to minimize noise and error.
77, 102,
114,
138[11]
n.c. 21, 81, I Leave these pins unconnected.
98[12]
VDD(DCDC)(3V3) 18, 60, I 3.3 V DC-to-DC converter supply voltage: This is the power supply for the on-chip
121[13] DC-to-DC converter only.
VDDA 14[14] I analog 3.3 V pad supply voltage: This should be nominally the same voltage as
VDD(3V3) but should be isolated to minimize noise and error. This voltage is used to
power the ADC and DAC.
VREF 17[14] I ADC reference: This should be nominally the same voltage as VDD(3V3) but should
be isolated to minimize noise and error. The level on this pin is used as a reference
for ADC and DAC.
VBAT 27[14] I RTC pin power supply: 3.3 V on this pin supplies the power to the RTC peripheral.
[4] Open-drain, 5 V tolerant digital I/O pad compatible with I2C-bus 400 kHz specification. It requires an external pull-up to provide output
functionality. When power is switched off, this pin connected to the I2C-bus is floating and does not disturb the I2C lines. Open-drain
configuration applies to all functions on this pin.
[5] Pad provides digital I/O and USB functions (LPC2378 only). It is designed in accordance with the USB specification, revision 2.0
(Full-speed and Low-speed mode only).


8.5 LPC2387 100-pin package
100
76
1 75
LPC2387FBD100
25 51
26
50
002aad329
Fig 29. LPC2387 pinning LQFP100 package
Table 99. LPC2387 pin description

connect block. Pins 12, 13, 14, and 31 of this port are not available.
P0[0]/RD1/TXD3/ 46[1] I/O P0[0] — General purpose digital input/output pin.
P0[4]/I2SRX_CLK/ 81[1] I/O P0[4] — General purpose digital input/output pin.
RD2/CAP2[0] I/O I2SRX_CLK — Receive Clock. It is driven by the master and received by the

Table 99. LPC2387 pin description …continued

P0[5]/I2SRX_WS/ 80[1] I/O P0[5] — General purpose digital input/output pin.
TD2/CAP2[1] I/O I2SRX_WS — Receive Word Select. It is driven by the master and received by
P0[6]/I2SRX_SDA/ 79[1] I/O P0[6] — General purpose digital input/output pin.
SSEL1/MAT2[0] I/O I2SRX_SDA — Receive data. It is driven by the transmitter and read by the
P0[7]/I2STX_CLK/ 78[1] I/O P0[7] — General purpose digital input/output pin.
SCK1/MAT2[1] I/O I2STX_CLK — Transmit Clock. It is driven by the master and received by the
P0[8]/I2STX_WS/ 77[1] I/O P0[8] — General purpose digital input/output pin.
MISO1/MAT2[2] I/O I2STX_WS — Transmit Word Select. It is driven by the master and received by
P0[9]/I2STX_SDA/ 76[1] I/O P0[9] — General purpose digital input/output pin.
MOSI1/MAT2[3] I/O I2STX_SDA — Transmit data. It is driven by the transmitter and read by the


CAP3[0]
I/O I2SRX_CLK — Receive Clock. It is driven by the master and received by the
CAP3[1]
I/O I2SRX_WS — Receive Word Select. It is driven by the master and received by
TXD3


P0[27]/SDA0 25[4] I/O P0[27] — General purpose digital input/output pin.
P0[28]/SCL0 24[4] I/O P0[28] — General purpose digital input/output pin.
P0[29]/USB_D+ 29[5] I/O P0[29] — General purpose digital input/output pin.
I/O USB_D+ — USB bidirectional D+ line.
P0[30]/USB_D 30[5] I/O P0[30] — General purpose digital input/output pin.
I/O USB_D — USB bidirectional D line.
connect block. Pins 2, 3, 5, 6, 7, 11, 12, and 13 of this port are not available.
P1[4]/ENET_TX_EN 93[1] I/O P1[4] — General purpose digital input/output pin.
O ENET_TX_EN — Ethernet transmit data enable.
P1[8]/ENET_CRS 92[1] I/O P1[8] — General purpose digital input/output pin.
I ENET_CRS — Ethernet carrier sense.
P1[16]/ENET_MDC 87[1] I/O P1[16] — General purpose digital input/output pin.
O ENET_MDC — Ethernet MIIM clock.
P1[17]/ENET_MDIO 86[1] I/O P1[17] — General purpose digital input/output pin.
I/O ENET_MDIO — Ethernet MIIM data input and output.


USB_PPWR1/
PWM1[2]/SCK0
PWM1[3]/SSEL0
USB_PWRD1/
PWM1[4]/MISO0
PWM1[5]/MOSI0
USB_HSTEN1/
PWM1[6]/
USB_OVRCR1/
P1[28]/USB_SCL1/ 44[1] I/O P1[28] — General purpose digital input/output pin.
PCAP1[0]/MAT0[0] I/O USB_SCL1 — USB port 1 I2C-bus serial clock (OTG transceiver).


P1[29]/USB_SDA1/ 45[1] I/O P1[29] — General purpose digital input/output pin.
PCAP1[1]/MAT0[1] I/O USB_SDA1 — USB port 1 I2C-bus serial data (OTG transceiver).
P1[30]/VBUS/AD0[4] 21[2] I/O P1[30] — General purpose digital input/output pin.
P1[31]/SCK1/AD0[5] 20[2] I/O P1[31] — General purpose digital input/output pin.
connect block. Pins 14 through 31 of this port are not available.
TXD1/TRACECLK O PWM1[1] — Pulse Width Modulator 1, channel 1 output.
RXD1/PIPESTAT0 O PWM1[2] — Pulse Width Modulator 1, channel 2 output.
CTS1/PIPESTAT1 O PWM1[3] — Pulse Width Modulator 1, channel 3 output.
DCD1/PIPESTAT2 O PWM1[4] — Pulse Width Modulator 1, channel 4 output.
DSR1/TRACESYNC O PWM1[5] — Pulse Width Modulator 1, channel 5 output.
DTR1/TRACEPKT0 O PWM1[6] — Pulse Width Modulator 1, channel 6 output.


P2[6]/PCAP1[0]/RI1/ 67[1] I/O P2[6] — General purpose digital input/output pin.
TRACEPKT1 I PCAP1[0] — Capture input for PWM1, channel 0.
RTS1/TRACEPKT2 I RD2 — CAN2 receiver input.
TXD2/TRACEPKT3 O TD2 — CAN2 transmitter output.
RXD2/EXTIN0 software control. Used with the SoftConnect USB feature.
Note: LOW on this pin while RESET is LOW forces on-chip bootloader to take
over control of the part after a reset.
I2STX_CLK
I/O I2STX_CLK — Transmit Clock. It is driven by the master and received by the
I2STX_WS
I/O I2STX_WS — Transmit Word Select. It is driven by the master and received by
I2STX_SDA
connect block. Pins 0 through 24, and 27 through 31 of this port are not
available.


connect block. Pins 0 through 27, 30, and 31 of this port are not available.
TDO 1[1] O TDO — Test Data Out for JTAG interface.
TDI 2[1] I TDI — Test Data In for JTAG interface.
RSTOUT 14 O RSTOUT — This is a 3.3 V pin. LOW on this pin indicates UM10211 being in
Reset state.
Note: This pin is available in LPC2387FBD100 devices only (LQFP100
package).
RESET 17[7] I External reset input: A LOW on this pin resets the device, causing I/O ports and
41, 55,
72, 97,
83[9]
VSSA 11[10] I analog ground: 0 V reference. This should nominally be the same voltage as
VSS, but should be isolated to minimize noise and error.
71, 96[11]
VDD(DCDC)(3V3) 13, 42, I 3.3 V DC-to-DC converter supply voltage: This is the supply voltage for the
84[12] on-chip DC-to-DC converter only.


VDDA 10[13] I analog 3.3 V pad supply voltage: This should be nominally the same voltage
as VDD(3V3) but should be isolated to minimize noise and error. This voltage is
used to power the ADC and DAC.
VREF 12[13] I ADC reference: This should be nominally the same voltage as VDD(3V3) but
should be isolated to minimize noise and error. Level on this pin is used as a
reference for ADC and DAC.
VBAT 19[13] I RTC pin power supply: 3.3 V on this pin supplies the power to the RTC
peripheral.
[6] 5 V tolerant pad with 10 ns glitch filter providing digital I/O functions with TTL levels and hysteresis
[7] 5 V tolerant pad with 20 ns glitch filter providing digital I/O function with TTL levels and hysteresis
8.6 LPC2388 144-pin package

144
109
1 108
LPC2388FBD144
36 73
37
72
002aad333
Fig 30. LPC2388 pinning LQFP144 package

Table 100. LPC2388 pin description

operation of port 0 pins depends upon the pin function selected via the Pin Connect
block.
P0[0]/RD1/TXD/ 66[1] I/O P0[0] — General purpose digital input/output pin.
I2SRX_CLK/ I/O I2SRX_CLK — Receive Clock. It is driven by the master and received by the slave.
RD2/CAP2[0] Corresponds to the signal SCK in the I2S-bus specification.
I2SRX_WS/ I/O I2SRX_WS — Receive Word Select. It is driven by the master and received by the
TD2/CAP2[1] slave. Corresponds to the signal WS in the I2S-bus specification.
I2STX_CLK/ I/O I2STX_CLK — Transmit Clock. It is driven by the master and received by the slave.
SCK1/MAT2[1] Corresponds to the signal SCK in the I2S-bus specification.
I2STX_WS/ I/O I2STX_WS — Transmit Word Select. It is driven by the master and received by the
MISO1/MAT2[2] slave. Corresponds to the signal WS in the I2S-bus specification.


SDA2/MAT3 [0] O TXD2 — Transmitter output for UART2.
P0[12]/MISO1/ 29[2] I/O P0[12] — General purpose digital input/output pin.
USB_PPWR2/ I/O MISO1 — Master In Slave Out for SSP1.
AD0[6]
O USB_PPWR2 — Port power enable signal for USB port 2.
USB_UP_LED2/ O USB_UP_LED2 — USB port 2 Good Link LED indicator. It is LOW when device is
MOSI1/AD0[7] configured (non-control endpoints enabled). It is HIGH when the device is not
configured or during global suspend.
USB_HSTEN2/ O USB_HSTEN2 — Host Enabled status for USB port 2.
USB_CONNECT2/
SSEL1 O USB_CONNECT2 — SoftConnect control for USB port 2. Signal used to switch an
external 1.5 k resistor under software control. Used with the SoftConnect USB
feature.
P0[16]/RXD1/ 90[1] I/O P0 [16] — General purpose digital input/output pin.


CAP3[0]
I/O I2SRX_CLK — Receive Clock. It is driven by the master and received by the slave.
CAP3[1]
I/O I2SRX_WS — Receive Word Select. It is driven by the master and received by the
TXD3
AOUT/RXD3 I AD0[3] — ]A/D converter 0, input 3.
P0[27]/SDA0 35[4] I/O P0[27] — General purpose digital input/output pin. Output is open-drain.


P0[28]/SCL0 34[4] I/O P0[28] — General purpose digital input/output pin. Output is open-drain.
I/O USB_D+1 — USB port 1 bidirectional D+ line.
P0[30]/USB_D1 43[5] I/O P0[30] — General purpose digital input/output pin.
I/O USB_D1 — USB port 1 bidirectional D line.
I/O USB_D+2 — USB port 2 bidirectional D+ line.
block. Pins 2, 3, 5, 6, 7, 11, 12, and 13 of this port are not available.
ENET_MDIO I/O ENET_MDIO — Ethernet MI data input and output.
USB_UP_LED1/ O USB_UP_LED1 — USB port 1 Good Link LED indicator. It is LOW when device is
USB_PPWR1/


PWM1[2]/SCK0
PWM1[3]/SSEL0
USB_PWRD1/
PWM1[4]/MISO0
PWM1[5]/MOSI0
USB_HSTEN1/
PWM1[6]/
USB_OVRCR1/
USB_SCL1/ I/O USB_SCL1 — USB port 1 I2C-bus serial clock (OTG transceiver).
PCAP1[0]/
MAT0[0] I PCAP1[0] — Capture input for PWM1, channel 0.
USB_SDA1/ I/O USB_SDA1 — USB port 1 I2C-bus serial data (OTG transceiver).
PCAP1[1]/
MAT0[1] I PCAP1[1] — Capture input for PWM1, channel 1.


USB_PWRD2/ I USB_PWRD2 — Power Status for USB port 2.
VBUS/AD0[4]
USB_OVRCR2/ I USB_OVRCR2 — Over-Current status for USB port 2.
SCK1/AD0[5]
block. Pins 14 through 31 of this port are not available.
TRACECLK
PIPESTAT0
PIPESTAT1
PIPESTAT2
TRACESYNC
TRACEPKT0
P2[6]/PCAP1[0]/ 96[1] I/O P2[6] — General purpose digital input/output pin.
TRACEPKT1


RTS1/ I RD2 — CAN2 receiver input.
TRACEPKT2
TXD2/ O TD2 — CAN2 transmitter output.
TRACEPKT3
USB_CONNECT1/ O USB_CONNECT1 — USB port 1 Soft Connect control. Signal used to switch an
RXD2/ external 1.5 k resistor under the software control. Used with the SoftConnect USB
EXTIN0 feature.
Note: LOW on this pin while RESET is LOW forces on-chip boot-loader to take over
control of the part after a reset.
I2STX_CLK
I/O I2STX_CLK — Transmit Clock. It is driven by the master and received by the slave.
I2STX_WS
I/O I2STX_WS — Transmit Word Select. It is driven by the master and received by the
I2STX_SDA
block. Pins 8 through 22, and 27 through 31 of this port are not available.


PCAP1[0] I CAP0[0] — Capture input for Timer 0, channel 0.
PWM1[1] I CAP0[1] — Capture input for Timer 0, channel 1.
block. Pins 16 through 23, 26, and 27 of this port are not available.
P4[0]/A0 52[1] I/O P4[0] — ]General purpose digital input/output pin.


P4[24]/OE 127[1] I/O P4[24] — General purpose digital input/output pin.
O OE — LOW active Output Enable signal.
P4[25]/BLS0 124[1] I/O P4[25] — General purpose digital input/output pin.
O BLS0 — LOW active Byte Lane select signal 0.
P4[28]/MAT2[0]/ 118[1] I/O P4 [28] — General purpose digital input/output pin.
ALARM 26[8] O ALARM — RTC controlled output. This is a 1.8 V pin. It goes HIGH when a RTC
alarm is generated.
USB_D2 37 I/O USB_D2 — USB port 2 bidirectional D line.
DBGEN 6[1] I DBGEN — JTAG interface control signal. Also used for boundary scanning.
TDO 1[1] O TDO — Test Data out for JTAG interface.
TDI 3[1] I TDI — Test Data in for JTAG interface.


Note: LOW on this pin while RESET is LOW enables ETM pins (P2[9:0]) to operate
as Trace port after reset.
RSTOUT 20 O RSTOUT — This is a 3.3 V pin. LOW on this pin indicates LPC23xx being in Reset
state.
RESET 24[7] I external reset input: A LOW on this pin resets the device, causing I/O ports and
59, 65,
79, 103,
117,119,
139[9]
VSSA 15[10] I analog ground: 0 V reference. This should nominally be the same voltage as VSS,
but should be isolated to minimize noise and error.
77, 102,
114,
138[11]
n.c. 21, 81, I Leave these pins unconnected.
98[12]
VDD(DCDC)(3V3) 18, 60, I 3.3 V DC-to-DC converter supply voltage: This is the power supply for the on-chip
121[13] DC-to-DC converter only.
VDDA 14[14] I analog 3.3 V pad supply voltage: This should be nominally the same voltage as
VDD(3V3) but should be isolated to minimize noise and error. This voltage is used to
power the ADC and DAC.
VREF 17[14] I ADC reference: This should be nominally the same voltage as VDD(3V3) but should
be isolated to minimize noise and error. The level on this pin is used as a reference
for ADC and DAC.
VBAT 27[14] I RTC power supply: 3.3 V on this pin supplies the power to the RTC peripheral.
[4] Open-drain 5 V tolerant digital I/O pad, compatible with I2C-bus 400 kHz specification. It requires an external pull-up to provide output
functionality. When power is switched off, this pin connected to the I2C-bus is floating and does not disturb the I2C lines. Open-drain
configuration applies to all functions on this pin.



UM10211
Chapter 9: LPC23XX Pin connect block

See Table 101 for how to use the PINSEL registers for different LPC23xx parts.
Table 101. Part specific PINSEL registers

PINSEL LPC2361/ Functions LPC2364/ Functions LPC2377/78 Functions LPC2387 LPC2388
register 62 disabled 65/66/67/68 disabled disabled
PINSEL0 Table 105 - Table 105 CAN Table 106 CAN Table 105 Table 106
(LPC2365/ (LPC2377)
67)
PINSEL1 Table 107 - Table 107 USB Table 108 USBdevice, Table 107 Table 108
device, CAN
CAN (LPC2377)
(LPC2365/
67)
PINSEL2 Table 109 Ethernet Table 109 - Table 109 Table 109 Table 109
(LPC2361)
PINSEL3 Table 110 Ethernet Table 110 USB Table 111 Table 110 Table 111
(LPC2361) OTG/host
PINSEL4 Table 112 - Table 112 USB device Table 113 USB device Table 112 Table 113
(LPC2365/ (LPC2377)
67)
PINSEL5 not used - not used - not used not used not used
PINSEL6 not used - not used - Table 114 not used Table 114
PINSEL7 Table 115 - Table 115 - Table 116 Table 115 Table 116
PINSEL10 Table 120 - Table 120 - Table 120 Table 120 Table 120
9.2 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.
Peripherals should be connected to the appropriate pins prior to being activated and prior
to any related interrupts 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.
9.3 Pin 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.

Table 102. Pin function select register bits

PINSEL0 to Function Value after Reset
PINSEL9 Values
00 Primary (default) function, typically GPIO port 00
01 First alternate function
10 Second alternate function
11 Third alternate function
The direction control bit in the GPIO registers 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 therefore a different set of functions possible
for each pin. Details for a specific derivative may be found in the appropriate data sheet.
9.4 Pin mode select register values

The PINMODE registers control the on-chip pull-up/pull-down resistor feature (the mode)
for all ports. The on-chip pull-up/pull-down resistor can be selected for every pin
regardless of the function on this pin with the exception of the I2C pins and the USB pins
(see Section 9.5.13). Two bits are used to control the mode of a port pin. Bits are reserved
for unused pins as in the PINSEL registers.
Table 103. Pin Mode Select register Bits

PINMODE0 to Function Value after Reset
PINMODE9
Values
00 Pin has an on-chip pull-up resistor enabled. 00
01 Reserved. This value should not be used.
10 Pin has neither pull-up nor pull-down resistor enabled.
11 Pin has an on-chip pull-down resistor enabled.

The Pin Control Module contains 11 registers as shown in Table 104 below.
Table 104. Pin Connect Block Register Map

Name Description Access Reset Value[1] Address
PINSEL0 Pin function select register 0. R/W 0x0000 0000 0xE002 C000
PINSEL3 Pin function select register 3. R/W 0x0000 0000 0xE002 C00C
PINSEL7 Pin function select register 7. R/W 0x0000 0000 0xE002 C01C

Table 104. Pin Connect Block Register Map

Name Description Access Reset Value[1] Address
PINMODE0 Pin mode select register 0. R/W 0x0000 0000 0xE002 C040
PINMODE3 Pin mode select register 3. R/W 0x0000 0000 0xE002 C04C
PINMODE7 Pin mode select register 7. R/W 0x0000 0000 0xE002 C05C
Pin control module register reset values

On power-on-reset (POR) and BOD reset, all registers in this module are reset to '0'.
On external reset and watchdog reset:
• The corresponding bits for P0.31:0, P1.31:0, P2.13:0 are always reset to '0'.
• For all other bits (applies to LPC2377/78 and LPC2388 only):
– if the EMC_Reset_Disable = 1 (see Section 3.7 “Other system controls and status
flags”), they retain their values for external memory interface
– else if the EMC_Reset_Disable = 0, they are reset to '0'.
9.5.1 Pin Function Select register 0 (PINSEL0 - 0xE002 C000)

The PINSEL0 register controls the functions of the pins. The direction control bit in the
IO0DIR register (or the FIO0DIR register if the enhanced GPIO function is selected for
port 0) is effective only when the GPIO function is selected for a pin. For other functions,
the direction is controlled automatically.
9.5.1.1 100-pin packages

Table 105. Pin function select register 0 (PINSEL0 - address 0xE002 C000) bit description
(LPC2364/65/66/67/68 and LPC2387)
PINSEL0 Pin Function when Function when 01 Function Function Reset
name 00 when 10 when 11 value
1:0 P0.0 GPIO Port 0.0 RD1[1] TXD3 SDA1 00
3:2 P0.1 GPIO Port 0.1 TD1[1] RXD3 SCL1 00
5:4 P0.2 GPIO Port 0.2 TXD0 Reserved Reserved 00
7:6 P0.3 GPIO Port 0.3 RXD0 Reserved Reserved 00
9:8 P0.4 GPIO Port 0.4 I2SRX_CLK RD2[1] CAP2.0 00
11:10 P0.5 GPIO Port 0.5 I2SRX_WS TD2[1] CAP2.1 00
13:12 P0.6 GPIO Port 0.6 I2SRX_SDA SSEL1 MAT2.0 00
15:14 P0.7 GPIO Port 0.7 I2STX_CLK SCK1 MAT2.1 00
17:16 P0.8 GPIO Port 0.8 I2STX_WS MISO1 MAT2.2 00

(LPC2364/65/66/67/68 and LPC2387)
PINSEL0 Pin Function when Function when 01 Function Function Reset
name 00 when 10 when 11 value
19:18 P0.9 GPIO Port 0.9 I2STX_SDA MOSI1 MAT2.3 00
21:20 P0.10 GPIO Port 0.10 TXD2 SDA2 MAT3.0 00
23:22 P0.11 GPIO Port 0.11 RXD2 SCL2 MAT3.1 00
25:24 - Reserved Reserved Reserved Reserved 00
31:30 P0.15 GPIO Port 0.15 TXD1 SCK0 SCK 00
[1] LPC2361/62/64/66/68 and LPC2387 only. These bits are reserved on LPC2365/67.

(LPC2377/78 and LPC2388)
PINSEL0 Pin Function when Function when 01 Function when Function Reset
name 00 10 when 11 value
1:0 P0.0 GPIO Port 0.0 RD1[1] TXD3 SDA1 00
3:2 P0.1 GPIO Port 0.1 TD1[1] RXD3 SCL1 00
5:4 P0.2 GPIO Port 0.2 TXD0 Reserved Reserved 00
7:6 P0.3 GPIO Port 0.3 RXD0 Reserved Reserved 00
9:8 P0.4 GPIO Port 0.4 I2SRX_CLK RD2[1] CAP2.0 00
11:10 P0.5 GPIO Port 0.5 I2SRX_WS TD2[1] CAP2.1 00
13:12 P0.6 GPIO Port 0.6 I2SRX_SDA SSEL1 MAT2.0 00
15:14 P0.7 GPIO Port 0.7 I2STX_CLK SCK1 MAT2.1 00
17:16 P0.8 GPIO Port 0.8 I2STX_WS MISO1 MAT2.2 00
19:18 P0.9 GPIO Port 0.9 I2STX_SDA MOSI1 MAT2.3 00
21:20 P0.10 GPIO Port 0.10 TXD2 SDA2 MAT3.0 00
23:22 P0.11 GPIO Port 0.11 RXD2 SCL2 MAT3.1 00
25:24 P0.12 GPIO Port 0.12 USB_PPWR2[2] MISO1 AD0.6 00
27:26 P0.13 GPIO Port 0.13 USB_UP_LED2[1] MOSI1 AD0.7 00
29:28 P0.14 GPIO Port 0.14 USB_HSTEN2[2] USB_CONNEC SSEL1 00
T2[1]
31:30 P0.15 GPIO Port 0.15 TXD1 SCK0 SCK 00
[1] LPC2378/88 only. These bits are reserved on LPC2377.

[2] LPC2388 only. These bits are reserved on LPC2377/78.
9.5.2 Pin Function Select Register 1 (PINSEL1 - 0xE002 C004)

IO0DIR (or the FIO0DIR register if the enhanced GPIO function is selected for port 0)
register is effective only when the GPIO function is selected for a pin. For other functions


(LPC2364/65/66/67/68 and LPC2387)
PINSEL1 Pin Function when Function Function Function Reset
name 00 when 01 when 10 when 11 value
1:0 P0.16 GPIO Port 0.16 RXD1 SSEL0 SSEL 00
3:2 P0.17 GPIO Port 0.17 CTS1 MISO0 MISO 00
5:4 P0.18 GPIO Port 0.18 DCD1 MOSI0 MOSI 00
7:6 P0.19 GPIO Port 0.19 DSR1 MCICLK SDA1 00
9:8 P0.20 GPIO Port 0.20 DTR1 MCICMD SCL1 00
11:10 P0.21 GPIO Port 0.21 RI1 MCIPWR RD1[1] 00
13:12 P0.22 GPIO Port 0.22 RTS1 MCIDAT0 TD1[1] 00
15:14 P0.23 GPIO Port 0.23 AD0.0 I2SRX_CLK CAP3.0 00
17:16 P0.24 GPIO Port 0.24 AD0.1 I2SRX_WS CAP3.1 00
19:18 P0.25 GPIO Port 0.25 AD0.2 I2SRX_SDA TXD3 00
21:20 P0.26 GPIO Port 0.26 AD0.3 AOUT RXD3 00
23:22 P0.27[2] GPIO Port 0.27 SDA0 Reserved Reserved 00
25:24 P0.28[2] GPIO Port 0.28 SCL0 Reserved Reserved 00
27:26 P0.29 GPIO Port 0.29 USB_D1 Reserved Reserved 00
29:28 P0.30 GPIO Port 0.30 USB_D Reserved Reserved 00
31:30 P0.31 Reserved Reserved Reserved Reserved 00
[2] Pins P027] and P0[28] are open-drain for I2C0 and GPIO functionality for I2C-bus compliance.

(LPC2377/78 and LPC2388)
1:0 P0.16 GPIO Port 0.16 RXD1 SSEL0 SSEL 00
3:2 P0.17 GPIO Port 0.17 CTS1 MISO0 MISO 00
5:4 P0.18 GPIO Port 0.18 DCD1 MOSI0 MOSI 00
7:6 P0.19 GPIO Port 0.19 DSR1 MCICLK SDA1 00
9:8 P0.20 GPIO Port 0.20 DTR1 MCICMD SCL1 00
11:10 P0.21 GPIO Port 0.21 RI1 MCIPWR RD1[1] 00
13:12 P0.22 GPIO Port 0.22 RTS1 MCIDAT0 TD1[1] 00
15:14 P0.23 GPIO Port 0.23 AD0.0 I2SRX_CLK CAP3.0 00
17:16 P0.24 GPIO Port 0.24 AD0.1 I2SRX_WS CAP3.1 00
19:18 P0.25 GPIO Port 0.25 AD0.2 I2SRX_SDA TXD3 00
21:20 P0.26 GPIO Port 0.26 AD0.3 AOUT RXD3 00
23:22 P0.27[2] GPIO Port 0.27 SDA0 Reserved Reserved 00
25:24 P0.28[2] GPIO Port 0.28 SCL0 Reserved Reserved 00

(LPC2377/78 and LPC2388)
27:26 P0.29 GPIO Port 0.29 USB_D Reserved Reserved 00
29:28 P0.30 GPIO Port 0.30 USB_D Reserved Reserved 00
31:30 P0.31 GPIO Port 0.30 USB_D+2 Reserved Reserved 00
[1] LPC2378/88 only. These bits are reserved on LPC2377.

[2] Pins P027] and P0[28] are open-drain for I2C0 and GPIO functionality for I2C-bus compliance.
9.5.3 Pin Function Select register 2 (PINSEL2 - 0xE002 C008)

9.5.3.1 100-pin packages and 144-pin packages

(LPC2364/65/66/67/68, LPC2377/78, LPC2387, LPC2388)
PINSEL2 Pin Function when Function when Function Function Reset
name 00 01 when 10 when 11 value
1:0 P1.0 GPIO Port 1.0 ENET_TXD0 Reserved Reserved 00
3:2 P1.1 GPIO Port 1.1 ENET_TXD1 Reserved Reserved 00
9:8 P1.4 GPIO Port 1.4 ENET_TX_EN Reserved Reserved 00
17:16 P1.8 GPIO Port 1.8 ENET_CRS Reserved Reserved 00
19:18 P1.9 GPIO Port 1.9 ENET_RXD0 Reserved Reserved 00
21:20 P1.10 GPIO Port 1.10 ENET_RXD1 Reserved Reserved 00
29:28 P1.14 GPIO Port 1.14 ENET_RX_ER Reserved Reserved 00
31:30 P1.15 GPIO Port 1.15 ENET_REF_CLK Reserved Reserved 00
9.5.4 Pin Function Select Register 3 (PINSEL3 - 0xE002 C00C)

direction is controlled automatically.


Table 110. Pin function select register 3 (PINSEL3 - address 0xE002 C00C) bit description
(LPC2361/62/64/65/66/67/68 and LPC2387)
PINSEL3 Pin Function when Function when Function Function Reset
name 00 01 when 10 when 11 value
1:0 P1.16 GPIO Port 1.16 ENET_MDC Reserved Reserved 00
3:2 P1.17 GPIO Port 1.17 ENET_MDIO Reserved Reserved 00
5:4 P1.18 GPIO Port 1.18 USB_UP_LED1[1] PWM1.1 CAP1.0 00
7:6 P1.19 GPIO Port 1.19 USB_TX_E1[2] USB_PPWR1 CAP1.1 00
[2]
9:8 P1.20 GPIO Port 1.20 USB_TX_DP1[2] PWM1.2 SCK0 00

11:10 P1.21 GPIO Port 1.21 USB_TX_DM1[2] PWM1.3 SSEL0 00
13:12 P1.22 GPIO Port 1.22 USB_RCV1[2] USB_PWRD1 MAT1.0 00
[2]
15:14 P1.23 GPIO Port 1.23 USB_RX_DP1[2] PWM1.4 MISO0 00

17:16 P1.24 GPIO Port 1.24 USB_RX_DM1[2] PWM1.5 MOSI0 00
19:18 P1.25 GPIO Port 1.25 USB_LS1[2] USB_HSTEN MAT1.1 00
1[2]
21:20 P1.26 GPIO Port 1.26 USB_SSPND1[2] PWM1.6 CAP0.0 00
23:22 P1.27 GPIO Port 1.27 USB_INT1[2] USB_OVRCR CAP0.1 00
1[2]
25:24 P1.28 GPIO Port 1.28 USB_SCL1[2] PCAP1.0 MAT0.0 00
27:26 P1.29 GPIO Port 1.29 USB_SDA1[2] PCAP1.1 MAT0.1 00
29:28 P1.30 GPIO Port 1.30 Reserved VBUS[1] AD0.4 00
31:30 P1.31 GPIO Port 1.31 Reserved SCK1 AD0.5 00
[1] LPC2361/62/64/66/68 and LPC2387 only. These bits are reserved for LPC2365/66.
[2] LPC2361/62 only.

(LPC2377/78 and LPC2388)
PINSEL3 Pin Function Function when Function when Function Reset
name when 00 01 10 when 11 value
1:0 P1.16 GPIO Port 1.16 ENET_MDC Reserved Reserved 00
3:2 P1.17 GPIO Port 1.17 ENET_MDIO Reserved Reserved 00
5:4 P1.18 GPIO Port 1.18 USB_UP_LED1[1] PWM1.1 CAP1.0 00
7:6 P1.19 GPIO Port 1.19 USB_TX_E1[2] USB_PPWR1[2] CAP1.1 00
9:8 P1.20 GPIO Port 1.20 USB_TX_DP1[2] PWM1.2 SCK0 00
11:10 P1.21 GPIO Port 1.21 USB_TX_DM1[2] PWM1.3 SSEL0 00
13:12 P1.22 GPIO Port 1.22 USB_RCV1[2] USB_PWRD1[2] MAT1.0 00
15:14 P1.23 GPIO Port 1.23 USB_RX_DP1[2] PWM1.4 MISO0 00
17:16 P1.24 GPIO Port 1.24 USB_RX_DM1[2] PWM1.5 MOSI0 00
19:18 P1.25 GPIO Port 1.25 USB_LS1[2] USB_HSTEN1[2] MAT1.1 00
21:20 P1.26 GPIO Port 1.26 USB_SSPND1[2] PWM1.6 CAP0.0 00

(LPC2377/78 and LPC2388)
PINSEL3 Pin Function Function when Function when Function Reset
name when 00 01 10 when 11 value
23:22 P1.27 GPIO Port 1.27 USB_INT1[2] USB_OVRCR1[2] CAP0.1 00
25:24 P1.28 GPIO Port 1.28 USB_SCL1[2] PCAP1.0 MAT0.0 00
27:26 P1.29 GPIO Port 1.29 USB_SDA1[2] PCAP1.1 MAT0.1 00
29:28 P1.30 GPIO Port 1.30 USB_PWRD2[2] VBUS [1] AD0.4 00
31:30 P1.31 GPIO Port 1.31 USB_OVRCR2[2] SCK1 AD0.5 00
[1] LPC2378 and LPC2388 only. These bits are reserved for LPC2377.
[2] LPC2388 only. These bits are reserved for LPC2377/78.

FIO2DIR register is effective only when the GPIO function is selected for a pin. For other
functions, direction is controlled automatically.

(LPC2364/65/66/67/68 and LPC2387)
PINSEL4 Pin Function when Function when 01 Function Function when Reset
name 00 when 10 11 value
1:0 P2.0 GPIO Port 2.0 PWM1.1 TXD1 TRACECLK[1] 00
3:2 P2.1 GPIO Port 2.1 PWM1.2 RXD1 PIPESTAT0[1] 00
5:4 P2.2 GPIO Port 2.2 PWM1.3 CTS1 PIPESTAT1[1] 00
7:6 P2.3 GPIO Port 2.3 PWM1.4 DCD1 PIPESTAT2[1] 00
9:8 P2.4 GPIO Port 2.4 PWM1.5 DSR1 TRACESYNC[1] 00
11:10 P2.5 GPIO Port 2.5 PWM1.6 DTR1 TRACEPKT0[1] 00
13:12 P2.6 GPIO Port 2.6 PCAP1.0 RI1 TRACEPKT1[1] 00
15:14 P2.7 GPIO Port 2.7 RD2[2] RTS1 TRACEPKT2[1] 00
17:16 P2.8 GPIO Port 2.8 TD2[2] TXD2 TRACEPKT3[1] 00
19:18 P2.9 GPIO Port 2.9 USB_CONNECT1[2] RXD2 EXTIN0[1] 00
21:20 P2.10 GPIO Port 2.10 EINT0 Reserved Reserved 00
23:22 P2.11 GPIO Port 2.11 EINT1 MCIDAT1 I2STX_CLK 00
25:24 P2.12 GPIO Port 2.12 EINT2 MCIDAT2 I2STX_WS 00
27:26 P2.13 GPIO Port 2.13 EINT3 MCIDAT3 I2STX_SDA 00
[1] See Section 9.5.11 “Pin Function Select Register 10 (PINSEL10 - 0xE002 C028)” for details on using the
ETM functionality.


(LPC2377/78 and LPC2388)
PINSEL4 Pin Function when Function when 01 Function Function when Reset
name 00 when 10 11 value
1:0 P2.0 GPIO Port 2.0 PWM1.1 TXD1 TRACECLK[1] 00
3:2 P2.1 GPIO Port 2.1 PWM1.2 RXD1 PIPESTAT0[1] 00
5:4 P2.2 GPIO Port 2.2 PWM1.3 CTS1 PIPESTAT1[1] 00
7:6 P2.3 GPIO Port 2.3 PWM1.4 DCD1 PIPESTAT2[1] 00
9:8 P2.4 GPIO Port 2.4 PWM1.5 DSR1 TRACESYNC[1] 00
11:10 P2.5 GPIO Port 2.5 PWM1.6 DTR1 TRACEPKT0[1] 00
13:12 P2.6 GPIO Port 2.6 PCAP1.0 RI1 TRACEPKT1[1] 00
15:14 P2.7 GPIO Port 2.7 RD2[2] RTS1 TRACEPKT2[1] 00
17:16 P2.8 GPIO Port 2.8 TD2[2] TXD2 TRACEPKT3[1] 00
19:18 P2.9 GPIO Port 2.9 USB_CONNECT1[2] RXD2 EXTIN0[1] 00
21:20 P2.10 GPIO Port 2.10 EINT0 Reserved Reserved 00
23:22 P2.11 GPIO Port 2.11 EINT1 MCIDAT1 I2STX_CLK 00
25:24 P2.12 GPIO Port 2.12 EINT2 MCIDAT2 I2STX_WS 00
27:26 P2.13 GPIO Port 2.13 EINT3 MCIDAT3 I2STX_SDA 00
[1] See Section 9.5.11 “Pin Function Select Register 10 (PINSEL10 - 0xE002 C028)” for details on using the
ETM functionality.
[2] LPC2378 and LPC2388 only. These bits are reserved on LPC2377.

The PINSEL5 register is not used on the LPC23XX.


The PINSEL6 is not used for LPC236x and LPC2387. All bits are reserved.

(LPC2377/78 and LPC2388)
1:0 P3.0 GPIO Port 3.0 D0 Reserved Reserved 00

(LPC2377/78 and LPC2388)
9.5.8 Pin Function Select Register 7 (PINSEL7 - 0xE002 C01C)


(LPC2364/65/66/67/68 and LPC2387)
19:18 P3.25 GPIO Port 3.25 Reserved MAT0.0 PWM1.2 00


(LPC2377/78 and LPC2388)
15:14 P3.23 GPIO Port 3.23 Reserved CAP0.0 PCAP1.0 00
17:16 P3.24 GPIO Port 3.24 Reserved CAP0.1 PWM1.1 00


The PINSEL8 is not used for LPC2364/65/66/67/68 and LPC2387. All bits are reserved.

(LPC2377/78 and LPC2388)
PINSEL8 Pin Function Function Function Function Reset
name when 00 when 01 when 10 when 11 value
1:0 P4.0 GPIO Port 4.0 A0 Reserved Reserved 00

(LPC2377/78 and LPC2388)
PINSEL8 Pin Function Function Function Function Reset
name when 00 when 01 when 10 when 11 value


(LPC2364/66/65/67/68 and LPC2387)
25:24 P4.28 GPIO Port 4.28 Reserved MAT2.0 TXD3 00
27:26 P4.29 GPIO Port 4.29 Reserved MAT2.1 RXD3 00


(LPC2377/78 and LPC2388)
17:16 P4.24 GPIO Port 4.24 OE Reserved Reserved 00
19:18 P4.25 GPIO Port 4.25 - BLS0 Reserved 00
25:24 P4.28 GPIO Port 4.28 Reserved MAT2.0 TXD3 00
27:26 P4.29 GPIO Port 4.29 Reserved MAT2.1 RXD3 00
29:28 P4.30 GPIO Port 4.30 CS0 Reserved Reserved 00
31:30 P4.31 GPIO Port 4.31 CS1 Reserved Reserved 00

Only bit 3 of this register is used to control the ETM interface pins.
The value of the RTCK I/O pin is sampled when the external reset is asserted. When
RTCK pin is low during external reset, bit 3 in PINSEL10 is set to enable the ETM
interface pins. When RTCK pin is high during external reset, bit 3 in PINSEL10 is cleared
to disable the ETM interface pins.
The ETM interface control pin can also be modified by the software.
value
2:0 - - Reserved. Software should not write 1 to these bits. NA
3 GPIO/TRACE ETM interface pins control. RTCK, see
0 ETM interface is disabled. the text
above
1 ETM interface is enabled. ETM signals are available
on the pins hosting them regardless of the PINSEL4
content.
31:4 - - Reserved. Software should not write 1 to these bits. NA
9.5.12 Pin Mode select register 0 (PINMODE0 - 0xE002 C040)

This register controls pull-up/pull-down resistor configuration for PORT0 pins 0 to 15.

Table 121. Pin Mode select register 0 (PINMODE0 - address 0xE002 C040) bit description
PINMODE0 Symbol Value Description Reset
value
1:0 P0.00MODE PORT0 pin 0 on-chip pull-up/down resistor control. 00
00 P0.00 pin has a pull-up resistor enabled.
01 Reserved. This value should not be used.
10 P0.00 pin has neither pull-up nor pull-down.
11 P0.00 has a pull-down resistor enabled.
...

This register controls pull-up/pull-down resistor configuration for PORT0 pins 16 to 26. For
details see Section 9.4 “Pin mode select register values”.
PINMODE1 Symbol Description Reset
value
...
31:21 - Reserved
Remark: The pin mode cannot be selected for pins P0[27] to P0[31]. Pins P0[27] and
P0[28] are dedicated I2C open-drain pins without pull-up/down. Pins P0[29], P0[30],
P0[31] are USB specific pins without configurable pull-up or pull-down resistors.

value
...
9.5.15 Pin Mode select register 3 (PINMODE3 - 0xE002 C04C)


Table 124. Pin Mode select register 3 (PINMODE3 - address 0xE002 C04C) bit description
value
...

value
...

value
1:0 P2.16MODE Reserved 00
...
31:30 P2.31MODE Reserved 00

value
...
9.5.19 Pin Mode select register 7 (PINMODE7 - 0xE002 C05C)


Table 128. Pin Mode select register 7 (PINMODE7 - address 0xE002 C05C) bit description
value
...

value
...

value
...

UM10211
Chapter 10: LPC23XX General Purpose Input/Output ports
(GPIO)

GPIOs are configured using the following registers:
1. Power: always enabled.

2. Clock: For fast GPIO ports, see Section 4.7.1. For legacy GPIO ports, use the
PCLKSEL1 register (Table 50).
3. Pins: Select GPIO pins and their modes in PINSEL0 to PINSEL10 and PINMODE0 to
PINMODE10 (Section 9.5).
4. Wake-up: Use the INTWAKE register (Table 55) to configure GPIO ports 0 and 2 for
wake-up if needed.
5. Interrupts: Enable GPIO interrupts in IO0/2IntEnR (Table 150) or IO0/2IntEnF
(Table 151). Interrupts are enabled in the VIC using the VICIntEnable register
(Table 76).
10.2 Features
10.2.1 Digital I/O ports

• GPIO PORT0 and PORT1 are ports accessible via either the group of registers
providing enhanced features and accelerated port access or the legacy group of
registers. PORT2/3/4 are accessed as fast ports only.
• Accelerated GPIO functions:
– 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 GPIO 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 any 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
10.2.2 Interrupt generating digital ports

• PORT0 and PORT2 provide an interrupt for each port pin.
• Each interrupt can be programmed to generate an interrupt on a rising edge, a falling
edge, or both.

Chapter 10: LPC23XX General Purpose Input/Output ports (GPIO)
• Edge detection is asynchronous, so it may operate when clocks are not present, such
as during Power-down mode. With this feature, level triggered interrupts are not
needed.
• Each enabled interrupt contributes to a Wake-up signal that can be used to bring the
part out of Power-down mode.
• Registers provide software a view of pending rising edge interrupts, pending falling
edge interrupts, and overall pending GPIO interrupts.
• GPIO0 and GPIO2 interrupts share the same VIC slot with the External Interrupt 3
event.
10.3 Applications
• General purpose I/O
• Driving LEDs, or other indicators
• Controlling off-chip devices
• Sensing digital inputs, detecting edges
• Bringing the part out of Power Down mode

Table 131. GPIO pin description
Pin Name Type Description
P0.[31:0] Input/ General purpose input/output. These are typically shared with other
P1.[31:0] Output peripherals functions and will therefore not all be available in an
P2.[31:0] application. Packaging options may affect the number of GPIOs
P3.[31:0] available in a particular device (see Table 2 and Table 101).
P4.[31:0] Some pins may be limited by requirements of the alternate functions of
the pin. For example, the pins containing the I2C0 function are
open-drain for any function of that pin. Details may be found in the
LPC2300 pin description.

LPC2300 has up to five 32-bit General Purpose I/O ports. PORT0 and PORT1 are
controlled via two groups of registers as shown in Table 132 and Table 133. Apart from
them, LPC2300 can have three additional 32-bit ports, PORT2, PORT3 and PORT4.
Details on a specific GPIO port usage can be found in Section 8.1 and Section 9.5.
Legacy registers shown in Table 132 allow backward compatibility with earlier family
devices, using existing code. The functions and relative timing of older GPIO
implementations is preserved. Only PORT0 and PORT1 can be controlled via the legacy
port registers.
The registers in Table 133 represent the enhanced GPIO features available on all of the
LPC2300’s GPIO ports. These registers are located directly on the local bus of the CPU
for the fastest possible read and write timing. They can be accessed as byte or half-word
long data, too. A mask register allows access to a group of bits in a single GPIO port
independently from other bits in the same port.

When PORT0 and PORT1 are used, user must select whether these ports will be
accessed via registers that provide enhanced features or a legacy set of registers (see
Section 3.7 “Other system controls and status flags” on page 38). 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.
Table 132. GPIO register map (legacy APB accessible registers)

Generic Description Access Reset PORTn Register
Name value[1] Address & Name
IOPIN GPIO Port Pin value register. The current state of the GPIO R/W NA IO0PIN - 0xE002 8000
configured port pins can always be read from this register, IO1PIN - 0xE002 8010
regardless of pin direction. By writing to this register port’s pins will
be set to the desired level instantaneously.
IOSET GPIO Port Output Set register. This register controls the state of R/W 0x0 IO0SET - 0xE002 8004
output pins in conjunction with the IOCLR register. Writing ones IO1SET - 0xE002 8014
produces highs at the corresponding port pins. Writing zeroes has
no effect.
IODIR GPIO Port Direction control register. This register individually R/W 0x0 IO0DIR - 0xE002 8008
controls the direction of each port pin. IO1DIR - 0xE002 8018
IOCLR GPIO Port Output Clear register. This register controls the state of WO 0x0 IO0CLR - 0xE002 800C
output pins. Writing ones produces lows at the corresponding port IO1CLR - 0xE002 801C
pins and clears the corresponding bits in the IOSET register.
Writing zeroes has no effect.
[1] Reset value reflects the data stored in used bits only. It does not include reserved bits content.

Table 133. GPIO register map (local bus accessible registers - enhanced GPIO features)
FIODIR Fast GPIO Port Direction control register. This register R/W 0x0 FIO0DIR - 0x3FFF C000
individually controls the direction of each port pin. FIO1DIR - 0x3FFF C020
FIO2DIR - 0x3FFF C040
FIOMASK Fast Mask register for port. Writes, sets, clears, and reads to R/W 0x0 FIO0MASK - 0x3FFF C010
port (done via writes to FIOPIN, FIOSET, and FIOCLR, and FIO1MASK - 0x3FFF C030
reads of FIOPIN) alter or return only the bits enabled by zeros FIO2MASK - 0x3FFF C050
in this register. FIO3MASK - 0x3FFF C070
FIO4MASK - 0x3FFF C090
FIOPIN Fast Port Pin value register using FIOMASK. The current state R/W 0x0 FIO0PIN - 0x3FFF C014
of digital port pins can be read from this register, regardless of FIO1PIN - 0x3FFF C034
pin direction or alternate function selection (as long as pins are FIO2PIN - 0x3FFF C054
not configured as an input to ADC). The value read is masked FIO3PIN - 0x3FFF C074
by ANDing with inverted FIOMASK. Writing to this register FIO4PIN - 0x3FFF C094
places corresponding values in all bits enabled by zeros in
FIOMASK.
Important: if a FIOPIN register is read, its bit(s) masked with 1
in the FIOMASK register will be set to 0 regardless of the
physical pin state.
FIOSET Fast Port Output Set register using FIOMASK. This register R/W 0x0 FIO0SET - 0x3FFF C018
controls the state of output pins. Writing 1s produces highs at FIO1SET - 0x3FFF C038
the corresponding port pins. Writing 0s has no effect. Reading FIO2SET - 0x3FFF C058
this register returns the current contents of the port output FIO3SET - 0x3FFF C078
register. Only bits enabled by 0 in FIOMASK can be altered. FIO4SET - 0x3FFF C098
FIOCLR Fast Port Output Clear register using FIOMASK0. This register WO 0x0 FIO0CLR - 0x3FFF C01C
controls the state of output pins. Writing 1s produces lows at FIO1CLR - 0x3FFF C03C
the corresponding port pins. Writing 0s has no effect. Only bits FIO2CLR - 0x3FFF C05C
enabled by 0 in FIOMASK0 can be altered. FIO3CLR - 0x3FFF C07C
FIO4CLR - 0x3FFF C09C
Table 134. GPIO interrupt register map

IntEnR GPIO Interrupt Enable for Rising edge. R/W 0x0 IO0IntEnR - 0xE002 8090
IO2IntEnR - 0xE002 80B0
IntEnF GPIO Interrupt Enable for Falling edge. R/W 0x0 IO0IntEnR - 0xE002 8094
IO2IntEnR - 0xE002 80B4
IntStatR GPIO Interrupt Status for Rising edge. RO 0x0 IO0IntStatR - 0xE002 8084
IO2IntStatR - 0xE002 80A4
IntStatF GPIO Interrupt Status for Falling edge. RO 0x0 IO0IntStatF - 0xE002 8088
IO2IntStatF - 0xE002 80A8
IntClr GPIO Interrupt Clear. WO 0x0 IO0IntClr - 0xE002 808C
IO2IntClr - 0xE002 80AC
IntStatus GPIO overall Interrupt Status. RO 0x00 IOIntStatus - 0xE002 8080

10.5.1 GPIO port Direction register IODIR and FIODIR(IO[0/1]DIR -

0xE002 80[0/1]8 and FIO[0/1/2/3/4]DIR - 0x3FFF C0[0/2/4/6/8]0)
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.
Remark: GPIO pins P0.29 and P0.30 are shared with the USB D+/ pins and must have
the same direction. If either P0DIR bits 29 or 30 are configured LOW in the IO0DIR or
FIO0DIR registers, both, P0.29 and P0.30, are inputs. If both, P0DIR bit 29 and bit 30 are
HIGH, both, P0.29 and P0.30, are outputs.
Legacy registers are the IO0DIR and IO1DIR while the enhanced GPIO functions are
supported via the FIO0DIR, FIO1DIR, FIO2DIR, FIO3DIR and FIO4DIR registers.
Table 135. GPIO port Direction register (IO0DIR - address 0xE002 8008 and IO1DIR - address
0xE002 8018) bit description
value
31:0 P0xDIR Slow GPIO Direction PORTx control bits. Bit 0 in IOxDIR 0x0
or controls pin Px.0, bit 31 IOxDIR controls pin Px.31.
P1xDIR 0 Controlled pin is an input pin.
1 Controlled pin is an output pin.
Table 136. Fast GPIO port Direction register (FIO[0/1/2/3/4]DIR - address

0x3FFF C0[0/2/4/6/8]0) bit description
value
31:0 FP0xDIR Fast GPIO Direction PORTx control bits. Bit 0 in FIOxDIR 0x0
FP1xDIR controls pin Px.0, bit 31 in FIOxDIR controls pin Px.31.
FP2xDIR 0 Controlled pin is input.
FP3xDIR
FP4xDIR 1 Controlled 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 137, too. Next to providing the same functions as the FIODIR register, these
additional registers allow easier and faster access to the physical port pins.

Table 137. Fast GPIO port Direction control byte and half-word accessible register
description
Generic Description Register Reset PORTn Register
Register length (bits) value Address & Name
name & access
FIOxDIR0 Fast GPIO Port x Direction 8 (byte) 0x00 FIO0DIR0 - 0x3FFF C000
control register 0. Bit 0 in R/W FIO1DIR0 - 0x3FFF C020
FIOxDIR0 register corresponds FIO2DIR0 - 0x3FFF C040
to pin Px.0 ... bit 7 to pin Px.7. FIO3DIR0 - 0x3FFF C060
FIO4DIR0 - 0x3FFF C080
to pin Px.8 ... bit 7 to pin Px.15. FIO3DIR1 - 0x3FFF C061
FIO4DIR1 - 0x3FFF C081
FIO0DIR2 Fast GPIO Port x Direction 8 (byte) 0x00 FIO0DIR2 - 0x3FFF C002
to pin Px.16 ... bit 7 to pin FIO3DIR2 - 0x3FFF C062
Px.23. FIO4DIR2 - 0x3FFF C082
to pin Px.24 ... bit 7 to pin FIO3DIR3 - 0x3FFF C063
Px.31. FIO4DIR3 - 0x3FFF C083
FIOxDIRL Fast GPIO Port x Direction 16 (half-word) 0x0000 FIO0DIRL - 0x3FFF C000
control Lower half-word R/W FIO1DIRL - 0x3FFF C020
register. Bit 0 in FIOxDIRL FIO2DIRL - 0x3FFF C040
register corresponds to pin FIO3DIRL - 0x3FFF C060
Px.0 ... bit 15 to pin Px.15. FIO4DIRL - 0x3FFF C080
FIOxDIRU Fast GPIO Port x Direction 16 (half-word) 0x0000 FIO0DIRU - 0x3FFF C002
control Upper half-word R/W FIO1DIRU - 0x3FFF C022
register. Bit 0 in FIOxDIRU FIO2DIRU - 0x3FFF C042
register corresponds to Px.16 FIO3DIRU - 0x3FFF C062
... bit 15 to Px.31. FIO4DIRU - 0x3FFF C082
10.5.2 GPIO port output Set register IOSET and FIOSET(IO[0/1]SET -

0xE002 80[0/1]4 and FIO[0/1/2/3/4]SET - 0x3FFF C0[1/3/5/7/9]8)
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 secondary function, writing
1 to the corresponding bit in the IOSET has no effect.
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 and IO1SET while the enhanced GPIOs are supported
via the FIO0SET, FIO1SET, FIO2SET, FIO3SET, and FIO4SET registers. Access to a port
pin via the FIOSET register is conditioned by the corresponding bit of the FIOMASK
register (see Section 10.5.5 “Fast GPIO port Mask register
FIOMASK(FIO[0/1/2/3/4]MASK - 0x3FFF C0[1/3/5/7/9]0)”).

Table 138. GPIO port output Set register (IO0SET - address 0xE002 8004 and IO1SET -
address 0xE002 8014) bit description
value
31:0 P0xSET Slow GPIO output value Set bits. Bit 0 in IOxSET controls pin 0x0
or Px.0, bit 31 in IOxSET controls pin Px.31.
P1xSET 0 Controlled pin output is unchanged.
1 Controlled pin output is set to HIGH.
Table 139. Fast GPIO port output Set register (FIO[0/1/2/3/4]SET - address
value
31:0 FP0xSET Fast GPIO output value Set bits. Bit 0 in FIOxSET controls pin 0x0
FP1xSET Px.0, bit 31 in FIOxSET controls pin Px.31.
FP2xSET 0 Controlled pin output is unchanged.
FP3xSET
FP4xSET 1 Controlled pin output is set to HIGH.
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 140, too. Next to providing the same functions as the FIOSET register, these
Table 140. Fast GPIO port output Set byte and half-word accessible register description
name & access
FIOxSET0 Fast GPIO Port x output Set 8 (byte) 0x00 FIO0SET0 - 0x3FFF C018
register 0. Bit 0 in FIOxSET0 R/W FIO1SET0 - 0x3FFF C038
register corresponds to pin FIO2SET0 - 0x3FFF C058
Px.0 ... bit 7 to pin Px.7. FIO3SET0 - 0x3FFF C078
FIO4SET0 - 0x3FFF C098
FIOxSET1 Fast GPIO Port x output Set 8 (byte) 0x00 FIO0SET1 - 0x3FFF C019
register 1. Bit 0 in FIOxSET1 R/W FIO1SET1 - 0x3FFF C039
register corresponds to pin FIO2SET1 - 0x3FFF C059
Px.8 ... bit 7 to pin Px.15. FIO3SET1 - 0x3FFF C079
FIO4SET1 - 0x3FFF C099
FIOxSET2 Fast GPIO Port x output Set 8 (byte) 0x00 FIO0SET2 - 0x3FFF C01A
register 2. Bit 0 in FIOxSET2 R/W FIO1SET2 - 0x3FFF C03A
register corresponds to pin FIO2SET2 - 0x3FFF C05A
Px.16 ... bit 7 to pin Px.23. FIO3SET2 - 0x3FFF C07A
FIO4SET2 - 0x3FFF C09A

Table 140. Fast GPIO port output Set byte and half-word accessible register description
name & access
FIOxSET3 Fast GPIO Port x output Set 8 (byte) 0x00 FIO0SET3 - 0x3FFF C01B
register 3. Bit 0 in FIOxSET3 R/W FIO1SET3 - 0x3FFF C03B
register corresponds to pin FIO2SET3 - 0x3FFF C05B
Px.24 ... bit 7 to pin Px.31. FIO3SET3 - 0x3FFF C07B
FIO4SET3 - 0x3FFF C09B
FIOxSETL Fast GPIO Port x output Set 16 (half-word) 0x0000 FIO0SETL - 0x3FFF C018
Lower half-word register. Bit 0 R/W FIO1SETL - 0x3FFF C038
in FIOxSETL register FIO2SETL - 0x3FFF C058
corresponds to pin Px.0 ... bit FIO3SETL - 0x3FFF C078
15 to pin Px.15. FIO4SETL - 0x3FFF C098
FIOxSETU Fast GPIO Port x output Set 16 (half-word) 0x0000 FIO0SETU - 0x3FFF C01A
Upper half-word register. Bit 0 R/W FIO1SETU - 0x3FFF C03A
in FIOxSETU register FIO2SETU - 0x3FFF C05A
corresponds to Px.16 ... bit FIO3SETU - 0x3FFF C07A
15 to Px.31. FIO4SETU - 0x3FFF C09A
10.5.3 GPIO port output Clear register IOCLR and FIOCLR (IO[0/1]CLR -
0xE002 80[0/1]C and FIO[0/1/2/3/4]CLR - 0x3FFF C0[1/3/5/7/9]C)
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 level at the corresponding port pin and clears
the corresponding bit in the IOSET register. Writing 0 has no effect. If any pin is configured
as an input or a secondary function, writing to IOCLR has no effect.
Legacy registers are the IO0CLR and IO1CLR while the enhanced GPIOs are supported
via the FIO0CLR, FIO1CLR, FIO2CLR, FIO3CLR, and FIO4CLR registers. Access to a
port pin via the FIOCLR register is conditioned by the corresponding bit of the FIOMASK
Table 141. GPIO port output Clear register (IO0CLR - address 0xE002 800C and IO1CLR -
address 0xE002 801C) bit description
value
31:0 P0xCLR Slow GPIO output value Clear bits. Bit 0 in IOxCLR controls pin 0x0
or Px.0, bit 31 in IOxCLR controls pin Px.31.
P1xCLR 0 Controlled pin output is unchanged.
1 Controlled pin output is set to LOW.
Table 142. Fast GPIO port output Clear register (FIO[0/1/2/3/4]CLR - address
0x3FFF C0[1/3/5/7/9]C) bit description
value
31:0 FP0xCLR Fast GPIO output value Clear bits. Bit 0 in FIOxCLR controls pin 0x0
FP1xCLR Px.0, bit 31 controls pin Px.31.
FP2xCLR 0 Controlled pin output is unchanged.
FP3xCLR
FP4xCLR 1 Controlled pin output is set to LOW.

Aside from the 32-bit long and word only accessible FIOCLR register, every fast GPIO
Table 143, too. Next to providing the same functions as the FIOCLR register, these
Table 143. Fast GPIO port output Clear byte and half-word accessible register description
name & access
FIOxCLR0 Fast GPIO Port x output 8 (byte) 0x00 FIO0CLR0 - 0x3FFF C01C
Clear register 0. Bit 0 in WO FIO1CLR0 - 0x3FFF C03C
FIOxCLR0 register FIO2CLR0 - 0x3FFF C05C
corresponds to pin Px.0 ... bit FIO3CLR0 - 0x3FFF C07C
7 to pin Px.7. FIO4CLR0 - 0x3FFF C09C
FIOxCLR1 Fast GPIO Port x output 8 (byte) 0x00 FIO0CLR1 - 0x3FFF C01D
Clear register 1. Bit 0 in WO FIO1CLR1 - 0x3FFF C03D
FIOxCLR1 register FIO2CLR1 - 0x3FFF C05D
corresponds to pin Px.8 ... bit FIO3CLR1 - 0x3FFF C07D
7 to pin Px.15. FIO4CLR1 - 0x3FFF C09D
FIOxCLR2 Fast GPIO Port x output 8 (byte) 0x00 FIO0CLR2 - 0x3FFF C01E
Clear register 2. Bit 0 in WO FIO1CLR2 - 0x3FFF C03E
FIOxCLR2 register FIO2CLR2 - 0x3FFF C05E
corresponds to pin Px.16 ... FIO3CLR2 - 0x3FFF C07E
bit 7 to pin Px.23. FIO4CLR2 - 0x3FFF C09E
FIOxCLR3 Fast GPIO Port x output 8 (byte) 0x00 FIO0CLR3 - 0x3FFF C01F
Clear register 3. Bit 0 in WO FIO1CLR3 - 0x3FFF C03F
FIOxCLR3 register FIO2CLR3 - 0x3FFF C05F
corresponds to pin Px.24 ... FIO3CLR3 - 0x3FFF C07F
bit 7 to pin Px.31. FIO4CLR3 - 0x3FFF C09F
FIOxCLRL Fast GPIO Port x output 16 (half-word) 0x0000 FIO0CLRL - 0x3FFF C01C
Clear Lower half-word WO FIO1CLRL - 0x3FFF C03C
register. Bit 0 in FIOxCLRL FIO2CLRL - 0x3FFF C05C
register corresponds to pin FIO3CLRL - 0x3FFF C07C
Px.0 ... bit 15 to pin Px.15. FIO4CLRL - 0x3FFF C09C
FIOxCLRU Fast GPIO Port x output 16 (half-word) 0x0000 FIO0CLRU - 0x3FFF C01E
Clear Upper half-word WO FIO1CLRU - 0x3FFF C03E
register. Bit 0 in FIOxCLRU FIO2CLRU - 0x3FFF C05E
register corresponds to pin FIO3CLRU - 0x3FFF C07E
Px.16 ... bit 15 to Px.31. FIO4CLRU - 0x3FFF C09E
10.5.4 GPIO port Pin value register IOPIN and FIOPIN (IO[0/1]PIN -
0xE002 80[0/1]0 and FIO[0/1/2/3/4]PIN - 0x3FFF C0[1/3/5/7/9]4)
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.
If a pin has an analog function as one of its options, the pin state cannot be read if the
analog configuration is selected. Selecting the pin as an A/D input disconnects 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 and IO1PIN while the enhanced GPIOs are supported
via the FIO0PIN, FIO1PIN, FIO2PIN, FIO3PIN and FIO4PIN registers. Access to a port
pin via the FIOPIN register is conditioned by the corresponding bit of the FIOMASK
Only pins masked with zeros in the Mask register (see Section 10.5.5 “Fast GPIO port
Mask register FIOMASK(FIO[0/1/2/3/4]MASK - 0x3FFF C0[1/3/5/7/9]0)”) will be
correlated to the current content of the Fast GPIO port pin value register.
Table 144. GPIO port Pin value register (IO0PIN - address 0xE002 8000 and IO1PIN - address
value
31:0 P0xVAL Slow GPIO pin value bits. Bit 0 in IOxPIN corresponds to pin 0x0
or Px.0, bit 31 in IOxPIN corresponds to pin Px.31.
P1xVAL Reading a 0 indicates that the port pin’s current state is LOW.
0 Controlled pin output is set to LOW.
1 Reading a 1 indicates that the port pin’s current state is HIGH.
Controlled pin output is set to HIGH.
Table 145. Fast GPIO port Pin value register (FIO[0/1/2/3/4]PIN - address
value
31:0 FP0xVAL Fast GPIO pin value bits. Bit 0 in FIOxPIN corresponds to pin 0x0
FP1xVAL Px.0, bit 31 in FIOxPIN corresponds to pin Px.31. Only bits also
FP2xVAL set to 0 in the FIOxMASK register are affected by a write or
FP3xVAL show the pin’s actual logic state.
FP4xVAL Reading a 0 indicates that the port pin’s current state is LOW.
0 Writing a 0 sets the output register value to LOW.
1 Reading a 1 indicates that the port pin’s current state is HIGH.
Writing a 1 sets the output register value to HIGH.
Aside from the 32-bit long and word only accessible FIOPIN register, every fast GPIO port
can also be controlled via several byte and half-word accessible registers listed in
Table 146, too. Next to providing the same functions as the FIOPIN register, these

Table 146. Fast GPIO port Pin value byte and half-word accessible register description
name & access
FIOxPIN0 Fast GPIO Port x Pin value 8 (byte) 0x00 FIO0PIN0 - 0x3FFF C014
register 0. Bit 0 in FIOxPIN0 R/W FIO1PIN0 - 0x3FFF C034
register corresponds to pin FIO2PIN0 - 0x3FFF C054
Px.0 ... bit 7 to pin Px.7. FIO3PIN0 - 0x3FFF C074
FIO4PIN0 - 0x3FFF C094
FIOxPINL Fast GPIO Port x Pin value 16 (half-word) 0x0000 FIO0PINL - 0x3FFF C014
Lower half-word register. Bit 0 R/W FIO1PINL - 0x3FFF C034
in FIOxPINL register FIO2PINL - 0x3FFF C054
corresponds to pin Px.0 ... bit FIO3PINL - 0x3FFF C074
15 to pin Px.15. FIO4PINL - 0x3FFF C094
FIOxPINU Fast GPIO Port x Pin value 16 (half-word) 0x0000 FIO0PINU - 0x3FFF C016
Upper half-word register. Bit 0 R/W FIO1PINU - 0x3FFF C036
in FIOxPINU register FIO2PINU - 0x3FFF C056
corresponds to pin Px.16 ... bit FIO3PINU - 0x3FFF C076
15 to Px.31. FIO4PINU - 0x3FFF C096
10.5.5 Fast GPIO port Mask register FIOMASK(FIO[0/1/2/3/4]MASK -

0x3FFF C0[1/3/5/7/9]0)
This register is available in the enhanced group of registers only. It is used to select port
pins that will and will not be affected by write accesses to the FIOPIN, FIOSET or FIOCLR
register. Mask register also filters out port’s content when the FIOPIN register is read.
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 10.6 “GPIO usage notes” on page 184

Table 147. Fast GPIO port Mask register (FIO[0/1/2/3/4]MASK - address

value
31:0 FP0xMASK, Fast GPIO physical pin access control. 0x0
FP1xMASK, 0 Controlled pin is affected by writes to the port’s FIOSET,
FP2xMASK, FIOCLR, and FIOPIN register(s). Current state of the pin can
FP3xMASK be read from the FIOPIN register.
FP4xMASK
1 Controlled pin is not affected by writes into the port’s
FIOSET, FIOCLR and FIOPIN register(s). When the FIOPIN
register is read, this bit will not be updated with the state of
the physical pin.
Aside from the 32-bit long and word only accessible FIOMASK register, every fast GPIO
Table 148, too. Next to providing the same functions as the FIOMASK register, these
Table 148. Fast GPIO port Mask byte and half-word accessible register description
name & access
FIOxMASK0 Fast GPIO Port x Mask 8 (byte) 0x0 FIO0MASK0 - 0x3FFF C010
register 0. Bit 0 in R/W FIO1MASK0 - 0x3FFF C030
FIOxMASK0 register FIO2MASK0 - 0x3FFF C050
corresponds to pin Px.0 ... FIO3MASK0 - 0x3FFF C070
bit 7 to pin Px.7. FIO4MASK0 - 0x3FFF C090
FIOxMASKL Fast GPIO Port x Mask 16 0x0 FIO0MASKL - 0x3FFF C010
Lower half-word register. (half-word) FIO1MASKL - 0x3FFF C030
Bit 0 in FIOxMASKL R/W FIO2MASKL - 0x3FFF C050
register corresponds to pin FIO3MASKL - 0x3FFF C070
Px.0 ... bit 15 to pin Px.15. FIO4MASKL - 0x3FFF C090
FIOxMASKU Fast GPIO Port x Mask 16 0x0 FIO0MASKU - 0x3FFF C012
Upper half-word register. (half-word) FIO1MASKU - 0x3FFF C032
Bit 0 in FIOxMASKU R/W FIO2MASKU - 0x3FFF C053
register corresponds to pin FIO3MASKU - 0x3FFF C072
Px.16 ... bit 15 to Px.31. FIO4MASKU - 0x3FFF C092

10.5.6 GPIO interrupt registers

The following registers configure the pins of port 0 and port 2 to generate interrupts.
10.5.6.1 GPIO overall Interrupt Status register (IOIntStatus - 0xE002 8080)

This read-only register indicates the presence of interrupt pending on all of the GPIO ports
that support GPIO interrupts. Only one bit per port is used.
Table 149. GPIO overall Interrupt Status register (IOIntStatus - address 0xE002 8080) bit
description
value
0 P0Int PORT0 GPIO interrupt pending. 0
0 There are no pending interrupts on PORT0.
1 There is at least one pending interrupt on PORT0.
1 - - Reserved. The value read from a reserved bit is not defined. NA
2 P2Int PORT2 GPIO interrupt pending. 0
0 There are no pending interrupts on PORT2.
1 There is at least one pending interrupt on PORT2.
31:2 - - Reserved. The value read from a reserved bit is not defined. NA
10.5.6.2 GPIO Interrupt Enable for Rising edge register (IO0IntEnR - 0xE002 8090
and IO2IntEnR - 0xE002 80B0)
Each bit in these read-write registers enables the rising edge interrupt for the
corresponding GPIO port pin.
Table 150. GPIO Interrupt Enable for Rising edge register (IO0IntEnR - address 0xE002 8090
and IO2IntEnR - address 0xE002 80B0) bit description
value
31:0 P0xER Enable Rising edge. Bit 0 in IOxIntEnR corresponds to pin Px.0, 0
and bit 31 in IOxIntEnR corresponds to pin Px.31.
P2xER 0 Rising edge interrupt is disabled on the controlled pin.
1 Rising edge interrupt is enabled on the controlled pin.
10.5.6.3 GPIO Interrupt Enable for Falling edge register (IO0IntEnF - 0xE002 8094
and IO2IntEnF - 0xE002 80B4)
Each bit in these read-write registers enables the falling edge interrupt for the
Table 151. GPIO Interrupt Enable for Falling edge register (IO0IntEnF - address 0xE002 8094
and IO2IntEnF - address 0xE002 80B4) bit description
value
31:0 P0xEF Enable Falling edge. Bit 0 in IOxIntEnF corresponds to pin Px.0, 0
and bit 31 in IOxIntEnF corresponds to pin Px.31.
P2xEF 0 Falling edge interrupt is disabled on the controlled pin.
1 Falling edge interrupt is enabled on the controlled pin.

10.5.6.4 GPIO Interrupt Status for Rising edge register (IO0IntStatR - 0xE002 8084
and IO2IntStatR - 0xE002 80A4)
Each bit in these read-only registers indicates the rising edge interrupt status for the
corresponding port.
Table 152. GPIO Status for Rising edge register (IO0IntStatR - address 0xE002 8084 and
IO2IntStatR - address 0xE002 80A4) bit description
value
31:0 P0xREI Rising Edge Interrupt status. Bit 0 in IOxIntStatR corresponds to 0
and pin Px.0, bit 31 in IOxIntStatR corresponds to pin Px.31.
P2xREI 0 Rising edge has not been detected on the corresponding pin.
1 An interrupt is generated due to a rising edge on the
corresponding pin.
10.5.6.5 GPIO Interrupt Status for Falling edge register (IO0IntStatF - 0xE002 8088
and IO2IntStatF - 0xE002 80A8)
Each bit in these read-only registers indicates the rising edge interrupt status for the
corresponding port.
Table 153. GPIO Status for Falling edge register (IO0IntStatF - address 0xE002 8088 and
IO2IntStatF - address 0xE002 80A8) bit description
value
31:0 P0xFEI Falling Edge Interrupt status. Bit 0 in IOxIntStatF corresponds to 0
and pin Px.0, bit 31 in IOxIntStatF corresponds to pin Px.31.
P2xFEI 0 Falling edge has not been detected on the corresponding pin.
1 An interrupt is generated due to a falling edge on the
corresponding pin.
10.5.6.6 GPIO Interrupt Clear register (IO0IntClr - 0xE002 808C and IO2IntClr -
0xE002 80AC)
Writing a 1 into each bit in these write-only registers clears any interrupts for the
Table 154. GPIO Status for Falling edge register (IO0IntClr - address 0xE002 808C and
IO2IntClr - address 0xE002 80AC) bit description
value
31:0 P0xCI Clear GPIO port Interrupt. Bit 0 in IOxIntClr corresponds to pin 0
and Px.0, bit 31 in IOxIntClr corresponds to pin Px.31.
P2xCI 0 Corresponding bit in IOxIntStatR and/or IOxIntStatF is
unchanged.
1 Corresponding bit in IOxIntStatR and IOxStatF is cleared to 0.

10.6 GPIO usage notes
10.6.1 Example 1: sequential accesses to IOSET and IOCLR affecting the

same GPIO pin/bit
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 the example code:
IO0DIR = 0x0000 0080 ;pin P0.7 configured as output

IO0CLR = 0x0000 0080 ;P0.7 goes LOW
IO0SET = 0x0000 0080 ;P0.7 goes HIGH
IO0CLR = 0x0000 0080 ;P0.7 goes LOW
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.
10.6.2 Example 2: an instantaneous 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
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;

10.6.3 Writing 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 a 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.
10.6.4 Output signal frequency considerations when using the legacy and
enhanced GPIO registers
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
assembly code and executed in the ARM mode.

UM10211
Chapter 11: LPC23XX Ethernet

The Ethernet is not available on part LPC2361.

The Ethernet controller is configured using the following registers:
1. Power: In the PCONP register (Table 56), set bit PCENET.

Remark: On reset, the Ethernet block is disabled (PCENET = 0).
3. Pins: Select Ethernet pins and their modes in PINSEL2/3 and PINMODE2/3
(Section 9.5).
4. Wake-up: Use the INTWAKE register (Table 55) to enable activity on the Ethernet port
to wake up the microcontroller from Power-down mode.
5. Interrupts: Interrupts are enabled in the VIC using the VICIntEnable register
(Table 76).
6. Initialization: see Section 11.18.2.
11.3 Introduction
Remark: LPC23xx devices are RMII interfaced only.
The Ethernet block contains a full featured 10 Mbps or 100 Mbps Ethernet MAC (Media
Access Controller) designed to provide optimized performance through the use of DMA
hardware acceleration. Features include a generous suite of control registers, half or full
duplex operation, flow control, control frames, hardware acceleration for transmit retry,
receive packet filtering and wake-up on LAN activity. Automatic frame transmission and
reception with Scatter-Gather DMA off-loads many operations from the CPU.
The Ethernet block and the CPU share a dedicated AHB subsystem (AHB2) that is used
to access the Ethernet SRAM for Ethernet data, control, and status information. All other
AHB traffic in the LPC2300 takes place on a different AHB subsystem, effectively
separating Ethernet activity from the rest of the system. The Ethernet DMA can also
access off-chip memory via the External Memory Controller, as well as the SRAM located
on AHB1, if is not being used by the USB block. However, using memory other than the
Ethernet SRAM, especially off-chip memory (possible in LPC2377/78 and LPC2388 only),
will slow Ethernet access to memory and increase the loading of AHB1.
The Ethernet block interfaces between an off-chip Ethernet PHY using the RMII (reduced
MII) protocol and the on-chip MIIM (Media Independent Interface Management) serial
bus, also known as MDIO (Management Data Input/Output).

Table 155. Ethernet acronyms, abbreviations, and definitions

Acronym or Definition
Abbreviation
AHB Advanced High-performance bus
CRC Cyclic Redundancy Check
DMA Direct Memory Access
Double-word 64 bit entity
FCS Frame Check Sequence (CRC)
Fragment A (part of an) Ethernet frame; one or multiple fragments can add up to a single
Ethernet frame.
Frame An Ethernet frame consists of destination address, source address, length
type field, payload and frame check sequence.
Half-word 16 bit entity
LAN Local Area Network
MAC Media Access Control sublayer
MII Media Independent Interface
MIIM MII management
Octet An 8 bit data entity, used in lieu of "byte" by IEEE 802.3
Packet A frame that is transported across Ethernet; a packet consists of a preamble,
a start of frame delimiter and an Ethernet frame.
PHY Ethernet Physical Layer
RMII Reduced MII
Rx Receive
TCP/IP Transmission Control Protocol / Internet Protocol. The most common
high-level protocol used with Ethernet.
Tx Transmit
VLAN Virtual LAN
WoL Wake-up on LAN
Word 32 bit entity
11.4 Features
• Ethernet standards support:
– Supports 10 or 100 Mbps PHY devices including 10 Base-T, 100 Base-TX,
100 Base-FX, and 100 Base-T4.
– Fully compliant with IEEE standard 802.3.
– Fully compliant with 802.3x Full Duplex Flow Control and Half Duplex back
pressure.
– Flexible transmit and receive frame options.
– VLAN frame support.
• Memory management:
– Independent transmit and receive buffers memory mapped to shared SRAM.
– DMA managers with scatter/gather DMA and arrays of frame descriptors.

– Memory traffic optimized by buffering and pre-fetching.
• Enhanced Ethernet features:

– Receive filtering.
– Multicast and broadcast frame support for both transmit and receive.
– Optional automatic FCS insertion (CRC) for transmit.
– Selectable automatic transmit frame padding.
– Over-length frame support for both transmit and receive allows any length frames.
– Promiscuous receive mode.
– Automatic collision backoff and frame retransmission.
– Includes power management by clock switching.
– Wake-on-LAN power management support allows system wake-up: using the
receive filters or a magic frame detection filter.
• Physical interface:
– Attachment of external PHY chip through a standard Reduced MII (RMII) interface.
– PHY register access is available via the Media Independent Interface Management
(MIIM) interface.
11.5 Architecture and operation

Figure 31 shows the internal architecture of the Ethernet block.
IN TER F ACE
TRANSMIT
HOST
BU S
FLOW
REGISTERS
register CONTROL RMII
interface (AHB
R MII A DAP TER
slave)
ETH ER N ET MAC
AH B BU S
BUS IN T ERF AC E
TRANSMIT TRANSMIT ET HE RN ET PHY

DMA RETRY
RMII
DMA interface RECEIVE RECEIVE

(AHB master) DMA BUFFER
MIIM
RECEIVE
FILTER
ETHERNET
BLOCK
Fig 31. Ethernet block diagram
The block diagram for the Ethernet block consists of:

• The host registers module containing the registers in the software view and handling
AHB accesses to the Ethernet block. The host registers connect to the transmit and
receive data path as well as the MAC.
• The DMA to AHB interface. This provides an AHB master connection that allows the
Ethernet block to access the Ethernet SRAM for reading of descriptors, writing of
status, and reading and writing data buffers.
• The Ethernet MAC which interfaces to the off-chip PHY via an RMII interface.
• The transmit data path, including:
– The transmit DMA manager which reads descriptors and data from memory and
writes status to memory.
– The transmit retry module handling Ethernet retry and abort situations.
– The transmit flow control module which can insert Ethernet pause frames.
• The receive data path, including:

– The receive DMA manager which reads descriptors from memory and writes data
and status to memory.
– The Ethernet MAC which detects frame types by parsing part of the frame header.
– The receive filter which can filter out certain Ethernet frames by applying different
filtering schemes.
– The receive buffer implementing a delay for receive frames to allow the filter to
filter out certain frames before storing them to memory.
11.6 DMA engine functions

The Ethernet block is designed to provide optimized performance via DMA hardware
acceleration. Independent scatter/gather DMA engines connected to the AHB bus off-load
many data transfers from the ARM7 CPU.
Descriptors, which are stored in memory, contain information about fragments of incoming
or outgoing Ethernet frames. A fragment may be an entire frame or a much smaller
amount of data. Each descriptor contains a pointer to a memory buffer that holds data
associated with a fragment, the size of the fragment buffer, and details of how the
fragment will be transmitted or received.
Descriptors are stored in arrays in memory, which are located by pointer registers in the
Ethernet block. Other registers determine the size of the arrays, point to the next
descriptor in each array that will be used by the DMA engine, and point to the next
descriptor in each array that will be used by the Ethernet device driver.
11.7 Overview of DMA operation

The DMA engine makes use of a Receive descriptor array and a Transmit descriptor array
in memory. All or part of an Ethernet frame may be contained in a memory buffer
associated with a descriptor. When transmitting, the transmit DMA engine uses as many
descriptors as needed (one or more) to obtain (gather) all of the parts of a frame, and
sends them out in sequence. When receiving, the receive DMA engine also uses as many
descriptors as needed (one or more) to find places to store (scatter) all of the data in the
received frame.

The base address registers for the descriptor array, registers indicating the number of
descriptor array entries, and descriptor array input/output pointers are contained in the
Ethernet block. The descriptor entries and all transmit and receive packet data are stored
in memory which is not a part of the Ethernet block. The descriptor entries tell where
related frame data is stored in memory, certain aspects of how the data is handled, and
the result status of each Ethernet transaction.
Hardware in the DMA engine controls how data incoming from the Ethernet MAC is saved
to memory, causes fragment related status to be saved, and advances the hardware
receive pointer for incoming data. Driver software must handle the disposition of received
data, changing of descriptor data addresses (to avoid unnecessary data movement), and
advancing the software receive pointer. The two pointers create a circular queue in the
descriptor array and allow both the DMA hardware and the driver software to know which
descriptors (if any) are available for their use, including whether the descriptor array is
empty or full.
Similarly, driver software must set up pointers to data that will be transmitted by the
Ethernet MAC, giving instructions for each fragment of data, and advancing the software
transmit pointer for outgoing data. Hardware in the DMA engine reads this information and
sends the data to the Ethernet MAC interface when possible, updating the status and
advancing the hardware transmit pointer.
11.8 Ethernet Packet

Figure 32 illustrates the different fields in an Ethernet packet.

ethernet packet
PREAMBLE
ETHERNET FRAME
7 bytes
start-of-frame
delimiter
1 byte
DESTINATION SOURCE OPTIONAL LEN

PAYLOAD FCS
ADDRESS ADDRESS VLAN TYPE
DesA DesA DesA DesA DesA DesA SrcA SrcA SrcA SrcA SrcA SrcA
oct6 oct5 oct4 oct3 oct2 oct1 oct6 oct5 oct4 oct3 oct2 oct1
LSB MSB
oct(0) oct(1) oct(2) oct(3) oct(4) oct(5) oct(6) oct(7)
time
Fig 32. Ethernet packet fields
A packet consists of a preamble, a start-of-frame delimiter and an Ethernet frame.
The Ethernet frame consists of the destination address, the source address, an optional
VLAN field, the length/type field, the payload and the frame check sequence.
Each address consists of 6 bytes where each byte consists of 8 bits. Bits are transferred
starting with the least significant bit.
11.9 Overview
11.9.1 Partitioning
The Ethernet block and associated device driver software offer the functionality of the
Media Access Control (MAC) sub layer of the data link layer in the OSI reference model
(see IEEE std 802.3). The MAC sub layer offers the service of transmitting and receiving
frames to the next higher protocol level, the MAC client layer, typically the Logical Link
Control sub layer. The device driver software implements the interface to the MAC client
layer. It sets up registers in the Ethernet block, maintains descriptor arrays pointing to
frames in memory and receives results back from the Ethernet block through interrupts.
When a frame is transmitted, the software partially sets up the Ethernet frames by

providing pointers to the destination address field, source address field, the length/type
field, the MAC client data field and optionally the CRC in the frame check sequence field.
Preferably concatenation of frame fields should be done by using the scatter/gather
functionality of the Ethernet core to avoid unnecessary copying of data. The hardware
adds the preamble and start frame delimiter fields and can optionally add the CRC, if
requested by software. When a packet is received the hardware strips the preamble and
start frame delimiter and passes the rest of the packet - the Ethernet frame - to the device
driver, including destination address, source address, length/type field, MAC client data
and frame check sequence (FCS).
Apart from the MAC, the Ethernet block contains receive and transmit DMA managers that
control receive and transmit data streams between the MAC and the AHB interface.
Frames are passed via descriptor arrays located in host memory, so that the hardware
can process many frames without software/CPU support. Frames can consist of multiple
fragments that are accessed with scatter/gather DMA. The DMA managers optimize
memory bandwidth using prefetching and buffering.
A receive filter block is used to identify received frames that are not addressed to this
Ethernet station, so that they can be discarded. The Rx filters include a perfect address
filter and a hash filter.
Wake-on-LAN power management support makes it possible to wake the system up from
a power-down state -a state in which some of the clocks are switched off -when wake-up
frames are received over the LAN. Wake-up frames are recognized by the receive filtering
modules or by a Magic Frame detection technology. System wake-up occurs by triggering
an interrupt.
An interrupt logic block raises and masks interrupts and keeps track of the cause of
interrupts. The interrupt block sends an interrupt request signal to the host system.
Interrupts can be enabled, cleared and set by software.
Support for IEEE 802.3/clause 31 flow control is implemented in the flow control block.
Receive flow control frames are automatically handled by the MAC. Transmit flow control
frames can be initiated by software. In half duplex mode, the flow control module will
generate back pressure by sending out continuous preamble only, interrupted by pauses
to prevent the jabber limit from being exceeded.
The Ethernet block has a standard Reduced Media Independent Interface (RMII) to
connect to an external Ethernet PHY chip. Registers in the PHY chip are accessed via the
AHB interface through the serial management connection of the MII bus (MIIM), typically
operating at 2.5 MHz.
11.9.2 Example PHY Devices

Some examples of compatible PHY devices are shown in Table 156.
Table 156. Example PHY Devices

Manufacturer Part Number(s)
Broadcom BCM5221
ICS ICS1893
Intel LXT971A
LSI Logic L80223, L80225, L80227

Table 156. Example PHY Devices

Manufacturer Part Number(s)
Micrel KS8721
National DP83847, DP83846, DP83843
SMSC LAN83C185

Table 157 shows the signals used for the Reduced Media Independent Interface (RMII) to
the external PHY.
Remark: The Ethernet interface must be enabled through the PCONP register and the
reference clock (ENET_REF_CLK signal) must be selected in the PINSEL register (see
Section 5) prior to the Ethernet configuration. If the reference clock is not connected to the
MAC, the CPU can become locked and no further functionality will be possible. This will
cause JTAG to lose communication with the target if debug mode is being used. For
details, see Section 11.18.2.
Table 157. Ethernet RMII pin descriptions

Pin Name Type Pin Description
ENET_TX_EN Output Transmit data enable
ENET_TXD[1:0] Output Transmit data, 2 bits
ENET_RXD[1:0] Input Receive data, 2 bits.
ENET_RX_ER Input Receive error.
ENET_CRS Input Carrier sense/data valid.
ENET_REF_CLK Input Reference clock
Table 158 shows the signals used for Media Independent Interface Management (MIIM) of
the external PHY.
Table 158. Ethernet MIIM pin descriptions

Pin Name Type Pin Description
ENET_MDC Output MIIM clock.
ENET_MDIO Input/Output MI data input and output
Remark: The Ethernet interface must be enabled through the PCONP register and the
Ethernet pins must be connected to port pins using the PINSEL registers (see Table 56
and Section 9.5). Enabling the Ethernet block without connecting the Ethernet signals to
external pins will lock the Ethernet interface and, in Debug mode, cause JTAG to lose
communication with the target.
11.11 Registers and software interface

The software interface of the Ethernet block consists of a register view and the format
definitions for the transmit and receive descriptors. These two aspects are addressed in
the next two subsections.

11.11.1 Register map

Table 159 lists the registers, register addresses and other basic information. The total
AHB address space required is 4 kilobytes.
After a hard reset or a soft reset via the RegReset bit of the Command register all bits in
all registers are reset to 0 unless stated otherwise in the following register descriptions.
Some registers will have unused bits which will return a 0 on a read via the AHB interface.
Writing to unused register bits of an otherwise writable register will not have side effects.
The register map consists of registers in the Ethernet MAC and registers around the core
for controlling DMA transfers, flow control and filtering.
Reading from reserved addresses or reserved bits leads to unpredictable data. Writing to
reserved addresses or reserved bits has no effect.
Reading of write-only registers will return a read error on the AHB interface. Writing of
read-only registers will return a write error on the AHB interface.
Table 159. Register definitions

Symbol Address R/W Description
MAC registers
MAC1 0xFFE0 0000 R/W MAC configuration register 1.
MAC2 0xFFE0 0004 R/W MAC configuration register 2.
IPGT 0xFFE0 0008 R/W Back-to-Back Inter-Packet-Gap register.
IPGR 0xFFE0 000C R/W Non Back-to-Back Inter-Packet-Gap register.
CLRT 0xFFE0 0010 R/W Collision window / Retry register.
MAXF 0xFFE0 0014 R/W Maximum Frame register.
SUPP 0xFFE0 0018 R/W PHY Support register.
TEST 0xFFE0 001C R/W Test register.
MCFG 0xFFE0 0020 R/W MII Mgmt Configuration register.
MCMD 0xFFE0 0024 R/W MII Mgmt Command register.
MADR 0xFFE0 0028 R/W MII Mgmt Address register.
MWTD 0xFFE0 002C WO MII Mgmt Write Data register.
MRDD 0xFFE0 0030 RO MII Mgmt Read Data register.
MIND 0xFFE0 0034 RO MII Mgmt Indicators register.
- 0xFFE0 0038 to - Reserved, user software should not write ones to
0xFFE0 003F reserved bits. The value read from a reserved bit
is not defined.
SA0 0xFFE0 0040 R/W Station Address 0 register.
- 0xFFE0 004C to - Reserved, user software should not write ones to
0xFFE0 00FC reserved bits. The value read from a reserved bit
is not defined.
Control registers
Command 0xFFE0 0100 R/W Command register.
Status 0xFFE0 0104 RO Status register.


RxDescriptor 0xFFE0 0108 R/W Receive descriptor base address register.
RxStatus 0xFFE0 010C R/W Receive status base address register.
RxDescriptorNumber 0xFFE0 0110 R/W Receive number of descriptors register.
RxProduceIndex 0xFFE0 0114 RO Receive produce index register.
RxConsumeIndex 0xFFE0 0118 R/W Receive consume index register.
TxDescriptor 0xFFE0 011C R/W Transmit descriptor base address register.
TxStatus 0xFFE0 0120 R/W Transmit status base address register.
TxDescriptorNumber 0xFFE0 0124 R/W Transmit number of descriptors register.
TxProduceIndex 0xFFE0 0128 R/W Transmit produce index register.
TxConsumeIndex 0xFFE0 012C RO Transmit consume index register.
0xFFE0 0154 reserved bits. The value read from a reserved bit
is not defined.
TSV0 0xFFE0 0158 RO Transmit status vector 0 register.
TSV1 0xFFE0 015C RO Transmit status vector 1 register.
RSV 0xFFE0 0160 RO Receive status vector register.
0xFFE0 016C reserved bits. The value read from a reserved bit
is not defined.
FlowControlCounter 0xFFE0 0170 R/W Flow control counter register.
FlowControlStatus 0xFFE0 0174 RO Flow control status register.
0xFFE0 01FC reserved bits. The value read from a reserved bit
is not defined.
Rx filter registers
RxFliterCtrl 0xFFE0 0200 Receive filter control register.
RxFilterWoLStatus 0xFFE0 0204 Receive filter WoL status register.
RxFilterWoLClear 0xFFE0 0208 Receive filter WoL clear register.
- 0xFFE0 020C - Reserved, user software should not write ones to
reserved bits. The value read from a reserved bit
is not defined.
HashFilterL 0xFFE0 0210 Hash filter table LSBs register.
HashFilterH 0xFFE0 0214 Hash filter table MSBs register.
0xFFE0 0FDC reserved bits. The value read from a reserved bit
is not defined.
Module control registers
IntStatus 0xFFE0 0FE0 RO Interrupt status register.
IntEnable 0xFFE0 0FE4 R/W Interrupt enable register.
IntClear 0xFFE0 0FE8 WO Interrupt clear register.
IntSet 0xFFE0 0FEC WO Interrupt set register.


- 0xFFE0 0FF0 - Reserved, user software should not write ones to
is not defined.
PowerDown 0xFFE0 0FF4 R/W Power-down register.
- 0xFFE0 0FF8 - Reserved, user software should not write ones to
is not defined.
The third column in the table lists the accessibility of the register: read-only, write-only,
read/write.
All AHB register write transactions except for accesses to the interrupt registers are
posted i.e. the AHB transaction will complete before write data is actually committed to the
register. Accesses to the interrupt registers will only be completed by accepting the write
data when the data has been committed to the register.
11.12 Ethernet MAC register definitions

This section defines the bits in the individual registers of the Ethernet block register map.
11.12.1 MAC Configuration Register 1 (MAC1 - 0xFFE0 0000)

The MAC configuration register 1 (MAC1) has an address of 0xFFE0 0000. Its bit
definition is shown in Table 160.
Table 160. MAC Configuration register 1 (MAC1 - address 0xFFE0 0000) bit description
Bit Symbol Function Reset
value
0 RECEIVE ENABLE Set this to allow receive frames to be received. Internally the MAC synchronizes 0
this control bit to the incoming receive stream.
1 PASS ALL RECEIVE When enabled (set to ’1’), the MAC will pass all frames regardless of type (normal 0
FRAMES vs. Control). When disabled, the MAC does not pass valid Control frames.
2 RX FLOW CONTROL When enabled (set to ’1’), the MAC acts upon received PAUSE Flow Control 0
frames. When disabled, received PAUSE Flow Control frames are ignored.
3 TX FLOW CONTROL When enabled (set to ’1’), PAUSE Flow Control frames are allowed to be 0
transmitted. When disabled, Flow Control frames are blocked.
4 LOOPBACK Setting this bit will cause the MAC Transmit interface to be looped back to the MAC 0
Receive interface. Clearing this bit results in normal operation.
7:5 - Unused 0x0
8 RESET TX Setting this bit will put the Transmit Function logic in reset. 0
9 RESET MCS / TX Setting this bit resets the MAC Control Sublayer / Transmit logic. The MCS logic 0
implements flow control.
10 RESET RX Setting this bit will put the Ethernet receive logic in reset. 0
11 RESET MCS / RX Setting this bit resets the MAC Control Sublayer / Receive logic. The MCS logic 0x0
implements flow control.
13:12 - Reserved. User software should not write ones to reserved bits. The value read 0x0

value
14 SIMULATION RESET Setting this bit will cause a reset to the random number generator within the 0
Transmit Function.
15 SOFT RESET Setting this bit will put all modules within the MAC in reset except the Host 1
Interface.
11.12.2 MAC Configuration Register 2 (MAC2 - 0xFFE0 0004)

The MAC configuration register 2 (MAC2) has an address of 0xFFE0 0004. Its bit
value
0 FULL-DUPLEX When enabled (set to ’1’), the MAC operates in Full-Duplex mode. When disabled, 0
the MAC operates in Half-Duplex mode.
1 FRAME LENGTH When enabled (set to ’1’), both transmit and receive frame lengths are compared to 0
CHECKING the Length/Type field. If the Length/Type field represents a length then the check is
performed. Mismatches are reported in the StatusInfo word for each received frame.
2 HUGE FRAME When enabled (set to ’1’), frames of any length are transmitted and received. 0
ENABLE
3 DELAYED CRC This bit determines the number of bytes, if any, of proprietary header information 0
that exist on the front of IEEE 802.3 frames. When 1, four bytes of header (ignored
by the CRC function) are added. When 0, there is no proprietary header.
4 CRC ENABLE Set this bit to append a CRC to every frame whether padding was required or not. 0
Must be set if PAD/CRC ENABLE is set. Clear this bit if frames presented to the
MAC contain a CRC.
5 PAD / CRC ENABLE Set this bit to have the MAC pad all short frames. Clear this bit if frames presented 0
to the MAC have a valid length. This bit is used in conjunction with AUTO PAD
ENABLE and VLAN PAD ENABLE. See Table 162 - Pad Operation for details on the
pad function.
6 VLAN PAD ENABLE Set this bit to cause the MAC to pad all short frames to 64 bytes and append a valid 0
CRC. Consult Table 162 - Pad Operation for more information on the various
padding features.
Note: This bit is ignored if PAD / CRC ENABLE is cleared.
7 AUTO DETECT PAD Set this bit to cause the MAC to automatically detect the type of frame, either tagged 0
ENABLE or un-tagged, by comparing the two octets following the source address with
0x8100 (VLAN Protocol ID) and pad accordingly. Table 162 - Pad Operation
provides a description of the pad function based on the configuration of this register.
Note: This bit is ignored if PAD / CRC ENABLE is cleared.
8 PURE PREAMBLE When enabled (set to ’1’), the MAC will verify the content of the preamble to ensure 0
ENFORCEMENT it contains 0x55 and is error-free. A packet with an incorrect preamble is discarded.
When disabled, no preamble checking is performed.
9 LONG PREAMBLE When enabled (set to ’1’), the MAC only allows receive packets which contain 0
ENFORCEMENT preamble fields less than 12 bytes in length. When disabled, the MAC allows any
length preamble as per the Standard.

value
12 NO BACKOFF When enabled (set to ’1’), the MAC will immediately retransmit following a collision 0
rather than using the Binary Exponential Backoff algorithm as specified in the
Standard.
13 BACK PRESSURE / When enabled (set to ’1’), after the MAC incidentally causes a collision during back 0
NO BACKOFF pressure, it will immediately retransmit without backoff, reducing the chance of
further collisions and ensuring transmit packets get sent.
14 EXCESS DEFER When enabled (set to ’1’) the MAC will defer to carrier indefinitely as per the 0
Standard. When disabled, the MAC will abort when the excessive deferral limit is
reached.
Table 162. Pad operation

Type Auto detect VLAN pad Pad/CRC Action
pad enable enable enable
MAC2 [7] MAC2 [6] MAC2 [5]
Any x x 0 No pad or CRC check
Any 0 0 1 Pad to 60 bytes, append CRC
Any x 1 1 Pad to 64 bytes, append CRC
Any 1 0 1 If untagged, pad to 60 bytes and append CRC. If VLAN tagged: pad to
64 bytes and append CRC.
11.12.3 Back-to-Back Inter-Packet-Gap Register (IPGT - 0xFFE0 0008)

The Back-to-Back Inter-Packet-Gap register (IPGT) has an address of 0xFFE0 0008. Its
bit definition is shown in Table 163.
Table 163. Back-to-back Inter-packet-gap register (IPGT - address 0xFFE0 0008) bit description
value
6:0 BACK-TO-BACK This is a programmable field representing the nibble time offset of the minimum 0x0
INTER-PACKET-GAP possible period between the end of any transmitted packet to the beginning of the
next. In Full-Duplex mode, the register value should be the desired period in
nibble times minus 3. In Half-Duplex mode, the register value should be the
desired period in nibble times minus 6. In Full-Duplex the recommended setting is
0x15 (21d), which represents the minimum IPG of 960 ns (in 100 Mbps mode) or
9.6 µs (in 10 Mbps mode). In Half-Duplex the recommended setting is 0x12 (18d),
which also represents the minimum IPG of 960 ns (in 100 Mbps mode) or 9.6 µs
(in 10 Mbps mode).
11.12.4 Non Back-to-Back Inter-Packet-Gap Register (IPGR - 0xFFE0 000C)

The Non Back-to-Back Inter-Packet-Gap register (IPGR) has an address of
0xFFE0 000C. Its bit definition is shown in Table 164.

Table 164. Non Back-to-back Inter-packet-gap register (IPGR - address 0xFFE0 000C) bit description
value
6:0 NON-BACK-TO-BACK This is a programmable field representing the Non-Back-to-Back 0x0
INTER-PACKET-GAP PART2 Inter-Packet-Gap. The recommended value is 0x12 (18d), which
represents the minimum IPG of 960 ns (in 100 Mbps mode) or 9.6 µs (in
10 Mbps mode).
7 - Reserved. User software should not write ones to reserved bits. The value 0x0
14:8 NON-BACK-TO-BACK This is a programmable field representing the optional carrierSense 0x0
INTER-PACKET-GAP PART1 window referenced in IEEE 802.3/4.2.3.2.1 'Carrier Deference'. If carrier is
detected during the timing of IPGR1, the MAC defers to carrier. If,
however, carrier becomes active after IPGR1, the MAC continues timing
IPGR2 and transmits, knowingly causing a collision, thus ensuring fair
access to medium. Its range of values is 0x0 to IPGR2. The recommended
value is 0xC (12d)
31:15 - Reserved. User software should not write ones to reserved bits. The value 0x0
11.12.5 Collision Window / Retry Register (CLRT - 0xFFE0 0010)

The Collision window / Retry register (CLRT) has an address of 0xFFE0 0010. Its bit
Table 165. Collision Window / Retry register (CLRT - address 0xFFE0 0010) bit description
value
3:0 RETRANSMISSION This is a programmable field specifying the number of retransmission attempts 0xF
MAXIMUM following a collision before aborting the packet due to excessive collisions. The
Standard specifies the attemptLimit to be 0xF (15d). See IEEE 802.3/4.2.3.2.5.
7:4 - Reserved. User software should not write ones to reserved bits. The value read from 0x0
13:8 COLLISION This is a programmable field representing the slot time or collision window during 0x37
WINDOW which collisions occur in properly configured networks. The default value of 0x37
(55d) represents a 56 byte window following the preamble and SFD.
31:14 - Reserved, user software should not write ones to reserved bits. The value read from NA
11.12.6 Maximum Frame Register (MAXF - 0xFFE0 0014)

The Maximum Frame register (MAXF) has an address of 0xFFE0 0014. Its bit definition is
shown in Table 166.
Table 166. Maximum Frame register (MAXF - address 0xFFE0 0014) bit description
value
15:0 MAXIMUM FRAME This field resets to the value 0x0600, which represents a maximum receive frame of 0x0600
LENGTH 1536 octets. An untagged maximum size Ethernet frame is 1518 octets. A tagged
frame adds four octets for a total of 1522 octets. If a shorter maximum length
restriction is desired, program this 16 bit field.
31:16 - Unused 0x0

11.12.7 PHY Support Register (SUPP - 0xFFE0 0018)

The PHY Support register (SUPP) has an address of 0xFFE0 0018. The SUPP register
provides additional control over the RMII interface. The bit definition of this register is
shown in Table 167.
Table 167. PHY Support register (SUPP - address 0xFFE0 0018) bit description
value
7:0 - Unused 0x0
8 SPEED This bit configures the Reduced MII logic for the current operating speed. When set, 0
100 Mbps mode is selected. When cleared, 10 Mbps mode is selected.
31:9 - Unused 0x0
Unused bits in the PHY support register should be left as zeroes.
11.12.8 Test Register (TEST - 0xFFE0 001C)

The Test register (TEST) has an address of 0xFFE0 001C. The bit definition of this
register is shown in Table 168. These bits are used for testing purposes only.
Table 168. Test register (TEST - address 0xFFE0 ) bit description

value
0 SHORTCUT PAUSE This bit reduces the effective PAUSE quanta from 64 byte-times to 1 byte-time. 0
QUANTA
1 TEST PAUSE This bit causes the MAC Control sublayer to inhibit transmissions, just as if a 0
PAUSE Receive Control frame with a nonzero pause time parameter was received.
2 TEST Setting this bit will cause the MAC to assert backpressure on the link. Backpressure 0
BACKPRESSURE causes preamble to be transmitted, raising carrier sense. A transmit packet from the
system will be sent during backpressure.
31:3 - Unused 0x0
11.12.9 MII Mgmt Configuration Register (MCFG - 0xFFE0 0020)

The MII Mgmt Configuration register (MCFG) has an address of 0xFFE0 0020. The bit
definition of this register is shown in Table 169.
Table 169. MII Mgmt Configuration register (MCFG - address 0xFFE0 0020) bit description
value
0 SCAN INCREMENT Set this bit to cause the MII Management hardware to perform read cycles across a 0
range of PHYs. When set, the MII Management hardware will perform read cycles
from address 1 through the value set in PHY ADDRESS[4:0]. Clear this bit to allow
continuous reads of the same PHY.
1 SUPPRESS Set this bit to cause the MII Management hardware to perform read/write cycles 0
PREAMBLE without the 32 bit preamble field. Clear this bit to cause normal cycles to be
performed. Some PHYs support suppressed preamble.
4:2 CLOCK SELECT This field is used by the clock divide logic in creating the MII Management Clock 0
(MDC) which IEEE 802.3u defines to be no faster than 2.5 MHz. Some PHYs
support clock rates up to 12.5 MHz, however. Refer to Table 170 below for the
definition of values for this field.

Table 169. MII Mgmt Configuration register (MCFG - address 0xFFE0 0020) bit description
value
14:5 - Unused 0x0
15 RESET MII MGMT This bit resets the MII Management hardware. 0
31:16 - Unused 0x0
Table 170. Clock select encoding

Clock Select Bit 4 Bit 3 Bit 2
Host Clock divided by 4 0 0 x
Host Clock divided by 6 0 1 0
11.12.10 MII Mgmt Command Register (MCMD - 0xFFE0 0024)

The MII Mgmt Command register (MCMD) has an address of 0xFFE0 0024. The bit
Table 171. MII Mgmt Command register (MCMD - address 0xFFE0 0024) bit description
value
0 READ This bit causes the MII Management hardware to perform a single Read cycle. The Read data is 0
returned in Register MRDD (MII Mgmt Read Data).
1 SCAN This bit causes the MII Management hardware to perform Read cycles continuously. This is 0
useful for monitoring Link Fail for example.
31:2 - Unused 0x0
11.12.11 MII Mgmt Address Register (MADR - 0xFFE0 0028)

The MII Mgmt Address register (MADR) has an address of 0xFFE0 0028. The bit
Table 172. MII Mgmt Address register (MADR - address 0xFFE0 0028) bit description
value
4:0 REGISTER This field represents the 5 bit Register Address field of Mgmt 0x0
ADDRESS cycles. Up to 32 registers can be accessed.
7:5 - Unused 0x0
12:8 PHY ADDRESS This field represents the 5 bit PHY Address field of Mgmt 0x0
cycles. Up to 31 PHYs can be addressed (0 is reserved).
31:13 - Unused 0x0

11.12.12 MII Mgmt Write Data Register (MWTD - 0xFFE0 002C)

The MII Mgmt Write Data register (MWTD) is a Write Only register with an address of
0xFFE0 002C. The bit definition of this register is shown in Table 173.
Table 173. MII Mgmt Write Data register (MWTD - address 0xFFE0 002C) bit description
value
15:0 WRITE When written, an MII Mgmt write cycle is performed using the 16 bit 0x0
DATA data and the pre-configured PHY and Register addresses from the
MII Mgmt Address register (MADR).
31:16 - Unused 0x0
11.12.13 MII Mgmt Read Data Register (MRDD - 0xFFE0 0030)

The MII Mgmt Read Data register (MRDD) is a Read Only register with an address of
0xFFE0 0030. The bit definition of this register is shown in Table 174.
Table 174. MII Mgmt Read Data register (MRDD - address 0xFFE0 0030) bit description
value
15:0 READ Following an MII Mgmt Read Cycle, the 16 bit data can be read from 0x0
DATA this location.
31:16 - Unused 0x0
11.12.14 MII Mgmt Indicators Register (MIND - 0xFFE0 0034)

The MII Mgmt Indicators register (MIND) is a Read Only register with an address of
0xFFE0 0034. The bit definition of this register is shown in Table 175.
Table 175. MII Mgmt Indicators register (MIND - address 0xFFE0 0034) bit description
value
0 BUSY When ’1’ is returned - indicates MII Mgmt is currently performing an 0
MII Mgmt Read or Write cycle.
1 SCANNING When ’1’ is returned - indicates a scan operation (continuous MII 0
Mgmt Read cycles) is in progress.
2 NOT VALID When ’1’ is returned - indicates MII Mgmt Read cycle has not 0
completed and the Read Data is not yet valid.
3 MII Link Fail When ’1’ is returned - indicates that an MII Mgmt link fail has 0
occurred.
31:4 - Unused 0x0
Here are two examples to access PHY via the MII Management Controller.
For PHY Write if scan is not used:
1. Write 0 to MCMD
2. Write PHY address and register address to MADR
3. Write data to MWTD
4. Wait for busy bit to be cleared in MIND

For PHY Read if scan is not used:
1. Write 1 to MCMD
2. Write PHY address and register address to MADR
3. Wait for busy bit to be cleared in MIND
4. Write 0 to MCMD
5. Read data from MRDD
11.12.15 Station Address 0 Register (SA0 - 0xFFE0 0040)

The Station Address 0 register (SA0) has an address of 0xFFE0 0040. The bit definition of
this register is shown in Table 176.
Table 176. Station Address register (SA0 - address 0xFFE0 0040) bit description
value
7:0 STATION ADDRESS, This field holds the second octet of the station address. 0x0
2nd octet
15:8 STATION ADDRESS, This field holds the first octet of the station address. 0x0
1st octet
31:16 - Unused 0x0
The station address is used for perfect address filtering and for sending pause control
frames. For the ordering of the octets in the packet please refer to Figure 32.

value
7:0 STATION ADDRESS, This field holds the fourth octet of the station address. 0x0
4th octet
15:8 STATION ADDRESS, This field holds the third octet of the station address. 0x0
3rd octet
31:16 - Unused 0x0


value
7:0 STATION ADDRESS, This field holds the sixth octet of the station address. 0x0
6th octet
15:8 STATION ADDRESS, This field holds the fifth octet of the station address. 0x0
5th octet
31:16 - Unused 0x0
11.13 Control register definitions
11.13.1 Command Register (Command - 0xFFE0 0100)

The Command register (Command) register has an address of 0xFFE0 0100. Its bit
Table 179. Command register (Command - address 0xFFE0 0100) bit description
value
0 RxEnable Enable receive. 0
1 TxEnable Enable transmit. 0
2 - Unused 0x0
3 RegReset When a ’1’ is written, all datapaths and the host registers are 0
reset. The MAC needs to be reset separately.
4 TxReset When a ’1’ is written, the transmit datapath is reset. 0
5 RxReset When a ’1’ is written, the receive datapath is reset. 0
6 PassRuntFrame When set to ’1’, passes runt frames smaller than 64 bytes to 0
memory unless they have a CRC error. If ’0’ runt frames are
filtered out.
7 PassRxFilter When set to ’1’, disables receive filtering i.e. all frames 0
received are written to memory.
8 TxFlowControl Enable IEEE 802.3 / clause 31 flow control sending pause 0
frames in full duplex and continuous preamble in half duplex.
9 RMII When set to ’1’, RMII mode is selected; if ’0’, MII mode is 0
selected (see Section 11.18.2).
10 FullDuplex When set to ’1’, indicates full duplex operation. 0
31:11 - Unused 0x0
All bits can be written and read. The Tx/RxReset bits are write only, reading will return a 0.
11.13.2 Status Register (Status - 0xFFE0 0104)

The Status register (Status) is a Read Only register with an address of 0xFFE0 0104. Its

Table 180. Status register (Status - address 0xFFE0 0104) bit description
value
0 RxStatus If 1, the receive channel is active. If 0, the receive channel is inactive. 0
1 TxStatus If 1, the transmit channel is active. If 0, the transmit channel is inactive. 0
31:2 - Unused 0x0
The values represent the status of the two channels/data paths. When the status is 1, the
channel is active, meaning:
• It is enabled and the Rx/TxEnable bit is set in the Command register or it just got
disabled while still transmitting or receiving a frame.
• Also, for the transmit channel, the transmit queue is not empty
i.e. ProduceIndex != ConsumeIndex.
• Also, for the receive channel, the receive queue is not full
i.e. ProduceIndex != ConsumeIndex - 1.
The status transitions from active to inactive if the channel is disabled by a software reset
of the Rx/TxEnable bit in the Command register and the channel has committed the status
and data of the current frame to memory. The status also transitions to inactive if the
transmit queue is empty or if the receive queue is full and status and data have been
committed to memory.
11.13.3 Receive Descriptor Base Address Register (RxDescriptor -

0xFFE0 0108)
The Receive Descriptor base address register (RxDescriptor) has an address of
0xFFE0 0108. Its bit definition is shown in Table 181.
Table 181. Receive Descriptor Base Address register (RxDescriptor - address 0xFFE0 0108)
bit description
value
1:0 - Fixed to ’00’ -
31:2 RxDescriptor MSBs of receive descriptor base address. 0x0
The receive descriptor base address is a byte address aligned to a word boundary i.e.
LSB 1:0 are fixed to ’00’. The register contains the lowest address in the array of
descriptors.
11.13.4 Receive Status Base Address Register (RxStatus - 0xFFE0 010C)

The receive descriptor base address is a byte address aligned to a word boundary i.e.
descriptors.
Table 182. receive Status Base Address register (RxStatus - address 0xFFE0 010C) bit
description
value
2:0 - Fixed to ’000’ -
31:3 RxStatus MSBs of receive status base address. 0x0

The receive status base address is a byte address aligned to a double word boundary i.e.
LSB 2:0 are fixed to ’000’.
11.13.5 Receive Number of Descriptors Register (RxDescriptor -

0xFFE0 0110)
The Receive Number of Descriptors register (RxDescriptorNumber) has an address of
Table 183. Receive Number of Descriptors register (RxDescriptor - address 0xFFE0 0110) bit
description
value
15:0 RxDescriptorNumber Number of descriptors in the descriptor array for which 0x0
RxDescriptor is the base address. The number of
descriptors is minus one encoded.
31:16 - Unused 0x0
The receive number of descriptors register defines the number of descriptors in the
descriptor array for which RxDescriptor is the base address. The number of descriptors
should match the number of statuses. The register uses minus one encoding i.e. if the
array has 8 elements, the value in the register should be 7.
11.13.6 Receive Produce Index Register (RxProduceIndex - 0xFFE0 0114)

The Receive Produce Index register (RxProduceIndex) is a Read Only register with an
address of 0xFFE0 0114. Its bit definition is shown in Table 184.
Table 184. Receive Produce Index register (RxProduceIndex - address 0xFFE0 0114) bit
description
value
15:0 RxProduceIndex Index of the descriptor that is going to be filled next by the 0x0
receive datapath.
31:16 - Unused 0x0
The receive produce index register defines the descriptor that is going to be filled next by
the hardware receive process. After a frame has been received, hardware increments the
index. The value is wrapped to 0 once the value of RxDescriptorNumber has been
reached. If the RxProduceIndex equals RxConsumeIndex - 1, the array is full and any
further frames being received will cause a buffer overrun error.
11.13.7 Receive Consume Index Register (RxConsumeIndex - 0xFFE0 0118)

The Receive consume index register (RxConsumeIndex) has an address of

Table 185. Receive Consume Index register (RXConsumeIndex - address 0xFFE0 0118) bit
description
value
15:0 RxConsumeIndex Index of the descriptor that is going to be processed next by
the receive
31:16 - Unused 0x0
The receive consume register defines the descriptor that is going to be processed next by
the software receive driver. The receive array is empty as long as RxProduceIndex equals
RxConsumeIndex. As soon as the array is not empty, software can process the frame
pointed to by RxConsumeIndex. After a frame has been processed by software, software
should increment the RxConsumeIndex. The value must be wrapped to 0 once the value
of RxDescriptorNumber has been reached. If the RxProduceIndex equals
RxConsumeIndex - 1, the array is full and any further frames being received will cause a
buffer overrun error.
11.13.8 Transmit Descriptor Base Address Register (TxDescriptor -

0xFFE0 011C)
The Transmit Descriptor base address register (TxDescriptor) has an address of
0xFFE0 011C. Its bit definition is shown in Table 186.
Table 186. Transmit Descriptor Base Address register (TxDescriptor - address 0xFFE0 011C)
bit description
value
1:0 - Fixed to ’00’ -
31:2 TxDescriptor MSBs of transmit descriptor base address. 0x0
The transmit descriptor base address is a byte address aligned to a word boundary i.e.
descriptors.
11.13.9 Transmit Status Base Address Register (TxStatus - 0xFFE0 0120)

The Transmit Status base address register (TxStatus) has an address of 0xFFE0 0120. Its
Table 187. Transmit Status Base Address register (TxStatus - address 0xFFE0 0120) bit
description
value
1:0 - Fixed to ’00’ -
31:2 TxStatus MSBs of transmit status base address. 0x0
The transmit status base address is a byte address aligned to a word boundary i.e. LSB
1:0 are fixed to ’00’. The register contains the lowest address in the array of statuses.

11.13.10 Transmit Number of Descriptors Register (TxDescriptorNumber -

0xFFE0 0124)
The Transmit Number of Descriptors register (TxDescriptorNumber) has an address of
Table 188. Transmit Number of Descriptors register (TxDescriptorNumber - address

value
15:0 TxDescriptorNumber Number of descriptors in the descriptor array for which
TxDescriptor is the base address. The register is minus
one encoded.
31:16 - Unused 0x0
The transmit number of descriptors register defines the number of descriptors in the
descriptor array for which TxDescriptor is the base address. The number of descriptors
should match the number of statuses. The register uses minus one encoding i.e. if the
array has 8 elements, the value in the register should be 7.
11.13.11 Transmit Produce Index Register (TxProduceIndex - 0xFFE0 0128)

The Transmit Produce Index register (TxProduceIndex) has an address of 0xFFE0 0128.
Its bit definition is shown in Table 189.
Table 189. Transmit Produce Index register (TxProduceIndex - address 0xFFE0 0128) bit
description
value
15:0 TxProduceIndex Index of the descriptor that is going to be filled next by the 0x0
transmit software driver.
31:16 - Unused 0x0
The transmit produce index register defines the descriptor that is going to be filled next by
the software transmit driver. The transmit descriptor array is empty as long as
TxProduceIndex equals TxConsumeIndex. If the transmit hardware is enabled, it will start
transmitting frames as soon as the descriptor array is not empty. After a frame has been
processed by software, it should increment the TxProduceIndex. The value must be
wrapped to 0 once the value of TxDescriptorNumber has been reached. If the
TxProduceIndex equals TxConsumeIndex - 1 the descriptor array is full and software
should stop producing new descriptors until hardware has transmitted some frames and
updated the TxConsumeIndex.
11.13.12 Transmit Consume Index Register (TxConsumeIndex - 0xFFE0 012C)

The Transmit Consume Index register (TxConsumeIndex) is a Read Only register with an
address of 0xFFE0 012C. Its bit definition is shown in Table 190.

Table 190. Transmit Consume Index register (TxConsumeIndex - address 0xFFE0 012C) bit
description
value
15:0 TxConsumeIndex Index of the descriptor that is going to be transmitted next by 0x0
the transmit datapath.
31:16 - Unused 0x0
The transmit consume index register defines the descriptor that is going to be transmitted
next by the hardware transmit process. After a frame has been transmitted hardware
increments the index, wrapping the value to 0 once the value of TxDescriptorNumber has
been reached. If the TxConsumeIndex equals TxProduceIndex the descriptor array is
empty and the transmit channel will stop transmitting until software produces new
descriptors.
11.13.13 Transmit Status Vector 0 Register (TSV0 - 0xFFE0 0158)

The Transmit Status Vector 0 register (TSV0) is a Read Only register with an address of
0xFFE0 0158. The transmit status vector registers store the most recent transmit status
returned by the MAC. Since the status vector consists of more than 4 bytes, status is
distributed over two registers TSV0 and TSV1. These registers are provided for debug
purposes, because the communication between driver software and the Ethernet block
takes place primarily through the frame descriptors. The status register contents are valid
as long as the internal status of the MAC is valid and should typically only be read when
the transmit and receive processes are halted.
Table 191 lists the bit definitions of the TSV0 register.
Table 191. Transmit Status Vector 0 register (TSV0 - address 0xFFE0 0158) bit description
value
0 CRC error The attached CRC in the packet did not match the 0
internally generated CRC.
1 Length check error Indicates the frame length field does not match the actual 0
number of data items and is not a type field.
2 Length out of range[1] Indicates that frame type/length field was larger than 0
1500 bytes.
3 Done Transmission of packet was completed. 0
4 Multicast Packet’s destination was a multicast address. 0
5 Broadcast Packet’s destination was a broadcast address. 0
6 Packet Defer Packet was deferred for at least one attempt, but less than 0
an excessive defer.
7 Excessive Defer Packet was deferred in excess of 6071 nibble times in 0
100 Mbps or 24287 bit times in 10 Mbps mode.
8 Excessive Collision Packet was aborted due to exceeding of maximum allowed 0
number of collisions.
9 Late Collision Collision occurred beyond collision window, 512 bit times. 0
10 Giant Byte count in frame was greater than can be represented 0
in the transmit byte count field in TSV1.
11 Underrun Host side caused buffer underrun. 0

Table 191. Transmit Status Vector 0 register (TSV0 - address 0xFFE0 0158) bit description
value
27:12 Total bytes The total number of bytes transferred including collided 0x0
attempts.
28 Control frame The frame was a control frame. 0
29 Pause The frame was a control frame with a valid PAUSE 0
opcode.
30 Backpressure Carrier-sense method backpressure was previously 0
applied.
31 VLAN Frame’s length/type field contained 0x8100 which is the 0
VLAN protocol identifier.
[1] The EMAC doesn't distinguish the frame type and frame length, so, e.g. when the IP(0x8000) or
ARP(0x0806) packets are received, it compares the frame type with the max length and gives the "Length
out of range" error. In fact, this bit is not an error indication, but simply a statement by the chip regarding the
status of the received frame.
11.13.14 Transmit Status Vector 1 Register (TSV1 - 0xFFE0 015C)

The Transmit Status Vector 1 register (TSV1) is a Read Only register with an address of
0xFFE0 015C. The transmit status vector registers store the most recent transmit status
returned by the MAC. Since the status vector consists of more than 4 bytes, status is
distributed over two registers TSV0 and TSV1. These registers are provided for debug
takes place primarily through the frame descriptors. The status register contents are valid
as long as the internal status of the MAC is valid and should typically only be read when
the transmit and receive processes are halted.Table 192 lists the bit definitions of the
TSV1 register.
Table 192. Transmit Status Vector 1 register (TSV1 - address 0xFFE0 015C) bit description
value
15:0 Transmit byte count The total number of bytes in the frame, not counting the 0x0
collided bytes.
19:16 Transmit collision Number of collisions the current packet incurred during 0x0
count transmission attempts. The maximum number of collisions
(16) cannot be represented.
31:20 - Unused 0x0
11.13.15 Receive Status Vector Register (RSV - 0xFFE0 0160)

The Receive status vector register (RSV) is a Read Only register with an address of
0xFFE0 0160. The receive status vector register stores the most recent receive status
returned by the MAC. This register is provided for debug purposes, because the
communication between driver software and the Ethernet block takes place primarily
through the frame descriptors. The status register contents are valid as long as the
internal status of the MAC is valid and should typically only be read when the transmit and
receive processes are halted.
Table 193 lists the bit definitions of the RSV register.

Table 193. Receive Status Vector register (RSV - address 0xFFE0 0160) bit description
value
15:0 Received byte count Indicates length of received frame. 0x0
16 Packet previously Indicates that a packet was dropped. 0
ignored
17 RXDV event Indicates that the last receive event seen was not long 0
previously seen enough to be a valid packet.
18 Carrier event Indicates that at some time since the last receive statistics, 0
previously seen a carrier event was detected.
19 Receive code Indicates that received PHY data does not represent a 0
violation valid receive code.
20 CRC error The attached CRC in the packet did not match the 0
internally generated CRC.
21 Length check error Indicates the frame length field does not match the actual 0
number of data items and is not a type field.
22 Length out of range[1] Indicates that frame type/length field was larger than 0
1518 bytes.
23 Receive OK The packet had valid CRC and no symbol errors. 0
24 Multicast The packet destination was a multicast address. 0
25 Broadcast The packet destination was a broadcast address. 0
26 Dribble Nibble Indicates that after the end of packet another 1-7 bits were 0
received. A single nibble, called dribble nibble, is formed
but not sent out.
27 Control frame The frame was a control frame. 0
28 PAUSE The frame was a control frame with a valid PAUSE 0
opcode.
29 Unsupported Opcode The current frame was recognized as a Control Frame but 0
contains an unknown opcode.
30 VLAN Frame’s length/type field contained 0x8100 which is the 0
VLAN protocol identifier.
31 - Unused 0x0
ARP(0x0806) packets are received, it compares the frame type with the max length and gives the "Length
out of range" error. In fact, this bit is not an error indication, but simply a statement by the chip regarding the
status of the received frame.
11.13.16 Flow Control Counter Register (FlowControlCounter - 0xFFE0 0170)

The Flow Control Counter register (FlowControlCounter) has an address of 0xFFE0 0170.
Table 194 lists the bit definitions of the register.

Table 194. Flow Control Counter register (FlowControlCounter - address 0xFFE0 0170) bit
description
value
15:0 MirrorCounter In full duplex mode the MirrorCounter specifies the number 0x0
of cycles before re-issuing the Pause control frame.
31:16 PauseTimer In full-duplex mode the PauseTimer specifies the value 0x0
that is inserted into the pause timer field of a pause flow
control frame. In half duplex mode the PauseTimer
specifies the number of backpressure cycles.
11.13.17 Flow Control Status Register (FlowControlStatus - 0xFFE0 0174)

The Flow Control Status register (FlowControlStatus) is a Read Only register with an
address of 0xFFE0 8174. Table 195 lists the bit definitions of the register.
Table 195. Flow Control Status register (FlowControlStatus - address 0xFFE0 8174) bit
description
value
15:0 MirrorCounterCurrent In full duplex mode this register represents the current 0x0
value of the datapath’s mirror counter which counts up to
the value specified by the MirrorCounter field in the
FlowControlCounter register. In half duplex mode the
register counts until it reaches the value of the PauseTimer
bits in the FlowControlCounter register.
31:16 - Unused 0x0
11.14 Receive filter register definitions
11.14.1 Receive Filter Control Register (RxFilterCtrl - 0xFFE0 0200)

The Receive Filter Control register (RxFilterCtrl) has an address of 0xFFE0 0200.
Table 196 lists the definition of the individual bits in the register.
Table 196. Receive Filter Control register (RxFilterCtrl - address 0xFFE0 0200) bit
description
value
0 AcceptUnicastEn When set to ’1’, all unicast frames are accepted. 0
1 AcceptBroadcastEn When set to ’1’, all broadcast frames are accepted. 0
2 AcceptMulticastEn When set to ’1’, all multicast frames are accepted. 0
3 AcceptUnicastHashEn When set to ’1’, unicast frames that pass the imperfect 0
hash filter are accepted.
4 AcceptMulticastHashEn When set to ’1’, multicast frames that pass the 0
imperfect hash filter are accepted.
5 AcceptPerfectEn When set to ’1’, the frames with a destination address 0
identical to the
station address are accepted.

Table 196. Receive Filter Control register (RxFilterCtrl - address 0xFFE0 0200) bit
description
value
11:6 - Reserved, user software should not write ones to NA
defined.
12 MagicPacketEnWoL When set to ’1’, the result of the magic packet filter will 0
generate a WoL interrupt when there is a match.
13 RxFilterEnWoL When set to ’1’, the result of the perfect address 0
matching filter and the imperfect hash filter will
generate a WoL interrupt when there is a match.
31:14 - Unused 0x0
11.14.2 Receive Filter WoL Status Register (RxFilterWoLStatus -

0xFFE0 0204)
The Receive Filter Wake-up on LAN Status register (RxFilterWoLStatus) is a Read Only
register with an address of 0xFFE0 0204.
Table 197. Receive Filter WoL Status register (RxFilterWoLStatus - address 0xFFE0 0204) bit
description
value
0 AcceptUnicastWoL When the value is ’1’, a unicast frames caused WoL. 0
1 AcceptBroadcastWoL When the value is ’1’, a broadcast frame caused WoL. 0
2 AcceptMulticastWoL When the value is ’1’, a multicast frame caused WoL. 0
3 AcceptUnicastHashWoL When the value is ’1’, a unicast frame that passes the 0
imperfect hash filter caused WoL.
4 AcceptMulticastHashWoL When the value is ’1’, a multicast frame that passes the 0
imperfect hash filter caused WoL.
5 AcceptPerfectWoL When the value is ’1’, the perfect address matching filter 0
caused WoL.
6 - Unused 0x0
7 RxFilterWoL When the value is ’1’, the receive filter caused WoL. 0
8 MagicPacketWoL When the value is ’1’, the magic packet filter caused 0
WoL.
31:9 - Unused 0x0
The bits in this register record the cause for a WoL. Bits in RxFilterWoLStatus can be
cleared by writing the RxFilterWoLClear register.
11.14.3 Receive Filter WoL Clear Register (RxFilterWoLClear - 0xFFE0 0208)

The Receive Filter Wake-up on LAN Clear register (RxFilterWoLClear) is a Write Only
register with an address of 0xFFE0 0208.

Table 198. Receive Filter WoL Clear register (RxFilterWoLClear - address 0xFFE0 0208) bit
description
value
0 AcceptUnicastWoLClr When a ’1’ is written to one of these bits (0 to 5), the 0
1 AcceptBroadcastWoLClr corresponding status bit in the RxFilterWoLStatus 0
register is cleared.
2 AcceptMulticastWoLClr 0
3 AcceptUnicastHashWoLClr 0
4 AcceptMulticastHashWoLClr 0
5 AcceptPerfectWoLClr 0
6 - Unused 0x0
7 RxFilterWoLClr When a ’1’ is written to one of these bits (7 and/or 8), 0
8 MagicPacketWoLClr the corresponding status bit in the RxFilterWoLStatus 0
register is cleared.
31:9 - Unused 0x0
The bits in this register are write-only; writing resets the corresponding bits in the
RxFilterWoLStatus register.
11.14.4 Hash Filter Table LSBs Register (HashFilterL - 0xFFE0 0210)

The Hash Filter table LSBs register (HashFilterL) has an address of 0xFFE0 0210.
Table 199 lists the bit definitions of the register. Details of Hash filter table use can be
found in Section 11.18.10 “Receive filtering” on page 245.
Table 199. Hash Filter Table LSBs register (HashFilterL - address 0xFFE0 0210) bit
description
value
31:0 HashFilterL Bit 31:0 of the imperfect filter hash table for receive 0x0
filtering.
11.14.5 Hash Filter Table MSBs Register (HashFilterH - 0xFFE0 0214)

The Hash Filter table MSBs register (HashFilterH) has an address of 0xFFE0 0214.
Table 200 lists the bit definitions of the register. Details of Hash filter table use can be
found in Section 11.18.10 “Receive filtering” on page 245.
Table 200. Hash Filter MSBs register (HashFilterH - address 0xFFE0 0214) bit description
value
31:0 HashFilterH Bit 63:32 of the imperfect filter hash table for receive 0x0
filtering.

11.15 Module control register definitions
11.15.1 Interrupt Status Register (IntStatus - 0xFFE0 0FE0)

The Interrupt Status register (IntStatus) is a Read Only register with an address of
0xFFE0 0FE0. The interrupt status register bit definition is shown in Table 201. Note that
all bits are flip-flops with an asynchronous set in order to be able to generate interrupts if
there are wake-up events while clocks are disabled.
Table 201. Interrupt Status register (IntStatus - address 0xFFE0 0FE0) bit description
value
0 RxOverrunInt Interrupt set on a fatal overrun error in the receive queue. The 0
fatal interrupt should be resolved by a Rx soft-reset. The bit is not
set when there is a nonfatal overrun error.
1 RxErrorInt Interrupt trigger on receive errors: AlignmentError, RangeError, 0
LengthError, SymbolError, CRCError or NoDescriptor or Overrun.
2 RxFinishedInt Interrupt triggered when all receive descriptors have been 0
processed i.e. on the transition to the situation where
ProduceIndex == ConsumeIndex.
3 RxDoneInt Interrupt triggered when a receive descriptor has been processed 0
while the Interrupt bit in the Control field of the descriptor was set.
4 TxUnderrunInt Interrupt set on a fatal underrun error in the transmit queue. The 0
fatal interrupt should be resolved by a Tx soft-reset. The bit is not
set when there is a nonfatal underrun error.
5 TxErrorInt Interrupt trigger on transmit errors: LateCollision, 0
ExcessiveCollision and ExcessiveDefer, NoDescriptor or
Underrun.
6 TxFinishedInt Interrupt triggered when all transmit descriptors have been 0
processed i.e. on the transition to the situation where
7 TxDoneInt Interrupt triggered when a descriptor has been transmitted while 0
the Interrupt bit in the Control field of the descriptor was set.
11:8 - Unused 0x0
12 SoftInt Interrupt triggered by software writing a 1 to the SoftintSet bit in 0
the IntSet register.
13 WakeupInt Interrupt triggered by a Wakeup event detected by the receive 0
filter.
31:14 - Unused 0x0
The interrupt status register is read-only. Setting can be done via the IntSet register. Reset
can be accomplished via the IntClear register.
11.15.2 Interrupt Enable Register (IntEnable - 0xFFE0 0FE4)

The Interrupt Enable register (IntEnable) has an address of 0xFFE0 0FE4. The interrupt
enable register bit definition is shown in Table 202.

Table 202. Interrupt Enable register (intEnable - address 0xFFE0 0FE4) bit description
value
0 RxOverrunIntEn Enable for interrupt trigger on receive buffer overrun or 0
descriptor underrun situations.
1 RxErrorIntEn Enable for interrupt trigger on receive errors. 0
2 RxFinishedIntEn Enable for interrupt triggered when all receive descriptors have 0
been processed i.e. on the transition to the situation where
3 RxDoneIntEn Enable for interrupt triggered when a receive descriptor has 0
been processed while the Interrupt bit in the Control field of the
descriptor was set.
4 TxUnderrunIntEn Enable for interrupt trigger on transmit buffer or descriptor 0
underrun situations.
5 TxErrorIntEn Enable for interrupt trigger on transmit errors. 0
6 TxFinishedIntEn Enable for interrupt triggered when all transmit descriptors 0
have been processed i.e. on the transition to the situation
where ProduceIndex == ConsumeIndex.
7 TxDoneIntEn Enable for interrupt triggered when a descriptor has been 0
transmitted while the Interrupt bit in the Control field of the
descriptor was set.
11:8 - Unused 0x0
12 SoftIntEn Enable for interrupt triggered by the SoftInt bit in the IntStatus 0
register, caused by software writing a 1 to the SoftIntSet bit in
the IntSet register.
13 WakeupIntEn Enable for interrupt triggered by a Wakeup event detected by 0
the receive filter.
31:14 - Unused 0x0
11.15.3 Interrupt Clear Register (IntClear - 0xFFE0 0FE8)

The Interrupt Clear register (IntClear) is a Write Only register with an address of
0xFFE0 0FE8. The interrupt clear register bit definition is shown in Table 203.
Table 203. Interrupt Clear register (IntClear - address 0xFFE0 0FE8) bit description
value
0 RxOverrunIntClr Writing a ’1’ to one of these bits clears (0 to 7) the 0
1 RxErrorIntClr corresponding status bit in interrupt status register 0
IntStatus.
2 RxFinishedIntClr 0
3 RxDoneIntClr 0
4 TxUnderrunIntClr 0
5 TxErrorIntClr 0
6 TxFinishedIntClr 0
7 TxDoneIntClr 0
11:8 - Unused 0x0

Table 203. Interrupt Clear register (IntClear - address 0xFFE0 0FE8) bit description
value
12 SoftIntClr Writing a ’1’ to one of these bits (12 and/or 13) clears the 0
13 WakeupIntClr corresponding status bit in interrupt status register 0
IntStatus.
31:14 - Unused 0x0
The interrupt clear register is write-only. Writing a 1 to a bit of the IntClear register clears
the corresponding bit in the status register. Writing a 0 will not affect the interrupt status.
11.15.4 Interrupt Set Register (IntSet - 0xFFE0 0FEC)

The Interrupt Set register (IntSet) is a Write Only register with an address of
0xFFE0 0FEC. The interrupt set register bit definition is shown in Table 204.
Table 204. Interrupt Set register (IntSet - address 0xFFE0 0FEC) bit description
value
0 RxOverrunIntSet Writing a ’1’ to one of these bits (0 to 7) sets the 0
1 RxErrorIntSet corresponding status bit in interrupt status register 0
IntStatus.
2 RxFinishedIntSet 0
3 RxDoneIntSet 0
4 TxUnderrunIntSet 0
5 TxErrorIntSet 0
6 TxFinishedIntSet 0
7 TxDoneIntSet 0
11:8 - Unused 0x0
12 SoftIntSet Writing a ’1’ to one of these bits (12 and/or 13) sets the 0
13 WakeupIntSet corresponding status bit in interrupt status register 0
IntStatus.
31:14 - Unused 0x0
The interrupt set register is write-only. Writing a 1 to a bit of the IntSet register sets the
corresponding bit in the status register. Writing a 0 will not affect the interrupt status.
11.15.5 Power Down Register (PowerDown - 0xFFE0 0FF4)

The Power-Down register (PowerDown) is used to block all AHB accesses except
accesses to the PowerDown register. The register has an address of 0xFFE0 0FF4. The
bit definition of the register is listed in Table 205.
Table 205. Power Down register (PowerDown - address 0xFFE0 0FF4) bit description
value
30:0 - Unused 0x0
31 PowerDownMACAHB If true, all AHB accesses will return a read/write error, 0
except accesses to the PowerDown register.
Setting the bit will return an error on all read and write accesses on the MACAHB interface
except for accesses to the PowerDown register.

11.16 Descriptor and status formats

This section defines the descriptor format for the transmit and receive scatter/gather DMA
engines. Each Ethernet frame can consist of one or more fragments. Each fragment
corresponds to a single descriptor. The DMA managers in the Ethernet block scatter (for
receive) and gather (for transmit) multiple fragments for a single Ethernet frame.
11.16.1 Receive descriptors and statuses

Figure 33 depicts the layout of the receive descriptors in memory.
RxDescriptor RxStatus
1 PACKET DATA BUFFER StatusInfo
CONTROL StatusHashCRC
RxDescriptorNumber PACKET DATA BUFFER StatusInfo
Fig 33. Receive descriptor memory layout
Receive descriptors are stored in an array in memory. The base address of the array is
stored in the RxDescriptor register, and should be aligned on a 4 byte address boundary.
The number of descriptors in the array is stored in the RxDescriptorNumber register using
a minus one encoding style e.g. if the array has 8 elements the register value should be 7.
Parallel to the descriptors there is an array of statuses. For each element of the descriptor
array there is an associated status field in the status array. The base address of the status
array is stored in the RxStatus register, and must be aligned on an 8 byte address
boundary. During operation (when the receive data path is enabled) the RxDescriptor,
RxStatus and RxDescriptorNumber registers should not be modified.
Two registers, RxConsumeIndex and RxProduceIndex, define the descriptor locations

that will be used next by hardware and software. Both registers act as counters starting at
0 and wrapping when they reach the value of RxDescriptorNumber. The RxProduceIndex
contains the index of the descriptor that is going to be filled with the next frame being

received. The RxConsumeIndex is programmed by software and is the index of the next
descriptor that the software receive driver is going to process. When RxProduceIndex ==
RxConsumeIndex, the receive buffer is empty. When RxProduceIndex ==
RxConsumeIndex -1 (taking wraparound into account), the receive buffer is full and newly
received data would generate an overflow unless the software driver frees up one or more
descriptors.
Each receive descriptor takes two word locations (8 bytes) in memory. Likewise each
status field takes two words (8 bytes) in memory. Each receive descriptor consists of a
pointer to the data buffer for storing receive data (Packet) and a control word (Control).
The Packet field has a zero address offset, the control field has a 4 byte address offset
with respect to the descriptor address as defined in Table 206.
Table 206. Receive Descriptor Fields

Symbol Address Bytes Description
offset
Packet 0x0 4 Base address of the data buffer for storing receive data.
Control 0x4 4 Control information, see Table 207.
The data buffer pointer (Packet) is a 32 bits byte aligned address value containing the
base address of the data buffer. The definition of the control word bits is listed in
Table 207.
Table 207. Receive Descriptor Control Word

Bit Symbol Description
10:0 Size Size in bytes of the data buffer. This is the size of the buffer reserved by the
device driver for a frame or frame fragment i.e. the byte size of the buffer
pointed to by the Packet field. The size is -1 encoded e.g. if the buffer is 8
bytes the size field should be equal to 7.
30:11 - Unused
31 Interrupt If true generate an RxDone interrupt when the data in this frame or frame
fragment and the associated status information has been committed to
memory.
Table 208 lists the fields in the receive status elements from the status array.
Table 208. Receive Status Fields

offset
StatusInfo 0x0 4 Receive status return flags, see Table 210.
StatusHashCRC 0x4 4 The concatenation of the destination address hash CRC and
the source address hash CRC.
Each receive status consists of two words. The StatusHashCRC word contains a
concatenation of the two 9 bit hash CRCs calculated from the destination and source
addresses contained in the received frame. After detecting the destination and source
addresses, StatusHashCRC is calculated once, then held for every fragment of the same
frame.
The concatenation of the two CRCs is shown in Table 209:

Table 209. Receive Status HashCRC Word

8:0 SAHashCRC Hash CRC calculated from the source address.
15:9 - Unused
24:16 DAHashCRC Hash CRC calculated from the destination address.
31:25 - Unused
The StatusInfo word contains flags returned by the MAC and flags generated by the
receive data path reflecting the status of the reception. Table 210 lists the bit definitions in
the StatusInfo word.
Table 210. Receive status information word

10:0 RxSize The size in bytes of the actual data transferred into one fragment buffer. In
other words, this is the size of the frame or fragment as actually written by
the DMA manager for one descriptor. This may be different from the Size
bits of the Control field in the descriptor that indicate the size of the buffer
allocated by the device driver. Size is -1 encoded e.g. if the buffer has
8 bytes the RxSize value will be 7.
17:11 - Unused
18 ControlFrame Indicates this is a control frame for flow control, either a pause frame or a
frame with an unsupported opcode.
19 VLAN Indicates a VLAN frame.
20 FailFilter Indicates this frame has failed the Rx filter. These frames will not normally
pass to memory. But due to the limitation of the size of the buffer, part of
this frame may already be passed to memory. Once the frame is found to
have failed the Rx filter, the remainder of the frame will be discarded
without being passed to the memory. However, if the PassRxFilter bit in
the Command register is set, the whole frame will be passed to memory.
21 Multicast Set when a multicast frame is received.
22 Broadcast Set when a broadcast frame is received.
23 CRCError The received frame had a CRC error.
24 SymbolError The PHY reports a bit error over the PHY interface during reception.
25 LengthError The frame length field value in the frame specifies a valid length, but does
not match the actual data length.
26 RangeError[1] The received packet exceeds the maximum packet size.
27 AlignmentError An alignment error is flagged when dribble bits are detected and also a
CRC error is detected. This is in accordance with IEEE std. 802.3/clause
4.3.2.
28 Overrun Receive overrun. The adapter can not accept the data stream.
29 NoDescriptor No new Rx descriptor is available and the frame is too long for the buffer
size in the current receive descriptor.
30 LastFlag When set to 1, indicates this descriptor is for the last fragment of a frame.
If the frame consists of a single fragment, this bit is also set to 1.
31 Error An error occurred during reception of this frame. This is a logical OR of
AlignmentError, RangeError, LengthError, SymbolError, CRCError, and
Overrun.

ARP(0x0806) packets are received, it compares the frame type with the max length and gives the "Range"
error. In fact, this bit is not an error indication, but simply a statement by the chip regarding the status of the
received frame.
For multi-fragment frames, the value of the AlignmentError, RangeError, LengthError,

SymbolError and CRCError bits in all but the last fragment in the frame will be 0; likewise
the value of the FailFilter, Multicast, Broadcast, VLAN and ControlFrame bits is undefined.
The status of the last fragment in the frame will copy the value for these bits from the
MAC. All fragment statuses will have valid LastFrag, RxSize, Error, Overrun and
NoDescriptor bits.
11.16.2 Transmit descriptors and statuses

Figure 34 depicts the layout of the transmit descriptors in memory.
TxDescriptor TxStatus
1 PACKET DATA BUFFER

StatusInfo
CONTROL

StatusInfo
CONTROL

StatusInfo
CONTROL

StatusInfo
CONTROL

StatusInfo
CONTROL
TxDescriptorNumber PACKET DATA BUFFER

StatusInfo
CONTROL
Fig 34. Transmit descriptor memory layout
Transmit descriptors are stored in an array in memory. The lowest address of the transmit
descriptor array is stored in the TxDescriptor register, and must be aligned on a 4 byte
address boundary. The number of descriptors in the array is stored in the
TxDescriptorNumber register using a minus one encoding style i.e. if the array has 8
elements the register value should be 7. Parallel to the descriptors there is an array of
statuses. For each element of the descriptor array there is an associated status field in the
status array. The base address of the status array is stored in the TxStatus register, and
must be aligned on a 4 byte address boundary. During operation (when the transmit data
path is enabled) the TxDescriptor, TxStatus, and TxDescriptorNumber registers should
not be modified.

Two registers, TxConsumeIndex and TxProduceIndex, define the descriptor locations that
will be used next by hardware and software. Both register act as counters starting at 0 and
wrapping when they reach the value of TxDescriptorNumber. The TxProduceIndex
contains the index of the next descriptor that is going to be filled by the software driver.
The TxConsumeIndex contains the index of the next descriptor going to be transmitted by
the hardware. When TxProduceIndex == TxConsumeIndex, the transmit buffer is empty.
When TxProduceIndex == TxConsumeIndex -1 (taking wraparound into account), the
transmit buffer is full and the software driver cannot add new descriptors until the
hardware has transmitted one or more frames to free up descriptors.
Each transmit descriptor takes two word locations (8 bytes) in memory. Likewise each
status field takes one word (4 bytes) in memory. Each transmit descriptor consists of a
pointer to the data buffer containing transmit data (Packet) and a control word (Control).
The Packet field has a zero address offset, whereas the control field has a 4 byte address
offset, see Table 211.
Table 211. Transmit descriptor fields

Symbol Address offset Bytes Description
Packet 0x0 4 Base address of the data buffer containing transmit data.
Control 0x4 4 Control information, see Table 212.
The data buffer pointer (Packet) is a 32 bit, byte aligned address value containing the
base address of the data buffer. The definition of the control word bits is listed in
Table 212.
Table 212. Transmit descriptor control word

10:0 Size Size in bytes of the data buffer. This is the size of the frame or fragment as it
needs to be fetched by the DMA manager. In most cases it will be equal to the
byte size of the data buffer pointed to by the Packet field of the descriptor. Size
is -1 encoded e.g. a buffer of 8 bytes is encoded as the Size value 7.
25:11 - Unused
26 Override Per frame override. If true, bits 30:27 will override the defaults from the MAC
internal registers. If false, bits 30:27 will be ignored and the default values
from the MAC will be used.
27 Huge If true, enables huge frame, allowing unlimited frame sizes. When false,
prevents transmission of more than the maximum frame length (MAXF[15:0]).
28 Pad If true, pad short frames to 64 bytes.
29 CRC If true, append a hardware CRC to the frame.
30 Last If true, indicates that this is the descriptor for the last fragment in the transmit
frame. If false, the fragment from the next descriptor should be appended.
31 Interrupt If true, a TxDone interrupt will be generated when the data in this frame or
frame fragment has been sent and the associated status information has been
committed to memory.
Table 213 shows the one field transmit status.
Table 213. Transmit status fields

offset
StatusInfo 0x0 4 Transmit status return flags, see Table 214.

The transmit status consists of one word which is the StatusInfo word. It contains flags
returned by the MAC and flags generated by the transmit data path reflecting the status of
the transmission. Table 214 lists the bit definitions in the StatusInfo word.
Table 214. Transmit status information word

20:0 - Unused
24:21 CollisionCount The number of collisions this packet incurred, up to the
Retransmission Maximum.
25 Defer This packet incurred deferral, because the medium was occupied.
This is not an error unless excessive deferral occurs.
26 ExcessiveDefer This packet incurred deferral beyond the maximum deferral limit and
was aborted.
27 ExcessiveCollision Indicates this packet exceeded the maximum collision limit and was
aborted.
28 LateCollision An Out of window Collision was seen, causing packet abort.
29 Underrun A Tx underrun occurred due to the adapter not producing transmit
data.
30 NoDescriptor The transmit stream was interrupted because a descriptor was not
available.
31 Error An error occurred during transmission. This is a logical OR of
Underrun, LateCollision, ExcessiveCollision, and ExcessiveDefer.
For multi-fragment frames, the value of the LateCollision, ExcessiveCollision,

ExcessiveDefer, Defer and CollissionCount bits in all but the last fragment in the frame will
be 0. The status of the last fragment in the frame will copy the value for these bits from the
MAC. All fragment statuses will have valid Error, NoDescriptor and Underrun bits.
11.17 Ethernet block functional description

This section defines the functions of the DMA capable 10/100 Ethernet MAC. After
introducing the DMA concepts of the Ethernet block, and a description of the basic
transmit and receive functions, this section elaborates on advanced features such as flow
control, receive filtering, etc.
11.17.1 Overview
The Ethernet block can transmit and receive Ethernet packets from an off-chip Ethernet
PHY connected through the RMII interface.
Typically during system start-up, the Ethernet block will be initialized. Software
initialization of the Ethernet block should include initialization of the descriptor and status
arrays as well as the receiver fragment buffers.
Remark: When initializing the Ethernet block, it is important to first configure the PHY and
ensure that reference clocks (ENET_REF_CLK signal in RMII mode, or both
ENET_RX_CLK and ENET_TX_CLK signals in MII mode) are present at the external pins
and connected to the EMAC module (selecting the appropriate pins using the PINSEL
registers) prior to continuing with Ethernet configuration. Otherwise the CPU can become
locked and no further functionality will be possible. This will cause JTAG lose
communication with the target, if debug mode is being used.

To transmit a packet the software driver has to set up the appropriate Control registers
and a descriptor to point to the packet data buffer before transferring the packet to
hardware by incrementing the TxProduceIndex register. After transmission, hardware will
increment TxConsumeIndex and optionally generate an interrupt.
The hardware will receive packets from the PHY and apply filtering as configured by the
software driver. While receiving a packet the hardware will read a descriptor from memory
to find the location of the associated receiver data buffer. Receive data is written in the
data buffer and receive status is returned in the receive descriptor status word. Optionally
an interrupt can be generated to notify software that a packet has been received. Note
that the DMA manager will prefetch and buffer up to three descriptors.
11.17.2 AHB interface

The registers of the Ethernet block connect to an AHB slave interface to allow access to
the registers from the CPU.
The AHB interface has a 32 bit data path, which supports only word accesses and has an
address aperture of 4 kB. Table 159 lists the registers of the Ethernet block.
All AHB write accesses to registers are posted except for accesses to the IntSet, IntClear
and IntEnable registers. AHB write operations are executed in order.
If the PowerDown bit of the PowerDown register is set, all AHB read and write accesses
will return a read or write error except for accesses to the PowerDown register.
Bus Errors
The Ethernet block generates errors for several conditions:
• The AHB interface will return a read error when there is an AHB read access to a
write-only register; likewise a write error is returned when there is an AHB write
access to the read-only register. An AHB read or write error will be returned on AHB
read or write accesses to reserved registers. These errors are propagated back to the
CPU. Registers defined as read-only and write-only are identified in Table 159.
• If the PowerDown bit is set all accesses to AHB registers will result in an error
response except for accesses to the PowerDown register.
11.18 Interrupts
The Ethernet block has a single interrupt request output to the CPU (via the Vectored
Interrupt Controller).
The interrupt service routine must read the IntStatus register to determine the origin of the
interrupt. All interrupt statuses can be set by software writing to the IntSet register;
statuses can be cleared by software writing to the IntClear register.
The transmit and receive data paths can only set interrupt statuses, they cannot clear
statuses. The SoftInt interrupt cannot be set by hardware and can be used by software for
test purposes.
11.18.1 Direct Memory Access (DMA)

Descriptor arrays

The Ethernet block includes two DMA managers. The DMA managers make it possible to
transfer frames directly to and from memory with little support from the processor and
without the need to trigger an interrupt for each frame.
The DMA managers work with arrays of frame descriptors and statuses that are stored in
memory. The descriptors and statuses act as an interface between the Ethernet hardware
and the device driver software. There is one descriptor array for receive frames and one
descriptor array for transmit frames. Using buffering for frame descriptors, the memory
traffic and memory bandwidth utilization of descriptors can be kept small.
Each frame descriptor contains two 32 bit fields: the first field is a pointer to a data buffer
containing a frame or a fragment, whereas the second field is a control word related to
that frame or fragment.
The software driver must write the base addresses of the descriptor and status arrays in
the TxDescriptor/RxDescriptor and TxStatus/RxStatus registers. The number of
descriptors/statuses in each array must be written in the
TxDescriptorNumber/RxDescriptorNumber registers. The number of descriptors in an
array corresponds to the number of statuses in the associated status array.
Transmit descriptor arrays, receive descriptor arrays and transmit status arrays must be
aligned on a 4 byte (32bit)address boundary, while the receive status array must be
aligned on a 8 byte (64bit) address boundary.
Ownership of descriptors
Both device driver software and Ethernet hardware can read and write the descriptor
arrays at the same time in order to produce and consume descriptors. Arbitration on the
AHB bus gives priority to the DMA hardware in the case of simultaneous requests. A
descriptor is "owned" either by the device driver or by the Ethernet hardware. Only the
owner of a descriptor reads or writes its value. Typically, the sequence of use and
ownership of descriptors and statuses is as follows: a descriptor is owned and set up by
the device driver; ownership of the descriptor/status is passed by the device driver to the
Ethernet block, which reads the descriptor and writes information to the status field; the
Ethernet block passes ownership of the descriptor back to the device driver, which uses
the status information and then recycles the descriptor to be used for another frame.
Software must pre-allocate the memory used to hold the descriptor arrays.
Software can hand over ownership of descriptors and statuses to the hardware by
incrementing (and wrapping if on the array boundary) the
TxProduceIndex/RxConsumeIndex registers. Hardware hands over descriptors and
status to software by updating the TxConsumeIndex/ RxProduceIndex registers.
After handing over a descriptor to the receive and transmit DMA hardware, device driver
software should not modify the descriptor or reclaim the descriptor by decrementing the
TxProduceIndex/ RxConsumeIndex registers because descriptors may have been
prefetched by the hardware. In this case the device driver software will have to wait until
the frame has been transmitted or the device driver has to soft-reset the transmit and/or
receive data paths which will also reset the descriptor arrays.
Sequential order with wrap-around

When descriptors are read from and statuses are written to the arrays, this is done in
sequential order with wrap-around. Sequential order means that when the Ethernet block
has finished reading/writing a descriptor/status, the next descriptor/status it reads/writes is
the one at the next higher, adjacent memory address. Wrap around means that when the
Ethernet block has finished reading/writing the last descriptor/status of the array (with the
highest memory address), the next descriptor/status it reads/writes is the first
descriptor/status of the array at the base address of the array.
Full and Empty state of descriptor arrays
The descriptor arrays can be empty, partially full or full. A descriptor array is empty when
all descriptors are owned by the producer. A descriptor array is partially full if both
producer and consumer own part of the descriptors and both are busy processing those
descriptors. A descriptor array is full when all descriptors (except one) are owned by the
consumer, so that the producer has no more room to process frames. Ownership of
descriptors is indicated with the use of a consume index and a produce index. The
produce index is the first element of the array owned by the producer. It is also the index
of the array element that is next going to be used by the producer of frames (it may
already be busy using it and subsequent elements). The consume index is the first
element of the array that is owned by the consumer. It is also the number of the array
element next to be consumed by the consumer of frames (it and subsequent elements
may already be in the process of being consumed). If the consume index and the produce
index are equal, the descriptor array is empty and all array elements are owned by the
producer. If the consume index equals the produce index plus one, then the array is full
and all array elements (except the one at the produce index) are owned by the consumer.
With a full descriptor array, still one array element is kept empty, to be able to easily
distinguish the full or empty state by looking at the value of the produce index and
consume index. An array must have at least 2 elements to be able to indicate a full
descriptor array with a produce index of value 0 and a consume index of value 1. The
wrap around of the arrays is taken into account when determining if a descriptor array is
full, so a produce index that indicates the last element in the array and a consume index
that indicates the first element in the array, also means the descriptor array is full. When
the produce index and the consume index are unequal and the consume index is not the
produce index plus one (with wrap around taken into account), then the descriptor array is
partially full and both the consumer and producer own enough descriptors to be able to
operate actively on the descriptor array.
Interrupt bit
The descriptors have an Interrupt bit, which is programmed by software. When the
Ethernet block is processing a descriptor and finds this bit set, it will allow triggering an
interrupt (after committing status to memory) by passing the RxDoneInt or TxDoneInt bits
in the IntStatus register to the interrupt output pin. If the Interrupt bit is not set in the
descriptor, then the RxDoneInt or TxDoneInt are not set and no interrupt is triggered (note
that the corresponding bits in IntEnable must also be set to trigger interrupts). This offers
flexible ways of managing the descriptor arrays. For instance, the device driver could add
10 frames to the Tx descriptor array, and set the Interrupt bit in descriptor number 5 in the
descriptor array. This would invoke the interrupt service routine before the transmit
descriptor array is completely exhausted. The device driver could add another batch of
frames to the descriptor array, without interrupting continuous transmission of frames.
Frame fragments

For maximum flexibility in frame storage, frames can be split up into multiple frame
fragments with fragments located in different places in memory. In this case one
descriptor is used for each frame fragment. So, a descriptor can point to a single frame or
to a fragment of a frame. By using fragments, scatter/gather DMA can be done: transmit
frames are gathered from multiple fragments in memory and receive frames can be
scattered to multiple fragments in memory.
By stringing together fragments it is possible to create large frames from small memory
areas. Another use of fragments is to be able to locate a frame header and frame payload
in different places and to concatenate them without copy operations in the device driver.
For transmissions, the Last bit in the descriptor Control field indicates if the fragment is the
last in a frame; for receive frames, the LastFrag bit in the StatusInfo field of the status
words indicates if the fragment is the last in the frame. If the Last(Frag) bit is 0 the next
descriptor belongs to the same Ethernet frame, If the Last(Frag) bit is 1 the next descriptor
is a new Ethernet frame.
11.18.2 Initialization
After reset, the Ethernet software driver needs to initialize the Ethernet block. During
initialization the software needs to:
• Remove the soft reset condition from the MAC.

• Configure the PHY via the MIIM interface of the MAC.
Remark: it is important to configure the PHY and insure that reference clock
(ENET_REF_CLK) is present at the external pin and connected to the Ethernet MAC
module (selecting the appropriate pin using the PINSEL registers) prior to continuing
with Ethernet configuration. Otherwise the CPU can become locked and no further
functionality will be possible. This will cause JTAG lose communication with the target,
if debug mode is being used.
• Select RMII mode.
• Configure the transmit and receive DMA engines, including the descriptor arrays.
• Configure the host registers (MAC1,MAC2 etc.) in the MAC.
• Enable the receive and transmit data paths.
Depending on the PHY, the software needs to initialize registers in the PHY via the MII
Management interface. The software can read and write PHY registers by programming
the MCFG, MCMD, MADR registers of the MAC. Write data should be written to the
MWTD register; read data and status information can be read from the MRDD and MIND
registers.
The Ethernet block supports RMII PHYs. During initialization software must select RMII
mode by programming the Command register.
Before switching to RMII mode the default soft reset (MAC1 register bit 15) has to be
deasserted when the Ethernet block is in MII mode . The phy_ref_clk must be running and
internally connected to the Ethernet block during this operation.

Transmit and receive DMA engines should be initialized by the device driver by allocating
the descriptor and status arrays in memory. Transmit and receive functions have their own
dedicated descriptor and status arrays. The base addresses of these arrays need to be
programmed in the TxDescriptor/TxStatus and RxDescriptor/RxStatus registers. The
number of descriptors in an array matches the number of statuses in an array.
Please note that the transmit descriptors, receive descriptors and receive statuses are 8
bytes each while the transmit statuses are 4 bytes each. All descriptor arrays and transmit
statuses need to be aligned on 4 byte boundaries; receive status arrays need to be
aligned on 8 byte boundaries. The number of descriptors in the descriptor arrays needs to
be written to the TxDescriptorNumber/RxDescriptorNumber registers using a -1 encoding
i.e. the value in the registers is the number of descriptors minus one e.g. if the descriptor
array has 4 descriptors the value of the number of descriptors register should be 3.
After setting up the descriptor arrays, frame buffers need to be allocated for the receive
descriptors before enabling the receive data path. The Packet field of the receive
descriptors needs to be filled with the base address of the frame buffer of that descriptor.
Amongst others the Control field in the receive descriptor needs to contain the size of the
data buffer using -1 encoding.
The receive data path has a configurable filtering function for discarding/ignoring specific
Ethernet frames. The filtering function should also be configured during initialization.
After an assertion of the hardware reset, the soft reset bit in the MAC will be asserted. The
soft reset condition must be removed before the Ethernet block can be enabled.
Enabling of the receive function is located in two places. The receive DMA manager
needs to be enabled and the receive data path of the MAC needs to be enabled. To
prevent overflow in the receive DMA engine the receive DMA engine should be enabled
by setting the RxEnable bit in the Command register before enabling the receive data path
in the MAC by setting the RECEIVE ENABLE bit in the MAC1 register.
The transmit DMA engine can be enabled at any time by setting the TxEnable bit in the
Command register.
Before enabling the data paths, several options can be programmed in the MAC, such as
automatic flow control, transmit to receive loop-back for verification, full/half duplex
modes, etc.
Base addresses of descriptor arrays and descriptor array sizes cannot be modified
without a (soft) reset of the receive and transmit data paths.
11.18.3 Transmit process

Overview
This section outlines the transmission process.
Device driver sets up descriptors and data
If the descriptor array is full the device driver should wait for the descriptor arrays to
become not full before writing to a descriptor in the descriptor array. If the descriptor array
is not full, the device driver should use the descriptor numbered TxProduceIndex of the
array pointed to by TxDescriptor.

The Packet pointer in the descriptor is set to point to a data frame or frame fragment to be
transmitted. The Size field in the Command field of the descriptor should be set to the
number of bytes in the fragment buffer, -1 encoded. Additional control information can be
indicated in the Control field in the descriptor (bits Interrupt, Last, CRC, Pad).
After writing the descriptor the descriptor needs to be handed over to the hardware by
incrementing (and possibly wrapping) the TxProduceIndex register.
If the transmit data path is disabled, the device driver should not forget to enable the
transmit data path by setting the TxEnable bit in the Command register.
When there is a multi-fragment transmission for fragments other than the last, the Last bit
in the descriptor must be set to 0; for the last fragment the Last bit must be set to 1. To
trigger an interrupt when the frame has been transmitted and transmission status has
been committed to memory, set the Interrupt bit in the descriptor Control field to 1. To have
the hardware add a CRC in the frame sequence control field of this Ethernet frame, set
the CRC bit in the descriptor. This should be done if the CRC has not already been added
by software. To enable automatic padding of small frames to the minimum required frame
size, set the Pad bit in the Control field of the descriptor to 1. In typical applications bits
CRC and Pad are both set to 1.
The device driver can set up interrupts using the IntEnable register to wait for a signal of
completion from the hardware or can periodically inspect (poll) the progress of
transmission. It can also add new frames at the end of the descriptor array, while
hardware consumes descriptors at the start of the array.
The device driver can stop the transmit process by resetting the TxEnable bit in the
Command register to 0. The transmission will not stop immediately; frames already being
transmitted will be transmitted completely and the status will be committed to memory
before deactivating the data path. The status of the transmit data path can be monitored
by the device driver reading the TxStatus bit in the Status register.
As soon as the transmit data path is enabled and the corresponding TxConsumeIndex
and TxProduceIndex are not equal i.e. the hardware still needs to process frames from
the descriptor array, the TxStatus bit in the Status register will return to 1 (active).
Tx DMA manager reads the Tx descriptor array
When the TxEnable bit is set, the Tx DMA manager reads the descriptors from memory at
the address determined by TxDescriptor and TxConsumeIndex. The number of
descriptors requested is determined by the total number of descriptors owned by the
hardware: TxProduceIndex - TxConsumeIndex. Block transferring descriptors minimizes
memory loading. Read data returned from memory is buffered and consumed as needed.
Tx DMA manager transmits data
After reading the descriptor the transmit DMA engine reads the associated frame data
from memory and transmits the frame. After transfer completion, the Tx DMA manager
writes status information back to the StatusInfo and StatusHashCRC words of the status
field. The value of the TxConsumeIndex is only updated after status information has been
committed to memory, which is checked by an internal tag protocol in the memory
interface. The Tx DMA manager continues to transmit frames until the descriptor array is

empty. If the transmit descriptor array is empty the TxStatus bit in the Status register will
return to 0 (inactive). If the descriptor array is empty the Ethernet hardware will set the
TxFinishedInt bit of the IntStatus register. The transmit data path will still be enabled.
The Tx DMA manager inspects the Last bit of the descriptor Control field when loading the
descriptor. If the Last bit is 0, this indicates that the frame consists of multiple fragments.
The Tx DMA manager gathers all the fragments from the host memory, visiting a string of
frame descriptors, and sends them out as one Ethernet frame on the Ethernet connection.
When the Tx DMA manager finds a descriptor with the Last bit in the Control field set to 1,
this indicates the last fragment of the frame and thus the end of the frame is found.
Update ConsumeIndex
Each time the Tx DMA manager commits a status word to memory it completes the
transmission of a descriptor and it increments the TxConsumeIndex (taking wrap around
into account) to hand the descriptor back to the device driver software. Software can
re-use the descriptor for new transmissions after hardware has handed it back.
The device driver software can keep track of the progress of the DMA manager by reading
the TxConsumeIndex register to see how far along the transmit process is. When the Tx
descriptor array is emptied completely, the TxConsumeIndex register retains its last value.
Write transmission status
After the frame has been transmitted over the RMII bus, the StatusInfo word of the frame
descriptor is updated by the DMA manager.
If the descriptor is for the last fragment of a frame (or for the whole frame if there are no
fragments), then depending on the success or failure of the frame transmission, error
flags (Error, LateCollision, ExcessiveCollision, Underrun, ExcessiveDefer, Defer) are set
in the status. The CollisionCount field is set to the number of collisions the frame incurred,
up to the Retransmission Maximum programmed in the Collision window/retry register of
the MAC.
Statuses for all but the last fragment in the frame will be written as soon as the data in the
frame has been accepted by the Tx DMA manager. Even if the descriptor is for a frame
fragment other than the last fragment, the error flags are returned via the AHB interface. If
the Ethernet block detects a transmission error during transmission of a (multi-fragment)
frame, all remaining fragments of the frame are still read via the AHB interface. After an
error, the remaining transmit data is discarded by the Ethernet block. If there are errors
during transmission of a multi-fragment frame the error statuses will be repeated until the
last fragment of the frame. Statuses for all but the last fragment in the frame will be written
as soon as the data in the frame has been accepted by the Tx DMA manager. These may
include error information if the error is detected early enough. The status for the last
fragment in the frame will only be written after the transmission has completed on the
Ethernet connection. Thus, the status for the last fragment will always reflect any error
that occurred anywhere in the frame.
The status of the last frame transmission can also be inspected by reading the TSV0 and
TSV1 registers. These registers do not report statuses on a fragment basis and do not
store information of previously sent frames. They are provided primarily for debug

takes place through the frame descriptors. The status registers are valid as long as the
internal status of the MAC is valid and should typically only be read when the transmit and
receive processes are halted.
Transmission error handling
If an error occurs during the transmit process, the Tx DMA manager will report the error
via the transmission StatusInfo word written in the Status array and the IntStatus interrupt
status register.
The transmission can generate several types of errors: LateCollision, ExcessiveCollision,

ExcessiveDefer, Underrun, and NoDescriptor. All have corresponding bits in the
transmission StatusInfo word. In addition to the separate bits in the StatusInfo word,
LateCollision, ExcessiveCollision, and ExcessiveDefer are ORed together into the Error
bit of the Status. Errors are also propagated to the IntStatus register; the TxError bit in the
IntStatus register is set in the case of a LateCollision, ExcessiveCollision, ExcessiveDefer,
or NoDescriptor error; Underrun errors are reported in the TxUnderrun bit of the IntStatus
register.
Underrun errors can have three causes:
• The next fragment in a multi-fragment transmission is not available. This is a nonfatal

error. A NoDescriptor status will be returned on the previous fragment and the TxError
bit in IntStatus will be set.
• The transmission fragment data is not available when the Ethernet block has already
started sending the frame. This is a nonfatal error. An Underrun status will be returned
on transfer and the TxError bit in IntStatus will be set.
• The flow of transmission statuses stalls and a new status has to be written while a
previous status still waits to be transferred across the memory interface. This is a fatal
error which can only be resolved by a soft reset of the hardware.
The first and second situations are nonfatal and the device driver has to resend the frame
or have upper software layers resend the frame. In the third case the hardware is in an
undefined state and needs to be soft reset by setting the TxReset bit in the Command
register.
After reporting a LateCollision, ExcessiveCollision, ExcessiveDefer or Underrun error, the

transmission of the erroneous frame will be aborted, remaining transmission data and
frame fragments will be discarded and transmission will continue with the next frame in
the descriptor array.
Device drivers should catch the transmission errors and take action.
Transmit triggers interrupts
The transmit data path can generate four different interrupt types:
• If the Interrupt bit in the descriptor Control field is set, the Tx DMA will set the
TxDoneInt bit in the IntStatus register after sending the fragment and committing the
associated transmission status to memory. Even if a descriptor (fragment) is not the
last in a multi-fragment frame the Interrupt bit in the descriptor can be used to
generate an interrupt.

• If the descriptor array is empty while the Ethernet hardware is enabled the hardware
will set the TxFinishedInt bit of the IntStatus register.
• If the AHB interface does not consume the transmission statuses at a sufficiently high
bandwidth the transmission may underrun in which case the TxUnderrun bit will be set
in the IntStatus register. This is a fatal error which requires a soft reset of the
transmission queue.
• In the case of a transmission error (LateCollision, ExcessiveCollision, or
ExcessiveDefer) or a multi-fragment frame where the device driver did provide the
initial fragments but did not provide the rest of the fragments (NoDescriptor) or in the
case of a nonfatal overrun, the hardware will set the TxErrorInt bit of the IntStatus
register.
All of the above interrupts can be enabled and disabled by setting or resetting the
corresponding bits in the IntEnable register. Enabling or disabling does not affect the
IntStatus register contents, only the propagation of the interrupt status to the CPU (via the
Vectored Interrupt Controller).
The interrupts, either of individual frames or of the whole list, are a good means of
communication between the DMA manager and the device driver, triggering the device
driver to inspect the status words of descriptors that have been processed.
Transmit example
Figure 35 illustrates the transmit process in an example transmitting uses a frame header
of 8 bytes and a frame payload of 12 bytes.

0x7FE0131B
0x7FE01314
TxDescriptor TxStatus
0x7FE010EC 0x7FE011F8
PACKET 0 HEADER (8 bytes)
status 0
Packet StatusInfo
descriptor 0
0x7FE0141C
0x7FE01411
0x7FE01419
0x7FE01314
status 1
0x7FE010F0 0x7FE011FC
0 0 CONTROL
Control 7 StatusInfo
status array
PACKET 0 PAYLOAD (12 bytes)
0x7FE010F4
status 2
Packet
descriptor 1
0x7FE01200
0x7FE01411 StatusInfo
descriptor array
0x7FE010F8
status 3
0 0 CONTROL
Control 7
StatusInfo 0x7FE01204
Packet
0x7FE010FC
0x7FE0132B
descriptor 2
0x7FE01324
0x7FE01419
0x7FE0100 1 1 CONTROL
Control 3
TxProduceIndex
PACKET 1 HEADER (8 bytes)

TxConsumeIndex
Packet
descriptor 3
0x7FE0104 0x7FE01324
TxDescriptorNumber
=3
0 0 CONTROL
Control 7
0x7FE01108
descriptor array fragment buffers status array
Fig 35. Transmit example memory and registers
After reset the values of the DMA registers will be zero. During initialization the device
driver will allocate the descriptor and status array in memory. In this example, an array of
four descriptors is allocated; the array is 4x2x4 bytes and aligned on a 4 byte address
boundary. Since the number of descriptors matches the number of statuses the status
array consists of four elements; the array is 4x1x4 bytes and aligned on a 4 byte address
boundary. The device driver writes the base address of the descriptor array
(0x7FE0 10EC) to the TxDescriptor register and the base address of the status array
(0x7FE0 11F8) to the TxStatus register. The device driver writes the number of descriptors
and statuses minus 1(3) to the TxDescriptorNumber register. The descriptors and
statuses in the arrays need not be initialized, yet.
At this point, the transmit data path may be enabled by setting the TxEnable bit in the
Command register. If the transmit data path is enabled while there are no further frames to
send the TxFinishedInt interrupt flag will be set. To reduce the processor interrupt load
only the desired interrupts can be enabled by setting the relevant bits in the IntEnable
register.
Now suppose application software wants to transmit a frame of 12 bytes using a TCP/IP
protocol (in real applications frames will be larger than 12 bytes). The TCP/IP stack will
add a header to the frame. The frame header need not be immediately in front of the
payload data in memory. The device driver can program the Tx DMA to collect header and
payload data. To do so, the device driver will program the first descriptor to point at the

frame header; the Last flag in the descriptor will be set to false/0 to indicate a
multi-fragment transmission. The device driver will program the next descriptor to point at
the actual payload data. The maximum size of a payload buffer is 2 kB so a single
descriptor suffices to describe the payload buffer. For the sake of the example though the
payload is distributed across two descriptors. After the first descriptor in the array
describing the header, the second descriptor in the array describes the initial 8 bytes of
the payload; the third descriptor in the array describes the remaining 4 bytes of the frame.
In the third descriptor the Last bit in the Control word is set to true/1 to indicate it is the last
descriptor in the frame. In this example the Interrupt bit in the descriptor Control field is set
in the last fragment of the frame in order to trigger an interrupt after the transmission
completed. The Size field in the descriptor’s Control word is set to the number of bytes in
the fragment buffer, -1 encoded.
Note that in real device drivers, the payload will typically only be split across multiple
descriptors if it is more than 2 kB. Also note that transmission payload data is forwarded to
the hardware without the device driver copying it (zero copy device driver).
After setting up the descriptors for the transaction the device driver increments the
TxProduceIndex register by 3 since three descriptors have been programmed. If the
transmit data path was not enabled during initialization the device driver needs to enable
the data path now.
If the transmit data path is enabled the Ethernet block will start transmitting the frame as
soon as it detects the TxProduceIndex is not equal to TxConsumeIndex - both were zero
after reset. The Tx DMA will start reading the descriptors from memory. The memory
system will return the descriptors and the Ethernet block will accept them one by one
while reading the transmit data fragments.
As soon as transmission read data is returned from memory, the Ethernet block will try to
start transmission on the Ethernet connection via the RMII interface.
After transmitting each fragment of the frame the Tx DMA will write the status of the
fragment’s transmission. Statuses for all but the last fragment in the frame will be written
as soon as the data in the frame has been accepted by the Tx DMA manager. The status
for the last fragment in the frame will only be written after the transmission has completed
on the Ethernet connection.
Since the Interrupt bit in the descriptor of the last fragment is set, after committing the
status of the last fragment to memory the Ethernet block will trigger a TxDoneInt interrupt,
which triggers the device driver to inspect the status information.
In this example the device driver cannot add new descriptors as long as the Ethernet
block has not incremented the TxConsumeIndex because the descriptor array is full (even
though one descriptor is not programmed yet). Only after the hardware commits the status
for the first fragment to memory and the TxConsumeIndex is set to 1 by the DMA manager
can the device driver program the next (the fourth) descriptor. The fourth descriptor can
already be programmed before completely transmitting the first frame.
In this example the hardware adds the CRC to the frame. If the device driver software
adds the CRC, the CRC trailer can be considered another frame fragment which can be
added by doing another gather DMA.

Each data byte is transmitted across the RMII interface as four 2-bit values. The Ethernet
block adds the preamble, frame delimiter leader, and the CRC trailer if hardware CRC is
enabled. Once transmission on the RMII interface commences the transmission cannot
be interrupted without generating an underrun error, which is why descriptors and data
read commands are issued as soon as possible and pipelined.
Using RMII, data between the Ethernet block and the PHY are communicated at 50 MHz.
In 10 Mbps mode data will only be transmitted once every 10 clock cycles.
11.18.4 Receive process

This section outlines the receive process including the activities in the device driver
software.
Device driver sets up descriptors
After initializing the receive descriptor and status arrays to receive frames from the
Ethernet connection, the receive data path should be enabled in the MAC1 register and
the Control register.
During initialization, each Packet pointer in the descriptors is set to point to a data
fragment buffer. The size of the buffer is stored in the Size bits of the Control field of the
descriptor. Additionally, the Control field in the descriptor has an Interrupt bit. The Interrupt
bit allows generation of an interrupt after a fragment buffer has been filled and its status
has been committed to memory.
After the initialization and enabling of the receive data path, all descriptors are owned by
the receive hardware and should not be modified by the software unless hardware hands
over the descriptor by incrementing the RxProduceIndex, indicating that a frame has been
received. The device driver is allowed to modify the descriptors after a (soft) reset of the
receive data path.
Rx DMA manager reads Rx descriptor arrays
When the RxEnable bit in the Command register is set, the Rx DMA manager reads the
descriptors from memory at the address determined by RxDescriptor and
RxProduceIndex. The Ethernet block will start reading descriptors even before actual
receive data arrives on the RMII interface (descriptor prefetching). The block size of the
descriptors to be read is determined by the total number of descriptors owned by the
hardware: RxConsumeIndex - RxProduceIndex - 1. Block transferring of descriptors
minimizes memory load. Read data returned from memory is buffered and consumed as
needed.
RX DMA manager receives data
After reading the descriptor, the receive DMA engine waits for the MAC to return receive
data from the RMII interface that passes the receive filter. Receive frames that do not
match the filtering criteria are not passed to memory. Once a frame passes the receive
filter, the data is written in the fragment buffer associated with the descriptor. The Rx DMA
does not write beyond the size of the buffer. When a frame is received that is larger than a
descriptor’s fragment buffer, the frame will be written to multiple fragment buffers of
consecutive descriptors. In the case of a multi-fragment reception, all but the last fragment
in the frame will return a status where the LastFrag bit is set to 0. Only on the last

fragment of a frame the LastFrag bit in the status will be set to 1. If a fragment buffer is the
last of a frame, the buffer may not be filled completely. The first receive data of the next
frame will be written to the fragment buffer of the next descriptor.
After receiving a fragment, the Rx DMA manager writes status information back to the
StatusInfo and StatusHashCRC words of the status. The Ethernet block writes the size in
bytes of a descriptor’s fragment buffer in the RxSize field of the Status word. The value of
the RxProduceIndex is only updated after the fragment data and the fragment status
information has been committed to memory, which is checked by an internal tag protocol
in the memory interface. The Rx DMA manager continues to receive frames until the
descriptor array is full. If the descriptor array is full, the Ethernet hardware will set the
RxFinishedInt bit of the IntStatus register. The receive data path will still be enabled. If the
receive descriptor array is full any new receive data will generate an overflow error and
interrupt.
Update ProduceIndex
Each time the Rx DMA manager commits a data fragment and the associated status word
to memory, it completes the reception of a descriptor and increments the RxProduceIndex
(taking wrap around into account) in order to hand the descriptor back to the device driver
software. Software can re-use the descriptor for new receptions by handing it back to
hardware when the receive data has been processed.
The device driver software can keep track of the progress of the DMA manager by reading
the RxProduceIndex register to see how far along the receive process is. When the Rx
descriptor array is emptied completely, the RxProduceIndex retains its last value.
Write reception status
After the frame has been received from the RMII bus, the StatusInfo and StatusHashCRC
words of the frame descriptor are updated by the DMA manager.
If the descriptor is for the last fragment of a frame (or for the whole frame if there are no
fragments), then depending on the success or failure of the frame reception, error flags
(Error, NoDescriptor, Overrun, AlignmentError, RangeError, LengthError, SymbolError, or
CRCError) are set in StatusInfo. The RxSize field is set to the number of bytes actually
written to the fragment buffer, -1 encoded. For fragments not being the last in the frame
the RxSize will match the size of the buffer. The hash CRCs of the destination and source
addresses of a packet are calculated once for all the fragments belonging to the same
packet and then stored in every StatusHashCRC word of the statuses associated with the
corresponding fragments. If the reception reports an error, any remaining data in the
receive frame is discarded and the LastFrag bit will be set in the receive status field, so
the error flags in all but the last fragment of a frame will always be 0.
The status of the last received frame can also be inspected by reading the RSV register.
The register does not report statuses on a fragment basis and does not store information
of previously received frames. RSV is provided primarily for debug purposes, because the
communication between driver software and the Ethernet block takes place through the
frame descriptors.
Reception error handling

When an error occurs during the receive process, the Rx DMA manager will report the
error via the receive StatusInfo written in the Status array and the IntStatus interrupt status
register.
The receive process can generate several types of errors: AlignmentError, RangeError,
LengthError, SymbolError, CRCError, Overrun, and NoDescriptor. All have corresponding
bits in the receive StatusInfo. In addition to the separate bits in the StatusInfo,
AlignmentError, RangeError, LengthError, SymbolError, and CRCError are ORed together
into the Error bit of the StatusInfo. Errors are also propagated to the IntStatus register; the
RxError bit in the IntStatus register is set if there is an AlignmentError, RangeError,
LengthError, SymbolError, CRCError, or NoDescriptor error; nonfatal overrun errors are
reported in the RxError bit of the IntStatus register; fatal Overrun errors are report in the
RxOverrun bit of the IntStatus register. On fatal overrun errors, the Rx data path needs to
be soft reset by setting the RxReset bit in the Command register.
Overrun errors can have three causes:
• In the case of a multi-fragment reception, the next descriptor may be missing. In this
case the NoDescriptor field is set in the status word of the previous descriptor and the
RxError in the IntStatus register is set. This error is nonfatal.
• The data flow on the receiver data interface stalls, corrupting the packet. In this case
the overrun bit in the status word is set and the RxError bit in the IntStatus register is
set. This error is nonfatal.
• The flow of reception statuses stalls and a new status has to be written while a
previous status still waits to be transferred across the memory interface. This error will
corrupt the hardware state and requires the hardware to be soft reset. The error is
detected and sets the Overrun bit in the IntStatus register.
The first overrun situation will result in an incomplete frame with a NoDescriptor status
and the RxError bit in IntStatus set. Software should discard the partially received frame.
In the second overrun situation the frame data will be corrupt which results in the Overrun
status bit being set in the Status word while the IntError interrupt bit is set. In the third case
receive errors cannot be reported in the receiver Status arrays which corrupts the
hardware state; the errors will still be reported in the IntStatus register’s Overrun bit. The
RxReset bit in the Command register should be used to soft reset the hardware.
Device drivers should catch the above receive errors and take action.
Receive triggers interrupts
The receive data path can generate four different interrupt types:
• If the Interrupt bit in the descriptor Control field is set, the Rx DMA will set the
RxDoneInt bit in the IntStatus register after receiving a fragment and committing the
associated data and status to memory. Even if a descriptor (fragment) is not the last in
a multi-fragment frame, the Interrupt bit in the descriptor can be used to generate an
interrupt.
• If the descriptor array is full while the Ethernet hardware is enabled, the hardware will
set the RxFinishedInt bit of the IntStatus register.
• If the AHB interface does not consume receive statuses at a sufficiently high
bandwidth, the receive status process may overrun, in which case the RxOverrun bit
will be set in the IntStatus register.

• If there is a receive error (AlignmentError, RangeError, LengthError, SymbolError, or

CRCError), or a multi-fragment frame where the device driver did provide descriptors
for the initial fragments but did not provide the descriptors for the rest of the
fragments, or if a nonfatal data Overrun occurred, the hardware will set the RxErrorInt
bit of the IntStatus register.
All of the above interrupts can be enabled and disabled by setting or resetting the
corresponding bits in the IntEnable register. Enabling or disabling does not affect the
IntStatus register contents, only the propagation of the interrupt status to the CPU (via the
Vectored Interrupt Controller).
The interrupts, either of individual frames or of the whole list, are a good means of
communication between the DMA manager and the device driver, triggering the device
driver to inspect the status words of descriptors that have been processed.
Device driver processes receive data
As a response to status (e.g. RxDoneInt) interrupts or polling of the RxProduceIndex, the

device driver can read the descriptors that have been handed over to it by the hardware
(RxProduceIndex - RxConsumeIndex). The device driver should inspect the status words
in the status array to check for multi-fragment receptions and receive errors.
The device driver can forward receive data and status to upper software layers. After
processing of data and status, the descriptors, statuses and data buffers may be recycled
and handed back to hardware by incrementing the RxConsumeIndex.
Receive example
Figure 36 illustrates the receive process in an example receiving a frame of 19 bytes.

0x7FE01409
0x7FE01410
RxDescriptor RxStatus
FRAGMENT 0 BUFFER(8 bytes)
Status 0
0x7FE010EC StatusInfo 7 0x7FE011F8
PACKET
Descriptor 0
0x7FE01411
0x7FE01418
0x7FE01409 StatusHashCRC
Status 1
0x7FE010F0 StatusInfo 7 0x7FE01200
1 CONTROL 7
status array
StatusHashCRC
Status 2
0x7FE010F4 PACKET StatusInfo 2 0x7FE01208
Descriptor 1
0x7FE0141B
0x7FE01419
0x7FE01411
StatusHashCRC
descriptor array
0x7FE010F8 1 CONTROL 7
Status 3
StatusInfo 7 0x7FE01210
FRAGMENT 2 BUFFER(3 bytes) StatusHashCRC

PACKET
0x7FE010FC
Descriptor 2
0x7FE0132C
0x7FE01325
0x7FE01419
0x7FE01100 1 CONTROL 7

PACKET RxProduceIndex
Descriptor 3
0x7FE01104 0x7FE01325
RxConsumeIndex
1 CONTROL 7
0x7FE01108 RxDescriptorNumber= 3
descriptor array fragment buffers status array
Fig 36. Receive Example Memory and Registers
After reset, the values of the DMA registers will be zero. During initialization, the device
driver will allocate the descriptor and status array in memory. In this example, an array of
four descriptors is allocated; the array is 4x2x4 bytes and aligned on a 4 byte address
boundary. Since the number of descriptors matches the number of statuses, the status
array consists of four elements; the array is 4x2x4 bytes and aligned on a 8 byte address
boundary. The device driver writes the base address of the descriptor array
(0xFEED B0EC) in the RxDescriptor register, and the base address of the status array
(0xFEED B1F8) in the RxStatus register. The device driver writes the number of
descriptors and statuses minus 1 (3) in the RxDescriptorNumber register. The descriptors
and statuses in the arrays need not be initialized yet.
After allocating the descriptors, a fragment buffer needs to be allocated for each of the
descriptors. Each fragment buffer can be between 1 byte and 2 k bytes. The base
address of the fragment buffer is stored in the Packet field of the descriptors. The number
of bytes in the fragment buffer is stored in the Size field of the descriptor Control word.
The Interrupt field in the Control word of the descriptor can be set to generate an interrupt
as soon as the descriptor has been filled by the receive process. In this example the
fragment buffers are 8 bytes, so the value of the Size field in the Control word of the
descriptor is set to 7. Note that in this example, the fragment buffers are actually a

continuous memory space; even when a frame is distributed over multiple fragments it will
typically be in a linear, continuous memory space; when the descriptors wrap at the end of
the descriptor array the frame will not be in a continuous memory space.
The device driver should enable the receive process by writing a 1 to the RxEnable bit of
the Command register, after which the MAC needs to be enabled by writing a 1 to the
‘RECEIVE ENABLE’ bit of the MAC1 configuration register. The Ethernet block will now
start receiving Ethernet frames. To reduce the processor interrupt load, some interrupts
can be disabled by setting the relevant bits in the IntEnable register.
After the Rx DMA manager is enabled, it will start issuing descriptor read commands. In
this example the number of descriptors is 4. Initially the RxProduceIndex and
RxConsumeIndex are 0. Since the descriptor array is considered full if RxProduceIndex
== RxConsumeIndex - 1, the Rx DMA manager can only read (RxConsumeIndex -
RxProduceIndex - 1 =) 3 descriptors; note the wrapping.
After enabling the receive function in the MAC, data reception will begin starting at the
next frame i.e. if the receive function is enabled while the RMII interface is halfway
through receiving a frame, the frame will be discarded and reception will start at the next
frame. The Ethernet block will strip the preamble and start of frame delimiter from the
frame. If the frame passes the receive filtering, the Rx DMA manager will start writing the
frame to the first fragment buffer.
Suppose the frame is 19 bytes long. Due to the buffer sizes specified in this example, the
frame will be distributed over three fragment buffers. After writing the initial 8 bytes in the
first fragment buffer, the status for the first fragment buffer will be written and the Rx DMA
will continue filling the second fragment buffer. Since this is a multi-fragment receive, the
status of the first fragment will have a 0 for the LastFrag bit in the StatusInfo word; the
RxSize field will be set to 7 (8, -1 encoded). After writing the 8 bytes in the second
fragment the Rx DMA will continue writing the third fragment. The status of the second
fragment will be like the status of the first fragment: LastFrag = 0, RxSize = 7. After writing
the three bytes in the third fragment buffer, the end of the frame has been reached and the
status of the third fragment is written. The third fragment’s status will have the LastFrag bit
set to 1 and the RxSize equal to 2 (3, -1 encoded).
The next frame received from the RMII interface will be written to the fourth fragment
buffer i.e. five bytes of the third buffer will be unused.
The Rx DMA manager uses an internal tag protocol in the memory interface to check that
the receive data and status have been committed to memory. After the status of the
fragments are committed to memory, an RxDoneInt interrupt will be triggered, which
activates the device driver to inspect the status information. In this example, all
descriptors have the Interrupt bit set in the Control word i.e. all descriptors will generate
an interrupt after committing data and status to memory.
In this example the receive function cannot read new descriptors as long as the device
driver does not increment the RxConsumeIndex, because the descriptor array is full (even
though one descriptor is not programmed yet). Only after the device driver has forwarded
the receive data to application software, and after the device driver has updated the
RxConsumeIndex by incrementing it, will the Ethernet block can continue reading
descriptors and receive data. The device driver will probably increment the
RxConsumeIndex by 3, since the driver will forward the complete frame consisting of
three fragments to the application, and hence free up three descriptors at the same time.

Each four pairs of bits transferred on the RMII interface is transferred as a byte on the
data write interface after being delayed by 128 or 136 cycles for filtering by the receive
filter and buffer modules. The Ethernet block removes preamble, frame start delimiter, and
CRC from the data and checks the CRC. To limit the buffer NoDescriptor error probability,
three descriptors are buffered. The value of the RxProduceIndex is only updated after
status information has been committed to memory, which is checked by an internal tag
protocol in the memory interface. The software device driver will process the receive data,
after which the device driver will update the RxConsumeIndex.
11.18.5 Transmission retry

If a collision on the Ethernet occurs, it usually takes place during the collision window
spanning the first 64 bytes of a frame. If collision is detected, the Ethernet block will retry
the transmission. For this purpose, the first 64 bytes of a frame are buffered, so that this
data can be used during the retry. A transmission retry within the first 64 bytes in a frame
is fully transparent to the application and device driver software.
When a collision occurs outside of the 64 byte collision window, a LateCollision error is
triggered, and the transmission is aborted. After a LateCollision error, the remaining data
in the transmit frame will be discarded. The Ethernet block will set the Error and
LateCollision bits in the frame’s status fields. The TxError bit in the IntStatus register will
be set. If the corresponding bit in the IntEnable register is set, the TxError bit in the
IntStatus register will be propagated to the CPU (via the Vectored Interrupt Controller).
The device driver software should catch the interrupt and take appropriate actions.
The ‘RETRANSMISSION MAXIMUM’ field of the CLRT register can be used to configure
the maximum number of retries before aborting the transmission.
11.18.6 Status hash CRC calculations

For each received frame, the Ethernet block is able to detect the destination address and
source address and from them calculate the corresponding hash CRCs. To perform the
computation, the Ethernet block features two internal blocks: one is a controller
synchronized with the beginning and the end of each frame, the second block is the CRC
calculator.
When a new frame is detected, internal signaling notifies the controller.The controller
starts counting the incoming bytes of the frame, which correspond to the destination
address bytes. When the sixth (and last) byte is counted, the controller notifies the
calculator to store the corresponding 32 bit CRC into a first inner register. Then the
controller repeats counting the next incoming bytes, in order to get synchronized with the
source address. When the last byte of the source address is encountered, the controller
again notifies the CRC calculator, which freezes until the next new frame. When the
calculator receives this second notification, it stores the present 32 bit CRC into a second
inner register. Then the CRCs remain frozen in their own registers until new notifications
arise.
The destination address and source address hash CRCs being written in the
StatusHashCRC word are the nine most significant bits of the 32 bit CRCs as calculated
by the CRC calculator.

11.18.7 Duplex modes

The Ethernet block can operate in full duplex and half duplex mode. Half or full duplex
mode needs to be configured by the device driver software during initialization.
For a full duplex connection the FullDuplex bit of the Command register needs to be set to
1 and the FULL-DUPLEX bit of the MAC2 configuration register needs to be set to 1; for
half duplex the same bits need to be set to 0.
11.18.8 IEE 802.3/Clause 31 flow control

Overview
For full duplex connections, the Ethernet block supports IEEE 802.3/clause 31 flow control
using pause frames. This type of flow control may be used in full-duplex point-to-point
connections. Flow control allows a receiver to stall a transmitter e.g. when the receive
buffers are (almost) full. For this purpose, the receiving side sends a pause frame to the
transmitting side.
Pause frames use units of 512 bit times corresponding to 128 rx_clk/tx_clk cycles.
Receive flow control
In full-duplex mode, the Ethernet block will suspend its transmissions when the it receives
a pause frame. Rx flow control is initiated by the receiving side of the transmission. It is
enabled by setting the ‘RX FLOW CONTROL’ bit in the MAC1 configuration register. If the
RX FLOW CONTROL’ bit is zero, then the Ethernet block ignores received pause control
frames. When a pause frame is received on the Rx side of the Ethernet block,
transmission on the Tx side will be interrupted after the currently transmitting frame has
completed, for an amount of time as indicated in the received pause frame. The transmit
data path will stop transmitting data for the number of 512 bit slot times encoded in the
pause-timer field of the received pause control frame.
By default the received pause control frames are not forwarded to the device driver. To
forward the receive flow control frames to the device driver, set the ‘PASS ALL RECEIVE
FRAMES’ bit in the MAC1 configuration register.
Transmit flow control
If case device drivers need to stall the receive data e.g. because software buffers are full,
the Ethernet block can transmit pause control frames. Transmit flow control needs to be
initiated by the device driver software; there is no IEEE 802.3/31 flow control initiated by
hardware, such as the DMA managers.
With software flow control, the device driver can detect a situation in which the process of
receiving frames needs to be interrupted by sending out Tx pause frames. Note that due
to Ethernet delays, a few frames can still be received before the flow control takes effect
and the receive stream stops.
Transmit flow control is activated by writing 1 to the TxFlowControl bit of the Command
register. When the Ethernet block operates in full duplex mode, this will result in
transmission of IEEE 802.3/31 pause frames. The flow control continues until a 0 is
written to TxFlowControl bit of the Command register.

If the MAC is operating in full-duplex mode, then setting the TxFlowControl bit of the
Command register will start a pause frame transmission. The value inserted into the
pause-timer value field of transmitted pause frames is programmed via the
PauseTimer[15:0] bits in the FlowControlCounter register. When the TxFlowControl bit is
deasserted, another pause frame having a pause-timer value of 0x0000 is automatically
sent to abort flow control and resume transmission.
When flow control be in force for an extended time, a sequence of pause frames must be
transmitted. This is supported with a mirror counter mechanism. To enable mirror
counting, a nonzero value is written to the MirrorCounter[15:0] bits in the
FlowControlCounter register. When the TxFlowControl bit is asserted, a pause frame is
transmitted. After sending the pause frame, an internal mirror counter is initialized to zero.
The internal mirror counter starts incrementing one every 512 bit-slot times. When the
internal mirror counter reaches the MirrorCounter value, another pause frame is
transmitted with pause-timer value equal to the PauseTimer field from the
FlowControlCounter register, the internal mirror counter is reset to zero and restarts
counting. The register MirrorCounter[15:0] is usually set to a smaller value than register
PauseTimer[15:0] to ensure an early expiration of the mirror counter, allowing time to send
a new pause frame before the transmission on the other side can resume. By continuing
to send pause frames before the transmitting side finishes counting the pause timer, the
pause can be extended as long as TxFlowControl is asserted. This continues until
TxFlowControl is deasserted when a final pause frame having a pause-timer value of
0x0000 is automatically sent to abort flow control and resume transmission. To disable the
mirror counter mechanism, write the value 0 to MirrorCounter field in the
FlowControlCounter register. When using the mirror counter mechanism, account for
time-of-flight delays, frame transmission time, queuing delays, crystal frequency
tolerances, and response time delays by programming the MirrorCounter conservatively,
typically about 80% of the PauseTimer value.
If the software device driver sets the MirrorCounter field of the FlowControlCounter
register to zero, the Ethernet block will only send one pause control frame. After sending
the pause frame an internal pause counter is initialized at zero; the internal pause counter
is incremented by one every 512 bit-slot times. Once the internal pause counter reaches
the value of the PauseTimer register, the TxFlowControl bit in the Command register will
be reset. The software device driver can poll the TxFlowControl bit to detect when the
pause completes.
The value of the internal counter in the flow control module can be read out via the
FlowControlStatus register. If the MirrorCounter is nonzero, the FlowControlStatus register
will return the value of the internal mirror counter; if the MirrorCounter is zero the
FlowControlStatus register will return the value of the internal pause counter value.
The device driver is allowed to dynamically modify the MirrorCounter register value and
switch between zero MirrorCounter and nonzero MirrorCounter modes.
Transmit flow control is enabled via the ‘TX FLOW CONTROL’ bit in the MAC1
configuration register. If the ‘TX FLOW CONTROL’ bit is zero, then the MAC will not
transmit pause control frames, software must not initiate pause frame transmissions, and
the TxFlowControl bit in the Command register should be zero.
Transmit flow control example
Figure 37 illustrates the transmit flow control.

device driver PauseTimer

clear
register MirrorCounter
TxFlowCtl TxFlowCtl
writes
RMII normal pause control pause control pause control

frame normal transimisson frame frame
transmit transmission transmission transmission transmission
MirrorCounter
(1/515 bit
slots)
RMII
normal receive pause in effect normal receive
receive
0 50 100 150 200 250 300 350 400 450 500
Fig 37. Transmit Flow Control
In this example, a frame is received while transmitting another frame (full duplex.) The
device driver detects that some buffer might overrun and enables the transmit flow control
by programming the PauseTimer and MirrorCounter fields of the FlowControlCounter
register, after which it enables the transmit flow control by setting the TxFlowControl bit in
the Command register.
As a response to the enabling of the flow control a pause control frame will be sent after
the currently transmitting frame has been transmitted. When the pause frame
transmission completes the internal mirror counter will start counting bit slots; as soon as
the counter reaches the value in the MirrorCounter field another pause frame is
transmitted. While counting the transmit data path will continue normal transmissions.
As soon as software disables transmit flow control a zero pause control frame is
transmitted to resume the receive process.
11.18.9 Half-Duplex mode backpressure

When in half-duplex mode, backpressure can be generated to stall receive packets by
sending continuous preamble that basically jams any other transmissions on the Ethernet
medium. When the Ethernet block operates in half duplex mode, asserting
the TxFlowControl bit in the Command register will result in applying continuous preamble
on the Ethernet wire, effectively blocking traffic from any other Ethernet station on the
same segment.
In half duplex mode, when the TxFlowControl bit goes high, continuous preamble is sent
until TxFlowControl is deasserted. If the medium is idle, the Ethernet block begins
transmitting preamble, which raises carrier sense causing all other stations to defer. In the
event the transmitting of preamble causes a collision, the backpressure ‘rides through’ the
collision. The colliding station backs off and then defers to the backpressure. If during
backpressure, the user wishes to send a frame, the backpressure is interrupted, the frame
sent and then the backpressure resumed. If TxFlowControl is asserted for longer than
3.3 ms in 10 Mbps mode or 0.33 ms in 100 Mbps mode, backpressure will cease sending
preamble for several byte times to avoid the jabber limit.

11.18.10 Receive filtering

Features of receive filtering
The Ethernet MAC has several receive packet filtering functions that can be configured
from the software driver:
• Perfect address filter: allows packets with a perfectly matching station address to be
identified and passed to the software driver.
• Hash table filter: allows imperfect filtering of packets based on the station address.
• Unicast/multicast/broadcast filtering: allows passing of all unicast, multicast, and/or
broadcast packets.
• Magic packet filter: detection of magic packets to generate a Wake-on-LAN interrupt.
The filtering functions can be logically combined to create complex filtering functions.
Furthermore, the Ethernet block can pass or reject runt packets smaller than 64 bytes; a
promiscuous mode allows all packets to be passed to software.
Overview
The Ethernet block has the capability to filter out receive frames by analyzing the Ethernet
destination address in the frame. This capability greatly reduces the load on the host
system, because Ethernet frames that are addressed to other stations would otherwise
need to be inspected and rejected by the device driver software, using up bandwidth,
memory space, and host CPU time. Address filtering can be implemented using the
perfect address filter or the (imperfect) hash filter. The latter produces a 6 bits hash code
which can be used as an index into a 64 entry programmable hash table. Figure 38
depicts a functional view of the receive filter.
At the top of the diagram the Ethernet receive frame enters the filters. Each filter is
controlled by signals from control registers; each filter produces a ‘Ready’ output and a
‘Match’ output. If ‘Ready’ is 0 then the Match value is ‘don’t care’; if a filter finishes filtering
then it will assert its Ready output; if the filter finds a matching frame it will assert the
Match output along with the Ready output. The results of the filters are combined by logic
functions into a single RxAbort output. If the RxAbort output is asserted, the frame does
not need to be received.
In order to reduce memory traffic, the receive data path has a buffer of 68 bytes. The
Ethernet MAC will only start writing a frame to memory after 68 byte delays. If the RxAbort
signal is asserted during the initial 68 bytes of the frame, the frame can be discarded and
removed from the buffer and not stored to memory at all, not using up receive descriptors,
etc. If the RxAbort signal is asserted after the initial 68 bytes in a frame (probably due to
reception of a Magic Packet), part of the frame is already written to memory and the
Ethernet MAC will stop writing further data in the frame to memory; the FailFilter bit in the
status word of the frame will be set to indicate that the software device driver can discard
the frame immediately.

packet
AcceptUnicastEn
AcceptMulticastEn
StationAddress
IMPERFECT PERFECT
AcceptMulticastHashEn
HASH ADDRESS
AcceptPerfectEn
AcceptUnicastHashEn FILTER FILTER
HashFilter
PAReady
H FMatc h
PAMatch
HFReady
CRC
OK?
FMatch
RxFilterWoL
RxFilterEnWoL
RxAbort
FReady
Fig 38. Receive filter block diagram
Unicast, broadcast and multicast
Generic filtering based on the type of frame (unicast, multicast or broadcast) can be
programmed using the AcceptUnicastEn, AcceptMulticastEn, or AcceptBroadcastEn bits
of the RxFilterCtrl register. Setting the AcceptUnicast, AcceptMulticast, and
AcceptBroadcast bits causes all frames of types unicast, multicast and broadcast,
respectively, to be accepted, ignoring the Ethernet destination address in the frame. To
program promiscuous mode, i.e. to accept all frames, set all 3 bits to 1.
Perfect address match
When a frame with a unicast destination address is received, a perfect filter compares the
destination address with the 6 byte station address programmed in the station address
registers SA0, SA1, SA2. If the AcceptPerfectEn bit in the RxFilterCtrl register is set to 1,
and the address matches, the frame is accepted.
Imperfect hash filtering
An imperfect filter is available, based on a hash mechanism. This filter applies a hash
function to the destination address and uses the hash to access a table that indicates if
the frame should be accepted. The advantage of this type of filter is that a small table can
cover any possible address. The disadvantage is that the filtering is imperfect, i.e.
sometimes frames are accepted that should have been discarded.

• Hash function:
– The standard Ethernet cyclic redundancy check (CRC) function is calculated from
the 6 byte destination address in the Ethernet frame (this CRC is calculated
anyway as part of calculating the CRC of the whole frame), then bits [28:23] out of
the 32 bits CRC result are taken to form the hash. The 6 bit hash is used to access
the hash table: it is used as an index in the 64 bit HashFilter register that has been
programmed with accept values. If the selected accept value is 1, the frame is
accepted.
– The device driver can initialize the hash filter table by writing to the registers
HashFilterL and HashfilterH. HashFilterL contains bits 0 through 31 of the table
and HashFilterH contains bit 32 through 63 of the table. So, hash value 0
corresponds to bit 0 of the HashfilterL register and hash value 63 corresponds to
bit 31 of the HashFilterH register.
• Multicast and unicast
– The imperfect hash filter can be applied to multicast addresses, by setting the
AcceptMulticastHashEn bit in the RxFilter register to 1.
– The same imperfect hash filter that is available for multicast addresses can also be
used for unicast addresses. This is useful to be able to respond to a multitude of
unicast addresses without enabling all unicast addresses. The hash filter can be
applied to unicast addresses by setting the AcceptUnicastHashEn bit in the
RxFilter register to 1.
Enabling and disabling filtering
The filters as defined in the sections above can be bypassed by setting the PassRxFilter
bit in the Command register. When the PassRxFilter bit is set, all receive frames will be
passed to memory. In this case the device driver software has to implement all filtering
functionality in software. Setting the PassRxFilter bit does not affect the runt frame filtering
as defined in the next section.
Runt frames
A frame with less than 64 bytes (or 68 bytes for VLAN frames) is shorter than the
minimum Ethernet frame size and therefore considered erroneous; they might be collision
fragments. The receive data path automatically filters and discards these runt frames
without writing them to memory and using a receive descriptor.
When a runt frame has a correct CRC there is a possibility that it is intended to be useful.
The device driver can receive the runt frames with correct CRC by setting the
PassRuntFrame bit of the Command register to 1.
11.18.11 Power management

The Ethernet block supports power management by means of clock switching. All clocks
in the Ethernet core can be switched off. If Wake-up on LAN is needed, the rx_clk should
not be switched off.
11.18.12 Wake-up on LAN

Overview

The Ethernet block supports power management with remote wake-up over LAN. The
host system can be powered down, even including part of the Ethernet block itself, while
the Ethernet block continues to listen to packets on the LAN. Appropriately formed
packets can be received and recognized by the Ethernet block and used to trigger the
host system to wake up from its power-down state.
Wake-up of the system takes effect through an interrupt. When a wake-up event is
detected, the WakeupInt bit in the IntStatus register is set. The interrupt status will trigger
an interrupt if the corresponding WakeupIntEn bit in the IntEnable register is set. This
interrupt should be used by system power management logic to wake up the system.
While in a power-down state the packet that generates a Wake-up on LAN event is lost.
There are two ways in which Ethernet packets can trigger wake-up events: generic
Wake-up on LAN and Magic Packet. Magic Packet filtering uses an additional filter for
Magic Packet detection. In both cases a Wake-up on LAN event is only triggered if the
triggering packet has a valid CRC. Figure 38 shows the generation of the wake-up signal.
The RxFilterWoLStatus register can be read by the software to inspect the reason for a
Wake-up event. Before going to power-down the power management software should
clear the register by writing the RxFilterWolClear register.
NOTE: when entering in power-down mode, a receive frame might be not entirely stored
into the Rx buffer. In this situation, after turning exiting power-down mode, the next
receive frame is corrupted due to the data of the previous frame being added in front of
the last received frame. Software drivers have to reset the receive data path just after
exiting power-down mode.
The following subsections describe the two Wake-up on LAN mechanisms.
Filtering for WoL
The receive filter functionality can be used to generate Wake-up on LAN events. If the
RxFilterEnWoL bit of the RxFilterCtrl register is set, the receive filter will set the WakeupInt
bit of the IntStatus register if a frame is received that passes the filter. The interrupt will
only be generated if the CRC of the frame is correct.
Magic Packet WoL
The Ethernet block supports wake-up using Magic Packet technology (see ‘Magic Packet
technology’, Advanced Micro Devices). A Magic Packet is a specially formed packet solely
intended for wake-up purposes. This packet can be received, analyzed and recognized by
the Ethernet block and used to trigger a wake-up event.
A Magic Packet is a packet that contains in its data portion the station address repeated
16 times with no breaks or interruptions, preceded by 6 Magic Packet synchronization
bytes with the value 0xFF. Other data may be surrounding the Magic Packet pattern in the
data portion of the packet. The whole packet must be a well-formed Ethernet frame.
The magic packet detection unit analyzes the Ethernet packets, extracts the packet
address and checks the payload for the Magic Packet pattern. The address from the
packet is used for matching the pattern (not the address in the SA0/1/2 registers.) A magic
packet only sets the wake-up interrupt status bit if the packet passes the receive filter as
illustrated in Figure 38: the result of the receive filter is ANDed with the magic packet filter
result to produce the result.

Magic Packet filtering is enabled by setting the MagicPacketEnWoL bit of the RxFilterCtrl
register. Note that when doing Magic Packet WoL, the RxFilterEnWoL bit in the
RxFilterCtrl register should be 0. Setting the RxFilterEnWoL bit to 1 would accept all
packets for a matching address, not just the Magic Packets i.e. WoL using Magic Packets
is more strict.
When a magic packet is detected, apart from the WakeupInt bit in the IntStatus register,
the MagicPacketWoL bit is set in the RxFilterWoLStatus register. Software can reset the
bit writing a 1 to the corresponding bit of the RxFilterWoLClear register.
Example: An example of a Magic Packet with station address 0x11 0x22 0x33 0x44 0x55
0x66 is the following (MISC indicates miscellaneous additional data bytes in the packet):
<DESTINATION> <SOURCE> <MISC>

FF FF FF FF FF FF
11 22 33 44 55 66 11 22 33 44 55 66
11 22 33 44 55 66 11 22 33 44 55 66
11 22 33 44 55 66 11 22 33 44 55 66
11 22 33 44 55 66 11 22 33 44 55 66
11 22 33 44 55 66 11 22 33 44 55 66
11 22 33 44 55 66 11 22 33 44 55 66
11 22 33 44 55 66 11 22 33 44 55 66
11 22 33 44 55 66 11 22 33 44 55 66
<MISC> <CRC>
11.18.13 Enabling and disabling receive and transmit

Enabling and disabling reception
After reset, the receive function of the Ethernet block is disabled. The receive function can
be enabled by the device driver setting the RxEnable bit in the Command register and the
“RECEIVE ENABLE’ bit in the MAC1 configuration register (in that order).
The status of the receive data path can be monitored by the device driver by reading the
RxStatus bit of the Status register. Figure 39 illustrates the state machine for the
generation of the RxStatus bit.

ACTIVE
RxStatus = 1
xxxxxxxxxxxxxxxxxx
RxEnable = 0 and not busy receiving

RxEnable = 1 OR
RxProduceIndex = RxConsumeIndex - 1
INACTIVE
RxStatus = 0
reset
Fig 39. Receive Active/Inactive state machine
After a reset, the state machine is in the INACTIVE state. As soon as the RxEnable bit is
set in the Command register, the state machine transitions to the ACTIVE state. As soon
as the RxEnable bit is cleared, the state machine returns to the INACTIVE state. If the
receive data path is busy receiving a packet while the receive data path gets disabled, the
packet will be received completely, stored to memory along with its status before returning
to the INACTIVE state. Also if the Receive descriptor array is full, the state machine will
return to the INACTIVE state.
For the state machine in Figure 39, a soft reset is like a hardware reset assertion, i.e. after
a soft reset the receive data path is inactive until the data path is re-enabled.
Enabling and disabling transmission
After reset, the transmit function of the Ethernet block is disabled. The Tx transmit data
path can be enabled by the device driver setting the TxEnable bit in the Command
register to 1.
The status of the transmit data paths can be monitored by the device driver reading the
TxStatus bit of the Status register. Figure 40 illustrates the state machine for the
generation of the TxStatus bit.

ACTIVE
TxStatus = 1
xxxxxxxxxxxxxxxxxxxxxx
TxEnable = 1 TxEnable = 0 and not busy transmitting

AND OR
TxProduceIndex <> TxConsumeIndex TxProduceIndex = TxConsumeIndex
INACTIVE
TxStatus = 0
reset
Fig 40. Transmit Active/Inactive state machine
After reset, the state machine is in the INACTIVE state. As soon as the TxEnable bit is set
in the Command register and the Produce and Consume indices are not equal, the state
machine transitions to the ACTIVE state. As soon as the TxEnable bit is cleared and the
transmit data path has completed all pending transmissions, including committing the
transmission status to memory, the state machine returns to the INACTIVE state. The
state machine will also return to the INACTIVE state if the Produce and Consume indices
are equal again i.e. all frames have been transmitted.
For the state machine in Figure 40, a soft reset is like a hardware reset assertion, i.e. after
a soft reset the transmit data path is inactive until the data path is re-enabled.
11.18.14 Transmission padding and CRC

In the case of a frame of less than 60 bytes (or 64 bytes for VLAN frames), the Ethernet
block can pad the frame to 64 or 68 bytes including a 4 bytes CRC Frame Check
Sequence (FCS). Padding is affected by the value of the ‘AUTO DETECT PAD ENABLE’
(ADPEN), ‘VLAN PAD ENABLE’ (VLPEN) and ‘PAD/CRC ENABLE’ (PADEN) bits of the
MAC2 configuration register, as well as the Override and Pad bits from the transmit
descriptor Control word. CRC generation is affected by the ‘CRC ENABLE’ (CRCE) and
‘DELAYED CRC’ (DCRC) bits of the MAC2 configuration register, and the Override and
CRC bits from the transmit descriptor Control word.
The effective pad enable (EPADEN) is equal to the ‘PAD/CRC ENABLE’ bit from the
MAC2 register if the Override bit in the descriptor is 0. If the Override bit is 1, then
EPADEN will be taken from the descriptor Pad bit. Likewise the effective CRC enable
(ECRCE) equals CRCE if the Override bit is 0, otherwise it equal the CRC bit from the
descriptor.
If padding is required and enabled, a CRC will always be appended to the padded frames.
A CRC will only be appended to the non-padded frames if ECRCE is set.
If EPADEN is 0, the frame will not be padded and no CRC will be added unless ECRCE is
set.

If EPADEN is 1, then small frames will be padded and a CRC will always be added to the
padded frames. In this case if ADPEN and VLPEN are both 0, then the frames will be
padded to 60 bytes and a CRC will be added creating 64 bytes frames; if VLPEN is 1, the
frames will be padded to 64 bytes and a CRC will be added creating 68 bytes frames; if
ADPEN is 1, while VLPEN is 0 VLAN frames will be padded to 64 bytes, non VLAN
frames will be padded to 60 bytes, and a CRC will be added to padded frames, creating
64 or 68 bytes padded frames.
If CRC generation is enabled, CRC generation can be delayed by four bytes by setting the
DELAYED CRC bit in the MAC2 register, in order to skip proprietary header information.
11.18.15 Huge frames and frame length checking

The ‘HUGE FRAME ENABLE’ bit in the MAC2 configuration register can be set to 1 to
enable transmission and reception of frames of any length. Huge frame transmission can
be enabled on a per frame basis by setting the Override and Huge bits in the transmit
descriptor Control word.
When enabling huge frames, the Ethernet block will not check frame lengths and report
frame length errors (RangeError and LengthError). If huge frames are enabled, the
received byte count in the RSV register may be invalid because the frame may exceed the
maximum size; the RxSize fields from the receive status arrays will be valid.
Frame lengths are checked by comparing the length/type field of the frame to the actual
number of bytes in the frame. A LengthError is reported by setting the corresponding bit in
the receive StatusInfo word.
The MAXF register allows the device driver to specify the maximum number of bytes in a
frame. The Ethernet block will compare the actual receive frame to the MAXF value and
report a RangeError in the receive StatusInfo word if the frame is larger.
11.18.16 Statistics counters

Generally, Ethernet applications maintain many counters that track Ethernet traffic
statistics. There are a number of standards specifying such counters, such as IEEE std
802.3 / clause 30. Other standards are RFC 2665 and RFC 2233.
The approach taken here is that by default all counters are implemented in software. With
the help of the StatusInfo field in frame statuses, many of the important statistics events
listed in the standards can be counted by software.
11.18.17 MAC status vectors

Transmit and receive status information as detected by the MAC are available in registers
TSV0, TSV1 and RSV so that software can poll them. These registers are normally of
limited use because the communication between driver software and the Ethernet block
takes place primarily through frame descriptors. Statistical events can be counted by
software in the device driver. However, for debug purposes the transmit and receive status
vectors are made visible. They are valid as long as the internal status of the MAC is valid
and should typically only be read when the transmit and receive processes are halted.

11.18.18 Reset
The Ethernet block has a hard reset input which is connected to the chip reset, as well as
several soft resets which can be activated by setting the appropriate bits in registers. All
registers in the Ethernet block have a value of 0 after a hard reset, unless otherwise
specified.
Hard reset
After a hard reset, all registers will be set to their default value.
Soft reset
Parts of the Ethernet block can be soft reset by setting bits in the Command register and
the MAC1 configuration register.The MAC1 register has six different reset bits:
• SOFT RESET: Setting this bit will put all modules in the MAC in reset, except for the
MAC registers (at addresses 0x000 to 0x0FC). The value of the soft reset after a
hardware reset assertion is 1, i.e. the soft reset needs to be cleared after a hardware
reset.
• SIMULATION RESET: Resets the random number generator in the Transmit

Function. The value after a hardware reset assertion is 0.
• RESET MCS/Rx: Setting this bit will reset the MAC Control Sublayer (pause frame
logic) and the receive function in the MAC. The value after a hardware reset assertion
is 0.
• RESET Rx: Setting this bit will reset the receive function in the MAC. The value after a
hardware reset assertion is 0.
• RESET MCS/Tx: Setting this bit will reset the MAC Control Sublayer (pause frame
logic) and the transmit function in the MAC. The value after a hardware reset
assertion is 0.
• RESET Tx: Setting this bit will reset the transmit function of the MAC. The value after
a hardware reset assertion is 0.
The above reset bits must be cleared by software.
The Command register has three different reset bits:
• TxReset: Writing a ‘1’ to the TxReset bit will reset the transmit data path, excluding the
MAC portions, including all (read-only) registers in the transmit data path, as well as
the TxProduceIndex register in the host registers module. A soft reset of the transmit
data path will abort all AHB transactions of the transmit data path. The reset bit will be
cleared autonomously by the Ethernet block. A soft reset of the Tx data path will clear
the TxStatus bit in the Status register.
• RxReset: Writing a ‘1’ to the RxReset bit will reset the receive data path, excluding the
MAC portions, including all (read-only) registers in the receive data path, as well as
the RxConsumeIndex register in the host registers module. A soft reset of the receive
data path will abort all AHB transactions of the receive data path. The reset bit will be
cleared autonomously by the Ethernet block. A soft reset of the Rx data path will clear
the RxStatus bit in the Status register.

• RegReset: Resets all of the data paths and registers in the host registers module,
excluding the registers in the MAC. A soft reset of the registers will also abort all AHB
transactions of the transmit and receive data path. The reset bit will be cleared
autonomously by the Ethernet block.
To do a full soft reset of the Ethernet block, device driver software must:
• Set the ‘SOFT RESET’ bit in the MAC1 register to 1.

• Set the RegReset bit in the Command register, this bit clears automatically.
• Reinitialize the MAC registers (0x000 to 0x0FC).
• Reset the ‘SOFT RESET’ bit in the MAC1 register to 0.
To reset just the transmit data path, the device driver software has to:
• Set the ‘RESET MCS/Tx’ bit in the MAC1 register to 1.

• Disable the Tx DMA managers by setting the TxEnable bits in the Command register
to 0.
• Set the TxReset bit in the Command register, this bit clears automatically.
• Reset the ‘RESET MCS/Tx’ bit in the MAC1 register to 0.
To reset just the receive data path, the device driver software has to:
• Disable the receive function by resetting the ‘RECEIVE ENABLE’ bit in the MAC1
configuration register and resetting of the RxEnable bit of the Command register.
• Set the ‘RESET MCS/Rx’ bit in the MAC1 register to 1.
• Set the RxReset bit in the Command register, this bit clears automatically.
• Reset the ‘RESET MCS/Rx’ bit in the MAC1 register to 0.
11.18.19 Ethernet errors

The Ethernet block generates errors for the following conditions:
• A reception can cause an error: AlignmentError, RangeError, LengthError,

SymbolError, CRCError, NoDescriptor, or Overrun. These are reported back in the
receive StatusInfo and in the interrupt status register (IntStatus).
• A transmission can cause an error: LateCollision, ExcessiveCollision,
ExcessiveDefer, NoDescriptor, or Underrun. These are reported back in the
transmission StatusInfo and in the interrupt status register (IntStatus).
11.19 AHB bandwidth

The Ethernet block is connected to an AHB bus which must carry all of the data and
control information associated with all Ethernet traffic in addition to the CPU accesses
required to operate the Ethernet block and deal with message contents.
11.19.1 DMA access

Assumptions

By making some assumptions, the bandwidth needed for each type of AHB transfer can
be calculated and added in order to find the overall bandwidth requirement.
The flexibility of the descriptors used in the Ethernet block allows the possibility of defining
memory buffers in a range of sizes. In order to analyze bus bandwidth requirements,
some assumptions must be made about these buffers. The "worst case" is not addressed
since that would involve all descriptors pointing to single byte buffers, with most of the
memory occupied in holding descriptors and very little data. It can easily be shown that
the AHB cannot handle the huge amount of bus traffic that would be caused by such a
degenerate (and illogical) case.
For this analysis, an Ethernet packet is assumed to consist of a 64 byte frame.

Continuous traffic is assumed on both the transmit and receive channels.
This analysis does not reflect the flow of Ethernet traffic over time, which would include
inter-packet gaps in both the transmit and receive channels that reduce the bandwidth
requirements over a larger time frame.
Types of DMA access and their bandwidth requirements
The interface to an external Ethernet PHY is via RMII. RMII operates at 50 MHz,
transferring a byte in 4 clock cycles. The data transfer rate is 12.5 Mbps.
The Ethernet block initiates DMA accesses for the following cases:
• Tx descriptor read:
– Transmit descriptors occupy 2 words (8 bytes) of memory and are read once for
each use of a descriptor.
– Two word read happens once every 64 bytes (16 words) of transmitted data.
– This gives 1/8th of the data rate, which = 1.5625 Mbps.
• Rx descriptor read:
– Receive descriptors occupy 2 words (8 bytes) of memory and are read once for
each use of a descriptor.
– Two word read happens once every 64 bytes (16 words) of received data.
• Tx status write:
– Transmit status occupies 1 word (4 bytes) of memory and is written once for each
use of a descriptor.
– One word write happens once every 64 bytes (16 words) of transmitted data.
• Rx status write:
– Receive status occupies 2 words (8 bytes) of memory and is written once for each
use of a descriptor.
– Two word write happens once every 64 bytes (16 words) of received data.
– This gives 1/8 of the data rate, which = 1.5625 Mbps.
• Tx data read:
– Data transmitted in an Ethernet frame, the size is variable.
– Basic Ethernet rate = 12.5 Mbps.

• Rx data write:
– Data to be received in an Ethernet frame, the size is variable.
– Basic Ethernet rate = 12.5 Mbps.
This gives a total rate of 30.5 Mbps for the traffic generated by the Ethernet DMA function.
11.19.2 Types of CPU access

• Accesses that mirror each of the DMA access types:
– All or part of status values must be read, and all or part of descriptors need to be
written after each use, transmitted data must be stored in the memory by the CPU,
and eventually received data must be retrieved from the memory by the CPU.
– This gives roughly the same or slightly lower rate as the combined DMA functions,
which = 30.5 Mbps.
• Access to registers in the Ethernet block:
– The CPU must read the RxProduceIndex, TxConsumeIndex, and IntStatus
registers, and both read and write the RxConsumeIndex and TxProduceIndex
registers.
– 7 word read/writes once every 64 bytes (16 words) of transmitted and received
data.
– This gives 7/16 of the data rate, which = 5.4688 Mbps.
This gives a total rate of 36 Mbps for the traffic generated by the Ethernet DMA function.
11.19.3 Overall bandwidth

Overall traffic on the AHB is the sum of DMA access rates and CPU access rates, which
comes to approximately 66.5 MB/s.
The peak bandwidth requirement can be somewhat higher due to the use of small
memory buffers, in order to hold often used addresses (e.g. the station address) for
example. Driver software can determine how to build frames in an efficient manner that
does not overutilize the AHB.
The bandwidth available on the AHB bus depends on the system clock frequency. As an
example, assume that the system clock is set at 60 MHz. All or nearly all of bus accesses
related to the Ethernet will be word transfers. The raw AHB bandwidth can be
approximated as 4 bytes per two system clocks, which equals 2 times the system clock
rate. With a 60 MHz system clock, the bandwidth is 120 MB/s, giving about 55% utilization
for Ethernet traffic during simultaneous transmit and receive operations.
11.20 CRC calculation

The calculation is used for several purposes:
• Generation the FCS at the end of the Ethernet frame.

• Generation of the hash table index for the hash table filtering.
• Generation of the destination and source address hash CRCs.

The C pseudocode function below calculates the CRC on a frame taking the frame
(without FCS) and the number of bytes in the frame as arguments. The function returns
the CRC as a 32 bit integer.
int crc_calc(char frame_no_fcs[], int frame_len) {

int i; // iterator
int j; // another iterator
char byte; // current byte
int crc; // CRC result
int q0, q1, q2, q3; // temporary variables
crc = 0xFFFFFFFF;
for (i = 0; i < frame_len; i++) {
byte = *frame_no_fcs++;
for (j = 0; j < 2; j++) {
if (((crc >> 28) ^ (byte >> 3)) & 0x00000001) {
q3 = 0x04C11DB7;
} else {
q3 = 0x00000000;
}
if (((crc >> 29) ^ (byte >> 2)) & 0x00000001) {
q2 = 0x09823B6E;
} else {
q2 = 0x00000000;
}
if (((crc >> 30) ^ (byte >> 1)) & 0x00000001) {
q1 = 0x130476DC;
} else {
q1 = 0x00000000;
}
if (((crc >> 31) ^ (byte >> 0)) & 0x00000001) {
q0 = 0x2608EDB8;
} else {
q0 = 0x00000000;
}
crc = (crc << 4) ^ q3 ^ q2 ^ q1 ^ q0;
byte >>= 4;
}
}
return crc;
}
For FCS calculation, this function is passed a pointer to the first byte of the frame and the
length of the frame without the FCS.
For hash filtering, this function is passed a pointer to the destination address part of the
frame and the CRC is only calculated on the 6 address bytes. The hash filter uses bits
[28:23] for indexing the 64 bits {HashFilterH, HashFilterL } vector. If the corresponding bit
is set the packet is passed, otherwise it is rejected by the hash filter.

For obtaining the destination and source address hash CRCs, this function calculates first
both the 32 bit CRCs, then the nine most significant bits from each 32 bit CRC are
extracted, concatenated, and written in every StatusHashCRC word of every fragment
status.

UM10211
Chapter 12: LPC23XX CAN controllers CAN1/2

This chapter describes the CAN controllers for the following LPC23XX parts:
• LPC2361/62
• LPC2364/66/68
• LPC2378
• LPC2387
• LPC2388
LPC2365/67 and LPC2377 do not include CAN controllers.

The CAN1/2 peripherals are configured using the following registers:
1. Power: In the PCONP register (Table 56), set bits PCAN1/2.

Remark: On reset, the CAN1/2 blocks are disabled (PCAN1/2 = 0).
2. Peripheral clock: In the PCLK_SEL0 register (Table 49), select PCLK_CAN1/2 and,
for the acceptance filter, PCLK_ACF. PCLK_CAN1/2 and PCLK_ACF must be set to
the same value.
Remark: If CAN baudrates above 100 kbit/s (see Table 226) are needed, do not
select the IRC as the clock source (see Table 35).
3. Wake-up: Use the INTWAKE register (Table 55) to enable the CAN controllers to
wake up the microcontroller from Power-down mode.
4. Pins: Select CAN1/2 pins and pin modes in registers PINSELn and PINMODEn (see
Section 9.5).
5. Interrupts: CAN interrupts are enabled using the CAN1/2IER registers (Table 225).
Interrupts are enabled in the VIC using the VICIntEnable register (Table 76).
6. CAN controller initialization: see CANMOD register (Table 221).
12.3 Introduction
Controller Area Network (CAN) is the definition of a high performance communication
protocol for serial data communication. The CAN Controller is designed to provide a full
implementation of the CAN-Protocol according to the CAN Specification Version 2.0B.
Microcontrollers with this on-chip CAN controller are used to build powerful local networks
by supporting distributed real-time control with a very high level of security. The
applications are automotive, industrial environments, and high speed networks as well as
low cost multiplex wiring. The result is a strongly reduced wiring harness and enhanced
diagnostic and supervisory capabilities.

The CAN block is intended to support multiple CAN buses simultaneously, allowing the
device to be used as a gateway, switch, or router among a number of CAN buses in
various applications.
The CAN module consists of two elements: the controller and the Acceptance Filter. All
registers and the RAM are accessed as 32 bit words.
12.4 Features
12.4.1 General CAN features

• Compatible with CAN specification 2.0B, ISO 11898-1.
• Multi-master architecture with non destructive bit-wise arbitration.
• Bus access priority determined by the message identifier (11-bit or 29-bit).
• Guaranteed latency time for high priority messages.
• Programmable transfer rate (up to 1 Mbit/s).
• Multicast and broadcast message facility.
• Data length from 0 up to 8 bytes.
• Powerful error handling capability.
• Non-return-to-zero (NRZ) coding/decoding with bit stuffing.
12.4.2 CAN controller features

• 2 CAN controllers and buses.
• Supports 11-bit identifier as well as 29-bit identifier.
• Double Receive Buffer and Triple Transmit Buffer.
• Programmable Error Warning Limit and Error Counters with read/write access.
• Arbitration Lost Capture and Error Code Capture with detailed bit position.
• Single Shot Transmission (no re-transmission).
• Listen Only Mode (no acknowledge, no active error flags).
• Reception of "own" messages (Self Reception Request).
12.4.3 Acceptance filter features

• Fast hardware implemented search algorithm supporting a large number of CAN
identifiers.
• Global Acceptance Filter recognizes 11 and 29 bit Rx Identifiers for all CAN buses.
• Allows definition of explicit and groups for 11-bit and 29-bit CAN identifiers.
• Acceptance Filter can provide FullCAN-style automatic reception for selected
Standard Identifiers.


Table 215. CAN Pin descriptions
RD2/1 Inputs Serial Inputs. From CAN transceivers.
TD2/1 Outputs Serial Outputs. To CAN transceivers.
12.6 CAN controller architecture

The CAN Controller is a complete serial interface with both Transmit and Receive Buffers
but without Acceptance Filter. CAN Identifier filtering is done for all CAN channels in a
separate block (Acceptance Filter). Except for message buffering and acceptance filtering
the functionality is similar to the PeliCAN concept.
The CAN Controller Block includes interfaces to the following blocks:
• APB Interface
• Acceptance Filter
• Vectored Interrupt Controller (VIC)
• CAN Transceiver
• Common Status Registers
INTERFACE CAN CORE

APB BUS
MANAGEMENT BLOCK
LOGIC
TX
ERROR CAN
RX
MANAGEMENT TRANSCEIVER
VIC LOGIC
TRANSMIT
BUFFERS 1,2
AND 3 BIT
COMMON
TIMING
STATUS
LOGIC
REGISTER
BIT
RECEIVE
ACCEPTANCE STREAM
BUFFERS 1
FILTER PROCESSOR
AND 2
Fig 41. CAN controller block diagram
12.6.1 APB interface block (AIB)

The APB Interface Block provides access to all CAN Controller registers.

12.6.2 Interface management logic (IML)

The Interface Management Logic interprets commands from the CPU, controls internal
addressing of the CAN Registers and provides interrupts and status information to the
CPU.
12.6.3 Transmit Buffers (TXB)

The TXB represents a Triple Transmit Buffer, which is the interface between the Interface
Management Logic (IML) and the Bit Stream Processor (BSP). Each Transmit Buffer is
able to store a complete message which can be transmitted over the CAN network. This
buffer is written by the CPU and read out by the BSP.
INTERFACE CAN CORE

APB BUS
MANAGEMENT BLOCK
LOGIC
TX
ERROR CAN
RX
MANAGEMENT TRANSCEIVER
VIC LOGIC
TRANSMIT
BUFFERS 1,2
AND 3 BIT
COMMON
TIMING
STATUS
LOGIC
REGISTER
BIT
RECEIVE
ACCEPTANCE STREAM
BUFFERS 1
FILTER PROCESSOR
AND 2
Fig 42. Transmit buffer layout for standard and extended frame format configurations
12.6.4 Receive Buffer (RXB)

The Receive Buffer (RXB) represents a CPU accessible Double Receive Buffer. It is
located between the CAN Controller Core Block and APB Interface Block and stores all
received messages from the CAN Bus line. With the help of this Double Receive Buffer
concept the CPU is able to process one message while another message is being
received.
The global layout of the Receive Buffer is very similar to the Transmit Buffer described
earlier. Identifier, Frame Format, Remote Transmission Request bit and Data Length
Code have the same meaning as described for the Transmit Buffer. In addition, the
Receive Buffer includes an ID Index field (see Section 12.8.9.1 “ID index field”).
The received Data Length Code represents the real transmitted Data Length Code, which
may be greater than 8 depending on transmitting CAN node. Nevertheless, the maximum
number of received data bytes is 8. This should be taken into account by reading a

message from the Receive Buffer. If there is not enough space for a new message within
the Receive Buffer, the CAN Controller generates a Data Overrun condition when this
message becomes valid and the acceptance test was positive. A message that is partly
written into the Receive Buffer (when the Data Overrun situation occurs) is deleted. This
situation is signalled to the CPU via the Status Register and the Data Overrun Interrupt, if
enabled.
31 24 23 16 15 10 9 8 7 0
RX Frame info unused RX DLC unused ID Index RFS

Descriptor
Field
unused ID.28 ... ID.18 RID
RX Data 4 RX Data 3 RX Data 2 RX Data 1 RDA

Data Field
RX Data 8 RX Data 7 RX Data 6 RX Data 5 RDB
Standard Frame Format (11-bit Identifier) BPM=bypass

message
31 24 23 16 15 10 9 8 7 0
RX Frame info unused RX DLC unused ID Index RFS

Descriptor
Field
unused ID.28 ... ID.00 RID
RX Data 4 RX Data 3 RX Data 2 RX Data 1 RDA

Data Field
RX Data 8 RX Data 7 RX Data 6 RX Data 5 RDB
Extended Frame Format (29-bit Identifier)
Fig 43. Receive buffer layout for standard and extended frame format configurations
12.6.5 Error Management Logic (EML)

The EML is responsible for the error confinement. It gets error announcements from the
BSP and then informs the BSP and IML about error statistics.
12.6.6 Bit Timing Logic (BTL)

The Bit Timing Logic monitors the serial CAN Bus line and handles the Bus line related bit
timing. It synchronizes to the bit stream on the CAN Bus on a "recessive" to "dominant"
Bus line transition at the beginning of a message (hard synchronization) and
re-synchronizes on further transitions during the reception of a message (soft
synchronization). The BTL also provides programmable time segments to compensate for
the propagation delay times and phase shifts (e.g. due to oscillator drifts) and to define the
sample point and the number of samples to be taken within a bit time.
12.6.7 Bit Stream Processor (BSP)

The Bit Stream Processor is a sequencer, controlling the data stream between the
Transmit Buffer, Receive Buffers and the CAN Bus. It also performs the error detection,
arbitration, stuffing and error handling on the CAN Bus.

12.6.8 CAN controller self-tests

The CAN controller of the LPC2000 family supports two different options for self-tests:
• Global Self-Test (setting the self reception request bit in normal Operating Mode)
• Local Self-Test (setting the self reception request bit in Self Test Mode)
Both self-tests are using the ‘Self Reception’ feature of the CAN Controller. With the Self
Reception Request, the transmitted message is also received and stored in the receive
buffer. Therefore the acceptance filter has to be configured accordingly. As soon as the
CAN message is transmitted, a transmit and a receive interrupt are generated, if enabled.
Global self test

A Global Self-Test can for example be used to verify the chosen configuration of the CAN
Controller in a given CAN system. As shown in Figure 44, at least one other CAN node,
which is acknowledging each CAN message has to be connected to the CAN bus.
TX
TXBuffer
Buffer CAN Bus
TX Buffer
LPC23xx Transceiver
ack
RX Buffer
Fig 44. Global Self-Test (high-speed CAN Bus example)
Initiating a Global Self-Test is similar to a normal CAN transmission. In this case the
transmission of a CAN message(s) is initiated by setting Self Reception Request bit
(SRR) in conjunction with the selected Message Buffer bits (STB3, STB2, STB1) in the
CAN Controller Command register (CANCMR).
Local self test

The Local Self-Test perfectly fits for single node tests. In this case an acknowledge from
other nodes is not needed. As shown in the Figure below, a CAN transceiver with an
appropriate CAN bus termination has to be connected to the LPC. The CAN Controller
has to be put into the 'Self Test Mode' by setting the STM bit in the CAN Controller Mode
register (CANMOD). Hint: Setting the Self Test Mode bit (STM) is possible only when the
CAN Controller is in Reset Mode.

TX
TXBuffer
TXBuffer
Buffer
LPC23xx Transceiver
RX Buffer
Fig 45. Local Self-Test (high-speed CAN Bus example)
A message transmission is initiated by setting Self Reception Request bit (SRR) in

conjunction with the selected Message Buffer(s) (STB3, STB2, STB1).
12.7 Memory map of the CAN block

The CAN Controllers and Acceptance Filter occupy a number of APB slots, as follows:
Table 216. Memory Map of the CAN Block

Address Range Used for
0xE003 8000 - 0xE003 87FF Acceptance Filter RAM.
0xE003 C000 - 0xE003 C017 Acceptance Filter Registers.
0xE004 0000 - 0xE004 000B Central CAN Registers.
0xE004 4000 - 0xE004 405F CAN Controller 1 Registers.
0xE004 8000 - 0xE004 805F CAN Controller 2 Registers.
12.8 CAN controller registers

CAN block implements the registers shown in Table 217 and Table 218. More detailed
descriptions follow.
Table 217. CAN acceptance filter and central CAN registers

Name Description Access Reset Value Address
AFMR Acceptance Filter Register R/W 1 0xE003 C000
SFF_sa Standard Frame Individual Start Address Register R/W 0 0xE003 C004
SFF_GRP_sa Standard Frame Group Start Address Register R/W 0 0xE003 C008
EFF_sa Extended Frame Start Address Register R/W 0 0xE003 C00C
EFF_GRP_sa Extended Frame Group Start Address Register R/W 0 0xE003 C010
ENDofTable End of AF Tables register R/W 0 0xE003 C014
LUTerrAd LUT Error Address register RO 0 0xE003 C018
LUTerr LUT Error Register RO 0 0xE003 C01C
FCANIE FullCAN interrupt enable register R/W 0 0xE003 C020
FCANIC0 FullCAN interrupt and capture register 0 R/W 0 0xE003 C024
FCANIC1 FullCAN interrupt and capture register 1 R/W 0 0xE003 C028

Table 217. CAN acceptance filter and central CAN registers

CANTxSR CAN Central Transmit Status Register RO 0x0003 0300 0xE004 0000
CANRxSR CAN Central Receive Status Register RO 0 0xE004 0004
CANMSR CAN Central Miscellaneous Register RO 0 0xE004 0008
Table 218. CAN1 and CAN2 controller register map

Generic Description Access CAN1 Register CAN2 Register
Name Address & Name Address & Name
MOD Controls the operating mode of the CAN R/W CAN1MOD - 0xE004 4000 CAN2MOD - 0xE004 8000
Controller.
CMR Command bits that affect the state of the WO CAN1CMR - 0xE004 4004 CAN2CMR - 0xE004 8004
CAN Controller
GSR Global Controller Status and Error Counters RO[1] CAN1GSR - 0xE004 4008 CAN2GSR - 0xE004 8008
ICR Interrupt status, Arbitration Lost Capture, RO CAN1ICR - 0xE004 400C CAN2ICR - 0xE004 800C
Error Code Capture
IER Interrupt Enable R/W CAN1IER - 0xE004 4010 CAN2IER - 0xE004 8010
BTR Bus Timing R/W[2] CAN1BTR - 0xE004 4014 CAN2BTR - 0xE004 8014
EWL Error Warning Limit R/W[2] CAN1EWL - 0xE004 4018 CAN2EWL - 0xE004 8018
SR Status Register RO CAN1SR - 0xE004 401C CAN2SR - 0xE004 801C
RFS Receive frame status R/W[2] CAN1RFS - 0xE004 4020 CAN2RFS - 0xE004 8020
RID Received Identifier R/W[2] CAN1RID - 0xE004 4024 CAN2RID - 0xE004 8024
RDA Received data bytes 1-4 R/W[2] CAN1RDA - 0xE004 4028 CAN2RDA - 0xE004 8028
RDB Received data bytes 5-8 R/W[2] CAN1RDB - 0xE004 402C CAN2RDB - 0xE004 802C
TFI1 Transmit frame info (Tx Buffer 1) R/W CAN1TFI1 - 0xE004 4030 CAN2TFI1 - 0xE004 8030
TID1 Transmit Identifier (Tx Buffer 1) R/W CAN1TID1 - 0xE004 4034 CAN2TID1 - 0xE004 8034
TDA1 Transmit data bytes 1-4 (Tx Buffer 1) R/W CAN1TDA1 - 0xE004 4038 CAN2TDA1 - 0xE004 8038
TDB1 Transmit data bytes 5-8 (Tx Buffer 1) R/W CAN1TDB1- 0xE004 403C CAN1TDB1 - 0xE004 403C
CAN2TDB1- 0xE004 803C CAN2TDB1 - 0xE004 803C
CAN2TFI2 - 0xE004 8040 CAN2TFI2 - 0xE004 8040
CAN2TID2 - 0xE004 8044 CAN2TID2 - 0xE004 8044
CAN2TDA2 - 0xE004 8048 CAN2TDA2 - 0xE004 8048
TDB2 Transmit data bytes 5-8 (Tx Buffer 2) R/W CAN1TDB2 - 0xE004 404C CAN1TDB2 - 0xE004 404C
CAN2TDB2 - 0xE004 804C CAN2TDB2 - 0xE004 804C
CAN2TFI3 - 0xE004 8050 CAN2TFI3 - 0xE004 8050
CAN2TID3 - 0xE004 8054 CAN2TID3 - 0xE004 8054
CAN2TDA3 - 0xE004 8058 CAN2TDA3 - 0xE004 8058
TDB3 Transmit data bytes 5-8 (Tx Buffer 3) R/W CAN1TDB3 - 0xE004 405C CAN1TDB3 - 0xE004 405C
CAN2TDB3 - 0xE004 805C CAN2TDB3 - 0xE004 805C
[1] The error counters can only be written when RM in CANMOD is 1.

[2] These registers can only be written when RM in CANMOD is 1.
The internal registers of each CAN Controller appear to the CPU as on-chip memory
mapped peripheral registers. Because the CAN Controller can operate in different modes
(Operating/Reset, see also Section 12.8.1 “Mode Register (CAN1MOD - 0xE004 4000,
CAN2MOD - 0xE004 8000)”), one has to distinguish between different internal address
definitions. Note that write access to some registers is only allowed in Reset Mode.
Table 219. CAN1 and CAN2 controller register map

Generic Operating Mode Reset Mode
Name Read Write Read Write
MOD Mode Mode Mode Mode
CMR 0x00 Command 0x00 Command
GSR Global Status and Error - Global Status and Error Error Counters only
Counters Counters
ICR Interrupt and Capture - Interrupt and Capture -
IER Interrupt Enable Interrupt Enable Interrupt Enable Interrupt Enable
BTR Bus Timing - Bus Timing Bus Timing
EWL Error Warning Limit - Error Warning Limit Error Warning Limit
SR Status - Status -
RFS Rx Info and Index - Rx Info and Index Rx Info and Index
RID Rx Identifier - Rx Identifier Rx Identifier
RDA Rx Data - Rx Data Rx Data
RDB Rx Info and Index - Rx Info and Index Rx Info and Index
TFI1 Tx Info1 Tx Info Tx Info Tx Info
TID1 Tx Identifier Tx Identifier Tx Identifier Tx Identifier
TDA1 Tx Data Tx Data Tx Data Tx Data
TDB1 Tx Data Tx Data Tx Data Tx Data
Table 220. CAN Wake and Sleep registers

CANSLEEPCLR Allows clearing the current CAN channel sleep state as well as R/W 0 0x400F C110
reading that state.
CANWAKEFLAGS Allows reading the wake-up state of the CAN channels. R/W 0 0x400F C114
In the following register tables, the column “Reset Value” shows how a hardware reset
affects each bit or field, while the column “RM Set” indicates how each bit or field is
affected if software sets the RM bit, or RM is set because of a Bus-Off condition. Note that
while hardware reset sets RM, in this case the setting noted in the “Reset Value” column
prevails over that shown in the “RM Set” column, in the few bits where they differ. In both
columns, X indicates the bit or field is unchanged.
12.8.1 Mode Register (CAN1MOD - 0xE004 4000, CAN2MOD - 0xE004 8000)

The contents of the Mode Register are used to change the behavior of the CAN
Controller. Bits may be set or reset by the CPU that uses the Mode Register as a
read/write memory. Reserved Bits are read as 0 and should be written as 0.

Table 221. Mode register (CAN1MOD - address 0xE004 4000, CAN2MOD - address 0xE004 8000) bit description
Bit Symbol Value Function Reset RM
Value Set
0 RM[1][6] Reset Mode. 1 1
0(normal) The CAN Controller is in the Operating Mode, and certain registers can not be
written.
1(reset) CAN operation is disabled, writable registers can be written and the current
transmission/reception of a message is aborted.
1 LOM[3][2] Listen Only Mode. 0 x
[6]
0(normal) The CAN controller acknowledges a successfully received message on the
CAN bus. The error counters are stopped at the current value.
1(listen only) The controller gives no acknowledgment, even if a message is successfully
received. Messages cannot be sent, and the controller operates in “error
passive” mode. This mode is intended for software bit rate detection and “hot
plugging”.
2 STM[3][6] Self Test Mode. 0 x
0(normal) A transmitted message must be acknowledged to be considered successful.
1(self test) The controller will consider a Tx message successful even if there is no
acknowledgment received.
In this mode a full node test is possible without any other active node on the bus
using the SRR bit in CANxCMR.
3 TPM[4] Transmit Priority Mode. 0 x
0(CAN ID) The transmit priority for 3 Transmit Buffers depends on the CAN Identifier.
1(local prio) The transmit priority for 3 Transmit Buffers depends on the contents of the Tx
Priority register within the Transmit Buffer.
4 SM[5] Sleep Mode. 0 0
0(wake-up) Normal operation.
1(sleep) The CAN controller enters Sleep Mode if no CAN interrupt is pending and there
is no bus activity. See the Sleep Mode description Section 12.9.2 on page 287.
5 RPM Receive Polarity Mode. 0 x
0(low active) RD input is active Low (dominant bit = 0).
1(high active) RD input is active High (dominant bit = 1) -- reverse polarity.
6 - - Reserved, user software should not write ones to reserved bits. 0 0
7 TM Test Mode. 0 x
0(disabled) Normal operation.
1(enabled) The TD pin will reflect the bit, detected on RD pin, with the next positive edge of
the system clock.
[1] During a Hardware reset or when the Bus Status bit is set '1' (Bus-Off), the Reset Mode bit is set '1' (present). After the Reset Mode bit
is set '0' the CAN Controller will wait for:
- one occurrence of Bus-Free signal (11 recessive bits), if the preceding reset has been caused by a Hardware reset or a CPU-initiated
reset.
- 128 occurrences of Bus-Free, if the preceding reset has been caused by a CAN Controller initiated Bus-Off, before re-entering the
Bus-On mode.
[2] This mode of operation forces the CAN Controller to be error passive. Message Transmission is not possible. The Listen Only Mode can
be used e.g. for software driven bit rate detection and "hot plugging".
[3] A write access to the bits MOD.1 and MOD.2 is possible only if the Reset Mode is entered previously.
[4] Transmit Priority Mode is explained in more detail in Section 12.6.3 “Transmit Buffers (TXB)”.

[5] The CAN Controller will enter Sleep Mode, if the Sleep Mode bit is set '1' (sleep), there is no bus activity, and none of the CAN interrupts
is pending. Setting of SM with at least one of the previously mentioned exceptions valid will result in a wake-up interrupt. The CAN
Controller will wake up if SM is set LOW (wake-up) or there is bus activity. On wake-up, a Wake-up Interrupt is generated. A sleeping
CAN Controller which wakes up due to bus activity will not be able to receive this message until it detects 11 consecutive recessive bits
(Bus-Free sequence). Note that setting of SM is not possible in Reset Mode. After clearing of Reset Mode, setting of SM is possible only
when Bus-Free is detected again.
[6] The LOM and STM bits can only be written if the RM bit is 1 prior to the write operation.
12.8.2 Command Register (CAN1CMR - 0xE004 x004, CAN2CMR -

0xE004 8004)
Writing to this write-only register initiates an action within the transfer layer of the CAN
Controller. Bits not listed should be written as 0. Reading this register yields zeroes.
At least one internal clock cycle is needed for processing between two commands.
Table 222. Command Register (CAN1CMR - address 0xE004 4004, CAN2CMR - address 0xE004 8004) bit description
Value Set
0[1][2] TR Transmission Request. 0 0
0 (absent) No transmission request.
1 (present) The message, previously written to the CANxTFI, CANxTID, and
optionally the CANxTDA and CANxTDB registers, is queued for
transmission from the selected Transmit Buffer. If at two or all three
of STB1, STB2 and STB3 bits are selected when TR=1 is written,
Transmit Buffer will be selected based on the chosen priority
scheme (for details see Section 12.6.3 “Transmit Buffers (TXB)”)
1[1][3] AT Abort Transmission. 0 0
0 (no action) Do not abort the transmission.
1 (present) if not already in progress, a pending Transmission Request for the
selected Transmit Buffer is cancelled.
2[4] RRB Release Receive Buffer. 0 0
0 (no action) Do not release the receive buffer.
1 (released) The information in the Receive Buffer (consisting of CANxRFS,
CANxRID, and if applicable the CANxRDA and CANxRDB registers)
is released, and becomes eligible for replacement by the next
received frame. If the next received frame is not available, writing
this command clears the RBS bit in the Status Register(s).
3[5] CDO Clear Data Overrun. 0 0
0 (no action) Do not clear the data overrun bit.
1 (clear) The Data Overrun bit in Status Register(s) is cleared.
4[1][6] SRR Self Reception Request. 0 0
0 (absent) No self reception request.
1 (present) The message, previously written to the CANxTFS, CANxTID, and
optionally the CANxTDA and CANxTDB registers, is queued for
transmission from the selected Transmit Buffer and received
simultaneously. This differs from the TR bit above in that the receiver
is not disabled during the transmission, so that it receives the
message if its Identifier is recognized by the Acceptance Filter.

Table 222. Command Register (CAN1CMR - address 0xE004 4004, CAN2CMR - address 0xE004 8004) bit description
Value Set
5 STB1 Select Tx Buffer 1. 0 0
0 (not selected) Tx Buffer 1 is not selected for transmission.
1 (selected) Tx Buffer 1 is selected for transmission.
[1] - Setting the command bits TR and AT simultaneously results in transmitting a message once. No re-transmission will be performed in
case of an error or arbitration lost (single shot transmission).
- Setting the command bits SRR and TR simultaneously results in sending the transmit message once using the self-reception feature.
No re-transmission will be performed in case of an error or arbitration lost.
- Setting the command bits TR, AT and SRR simultaneously results in transmitting a message once as described for TR and AT. The
moment the Transmit Status bit is set within the Status Register, the internal Transmission Request Bit is cleared automatically.
- Setting TR and SRR simultaneously will ignore the set SRR bit.
[2] If the Transmission Request or the Self-Reception Request bit was set '1' in a previous command, it cannot be cancelled by resetting the
bits. The requested transmission may only be cancelled by setting the Abort Transmission bit.
[3] The Abort Transmission bit is used when the CPU requires the suspension of the previously requested transmission, e.g. to transmit a
more urgent message before. A transmission already in progress is not stopped. In order to see if the original message has been either
transmitted successfully or aborted, the Transmission Complete Status bit should be checked. This should be done after the Transmit
Buffer Status bit has been set to '1' or a Transmit Interrupt has been generated.
[4] After reading the contents of the Receive Buffer, the CPU can release this memory space by setting the Release Receive Buffer bit '1'.
This may result in another message becoming immediately available. If there is no other message available, the Receive Interrupt bit is
reset. If the RRB command is given, it will take at least 2 internal clock cycles before a new interrupt is generated.
[5] This command bit is used to clear the Data Overrun condition signalled by the Data Overrun Status bit. As long as the Data Overrun
Status bit is set no further Data Overrun Interrupt is generated.
[6] Upon Self Reception Request, a message is transmitted and simultaneously received if the Acceptance Filter is set to the corresponding
identifier. A receive and a transmit interrupt will indicate correct self reception (see also Self Test Mode in Section 12.8.1 “Mode Register
(CAN1MOD - 0xE004 4000, CAN2MOD - 0xE004 8000)”).
12.8.3 Global Status Register (CAN1GSR - 0xE004 x008, CAN2GSR -

0xE004 8008)
The content of the Global Status Register reflects the status of the CAN Controller. This
register is read-only, except that the Error Counters can be written when the RM bit in the
CANMOD register is 1. Bits not listed read as 0 and should be written as 0.
Table 223. Global Status Register (CAN1GSR - address 0xE004 4008, CAN2GSR - address 0xE004 8008) bit
description
Value Set
0 RBS[1] Receive Buffer Status. 0 0
0 (empty) No message is available.
1 (full) At least one complete message is received by the Double Receive Buffer
and available in the CANxRFS, CANxRID, and if applicable the CANxRDA
and CANxRDB registers. This bit is cleared by the Release Receive Buffer
command in CANxCMR, if no subsequent received message is available.

Table 223. Global Status Register (CAN1GSR - address 0xE004 4008, CAN2GSR - address 0xE004 8008) bit
description
Value Set
1 DOS[2] Data Overrun Status. 0 0
0 (absent) No data overrun has occurred since the last Clear Data Overrun command
was given/written to CANxCMR (or since Reset).
1 (overrun) A message was lost because the preceding message to this CAN controller
was not read and released quickly enough (there was not enough space for
a new message in the Double Receive Buffer).
2 TBS Transmit Buffer Status. 1 1
0 (locked) At least one of the Transmit Buffers is not available for the CPU, i.e. at least
one previously queued message for this CAN controller has not yet been
sent, and therefore software should not write to the CANxTFI, CANxTID,
CANxTDA, nor CANxTDB registers of that (those) Tx buffer(s).
1 (released) All three Transmit Buffers are available for the CPU. No transmit message is
pending for this CAN controller (in any of the 3 Tx buffers), and software may
write to any of the CANxTFI, CANxTID, CANxTDA, and CANxTDB registers.
3 TCS[3] Transmit Complete Status. 1 x
0 (incomplete) At least one requested transmission has not been successfully completed
yet.
1 (complete) All requested transmission(s) has (have) been successfully completed.
4 RS[4] Receive Status. 1 0
0 (idle) The CAN controller is idle.
1 (receive) The CAN controller is receiving a message.
5 TS[4] Transmit Status. 1 0
0 (idle) The CAN controller is idle.
1 (transmit) The CAN controller is sending a message.
6 ES[5] Error Status. 0 0
0 (ok) Both error counters are below the Error Warning Limit.
1 (error) One or both of the Transmit and Receive Error Counters has reached the
limit set in the Error Warning Limit register.
7 BS[6] Bus Status. 0 0
0 (Bus-On) The CAN Controller is involved in bus activities
1 (Bus-Off) The CAN controller is currently not involved/prohibited from bus activity
because the Transmit Error Counter reached its limiting value of 255.
15:8 - - Reserved, user software should not write ones to reserved bits. The value NA
23:16 RXERR - The current value of the Rx Error Counter (an 8 - bit value). 0 X
31:24 TXERR - The current value of the Tx Error Counter (an 8 - bit value). 0 X
[1] After reading all messages and releasing their memory space with the command 'Release Receive Buffer,' this bit is cleared.
[2] If there is not enough space to store the message within the Receive Buffer, that message is dropped and the Data Overrun condition is
signalled to the CPU in the moment this message becomes valid. If this message is not completed successfully (e.g. because of an
error), no overrun condition is signalled.
[3] The Transmission Complete Status bit is set '0' (incomplete) whenever the Transmission Request bit or the Self Reception Request bit
is set '1' at least for one of the three Transmit Buffers. The Transmission Complete Status bit will remain '0' until all messages are
transmitted successfully.

[4] If both the Receive Status and the Transmit Status bits are '0' (idle), the CAN-Bus is idle. If both bits are set, the controller is waiting to
become idle again. After hardware reset 11 consecutive recessive bits have to be detected until idle status is reached. After Bus-off this
will take 128 times of 11 consecutive recessive bits.
[5] Errors detected during reception or transmission will effect the error counters according to the CAN specification. The Error Status bit is
set when at least one of the error counters has reached or exceeded the Error Warning Limit. An Error Warning Interrupt is generated, if
enabled. The default value of the Error Warning Limit after hardware reset is 96 decimal, see also Section 12.8.7 “Error Warning Limit
Register (CAN1EWL - 0xE004 4018, CAN2EWL - 0xE004 8018)”.
[6] Mode bit '1' (present) and an Error Warning Interrupt is generated, if enabled. Afterwards the Transmit Error Counter is set to '127', and
the Receive Error Counter is cleared. It will stay in this mode until the CPU clears the Reset Mode bit. Once this is completed the CAN
Controller will wait the minimum protocol-defined time (128 occurrences of the Bus-Free signal) counting down the Transmit Error
Counter. After that, the Bus Status bit is cleared (Bus-On), the Error Status bit is set '0' (ok), the Error Counters are reset, and an Error
Warning Interrupt is generated, if enabled. Reading the TX Error Counter during this time gives information about the status of the
Bus-Off recovery.
RX error counter
The RX Error Counter Register, which is part of the Status Register, reflects the current
value of the Receive Error Counter. After hardware reset this register is initialized to 0. In
Operating Mode this register appears to the CPU as a read only memory. A write access
to this register is possible only in Reset Mode. If a Bus Off event occurs, the RX Error
Counter is initialized to 0. As long as Bus Off is valid, writing to this register has no
effect.The Rx Error Counter is determined as follows:
RX Error Counter = (CANxGSR AND 0x00FF0000) / 0x00010000
Note that a CPU-forced content change of the RX Error Counter is possible only if the
Reset Mode was entered previously. An Error Status change (Status Register), an Error
Warning or an Error Passive Interrupt forced by the new register content will not occur
until the Reset Mode is cancelled again.
TX error counter
The TX Error Counter Register, which is part of the Status Register, reflects the current
value of the Transmit Error Counter. In Operating Mode this register appears to the CPU
as a read only memory. After hardware reset this register is initialized to ’0’. A write access
to this register is possible only in Reset Mode. If a bus-off event occurs, the TX Error
Counter is initialized to 127 to count the minimum protocol-defined time (128 occurrences
of the Bus-Free signal). Reading the TX Error Counter during this time gives information
about the status of the Bus-Off recovery. If Bus Off is active, a write access to TXERR in
the range of 0 to 254 clears the Bus Off Flag and the controller will wait for one occurrence
of 11 consecutive recessive bits (bus free) after clearing of Reset Mode. The Tx error
counter is determined as follows:
TX Error Counter = (CANxGSR AND 0xFF000000) / 0x01000000
Writing 255 to TXERR allows initiation of a CPU-driven Bus Off event. Note that a
CPU-forced content change of the TX Error Counter is possible only if the Reset Mode
was entered previously. An Error or Bus Status change (Status Register), an Error
Warning, or an Error Passive Interrupt forced by the new register content will not occur
until the Reset Mode is cancelled again. After leaving the Reset Mode, the new TX
Counter content is interpreted and the Bus Off event is performed in the same way as if it
was forced by a bus error event. That means, that the Reset Mode is entered again, the
TX Error Counter is initialized to 127, the RX Counter is cleared, and all concerned Status
and Interrupt Register Bits are set. Clearing of Reset Mode now will perform the protocol

defined Bus Off recovery sequence (waiting for 128 occurrences of the Bus-Free signal).
If the Reset Mode is entered again before the end of Bus Off recovery (TXERR>0), Bus
Off keeps active and TXERR is frozen.
12.8.4 Interrupt and Capture Register (CAN1ICR - 0xE004 400C, CAN2ICR -

0xE004 800C)
Bits in this register indicate information about events on the CAN bus. This register is
read-only. Bits not listed read as 0 and should be written as 0.
The Interrupt flags of the Interrupt and Capture Register allow the identification of an
interrupt source. When one or more bits are set, a CAN interrupt will be indicated to the
CPU. After this register is read from the CPU all interrupt bits are reset except of the
Receive Interrupt bit. The Interrupt Register appears to the CPU as a read only memory.
Bits 1 thru 10 clear when they are read.
Bits 16-23 are captured when a bus error occurs. At the same time, if the BEIE bit in
CANIER is 1, the BEI bit in this register is set, and a CAN interrupt can occur.
Bits 24-31 are captured when CAN arbitration is lost. At the same time, if the ALIE bit in
CANIER is 1, the ALI bit in this register is set, and a CAN interrupt can occur. Once either
of these bytes is captured, its value will remain the same until it is read, at which time it is
released to capture a new value.
The clearing of bits 1 to 10 and the releasing of bits 16-23 and 24-31 all occur on any read
from CANxICR, regardless of whether part or all of the register is read. This means that
software should always read CANxICR as a word, and process and deal with all bits of the
register as appropriate for the application.
Table 224. Interrupt and Capture Register (CAN1ICR - address 0xE004 400C, CAN2ICR -
Value Set
0 RI[1] 0 (reset) Receive Interrupt. This bit is set whenever the RBS bit 0 0
1 (set) in CANxSR and the RIE bit in CANxIER are both 1,
indicating that a new message was received and
stored in the Receive Buffer.
1 TI1 0 (reset) Transmit Interrupt 1. This bit is set when the TBS1 bit 0 0
1 (set) in CANxSR goes from 0 to 1 (whenever a message
out of TXB1 was successfully transmitted or aborted),
indicating that Transmit buffer 1 is available, and the
TIE1 bit in CANxIER is 1.
2 EI 0 (reset) Error Warning Interrupt. This bit is set on every 0 X
1 (set) change (set or clear) of either the Error Status or Bus
Status bit in CANxSR and the EIE bit bit is set within
the Interrupt Enable Register at the time of the
change.
3 DOI 0 (reset) Data Overrun Interrupt. This bit is set when the DOS 0 0
1 (set) bit in CANxSR goes from 0 to 1 and the DOIE bit in
CANxIER is 1.
4 WUI[2] 0 (reset) Wake-Up Interrupt. This bit is set if the CAN controller 0 0
1 (set) is sleeping and bus activity is detected and the WUIE
bit in CANxIER is 1.

Value Set
5 EPI 0 (reset) Error Passive Interrupt. This bit is set if the EPIE bit in 0 0
1 (set) CANxIER is 1, and the CAN controller switches
between Error Passive and Error Active mode in
either direction.
This is the case when the CAN Controller has reached
the Error Passive Status (at least one error counter
exceeds the CAN protocol defined level of 127) or if
the CAN Controller is in Error Passive Status and
enters the Error Active Status again.
6 ALI 0 (reset) Arbitration Lost Interrupt. This bit is set if the ALIE bit 0 0
1 (set) in CANxIER is 1, and the CAN controller loses
arbitration while attempting to transmit. In this case
the CAN node becomes a receiver.
7 BEI 0 (reset) Bus Error Interrupt -- this bit is set if the BEIE bit in 0 X
1 (set) CANxIER is 1, and the CAN controller detects an error
on the bus.
8 IDI 0 (reset) ID Ready Interrupt -- this bit is set if the IDIE bit in 0 0
1 (set) CANxIER is 1, and a CAN Identifier has been
received (a message was successfully transmitted or
aborted). This bit is set whenever a message was
successfully transmitted or aborted and the IDIE bit is
set in the IER reg.
15:11 - - Reserved, user software should not write ones to 0 0
reserved bits.

Value Set
20:16 ERRBIT Error Code Capture: when the CAN controller detects 0 X
4:0[3] a bus error, the location of the error within the frame is
captured in this field. The value reflects an internal
state variable, and as a result is not very linear:
00011 Start of Frame
00010 ID28 ... ID21
00110 ID20 ... ID18
00100 SRTR Bit
00101 IDE bit
00111 ID17 ... 13
01111 ID12 ... ID5
01110 ID4 ... ID0
01100 RTR Bit
01101 Reserved Bit 1
01001 Reserved Bit 0
01011 Data Length Code
01010 Data Field
01000 CRC Sequence
11000 CRC Delimiter
11001 Acknowledge Slot
11011 Acknowledge Delimiter
11010 End of Frame
10010 Intermission
10001 Active Error Flag
10110 Passive Error Flag
10011 Tolerate Dominant Bits
10111 Error Delimiter
11100 Overload flag
21 ERRDIR When the CAN controller detects a bus error, the 0 X
direction of the current bit is captured in this bit.
0 Error occurred during transmitting.
1 Error occurred during receiving.
23:22 ERRC1:0 When the CAN controller detects a bus error, the type 0 X
of error is captured in this field:
00 Bit error
01 Form error
10 Stuff error
11 Other error

Value Set
31:24 ALCBIT[4] - Each time arbitration is lost while trying to send on the 0 X
CAN, the bit number within the frame is captured into
this field. After the content of ALCBIT is read, the ALI
bit is cleared and a new Arbitration Lost interrupt can
occur.
00 arbitration lost in the first bit (MS) of identifier
... a
11 arbitration lost in SRTS bit (RTR bit for standard frame
messages)
12 arbitration lost in IDE bit
13 arbitration lost in 12th bit of identifier (extended frame
only)
...
30 arbitration lost in last bit of identifier (extended frame
only)
31 arbitration lost in RTR bit (extended frame only)
[1] The Receive Interrupt Bit is not cleared upon a read access to the Interrupt Register. Giving the Command
“Release Receive Buffer” will clear RI temporarily. If there is another message available within the Receive
Buffer after the release command, RI is set again. Otherwise RI remains cleared.
[2] A Wake-Up Interrupt is also generated if the CPU tries to set the Sleep bit while the CAN controller is
involved in bus activities or a CAN Interrupt is pending. The WUI flag can also get asserted when the
according enable bit WUIE is not set. In this case a Wake-Up Interrupt does not get asserted.
[3] Whenever a bus error occurs, the corresponding bus error interrupt is forced, if enabled. At the same time,
the current position of the Bit Stream Processor is captured into the Error Code Capture Register. The
content within this register is fixed until the user software has read out its content once. From now on, the
capture mechanism is activated again, i.e. reading the CANxICR enables another Bus Error Interrupt.
[4] On arbitration lost, the corresponding arbitration lost interrupt is forced, if enabled. At that time, the current
bit position of the Bit Stream Processor is captured into the Arbitration Lost Capture Register. The content
within this register is fixed until the user application has read out its contents once. From now on, the
capture mechanism is activated again.
12.8.5 Interrupt Enable Register (CAN1IER - 0xE004 4010, CAN2IER -

0xE004 8010)
This read/write register controls whether various events on the CAN controller will result in
an interrupt or not. Bits 10:0 in this register correspond 1-to-1 with bits 10:0 in the
CANxICR register. If a bit in the CANxIER register is 0 the corresponding interrupt is
disabled; if a bit in the CANxIER register is 1 the corresponding source is enabled to
trigger an interrupt.

Table 225. Interrupt Enable Register (CAN1IER - address 0xE004 4010, CAN2IER - address
Bit Symbol Function Reset RM
Value Set
0 RIE Receiver Interrupt Enable. When the Receive Buffer Status is 'full', 0 X
the CAN Controller requests the respective interrupt.
1 TIE1 Transmit Interrupt Enable for Buffer1. When a message has been 0 X
successfully transmitted out of TXB1 or Transmit Buffer 1 is
accessible again (e.g. after an Abort Transmission command), the
CAN Controller requests the respective interrupt.
2 EIE Error Warning Interrupt Enable. If the Error or Bus Status change 0 X
(see Status Register), the CAN Controller requests the respective
interrupt.
3 DOIE Data Overrun Interrupt Enable. If the Data Overrun Status bit is 0 X
set (see Status Register), the CAN Controller requests the
respective interrupt.
4 WUIE Wake-Up Interrupt Enable. If the sleeping CAN controller wakes 0 X
up, the respective interrupt is requested.
5 EPIE Error Passive Interrupt Enable. If the error status of the CAN 0 X
Controller changes from error active to error passive or vice versa,
the respective interrupt is requested.
6 ALIE Arbitration Lost Interrupt Enable. If the CAN Controller has lost 0 X
arbitration, the respective interrupt is requested.
7 BEIE Bus Error Interrupt Enable. If a bus error has been detected, the 0 X
8 IDIE ID Ready Interrupt Enable. When a CAN identifier has been 0 X
received, the CAN Controller requests the respective interrupt.
12.8.6 Bus Timing Register (CAN1BTR - 0xE004 4014, CAN2BTR -

0xE004 8014)
This register controls how various CAN timings are derived from the APB clock. It defines
the values of the Baud Rate Prescaler (BRP) and the Synchronization Jump Width (SJW).
Furthermore, it defines the length of the bit period, the location of the sample point and the
number of samples to be taken at each sample point. It can be read at any time but can
only be written if the RM bit in CANmod is 1.

Table 226. Bus Timing Register (CAN1BTR - address 0xE004 4014, CAN2BTR - address
Value Set
9:0 BRP Baud Rate Prescaler. The APB clock is divided by (this 0 X
value plus one) to produce the CAN clock.
13:10 - Reserved, user software should not write ones to reserved NA
15:14 SJW The Synchronization Jump Width is (this value plus one) 0 X
CAN clocks.
19:16 TESG1 The delay from the nominal Sync point to the sample point 1100 X
is (this value plus one) CAN clocks.
22:20 TESG2 The delay from the sample point to the next nominal sync 001 X
point is (this value plus one) CAN clocks. The nominal CAN
bit time is (this value plus the value in TSEG1 plus 3) CAN
clocks.
23 SAM Sampling
0 The bus is sampled once (recommended for high speed 0 X
buses)
1 The bus is sampled 3 times (recommended for low to
medium speed buses to filter spikes on the bus-line)
Baud rate prescaler

The period of the CAN system clock tSCL is programmable and determines the individual
bit timing. The CAN system clock tSCL is calculated using the following equation:
(1)
t SCL = t CANsuppliedCLK   BRP + 1 
Synchronization jump width

To compensate for phase shifts between clock oscillators of different bus controllers, any
bus controller must re-synchronize on any relevant signal edge of the current
transmission. The synchronization jump width tSJW defines the maximum number of clock
cycles a certain bit period may be shortened or lengthened by one re-synchronization:
(2)
t SJW = t SCL   SJW + 1 
Time segment 1 and time segment 2

Time segments TSEG1 and TSEG2 determine the number of clock cycles per bit period
and the location of the sample point:
(3)
t SYNCSEG = t SCL

(4)
t TSEG1 = t SCL   TSEG1 + 1 
(5)
t TSEG2 = t SCL   TSEG2 + 1 
12.8.7 Error Warning Limit Register (CAN1EWL - 0xE004 4018, CAN2EWL -

0xE004 8018)
This register sets a limit on Tx or Rx errors at which an interrupt can occur. It can be read
at any time but can only be written if the RM bit in CANmod is 1. The default value (after
hardware reset) is 96.
Table 227. Error Warning Limit register (CAN1EWL - address 0xE004 4018, CAN2EWL -
Value Set
7:0 EWL During CAN operation, this value is compared to both the Tx and 9610 = 0x6 X
Rx Error Counters. If either of these counter matches this value, 0
the Error Status (ES) bit in CANSR is set.
Note that a content change of the Error Warning Limit Register is possible only if the
Reset Mode was entered previously. An Error Status change (Status Register) and an
Error Warning Interrupt forced by the new register content will not occur until the Reset
Mode is cancelled again.
12.8.8 Status Register (CAN1SR - 0xE004 401C, CAN2SR - 0xE004 801C)

This register contains three status bytes in which the bits not related to transmission are
identical to the corresponding bits in the Global Status Register, while those relating to
transmission reflect the status of each of the 3 Tx Buffers.
Table 228. Status Register (CAN1SR - address 0xE004 401C, CAN2SR - address 0xE004 801C) bit description
Value Set
0 RBS Receive Buffer Status. This bit is identical to the RBS bit in the CANxGSR. 0 0
1 DOS Data Overrun Status. This bit is identical to the DOS bit in the CANxGSR. 0 0
2 TBS1[1] Transmit Buffer Status 1. 1 1
0(locked) Software cannot access the Tx Buffer 1 nor write to the corresponding
CANxTFI, CANxTID, CANxTDA, and CANxTDB registers because a
message is either waiting for transmission or is in transmitting process.
1(released) Software may write a message into the Transmit Buffer 1 and its CANxTFI,
CANxTID, CANxTDA, and CANxTDB registers.
3 TCS1[2] Transmission Complete Status. 1 x
0(incomplete) The previously requested transmission for Tx Buffer 1 is not complete.
1(complete) The previously requested transmission for Tx Buffer 1 has been successfully
completed.
4 RS Receive Status. This bit is identical to the RS bit in the GSR. 1 0

Value Set
5 TS1 Transmit Status 1. 1 0
0(idle) There is no transmission from Tx Buffer 1.
1(transmit) The CAN Controller is transmitting a message from Tx Buffer 1.
6 ES Error Status. This bit is identical to the ES bit in the CANxGSR. 0 0
7 BS Bus Status. This bit is identical to the BS bit in the CANxGSR. 0 0
completed.
completed.

Value Set
[1] If the CPU tries to write to this Transmit Buffer when the Transmit Buffer Status bit is '0' (locked), the written byte is not accepted and is
lost without this being signalled.
[2] The Transmission Complete Status bit is set '0' (incomplete) whenever the Transmission Request bit or the Self Reception Request bit
is set '1' for this TX buffer. The Transmission Complete Status bit remains '0' until a message is transmitted successfully.
12.8.9 Receive Frame Status Register (CAN1RFS - 0xE004 4020, CAN2RFS -

0xE004 8020)
This register defines the characteristics of the current received message. It is read-only in
normal operation but can be written for testing purposes if the RM bit in CANxMOD is 1.
Table 229. Receive Frame Status register (CAN1RFS - address 0xE004 4020, CAN2RFS -
Value Set
9:0 ID Index If the BP bit (below) is 0, this value is the zero-based number of the 0 X
Lookup Table RAM entry at which the Acceptance Filter matched
the received Identifier. Disabled entries in the Standard tables are
included in this numbering, but will not be matched. See
Section 12.18 “Examples of acceptance filter tables and ID index
values” on page 310 for examples of ID Index values.
10 BP If this bit is 1, the current message was received in AF Bypass 0 X
mode, and the ID Index field (above) is meaningless.
19:16 DLC The field contains the Data Length Code (DLC) field of the current 0 X
received message. When RTR = 0, this is related to the number of
data bytes available in the CANRDA and CANRDB registers as
follows:
0000-0111 = 0 to 7 bytes1000-1111 = 8 bytes
With RTR = 1, this value indicates the number of data bytes
requested to be sent back, with the same encoding.
30 RTR This bit contains the Remote Transmission Request bit of the 0 X
current received message. 0 indicates a Data Frame, in which (if
DLC is non-zero) data can be read from the CANRDA and possibly
the CANRDB registers. 1 indicates a Remote frame, in which case
the DLC value identifies the number of data bytes requested to be
sent using the same Identifier.
31 FF A 0 in this bit indicates that the current received message included 0 X
an 11 bit Identifier, while a 1 indicates a 29 bit Identifier. This affects
the contents of the CANid register described below.

12.8.9.1 ID index field

The ID Index is a 10-bit field in the Info Register that contains the table position of the ID
Look-up Table if the currently received message was accepted. The software can use this
index to simplify message transfers from the Receive Buffer into the Shared Message
Memory. Whenever bit 10 (BP) of the ID Index in the CANRFS register is 1, the current
CAN message was received in acceptance filter bypass mode.
12.8.10 Receive Identifier Register (CAN1RID - 0xE004 4024, CAN2RID -

0xE004 8024)
This register contains the Identifier field of the current received message. It is read-only in
normal operation but can be written for testing purposes if the RM bit in CANmod is 1. It
has two different formats depending on the FF bit in CANRFS. See Table 217 for details
on specific CAN channel register address.
Table 230. Receive Identifier Register (CAN1RID - address 0xE004 4024, CAN2RID - address
Bit Symbol Function Reset Value RM Set
10:0 ID The 11 bit Identifier field of the current received 0 X
message. In CAN 2.0A, these bits are called ID10-0,
while in CAN 2.0B they’re called ID29-18.
defined.
Table 231. RX Identifier register when FF = 1

Bit Symbol Function Reset Value RM Set
28:0 ID The 29 bit Identifier field of the current received 0 X
message. In CAN 2.0B these bits are called ID29-0.
defined.
12.8.11 Receive Data Register A (CAN1RDA - 0xE004 4028, CAN2RDA -

0xE004 8028)
This register contains the first 1-4 Data bytes of the current received message. It is
read-only in normal operation, but can be written for testing purposes if the RM bit in
CANMOD is 1. See Table 217 for details on specific CAN channel register address.
Table 232. Receive Data register A (CAN1RDA - address 0xE004 4028, CAN2RDA - address
Value Set
7:0 Data 1 If the DLC field in CANRFS Š 0001, this contains the first Data byte 0 X
of the current received message.

Table 232. Receive Data register A (CAN1RDA - address 0xE004 4028, CAN2RDA - address
Value Set
12.8.12 Receive Data Register B (CAN1RDB - 0xE004 402C, CAN2RDB -

0xE004 802C)
This register contains the 5th through 8th Data bytes of the current received message. It is
read-only in normal operation, but can be written for testing purposes if the RM bit in
CANMOD is 1. See Table 217 for details on specific CAN channel register address.
Table 233. Receive Data register B (CAN1RDB - address 0xE004 402C, CAN2RDB - address
0xE004 802C) bit description
Value Set
12.8.13 Transmit Frame Information Register (CAN1TFI[1/2/3] - 0xE004 40[30/

40/50], CAN2TFI[1/2/3] - 0xE004 80[30/40/50])
When the corresponding TBS bit in CANSR is 1, software can write to one of these
registers to define the format of the next transmit message for that Tx buffer. Bits not listed
read as 0 and should be written as 0.
The values for the reserved bits of the CANxTFI register in the Transmit Buffer should be
set to the values expected in the Receive Buffer for an easy comparison, when using the
Self Reception facility (self test), otherwise they are not defined.
The CAN Controller consist of three Transmit Buffers. Each of them has a length of 4
words and is able to store one complete CAN message as shown in Figure 42.
The buffer layout is subdivided into Descriptor and Data Field where the first word of the
Descriptor Field includes the TX Frame Info that describes the Frame Format, the Data
Length and whether it is a Remote or Data Frame. In addition, a TX Priority register allows
the definition of a certain priority for each transmit message. Depending on the chosen
Frame Format, an 11-bit identifier for Standard Frame Format (SFF) or an 29-bit identifier
for Extended Frame Format (EFF) follows. Note that unused bits in the TID field have to
be defined as 0. The Data Field in TDA and TDB contains up to eight data bytes.

Table 234. Transmit Frame Information Register (CAN1TFI[1/2/3] - address

0xE004 40[30/40/50], CAN2TFI[1/2/3] - 0xE004 80[30/40/50]) bit description
Value Set
7:0 PRIO If the TPM (Transmit Priority Mode) bit in the CANxMOD register is x
set to 1, enabled Tx Buffers contend for the right to send their
messages based on this field. The buffer with the lowest TX Priority
value wins the prioritization and is sent first.
15:8 - Reserved. 0
19:16 DLC Data Length Code. This value is sent in the DLC field of the next 0 X
transmit message. In addition, if RTR = 0, this value controls the
number of Data bytes sent in the next transmit message, from the
CANxTDA and CANxTDB registers:
0000-0111 = 0-7 bytes
1xxx = 8 bytes
29:20 - Reserved. 0
30 RTR This value is sent in the RTR bit of the next transmit message. If 0 X
this bit is 0, the number of data bytes called out by the DLC field are
sent from the CANxTDA and CANxTDB registers. If this bit is 1, a
Remote Frame is sent, containing a request for that number of
bytes.
31 FF If this bit is 0, the next transmit message will be sent with an 11 bit 0 X
Identifier (standard frame format), while if it’s 1, the message will be
sent with a 29 bit Identifier (extended frame format).
Automatic transmit priority detection

To allow uninterrupted streams of transmit messages, the CAN Controller provides
Automatic Transmit Priority Detection for all Transmit Buffers. Depending on the selected
Transmit Priority Mode, internal prioritization is based on the CAN Identifier or a user
defined "local priority". If more than one message is enabled for transmission (TR=1) the
internal transmit message queue is organized such as that the transmit buffer with the
lowest CAN Identifier (TID) or the lowest "local priority" (TX Priority) wins the prioritization
and is sent first. The result of the internal scheduling process is taken into account short
before a new CAN message is sent on the bus. This is also true after the occurrence of a
transmission error and right before a re-transmission.
Tx DLC
The number of bytes in the Data Field of a message is coded with the Data Length Code
(DLC). At the start of a Remote Frame transmission the DLC is not considered due to the
RTR bit being '1 ' (remote). This forces the number of transmitted/received data bytes to
be 0. Nevertheless, the DLC must be specified correctly to avoid bus errors, if two CAN
Controllers start a Remote Frame transmission with the same identifier simultaneously.
For reasons of compatibility no DLC > 8 should be used. If a value greater than 8 is
selected, 8 bytes are transmitted in the data frame with the Data Length Code specified in
DLC. The range of the Data Byte Count is 0 to 8 bytes and is coded as follows:
(6)
DataByteCount = DLC

12.8.14 Transmit Identifier Register (CAN1TID[1/2/3] - 0xE004 40[34/44/54],

CAN2TID[1/2/3] - 0xE004 80[34/44/54])
When the corresponding TBS bit in CANxSR is 1, software can write to one of these
registers to define the Identifier field of the next transmit message. Bits not listed read as 0
and should be written as 0. The register assumes two different formats depending on the
FF bit in CANTFI.
In Standard Frame Format messages, the CAN Identifier consists of 11 bits (ID.28 to
ID.18), and in Extended Frame Format messages, the CAN identifier consists of 29 bits
(ID.28 to ID.0). ID.28 is the most significant bit, and it is transmitted first on the bus during
the arbitration process. The Identifier acts as the message's name, used in a receiver for
acceptance filtering, and also determines the bus access priority during the arbitration
process.
Table 235. Transfer Identifier Register (CAN1TID[1/2/3] - address 0xE004 40[34/44/54],

CAN2TID[1/2/3] - address 0xE004 80[34/44/54]) bit description
Value Set
10:0 ID The 11 bit Identifier to be sent in the next transmit message. 0 X
Table 236. Transfer Identifier register when FF = 1

Value Set
28:0 ID The 29 bit Identifier to be sent in the next transmit message. 0 X
12.8.15 Transmit Data Register A (CAN1TDA[1/2/3] - 0xE004 40[38/48/58],

CAN2TDA[1/2/3] - 0xE004 80[38/48/58])
registers to define the first 1 - 4 data bytes of the next transmit message. The Data Length
Code defines the number of transferred data bytes. The first bit transmitted is the most
significant bit of TX Data Byte 1.
Table 237. Transmit Data Register A (CAN1TDA[1/2/3] - address 0xE004 40[38/48/58],

CAN2TDA[1/2/3] - address 0xE004 80[38/48/58]) bit description
Value Set
7:0 Data 1 If RTR = 0 and DLC Š 0001 in the corresponding CANxTFI, this 0 X
byte is sent as the first Data byte of the next transmit message.
15;8 Data 2 If RTR = 0 and DLC Š 0010 in the corresponding CANxTFI, this 0 X
byte is sent as the 2nd Data byte of the next transmit message.
byte is sent as the 3rd Data byte of the next transmit message.
byte is sent as the 4th Data byte of the next transmit message.

12.8.16 Transmit Data Register B (CAN1TDB[1/2/3] - 0xE004 40[3C/4C/5C],

CAN2TDB[1/2/3] - 0xE004 80[3C/4C/5C])
registers to define the 5th through 8th data bytes of the next transmit message. The Data
Length Code defines the number of transferred data bytes. The first bit transmitted is the
most significant bit of TX Data Byte 1.
Table 238. Transmit Data Register B (CAN1TDB[1/2/3] - address 0xE004 40[3C/4C/5C],

CAN2TDB[1/2/3] - address 0xE004 80[3C/4C/5C]) bit description
Value Set
7:0 Data 5 If RTR = 0 and DLC Š 0101 in the corresponding CANTFI, this 0 X
15;8 Data 6 If RTR = 0 and DLC Š 0110 in the corresponding CANTFI, this 0 X
12.8.17 CAN Sleep Clear register (CANSLEEPCLR - 0x400F C110)

This register provides the current sleep state of the two CAN channels and provides a
means to restore the clocks to that channel following wake-up. Refer to Section 12.9.2
“Sleep mode” for more information on the CAN sleep feature.
Table 239. CAN Sleep Clear register (CANSLEEPCLR - address 0x400F C110) bit description
Bit Symbol Function Reset Value
0 - Reserved, user software should not write ones to reserved bits. The value read from a NA
1 CAN1SLEEP Sleep status and control for CAN channel 1. 0
Read: when 1, indicates that CAN channel 1 is in the sleep mode.
Write: writing a 1 causes clocks to be restored to CAN channel 1.
2 CAN2SLEEP Sleep status and control for CAN channel 2. 0
Read: when 1, indicates that CAN channel 2 is in the sleep mode.
Write: writing a 1 causes clocks to be restored to CAN channel 2.
31:3 - Reserved, user software should not write ones to reserved bits. The value read from a NA
12.8.18 CAN Wake-up Flags register (CANWAKEFLAGS - 0x400F C114)

This register provides the wake-up status for the two CAN channels and allows clearing
wake-up events. Refer to Section 12.9.2 “Sleep mode” for more information on the CAN
sleep feature.

Table 240. CAN Wake-up Flags register (CANWAKEFLAGS - address 0x400F C114) bit description
Bit Symbol Function Reset Value
0 - Reserved, user software should not write ones to reserved bits. The value read from NA
1 CAN1WAKE Wake-up status for CAN channel 1. 0
Read: when 1, indicates that a falling edge has occurred on the receive data line of
CAN channel 1.
Write: writing a 1 clears this bit.
2 CAN2WAKE Wake-up status for CAN channel 2. 0
Read: when 1, indicates that a falling edge has occurred on the receive data line of
CAN channel 2.
Write: writing a 1 clears this bit.
31:3 - Reserved, user software should not write ones to reserved bits. The value read from NA
12.9 CAN controller operation
12.9.1 Error handling

The CAN Controllers count and handle transmit and receive errors as specified in CAN
Spec 2.0B. The Transmit and Receive Error Counters are incriminated for each detected
error and are decremented when operation is error-free. If the Transmit Error counter
contains 255 and another error occurs, the CAN Controller is forced into a state called
Bus-Off. In this state, the following register bits are set: BS in CANxSR, BEI and EI in
CANxIR if these are enabled, and RM in CANxMOD. RM resets and disables much of the
CAN Controller. Also at this time the Transmit Error Counter is set to 127 and the Receive
Error Counter is cleared. Software must next clear the RM bit. Thereafter the Transmit
Error Counter will count down 128 occurrences of the Bus Free condition (11 consecutive
recessive bits). Software can monitor this countdown by reading the Tx Error Counter.
When this countdown is complete, the CAN Controller clears BS and ES in CANxSR, and
sets EI in CANxSR if EIE in IER is 1.
The Tx and Rx error counters can be written if RM in CANxMOD is 1. Writing 255 to the
Tx Error Counter forces the CAN Controller to Bus-Off state. If Bus-Off (BS in CANxSR) is
1, writing any value 0 through 254 to the Tx Error Counter clears Bus-Off. When software
clears RM in CANxMOD thereafter, only one Bus Free condition (11 consecutive
recessive bits) is needed before operation resumes.
12.9.2 Sleep mode

The CAN Controller will enter sleep mode if the SM bit in the CAN Mode register is 1, no
CAN interrupt is pending, and there is no activity on the CAN bus. Software can only set
SM when RM in the CAN Mode register is 0; it can also set the WUIE bit in the CAN
Interrupt Enable register to enable an interrupt on any wake-up condition.
The CAN Controller wakes up (and sets WUI in the CAN Interrupt register if WUIE in the
CAN Interrupt Enable register is 1) in response to a) a dominant bit on the CAN bus, or b)
software clearing SM in the CAN Mode register. A sleeping CAN Controller, that wakes up
in response to bus activity, is not able to receive an initial message, until after it detects
Bus_Free (11 consecutive recessive bits). If an interrupt is pending or the CAN bus is
active when software sets SM, the wake-up is immediate.

12.9.3 Interrupts
Each CAN Controller produces interrupt requests for Receive, Transmit, and “other
status”. The Transmit interrupt is the OR of the Transmit interrupts from the three Tx
Buffers. The Receive, Transmit, and “other status” interrupts from all of the CAN
controllers and the Acceptance Filter LUTerr condition are ORed into one VIC channel
(see Table 86).
12.9.4 Transmit priority

If the TPM bit in the CANxMOD register is 0, multiple enabled Tx Buffers contend for the
right to send their messages based on the value of their CAN Identifier (TID). If TPM is 1,
they contend based on the PRIO fields in bits 7:0 of their CANxTFS registers. In both
cases the smallest binary value has priority. If two (or three) transmit-enabled buffers have
the same smallest value, the lowest-numbered buffer sends first.
The CAN controller selects among multiple enabled Tx Buffers dynamically, just before it
sends each message.
12.10 Centralized CAN registers

For easy and fast access, all CAN Controller Status bits from each CAN Controller Status
register are bundled together. Each defined byte of the following registers contains one
particular status bit from each of the CAN controllers, in its LS bits.
All Status registers are “read-only” and allow byte, half word and word access.
12.10.1 Central Transmit Status Register (CANTxSR - 0xE004 0000)

Table 241. Central Transit Status Register (CANTxSR - address 0xE004 0000) bit description
Value
0 TS1 When 1, the CAN controller 1 is sending a message (same as TS in the 0
).
1 TS2 When 1, the CAN controller 2 is sending a message (same as TS in the 0
CAN2GSR)
8 TBS1 When 1, all 3 Tx Buffers of the CAN1 controller are available to the CPU 1
(same as TBS in CAN1GSR).
9 TBS2 When 1, all 3 Tx Buffers of the CAN2 controller are available to the CPU 1
(same as TBS in CAN2GSR).
16 TCS1 When 1, all requested transmissions have been completed successfully 1
by the CAN1 controller (same as TCS in CAN1GSR).
17:16 TCS2 When 1, all requested transmissions have been completed successfully 1
by the CAN2 controller (same as TCS in CAN2GSR).

12.10.2 Central Receive Status Register (CANRxSR - 0xE004 0004)

Table 242. Central Receive Status Register (CANRxSR - address 0xE004 0004) bit
description
Value
0 RS1 When 1, CAN1 is receiving a message (same as RS in CAN1GSR). 0
1 RS2 When 1, CAN2 is receiving a message (same as RS in CAN2GSR). 0
8 RB1 When 1, a received message is available in the CAN1 controller (same 0
as RBS in CAN1GSR).
9 RB2 When 1, a received message is available in the CAN2 controller (same 0
as RBS in CAN2GSR).
16 DOS1 When 1, a message was lost because the preceding message to CAN1 0
controller was not read out quickly enough (same as DOS in CAN1GSR).
17:16 DOS2 When 1, a message was lost because the preceding message to CAN2 0
controller was not read out quickly enough (same as DOS in CAN2GSR).
12.10.3 Central Miscellaneous Status Register (CANMSR - 0xE004 0008)

Table 243. Central Miscellaneous Status Register (CANMSR - address 0xE004 0008) bit
description
Value
0 E1 When 1, one or both of the CAN1 Tx and Rx Error Counters has reached 0
the limit set in the CAN1EWL register (same as ES in CAN1GSR)
1 E2 When 1, one or both of the CAN2 Tx and Rx Error Counters has reached 0
the limit set in the CAN2EWL register (same as ES in CAN2GSR)
8 BS1 When 1, the CAN controller is currently not involved/prohibited from bus 0
activity (same as BS in CAN1GSR).
9 BS2 When 1, the CAN controller is currently not involved/prohibited from bus 0
activity (same as BS in CAN1GSR).
12.11 Global acceptance filter

This block provides lookup for received Identifiers (called Acceptance Filtering in CAN
terminology) for all the CAN Controllers. It includes a 512 x 32 (2 kB) RAM in which
software maintains one to five tables of Identifiers. This RAM can contain up to 1024
Standard Identifiers or 512 Extended Identifiers, or a mixture of both types.

12.12 Acceptance filter modes

The Acceptance Filter can be put into different modes by setting the according AccOff,
AccBP, and eFCAN bits in the Acceptance Filter Mode Register (Section 12.15.1
“Acceptance Filter Mode Register (AFMR - 0xE003 C000)”). During each mode the
access to the Configuration Register and the ID Look-up table is handled differently.
Table 244. Acceptance filter modes and access control

Acceptance Bit Bit Acceptance ID Look-up Acceptanc CAN controller
filter mode AccOff AccBP filter state table e filter message receive
RAM[1] config.
registers
Off Mode 1 0 reset & r/w access r/w access no messages
halted from CPU from CPU accepted
Bypass X 1 reset & r/w access r/w access all messages
Mode halted from CPU from CPU accepted
Operating 0 0 running read only access from hardware
Mode and from CPU[2] Acceptance acceptance filtering
FullCAN filter only
Mode
[1] The whole ID Look-up Table RAM is only word accessible.

[2] During the Operating Mode of the Acceptance Filter the Look-up Table can be accessed only to disable or
enable Messages.
A write access to all section configuration registers is only possible during the Acceptance
Filter Off and Bypass Mode. Read access is allowed in all Acceptance Filter Modes.
12.12.1 Acceptance filter Off mode

The Acceptance Filter Off Mode is typically used during initialization. During this mode an
unconditional access to all registers and to the Look-up Table RAM is possible. With the
Acceptance Filter Off Mode, CAN messages are not accepted and therefore not stored in
the Receive Buffers of active CAN Controllers.
12.12.2 Acceptance filter Bypass mode

The Acceptance Filter Bypass Mode can be used for example to change the acceptance
filter configuration during a running system, e.g. change of identifiers in the ID-Look-up
Table memory. During this re-configuration, software acceptance filtering has to be used.
It is recommended to use the ID ready Interrupt (ID Index) and the Receive Interrupt (RI).
In this mode all CAN message are accepted and stored in the Receive Buffers of active
CAN Controllers.
12.12.3 Acceptance filter Operating mode

The Acceptance Filter is in Operating Mode when neither the AccOff nor the AccBP in the
Configuration Register is set and the eFCAN = 0.

12.12.4 FullCAN mode

The Acceptance Filter is in Operating Mode when neither the AccOff nor the AccBP in the
Configuration Register is set and the eFCAN = 1. More details on FullCAN mode are
available in Section 12.17 “FullCAN mode”.
12.13 Sections of the ID look-up table RAM

Four 12-bit section configuration registers (SFF_sa, SFF_GRP_sa, EFF_sa,
EFF_GRP_sa) are used to define the boundaries of the different identifier sections in the
ID-Look-up Table Memory. The fifth 12-bit section configuration register, the End of Table
address register (ENDofTable) is used to define the end of all identifier sections. The End
of Table address is also used to assign the start address of the section where FullCAN
Message Objects, if enabled are stored.
Table 245. Section configuration register settings

ID-Look up Table Section Register Value Section
status
FullCAN (Standard Frame Format) Identifier Section SFF_sa = 0x000 disabled
> 0x000 enabled
Explicit Standard Frame Format Identifier Section SFF_GRP_sa = SFF_sa disabled
> SFF_sa enabled
Group of Standard Frame Format Identifier Section EFF_sa = SFF_GRP_sa disabled
> SFF_GRP_sa enabled
Explicit Extended Frame Format Identifier Section EFF_GRP_sa = EFF_sa disabled
> EFF_sa enabled
Group of Extended Frame Format Identifier Section ENDofTable = EFF_GRP_sa disabled
> EFF_GRP_sa enabled
12.14 ID look-up table RAM

The Whole ID Look-up Table RAM is only word accessible. A write access is only possible
during the Acceptance Filter Off or Bypass Mode. Read access is allowed in all
Acceptance Filter Modes.
If Standard (11 bit) Identifiers are used in the application, at least one of 3 tables in
Acceptance Filter RAM must not be empty. If the optional “fullCAN mode” is enabled, the
first table contains Standard identifiers for which reception is to be handled in this mode.
The next table contains individual Standard Identifiers and the third contains ranges of
Standard Identifiers, for which messages are to be received via the CAN Controllers. The
tables of fullCAN and individual Standard Identifiers must be arranged in ascending
numerical order, one per halfword, two per word. Since each CAN bus has its own
address map, each entry also contains the number of the CAN Controller (SCC = 000
(CAN1) -or SCC = 001 (CAN2)) to which it applies.

31 29 26 16
15 13 10 0
DIS NOT
CONTROLLER # IDENTIFIER
ABLE USED
Fig 46. Entry in FullCAN and individual standard identifier tables
The table of Standard Identifier Ranges contains paired upper and lower (inclusive)
bounds, one pair per word. These must also be arranged in ascending numerical order.
31 29 26 16 10 0
NOT USED
NOT USED
DISABLE
DISABLE
CONTROLLER LOWER IDENTIFIER CONTROLLER UPPER IDENTIFIER
# BOUND # BOUND
Fig 47. Entry in standard identifier range table
The disable bits in Standard entries provide a means to turn response, to particular CAN
Identifiers or ranges of Identifiers, on and off dynamically. When the Acceptance Filter
function is enabled, only the disable bits in Acceptance Filter RAM can be changed by
software. Response to a range of Standard addresses can be enabled by writing 32 zero
bits to its word in RAM, and turned off by writing 32 one bits (0xFFFF FFFF) to its word in
RAM. Only the disable bits are actually changed. Disabled entries must maintain the
ascending sequence of Identifiers.
If Extended (29 bit) Identifiers are used in the application, at least one of the other two
tables in Acceptance Filter RAM must not be empty, one for individual Extended Identifiers
and one for ranges of Extended Identifiers. The table of individual Extended Identifiers
must be arranged in ascending numerical order.
31 29 28 0
CONTROLLER # IDENTIFIER
Fig 48. Entry in either extended identifier table
The table of ranges of Extended Identifiers must contain an even number of entries, of the
same form as in the individual Extended Identifier table. Like the Individual Extended
table, the Extended Range must be arranged in ascending numerical order. The first and
second (3rd and 4th …) entries in the table are implicitly paired as an inclusive range of
Extended addresses, such that any received address that falls in the inclusive range is
received (accepted). Software must maintain the table to consist of such word pairs.
There is no facility to receive messages to Extended identifiers using the fullCAN method.

Five address registers point to the boundaries between the tables in Acceptance Filter
RAM: fullCAN Standard addresses, Standard Individual addresses, Standard address
ranges, Extended Individual addresses, and Extended address ranges. These tables
must be consecutive in memory. The start of each of the latter four tables is implicitly the
end of the preceding table. The end of the Extended range table is given in an End of
Tables register. If the start address of a table equals the start of the next table or the End
Of Tables register, that table is empty.
When the Receive side of a CAN controller has received a complete Identifier, it signals
the Acceptance Filter of this fact. The Acceptance Filter responds to this signal, and reads
the Controller number, the size of the Identifier, and the Identifier itself from the Controller.
It then proceeds to search its RAM to determine whether the message should be received
or ignored.
If fullCAN mode is enabled and the CAN controller signals that the current message
contains a Standard identifier, the Acceptance Filter first searches the table of identifiers
for which reception is to be done in fullCAN mode. Otherwise, or if the AF doesn’t find a
match in the fullCAN table, it searches its individual Identifier table for the size of Identifier
signalled by the CAN controller. If it finds an equal match, the AF signals the CAN
controller to retain the message, and provides it with an ID Index value to store in its
Receive Frame Status register.
If the Acceptance Filter does not find a match in the appropriate individual Identifier table,
it then searches the Identifier Range table for the size of Identifier signalled by the CAN
controller. If the AF finds a match to a range in the table, it similarly signals the CAN
controller to retain the message, and provides it with an ID Index value to store in its
Receive Frame Status register. If the Acceptance Filter does not find a match in either the
individual or Range table for the size of Identifier received, it signals the CAN controller to
discard/ignore the received message.
12.15 Acceptance filter registers
12.15.1 Acceptance Filter Mode Register (AFMR - 0xE003 C000)

The AccBP and AccOff bits of the acceptance filter mode register are used for putting the
acceptance filter into the Bypass and Off mode. The eFCAN bit of the mode register can
be used to activate a FullCAN mode enhancement for received 11-bit CAN ID messages.
Table 246. Acceptance Filter Mode Register (AFMR - address 0xE003 C000) bit description
Value
0 AccOff[2] 1 if AccBP is 0, the Acceptance Filter is not operational. All Rx 1
messages on all CAN buses are ignored.
1 AccBP[1] 1 All Rx messages are accepted on enabled CAN controllers. 0
Software must set this bit before modifying the contents of any of
the registers described below, and before modifying the contents
of Lookup Table RAM in any way other than setting or clearing
Disable bits in Standard Identifier entries. When both this bit and
AccOff are 0, the Acceptance filter operates to screen received
CAN Identifiers.

Table 246. Acceptance Filter Mode Register (AFMR - address 0xE003 C000) bit description
Value
2 eFCAN[3] 0 Software must read all messages for all enabled IDs on all 0
enabled CAN buses, from the receiving CAN controllers.
1 The Acceptance Filter itself will take care of receiving and storing
messages for selected Standard ID values on selected CAN
buses. See Section 12.17 “FullCAN mode” on page 299.
[1] Acceptance Filter Bypass Mode (AccBP): By setting the AccBP bit in the Acceptance Filter Mode Register,
the Acceptance filter is put into the Acceptance Filter Bypass mode. During bypass mode, the internal state
machine of the Acceptance Filter is reset and halted. All received CAN messages are accepted, and
acceptance filtering can be done by software.
[2] Acceptance Filter Off mode (AccOff): After power-upon hardware reset, the Acceptance filter will be in Off
mode, the AccOff bit in the Acceptance filter Mode register 0 will be set to 1. The internal state machine of
the acceptance filter is reset and halted. If not in Off mode, setting the AccOff bit, either by hardware or by
software, will force the acceptance filter into Off mode.
[3] FullCan Mode Enhancements: A FullCan mode for received CAN messages can be enabled by setting the
eFCAN bit in the acceptance filter mode register.
12.15.2 Section configuration registers

The 10 bit section configuration registers are used for the ID look-up table RAM to indicate
the boundaries of the different sections for explicit and group of CAN identifiers for 11 bit
CAN and 29 bit CAN identifiers, respectively. The 10 bit wide section configuration
registers allow the use of a 512x32 (2 kB) look-up table RAM. The whole ID Look-up Table
RAM is only word accessible. All five section configuration registers contain APB
addresses for the acceptance filter RAM and do not include the APB base address. A
write access to all section configuration registers is only possible during the Acceptance
filter off and Bypass modes. Read access is allowed in all acceptance filter modes.
12.15.3 Standard Frame Individual Start Address Register (SFF_sa -

0xE003 C004)
Table 247. Standard Frame Individual Start Address Register (SFF_sa - address
0xE003 C004) bit description
Value
10:2 SFF_sa[1] The start address of the table of individual Standard Identifiers in AF 0
Lookup RAM. If the table is empty, write the same value in this register
and the SFF_GRP_sa register described below. For compatibility with
possible future devices, write zeroes in bits 31:11 and 1:0 of this
register. If the eFCAN bit in the AFMR is 1, this value also indicates the
size of the table of Standard IDs which the Acceptance Filter will search
and (if found) automatically store received messages in Acceptance
Filter RAM.

[1] Write access to the look-up table section configuration registers are possible only during the Acceptance
filter bypass mode or the Acceptance filter off mode.
12.15.4 Standard Frame Group Start Address Register (SFF_GRP_sa -

0xE003 C008)
Table 248. Standard Frame Group Start Address Register (SFF_GRP_sa - address
Value
11:2 SFF_GRP_sa[1] The start address of the table of grouped Standard Identifiers in 0
AF Lookup RAM. If the table is empty, write the same value in
this register and the EFF_sa register described below. The
largest value that should be written to this register is 0x800, when
only the Standard Individual table is used, and the last word
(address 0x7FC) in AF Lookup Table RAM is used. For
compatibility with possible future devices, please write zeroes in
bits 31:12 and 1:0 of this register.
12.15.5 Extended Frame Start Address Register (EFF_sa - 0xE003 C00C)

Table 249. Extended Frame Start Address Register (EFF_sa - address 0xE003 C00C) bit
description
Value
10:2 EFF_sa[1] The start address of the table of individual Extended Identifiers in AF 0
Lookup RAM. If the table is empty, write the same value in this register
and the EFF_GRP_sa register described below. The largest value that
should be written to this register is 0x800, when both Extended Tables
are empty and the last word (address 0x7FC) in AF Lookup Table RAM
is used. For compatibility with possible future devices, please write
zeroes in bits 31:11 and 1:0 of this register.

12.15.6 Extended Frame Group Start Address Register (EFF_GRP_sa -

0xE003 C010)
Table 250. Extended Frame Group Start Address Register (EFF_GRP_sa - address
Value
11:2 Eff_GRP_sa[1] The start address of the table of grouped Extended Identifiers in 0
AF Lookup RAM. If the table is empty, write the same value in this
register and the ENDofTable register described below. The largest
value that should be written to this register is 0x800, when this
table is empty and the last word (address 0x7FC) in AF Lookup
Table RAM is used. For compatibility with possible future devices,
please write zeroes in bits 31:12 and 1:0 of this register.
12.15.7 End of AF Tables Register (ENDofTable - 0xE003 C014)

Table 251. End of AF Tables Register (ENDofTable - address 0xE003 C014) bit description
Value
11:2 EndofTable The address above the last active address in the last active AF table. 0
[1] For compatibility with possible future devices, please write zeroes in
bits 31:12 and 1:0 of this register.
If the eFCAN bit in the AFMR is 0, the largest value that should be
written to this register is 0x800, which allows the last word (address
0x7FC) in AF Lookup Table RAM to be used.
If the eFCAN bit in the AFMR is 1, this value marks the start of the
area of Acceptance Filter RAM, into which the Acceptance Filter will
automatically receive messages for selected IDs on selected CAN
buses. In this case, the maximum value that should be written to this
register is 0x800 minus 6 times the value in SFF_sa. This allows 12
bytes of message storage between this address and the end of
Acceptance Filter RAM, for each Standard ID that is specified
between the start of Acceptance Filter RAM, and the next active AF
table.
12.15.8 Status registers

The look-up table error status registers, the error addresses, and the flag register provide
information if a programming error in the look-up table RAM during the ID screening was
encountered. The look-up table error address and flag register have only read access. If

an error is detected, the LUTerror flag is set, and the LUTerrorAddr register provides the
information under which address during an ID screening an error in the look-up table was
encountered. Any read of the LUTerrorAddr Filter block can be used for a look-up table
interrupt.
12.15.9 LUT Error Address Register (LUTerrAd - 0xE003 C018)

Table 252. LUT Error Address Register (LUTerrAd - address 0xE003 C018) bit description
Value
10:2 LUTerrAd It the LUT Error bit (below) is 1, this read-only field contains the address 0
in AF Lookup Table RAM, at which the Acceptance Filter encountered
an error in the content of the tables.
12.15.10 LUT Error Register (LUTerr - 0xE003 C01C)

Table 253. LUT Error Register (LUTerr - address 0xE003 C01C) bit description
Value
0 LUTerr This read-only bit is set to 1 if the Acceptance Filter encounters an error 0
in the content of the tables in AF RAM. It is cleared when software reads
the LUTerrAd register. This condition is ORed with the “other CAN”
interrupts from the CAN controllers, to produce the request for a VIC
interrupt channel.
12.15.11 Global FullCANInterrupt Enable register (FCANIE - 0xE003 C020)

A write access to the Global FullCAN Interrupt Enable register is only possible when the
Acceptance Filter is in the off mode.
Table 254. Global FullCAN Enable register (FCANIE - address 0xE003 C020) bit description
Value
0 FCANIE Global FullCAN Interrupt Enable. When 1, this interrupt is enabled. 0
12.15.12 FullCAN Interrupt and Capture registers (FCANIC0 - 0xE003 C024 and
FCANIC1 - 0xE003 C028)
For detailed description on these two registers, see Section 12.17.2 “FullCAN interrupts”.

Table 255. FullCAN Interrupt and Capture register 0 (FCANIC0 - address 0xE003 C024) bit
description
Value
0 IntPnd0 FullCan Interrupt Pending bit 0. 0
... IntPndx (0<x<31) FullCan Interrupt Pending bit x. 0
Table 256. FullCAN Interrupt and Capture register 1 (FCANIC1 - address 0xE003 C028) bit
description
Value
... IntPndx (32<x<63) FullCan Interrupt Pending bit x. 0
12.16 Configuration and search algorithm

The CAN Identifier Look-up Table Memory can contain explicit identifiers and groups of
CAN identifiers for Standard and Extended CAN Frame Formats. They are organized as a
sorted list or table with an increasing order of the Source CAN Channel (SCC) together
with CAN Identifier in each section.
SCC value equals CAN_controller - 1, i.e., SCC = 0 matches CAN1 and SCC = 1
matches CAN2.
Every CAN identifier is linked to an ID Index number. In case of a CAN Identifier match,
the matching ID Index is stored in the Identifier Index of the Frame Status Register
(CANRFS) of the according CAN Controller.
12.16.1 Acceptance filter search algorithm

The identifier screening process of the acceptance filter starts in the following order:
1. FullCAN (Standard Frame Format) Identifier Section

2. Explicit Standard Frame Format Identifier Section
3. Group of Standard Frame Format Identifier Section
4. Explicit Extended Frame Format Identifier Section
5. Group of Extended Frame Format Identifier Section
Note: Only activated sections will take part in the screening process.
In cases where equal message identifiers of same frame format are defined in more than
one section, the first match will end the screening process for this identifier.
For example, if the same Source CAN Channel in conjunction with the identifier is defined
in the FullCAN, the Explicit Standard Frame Format and the Group of Standard Frame
Format Identifier Sections, the screening will already be finished with the match in the
FullCAN section.

In the example of Figure 49, Identifiers with their Source CAN Channel have been defined
in the FullCAN, Explicit and Group of Standard Frame Format Identifier Sections.
Message Message
disable bit disable bit
Index 0, 1 SCC = 0 0 ID = 0x5A SCC 0 ... FullCAN

Explicit
Index 2, 3 SCC 0 ... SCC 0 ... Standard
Frame
Index 4, 5 SCC 0 ... SCC 0 ... Format
Identifier
Index 6, 7 SCC 0 ... SCC 0 ... Section
Explicit
Index 8, 9 SCC = 0 0 ID = 0x5A SCC 0 ...
Standard
Frame
Index 10, 11 SCC 0 ... SCC 0 ...
Format
Identifier
Index 12, 13 SCC 0 ... SCC 0 ...
Section
Group of
Index 14 SCC = 0 0 ID = 0x5A SCC = 0 0 ID = 0x5F
0x5A Standard
Frame
Index 15 SCC 0 ... SCC 0 ... Format
Identifier
Section
Fig 49. ID Look-up table example explaining the search algorithm
The identifier 0x5A of the CAN Controller 1 with the Source CAN Channel SCC = 0, is
defined in all three sections. With this configuration incoming CAN messages on CAN
Controller 1 with a 0x5A identifier will find a match in the FullCAN section.
It is possible to disable the ‘0x5A identifier’ in the FullCAN section. With that, the
screening process would be finished with the match in the Explicit Identifier Section.
The first group in the Group Identifier Section has been defined such that incoming CAN
messages with identifiers of 0x5A up to 0x5F are accepted on CAN Controller 1 with the
Source CAN Channel SCC = 0. As stated above, the identifier 0x5A would find a match
already in the FullCAN or in the Explicit Identifier section if enabled. The rest of the
defined identifiers of this group (0x5B to 0x5F) will find a match in this Group Identifier
Section.
This way the user can switch dynamically between different filter modes for the same
identifiers.
12.17 FullCAN mode

The FullCAN mode is based on capabilities provided by the CAN Gateway module used in
the LPC2000 family of products. This block uses the Acceptance Filter to provide filtering
for both CAN channels.

The concept of the CAN Gateway block is mainly based on a BasicCAN functionality. This
concept fits perfectly in systems where a gateway is used to transfer messages or
message data between different CAN channels. A BasicCAN device is generating a
receive interrupt whenever a CAN message is accepted and received. Software has to
move the received message out of the receive buffer from the according CAN controller
into the user RAM.
To cover dashboard like applications where the controller typically receives data from
several CAN channels for further processing, the CAN Gateway block was extended by a
so-called FullCAN receive function. This additional feature uses an internal message
handler to move received FullCAN messages from the receive buffer of the according
CAN controller into the FullCAN message object data space of Look-up Table RAM.
When fullCAN mode is enabled, the Acceptance Filter itself takes care of receiving and
storing messages for selected Standard ID values on selected CAN buses, in the style of
“FullCAN” controllers.
In order to set this bit and use this mode, two other conditions must be met with respect to
the contents of Acceptance Filter RAM and the pointers into it:
• The Standard Frame Individual Start Address Register (SFF_sa) must be greater than
or equal to the number of IDs for which automatic receive storage is to be done, times
two. SFF_sa must be rounded up to a multiple of 4 if necessary.
• The EndOfTable register must be less than or equal to 0x800 minus 6 times the
SFF_sa value, to allow 12 bytes of message storage for each ID for which automatic
receive storage will be done.
When these conditions are met and eFCAN is set:
• The area between the start of Acceptance Filter RAM and the SFF_sa address, is
used for a table of individual Standard IDs and CAN Controller/bus identification,
sorted in ascending order and in the same format as in the Individual Standard ID
table (see Figure 46 “Entry in FullCAN and individual standard identifier tables” on
page 292). Entries can be marked as “disabled” as in the other Standard tables. If
there are an odd number of “FullCAN” ID’s, at least one entry in this table must be so
marked.
• The first (SFF_sa)/2 IDindex values are assigned to these automatically-stored ID’s.
That is, IDindex values stored in the Rx Frame Status Register, for IDs not handled in
this way, are increased by (SFF_sa)/2 compared to the values they would have when
eFCAN is 0.
• When a Standard ID is received, the Acceptance Filter searches this table before the
Standard Individual and Group tables.
• When a message is received for a controller and ID in this table, the Acceptance filter
reads the received message out of the CAN controller and stores it in Acceptance
Filter RAM, starting at (EndOfTable) + its IDindex*12.
• The format of such messages is shown in Table 257.

12.17.1 FullCAN message layout

Table 257. Format of automatically stored Rx messages
Address 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1 9 8 7 6 5 4 3 2 1 0
1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
0 F R 0000 SEM 0000 DLC 00000 ID.28 ... ID.18
F T [1:0]
R
+4 Rx Data 4 Rx Data 3 Rx Data 2 Rx Data 1
+8 Rx Data 8 Rx Data 7 Rx Data 6 Rx Data 5
The FF, RTR, and DLC fields are as described in Table 229.
Since the FullCAN message object section of the Look-up table RAM can be accessed
both by the Acceptance Filter and the CPU, there is a method for insuring that no CPU
reads from FullCAN message object occurs while the Acceptance Filter hardware is
writing to that object.
For this purpose the Acceptance Filter uses a 3-state semaphore, encoded with the two
semaphore bits SEM1 and SEM0 (see Table 257 “Format of automatically stored Rx
messages”) for each message object. This mechanism provides the CPU with information
about the current state of the Acceptance Filter activity in the FullCAN message object
section.
The semaphore operates in the following manner:
Table 258. FullCAN semaphore operation

SEM1 SEM0 activity
0 1 Acceptance Filter is updating the content
1 1 Acceptance Filter has finished updating the content
0 0 CPU is in process of reading from the Acceptance Filter
Prior to writing the first data byte into a message object, the Acceptance Filter will write
the FrameInfo byte into the according buffer location with SEM[1:0] = 01.
After having written the last data byte into the message object, the Acceptance Filter will
update the semaphore bits by setting SEM[1:0] = 11.
Before reading a message object, the CPU should read SEM[1:0] to determine the current
state of the Acceptance Filter activity therein. If SEM[1:0] = 01, then the Acceptance Filter
is currently active in this message object. If SEM[1:0] = 11, then the message object is
available to be read.
Before the CPU begins reading from the message object, it should clear SEM[1:0] = 00.
When the CPU is finished reading, it can check SEM[1:0] again. At the time of this final
check, if SEM[1:0] = 01 or 11, then the Acceptance Filter has updated the message object
during the time when the CPU reads were taking place, and the CPU should discard the
data. If, on the other hand, SEM[1:0] = 00 as expected, then valid data has been
successfully read by the CPU.
Figure 50 shows how software should use the SEM field to ensure that all three words
read from the message are all from the same received message.

START
read 1st word
SEM == 01?
this message has not been

SEM == 11?
received since last check
clear SEM, write back 1st word
read 2nd and 3rd words
read 1st word
SEM == 00?
most recently read 1st, 2nd, and

3rd words are from the same
message
Fig 50. Semaphore procedure for reading an auto-stored message

12.17.2 FullCAN interrupts

The CAN Gateway Block contains a 2 kB ID Look-up Table RAM. With this size a
maximum number of 146 FullCAN objects can be defined if the whole Look-up Table RAM
is used for FullCAN objects only. Only the first 64 FullCAN objects can be configured to
participate in the interrupt scheme. It is still possible to define more than 64 FullCAN
objects. The only difference is, that the remaining FullCAN objects will not provide a
FullCAN interrupt.
The FullCAN Interrupt Register-set contains interrupt flags (IntPndx) for (pending)
FullCAN receive interrupts. As soon as a FullCAN message is received, the according
interrupt bit (IntPndx) in the FCAN Interrupt Register gets asserted. In case that the Global
FullCAN Interrupt Enable bit is set, the FullCAN Receive Interrupt is passed to the
Vectored Interrupt Controller.
Application Software has to solve the following:
1. Index/Object number calculation based on the bit position in the FCANIC Interrupt
Register for more than one pending interrupt.
2. Interrupt priority handling if more than one FullCAN receive interrupt is pending.
The software that covers the interrupt priority handling has to assign a receive interrupt
priority to every FullCAN object. If more than one interrupt is pending, then the software
has to decide, which received FullCAN object has to be served next.
To each FullCAN object a new FullCAN Interrupt Enable bit (FCANIntxEn) is added, so
that it is possible to enable or disable FullCAN interrupts for each object individually. The
new Message Lost flag (MsgLstx) is introduced to indicate whether more than one
FullCAN message has been received since last time this message object was read by the
CPU. The Interrupt Enable and the Message Lost bits reside in the existing Look-up Table
RAM.
12.17.2.1 FullCAN message interrupt enable bit

In Figure 51 8 FullCAN Identifiers with their Source CAN Channel are defined in the
FullCAN, Section. The new introduced FullCAN Message Interrupt enable bit can be used
to enable for each FullCAN message an Interrupt.

Message Message
3 2 1
1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
Index 0, 1 SCC 0 11-bit CAN ID SCC 0 11-bit CAN ID FullCAN

Explicit
Index 2, 3 SCC 0 11-bit CAN ID SCC 0 11-bit CAN ID Standard
Frame
Index 4, 5 SCC 0 11-bit CAN ID SCC 0 11-bit CAN ID Format
Identifier
Index 6, 7 SCC 0 11-bit CAN ID SCC 0 11-bit CAN ID Section
New: New:
FullCAN FullCAN
Message Message
Interrupt Interrupt
enable bit enable bit
Fig 51. FullCAN section example of the ID look-up table
12.17.2.2 Message lost bit and CAN channel number

Figure 52 is the detailed layout structure of one FullCAN message stored in the FullCAN
message object section of the Look-up Table.
New: New:
FullCAN CAN
Message Source
lost bit Channel
APB 31 24 23 16 15 10 9 8 7 0
Base +
R S S
F T
E E un- ID.2 ID.1
Msg_ObjAddr + 0 unused M M unused RX DLC SCC ............................
R used 8 8
F 1 0
Msg_ObjAddr + 4 RX Data 4 RX Data 3 RX Data 2 RX Data 1
Msg_ObjAddr + 8 RX Data 8 RX Data 7 RX Data 6 RX Data 5
Fig 52. FullCAN message object layout
The new message lost bit (MsgLst) is introduced to indicate whether more than one
FullCAN message has been received since last time this message object was read. For
more information the CAN Source Channel (SCC) of the received FullCAN message is
added to Message Object.

12.17.2.3 Setting the interrupt pending bits (IntPnd 63 to 0)

The interrupt pending bit (IntPndx) gets asserted in case of an accepted FullCAN
message and if the interrupt of the according FullCAN Object is enabled (enable bit
FCANIntxEn) is set).
During the last write access from the data storage of a FullCAN message object the
interrupt pending bit of a FullCAN object (IntPndx) gets asserted.
12.17.2.4 Clearing the interrupt pending bits (IntPnd 63 to 0)

Each of the FullCAN Interrupt Pending requests gets cleared when the semaphore bits of
a message object are cleared by Software (ARM CPU).
12.17.2.5 Setting the message lost bit of a FullCAN message object (MsgLost 63 to 0)
The Message Lost bit of a FullCAN message object gets asserted in case of an accepted
FullCAN message and when the FullCAN Interrupt of the same object is asserted already.
During the first write access from the data storage of a FullCAN message object the
Message Lost bit of a FullCAN object (MsgLostx) gets asserted if the interrupt pending bit
is set already.
12.17.2.6 Clearing the message lost bit of a FullCAN message object (MsgLost 63 to
0)
The Message Lost bit of a FullCAN message object gets cleared when the FullCAN
Interrupt of the same object is not asserted.
During the first write access from the data storage of a FullCAN message object the
Message Lost bit of a FullCAN object (MsgLostx) gets cleared if the interrupt pending bit
is not set.
12.17.3 Set and clear mechanism of the FullCAN interrupt

Special precaution is needed for the built-in set and clear mechanism of the FullCAN
Interrupts. The following text illustrates how the already existing Semaphore Bits (see
Section 12.17.1 “FullCAN message layout” for more details) and how the new introduced
features (IntPndx, MsgLstx) will behave.
12.17.3.1 Scenario 1: Normal case, no message lost

Figure 53 below shows a typical “normal” scenario in which an accepted FullCAN
message is stored in the FullCAN Message Object Section. After storage the message is
read out by Software (ARM CPU).

semaphore
01 11 00
bits
IntPndx
look-up Write write write write read clear read read read
ID, SEM D1 D2 SEM SEM SEM D1 D2 SEM
table
access
MsgLostx
message ARM
handler processor
access access
Fig 53. Normal case, no messages lost
12.17.3.2 Scenario 2: Message lost

In this scenario a first FullCAN Message is stored and read out by Software (1st Object
write and read). In a second course a second message is stored (2nd Object write) but not
read out before a third message gets stored (3rd Object write). Since the FullCAN Interrupt
of that Object (IntPndx) is already asserted, the Message Lost Signal gets asserted.
semaphore 01 11 00 01 11 11
bits
IntPndx
look-up write write write

table write write write read clear read read read ID, write write write write write write
ID, ID,
D1 D2 SEM SEM SEM D1 D2 SEM SEM D1 D2 SEM D1 D2 SEM
access SEM SEM
1st Object 2nd Object 3rd Object

write write write
1st Object
read
MsgLostx
message ARM
handler processor
access access
Fig 54. Message lost

12.17.3.3 Scenario 3: Message gets overwritten indicated by Semaphore bits

This scenario is a special case in which the lost message is indicated by the existing
semaphore bits. The scenario is entered, if during a Software read of a message object
another new message gets stored by the message handler. In this case, the FullCAN
Interrupt bit gets set for a second time with the 2nd Object write.
semaphore 01 11 00 01 11 00
bits
IntPndx
look-up write write

write write write read clear read read read clear read read read
table ID, ID, write write write
D1 D2 SEM SEM SEM D1 D2 SEM SEM D1 D2 SEM
access SEM SEM D1 D2 SEM
1st Object 2nd Object

write write
2nd Object
1st Object read
read
Interrupt Service
Routine
MsgLostx
message ARM
handler processor
access access
Fig 55. Message gets overwritten
12.17.3.4 Scenario 3.1: Message gets overwritten indicated by Semaphore bits and
Message Lost
This scenario is a sub-case to Scenario 3 in which the lost message is indicated by the
existing semaphore bits and by Message Lost.

semaphore 01 11 00 01 11 00
bits
IntPndx
write write
look-up write write write read clear write write write read read read clear read read read
ID, ID,
table D1 D2 SEM SEM SEM D1 D2 SEM D1 D2 SEM SEM D1 D2 SEM
SEM SEM
access 1st Object 2nd Object
write write
1st Object read 2nd Object
read
Interrupt Service
Routine
MsgLostx
message ARM
handler processor
access access
Fig 56. Message overwritten indicated by semaphore bits and message lost
12.17.3.5 Scenario 3.2: Message gets overwritten indicated by Message Lost

This scenario is a sub-case to Scenario 3 in which the lost message is indicated by
Message Lost.

semaphore 01 11 01 11 00 01 11
bits
IntPndx
look-up write write write

write write write read write write write clear read read read write write write
table ID, ID, ID,
D1 D2 SEM SEM D1 D2 SEM SEM D1 D2 SEM D1 D2 SEM
access SEM SEM SEM

write write write
1st Object
read
Interrupt Service
Routine
MsgLostx
message ARM
handler processor
access access
Fig 57. Message overwritten indicated by message lost
12.17.3.6 Scenario 4: Clearing Message Lost bit

This scenario is a special case in which the lost message bit of an object gets set during
an overwrite of a none read message object (2nd Object write). The subsequent read out
of that object by Software (1st Object read) clears the pending Interrupt. The 3rd Object
write clears the Message Lost bit. Every “write ID, SEM” clears Message Lost bit if no
pending Interrupt of that object is set.

semaphore 01 11 01 11 00 11
bits
IntPndx
write write write

look-up write write write write write write read clear read read read write write write
ID, ID, ID,
D1 D2 SEM D1 D2 SEM SEM SEM D1 D2 SEM D1 D2 SEM
table SEM SEM SEM
access
write write write
1st Object
read
MsgLostx
message ARM
handler processor
access access
Fig 58. Clearing message lost
12.18 Examples of acceptance filter tables and ID index values
12.18.1 Example 1: only one section is used

SFF_sa < ENDofTable OR
SFF_GRP_sa < ENDofTable OR
EFF_sa < ENDofTable OR
EFF_GRP_sa < ENDofTable
The start address of a section is lower than the end address of all programmed CAN
identifiers.
12.18.2 Example 2: all sections are used

SFF_sa < SFF_GRP_sa AND
SFF_GRP_sa < EFF_sa AND
EFF_sa < EFF_GRP_sa AND
EFF_GRP_sa < ENDofTable
In cases of a section not being used, the start address has to be set onto the value of the
next section start address.
12.18.3 Example 3: more than one but not all sections are used
If the SFF group is not used, the start address of the SFF Group Section (SFF_GRP_sa
register) has to be set to the same value of the next section start address, in this case the
start address of the Explicit SFF Section (SFF_sa register).

In cases where explicit identifiers as well as groups of the identifiers are programmed, a
CAN identifier search has to start in the explicit identifier section first. If no match is found,
it continues the search in the group of identifier section. By this order it can be guaranteed
that in case where an explicit identifier match is found, the succeeding software can
directly proceed on this certain message whereas in case of a group of identifier match
the succeeding software needs more steps to identify the message.
12.18.4 Configuration example 4

Suppose that the five Acceptance Filter address registers contain the values shown in the
third column below. In this case each table contains the decimal number of words and
entries shown in the next two columns, and the ID Index field of the CANRFS register can
return the decimal values shown in the column ID Indexes for CAN messages whose
Identifiers match the entries in that table.
Table 259. Example of Acceptance Filter Tables and ID index Values

Table Register Value # Words # Entire ID Indexes
Standard Individual SFF_sa 0x040 810 1610 0-1510
Standard Group SFF_GRP_sa 0x060 410 410 16-1910
Extended Individual EFF_sa 0x070 810 1610 20-5510
Extended Group EFF_GRP_sa 0x100 810 1610 56-5710
ENDofTable 0x110

Figure 59 below is a more detailed and graphic example of the address registers, table
layout, and ID Index values. It shows:
• A Standard Individual table starting at the start of Acceptance Filter RAM and
containing 26 Identifiers, followed by:
• A Standard Group table containing 12 ranges of Identifiers, followed by:
• An Extended Individual table containing 3 Identifiers, followed by:
• An Extended Group table containing 2 ranges of Identifiers.

SFF_sa 000 d := 000 h := 0 0000 0000 b

look-up table RAM ID index #
APB base +
column_lower column_upper
address
0
00d = 00h 0 1
1
04d = 04h 2
2 3
explicit SFF table

3
22
44d = 2Ch 22 23
23
24
48d = 30h 24 25
25
2 6 26 d
52d = 34h
SFF_GRP_sa 52 d := 034 h := 0 0011 0100 b
group SFF table

84d = 54h lower_boundary 3 4 upper_boundary 34 d
88d = 58h lower_boundary 3 5 upper_boundary 35 d
92d = 5Ch lower_boundary 3 6 upper_boundary 36 d
EFF_sa 100 d := 064 h := 0 0110 0100 b
38 38 d
explicit EFF table

100d = 64h
104d = 68h 39 39 d
EFF_GRP_sa 112 d := 070 h := 0 0111 0000 b
lower_boundary 41 41 d
112d = 70h
group EFF table
116d = 74h upper_boundary
120d = 78h lower_boundary 42 42 d
124d = 7Ch upper_boundary
ENDofTable 128 d := 080 h := 0 1000 0000 b
Fig 59. Detailed example of acceptance filter tables and ID index values

The Table below shows which sections and therefore which types of CAN identifiers are
used and activated. The ID-Look-up Table configuration of this example is shown in
Figure 60.

Table 260. Used ID-Look-up Table sections

ID-Look-up Table Section Status
FullCAN not activated
Explicit Standard Frame Format activated
Group of Standard Frame Format activated
Explicit Extended Frame Format activated
Group of Extended Frame Format activated
Explicit standard frame format identifier section (11-bit CAN ID):

The start address of the Explicit Standard Frame Format section is defined in the SFF_sa
register with the value of 0x00. The end of this section is defined in the SFF_GRP_sa
register. In the Explicit Standard Frame Format section of the ID Look-up Table two CAN
Identifiers with their Source CAN Channels (SCC) share one 32-bit word. Not used or
disabled CAN Identifiers can be marked by setting the message disable bit.
Group of standard frame format identifier section (11-bit CAN ID):

The start address of the Group of Standard Frame Format section is defined with the
SFF_GRP_sa register with the value of 0x10. The end of this section is defined with the
EFF_sa register. In the Group of Standard Frame Format section two CAN Identifiers with
the same Source CAN Channel (SCC) share one 32-bit word and represent a range of
CAN Identifiers to be accepted. Bit 31 down to 16 represents the lower boundary and bit
15 down to 0 represents the upper boundary of the range of CAN Identifiers. All Identifiers
within this range (including the boundary identifiers) will be accepted. A whole group can
be disabled and not used by the acceptance filter by setting the message disable bit in the
upper and lower boundary identifier. To provide memory space for four Groups of
Standard Frame Format identifiers, the EFF_sa register value is set to 0x20. The identifier
group with the Index 9 of this section is not used and therefore disabled.
Explicit extended frame format identifier section (29-bit CAN ID, Figure 60)
The start address of the Explicit Extended Frame Format section is defined with the
EFF_sa register with the value of 0x20. The end of this section is defined with the
EFF_GRP_sa register. In the explicit Extended Frame Format section only one CAN
Identifier with its Source CAN Channel (SCC) is programmed per address line. To provide
memory space for four Explicit Extended Frame Format identifiers, the EFF_GRP_sa
register value is set to 0x30.
Group of extended frame format identifier section (29-bit CAN ID, Figure 60)
The start address of the Group of Extended Frame Format is defined with the
EFF_GRP_sa register with the value of 0x30. The end of this section is defined with the
End of Table address register (ENDofTable). In the Group of Extended Frame Format
section the boundaries are programmed with a pair of address lines; the first is the lower
boundary, the second the upper boundary. To provide memory space for two Groups of
Extended Frame Format Identifiers, the ENDofTable register value is set to 0x40.

Message Message
Index
SFF_sa MSB LSB MSB LSB

SCC 0 ID28 0 ID18 SCC 0 ID28 1 ID18
= 0x00 Explicit
MSB LSB MSB LSB
Standard SCC 0 ID28 2 ID18 SCC 0 ID28 3 ID18
Frame
MSB LSB MSB LSB
... Format SCC 0 ID28 4 ID18 SCC 0 ID28 5 ID18
Identifier
MSB LSB MSB LSB
Section SCC 0 ID28 6 ID18 SCC 1 ID28 Disabled, 7 ID18
SFF_GRP_sa MSB LSB MSB LSB

SCC 0 ID28 8 ID18 SCC 0 ID28 8 ID18 Group 8
= 0x10
Group of
MSB LSB MSB LSB Disabled
Standard SCC 1 ID28 Disabled, 9 ID18 SCC 1 ID28 Disabled, 9 ID18
Frame Group 9
MSB LSB MSB LSB
...Format SCC 1 ID28 10 ID18 SCC 1 ID28 10 ID18 Group 10
Identifier
MSB LSB MSB LSB
Section SCC 0 ID28 11 ID18 SCC 0
ID28 11 ID18 Group 11
EFF_sa MSB LSB
SCC ID28 12 ID0
= 0x20
Explicit
MSB LSB
Extended SCC ID28 13 ID0
Frame
MSB LSB
Format SCC ID28 14 ID0
Identifier
MSB LSB
Section SCC ID28 15 ID0
EFF_GRP_sa MSB LSB
= 0x30 SCC ID28 16 ID0
Group of Group 16
MSB LSB
Extended SCC ID28 16 ID0
Frame
MSB LSB
Format SCC ID28 17 ID0
Identifier Group 17
MSB LSB
Section SCC ID28 17 ID0
ENDofTable
= 0x40
Fig 60. ID Look-up table configuration example (no FullCAN)

The Table below shows which sections and therefore which types of CAN identifiers are
used and activated. The ID-Look-up Table configuration of this example is shown in
Figure 61.
This example uses a typical configuration in which FullCAN as well as Explicit Standard
Frame Format messages are defined. As described in Section 12.16.1 “Acceptance filter
search algorithm”, acceptance filtering takes place in a certain order. With the enabled
FullCAN section, the identifier screening process of the acceptance filter starts always in
the FullCAN section first, before it continues with the rest of enabled sections.e disabled.
Table 261. Used ID-Look-up Table sections

ID-Look-up Table Section Status
FullCAN activated and enabled
Explicit Standard Frame Format activated
Group of Standard Frame Format not activated
Explicit Extended Frame Format not activated
Group of Extended Frame Format not activated

FullCAN explicit standard frame format identifier section (11-bit CAN ID)
The start address of the FullCAN Explicit Standard Frame Format Identifier section is
(automatically) set to 0x00. The end of this section is defined in the SFF_sa register. In the
FullCAN ID section only identifiers of FullCAN Object are stored for acceptance filtering.
In this section two CAN Identifiers with their Source CAN Channels (SCC) share one
32-bit word. Not used or disabled CAN Identifiers can be marked by setting the message
disable bit. The FullCAN Object data for each defined identifier can be found in the
FullCAN Message Object section. In case of an identifier match during the acceptance
filter process, the received FullCAN message object data is moved from the Receive
Buffer of the appropriate CAN Controller into the FullCAN Message Object section. To
provide memory space for eight FullCAN, Explicit Standard Frame Format identifiers, the
SFF_sa register value is set to 0x10. The identifier with the Index 1 of this section is not
used and therefore disabled.
Explicit standard frame format identifier section (11-bit CAN ID)

The start address of the Explicit Standard Frame Format section is defined in the SFF_sa
register with the value of 0x10. The end of this section is defined in the End of Table
address register (ENDofTable). In the explicit Standard Frame Format section of the ID
Look-up Table two CAN Identifiers with their Source CAN Channel (SCC) share one 32-bit
word. Not used or disabled CAN Identifiers can be marked by setting the message disable
bit. To provide memory space for eight Explicit Standard Frame Format identifiers, the
ENDofTable register value is set to 0x20.
FullCAN message object data section

The start address of the FullCAN Message Object Data section is defined with the
ENDofTable register. The number of enabled FullCAN identifiers is limited to the available
memory space in the FullCAN Message Object Data section. Each defined FullCAN
Message needs three address lines for the Message Data in the FullCAN Message Object
Data section. The FullCAN Message Object section is organized in that way, that each
Index number of the FullCAN Identifier section corresponds to a Message Object Number
in the FullCAN Message Object section.

Message FullCAN Message FullCAN

Disable bit Interrupt Disable bit Interrupt
Enable bit Index Enable bit
MSB LSB
FullCAN SCC 0 0 0 SCC 1 1 MSB Disabled, 1 LSB
ID28 ID18 ID28 ID18
Explicit
0 1
MSB LSB 0 0 MSB LSB
Standard SCC ID28 2 ID18 SCC ID28 3 ID18
Frame
0 1
MSB LSB 0 0
MSB LSB
... Format SCC ID28 4 ID18 SCC 5 ID18
ID28
Identifier
0 1
MSB LSB 0 0
MSB LSB
Section SCC ID28 6 ID18 SCC ID28 7 ID18
SFF_sa MSB LSB MSB LSB
SCC 0 0 8 SCC 0 0 9
= 0x10 ID28 ID18 ID28 ID18
Explicit
Standard 0 0
MSB LSB 0 0
MSB LSB
SCC ID28 10 ID18 SCC ID28 11 ID18
Frame
MSB LSB MSB LSB
...Format SCC 0 0 12 SCC 0 0 13
ID28 ID18 ID28 ID18
Identifier
MSB LSB MSB LSB
Section SCC 0 0 14 SCC 0 0 15
ID28 ID18 ID28 ID18
ENDofTable =
FF RTR SEM DLC CAN-ID
SFF_GRP_sa =
EFF_sa = FullCAN Message Object
RXDATA 4, 3, 2, 1
EFF_GRP_sa = Data 0
Message
0x20
Object RXDATA 8, 7, 6, 5
section
Section No Message Data, disabled.
Message Object
No Message Data, disabled.
Data 1
No Message Data, disabled.
FF RTR SEM DLC CAN-ID

Message Object
RXDATA 4, 3, 2, 1
Data 2
RXDATA 8, 7, 6, 5
Fig 61. ID Look-up table configuration example (FullCAN activated and enabled)
12.18.8 Look-up table programming guidelines

All identifier sections of the ID Look-up Table have to be programmed in such a way, that
each active section is organized as a sorted list or table with an increasing order of the
Source CAN Channel (SCC) together with CAN Identifier in each section.
SCC value equals CAN_controller - 1, i.e., SCC = 0 matches CAN1 and SCC = 1
matches CAN2.
In cases, where a syntax error in the ID Look-up Table is encountered, the Look-up Table
address of the incorrect line is made available in the Look-up Table Error Address
Register (LUTerrAd).
The reporting process in the Look-up Table Error Address Register (LUTerrAd) is a
“run-time” process. Only those address lines with syntax error are reported, which were
passed through the acceptance filtering process.
The following general rules for programming the Look-up Table apply:

• Each section has to be organized as a sorted list or table with an increasing order of
the Source CAN Channel (SCC) in conjunction with the CAN Identifier (there is no
exception for disabled identifiers).
• The upper and lower bound in a Group of Identifiers definition has to be from the
same Source CAN Channel.
• To disable a Group of Identifiers the message disable bit has to be set for both, the
upper and lower bound.

UM10211
Chapter 13: LPC23XX USB device controller

This chapter describes the USB device controller for the following LPC23XX parts:
• LPC2361/62
• LPC2364/66/68
• LPC2378
• LPC2387
• LPC2388
LPC2365/67 and LPC2377 do not include a USB interface.

The USB controller is configured using the following registers:
1. Power: In the PCONP register (Table 56), set bit PCUSB.

Remark: On reset, the USB block is disabled (PCUSB = 0).
2. Clock: see Table 47.
3. Pins: Select USB pins and their modes in PINSEL0 to PINSEL5 and PINMODE0 to
4. Wake-up: Use the INTWAKE register (Table 55) to enable activity on the USB bus
port to wake up the microcontroller from Power-down mode.
(Table 76).
6. Initialization: see Section 13.13.
13.3 Introduction
The Universal Serial Bus (USB) is a four-wire bus that supports communication between a
host and one or more (up to 127) peripherals. The host controller allocates the USB
bandwidth to attached devices through a token-based protocol. The bus supports hot
plugging and dynamic configuration of the devices. All transactions are initiated by the
host controller.
The host schedules transactions in 1 ms frames. Each frame contains a Start-Of-Frame

(SOF) marker and transactions that transfer data to or from device endpoints. Each device
can have a maximum of 16 logical or 32 physical endpoints. There are four types of
transfers defined for the endpoints. Control transfers are used to configure the device.
Interrupt transfers are used for periodic data transfer. Bulk transfers are used when the
rate of transfer is not critical. Isochronous transfers have guaranteed delivery time but no
error correction.

For more information on the Universal Serial Bus, see the USB Implementers Forum web
site.
The USB device controller on the LPC23xx enables full-speed (12 Mb/s) data exchange
with a USB host controller.
Table 262. USB related acronyms, abbreviations, and definitions used in this chapter
Acronym/abbreviation Description
AHB Advanced High-performance bus
ATLE Auto Transfer Length Extraction
ATX Analog Transceiver
DD DMA Descriptor
DDP DMA Description Pointer
EOP End-Of-Packet
EP Endpoint
EP_RAM Endpoint RAM
FS Full Speed
LED Light Emitting Diode
LS Low Speed
MPS Maximum Packet Size
NAK Negative Acknowledge
PLL Phase Locked Loop
RAM Random Access Memory
SOF Start-Of-Frame
SIE Serial Interface Engine
SRAM Synchronous RAM
UDCA USB Device Communication Area
USB Universal Serial Bus
13.4 Features
• Fully compliant with the USB 2.0 specification (full speed).
• Supports 32 physical (16 logical) endpoints.
• Supports Control, Bulk, Interrupt and Isochronous endpoints.
• Scalable realization of endpoints at run time.
• Endpoint maximum packet size selection (up to USB maximum specification) by
software at run time.
• Supports SoftConnect and GoodLink features.
• Supports DMA transfers on all non-control endpoints.
• Allows dynamic switching between CPU controlled and DMA modes.
• Double buffer implementation for Bulk and Isochronous endpoints.

13.5 Fixed endpoint configuration

Table 263 shows the supported endpoint configurations. Endpoints are realized and
configured at run time using the Endpoint realization registers, documented in
Section 13.10.5 “Endpoint realization registers”.
Table 263. Fixed endpoint configuration

Logical Physical Endpoint type Direction Packet size (bytes) Double buffer
endpoint endpoint
0 0 Control Out 8, 16, 32, 64 No
0 1 Control In 8, 16, 32, 64 No
1 2 Interrupt Out 1 to 64 No
1 3 Interrupt In 1 to 64 No
2 4 Bulk Out 8, 16, 32, 64 Yes
2 5 Bulk In 8, 16, 32, 64 Yes
3 6 Isochronous Out 1 to 1023 Yes
3 7 Isochronous In 1 to 1023 Yes
5 10 Bulk Out 8, 16, 32, 64 Yes
5 11 Bulk In 8, 16, 32, 64 Yes
8 16 Bulk Out 8, 16, 32, 64 Yes
8 17 Bulk In 8, 16, 32, 64 Yes
11 22 Bulk Out 8, 16, 32, 64 Yes
11 23 Bulk In 8, 16, 32, 64 Yes
14 28 Bulk Out 8, 16, 32, 64 Yes
14 29 Bulk In 8, 16, 32, 64 Yes
15 30 Bulk Out 8, 16, 32, 64 Yes
15 31 Bulk In 8, 16, 32, 64 Yes

13.6 Functional description

The architecture of the USB device controller is shown below in Figure 62.
BUS VBUS
MASTER DMA
USB_CONNECT,
INTERFACE ENGINE
DMA interface USB_CONNECT1(
(AHB master) USB_CONNECT2(
USB_D+,
AHB BUS
USB ATX
EP_RAM SERIAL USB_D+1(1),
REGISTER
ACCESS INTERFACE USB_D-1(1)
INTERFACE
CONTROL ENGINE
USB_D-,
USB_D-1(1),
USB_D-2(1)
USB_UP_LED,
USB_UP_LED1(1),
register USB_UP_LED2(1)
interface EP_RAM
(AHB slave) USB DEVICE (4K)
BLOCK
(1) LPC2378 only

Fig 62. USB device controller block diagram
13.6.1 Analog transceiver

The USB Device Controller has a built-in analog transceiver (ATX). The USB ATX
sends/receives the bi-directional D+ and D- signals of the USB bus.
13.6.2 Serial Interface Engine (SIE)

The SIE implements the full USB protocol layer. It is completely hardwired for speed and
needs no firmware intervention. It handles transfer of data between the endpoint buffers in
EP_RAM and the USB bus. The functions of this block include: synchronization pattern
recognition, parallel/serial conversion, bit stuffing/de-stuffing, CRC checking/generation,
PID verification/generation, address recognition, and handshake evaluation/generation.
13.6.3 Endpoint RAM (EP_RAM)

Each endpoint buffer is implemented as an SRAM based FIFO. The SRAM dedicated for
this purpose is called the EP_RAM. Each realized endpoint has a reserved space in the
EP_RAM. The total EP_RAM space required depends on the number of realized
endpoints, the maximum packet size of the endpoint, and whether the endpoint supports
double buffering.
13.6.4 EP_RAM access control

The EP_RAM Access Control logic handles transfer of data from/to the EP_RAM and the
three sources that can access it: the CPU (via the Register Interface), the SIE, and the
DMA Engine.

13.6.5 DMA engine and bus master interface

When enabled for an endpoint, the DMA Engine transfers data between RAM on the AHB
bus and the endpoint’s buffer in EP_RAM. A single DMA channel is shared between all
endpoints. When transferring data, the DMA Engine functions as a master on the AHB
bus through the bus master interface.
13.6.6 Register interface

The Register Interface allows the CPU to control the operation of the USB Device
Controller. It also provides a way to write transmit data to the controller and read receive
data from the controller.
13.6.7 SoftConnect
The connection to the USB is accomplished by bringing D+ (for a full-speed device) HIGH
through a 1.5 kOhm pull-up resistor. The SoftConnect feature can be used to allow
software to finish its initialization sequence before deciding to establish connection to the
USB. Re-initialization of the USB bus connection can also be performed without having to
unplug the cable.
To use the SoftConnect feature, the CONNECT signal should control an external switch
that connects the 1.5 kOhm resistor between D+ and +3.3V. Software can then control the
CONNECT signal by writing to the CON bit using the SIE Set Device Status command.
13.6.8 GoodLink
Good USB connection indication is provided through GoodLink technology. When the
device is successfully enumerated and configured, the LED indicator will be permanently
ON. During suspend, the LED will be OFF.
This feature provides a user-friendly indicator on the status of the USB device. It is a
useful field diagnostics tool to isolate faulty equipment.
To use the GoodLink feature the UP_LED signal should control an LED. The UP_LED
signal is controlled using the SIE Configure Device command.
13.7 Operational overview

Transactions on the USB bus transfer data between device endpoints and the host. The
direction of a transaction is defined with respect to the host. OUT transactions transfer
data from the host to the device. IN transactions transfer data from the device to the host.
All transactions are initiated by the host controller.
For an OUT transaction, the USB ATX receives the bi-directional D+ and D- signals of the
USB bus. The Serial Interface Engine (SIE) receives the serial data from the ATX and
converts it into a parallel data stream. The parallel data is written to the corresponding
endpoint buffer in the EP_RAM.
For IN transactions, the SIE reads the parallel data from the endpoint buffer in EP_RAM,
converts it into serial data, and transmits it onto the USB bus using the USB ATX.

Once data has been received or sent, the endpoint buffer can be read or written. How this
is accomplished depends on the endpoint’s type and operating mode. The two operating
modes for each endpoint are Slave (CPU-controlled) mode, and DMA mode.
In Slave mode, the CPU transfers data between RAM and the endpoint buffer using the
Register Interface. See Section 13.14 “Slave mode operation” for a detailed description of
this mode.
In DMA mode, the DMA transfers data between RAM and the endpoint buffer. See
Section 13.15 “DMA operation” for a detailed description of this mode.

Table 264. USB external interface
Name Direction Description
VBUS I VBUS status input. When this function is not enabled
via its corresponding PINSEL register, it is driven
HIGH internally.
USB_CONNECT, O SoftConnect control signal.
USB_CONNECT1[1],
USB_CONNECT2[1]
USB_UP_LED, O GoodLink LED control signal.
USB_UP_LED1[1],
USB_UP_LED2[1]
USB_D+, USB_D+1[1], I/O Positive differential data.
USB_D+2[1]
USB_D-, USB_D-1[1], I/O Negative differential data.
USB_D-2[1]
[1] LPC2378 only.
13.8.1 LPC2378 usage note

For the LPC2378 only, the USB interface can be routed to either USB port1 (using
USB_CONNECT1, USB_UP_LED1, USB_D+1, USB_D) or USB port2 (using
USB_CONNECT2, USB_UP_LED2, USB_D+2, USB_D) to allow for more versatile pin
multiplexing (see Section 13.10.1.1 “USB Port Select register (USBPortSel - 0xFFE0
C110 – LPC2378 only)”).
13.8.2 LPC2388 usage note

It is not possible to configure both ports as USB device at the same time. To use both
ports for USB transfer, it is recommended to configure port1 as the host and port2 as the
device. See Section 6.3 “Connecting USB as one port host and one port device” on page
399 for details.
Remark: If port1 is configured as device and port2 is configured as host, the

USB_PWRD2 pin function is not available for monitoring the bus power of the host.

13.9 Clocking and power management

This section describes the clocking and power management features of the USB Device
Controller.
13.9.1 Power requirements

The USB protocol insists on power management by the device. This becomes very critical
if the device draws power from the bus (bus-powered device). The following constraints
should be met by a bus-powered device:
1. A device in the non-configured state should draw a maximum of 100 mA from the bus.
2. A configured device can draw only up to what is specified in the Max Power field of
the configuration descriptor. The maximum value is 500 mA.
3. A suspended device can draw a maximum of 500 A.
13.9.2 Clocks
The USB device controller clocks are shown in Table 265
Table 265. USB device controller clock sources

Clock source Description
AHB master clock Clock for the AHB master bus interface and DMA
AHB slave clock Clock for the AHB slave interface
usbclk 48 MHz clock from the USB clock divider, used to recover the
12 MHz clock from the USB bus
13.9.3 Power management support

To help conserve power, the USB device controller automatically disables the AHB master
clock and usbclk when not in use.
When the USB Device Controller goes into the suspend state (bus is idle for 3 ms), the
usbclk input to the device controller is automatically disabled, helping to conserve power.
However, if software wishes to access the device controller registers, usbclk must be
active. To allow access to the device controller registers while in the suspend state, the
USBClkCtrl and USBClkSt registers are provided.
When software wishes to access the device controller registers, it should first ensure
usbclk is enabled by setting DEV_CLK_EN in the USBClkCtrl register, and then poll the
corresponding DEV_CLK_ON bit in USBClkSt until set. Once set, usbclk will remain
enabled until DEV_CLK_EN is cleared by software.
When a DMA transfer occurs, the device controller automatically turns on the AHB master
clock. Once asserted, it remains active for a minimum of 2 ms (2 frames), to help ensure
that DMA throughput is not affected by turning off the AHB master clock. 2 ms after the
last DMA access, the AHB master clock is automatically disabled to help conserve power.
If desired, software also has the capability of forcing this clock to remain enabled using the
USBClkCtrl register.

Note that the AHB slave clock is always enabled as long as the PCUSB bit of PCONP is
set. When the device controller is not in use, all of the device controller clocks may be
disabled by clearing PCUSB.
The USB_NEED_CLK signal is used to facilitate going into and waking up from chip
Power Down mode. USB_NEED_CLK is asserted if any of the bits of the USBClkSt
register are asserted.
After entering the suspend state with DEV_CLK_EN and AHB_CLK_EN cleared, the
DEV_CLK_ON and AHB_CLK_ON will be cleared when the corresponding clock turns off.
When both bits are zero, USB_NEED_CLK will be low, indicating that the chip can be put
into Power Down mode by writing to the PCON register. The status of USB_NEED_CLK
can be read from the USBIntSt register.
Any bus activity in the suspend state will cause the USB_NEED_CLK signal to be
asserted. When the USB is configured to be a wake-up source from Power Down
(USBWAKE bit set in the INTWAKE register), the assertion of USB_NEED_CLK causes
the chip to wake up from Power Down mode.
13.9.4 Remote wake-up

The USB device controller supports software initiated remote wake-up. Remote wake-up
involves resume signaling on the USB bus initiated from the device. This is done by
clearing the SUS bit in the SIE Set Device Status register. Before writing into the register,
all the clocks to the device controller have to be enabled using the USBClkCtrl register.

Table 266 shows the USB Device Controller registers directly accessible by the CPU. The
Serial Interface Engine (SIE) has other registers that are indirectly accessible via the SIE
command registers. See Section 13.12 “Serial interface engine command description” for
more info.
Table 266. USB device register map

Name Description Access Reset value[1] Address
Port select register (LPC2378 only)
USBPortSel USB Port Select R/W 0x0000 0000 0xFFE0 C110
Clock control registers
USBClkCtrl USB Clock Control R/W 0x0000 0000 0xFFE0 CFF4
USBClkSt USB Clock Status RO 0x0000 0000 0xFFE0 CFF8
Device interrupt registers
USBIntSt USB Interrupt Status R/W 0x8000 0000 0xE01F C1C0
USBDevIntSt USB Device Interrupt Status RO 0x0000 0010 0xFFE0 C200
USBDevIntEn USB Device Interrupt Enable R/W 0x0000 0000 0xFFE0 C204
USBDevIntClr USB Device Interrupt Clear WO 0x0000 0000 0xFFE0 C208
USBDevIntSet USB Device Interrupt Set WO 0x0000 0000 0xFFE0 C20C
USBDevIntPri USB Device Interrupt Priority WO 0x00 0xFFE0 C22C
Endpoint interrupt registers
USBEpIntSt USB Endpoint Interrupt Status RO 0x0000 0000 0xFFE0 C230

Table 266. USB device register map

Name Description Access Reset value[1] Address
USBEpIntEn USB Endpoint Interrupt Enable R/W 0x0000 0000 0xFFE0 C234
USBEpIntClr USB Endpoint Interrupt Clear WO 0x0000 0000 0xFFE0 C238
USBEpIntSet USB Endpoint Interrupt Set WO 0x0000 0000 0xFFE0 C23C
USBEpIntPri USB Endpoint Priority WO[3] 0x0000 0000 0xFFE0 C240
Endpoint realization registers
USBReEp USB Realize Endpoint R/W 0x0000 0003 0xFFE0 C244
USBEpInd USB Endpoint Index WO[3] 0x0000 0000 0xFFE0 C248
USBMaxPSize USB MaxPacketSize R/W 0x0000 0008 0xFFE0 C24C
USB transfer registers
USBRxData USB Receive Data RO 0x0000 0000 0xFFE0 C218
USBRxPLen USB Receive Packet Length RO 0x0000 0000 0xFFE0 C220
USBTxData USB Transmit Data WO[3] 0x0000 0000 0xFFE0 C21C
USBTxPLen USB Transmit Packet Length WO[3] 0x0000 0000 0xFFE0 C224
USBCtrl USB Control R/W 0x0000 0000 0xFFE0 C228
SIE Command registers
USBCmdCode USB Command Code WO[3] 0x0000 0000 0xFFE0 C210
USBCmdData USB Command Data RO 0x0000 0000 0xFFE0 C214
DMA registers
USBDMARSt USB DMA Request Status RO 0x0000 0000 0xFFE0 C250
USBDMARClr USB DMA Request Clear WO[3] 0x0000 0000 0xFFE0 C254
USBDMARSet USB DMA Request Set WO[3] 0x0000 0000 0xFFE0 C258
USBUDCAH USB UDCA Head R/W 0x0000 0000 0xFFE0 C280
USBEpDMASt USB Endpoint DMA Status RO 0x0000 0000 0xFFE0 C284
USBEpDMAEn USB Endpoint DMA Enable WO[3] 0x0000 0000 0xFFE0 C288
USBEpDMADis USB Endpoint DMA Disable WO[3] 0x0000 0000 0xFFE0 C28C
USBDMAIntSt USB DMA Interrupt Status RO 0x0000 0000 0xFFE0 C290
USBDMAIntEn USB DMA Interrupt Enable R/W 0x0000 0000 0xFFE0 C294
USBEoTIntSt USB End of Transfer Interrupt Status RO 0x0000 0000 0xFFE0 C2A0
USBEoTIntClr USB End of Transfer Interrupt Clear WO[3] 0x0000 0000 0xFFE0 C2A4
USBEoTIntSet USB End of Transfer Interrupt Set WO[3] 0x0000 0000 0xFFE0 C2A8
USBNDDRIntSt USB New DD Request Interrupt Status RO 0x0000 0000 0xFFE0 C2AC
USBNDDRIntClr USB New DD Request Interrupt Clear WO[3] 0x0000 0000 0xFFE0 C2B0
USBNDDRIntSet USB New DD Request Interrupt Set WO[3] 0x0000 0000 0xFFE0 C2B4
USBSysErrIntSt USB System Error Interrupt Status RO 0x0000 0000 0xFFE0 C2B8
USBSysErrIntClr USB System Error Interrupt Clear WO[3] 0x0000 0000 0xFFE0 C2BC
USBSysErrIntSet USB System Error Interrupt Set WO[3] 0x0000 0000 0xFFE0 C2C0
[2] The USBPortSel register is identical to the OTGStCtrl register (see Table 338). In device-only operations only bits 0 and 1 of this register
are used to control the routing of USB pins to port 1 or port 2.
[3] Reading WO register will return an invalid value.

13.10.1 Port select register
13.10.1.1 USB Port Select register (USBPortSel - 0xFFE0 C110 – LPC2378 only)
This register selects the USB port pins the USB device signals are routed to. USBPortSel
is a read/write register.
Table 267. USB Port Select register (USBPortSel - address 0xFFE0 C110) bit description
Bit Symbol Value Description Reset value
1:0 PORTSEL 0x0 The USB device controller signals are mapped to 0
the U1 port: USB_CONNECT1, USB_UP_LED1,
USB_D+1, USB_D-1.
0x3 The USB device controller signals are mapped to
the U2 port:USB_CONNECT2, USB_UP_LED2,
USB_D+2, USB_D-2.
not defined.
13.10.2 Clock control registers
13.10.2.1 USB Clock Control register (USBClkCtrl - 0xFFE0 CFF4)

This register controls the clocking of the USB Device Controller. Whenever software
wants to access the device controller registers, both DEV_CLK_EN and AHB_CLK_EN
must be set. The PORTSEL_CLK_EN bit need only be set when accessing the
USBPortSel register.
The software does not have to repeat this exercise for every register access, provided that
the corresponding USBClkCtrl bits are already set. Note that this register is functional only
when the PCUSB bit of PCONP is set; when PCUSB is cleared, all clocks to the device
controller are disabled irrespective of the contents of this register. USBClkCtrl is a
read/write register.
Table 268. USBClkCtrl register (USBClkCtrl - address 0xFFE0 CFF4) bit description
value
0 - Reserved, user software should not write ones to NA
not defined.
1 DEV_CLK_EN Device clock enable. Enables the usbclk input to the 0
device controller
not defined.
3 PORTSEL_CLK_EN Port select register clock enable(LPC2378 only). NA
4 AHB_CLK_EN AHB clock enable 0
not defined.

13.10.2.2 USB Clock Status register (USBClkSt - 0xFFE0 CFF8)

This register holds the clock availability status. The bits of this register are ORed together
to form the USB_NEED_CLK signal. When enabling a clock via USBClkCtrl, software
should poll the corresponding bit in USBClkSt. If it is set, then software can go ahead with
the register access. Software does not have to repeat this exercise for every access,
provided that the USBClkCtrl bits are not disturbed. USBClkSt is a read only register.
Table 269. USB Clock Status register (USBClkSt - 0xFFE0 CFF8) bit description
value
not defined.
1 DEV_CLK_ON Device clock on. The usbclk input to the device 0
controller is active.
not defined.
3 PORTSEL_CLK_ON Port select register clock on (LPC2378 only). NA
4 AHB_CLK_ON AHB clock on. 0
not defined.
13.10.3 Device interrupt registers
13.10.3.1 USB Interrupt Status register (USBIntSt - 0xE01F C1C0)

The USB Device Controller has three interrupt lines. This register allows software to
determine their status with a single read operation. All three interrupt lines are ORed
together to a single channel of the vectored interrupt controller. This register also contains
the USB_NEED_CLK status and EN_USB_INTS control bits. USBIntSt is a read/write
register.
Table 270. USB Interrupt Status register (USBIntSt - address 0xE01F C1C0) bit description
value
0 USB_INT_REQ_LP Low priority interrupt line status. This bit is read only. 0
1 USB_INT_REQ_HP High priority interrupt line status. This bit is read only. 0
2 USB_INT_REQ_DMA DMA interrupt line status. This bit is read only. 0

Table 270. USB Interrupt Status register (USBIntSt - address 0xE01F C1C0) bit description
value
8 USB_NEED_CLK USB need clock indicator. This bit is set to 1 when USB activity or a 0
change of state on the USB data pins is detected, and it indicates that a
PLL supplied clock of 48 MHz is needed. Once USB_NEED_CLK
becomes one, it resets to zero 5 ms after the last packet has been
received/sent, or 2 ms after the Suspend Change (SUS_CH) interrupt
has occurred. A change of this bit from 0 to 1 can wake up the
microcontroller if activity on the USB bus is selected to wake up the part
from the Power Down mode (see Section 4.8.8 “Interrupt Wakeup
Register (INTWAKE - 0xE01F C144)” for details). Also see
Section 4.6.10 “PLL and Power-down mode” and Section 4.8.9 “Power
Control for Peripherals register (PCONP - 0xE01F C0C4)” for
considerations about the PLL and invoking the Power Down mode. This
bit is read only.
31 EN_USB_INTS Enable all USB interrupts. When this bit is cleared, the Vectored 1
Interrupt Controller does not see the ORed output of the USB interrupt
lines.
13.10.3.2 USB Device Interrupt Status register (USBDevIntSt - 0xFFE0 C200)

The USBDevIntSt register holds the status of each interrupt. A 0 indicates no interrupt and
1 indicates the presence of the interrupt. USBDevIntSt is a read only register.
Table 271. USB Device Interrupt Status register (USBDevIntSt - address 0xFFE0 C200) bit allocation
Reset value: 0x0000 0000
Bit 31 30 29 28 27 26 25 24
Symbol - - - - - - - -
Bit 23 22 21 20 19 18 17 16
Symbol - - - - - - - -
Bit 15 14 13 12 11 10 9 8
Symbol - - - - - - ERR_INT EP_RLZED
Bit 7 6 5 4 3 2 1 0
Symbol TxENDPKT Rx CDFULL CCEMPTY DEV_STAT EP_SLOW EP_FAST FRAME
ENDPKT
Table 272. USB Device Interrupt Status register (USBDevIntSt - address 0xFFE0 C200) bit description
0 FRAME The frame interrupt occurs every 1 ms. This is used in isochronous packet transfers. 0
1 EP_FAST Fast endpoint interrupt. If an Endpoint Interrupt Priority register (USBEpIntPri) bit is 0
set, the corresponding endpoint interrupt will be routed to this bit.
2 EP_SLOW Slow endpoints interrupt. If an Endpoint Interrupt Priority Register (USBEpIntPri) bit is 0
not set, the corresponding endpoint interrupt will be routed to this bit.
3 DEV_STAT Set when USB Bus reset, USB suspend change or Connect change event occurs. 0
Refer to Section 13.12.6 “Set Device Status (Command: 0xFE, Data: write 1 byte)” on
page 355.
4 CCEMPTY The command code register (USBCmdCode) is empty (New command can be written). 1
5 CDFULL Command data register (USBCmdData) is full (Data can be read now). 0

Table 272. USB Device Interrupt Status register (USBDevIntSt - address 0xFFE0 C200) bit description
6 RxENDPKT The current packet in the endpoint buffer is transferred to the CPU. 0
7 TxENDPKT The number of data bytes transferred to the endpoint buffer equals the number of 0
bytes programmed in the TxPacket length register (USBTxPLen).
8 EP_RLZED Endpoints realized. Set when Realize Endpoint register (USBReEp) or MaxPacketSize 0
register (USBMaxPSize) is updated and the corresponding operation is completed.
9 ERR_INT Error Interrupt. Any bus error interrupt from the USB device. Refer to Section 13.12.9 0
“Read Error Status (Command: 0xFB, Data: read 1 byte)” on page 357
13.10.3.3 USB Device Interrupt Enable register (USBDevIntEn - 0xFFE0 C204)

Writing a one to a bit in this register enables the corresponding bit in USBDevIntSt to
generate an interrupt on one of the interrupt lines when set. By default, the interrupt is
routed to the USB_INT_REQ_LP interrupt line. Optionally, either the EP_FAST or FRAME
interrupt may be routed to the USB_INT_REQ_HP interrupt line by changing the value of
USBDevIntPri. USBDevIntEn is a read/write register.
Table 273. USB Device Interrupt Enable register (USBDevIntEn - address 0xFFE0 C204) bit allocation
Bit 31 30 29 28 27 26 25 24
Symbol - - - - - - - -
Bit 23 22 21 20 19 18 17 16
Symbol - - - - - - - -
Bit 15 14 13 12 11 10 9 8
Bit 7 6 5 4 3 2 1 0
ENDPKT
Table 274. USB Device Interrupt Enable register (USBDevIntEn - address 0xFFE0 C204) bit description
31:0 See 0 No interrupt is generated. 0
USBDevIntEn 1 An interrupt will be generated when the corresponding bit in the Device
bit allocation Interrupt Status (USBDevIntSt) register (Table 271) is set. By default, the
table above interrupt is routed to the USB_INT_REQ_LP interrupt line. Optionally, either
the EP_FAST or FRAME interrupt may be routed to the
USB_INT_REQ_HP interrupt line by changing the value of USBDevIntPri.
13.10.3.4 USB Device Interrupt Clear register (USBDevIntClr - 0xFFE0 C208)

Writing one to a bit in this register clears the corresponding bit in USBDevIntSt. Writing a
zero has no effect.
Remark: Before clearing the EP_SLOW or EP_FAST interrupt bits, the corresponding
endpoint interrupts in USBEpIntSt should be cleared.
USBDevIntClr is a write only register.

Table 275. USB Device Interrupt Clear register (USBDevIntClr - address 0xFFE0 C208) bit allocation
Bit 31 30 29 28 27 26 25 24
Symbol - - - - - - - -
Bit 23 22 21 20 19 18 17 16
Symbol - - - - - - - -
Bit 15 14 13 12 11 10 9 8
Bit 7 6 5 4 3 2 1 0
ENDPKT
Table 276. USB Device Interrupt Clear register (USBDevIntClr - address 0xFFE0 C208) bit description
31:0 See 0 No effect. 0
USBDevIntClr 1 The corresponding bit in USBDevIntSt (Section 13.10.3.2) is cleared.
bit allocation
table above
13.10.3.5 USB Device Interrupt Set register (USBDevIntSet - 0xFFE0 C20C)

Writing one to a bit in this register sets the corresponding bit in the USBDevIntSt. Writing a
zero has no effect
USBDevIntSet is a write only register.
Table 277. USB Device Interrupt Set register (USBDevIntSet - address 0xFFE0 C20C) bit allocation
Bit 31 30 29 28 27 26 25 24
Symbol - - - - - - - -
Bit 23 22 21 20 19 18 17 16
Symbol - - - - - - - -
Bit 15 14 13 12 11 10 9 8
Bit 7 6 5 4 3 2 1 0
ENDPKT
Table 278. USB Device Interrupt Set register (USBDevIntSet - address 0xFFE0 C20C) bit description
USBDevIntSet 1 The corresponding bit in USBDevIntSt (Section 13.10.3.2) is set.
bit allocation
table above

13.10.3.6 USB Device Interrupt Priority register (USBDevIntPri - 0xFFE0 C22C)

Writing one to a bit in this register causes the corresponding interrupt to be routed to the
USB_INT_REQ_HP interrupt line. Writing zero causes the interrupt to be routed to the
USB_INT_REQ_LP interrupt line. Either the EP_FAST or FRAME interrupt can be routed
to USB_INT_REQ_HP, but not both. If the software attempts to set both bits to one, no
interrupt will be routed to USB_INT_REQ_HP. USBDevIntPri is a write only register.
Table 279. USB Device Interrupt Priority register (USBDevIntPri - address 0xFFE0 C22C) bit description
0 FRAME 0 FRAME interrupt is routed to USB_INT_REQ_LP. 0
1 FRAME interrupt is routed to USB_INT_REQ_HP.
1 EP_FAST 0 EP_FAST interrupt is routed to USB_INT_REQ_LP. 0
1 EP_FAST interrupt is routed to USB_INT_REQ_HP.
7:2 - - Reserved, user software should not write ones to reserved bits. The value NA
13.10.4 Endpoint interrupt registers

The registers in this group facilitate handling of endpoint interrupts. Endpoint interrupts are
used in Slave mode operation.
13.10.4.1 USB Endpoint Interrupt Status register (USBEpIntSt - 0xFFE0 C230)

Each physical non-isochronous endpoint is represented by a bit in this register to indicate
that it has generated an interrupt. All non-isochronous OUT endpoints generate an
interrupt when they receive a packet without an error. All non-isochronous IN endpoints
generate an interrupt when a packet is successfully transmitted, or when a NAK
handshake is sent on the bus and the interrupt on NAK feature is enabled (see
Section 13.12.3 “Set Mode (Command: 0xF3, Data: write 1 byte)” on page 354). A bit set
to one in this register causes either the EP_FAST or EP_SLOW bit of USBDevIntSt to be
set depending on the value of the corresponding bit of USBEpDevIntPri. USBEpIntSt is a
read only register.
Note that for Isochronous endpoints, handling of packet data is done when the FRAME
interrupt occurs.
Table 280. USB Endpoint Interrupt Status register (USBEpIntSt - address 0xFFE0 C230) bit allocation
Bit 31 30 29 28 27 26 25 24
Symbol EP15TX EP15RX EP14TX EP14RX EP13TX EP13RX EP12TX EP12RX
Bit 23 22 21 20 19 18 17 16
Bit 15 14 13 12 11 10 9 8
Bit 7 6 5 4 3 2 1 0

Table 281. USB Endpoint Interrupt Status register (USBEpIntSt - address 0xFFE0 C230) bit description
0 EP0RX Endpoint 0, Data Received Interrupt bit. 0
1 EP0TX Endpoint 0, Data Transmitted Interrupt bit or sent a NAK. 0
6 EP3RX Endpoint 3, Isochronous endpoint. NA
7 EP3TX Endpoint 3, Isochronous endpoint. NA
13.10.4.2 USB Endpoint Interrupt Enable register (USBEpIntEn - 0xFFE0 C234)

Setting a bit to 1 in this register causes the corresponding bit in USBEpIntSt to be set
when an interrupt occurs for the associated endpoint. Setting a bit to 0 causes the
corresponding bit in USBDMARSt to be set when an interrupt occurs for the associated
endpoint. USBEpIntEn is a read/write register.

Table 282. USB Endpoint Interrupt Enable register (USBEpIntEn - address 0xFFE0 C234) bit allocation
Bit 31 30 29 28 27 26 25 24
Bit 23 22 21 20 19 18 17 16
Bit 15 14 13 12 11 10 9 8
Bit 7 6 5 4 3 2 1 0
Table 283. USB Endpoint Interrupt Enable register (USBEpIntEn - address 0xFFE0 C234) bit description
31:0 See 0 The corresponding bit in USBDMARSt is set when an interrupt occurs for 0
USBEpIntEn this endpoint.
bit allocation 1 The corresponding bit in USBEpIntSt is set when an interrupt occurs
table above for this endpoint. Implies Slave mode for this endpoint.
13.10.4.3 USB Endpoint Interrupt Clear register (USBEpIntClr - 0xFFE0 C238)

Writing a one to this a bit in this register causes the SIE Select Endpoint/Clear Interrupt
command to be executed (Table 327) for the corresponding physical endpoint. Writing
zero has no effect. Before executing the Select Endpoint/Clear Interrupt command, the
CDFULL bit in USBDevIntSt is cleared by hardware. On completion of the command, the
CDFULL bit is set, USBCmdData contains the status of the endpoint, and the
corresponding bit in USBEpIntSt is cleared.
Notes:
• When clearing interrupts using USBEpIntClr, software should wait for CDFULL to be
set to ensure the corresponding interrupt has been cleared before proceeding.
• While setting multiple bits in USBEpIntClr simultaneously is possible, it is not
recommended; only the status of the endpoint corresponding to the least significant
interrupt bit cleared will be available at the end of the operation.
• Alternatively, the SIE Select Endpoint/Clear Interrupt command can be directly
invoked using the SIE command registers, but using USBEpIntClr is recommended
because of its ease of use.
Each physical endpoint has its own reserved bit in this register. The bit field definition is
the same as that of USBEpIntSt shown in Table 280 . USBEpIntClr is a write only register.
Table 284. USB Endpoint Interrupt Clear register (USBEpIntClr - address 0xFFE0 C238) bit allocation
Bit 31 30 29 28 27 26 25 24
Bit 23 22 21 20 19 18 17 16
Bit 15 14 13 12 11 10 9 8

Bit 7 6 5 4 3 2 1 0
Table 285. USB Endpoint Interrupt Clear register (USBEpIntClr - address 0xFFE0 C238) bit description
USBEpIntClr 1 Clears the corresponding bit in USBEpIntSt, by executing the SIE Select
bit allocation Endpoint/Clear Interrupt command for this endpoint.
table above
13.10.4.4 USB Endpoint Interrupt Set register (USBEpIntSet - 0xFFE0 C23C)

Writing a one to a bit in this register sets the corresponding bit in USBEpIntSt. Writing zero
has no effect. Each endpoint has its own bit in this register. USBEpIntSet is a write only
register.
Table 286. USB Endpoint Interrupt Set register (USBEpIntSet - address 0xFFE0 C23C) bit allocation
Bit 31 30 29 28 27 26 25 24
Bit 23 22 21 20 19 18 17 16
Bit 15 14 13 12 11 10 9 8
Bit 7 6 5 4 3 2 1 0
Table 287. USB Endpoint Interrupt Set register (USBEpIntSet - address 0xFFE0 C23C) bit description
USBEpIntSet 1 Sets the corresponding bit in USBEpIntSt.
bit allocation
table above
13.10.4.5 USB Endpoint Interrupt Priority register (USBEpIntPri - 0xFFE0 C240)

This register determines whether an endpoint interrupt is routed to the EP_FAST or
EP_SLOW bits of USBDevIntSt. If a bit in this register is set to one, the interrupt is routed
to EP_FAST, if zero it is routed to EP_SLOW. Routing of multiple endpoints to EP_FAST
or EP_SLOW is possible.
Note that the USBDevIntPri register determines whether the EP_FAST interrupt is routed
to the USB_INT_REQ_HP or USB_INT_REQ_LP interrupt line.
USBEpIntPri is a write only register.
Table 288. USB Endpoint Interrupt Priority register (USBEpIntPri - address 0xFFE0 C240) bit allocation
Bit 31 30 29 28 27 26 25 24
Symbol EP15TX EP15RX EP14TX E14RX EP13TX EP13RX EP12TX EP12RX

Bit 23 22 21 20 19 18 17 16
Bit 15 14 13 12 11 10 9 8
Bit 7 6 5 4 3 2 1 0
Table 289. USB Endpoint Interrupt Priority register (USBEpIntPri - address 0xFFE0 C240) bit description
31:0 See 0 The corresponding interrupt is routed to the EP_SLOW bit of USBDevIntSt 0
USBEpIntPri 1 The corresponding interrupt is routed to the EP_FAST bit of USBDevIntSt
bit allocation
table above
13.10.5 Endpoint realization registers

The registers in this group allow realization and configuration of endpoints at run time.
13.10.5.1 EP RAM requirements

The USB device controller uses a RAM based FIFO for each endpoint buffer. The RAM
dedicated for this purpose is called the Endpoint RAM (EP_RAM). Each endpoint has
space reserved in the EP_RAM. The EP_RAM space required for an endpoint depends
on its MaxPacketSize and whether it is double buffered. 32 words of EP_RAM are used by
the device for storing the endpoint buffer pointers. The EP_RAM is word aligned but the
MaxPacketSize is defined in bytes hence the RAM depth has to be adjusted to the next
word boundary. Also, each buffer has one word header showing the size of the packet
length received.
The EP_ RAM space (in words) required for the physical endpoint can be expressed as
EPRAMspace =  -------------------------------------------------- + 1  dbstatus

MaxPacketSize + 3
 4 
where dbstatus = 1 for a single buffered endpoint and 2 for double a buffered endpoint.
Since all the realized endpoints occupy EP_RAM space, the total EP_RAM requirement is
TotalEPRAMspace = 32 +  EPRAMspace  n 
n=0
where N is the number of realized endpoints. Total EP_RAM space should not exceed
4096 bytes (4 kB, 1 kwords).

13.10.5.2 USB Realize Endpoint register (USBReEp - 0xFFE0 C244)

Writing one to a bit in this register causes the corresponding endpoint to be realized.
Writing zeros causes it to be unrealized. This register returns to its reset state when a bus
reset occurs. USBReEp is a read/write register.
Table 290. USB Realize Endpoint register (USBReEp - address 0xFFE0 C244) bit allocation
Bit 31 30 29 28 27 26 25 24
Symbol EP31 EP30 EP29 EP28 EP27 EP26 EP25 EP24
Bit 23 22 21 20 19 18 17 16
Bit 15 14 13 12 11 10 9 8
Bit 7 6 5 4 3 2 1 0
Table 291. USB Realize Endpoint register (USBReEp - address 0xFFE0 C244) bit description
0 EP0 0 Control endpoint EP0 is not realized. 1
1 Control endpoint EP0 is realized.
1 EP1 0 Control endpoint EP1 is not realized. 1
1 Control endpoint EP1 is realized.
31:2 EPxx 0 Endpoint EPxx is not realized. 0
1 Endpoint EPxx is realized.
On reset, only the control endpoints are realized. Other endpoints, if required, are realized
by programming the corresponding bits in USBReEp. To calculate the required EP_RAM
space for the realized endpoints, see Section 13.10.5.1.
Realization of endpoints is a multi-cycle operation. Pseudo code for endpoint realization is

shown below.
Clear EP_RLZED bit in USBDevIntSt;
for every endpoint to be realized,

{
/* OR with the existing value of the Realize Endpoint register */
USBReEp |= (UInt32) ((0x1 << endpt));
/* Load Endpoint index Reg with physical endpoint no.*/
USBEpIn = (UInt32) endpointnumber;
/* load the max packet size Register */

USBEpMaxPSize = MPS;
/* check whether the EP_RLZED bit in the Device Interrupt Status register is set
*/
while (!(USBDevIntSt & EP_RLZED))
{
/* wait until endpoint realization is complete */

}
/* Clear the EP_RLZED bit */
Clear EP_RLZED bit in USBDevIntSt;
}
The device will not respond to any transactions to unrealized endpoints. The SIE
Configure Device command will only cause realized and enabled endpoints to respond to
transactions. For details see Table 322.
13.10.5.3 USB Endpoint Index register (USBEpIn - 0xFFE0 C248)

Each endpoint has a register carrying the MaxPacketSize value for that endpoint. This is
in fact a register array. Hence before writing, this register is addressed through the
USBEpIn register.
The USBEpIn register will hold the physical endpoint number. Writing to USBMaxPSize
will set the array element pointed to by USBEpIn. USBEpIn is a write only register.
Table 292. USB Endpoint Index register (USBEpIn - address 0xFFE0 C248) bit description
4:0 PHY_EP Physical endpoint number (0-31) 0
13.10.5.4 USB MaxPacketSize register (USBMaxPSize - 0xFFE0 C24C)

On reset, the control endpoint is assigned the maximum packet size of 8 bytes. Other
endpoints are assigned 0. Modifying USBMaxPSize will cause the endpoint buffer
addresses within the EP_RAM to be recalculated. This is a multi-cycle process. At the
end, the EP_RLZED bit will be set in USBDevIntSt (Table 271). USBMaxPSize array
indexing is shown in Figure 63. USBMaxPSize is a read/write register.
Table 293. USB MaxPacketSize register (USBMaxPSize - address 0xFFE0 C24C) bit
description
9:0 MPS The maximum packet size value. 0x008[1]
[1] Reset value for EP0 and EP1. All other endpoints have a reset value of 0x0.
MPS_EP0
ENDPOINT INDEX
MPS_EP31
The Endpoint Index is set via the USBEpIn register. MPS_EP0 to MPS_EP31 are accessed via the
USBMaxPSize register.
Fig 63. USB MaxPacketSize register array indexing

13.10.6 USB transfer registers

The registers in this group are used for transferring data between endpoint buffers and
RAM in Slave mode operation. See Section 13.14 “Slave mode operation”.
13.10.6.1 USB Receive Data register (USBRxData - 0xFFE0 C218)

For an OUT transaction, the CPU reads the endpoint buffer data from this register. Before
reading this register, the RD_EN bit and LOG_ENDPOINT field of the USBCtrl register
should be set appropriately. On reading this register, data from the selected endpoint
buffer is fetched. The data is in little endian format: the first byte received from the USB
bus will be available in the least significant byte of USBRxData. USBRxData is a read only
register.
Table 294. USB Receive Data register (USBRxData - address 0xFFE0 C218) bit description
31:0 RX_DATA Data received. 0x0000 0000
13.10.6.2 USB Receive Packet Length register (USBRxPLen - 0xFFE0 C220)

This register contains the number of bytes remaining in the endpoint buffer for the current
packet being read via the USBRxData register, and a bit indicating whether the packet is
valid or not. Before reading this register, the RD_EN bit and LOG_ENDPOINT field of the
USBCtrl register should be set appropriately. This register is updated on each read of the
USBRxData register. USBRxPLen is a read only register.
Table 295. USB Receive Packet Length register (USBRxPlen - address 0xFFE0 C220) bit
description
value
9:0 PKT_LNGTH - The remaining number of bytes to be read from the 0
currently selected endpoint’s buffer. When this field
decrements to 0, the RxENDPKT bit will be set in
USBDevIntSt.
10 DV Data valid. This bit is useful for isochronous endpoints. 0
Non-isochronous endpoints do not raise an interrupt when
an erroneous data packet is received. But invalid data
packet can be produced with a bus reset. For isochronous
endpoints, data transfer will happen even if an erroneous
packet is received. In this case DV bit will not be set for the
packet.
0 Data is invalid.
1 Data is valid.
11 PKT_RDY - The PKT_LNGTH field is valid and the packet is ready for 0
reading.
13.10.6.3 USB Transmit Data register (USBTxData - 0xFFE0 C21C)

For an IN transaction, the CPU writes the endpoint data into this register. Before writing to
this register, the WR_EN bit and LOG_ENDPOINT field of the USBCtrl register should be
set appropriately, and the packet length should be written to the USBTxPlen register. On

writing this register, the data is written to the selected endpoint buffer. The data is in little
endian format: the first byte sent on the USB bus will be the least significant byte of
USBTxData. USBTxData is a write only register.
Table 296. USB Transmit Data register (USBTxData - address 0xFFE0 C21C) bit description
31:0 TX_DATA Transmit Data. 0x0000 0000
13.10.6.4 USB Transmit Packet Length register (USBTxPLen - 0xFFE0 C224)

This register contains the number of bytes transferred from the CPU to the selected
endpoint buffer. Before writing data to USBTxData, software should first write the packet
length (MaxPacketSize) to this register. After each write to USBTxData, hardware
decrements USBTxPLen by 4. The WR_EN bit and LOG_ENDPOINT field of the USBCtrl
register should be set to select the desired endpoint buffer before starting this process.
For data buffers larger than the endpoint’s MaxPacketSize, software should submit data in
packets of MaxPacketSize, and send the remaining extra bytes in the last packet. For
example, if the MaxPacketSize is 64 bytes and the data buffer to be transferred is of
length 130 bytes, then the software sends two 64-byte packets and the remaining 2 bytes
in the last packet. So, a total of 3 packets are sent on USB. USBTxPLen is a write only
register.
Table 297. USB Transmit Packet Length register (USBTxPLen - address 0xFFE0 C224) bit
description
value
9:0 PKT_LNGTH - The remaining number of bytes to be written to the 0x000
selected endpoint buffer. This field is decremented by 4 by
hardware after each write to USBTxData. When this field
decrements to 0, the TxENDPKT bit will be set in
USBDevIntSt.
13.10.6.5 USB Control register (USBCtrl - 0xFFE0 C228)

This register controls the data transfer operation of the USB device. It selects the endpoint
buffer that is accessed by the USBRxData and USBTxData registers, and enables
reading and writing them. USBCtrl is a read/write register.
Table 298. USB Control register (USBCtrl - address 0xFFE0 C228) bit description
value
0 RD_EN Read mode control. Enables reading data from the OUT 0
endpoint buffer for the endpoint specified in the
LOG_ENDPOINT field using the USBRxData register.
This bit is cleared by hardware when the last word of
the current packet is read from USBRxData.
0 Read mode is disabled.
1 Read mode is enabled.

Table 298. USB Control register (USBCtrl - address 0xFFE0 C228) bit description
value
1 WR_EN Write mode control. Enables writing data to the IN 0
endpoint buffer for the endpoint specified in the
LOG_ENDPOINT field using the USBTxData register.
This bit is cleared by hardware when the number of
bytes in USBTxLen have been sent.
0 Write mode is disabled.
1 Write mode is enabled.
5:2 LOG_ENDPOINT - Logical Endpoint number. 0x0
defined.
13.10.7 SIE command code registers

The SIE command code registers are used for communicating with the Serial Interface
Engine. See Section 13.12 “Serial interface engine command description” for more
information.
13.10.7.1 USB Command Code register (USBCmdCode - 0xFFE0 C210)

This register is used for sending the command and write data to the SIE. The commands
written here are propagated to the SIE and executed there. After executing the command,
the register is empty, and the CCEMPTY bit of USBDevIntSt register is set. See
Section 13.12 for details. USBCmdCode is a write only register.
Table 299. USB Command Code register (USBCmdCode - address 0xFFE0 C210) bit description
15:8 CMD_PHASE The command phase: 0x00
0x01 Read
0x02 Write
0x05 Command
23:16 CMD_CODE/ This is a multi-purpose field. When CMD_PHASE is 0x00
CMD_WDATA Command or Read, this field contains the code for the
command (CMD_CODE). When CMD_PHASE is Write,
this field contains the command write data (CMD_WDATA).
13.10.7.2 USB Command Data register (USBCmdData - 0xFFE0 C214)

This register contains the data retrieved after executing a SIE command. When the data is
ready to be read, the CD_FULL bit of the USBDevIntSt register is set. See Table 271 for
details. USBCmdData is a read only register.

Table 300. USB Command Data register (USBCmdData - address 0xFFE0 C214) bit
description
7:0 CMD_RDATA Command Read Data. 0x00
13.10.8 DMA registers

The registers in this group are used for the DMA mode of operation (see Section 13.15
“DMA operation”)
13.10.8.1 USB DMA Request Status register (USBDMARSt - 0xFFE0 C250)

A bit in this register associated with a non-isochronous endpoint is set by hardware when
an endpoint interrupt occurs (see the description of USBEpIntSt) and the corresponding
bit in USBEpIntEn is 0. A bit associated with an isochronous endpoint is set when the
corresponding bit in USBEpIntEn is 0 and a FRAME interrupt occurs. A set bit serves as a
flag for the DMA engine to start the data transfer if the DMA is enabled for the
corresponding endpoint in the USBEpDMASt register. The DMA cannot be enabled for
control endpoints (EP0 and EP1). USBDMARSt is a read only register.
Table 301. USB DMA Request Status register (USBDMARSt - address 0xFFE0 C250) bit allocation
Bit 31 30 29 28 27 26 25 24
Bit 23 22 21 20 19 18 17 16
Bit 15 14 13 12 11 10 9 8
Bit 7 6 5 4 3 2 1 0
Table 302. USB DMA Request Status register (USBDMARSt - address 0xFFE0 C250) bit description
0 EP0 0 Control endpoint OUT (DMA cannot be enabled for this endpoint and EP0 0
bit must be 0).
1 EP1 0 Control endpoint IN (DMA cannot be enabled for this endpoint and EP1 bit 0
must be 0).
31:2 EPxx Endpoint xx (2 xx 31) DMA request. 0
0 DMA not requested by endpoint xx.
1 DMA requested by endpoint xx.
[1] DMA can not be enabled for this endpoint and the corresponding bit in the USBDMARSt must be 0.
13.10.8.2 USB DMA Request Clear register (USBDMARClr - 0xFFE0 C254)

Writing one to a bit in this register will clear the corresponding bit in the USBDMARSt
register. Writing zero has no effect.

This register is intended for initialization prior to enabling the DMA for an endpoint. When
the DMA is enabled for an endpoint, hardware clears the corresponding bit in
USBDMARSt on completion of a packet transfer. Therefore, software should not clear the
bit using this register while the endpoint is enabled for DMA operation.
USBDMARClr is a write only register.
The USBDMARClr bit allocation is identical to the USBDMARSt register (Table 301).
Table 303. USB DMA Request Clear register (USBDMARClr - address 0xFFE0 C254) bit description
0 EP0 0 Control endpoint OUT (DMA cannot be enabled for this endpoint and the 0
EP0 bit must be 0).
1 EP1 0 Control endpoint IN (DMA cannot be enabled for this endpoint and the EP1 0
bit must be 0).
31:2 EPxx Clear the endpoint xx (2 xx 31) DMA request. 0
0 No effect.
1 Clear the corresponding bit in USBDMARSt.
13.10.8.3 USB DMA Request Set register (USBDMARSet - 0xFFE0 C258)

Writing one to a bit in this register sets the corresponding bit in the USBDMARSt register.
Writing zero has no effect.
This register allows software to raise a DMA request. This can be useful when switching
from Slave to DMA mode of operation for an endpoint: if a packet to be processed in DMA
mode arrives before the corresponding bit of USBEpIntEn is cleared, the DMA request is
not raised by hardware. Software can then use this register to manually start the DMA
transfer.
Software can also use this register to initiate a DMA transfer to proactively fill an IN
endpoint buffer before an IN token packet is received from the host.
USBDMARSet is a write only register.
The USBDMARSet bit allocation is identical to the USBDMARSt register (Table 301).
Table 304. USB DMA Request Set register (USBDMARSet - address 0xFFE0 C258) bit
description
value
0 EP0 0 Control endpoint OUT (DMA cannot be enabled for this endpoint 0
and the EP0 bit must be 0).
1 EP1 0 Control endpoint IN (DMA cannot be enabled for this endpoint and 0
the EP1 bit must be 0).
31:2 EPxx Set the endpoint xx (2 xx 31) DMA request. 0
0 No effect.
1 Set the corresponding bit in USBDMARSt.

13.10.8.4 USB UDCA Head register (USBUDCAH - 0xFFE0 C280)

The UDCA (USB Device Communication Area) Head register maintains the address
where the UDCA is located in the USB RAM. Refer to Section 13.15.2 “USB device
communication area” and Section 13.15.4 “The DMA descriptor” for more details on the
UDCA and DMA descriptors. USBUDCAH is a read/write register.
Table 305. USB UDCA Head register (USBUDCAH - address 0xFFE0 C280) bit description
6:0 - Reserved. Software should not write ones to reserved bits. The UDCA is 0x00
aligned to 128-byte boundaries.
31:7 UDCA_ADDR Start address of the UDCA. 0
13.10.8.5 USB EP DMA Status register (USBEpDMASt - 0xFFE0 C284)

Bits in this register indicate whether DMA operation is enabled for the corresponding
endpoint. A DMA transfer for an endpoint can start only if the corresponding bit is set in
this register. USBEpDMASt is a read only register.
Table 306. USB EP DMA Status register (USBEpDMASt - address 0xFFE0 C284) bit
description
value
0 EP0_DMA_ENABLE 0 Control endpoint OUT (DMA cannot be enabled for 0
this endpoint and the EP0_DMA_ENABLE bit must
be 0).
1 EP1_DMA_ENABLE 0 Control endpoint IN (DMA cannot be enabled for this 0
endpoint and the EP1_DMA_ENABLE bit must be
0).
31:2 EPxx_DMA_ENABLE endpoint xx (2 xx 31) DMA enabled bit. 0
0 The DMA for endpoint EPxx is disabled.
1 The DMA for endpoint EPxx is enabled.
13.10.8.6 USB EP DMA Enable register (USBEpDMAEn - 0xFFE0 C288)

Writing one to a bit to this register will enable the DMA operation for the corresponding
endpoint. Writing zero has no effect.The DMA cannot be enabled for control endpoints
EP0 and EP1. USBEpDMAEn is a write only register.
Table 307. USB EP DMA Enable register (USBEpDMAEn - address 0xFFE0 C288) bit
description
value
0 EP0_DMA_ENABLE 0 Control endpoint OUT (DMA cannot be enabled for 0
this endpoint and the EP0_DMA_ENABLE bit value
must be 0).
1 EP1_DMA_ENABLE 0 Control endpoint IN (DMA cannot be enabled for this 0
endpoint and the EP1_DMA_ENABLE bit must be 0).
31:2 EPxx_DMA_ENABLE Endpoint xx(2 xx 31) DMA enable control bit. 0
0 No effect.
1 Enable the DMA operation for endpoint EPxx.

13.10.8.7 USB EP DMA Disable register (USBEpDMADis - 0xFFE0 C28C)

Writing a one to a bit in this register clears the corresponding bit in USBEpDMASt. Writing
zero has no effect on the corresponding bit of USBEpDMASt. Any write to this register
clears the internal DMA_PROCEED flag. Refer to Section 13.15.5.4 “Optimizing
descriptor fetch” for more information on the DMA_PROCEED flag. If a DMA transfer is in
progress for an endpoint when its corresponding bit is cleared, the transfer is completed
before the DMA is disabled. When an error condition is detected during a DMA transfer,
the corresponding bit is cleared by hardware. USBEpDMADis is a write only register.
Table 308. USB EP DMA Disable register (USBEpDMADis - address 0xFFE0 C28C) bit
description
value
0 EP0_DMA_DISABLE 0 Control endpoint OUT (DMA cannot be enabled for 0
this endpoint and the EP0_DMA_DISABLE bit value
must be 0).
1 EP1_DMA_DISABLE 0 Control endpoint IN (DMA cannot be enabled for 0
this endpoint and the EP1_DMA_DISABLE bit value
must be 0).
31:2 EPxx_DMA_DISABLE Endpoint xx (2 xx 31) DMA disable control bit. 0
0 No effect.
1 Disable the DMA operation for endpoint EPxx.
13.10.8.8 USB DMA Interrupt Status register (USBDMAIntSt - 0xFFE0 C290)

Each bit of this register reflects whether any of the 32 bits in the corresponding interrupt
status register are set. USBDMAIntSt is a read only register.
Table 309. USB DMA Interrupt Status register (USBDMAIntSt - address 0xFFE0 C290) bit
description
value
0 EOT End of Transfer Interrupt bit. 0
0 All bits in the USBEoTIntSt register are 0.
1 At least one bit in the USBEoTIntSt is set.
1 NDDR New DD Request Interrupt bit. 0
0 All bits in the USBNDDRIntSt register are 0.
1 At least one bit in the USBNDDRIntSt is set.
2 ERR System Error Interrupt bit. 0
0 All bits in the USBSysErrIntSt register are 0.
1 At least one bit in the USBSysErrIntSt is set.
31:3 - - Reserved, user software should not write NA
ones to reserved bits. The value read from a
13.10.8.9 USB DMA Interrupt Enable register (USBDMAIntEn - 0xFFE0 C294)

Writing a one to a bit in this register enables the corresponding bit in USBDMAIntSt to
generate an interrupt on the USB_INT_REQ_DMA interrupt line when set. USBDMAIntEn
is a read/write register.

Table 310. USB DMA Interrupt Enable register (USBDMAIntEn - address 0xFFE0 C294) bit
description
value
0 EOT End of Transfer Interrupt enable bit. 0
0 The End of Transfer Interrupt is disabled.
1 The End of Transfer Interrupt is enabled.
1 NDDR New DD Request Interrupt enable bit. 0
0 The New DD Request Interrupt is
disabled.
1 The New DD Request Interrupt is
enabled.
2 ERR System Error Interrupt enable bit. 0
0 The System Error Interrupt is disabled.
1 The System Error Interrupt is enabled.
31:3 - - Reserved, user software should not write NA
ones to reserved bits. The value read
13.10.8.10 USB End of Transfer Interrupt Status register (USBEoTIntSt - 0xFFE0 C2A0)
When the DMA transfer completes for the current DMA descriptor, either normally
(descriptor is retired) or because of an error, the bit corresponding to the endpoint is set in
this register. The cause of the interrupt is recorded in the DD_status field of the descriptor.
USBEoTIntSt is a read only register.
Table 311. USB End of Transfer Interrupt Status register (USBEoTIntSt - address
0xFFE0 C2A0s) bit description
value
31:0 EPxx Endpoint xx (2 xx 31) End of Transfer Interrupt request. 0
0 There is no End of Transfer interrupt request for endpoint xx.
1 There is an End of Transfer Interrupt request for endpoint xx.
13.10.8.11 USB End of Transfer Interrupt Clear register (USBEoTIntClr - 0xFFE0 C2A4)
Writing one to a bit in this register clears the corresponding bit in the USBEoTIntSt
register. Writing zero has no effect. USBEoTIntClr is a write only register.
Table 312. USB End of Transfer Interrupt Clear register (USBEoTIntClr - address
0xFFE0 C2A4) bit description
value
31:0 EPxx Clear endpoint xx (2 xx 31) End of Transfer Interrupt request. 0
0 No effect.
1 Clear the EPxx End of Transfer Interrupt request in the
USBEoTIntSt register.

13.10.8.12 USB End of Transfer Interrupt Set register (USBEoTIntSet - 0xFFE0 C2A8)
Writing one to a bit in this register sets the corresponding bit in the USBEoTIntSt register.
Writing zero has no effect. USBEoTIntSet is a write only register.
Table 313. USB End of Transfer Interrupt Set register (USBEoTIntSet - address
0xFFE0 C2A8) bit description
value
31:0 EPxx Set endpoint xx (2 xx 31) End of Transfer Interrupt request. 0
0 No effect.
1 Set the EPxx End of Transfer Interrupt request in the
USBEoTIntSt register.
13.10.8.13 USB New DD Request Interrupt Status register (USBNDDRIntSt - 0xFFE0

C2AC)
A bit in this register is set when a transfer is requested from the USB device and no valid
DD is detected for the corresponding endpoint. USBNDDRIntSt is a read only register.
Table 314. USB New DD Request Interrupt Status register (USBNDDRIntSt - address
0xFFE0 C2AC) bit description
31:0 EPxx Endpoint xx (2 xx 31) new DD interrupt request. 0
0 There is no new DD interrupt request for endpoint xx.
1 There is a new DD interrupt request for endpoint xx.
13.10.8.14 USB New DD Request Interrupt Clear register (USBNDDRIntClr - 0xFFE0

C2B0)
Writing one to a bit in this register clears the corresponding bit in the USBNDDRIntSt
register. Writing zero has no effect. USBNDDRIntClr is a write only register.
Table 315. USB New DD Request Interrupt Clear register (USBNDDRIntClr - address 0xFFE0
C2B0) bit description
31:0 EPxx Clear endpoint xx (2 xx 31) new DD interrupt request. 0
0 No effect.
1 Clear the EPxx new DD interrupt request in the
USBNDDRIntSt register.
13.10.8.15 USB New DD Request Interrupt Set register (USBNDDRIntSet - 0xFFE0

C2B4)
Writing one to a bit in this register sets the corresponding bit in the USBNDDRIntSt
register. Writing zero has no effect. USBNDDRIntSet is a write only register

Table 316. USB New DD Request Interrupt Set register (USBNDDRIntSet - address 0xFFE0
C2B4) bit description
31:0 EPxx Set endpoint xx (2 xx 31) new DD interrupt request. 0
0 No effect.
1 Set the EPxx new DD interrupt request in the
USBNDDRIntSt register.
13.10.8.16 USB System Error Interrupt Status register (USBSysErrIntSt - 0xFFE0 C2B8)
If a system error (AHB bus error) occurs when transferring the data or when fetching or
updating the DD the corresponding bit is set in this register. USBSysErrIntSt is a read only
register.
Table 317. USB System Error Interrupt Status register (USBSysErrIntSt - address
0xFFE0 C2B8) bit description
value
31:0 EPxx Endpoint xx (2 xx 31) System Error Interrupt request. 0
0 There is no System Error Interrupt request for endpoint xx.
1 There is a System Error Interrupt request for endpoint xx.
13.10.8.17 USB System Error Interrupt Clear register (USBSysErrIntClr - 0xFFE0 C2BC)
Writing one to a bit in this register clears the corresponding bit in the USBSysErrIntSt
register. Writing zero has no effect. USBSysErrIntClr is a write only register.
Table 318. USB System Error Interrupt Clear register (USBSysErrIntClr - address
0xFFE0 C2BC) bit description
value
31:0 EPxx Clear endpoint xx (2 xx 31) System Error Interrupt request. 0
0 No effect.
1 Clear the EPxx System Error Interrupt request in the
USBSysErrIntSt register.
13.10.8.18 USB System Error Interrupt Set register (USBSysErrIntSet - 0xFFE0 C2C0)
Writing one to a bit in this register sets the corresponding bit in the USBSysErrIntSt
register. Writing zero has no effect. USBSysErrIntSet is a write only register.
Table 319. USB System Error Interrupt Set register (USBSysErrIntSet - address 0xFFE0
C2C0) bit description
value
31:0 EPxx Set endpoint xx (2 xx 31) System Error Interrupt request. 0
0 No effect.
1 Set the EPxx System Error Interrupt request in the
USBSysErrIntSt register.

13.11 Interrupt handling

This section describes how an interrupt event on any of the endpoints is routed to the
Vectored Interrupt Controller (VIC). For a diagram showing interrupt event handling, see
Figure 64.
All non-isochronous OUT endpoints (control, bulk, and interrupt endpoints) generate an
interrupt when they receive a packet without an error. All non-isochronous IN endpoints
generate an interrupt when a packet has been successfully transmitted or when a NAK
signal is sent and interrupts on NAK are enabled by the SIE Set Mode command, see
Section 13.12.3. For isochronous endpoints, a frame interrupt is generated every 1 ms.
The interrupt handling is different for Slave and DMA mode.
Slave mode
If an interrupt event occurs on an endpoint and the endpoint interrupt is enabled in the
USBEpIntEn register, the corresponding status bit in the USBEpIntSt is set. For
non-isochronous endpoints, all endpoint interrupt events are divided into two types by the
corresponding USBEpIntPri[n] registers: fast endpoint interrupt events and slow endpoint
interrupt events. All fast endpoint interrupt events are ORed and routed to bit EP_FAST in
the USBDevIntSt register. All slow endpoint interrupt events are ORed and routed to the
EP_SLOW bit in USBDevIntSt.
For isochronous endpoints, the FRAME bit in USBDevIntSt is set every 1 ms.
The USBDevIntSt register holds the status of all endpoint interrupt events as well as the
status of various other interrupts (see Section 13.10.3.2). By default, all interrupts (if
enabled in USBDevIntEn) are routed to the USB_INT_REQ_LP bit in the USBIntSt
register to request low priority interrupt handling. However, the USBDevIntPri register can
route either the FRAME or the EP_FAST bit to the USB_INT_REQ_HP bit in the USBIntSt
register.
Only one of the EP_FAST and FRAME interrupt events can be routed to the
USB_INT_REQ_HP bit. If routing both bits to USB_INT_REQ_HP is attempted, both
interrupt events are routed to USB_INT_REQ_LP.
Slow endpoint interrupt events are always routed directly to the USB_INT_REQ_LP bit for
low priority interrupt handling by software.
The final interrupt signal to the VIC is gated by the EN_USB_INTS bit in the USBIntSt
register. The USB interrupts are routed to VIC channel #22 only if EN_USB_INTS is set.
DMA mode
If an interrupt event occurs on a non-control endpoint and the endpoint interrupt is not
enabled in the USBEpIntEn register, the corresponding status bit in the USBDMARSt is
set by hardware. This serves as a flag for the DMA engine to transfer data if DMA transfer
is enabled for the corresponding endpoint in the USBEpDMASt register.
Three types of interrupts can occur for each endpoint for data transfers in DMA mode: End
of transfer interrupt , new DD request interrupt, and system error interrupt. These interrupt
events set a bit for each endpoint in the respective registers USBEoTIntSt,
USBNDDRIntSt, and USBSysErrIntSt. The End of transfer interrupts from all endpoints

are then Ored and routed to the EOT bit in USBDMAIntSt. Likewise, all New DD request
interrupts and system error interrupt events are routed to the NDDR and ERR bits
respectively in the USBDMAStInt register.
The EOT, NDDR, and ERR bits (if enabled in USBDMAIntEn) are ORed to set the
USB_INT_REQ_DMA bit in the USBIntSt register. If the EN_USB_INTS bit is set in
USBIntSt, the interrupt is routed to VIC channel #22.

interrupt
event on
EPn
Slave mode
from other
USBEpIntSt Endpoints
. USBDevIntSt
.
.
. FRAME
. EP_FAST
n . EP_SLOW
.
. USBDevIntPri[0] .
.
.
.
. .
. .
. .
USBEpIntEn[n] . .
.
USBEpIntPri[n] .. USBDevIntPri[1]
.
ERR_INT
USBDMARSt USBIntSt
USB_INT_REQ_HP to VIC
USB_INT_REQ_LP
channel
USB_INT_REQ_DMA
n to DMA engine #22
EN_USB_INTS
USBEoTIntST
DMA Mode
0
.
.
.
.
31
USBNDDRIntSt
0 USBDMAIntSt
. EOT
.
. NDDR
.
ERR
31
USBSysErrIntSt
0
.
.
.
.
31
For simplicity, USBDevIntEn and USBDMAIntEn are not shown.

Fig 64. Interrupt event handling

13.12 Serial interface engine command description

The functions and registers of the Serial Interface Engine (SIE) are accessed using
commands, which consist of a command code followed by optional data bytes (read or
write action). The USBCmdCode (Table 299) and USBCmdData (Table 300) registers are
used for these accesses.
A complete access consists of two phases:
1. Command phase: the USBCmdCode register is written with the CMD_PHASE field
set to the value 0x05 (Command), and the CMD_CODE field set to the desired
command code. On completion of the command, the CCEMPTY bit of USBDevIntSt is
set.
2. Data phase (optional): for writes, the USBCmdCode register is written with the
CMD_PHASE field set to the value 0x01 (Write), and the CMD_WDATA field set with
the desired write data. On completion of the write, the CCEMPTY bit of USBDevIntSt
is set. For reads, USBCmdCode register is written with the CMD_PHASE field set to
the value 0x02 (Read), and the CMD_CODE field set with command code the read
corresponds to. On completion of the read, the CDFULL bit of USBDevInSt will be set,
indicating the data is available for reading in the USBCmdData register. In the case of
multi-byte registers, the least significant byte is accessed first.
An overview of the available commands is given in Table 320.
Here is an example of the Read Current Frame Number command (reading 2 bytes):
USBDevIntClr = 0x30; // Clear both CCEMPTY & CDFULL

USBCmdCode = 0x00F50500; // CMD_CODE=0xF5, CMD_PHASE=0x05(Command)
while (!(USBDevIntSt & 0x10)); // Wait for CCEMPTY.
USBDevIntClr = 0x10; // Clear CCEMPTY interrupt bit.
USBCmdCode = 0x00F50200; // CMD_CODE=0xF5, CMD_PHASE=0x02(Read)
while (!(USBDevIntSt & 0x20)); // Wait for CDFULL.
USBDevIntClr = 0x20; // Clear CDFULL.
CurFrameNum = USBCmdData; // Read Frame number LSB byte.
USBCmdCode = 0x00F50200; // CMD_CODE=0xF5, CMD_PHASE=0x02(Read)
while (!(USBDevIntSt & 0x20)); // Wait for CDFULL.
Temp = USBCmdData; // Read Frame number MSB byte
USBDevIntClr = 0x20; // Clear CDFULL interrupt bit.
CurFrameNum = CurFrameNum | (Temp << 8);
Here is an example of the Set Address command (writing 1 byte):
USBDevIntClr = 0x10; // Clear CCEMPTY.

USBCmdCode = 0x00D00500; // CMD_CODE=0xD0, CMD_PHASE=0x05(Command)
USBCmdCode = 0x008A0100; // CMD_WDATA=0x8A(DEV_EN=1, DEV_ADDR=0xA),
// CMD_PHASE=0x01(Write)

Table 320. SIE command code table

Command name Recipient Code (Hex) Data phase
Device commands
Set Address Device D0 Write 1 byte
Configure Device Device D8 Write 1 byte
Set Mode Device F3 Write 1 byte
Read Current Frame Number Device F5 Read 1 or 2 bytes
Read Test Register Device FD Read 2 bytes
Set Device Status Device FE Write 1 byte
Get Device Status Device FE Read 1 byte
Get Error Code Device FF Read 1 byte
Read Error Status Device FB Read 1 byte
Endpoint Commands
Select Endpoint Endpoint 0 00 Read 1 byte (optional)
Endpoint 1 01 Read 1 byte (optional)
Endpoint xx xx Read 1 byte (optional)
Select Endpoint/Clear Interrupt Endpoint 0 40 Read 1 byte
Endpoint 1 41 Read 1 byte
Endpoint xx xx  40 Read 1 byte
Set Endpoint Status Endpoint 0 40 Write 1 byte
Endpoint 1 41 Write 1 byte
Endpoint xx xx  40 Write 1 byte
Clear Buffer Selected Endpoint F2 Read 1 byte (optional)
Validate Buffer Selected Endpoint FA None
13.12.1 Set Address (Command: 0xD0, Data: write 1 byte)

The Set Address command is used to set the USB assigned address and enable the
(embedded) function. The address set in the device will take effect after the status stage
of the control transaction. After a bus reset, DEV_ADDR is set to 0x00, and DEV_EN is
set to 1. The device will respond to packets for function address 0x00, endpoint 0 (default
endpoint).
Table 321. Device Set Address Register bit description

6:0 DEV_ADDR Device address set by the software. After a bus reset this field is set to 0x00
0x00.
7 DEV_EN Device Enable. After a bus reset this bit is set to 1. 0
0: Device will not respond to any packets.
1: Device will respond to packets for function address DEV_ADDR.
13.12.2 Configure Device (Command: 0xD8, Data: write 1 byte)

A value of 1 written to the register indicates that the device is configured and all the
enabled non-control endpoints will respond. Control endpoints are always enabled and
respond even if the device is not configured, in the default state.

Table 322. Configure Device Register bit description

0 CONF_DEVICE Device is configured. All enabled non-control endpoints will respond. This
bit is cleared by hardware when a bus reset occurs. When set, the
UP_LED signal is driven LOW if the device is not in the suspended state
(SUS=0).
13.12.3 Set Mode (Command: 0xF3, Data: write 1 byte)

Table 323. Set Mode Register bit description
value
0 AP_CLK Always PLL Clock. 0
0 USB_NEED_CLK is functional; the 48 MHz clock can be
stopped when the device enters suspend state.
1 USB_NEED_CLK is fixed to 1; the 48 MHz clock cannot be
stopped when the device enters suspend state.
1 INAK_CI Interrupt on NAK for Control IN endpoint. 0
0 Only successful transactions generate an interrupt.
1 Both successful and NAKed IN transactions generate interrupts.
2 INAK_CO Interrupt on NAK for Control OUT endpoint. 0
1 Both successful and NAKed OUT transactions generate
interrupts.
3 INAK_II Interrupt on NAK for Interrupt IN endpoint. 0
4 INAK_IO[1] Interrupt on NAK for Interrupt OUT endpoints. 0
interrupts.
5 INAK_BI Interrupt on NAK for Bulk IN endpoints. 0
6 INAK_BO[2] Interrupt on NAK for Bulk OUT endpoints. 0
interrupts.
7 - - Reserved, user software should not write ones to reserved bits. NA
[1] This bit should be reset to 0 if the DMA is enabled for any of the Interrupt OUT endpoints.
[2] This bit should be reset to 0 if the DMA is enabled for any of the Bulk OUT endpoints.

13.12.4 Read Current Frame Number (Command: 0xF5, Data: read 1 or 2

bytes)
Returns the frame number of the last successfully received SOF. The frame number is
eleven bits wide. The frame number returns least significant byte first. In case the user is
only interested in the lower 8 bits of the frame number, only the first byte needs to be read.
• In case no SOF was received by the device at the beginning of a frame, the frame
number returned is that of the last successfully received SOF.
• In case the SOF frame number contained a CRC error, the frame number returned will
be the corrupted frame number as received by the device.
13.12.5 Read Test Register (Command: 0xFD, Data: read 2 bytes)

The test register is 16 bits wide. It returns the value of 0xA50F if the USB clocks (usbclk
and AHB slave clock) are running.
13.12.6 Set Device Status (Command: 0xFE, Data: write 1 byte)

The Set Device Status command sets bits in the Device Status Register.
Table 324. Set Device Status Register bit description

value
0 CON The Connect bit indicates the current connect status of the 0
device. It controls the CONNECT output pin, used for
SoftConnect. Reading the connect bit returns the current connect
status. This bit is cleared by hardware when the VBUS status input
is LOW for more than 3 ms. The 3 ms delay filters out temporary
dips in the VBUS voltage.
0 Writing a 0 will make the CONNECT pin go HIGH.
1 Writing a 1 will make the CONNECT pin go LOW..
1 CON_CH Connect Change. 0
0 This bit is cleared when read.
1 This bit is set when the device’s pull-up resistor is disconnected
because VBUS disappeared. The DEV_STAT interrupt is
generated when this bit is 1.
2 SUS Suspend: The Suspend bit represents the current suspend state. 0
When the device is suspended (SUS = 1) and the CPU writes a 0
into it, the device will generate a remote wakeup. This will only
happen when the device is connected (CON = 1). When the
device is not connected or not suspended, writing a 0 has no
effect. Writing a 1 to this bit has no effect.
0 This bit is reset to 0 on any activity.
1 This bit is set to 1 when the device hasn’t seen any activity on its
upstream port for more than 3 ms.

Table 324. Set Device Status Register bit description

value
3 SUS_CH Suspend (SUS) bit change indicator. The SUS bit can toggle 0
because:
• The device goes into the suspended state.
• The device is disconnected.
• The device receives resume signalling on its upstream port.
This bit is cleared when read.
0 SUS bit not changed.
1 SUS bit changed. At the same time a DEV_STAT interrupt is
generated.
4 RST Bus Reset bit. On a bus reset, the device will automatically go to 0
the default state. In the default state:
• Device is unconfigured.
• Will respond to address 0.
• Control endpoint will be in the Stalled state.
• All endpoints are unrealized except control endpoints EP0
and EP1.
• Data toggling is reset for all endpoints.
• All buffers are cleared.
• There is no change to the endpoint interrupt status.
• DEV_STAT interrupt is generated.
Note: Bus resets are ignored when the device is not connected
(CON=0).
0 This bit is cleared when read.
1 This bit is set when the device receives a bus reset. A DEV_STAT
interrupt is generated.
13.12.7 Get Device Status (Command: 0xFE, Data: read 1 byte)

The Get Device Status command returns the Device Status Register. Reading the device
status returns 1 byte of data. The bit field definition is same as the Set Device Status
Register as shown in Table 324.
Remark: To ensure correct operation, the DEV_STAT bit of USBDevIntSt must be cleared
before executing the Get Device Status command.
13.12.8 Get Error Code (Command: 0xFF, Data: read 1 byte)

Different error conditions can arise inside the SIE. The Get Error Code command returns
the last error code that occurred. The 4 least significant bits form the error code.

Table 325. Get Error Code Register bit description

value
3:0 EC Error Code. 0x0
0000 No Error.
0001 PID Encoding Error.
0010 Unknown PID.
0011 Unexpected Packet - any packet sequence violation from the
specification.
0100 Error in Token CRC.
0101 Error in Data CRC.
0110 Time Out Error.
0111 Babble.
1000 Error in End of Packet.
1001 Sent/Received NAK.
1010 Sent Stall.
1011 Buffer Overrun Error.
1100 Sent Empty Packet (ISO Endpoints only).
1101 Bitstuff Error.
1110 Error in Sync.
1111 Wrong Toggle Bit in Data PID, ignored data.
4 EA - The Error Active bit will be reset once this register is read.
13.12.9 Read Error Status (Command: 0xFB, Data: read 1 byte)

This command reads the 8-bit Error register from the USB device. This register records
which error events have recently occurred in the SIE. If any of these bits are set, the
ERR_INT bit of USBDevIntSt is set. The error bits are cleared after reading this register.
Table 326. Read Error Status Register bit description

0 PID_ERR PID encoding error or Unknown PID or Token CRC. 0
1 UEPKT Unexpected Packet - any packet sequence violation from the 0
specification.
2 DCRC Data CRC error. 0
3 TIMEOUT Time out error. 0
4 EOP End of packet error. 0
5 B_OVRN Buffer Overrun. 0
6 BTSTF Bit stuff error. 0
7 TGL_ERR Wrong toggle bit in data PID, ignored data. 0

13.12.10 Select Endpoint (Command: 0x00 - 0x1F, Data: read 1 byte (optional))
The Select Endpoint command initializes an internal pointer to the start of the selected
buffer in EP_RAM. Optionally, this command can be followed by a data read, which
returns some additional information on the packet(s) in the endpoint buffer(s). The
command code of the Select Endpoint command is equal to the physical endpoint
number. In the case of a single buffered endpoint the B_2_FULL bit is not valid.
Table 327. Select Endpoint Register bit description

value
0 FE Full/Empty. This bit indicates the full or empty status of the 0
endpoint buffer(s). For IN endpoints, the FE bit gives the
ANDed result of the B_1_FULL and B_2_FULL bits. For OUT
endpoints, the FE bit gives ORed result of the B_1_FULL and
B_2_FULL bits. For single buffered endpoints, this bit simply
reflects the status of B_1_FULL.
0 For an IN endpoint, at least one write endpoint buffer is empty.
1 For an OUT endpoint, at least one endpoint read buffer is full.
1 ST Stalled endpoint indicator. 0
0 The selected endpoint is not stalled.
1 The selected endpoint is stalled.
2 STP SETUP bit: the value of this bit is updated after each 0
successfully received packet (i.e. an ACKed package on that
particular physical endpoint).
0 The STP bit is cleared by doing a Select Endpoint/Clear
Interrupt on this endpoint.
1 The last received packet for the selected endpoint was a
SETUP packet.
3 PO Packet over-written bit. 0
0 The PO bit is cleared by the ‘Select Endpoint/Clear Interrupt’
command.
1 The previously received packet was over-written by a SETUP
packet.
4 EPN EP NAKed bit indicates sending of a NAK. If the host sends an 0
OUT packet to a filled OUT buffer, the device returns NAK. If
the host sends an IN token packet to an empty IN buffer, the
device returns NAK.
0 The EPN bit is reset after the device has sent an ACK after an
OUT packet or when the device has seen an ACK after sending
an IN packet.
1 The EPN bit is set when a NAK is sent and the interrupt on NAK
feature is enabled.
5 B_1_FULL The buffer 1 status. 0
0 Buffer 1 is empty.
1 Buffer 1 is full.

Table 327. Select Endpoint Register bit description

value
6 B_2_FULL The buffer 2 status. 0
0 Buffer 2 is empty.
1 Buffer 2 is full.
7 - - Reserved, user software should not write ones to reserved bits. NA
13.12.11 Select Endpoint/Clear Interrupt (Command: 0x40 - 0x5F, Data: read 1

byte)
Commands 0x40 to 0x5F are identical to their Select Endpoint equivalents, with the
following differences:
• They clear the bit corresponding to the endpoint in the USBEpIntSt register.
• In case of a control OUT endpoint, they clear the STP and PO bits in the
corresponding Select Endpoint Register.
• Reading one byte is obligatory.
Remark: This command may be invoked by using the USBCmdCode and USBCmdData
registers, or by setting the corresponding bit in USBEpIntClr. For ease of use, using the
USBEpIntClr register is recommended.
13.12.12 Set Endpoint Status (Command: 0x40 - 0x55, Data: write 1 byte
(optional))
The Set Endpoint Status command sets status bits 7:5 and 0 of the endpoint. The
Command Code of Set Endpoint Status is equal to the sum of 0x40 and the physical
endpoint number in hex. Not all bits can be set for all types of endpoints.
Table 328. Set Endpoint Status Register bit description

value
0 ST Stalled endpoint bit. A Stalled control endpoint is automatically 0
unstalled when it receives a SETUP token, regardless of the
content of the packet. If the endpoint should stay in its stalled
state, the CPU can stall it again by setting this bit. When a stalled
endpoint is unstalled - either by the Set Endpoint Status
command or by receiving a SETUP token - it is also re-initialized.
This flushes the buffer: in case of an OUT buffer it waits for a
DATA 0 PID; in case of an IN buffer it writes a DATA 0 PID. There
is no change of the interrupt status of the endpoint. When
already unstalled, writing a zero to this bit initializes the endpoint.
When an endpoint is stalled by the Set Endpoint Status
command, it is also re-initialized.
0 The endpoint is unstalled.
1 The endpoint is stalled.

Table 328. Set Endpoint Status Register bit description

value
5 DA Disabled endpoint bit. 0
0 The endpoint is enabled.
1 The endpoint is disabled.
6 RF_MO Rate Feedback Mode. 0
0 Interrupt endpoint is in the Toggle mode.
1 Interrupt endpoint is in the Rate Feedback mode. This means
that transfer takes place without data toggle bit.
7 CND_ST Conditional Stall bit. 0
0 Unstalls both control endpoints.
1 Stall both control endpoints, unless the STP bit is set in the
Select Endpoint register. It is defined only for control OUT
endpoints.
13.12.13 Clear Buffer (Command: 0xF2, Data: read 1 byte (optional))

When an OUT packet sent by the host has been received successfully, an internal
hardware FIFO status Buffer_Full flag is set. All subsequent packets will be refused by
returning a NAK. When the device software has read the data, it should free the buffer by
issuing the Clear Buffer command. This clears the internal Buffer_Full flag. When the
buffer is cleared, new packets will be accepted.
When bit 0 of the optional data byte is 1, the previously received packet was over-written
by a SETUP packet. The Packet over-written bit is used only in control transfers.
According to the USB specification, a SETUP packet should be accepted irrespective of
the buffer status. The software should always check the status of the PO bit after reading
the SETUP data. If it is set then it should discard the previously read data, clear the PO bit
by issuing a Select Endpoint/Clear Interrupt command, read the new SETUP data and
again check the status of the PO bit.
See Section 13.14 “Slave mode operation” for a description of when this command is
used.
Table 329. Clear Buffer Register bit description

value
0 PO Packet over-written bit. This bit is only applicable to the control 0
endpoint EP0.
0 The previously received packet is intact.
1 The previously received packet was over-written by a later SETUP
packet.
7:1 - - Reserved, user software should not write ones to reserved bits. The NA
13.12.14 Validate Buffer (Command: 0xFA, Data: none)

When the CPU has written data into an IN buffer, software should issue a Validate Buffer
command. This tells hardware that the buffer is ready for sending on the USB bus.
Hardware will send the contents of the buffer when the next IN token packet is received.

Internally, there is a hardware FIFO status flag called Buffer_Full. This flag is set by the
Validate Buffer command and cleared when the data has been sent on the USB bus and
the buffer is empty.
A control IN buffer cannot be validated when its corresponding OUT buffer has the Packet
Over-written (PO) bit (see the Clear Buffer Register) set or contains a pending SETUP
packet. For the control endpoint the validated buffer will be invalidated when a SETUP
packet is received.
See Section 13.14 “Slave mode operation” for a description of when this command is
used.
13.13 USB device controller initialization

The LPC23xx USB device controller initialization includes the following steps:
1. Enable the device controller by setting the PCUSB bit of PCONP.

2. Configure and enable the PLL and Clock Dividers to provide 48 MHz for usbclk and
the desired frequency for cclk. For correct operation of synchronization logic in the
device controller, the minimum cclk frequency is 18 MHz. For the procedure for
determining the PLL setting and configuration, see Section 4.6.12 “Procedure for
determining PLL settings”.
3. Enable the device controller clocks by setting DEV_CLK_EN and AHB_CLK_EN bits
in the USBClkCtrl register. Poll the respective clock bits in the USBClkSt register until
they are set.
4. LPC2377/78 and LPC2388 only: select the desired USB port pins using the
USBPortSel register. The PORTSEL_CLK_EN bit must be set in USBClkCtrl before
accessing USBPortSel and should be cleared after accessing USBPortSel.
5. Enable the USB pin functions by writing to the corresponding PINSEL register.
6. Disable the pull-up resistor on the VBUS pin using the corresponding PINMODE
register.
7. Set USBEpIn and USBMaxPSize registers for EP0 and EP1, and wait until the
EP_RLZED bit in USBDevIntSt is set so that EP0 and EP1 are realized.
8. Enable endpoint interrupts (Slave mode):
– Clear all endpoint interrupts using USBEpIntClr.
– Clear any device interrupts using USBDevIntClr.
– Enable Slave mode for the desired endpoints by setting the corresponding bits in
USBEpIntEn.
– Set the priority of each enabled interrupt using USBEpIntPri.
– Configure the desired interrupt mode using the SIE Set Mode command.
– Enable device interrupts using USBDevIntEn (normally DEV_STAT, EP_SLOW,
and possibly EP_FAST).
9. Configure the DMA (DMA mode):
– Disable DMA operation for all endpoints using USBEpDMADis.
– Clear any pending DMA requests using USBDMARClr.

– Clear all DMA interrupts using USBEoTIntClr, USBNDDRIntClr, and

USBSysErrIntClr.
– Prepare the UDCA in system memory.
– Write the desired address for the UDCA to USBUDCAH (for example 0x7FD0
0000).
– Enable the desired endpoints for DMA operation using USBEpDMAEn.
– Set EOT, DDR, and ERR bits in USBDMAIntEn.
10. Install USB interrupt handler in the VIC by writing its address to the corresponding
VICVectAddr register and enabling the USB interrupt in the VICIntEnable register.
11. Set default USB address to 0x0 and DEV_EN to 1 using the SIE Set Address
command. A bus reset will also cause this to happen.
12. Set CON bit to 1 to make CONNECT active using the SIE Set Device Status
command.
The configuration of the endpoints varies depending on the software application. By

default, all the endpoints are disabled except control endpoints EP0 and EP1. Additional
endpoints are enabled and configured by software after a SET_CONFIGURATION or
SET_INTERFACE device request is received from the host.
13.14 Slave mode operation

In Slave mode, the CPU transfers data between RAM and the endpoint buffer using the
Register Interface.
13.14.1 Interrupt generation

In slave mode, data packet transfer between RAM and an endpoint buffer can be initiated
in response to an endpoint interrupt. Endpoint interrupts are enabled using the
USBEpIntEn register, and are observable in the USBEpIntSt register.
All non-isochronous OUT endpoints generate an endpoint interrupt when they receive a
packet without an error. All non-isochronous IN endpoints generate an interrupt when a
packet is successfully transmitted, or when a NAK handshake is sent on the bus and the
interrupt on NAK feature is enabled.
For Isochronous endpoints, transfer of data is done when the FRAME interrupt (in
USBDevIntSt) occurs.
13.14.2 Data transfer for OUT endpoints

When the software wants to read the data from an endpoint buffer it should set the
RD_EN bit and program LOG_ENDPOINT with the desired endpoint number in the
USBCtrl register. The control logic will fetch the packet length to the USBRxPLen register,
and set the PKT_RDY bit (Table 295 ).
Software can now start reading the data from the USBRxData register (Table 294). When
the end of packet is reached, the RD_EN bit is cleared, and the RxENDPKT bit is set in
the USBDevSt register. Software now issues a Clear Buffer (refer to Table 329) command.
The endpoint is now ready to accept the next packet. For OUT isochronous endpoints, the

next packet will be received irrespective of whether the buffer has been cleared. Any data
not read from the buffer before the end of the frame is lost. See Section 13.16 “Double
buffered endpoint operation” for more details.
If the software clears RD_EN before the entire packet is read, reading is terminated, and
the data remains in the endpoint’s buffer. When RD_EN is set again for this endpoint, the
data will be read from the beginning.
13.14.3 Data transfer for IN endpoints

When writing data to an endpoint buffer, WR_EN (Section 13.10.6.5 “USB Control register
(USBCtrl - 0xFFE0 C228)”) is set and software writes to the number of bytes it is going to
send in the packet to the USBTxPLen register (Section 13.10.6.4). It can then write data
continuously in the USBTxData register.
When the number of bytes programmed in USBTxPLen have been written to USBTxData,
the WR_EN bit is cleared, and the TxENDPKT bit is set in the USBDevIntSt register.
Software issues a Validate Buffer (Section 13.12.14 “Validate Buffer (Command: 0xFA,
Data: none)”) command. The endpoint is now ready to send the packet. For IN
isochronous endpoints, the data in the buffer will be sent only if the buffer is validated
before the next FRAME interrupt occurs; otherwise, an empty packet will be sent in the
next frame. If the software clears WR_EN before the entire packet is written, writing will
start again from the beginning the next time WR_EN is set for this endpoint.
Both RD_EN and WR_EN can be high at the same time for the same logical endpoint.
Interleaved read and write operation is possible.
13.15 DMA operation

In DMA mode, the DMA transfers data between RAM and the endpoint buffer.
The following sections discuss DMA mode operation. Background information is given in
sections Section 13.15.2 “USB device communication area” and Section 13.15.3
“Triggering the DMA engine”. The fields of the DMA Descriptor are described in section
Section 13.15.4 “The DMA descriptor”. The last three sections describe DMA operation:
Section 13.15.5 “Non-isochronous endpoint operation”, Section 13.15.6 “Isochronous
endpoint operation”, and Section 13.15.7 “Auto Length Transfer Extraction (ATLE) mode
operation”.
13.15.1 Transfer terminology

Within this section three types of transfers are mentioned:
1. USB transfers – transfer of data over the USB bus. The USB 2.0 specification refers
to these simply as transfers. Within this section they are referred to as USB transfers
to distinguish them from DMA transfers. A USB transfer is composed of transactions.
Each transaction is composed of packets.
2. DMA transfers – the transfer of data between an endpoint buffer and system memory
(RAM).
3. Packet transfers – in this section, a packet transfer refers to the transfer of a packet of
data between an endpoint buffer and system memory (RAM). A DMA transfer is
composed of one or more packet transfers.

13.15.2 USB device communication area

The CPU and DMA controller communicate through a common area of memory, called the
USB Device Communication Area, or UDCA. The UDCA is a 32-word array of DMA
Descriptor Pointers (DDPs), each of which corresponds to a physical endpoint. Each DDP
points to the start address of a DMA Descriptor, if one is defined for the endpoint. DDPs
for unrealized endpoints and endpoints disabled for DMA operation are ignored and can
be set to a NULL (0x0) value.
The start address of the UDCA is stored in the USBUDCAH register. The UDCA can
reside at any 128-byte boundary of RAM that is accessible to both the CPU and DMA
controller.
Figure 65 illustrates the UDCA and its relationship to the UDCA Head (USBUDCAH)
register and DMA Descriptors.
UDCA NULL
0
NULL
NULL
1 Next_DD_pointer Next_DD_pointer Next_DD_pointer
2
DDP-EP2
DD-EP2-a DD-EP2-b DD-EP2-c
NULL
UDCA HEAD
REGISTER NULL
Next_DD_pointer Next_DD_pointer
16
DDP-EP16
DD-EP16-a DD-EP16-b
31
DDP-EP31
Fig 65. UDCA Head register and DMA Descriptors
13.15.3 Triggering the DMA engine

An endpoint raises a DMA request when Slave mode is disabled by setting the
corresponding bit in the USBEpIntEn register to 0 (Section 13.10.4.2) and an endpoint
interrupt occurs (see Section 13.10.8.1 “USB DMA Request Status register (USBDMARSt
- 0xFFE0 C250)”).
A DMA transfer for an endpoint starts when the endpoint is enabled for DMA operation in
USBEpDMASt, the corresponding bit in USBDMARSt is set, and a valid DD is found for
the endpoint.
All endpoints share a single DMA channel to minimize hardware overhead. If more than
one DMA request is active in USBDMARSt, the endpoint with the lowest physical endpoint
number is processed first.

In DMA mode, the bits corresponding to Interrupt on NAK for Bulk OUT and Interrupt OUT
endpoints (INAK_BO and INAK_IO) should be set to 0 using the SIE Set Mode command
(Section 13.12.3).
13.15.4 The DMA descriptor

DMA transfers are described by a data structure called the DMA Descriptor (DD).
DDs are placed in the USB RAM. These descriptors can be located anywhere in the USB
RAM at word-aligned addresses. USB RAM is part of the system memory that is used for
the USB purposes. It is located at address 0x7FD0 0000 and is 8 kB in size.
DDs for non-isochronous endpoints are four words long. DDs for isochronous endpoints
are five words long.
The parameters associated with a DMA transfer are:
• The start address of the DMA buffer

• The length of the DMA buffer
• The start address of the next DMA descriptor
• Control information
• Count information (number of bytes transferred)
• Status information
Table 330 lists the DMA descriptor fields.
Table 330. DMA descriptor

Word Access Access Bit Description
position (H/W) (S/W) position
0 R R/W 31:0 Next_DD_pointer (USB RAM address)
1 R R/W 1:0 DMA_mode (00 -Normal; 01 - ATLE)
R R/W 2 Next_DD_valid (1 - valid; 0 - invalid)
- - 3 Reserved
R R/W 4 Isochronous_endpoint (1 - isochronous;
0 - non-isochronous)
R R/W 15:5 Max_packet_size
R/W[1] R/W 31:16 DMA_buffer_length
This value is specified in bytes for non-isochronous
endpoints and in number of packets for isochronous
endpoints.
2 R/W R/W 31:0 DMA_buffer_start_addr

Table 330. DMA descriptor

Word Access Access Bit Description
position (H/W) (S/W) position
3 R/W R/I 0 DD_retired (To be initialized to 0)
W R/I 4:1 DD_status (To be initialized to 0000):
0000 - NotServiced
0001 - BeingServiced
0010 - NormalCompletion
0011 - DataUnderrun (short packet)
1000 - DataOverrun
1001 - SystemError
W R/I 5 Packet_valid (To be initialized to 0)
W R/I 6 LS_byte_extracted (ATLE mode) (To be initialized to 0)
W R/I 7 MS_byte_extracted (ATLE mode) (To be initialized to 0)
R W 13:8 Message_length_position (ATLE mode)
- - 15:14 Reserved
R/W R/I 31:16 Present_DMA_count (To be initialized to 0)
4 R/W R/W 31:0 Isochronous_packetsize_memory_address
[1] Write only in ATLE mode
Legend: R - Read; W - Write; I - Initialize
13.15.4.1 Next_DD_pointer
Pointer to the memory location from where the next DMA descriptor will be fetched.
13.15.4.2 DMA_mode
Specifies the DMA mode of operation. Two modes have been defined: Normal and
Automatic Transfer Length Extraction (ATLE) mode. In normal mode, software initializes
the DMA_buffer_length for OUT endpoints. In ATLE mode, the DMA_buffer_length is
extracted from the incoming data. See Section 13.15.7 “Auto Length Transfer Extraction
(ATLE) mode operation” on page 372 for more details.
13.15.4.3 Next_DD_valid
This bit indicates whether the software has prepared the next DMA descriptor. If set, the
DMA engine fetches the new descriptor when it is finished with the current one.
13.15.4.4 Isochronous_endpoint
When set, this bit indicates that the descriptor belongs to an isochronous endpoint. Hence
5 words have to be read when fetching it.
13.15.4.5 Max_packet_size
The maximum packet size of the endpoint. This parameter is used while transferring the
data for IN endpoints from the memory. It is used for OUT endpoints to detect the short
packet. This is applicable to non-isochronous endpoints only. This field should be set to
the same MPS value that is assigned for the endpoint using the USBMaxPSize register.

13.15.4.6 DMA_buffer_length
This indicates the depth of the DMA buffer allocated for transferring the data. The DMA
engine will stop using this descriptor when this limit is reached and will look for the next
descriptor.
In Normal mode operation, software sets this value for both IN and OUT endpoints. In
ATLE mode operation, software sets this value for IN endpoints only. For OUT endpoints,
hardware sets this value using the extracted length of the data stream.
For isochronous endpoints, DMA_buffer_length is specified in number of packets, for

non-isochronous endpoints in bytes.
13.15.4.7 DMA_buffer_start_addr
The address where the data is read from or written to. This field is updated each time the
DMA engine finishes transferring a packet.
13.15.4.8 DD_retired
This bit is set by hardware when the DMA engine finishes the current descriptor. This
happens when the end of the buffer is reached, a short packet is transferred
(non-isochronous endpoints), or an error condition is detected.
13.15.4.9 DD_status
The status of the DMA transfer is encoded in this field. The following codes are defined:
• NotServiced - No packet has been transferred yet.

• BeingServiced - At least one packet is transferred.
• NormalCompletion - The DD is retired because the end of the buffer is reached and
there were no errors. The DD_retired bit is also set.
• DataUnderrun - Before reaching the end of the DMA buffer, the USB transfer is
terminated because a short packet is received. The DD_retired bit is also set.
• DataOverrun - The end of the DMA buffer is reached in the middle of a packet
transfer. This is an error situation. The DD_retired bit is set. The present DMA count
field is equal to the value of DMA_buffer_length. The packet must be re-transmitted
from the endpoint buffer in another DMA transfer. The corresponding
EPxx_DMA_ENABLE bit in USBEpDMASt is cleared.
• SystemError - The DMA transfer being serviced is terminated because of an error on
the AHB bus. The DD_retired bit is not set in this case. The corresponding
EPxx_DMA_ENABLE in USBEpDMASt is cleared. Since a system error can happen
while updating the DD, the DD fields in RAM may be unreliable.
13.15.4.10 Packet_valid
This bit is used for isochronous endpoints. It indicates whether the last packet transferred
to the memory is received with errors or not. This bit is set if the packet is valid, i.e., it was
received without errors. See Section 13.15.6 “Isochronous endpoint operation” on page
370 for isochronous endpoint operation.
This bit is unnecessary for non-isochronous endpoints because a DMA request is

generated only for packets without errors, and thus Packet_valid will always be set when
the request is generated.

13.15.4.11 LS_byte_extracted
Used in ATLE mode. When set, this bit indicates that the Least Significant Byte (LSB) of
the transfer length has been extracted. The extracted size is reflected in the
DMA_buffer_length field, bits 23:16.
13.15.4.12 MS_byte_extracted
Used in ATLE mode. When set, this bit indicates that the Most Significant Byte (MSB) of
the transfer size has been extracted. The size extracted is reflected in the
DMA_buffer_length field, bits 31:24. Extraction stops when LS_Byte_extracted and
MS_byte_extracted bits are set.
13.15.4.13 Present_DMA_count
The number of bytes transferred by the DMA engine. The DMA engine updates this field
after completing each packet transfer.
For isochronous endpoints, Present_DMA_count is the number of packets transferred; for

non-isochronous endpoints, Present_DMA_count is the number of bytes.
13.15.4.14 Message_length_position
Used in ATLE mode. This field gives the offset of the message length position embedded
in the incoming data packets. This is applicable only for OUT endpoints. Offset 0 indicates
that the message length starts from the first byte of the first packet.
13.15.4.15 Isochronous_packetsize_memory_address
The memory buffer address where the packet size information along with the frame
number has to be transferred or fetched. See Figure 66. This is applicable to isochronous
endpoints only.
13.15.5 Non-isochronous endpoint operation
13.15.5.1 Setting up DMA transfers

Software prepares the DMA Descriptors (DDs) for those physical endpoints to be enabled
for DMA transfer. These DDs are present in the USB RAM. The start address of the first
DD is programmed into the DMA Description pointer (DDP) location for the corresponding
endpoint in the UDCA. Software then sets the EPxx_DMA_ENABLE bit for this endpoint in
the USBEpDMAEn register (Section 13.10.8.6).The DMA_mode bit field in the descriptor
is set to ‘00’ for normal mode operation. All other DD fields are initialized as specified in
Table 330.
DMA operation is not supported for physical endpoints 0 and 1 (default control endpoints).
13.15.5.2 Finding DMA Descriptor

When there is a trigger for a DMA transfer for an endpoint, the DMA engine will first
determine whether a new descriptor has to the fetched or not. A new descriptor does not
have to be fetched if the last packet transferred was for the same endpoint and the DD is
not yet in the retired state. An internal flag called DMA_PROCEED is used to identify this
condition (see Section 13.15.5.4 “Optimizing descriptor fetch” on page 369).

If a new descriptor has to be read, the DMA engine will calculate the location of the DDP
for this endpoint and will fetch the start address of the DD from this location. A DD start
address at location zero is considered invalid. In this case the NDDR interrupt is raised.
All other word-aligned addresses are considered valid.
When the DD is fetched, the DD status word (word 3) is read first and the status of the
DD_retired bit is checked. If not set, DDP points to a valid DD. If DD_retired is set, the
DMA engine will read the control word (word 1) of the DD.
If Next_DD_valid bit is set, the DMA engine will fetch the Next_DD_pointer field (word 0)
of the DD and load it to the DDP. The new DDP is written to the UDCA area.
The full DD (4 words) will then be fetched from the address in the DDP. The DD will give
the details of the DMA transfer to be done. The DMA engine will load its hardware
resources with the information fetched from the DD (start address, DMA count etc.).
If Next_DD_valid is not set and DD_retired bit is set, the DMA engine raises the NDDR
interrupt for this endpoint and clears the corresponding EPxx_DMA_ENABLE bit.
13.15.5.3 Transferring the data

For OUT endpoints, the current packet is read from the EP_RAM by the DMA Engine and
transferred to the USB RAM memory locations starting from DMA_buffer_start_addr. For
IN endpoints, the data is fetched from the USB RAM at DMA_buffer_start_addr and
written to the EP_RAM. The DMA_buffer_start_addr and Present_DMA_count fields are
updated after each packet is transferred.
13.15.5.4 Optimizing descriptor fetch

A DMA transfer normally involves multiple packet transfers. Hardware will not re-fetch a
new DD from memory unless the endpoint changes. To indicate an ongoing multi-packet
transfer, hardware sets an internal flag called DMA_PROCEED.
The DMA_PROCEED flag is cleared after the required number of bytes specified in the
DMA_buffer_length field is transferred. It is also cleared when the software writes into the
USBEpDMADis register. The ability to clear the DMA_PROCEED flag allows software to
force the DD to be re-fetched for the next packet transfer. Writing all zeros into the
USBEpDMADis register clears the DMA_PROCEED flag without disabling DMA operation
for any endpoint.
13.15.5.5 Ending the packet transfer

On completing a packet transfer, the DMA engine writes back the DD with updated status
information to the same memory location from where it was read. The
DMA_buffer_start_addr, Present_DMA_count, and the DD_status fields in the DD are
updated.
A DD can have the following types of completion:
Normal completion - If the current packet is fully transferred and the

Present_DMA_count field equals the DMA_buffer_length, the DD has completed
normally. The DD will be written back to memory with DD_retired set and DD_status set
to NormalCompletion. The EOT interrupt is raised for this endpoint.

USB transfer end completion - If the current packet is fully transferred and its size is
less than the Max_packet_size field, and the end of the DMA buffer is still not reached,
the USB transfer end completion occurs. The DD will be written back to the memory
with DD_retired set and DD_Status set to the DataUnderrun completion code. The EOT
interrupt is raised for this endpoint.
Error completion - If the current packet is partially transferred i.e. the end of the DMA
buffer is reached in the middle of the packet transfer, an error situation occurs. The DD
is written back with DD_retired set and DD_status set to the DataOverrun status code.
The EOT interrupt is raised for this endpoint and the corresponding bit in USBEpDMASt
register is cleared. The packet will be re-sent from the endpoint buffer to memory when
the corresponding EPxx_DMA_ENABLE bit is set again using the USBEpDMAEn
register.
13.15.5.6 No_Packet DD
For an IN transfer, if the system does not have any data to send for a while, it can respond
to an NDDR interrupt by programming a No_Packet DD. This is done by setting both the
Max_packet_size and DMA_buffer_length fields in the DD to 0. On processing a
No_Packet DD, the DMA engine clears the DMA request bit in USBDMARSt
corresponding to the endpoint without transferring a packet. The DD is retired with a
status code of NormalCompletion. This can be repeated as often as necessary. The
device will respond to IN token packets on the USB bus with a NAK until a DD with a data
packet is programmed and the DMA transfers the packet into the endpoint buffer.
13.15.6 Isochronous endpoint operation

For isochronous endpoints, the packet size can vary for each packet. There is one packet
per isochronous endpoint for each frame.
13.15.6.1 Setting up DMA transfers

Software sets the isochronous endpoint bit to 1 in the DD, and programs the initial value of
the Isochronous_packetsize_memory_address field. All other fields are initialized the
same as for non-isochronous endpoints.
For isochronous endpoints, the DMA_buffer_length and Present_DMA_count fields are in

frames rather than bytes.
13.15.6.2 Finding the DMA Descriptor

Finding the descriptors is done in the same way as that for a non-isochronous endpoint.
A DMA request will be placed for DMA-enabled isochronous endpoints on every FRAME
interrupt. On processing the request, the DMA engine will fetch the descriptor and if
Isochronous_endpoint is set, will fetch the Isochronous_packetsize_memory_address
from the fifth word of the DD.
13.15.6.3 Transferring the Data

The data is transferred to or from the memory location DMA_buffer_start_addr. After the
end of the packet transfer the Present_DMA_count value is incremented by 1.

The isochronous packet size is stored in memory as shown in Figure 66. Each word in the
packet size memory shown is divided into fields: Frame_number (bits 31 to 17),
Packet_valid (bit 16), and Packet_length (bits 15 to 0). The space allocated for the packet
size memory for a given DD should be DMA_buffer_length words in size – one word for
each packet to transfer.
OUT endpoints
At the completion of each frame, the packet size is written to the address location in
Isochronous_packet_size_memory_address, and
Isochronous_packet_size_memory_address is incremented by 4.
IN endpoints
Only the Packet_length field of the isochronous packet size word is used. For each frame,
an isochronous data packet of size specified by this field is transferred from the USB
device to the host, and Isochronous_packet_size_memory_address is incremented by 4
at the end of the packet transfer. If Packet_length is zero, an empty packet will be sent by
the USB device.
13.15.6.4 DMA descriptor completion

DDs for isochronous endpoints can only end with a status code of NormalCompletion
since there is no short packet on Isochronous endpoints, and the USB transfer continues
indefinitely until a SystemError occurs. There is no DataOverrun detection for isochronous
endpoints.
13.15.6.5 Isochronous OUT Endpoint Operation Example

Assume that an isochronous endpoint is programmed for the transfer of 10 frames and
that the transfer begins when the frame number is 21. After transferring four frames with
packet sizes of 10,15, 8 and 20 bytes without errors, the descriptor and memory map
appear as shown in Figure 66.
The_total_number_of_bytes_transferred = 0x0A + 0x0F + 0x08 + 0x14 = 0x35.
The Packet_valid bit (bit 16) of all the words in the packet length memory is set to 1.

Next_DD_Pointer
W0
NULL
DMA_buffer_length Max_packet_size Isochronous_endpoint Next_DD_Valid DMA_mode
W1
0x000A 0x0 1 0 0
DMA_buffer_start_addr
W2
0x80000000
Present_DMA_Count ATLE settings Packet_Valid DD_Status DD_Retired
W3
0x0 NA NA 0x0 0
Isocronous_packetsize_memory_address
W4
0x60000000
after 4 packets
W0 0x0
W1 0x000A0010
FULL
W2 0x80000035
W3 0x4 - - 0x1 0
frame_ number Packet_Valid Packet_Length
EMPTY
W4 0x60000010 31 16 15 0
21 1 10
22 1 15
23 1 8
24 1 20
data memory
packet size memory
Fig 66. Isochronous OUT endpoint operation example
13.15.7 Auto Length Transfer Extraction (ATLE) mode operation

Some host drivers such as NDIS (Network Driver Interface Specification) host drivers are
capable of concatenating small USB transfers (delta transfers) to form a single large USB
transfer. For OUT USB transfers, the device hardware has to break up this concatenated
transfer back into the original delta transfers and transfer them to separate DMA buffers.
This is achieved by setting the DMA mode to Auto Transfer Length Extraction (ATLE)
mode in the DMA descriptor. ATLE mode is supported for Bulk endpoints only.
OUT transfers in ATLE mode

data to be sent data in packets data to be stored in USB

by host driver as seen on USB RAM by DMA engine
160 bytes DMA_buffer_start_addr

64 bytes
of DD1
160 bytes
64 bytes
32 bytes
32 bytes
100 bytes
100 bytes
64 bytes DMA_buffer_start_addr
of DD2
4 bytes
Fig 67. Data transfer in ATLE mode
Figure 67 shows a typical OUT USB transfer in ATLE mode, where the host concatenates
two USB transfers of 160 bytes and 100 bytes, respectively. Given a MaxPacketSize of
64, the device hardware interprets this USB transfer as four packets of 64 bytes and a
short packet of 4 bytes. The third and fourth packets are concatenated. Note that in
Normal mode, the USB transfer would be interpreted as packets of 64, 64, 32, and 64 and
36 bytes.
It is now the responsibility of the DMA engine to separate these two USB transfers and put
them in the memory locations in the DMA_buffer_start_addr field of DMA Descriptor 1
(DD1) and DMA Descriptor 2 (DD2).
Hardware reads the two-byte-wide DMA_buffer_length at the offset (from the start of the
USB transfer) specified by Message_length_position from the incoming data packets and
writes it in the DMA_buffer_length field of the DD. To ensure that both bytes of the
DMA_buffer_length are extracted in the event they are split between two packets, the
flags LS_byte_extracted and MS_byte_extracted are set by hardware after the respective
byte is extracted. After the extraction of the MS byte, the DMA transfer continues as in the
normal mode.
The flags LS_byte_extracted and MS_byte_extracted are set to 0 by software when

preparing a new DD. Therefore, once a DD is retired, the transfer length is extracted again
for the next DD.
If DD1 is retired during the transfer of a concatenated packet (such as the third packet in
Figure 67), and DD2 is not programmed (Next_DD_valid field of DD1 is 0), then DD1 is
retired with DD_status set to the DataOverrun status code. This is treated as an error
condition and the corresponding EPxx_DMA_ENABLE bit of USBEpDMASt is cleared by
hardware.

In ATLE mode, the last buffer length to be transferred always ends with a short or empty
packet indicating the end of the USB transfer. If the concatenated transfer lengths are
such that the USB transfer ends on a MaxPacketSize packet boundary, the (NDIS) host
will send an empty packet to mark the end of the USB transfer.
IN transfers in ATLE mode
For IN USB transfers from the device to the host, DMA_buffer_length is set by the device
software as in normal mode.
In ATLE mode, the device concatenates data from multiple DDs to form a single USB
transfer. If a DD is retired in the middle of a packet (packet size is less than
MaxPacketSize), the next DD referenced by Next_DD_pointer is fetched, and the
remaining bytes to form a packet of MaxPacketSize are transferred from the next DD’s
buffer.
If the next DD is not programmed (i.e. Next_DD_valid field in DD is 0), and the DMA buffer
length for the current DD has completed before the MaxPacketSize packet boundary, then
the available bytes from current DD are sent as a short packet on USB, which marks the
end of the USB transfer for the host.
If the last buffer length completes on a MaxPacketSize packet boundary, the device
software must program the next DD with DMA_buffer_length field 0, so that an empty
packet is sent by the device to mark the end of the USB transfer for the host.
13.15.7.1 Setting up the DMA transfer

For OUT endpoints, the host hardware needs to set the field Message_length_position in
the DD. This indicates the start location of the message length in the incoming data
packets. Also the device software has to set the DMA_buffer_length field to 0 for OUT
endpoints because this field is updated by the device hardware after the extraction of the
buffer length.
For IN endpoints, descriptors are set in the same way as in normal mode operation.
Since a single packet can be split between two DDs, software should always keep two
DDs ready, except for the last DMA transfer which ends with a short or empty packet.
13.15.7.2 Finding the DMA Descriptor

DMA descriptors are found in the same way as the normal mode operation.
13.15.7.3 Transferring the Data

OUT endpoints
If the LS_byte_extracted or MS_byte_extracted bit in the status field is not set, the
hardware will extract the transfer length from the data stream and program
DMA_buffer_length. Once the extraction is complete both the LS_byte_extracted and
MS_byte_extracted bits will be set.
IN endpoints
The DMA transfer proceeds as in normal mode and continues until the number of bytes
transferred equals the DMA_buffer_length.

13.15.7.4 Ending the packet transfer

The DMA engine proceeds with the transfer until the number of bytes specified in the field
DMA_buffer_length is transferred to or from the USB RAM. Then the EOT interrupt will be
generated. If this happens in the middle of the packet, the linked DD will get loaded and
the remaining part of the packet gets transferred to or from the address pointed by the
new DD.
OUT endpoints
If the linked DD is not valid and the packet is partially transferred to memory, the DD ends
with DataOverrun status code set, and the DMA will be disabled for this endpoint.
Otherwise DD_status will be updated with the NormalCompletion status code.
IN endpoints
If the linked DD is not valid and the packet is partially transferred to USB, the DD ends
with a status code of NormalCompletion in the DD_status field. This situation corresponds
to the end of the USB transfer, and the packet will be sent as a short packet. Also, when
the linked DD is valid and buffer length is 0, an empty packet will be sent to indicate the
end of the USB transfer.
13.16 Double buffered endpoint operation

The Bulk and Isochronous endpoints of the USB Device Controller are double buffered to
increase data throughput.
When a double-buffered endpoint is realized, enough space for both endpoint buffers is
automatically allocated in the EP_RAM. See Section 13.10.5.1.
For the following discussion, the endpoint buffer currently accessible to the CPU or DMA
engine for reading or writing is said to be the active buffer.
13.16.1 Bulk endpoints

For Bulk endpoints, the active endpoint buffer is switched by the SIE Clear Buffer or
Validate Buffer commands.
The following example illustrates how double buffering works for a Bulk OUT endpoint in
Slave mode:
Assume that both buffer 1 (B_1) and buffer 2 (B_2) are empty, and that the active buffer is
B_1.
1. The host sends a data packet to the endpoint. The device hardware puts the packet
into B_1, and generates an endpoint interrupt.
2. Software clears the endpoint interrupt and begins reading the packet data from B_1.
While B_1 is still being read, the host sends a second packet, which device hardware
places in B_2, and generates an endpoint interrupt.
3. Software is still reading from B_1 when the host attempts to send a third packet. Since
both B_1 and B_2 are full, the device hardware responds with a NAK.
4. Software finishes reading the first packet from B_1 and sends a SIE Clear Buffer
command to free B_1 to receive another packet. B_2 becomes the active buffer.

5. Software sends the SIE Select Endpoint command to read the Select Endpoint
Register and test the FE bit. Software finds that the active buffer (B_2) has data
(FE=1). Software clears the endpoint interrupt and begins reading the contents of
B_2.
6. The host resends the third packet which device hardware places in B_1. An endpoint
interrupt is generated.
7. Software finishes reading the second packet from B_2 and sends a SIE Clear Buffer
Software waits for the next endpoint interrupt to occur (it already has been generated
back in step 6).
8. Software responds to the endpoint interrupt by clearing it and begins reading the third
packet from B_1.
9. Software finishes reading the third packet from B_1 and sends a SIE Clear Buffer
10. Software tests the FE bit and finds that the active buffer (B_2) is empty (FE=0).
11. Both B_1 and B_2 are empty. Software waits for the next endpoint interrupt to occur.
The active buffer is now B_2. The next data packet sent by the host will be placed in
B_2.
The following example illustrates how double buffering works for a Bulk IN endpoint in
Slave mode:
Assume that both buffer 1 (B_1) and buffer 2 (B_2) are empty and that the active buffer is
B_1. The interrupt on NAK feature is enabled.
1. The host requests a data packet by sending an IN token packet. The device responds
with a NAK and generates an endpoint interrupt.
2. Software clears the endpoint interrupt. The device has three packets to send.
Software fills B_1 with the first packet and sends a SIE Validate Buffer command. The
active buffer is switched to B_2.
3. Software sends the SIE Select Endpoint command to read the Select Endpoint
Register and test the FE bit. It finds that B_2 is empty (FE=0) and fills B_2 with the
second packet. Software sends a SIE Validate Buffer command, and the active buffer
is switched to B_1.
4. Software waits for the endpoint interrupt to occur.
5. The device successfully sends the packet in B_1 and clears the buffer. An endpoint
interrupt occurs.
6. Software clears the endpoint interrupt. Software fills B_1 with the third packet and
validates it using the SIE Validate Buffer command. The active buffer is switched to
B_2.
7. The device successfully sends the second packet from B_2 and generates an
endpoint interrupt.
8. Software has no more packets to send, so it simply clears the interrupt.
9. The device successfully sends the third packet from B_1 and generates an endpoint
interrupt.
10. Software has no more packets to send, so it simply clears the interrupt.

11. Both B_1 and B_2 are empty, and the active buffer is B_2. The next packet written by
software will go into B_2.
In DMA mode, switching of the active buffer is handled automatically in hardware. For
Bulk IN endpoints, proactively filling an endpoint buffer to take advantage of the double
buffering can be accomplished by manually starting a packet transfer using the
USBDMARSet register.
13.16.2 Isochronous endpoints

For isochronous endpoints, the active data buffer is switched by hardware when the
FRAME interrupt occurs. The SIE Clear Buffer and Validate Buffer commands do not
cause the active buffer to be switched.
Double buffering allows the software to make full use of the frame interval writing or
reading a packet to or from the active buffer, while the packet in the other buffer is being
sent or received on the bus.
For an OUT isochronous endpoint, any data not read from the active buffer before the end
of the frame is lost when it switches.
For an IN isochronous endpoint, if the active buffer is not validated before the end of the
frame, an empty packet is sent on the bus when the active buffer is switched, and its
contents will be overwritten when it becomes active again.

UM10211
Chapter 14: LPC23XX USB Host controller

The USB host controller is available on the LPC2387/88 and LPC2361/62 only.


port to wake-up the microcontroller from Power-down mode.
(Table 76).
14.3 Introduction
This section describes the host portion of the USB 2.0 OTG dual role core which
integrates the host controller (OHCI compliant), device controller, and I2C interface. The
I2C interface controls the external OTG ATX.
The USB is a 4 wire bus that supports communication between a host and a number (127
max.) of peripherals. The host controller allocates the USB bandwidth to attached devices
through a token based protocol. The bus supports hot plugging, un-plugging and dynamic
configuration of the devices. All transactions are initiated by the host controller.
The host controller enables data exchange with various USB devices attached to the bus.
It consists of register interface, serial interface engine and DMA controller. The register
interface complies to the OHCI specification.
Table 331. USB (OHCI) related acronyms and abbreviations used in this chapter
Acronym/abbreviation Description
AHB Advanced High-Performance Bus
FS Full Speed
LS Low Speed
OHCI Open Host Controller Interface

14.3.1 Features
• OHCI compliant.
• OpenHCI specifies the operation and interface of the USB Host Controller and SW
Driver
– USBOperational: Process Lists and generate SOF Tokens.
– USBReset: Forces reset signaling on the bus, SOF disabled.
– USBSuspend: Monitor USB for wake-up activity.
– USBResume: Forces resume signaling on the bus.
• The Host Controller has four USB states visible to the SW Driver.
• HCCA register points to Interrupt and Isochronous Descriptors List.
• ControlHeadED and BulkHeadED registers point to Control and Bulk Descriptors List.
14.3.2 Architecture
The architecture of the USB host controller is shown below in Figure 68.
register
interface
(AHB slave) REGISTER
U1
INTERFACE
port
USB
ATX
port 1 ATX
HOST CONTROL
AHB bus
CONTROLLER port 2 LOGIC/

DMA interface
(AHB master) BUS PORT
MASTER MUX USB
INTERFACE ATX
U2
port
USB HOST BLOCK
Fig 68. USB Host controller block diagram
14.4 Interfaces
The USB interface is controlled by the OTG controller. It has two USB ports indicated by
suffixes 1 and 2 in the USB pin names and referred to as USB port 1 (U1) and USB port 2
(U2) in the following text.

14.4.1 Pin description

Table 332. USB OTG port pins
Pin name Direction Description Type
VBUS I VBUS status input. When this function is not enabled USB Connector
HIGH internally.
Port U1
USB_D+1 I/O Positive differential data USB Connector
USB_D1 I/O Negative differential data USB Connector
USB_CONNECT1 O SoftConnect control signal Control
USB_UP_LED1 O GoodLink LED control signal Control
USB_INT1 I OTG ATX interrupt External OTG transceiver
USB_SCL1 I/O I2C serial clock External OTG transceiver
USB_SDA1 I/O I2C serial data External OTG transceiver
USB_TX_E1 O Transmit enable External OTG transceiver
USB_TX_DP1 O D+ transmit data External OTG transceiver
USB_TX_DM1 O D transmit data External OTG transceiver
USB_RCV1 I Differential receive data External OTG transceiver
USB_RX_DP1 I D+ receive data External OTG transceiver
USB_RX_DM1 I D receive data External OTG transceiver
USB_LS1 O Low speed status (applies to host functionality only) External OTG transceiver
USB_SSPND1 O Bus suspend status External OTG transceiver
USB_PPWR1 O Port power enable Host power switch
USB_PWRD1 I Port power status Host power switch
USB_OVRCR1 I Over-current status Host power switch
USB_HSTEN1 O Host enabled status
Port U2
U2PWRD2 I Port power status Host power switch
USB_HSTEN2 O Host enabled status Control
14.4.1.1 USB host usage note

Both ports can be configured as USB hosts. For details on how to connect the USB ports,
see the USB OTG chapter, Section 15.7.
The USB device/host/OTG controller is disabled after RESET and must be enabled by
writing a 1 to the PCUSB bit in the PCONP register, see Table 53.

14.4.2 Software interface

The software interface of the USB host block consists of a register view and the format
definitions for the endpoint descriptors. For details on these two aspects see the OHCI
specification. The register map is shown in the next subsection.
14.4.2.1 Register map

The following registers are located in the AHB clock ‘cclk’ domain. They can be accessed
directly by the processor. All registers are 32 bit wide and aligned in the word address
boundaries.
Table 333. USB Host register address definitions

Name Address R/W[1] Function Reset value
HcRevision 0xFFE0 C000 R BCD representation of the version of the HCI 0x10
specification that is implemented by the Host Controller.
HcControl 0xFFE0 C004 R/W Defines the operating modes of the HC. 0x0
HcCommandStatus 0xFFE0 C008 R/W This register is used to receive the commands from the 0x0
Host Controller Driver (HCD). It also indicates the status
of the HC.
HcInterruptStatus 0xFFE0 C00C R/W Indicates the status on various events that cause 0x0
hardware interrupts by setting the appropriate bits.
HcInterruptEnable 0xFFE0 C010 R/W Controls the bits in the HcInterruptStatus register and 0x0
indicates which events will generate a hardware
interrupt.
HcInterruptDisable 0xFFE0 C014 R/W The bits in this register are used to disable 0x0
corresponding bits in the HCInterruptStatus register and
in turn disable that event leading to hardware interrupt.
HcHCCA 0xFFE0 C018 R/W Contains the physical address of the host controller 0x0
communication area.
HcPeriodCurrentED 0xFFE0 C01C R Contains the physical address of the current isochronous 0x0
or interrupt endpoint descriptor.
HcControlHeadED 0xFFE0 C020 R/W Contains the physical address of the first endpoint 0x0
descriptor of the control list.
HcControlCurrentED 0xFFE0 C024 R/W Contains the physical address of the current endpoint 0x0
descriptor of the control list
HcBulkHeadED 0xFFE0 C028 R/W Contains the physical address of the first endpoint 0x0
descriptor of the bulk list.
HcBulkCurrentED 0xFFE0 C02C R/W Contains the physical address of the current endpoint 0x0
descriptor of the bulk list.
HcDoneHead 0xFFE0 C030 R Contains the physical address of the last transfer 0x0
descriptor added to the ‘Done’ queue.
HcFmInterval 0xFFE0 C034 R/W Defines the bit time interval in a frame and the full speed 0x2EDF
maximum packet size which would not cause an
overrun.
HcFmRemaining 0xFFE0 C038 R A 14-bit counter showing the bit time remaining in the 0x0
current frame.
HcFmNumber 0xFFE0 C03C R Contains a 16-bit counter and provides the timing 0x0
reference among events happening in the HC and the
HCD.

Table 333. USB Host register address definitions …continued

Name Address R/W[1] Function Reset value
HcPeriodicStart 0xFFE0 C040 R/W Contains a programmable 14-bit value which determines 0x0
the earliest time HC should start processing a periodic
list.
HcLSThreshold 0xFFE0 C044 R/W Contains 11-bit value which is used by the HC to 0x628h
determine whether to commit to transfer a maximum of
8-byte LS packet before EOF.
HcRhDescriptorA 0xFFE0 C048 R/W First of the two registers which describes the 0xFF000902
characteristics of the root hub.
HcRhDescriptorB 0xFFE0 C04C R/W Second of the two registers which describes the 0x60000h
characteristics of the Root Hub.
HcRhStatus 0xFFE0 C050 R/W This register is divided into two parts. The lower D-word 0x0
represents the hub status field and the upper word
represents the hub status change field.
HcRhPortStatus[1] 0xFFE0 C054 R/W Controls and reports the port events on a per-port basis. 0x0
HcRhPortStatus[2] 0xFFE0 C058 R/W Controls and reports the port events on a per port basis. 0x0
Module_ID/Ver_Rev_ID 0xFFE0 C0FC R IP number, where yy (0x00) is unique version number 0x3505yyzz
and zz (0x00) is a unique revision number.
[1] The R/W column in Table 333 lists the accessibility of the register:
a) Registers marked ‘R’ for access will return their current value when read.
b) Registers marked ‘R/W’ allow both read and write.
14.4.2.2 USB Host Register Definitions

Refer to the OHCI specification document on Compaq’s website for register definitions.

UM10211
Chapter 15: LPC23XX USB OTG controller

The USB OTG controller is available in LPC2387/88 and LPC2361/62 only. The
LPC2388 has two USB ports, the LPC2361/62 and LPC2387 have one USB port.


port to wake-up the microcontroller from Power-down mode (see Section 15.10.2).
(Table 76).
15.3 Introduction
This chapter describes the OTG and I2C portions of the USB 2.0 OTG dual role device
controller which integrates the (OHCI) host controller, device controller, and I2C. The I2C
interface (Master only) controls an external OTG transceiver.
USB OTG (On-The-Go) is a supplement to the USB 2.0 specification that augments the
capability of existing mobile devices and USB peripherals by adding host functionality for
connection to USB peripherals. The specification and more information on USB OTG can
be found on the USB Implementers Forum web site.
15.4 Features
• Fully compliant with On-The-Go supplement to the USB 2.0 Specification, Revision
1.0a.
• Hardware support for Host Negotiation Protocol (HNP).
• Includes a programmable timer required for HNP and SRP.
• Supports any OTG transceiver compliant with the OTG Transceiver Specification
(CEA-2011), Rev. 1.0.
15.5 Architecture
The architecture of the USB OTG controller is shown below in the block diagram.

The host, device, OTG, and I2C controllers can be programmed through the register
interface. The OTG controller enables dynamic switching between host and device roles
through the HNP protocol. One port may be connected to an external OTG transceiver to
support an OTG connection. The communication between the register interface and an
external OTG transceiver is handled through an I2C interface and through the external
OTG transceiver interrupt signal.
For USB connections that use the device or host controller only (not OTG), the ports use
an embedded USB Analog Transceiver (ATX).
OTG
TRANSCEIVER
register I2C
interface CONTROLLER
(AHB slave) REGISTER
U1
INTERFACE
port
OTG
CONTROLLER USB
ATX
ATX
port 1 CONTROL
AHB bus
DMA interface DEVICE LOGIC/

(AHB master) BUS CONTROLLER PORT
MASTER MUX USB
INTERFACE port 1 ATX
HOST
U2
CONTROLLER port 2
port
USB OTG BLOCK
EP_RAM
Fig 69. USB OTG controller block diagram
15.6 Modes of operation

On The LPC2361/62 and the LPC2387, the USB port can be configured as device, Host,
or OTG port.
On the LPC2388, the OTG controller is capable of operating in the following modes:
• One port host and one port dual-role device (see Figure 70)
• One port host and one port device (see Figure 72)
• Two-port host (see Figure 73)
15.7 Pin configuration

The OTG controller has two USB ports indicated by suffixes 1 and 2 in the USB pin names
and referred to as USB port 1 (U1) and USB port 2 (U2) in the following text.

Table 334. USB OTG port 1 pins

Pin name Direction Description Pin category
VBUS I VBUS status input. When this function is not enabled USB Connector
HIGH internally.
Port U1
USB_INT1 I OTG ATX interrupt External OTG transceiver
USB_SCL1 I/O I2C serial clock External OTG transceiver
USB_SDA1 I/O I2C serial data External OTG transceiver
USB_TX_E1 O Transmit enable External OTG transceiver
USB_TX_DP1 O D+ transmit data External OTG transceiver
USB_TX_DM1 O D transmit data External OTG transceiver
USB_RCV1 I Differential receive data External OTG transceiver
USB_RX_DP1 I D+ receive data External OTG transceiver
USB_RX_DM1 I D receive data External OTG transceiver
USB_LS1 O Low speed status (applies to host functionality only) External OTG transceiver
USB_SSPND1 O Bus suspend status External OTG transceiver
USB_HSTEN1 O Host enabled status
Port U2 (host functions on LPC2388 only)
USB_HSTEN2 O Host enabled status Control
The following figures show different ways to realize connections to an USB device using
ports U1 and U2. The example described here uses an ISP1302 (replaces ISP1301) for
the external OTG transceiver and the USB Host power switch LM3526-L (National
Semiconductors).
15.7.1 Connecting port U1 to an external OTG transceiver

For OTG functionality an external OTG transceiver must be connected to the LPC2400
device. There are two ways to connect the OTG transceiver (here ISP1302) to port U1:

1. Use the internal USB transceiver for USB signalling and use the external OTG
transceiver for OTG functionality only (see Figure 70). This option uses the internal
transceiver in VP/VM mode.
2. Use the external OTG transceiver in VP/VM mode for OTG functionality and USB
signalling (see Figure 71).
In both cases port U2 is connected as a host. Solution one uses fewer pins.
VDD
R1 R2 R3 R4
RSTOUT RESET_N VBUS

ADR/PSW ID
OE_N/INT_N DP 33 Ω
VDD Mini-AB
SPEED 33 Ω connector
DM
SUSPEND ISP1302
R4 R5 R6 VSS
USB_SCL1 SCL
USB_SDA1 SDA
USB_INT1 INT_N
USB_D+1
USB_D−1
VDD
USB_UP_LED1 R7
LPC2388 5V VDD
IN
OUTA
LM3526-L
USB_PPWR2 ENA
FLAGA
USB_OVRCR2
USB_PWRD2 VBUS
USB_D+2 33 Ω D+
USB-A
USB_D−2 33 Ω D− connector
VSS
15 kΩ 15 kΩ
VDD
USB_UP_LED2 R8
002aad336
Fig 70. USB OTG port configuration: port U1 OTG Dual-Role device, port U2 host

VDD
RSTOUT RESET_N
USB_TX_E1 OE_N/INT_N
USB_TX_DP1 DAT_VP
USB_TX_DM1 SE0_VM
USB_RCV1 RCV
USB_RX_DP1 VP VBUS
USB_RX_DM1 VM ID
VDD DP 33 Ω USB MINI-AB
ISP1302 connector
DM 33 Ω
LPC2388
ADR/PSW VSS
SPEED
SUSPEND
USB_SCL1 SCL
USB_SDA1 SDA
USB_INT1 INT_N
VDD
USB_UP_LED1
002aad337
Fig 71. USB OTG port configuration: VP_VM mode

15.7.2 Connecting USB as a two-port host

Both ports U1 and U2 are connected as hosts using an embedded USB transceiver. There
is no OTG functionality on either port.
VDD
USB_UP_LED1
VSS
USB_D+1 33 Ω D+
USB_D−1 33 Ω D−
USB-A
15 kΩ 15 kΩ connector
VDD
USB_PWRD1 VBUS
USB_OVRCR1
USB_PPWR1 ENA FLAGA

5V OUTA VDD
IN
LM3526-L OUTB
LPC2388
USB_PPWR2 ENB
FLAGB
USB_OVRCR2
USB_PWRD2 VBUS
USB_D+2 33 Ω D+ USB-A
connector
15 kΩ 15 kΩ VSS
VDD
USB_UP_LED2
002aad338
Fig 72. USB OTG port configuration: port U2 host, port U1 host
15.7.3 Connecting USB as one port host and one port device
Port U2 is connected as device, and port U1 is connected as host using an embedded
USB transceiver. There is no OTG functionality on either port.

VDD
USB_UP_LED1
VSS
USB_D+1 33 Ω D+
USB-A
15 kΩ 15 kΩ connector
VDD
USB_PWRD1 VBUS
USB_OVRCR1
USB_PPWR1 ENA FLAGA

5V OUTA
LM3526-L
IN
LPC2388
VDD
USB_UP_LED2
VDD
USB_CONNECT2
VSS
USB_D+2 33 Ω D+
33 Ω
USB-B
USB_D−2 D−
connector
VBUS VBUS
002aad335
Fig 73. USB OTG port configuration: port U1 host, port U2 device

The OTG and I2C registers are summarized in the following table.
The Device and Host registers are explained in Table 333 and Table 266 in the USB
Device Controller and USB Host (OHCI) Controller chapters. All registers are 32 bits wide
and aligned to word address boundaries.
Table 335. USB OTG and I2C register address definitions

Name Address Access Function
Interrupt register
USBIntSt 0xE01F C1C0 R/W USB Interrupt Status
OTG registers
OTGIntSt 0xFFE0 C100 RO OTG Interrupt Status
OTGIntEn 0xFFE0 C104 R/W OTG Interrupt Enable
OTGIntSet 0xFFE0 C108 WO OTG Interrupt Set
OTGIntClr 0xFFE0 C10C WO OTG Interrupt Clear
OTGStCtrl[1] 0xFFE0 C110 R/W OTG Status and Control

Table 335. USB OTG and I2C register address definitions

Name Address Access Function
OTGTmr 0xFFE0 C114 R/W OTG Timer
I2C registers
I2C_RX 0xFFE0 C300 RO I2C Receive
I2C_TX 0xFFE0 C300 WO I2C Transmit
I2C_STS 0xFFE0 C304 RO I2C Status
I2C_CTL 0xFFE0 C308 R/W I2C Control
I2C_CLKHI 0xFFE0 C30C R/W I2C Clock High
I2C_CLKLO 0xFFE0 C310 WO I2C Clock Low
Clock control registers
OTGClkCtrl 0xFFE0 CFF4 R/W OTG clock controller
OTGClkSt 0xFFE0 CFF8 RO OTG clock status
[1] Bits 0 and 1 of this register are used to control the routing of the USB pins to ports 1 and 2 in device-only
application (see Table 267).
15.8.1 USB Interrupt Status Register (USBIntSt - 0xE01F C1C0)

The USB OTG controller has seven interrupt lines. This register allows software to
determine their status with a single read operation.
The interrupt lines are ORed together to a single channel of the vectored interrupt
controller.
Table 336. USB Interrupt Status register - (USBIntSt - address 0xE01F C1) bit description
Value
0 USB_INT_REQ_LP Low priority interrupt line status. This bit is read only. 0
1 USB_INT_REQ_HP High priority interrupt line status. This bit is read only. 0
2 USB_INT_REQ_DMA DMA interrupt line status. This bit is read only. 0
3 USB_HOST_INT USB host interrupt line status. This bit is read only. 0
4 USB_ATX_INT External ATX interrupt line status. This bit is read only. 0
5 USB_OTG_INT OTG interrupt line status. This bit is read only. 0
6 USB_I2C_INT I2C module interrupt line status. This bit is read only. 0
defined.
8 USB_NEED_CLK USB need clock indicator. This bit is read only. 0
defined.
31 EN_USB_INTS Enable all USB interrupts. When this bit is cleared, the 1
VIC does not see the ORed output of the USB interrupt
lines.

15.8.2 OTG Interrupt Status Register (OTGIntSt - 0xE01F C100)

Bits is this register are set by hardware when the interrupt event occurs during the HNP
handoff sequence. See Section 15.9 for more information on when these bits are set.
Table 337. OTG Interrupt Status register (OTGIntSt - address 0xE01F C100) bit description
Value
0 TMR Timer time-out. 0
1 REMOVE_PU Remove pull-up. 0
This bit is set by hardware to indicate that software
needs to disable the D+ pull-up resistor.
2 HNP_FAILURE HNP failed. 0
This bit is set by hardware to indicate that the HNP
switching has failed.
3 HNP_SUCCESS HNP succeeded. 0
This bit is set by hardware to indicate that the HNP
switching has succeeded.
defined.
15.8.3 OTG Interrupt Enable Register (OTGIntEn - 0xFFE0 C104)

Writing a one to a bit in this register enables the corresponding bit in OTGIntSt to generate
an interrupt on one of the interrupt lines. The interrupt is routed to the USB_OTG_INT
interrupt line in the USBIntSt register.
The bit allocation and reset value of OTGIntEn is the same as OTGIntSt.
15.8.4 OTG Interrupt Set Register (OTGIntSet - 0xFFE0 C20C)

Writing a one to a bit in this register will set the corresponding bit in the OTGIntSt register.
Writing a zero has no effect. The bit allocation of OTGIntSet is the same as in OTGIntSt.
15.8.5 OTG Interrupt Clear Register (OTGIntClr - 0xFFE0 C10C)

Writing a one to a bit in this register will clear the corresponding bit in the OTGIntSt
register. Writing a zero has no effect. The bit allocation of OTGIntClr is the same as in
OTGIntSt.
15.8.6 OTG Status and Control Register (OTGStCtrl - 0xFFE0 C110)

The OTGStCtrl register allows enabling hardware tracking during the HNP hand over
sequence, controlling the OTG timer, monitoring the timer count, and controlling the
functions mapped to port U1 and U2.
Time critical events during the switching sequence are controlled by the OTG timer. The
timer can operate in two modes:
1. Monoshot mode: an interrupt is generated at the end of TIMEOUT_CNT (see

Section 15.8.7 “OTG Timer Register (OTGTmr - 0xFFE0 C114)”), the TMR bit is set in
OTGIntSt, and the timer will be disabled.

2. Free running mode: an interrupt is generated at the end of TIMEOUT_CNT (see

Section 15.8.7 “OTG Timer Register (OTGTmr - 0xFFE0 C114)”), the TMR bit is set,
and the timer value is reloaded into the counter. The timer is not disabled in this
mode.
Table 338. OTG Status Control register (OTGStCtrl - address 0xFFE0 C110) bit description
Value
1:0 PORT_FUNC Controls the function of ports U1 and U2. Bit 0 is set or -
cleared by hardware when B_HNP_TRACK or
A_HNP_TRACK is set and HNP succeeds. See
Section 15.9.
3:2 TMR_SCALE Timer scale selection. This field determines the duration 0x0
of each timer count.
00: 10 s (100 KHz)
01: 100 s (10 KHz)
10: 1000 s (1 KHz)
11: Reserved
4 TMR_MODE Timer mode selection. 0
0: monoshot
1: free running
5 TMR_EN Timer enable. When set, TMR_CNT increments. When 0
cleared, TMR_CNT is reset to 0.
6 TMR_RST Timer reset. Writing one to this bit resets TMR_CNT to 0. 0
This provides a single bit control for the software to
restart the timer when the timer is enabled.
defined.
8 B_HNP_TRACK Enable HNP tracking for B-device (peripheral), see 0
Section 15.9. Hardware clears this bit when
HNP_SUCCESS or HNP_FAILURE is set.
9 A_HNP_TRACK Enable HNP tracking for A-device (host), see 0
Section 15.9. Hardware clears this bit when
10 PU_REMOVED When the B-device changes its role from peripheral to 0
host, software sets this bit when it removes the D+
pull-up, see Section 15.9. Hardware clears this bit when
defined.
31:16 TMR_CNT Current timer count value. 0x0

OTGStCtrl
PORT_FUNC[0] = 0 PORT_FUNC[1] = 0
port1
DEVICE
CONTROLLER U1
U2
port1
HOST
CONTROLLER port2
Fig 74. Port selection for PORT_FUNC bit 0 = 0 and PORT_FUNC bit 1 = 0.
Table 339. Port function truth table

PORT_FUNC[0] = 0 PORT_FUNC[0] = 1
PORT_FUNC[1] = 0 U1 = device (OTG) U1 = host (OTG)
U2 = host U2 = host
PORT_FUNC[1] = 1 reserved U1 = host
U2 = device
15.8.7 OTG Timer Register (OTGTmr - 0xFFE0 C114)

Table 340. OTG Timer register (OTGTmr - address 0xFFE0 C114) bit description
Value
15:0 TIMEOUT_CNT The TMR interrupt is set when TMR_CNT reaches this value. 0xFFFF
15.8.8 OTG Clock Control Register (OTGClkCtrl - 0xFFE0 CFF4)

This register controls the clocking of the OTG controller. Whenever software wants to
access the registers, the corresponding clock control bit needs to be set. The software
does not have to repeat this exercise for every register access, provided that the
corresponding OTGClkCtrl bits are already set.
Table 341. OTG_clock_control register (OTG_clock_control - address 0xFFE0 CFF4) bit

description
Value
0 HOST_CLK_EN Host clock enable 0
0 Disable the Host clock.
1 Enable the Host clock.

Table 341. OTG_clock_control register (OTG_clock_control - address 0xFFE0 CFF4) bit

description
Value
1 DEV_CLK_EN Device clock enable 0
0 Disable the Device clock.
1 Enable the Device clock.
2 I2C_CLK_EN I2C clock enable 0
0 Disable the I2C clock.
1 Enable the I2C clock.
3 OTG_CLK_EN OTG clock enable 0
0 Disable the OTG clock.
1 Enable the OTG clock.
4 AHB_CLK_EN AHB master clock enable 0
0 Disable the AHB clock.
1 Enable the AHB clock.
31:5 - NA Reserved, user software should not write ones NA
to reserved bits. The value read from a
15.8.9 OTG Clock Status Register (OTGClkSt - 0xFFE0 CFF8)

This register holds the clock availability status. When enabling a clock via OTGClkCtrl,
software should poll the corresponding bit in this register. If it is set, then software can go
ahead with the register access. Software does not have to repeat this exercise for every
access, provided that the OTGClkCtrl bits are not disturbed.
Table 342. OTG_clock_status register (OTGClkSt - address 0xFFE0 CFF8) bit description
Value
0 HOST_CLK_ON Host clock status. 0
0 Host clock is not available.
1 Host clock is available.
1 DEV_CLK_ON Device clock status. 0
0 Device clock is not available.
1 Device clock is available.
2 I2C_CLK_ON I2C clock status. 0
0 I2C clock is not available.
1 I2C clock is available.
3 OTG_CLK_ON OTG clock status. 0
0 OTG clock is not available.
1 OTG clock is available.

Table 342. OTG_clock_status register (OTGClkSt - address 0xFFE0 CFF8) bit description
Value
4 AHB_CLK_ON AHB master clock status. 0
0 AHB clock is not available.
1 AHB clock is available.
31:5 - NA Reserved, user software should not write ones NA
to reserved bits. The value read from a
15.8.10 I2C Receive Register (I2C_RX - 0xFFE0 C300)

This register is the top byte of the receive FIFO. The receive FIFO is 4 bytes deep. The Rx
FIFO is flushed by a hard reset or by a soft reset (I2C_CTL bit 7). Reading an empty FIFO
gives unpredictable data results.
Table 343. I2C Receive register (I2C_RX - address 0xFFE0 C300) bit description
Value
7:0 RX Data Receive data. -
15.8.11 I2C Transmit Register (I2C_TX - 0xFFE0 C300)

This register is the top byte of the transmit FIFO. The transmit FIFO is 4 bytes deep.
The Tx FIFO is flushed by a hard reset, soft reset (I2C_CTL bit 7) or if an arbitration failure
occurs (I2C_STS bit 3). Data writes to a full FIFO are ignored.
I2C_TX must be written for both write and read operations to transfer each byte. Bits [7:0]
are ignored for master-receive operations. The master-receiver must write a dummy byte
to the TX FIFO for each byte it expects to receive in the RX FIFO. When the STOP bit is
set or the START bit is set to cause a RESTART condition on a byte written to the TX
FIFO (master-receiver), then the byte read from the slave is not acknowledged. That is,
the last byte of a master-receive operation is not acknowledged.
Table 344. I2C Transmit register (I2C_TX - address 0xFFE0 C300) bit description
Value
7:0 TX Data Transmit data. -
8 START When 1, issue a START condition before transmitting this byte. -
9 STOP When 1, issue a STOP condition after transmitting this byte. -
31:10 - Reserved. User software should not write ones to reserved bits. The -
15.8.12 I2C Status Register (I2C_STS - 0xFFE0 C304)

The I2C_STS register provides status information on the TX and RX blocks as well as the
current state of the external buses. Individual bits are enabled as interrupts by the
I2C_CTL register and routed to the I2C_USB_INT bit in USBIntSt.

Table 345. I2C status register (I2C_STS - address 0xFFE0 C304) bit description
Value
0 TDI Transaction Done Interrupt. This flag is set if a transaction 0
completes successfully. It is cleared by writing a one to bit 0 of
the status register. It is unaffected by slave transactions.
0 Transaction has not completed.
1 Transaction completed.
1 AFI Arbitration Failure Interrupt. When transmitting, if the SDA is low 0
when SDAOUT is high, then this I2C has lost the arbitration to
another device on the bus. The Arbitration Failure bit is set when
this happens. It is cleared by writing a one to bit 1 of the status
register.
0 No arbitration failure on last transmission.
1 Arbitration failure occurred on last transmission.
2 NAI No Acknowledge Interrupt. After every byte of data is sent, the 0
transmitter expects an acknowledge from the receiver. This bit is
set if the acknowledge is not received. It is cleared when a byte
is written to the master TX FIFO.
0 Last transmission received an acknowledge.
1 Last transmission did not receive an acknowledge.
3 DRMI Master Data Request Interrupt. Once a transmission is started, 0
the transmitter must have data to transmit as long as it isn’t
followed by a stop condition or it will hold SCL low until more
data is available. The Master Data Request bit is set when the
master transmitter is data-starved. If the master TX FIFO is
empty and the last byte did not have a STOP condition flag, then
SCL is held low until the CPU writes another byte to transmit.
This bit is cleared when a byte is written to the master TX FIFO.
0 Master transmitter does not need data.
1 Master transmitter needs data.
4 DRSI Slave Data Request Interrupt. Once a transmission is started, 0
the transmitter must have data to transmit as long as it isn’t
followed by a STOP condition or it will hold SCL low until more
data is available. The Slave Data Request bit is set when the
slave transmitter is data-starved. If the slave TX FIFO is empty
and the last byte transmitted was acknowledged, then SCL is
held low until the CPU writes another byte to transmit. This bit is
cleared when a byte is written to the slave Tx FIFO.
0 Slave transmitter does not need data.
1 Slave transmitter needs data.
5 Active Indicates whether the bus is busy. This bit is set when a START 0
condition has been seen. It is cleared when a STOP condition is
seen..
6 SCL The current value of the SCL signal. -
7 SDA The current value of the SDA signal. -

Table 345. I2C status register (I2C_STS - address 0xFFE0 C304) bit description
Value
8 RFF Receive FIFO Full (RFF). This bit is set when the RX FIFO is full 0
and cannot accept any more data. It is cleared when the RX
FIFO is not full. If a byte arrives when the Receive FIFO is full,
the SCL is held low until the CPU reads the RX FIFO and makes
room for it.
0 RX FIFO is not full
1 RX FIFO is full
9 RFE Receive FIFO Empty. RFE is set when the RX FIFO is empty 1
and is cleared when the RX FIFO contains valid data.
0 RX FIFO contains data.
1 RX FIFO is empty
10 TFF Transmit FIFO Full. TFF is set when the TX FIFO is full and is 0
cleared when the TX FIFO is not full.
0 TX FIFO is not full.
1 TX FIFO is full
11 TFE Transmit FIFO Empty. TFE is set when the TX FIFO is empty 1
and is cleared when the TX FIFO contains valid data.
0 TX FIFO contains valid data.
1 TX FIFO is empty
31:12 - NA Reserved, user software should not write ones to reserved bits. NA
15.8.13 I2C Control Register (I2C_CTL - 0xFFE0 C308)

The I2C_CTL register is used to enable interrupts and reset the I2C state machine.
Enabled interrupts cause the USB_I2C_INT interrupt output line to be asserted when set.
Table 346. I2C Control register (I2C_CTL - address 0xFFE0 C308) bit description
Value
0 TDIE Transmit Done Interrupt Enable. This enables the TDI interrupt signalling that this I2C 0
issued a STOP condition.
0 Disable the TDI interrupt.
1 Enable the TDI interrupt.
1 AFIE Transmitter Arbitration Failure Interrupt Enable. This enables the AFI interrupt which is 0
asserted during transmission when trying to set SDA high, but the bus is driven low by
another device.
0 Disable the AFI.
1 Enable the AFI.
2 NAIE Transmitter No Acknowledge Interrupt Enable. This enables the NAI interrupt signalling 0
that transmitted byte was not acknowledged.
0 Disable the NAI.
1 Enable the NAI.

Table 346. I2C Control register (I2C_CTL - address 0xFFE0 C308) bit description
Value
3 DRMIE Master Transmitter Data Request Interrupt Enable. This enables the DRMI interrupt which 0
signals that the master transmitter has run out of data, has not issued a STOP, and is
holding the SCL line low.
0 Disable the DRMI interrupt.
1 Enable the DRMI interrupt.
4 DRSIE Slave Transmitter Data Request Interrupt Enable. This enables the DRSI interrupt which 0
signals that the slave transmitter has run out of data and the last byte was acknowledged,
so the SCL line is being held low.
0 Disable the DRSI interrupt.
1 Enable the DRSI interrupt.
5 REFIE Receive FIFO Full Interrupt Enable. This enables the Receive FIFO Full interrupt to 0
indicate that the receive FIFO cannot accept any more data.
0 Disable the RFFI.
1 Enable the RFFI.
6 RFDAIE Receive Data Available Interrupt Enable. This enables the DAI interrupt to indicate that 0
data is available in the receive FIFO (i.e. not empty).
0 Disable the DAI.
1 Enable the DAI.
7 TFFIE Transmit FIFO Not Full Interrupt Enable. This enables the Transmit FIFO Not Full interrupt 0
to indicate that the more data can be written to the transmit FIFO. Note that this is not full.
It is intended help the CPU to write to the I2C block only when there is room in the FIFO
and do this without polling the status register.
0 Disable the TFFI.
1 Enable the TFFI.
8 SRST Soft reset. This is only needed in unusual circumstances. If a device issues a start 0
condition without issuing a stop condition. A system timer may be used to reset the I2C if
the bus remains busy longer than the time-out period. On a soft reset, the Tx and Rx
FIFOs are flushed, I2C_STS register is cleared, and all internal state machines are reset
to appear idle. The I2C_CLKHI, I2C_CLKLO and I2C_CTL (except Soft Reset Bit) are
NOT modified by a soft reset.
0 See the text.
1 Reset the I2C to idle state. Self clearing.
31:9 - NA Reserved, user software should not write ones to reserved bits. The value read from a NA
15.8.14 I2C Clock High Register (I2C_CLKHI - 0xFFE0 C30C)

The CLK register holds a terminal count for counting 48 MHz clock cycles to create the
high period of the slower I2C serial clock, SCL.
Table 347. I2C_CLKHI register (I2C_CLKHI - address 0xFFE0 C30C) bit description
Value
7:0 CDHI Clock divisor high. This value is the number of 48 MHz 0xB9
clocks the serial clock (SCL) will be high.

15.8.15 I2C Clock Low Register (I2C_CLKLO - 0xFFE0 C310)

The CLK register holds a terminal count for counting 48 MHz clock cycles to create the
low period of the slower I2C serial clock, SCL.
Table 348. I2C_CLKLO register (I2C_CLKLO - address 0xFFE0 C310) bit description
Value
7:0 CDLO Clock divisor low. This value is the number of 48 MHz 0xB9
clocks the serial clock (SCL) will be low.
15.8.16 Interrupt handling

The interrupts set in the OTGIntSt register are set and cleared during HNP switching. All
OTG related interrupts, if enabled, are routed to the USB_OTG_INT bit in the USBIntSt
register.
I2C related interrupts are set in the I2C_STS register and routed, if enabled by I2C_CTL,
to the USB_I2C_INT bit.
For more details on the interrupts created by device controller, see the USB device
chapter. For interrupts created by the host controllers, see the OHCI specification.
The EN_USB_INTS bit in the USBIntSt register enables the routing of any of the USB
related interrupts to the VIC controller (see Figure 75).
Remark: During the HNP switching between host and device with the OTG stack active,
an action may raise several levels of interrupts. It is advised to let the OTG stack initiate
any actions based on interrupts and ignore device and host level interrupts. This means
that during HNP switching, the OTG stack provides the communication to the host and
device controllers.
USBIntSt
USB_INT_REQ_HP to VIC
USB DEVICE USB_INT_REQ_LP
INTERRUPTS channel #22
USB_INT_REQ_DMA
USB_HOST_INT
USB_OTG_INT
USB HOST
INTERRUPTS USB_I2C_INT
OTGIntSt
TMR
REMOVE_PU
HNP_SUCCESS
HNP_FAILURE
USB_NEED_CLOCK
USB I2C EN_USB_INTS

INTERRUPTS
Fig 75. USB OTG interrupt handling

15.9 HNP support

This section describes the hardware support for the Host Negotiation Protocol (HNP)
provided by the OTG controller.
When two dual-role OTG devices are connected to each other, the plug inserted into the
mini-AB receptacle determines the default role of each device. The device with the mini-A
plug inserted becomes the default Host (A-device), and the device with the mini-B plug
inserted becomes the default Peripheral (B-device).
Once connected, the default Host (A-device) and the default Peripheral (B-device) can
switch Host and Peripheral roles using HNP.
The context of the OTG controller operation is shown in Figure 76. Each controller (Host,
Device, or OTG) communicates with its software stack through a set of status and control
registers and interrupts. In addition, the OTG software stack communicates with the
external OTG transceiver through the I2C interface and the external transceiver interrupt
signal.
The OTG software stack is responsible for implementing the HNP state machines as
described in the On-The-Go Supplement to the USB 2.0 Specification.
The OTG controller hardware provides support for some of the state transitions in the
HNP state machines as described in the following subsections.
The USB state machines, the HNP switching, and the communications between the USB
controllers are described in more detail in the following documentation:
• USB OHCI specification

• USB OTG supplement, version 1.2
• USB 2.0 specification
• ISP1302 data sheet and user manual

OHCI HOST
STACK CONTROLLER
OTG USB BUS

OTG MUX
CONTROLLER
STACK
DEVICE DEVICE
STACK CONTROLLER
I2C
CONTROLLER ISP1302
Fig 76. USB OTG controller with software stack
15.9.1 B-device: peripheral to host switching

In this case, the default role of the OTG controller is peripheral (B-device), and it switches
roles from Peripheral to Host.
The On-The-Go Supplement defines the behavior of a dual-role B-device during HNP
using a state machine diagram. The OTG software stack is responsible for implementing
all of the states in the Dual-Role B-Device State Diagram.
The OTG controller hardware provides support for the state transitions between the states
b_peripheral, b_wait_acon, and b_host in the Dual-Role B-Device state diagram. Setting
B_HNP_TRACK in the OTGStCtrl register enables hardware support for the B-device
switching from peripheral to host. The hardware actions after setting this bit are shown in
Figure 77.

idle
B_HNP_TRACK = 0
no
B_HNP_TRACK = 1 ?
set HNP_FAILURE,
clear B_HNP_TRACK,
clear PU_REMOVED
no
bus suspended ?
no
disconnect device controller from U1 PU_REMOVED set?
set REMOVE_PU
yes
PU_REMOVED set?
reconnect port U1 to the
device controller
yes
bus reset/resume detected?
no
reconnect port U1 to the

device controller
wait 25 s for bus to settle
yes yes
connect from A-device detected? bus reset/resume detected?
no no
set HNP_SUCCESS yes

set PORT_FUNC[0] connect U1 to host controller
SE0 sent by host? clear B_HNP_TRACK
drive J on internal host controller port
and SE0 on U1 clear PU_REMOVED
no
Fig 77. Hardware support for B-device switching from peripheral state to host state
Figure 78 shows the actions that the OTG software stack should take in response to the
hardware actions setting REMOVE_PU, HNP_SUCCESS, AND HNP_FAILURE. The
relationship of the software actions to the Dual-Role B-Device states is also shown.
B-device states are in bold font with a circle around them.

b_peripheral
when host sends SET_FEATURE
with b_hnp_enable,
set B_HNP_TRACK
no
REMOVE_PU set?
yes
remove D+ pull-up,
set PU_REMOVED
go to go to
b_wait_acon b_peripheral
yes
HNP_FAILURE set? add D+ pull-up
no
no
HNP_SUCCESS set?
yes
go to
b_host
Fig 78. State transitions implemented in software during B-device switching from peripheral to host
Note that only the subset of B-device HNP states and state transitions supported by
hardware are shown. Software is responsible for implementing all of the HNP states.
Figure 78 may appear to imply that the interrupt bits such as REMOVE_PU should be
polled, but this is not necessary if the corresponding interrupt is enabled.
Following are code examples that show how the actions in Figure 78 are accomplished.
The examples assume that ISP1302 is being used as the external OTG transceiver.
Remove D+ pull-up
/* Remove D+ pull-up through ISP1302 */

OTG_I2C_TX = 0x15A; // Send ISP1302 address, R/W=0
OTG_I2C_TX = 0x007; // Send OTG Control (Clear) register address
OTG_I2C_TX = 0x201; // Clear DP_PULLUP bit, send STOP condition

/* Wait for TDI to be set */

while (!(OTG_I2C_STS & TDI));
/* Clear TDI */
OTG_I2C_STS = TDI;
Add D+ pull-up
/* Add D+ pull-up through ISP1302 */

OTG_I2C_TX = 0x006; // Send OTG Control (Set) register address
OTG_I2C_TX = 0x201; // Set DP_PULLUP bit, send STOP condition

/* Clear TDI */
OTG_I2C_STS = TDI;
15.9.2 A-device: host to peripheral HNP switching

In this case, the role of the OTG controller is host (A-device), and the A-device switches
roles from host to peripheral.
The On-The-Go Supplement defines the behavior of a dual-role A-device during HNP
using a state machine diagram. The OTG software stack is responsible for implementing
all of the states in the Dual-Role A-Device State Diagram.
The OTG controller hardware provides support for the state transitions between a_host,
a_suspend, a_wait_vfall, and a_peripheral in the Dual-Role A-Device state diagram.
Setting A_HNP_TRACK in the OTGStCtrl register enables hardware support for switching
the A-device from the host state to the device state. The hardware actions after setting
this bit are shown in Figure 79.

idle
A_HNP_TRACK = 0
no
A_HNP_TRACK = 1 ? set HNP_FAILURE,
clear A_HNP_TRACK
disconnect host controller from U1
no no
bus suspended ? resume detected ?
yes yes connnect host controller back to U1
yes yes
bus reset detected? resume detected?
no no
no OTG timer expired?

(TMR =1 )
yes
clear A_HNP_TRACK
set HNP_SUCCESS
connect device to U1 by clearing
PORT_FUNC[0]
Fig 79. Hardware support for A-device switching from host state to peripheral state
Figure 80 shows the actions that the OTG software stack should take in response to the
hardware actions setting TMR, HNP_SUCCESS, and HNP_FAILURE. The relationship of
the software actions to the Dual-Role A-Device states is also shown. A-device states are
shown in bold font with a circle around them.

a_host
when host sends SET_FEATURE
with a_hnp_enable,
set A_HNP_TRACK
set BDIS_ACON_EN
in external OTG transceiver
load and enable OTG timer
suspend host on port 1
go to
a_suspend
no
no no
TMR set? HNP_SUCCESS set? HNP_FAILURE set?
yes yes
yes
clear BDIS_ACON_EN
stop the OTG timer stop OTG timer
bit in external OTG transceiver
discharge VBUS
go to
clear BDIS_ACON_EN
a_peripheral bit in external OTG transceiver
go to
a_wait_vfall go to
a_host
Fig 80. State transitions implemented in software during A-device switching from host to peripheral
Note that only the subset of A-device HNP states and state transitions supported by
hardware are shown. Software is responsible for implementing all of the HNP states.
Figure 80 may appear to imply that the interrupt bits such as TMR should be polled, but
this is not necessary if the corresponding interrupt is enabled.
Following are code examples that show how the actions in Figure 80 are accomplished.
The examples assume that ISP1302 is being used as the external OTG transceiver.
Set BDIS_ACON_EN in external OTG transceiver


/* Set BDIS_ACON_EN in ISP1302 */

OTG_I2C_TX = 0x004; // Send Mode Control 1 (Set) register address
OTG_I2C_TX = 0x210; // Set BDIS_ACON_EN bit, send STOP condition

/* Clear TDI */
OTG_I2C_STS = TDI;
Clear BDIS_ACON_EN in external OTG transceiver
/* Set BDIS_ACON_EN in ISP1302 */

OTG_I2C_TX = 0x005; // Send Mode Control 1 (Clear) register address
OTG_I2C_TX = 0x210; // Clear BDIS_ACON_EN bit, send STOP condition

/* Clear TDI */
OTG_I2C_STS = TDI;
Discharge VBUS
/* Clear the VBUS_DRV bit in ISP1302 */

OTG_I2C_TX = 0x007; // Send OTG Control (Clear) register address
OTG_I2C_TX = 0x220; // Clear VBUS_DRV bit, send STOP condition

/* Clear TDI */
OTG_I2C_STS = TDI;
/* Set the VBUS_DISCHRG bit in ISP1302 */

OTG_I2C_TX = 0x006; // Send OTG Control (Set) register address
OTG_I2C_TX = 0x240; // Set VBUS_DISCHRG bit, send STOP condition

/* Clear TDI */
OTG_I2C_STS = TDI;

Load and enable OTG timer
/* The following assumes that the OTG timer has previously been */
/* configured for a time scale of 1 ms (TMR_SCALE = “10”) */

/* and monoshot mode (TMR_MODE = 0) */
/* Load the timeout value to implement the a_aidl_bdis_tmr timer */

/* the minimum value is 200 ms */
OTG_TIMER = 200;
/* Enable the timer */

OTG_STAT_CTRL |= TMR_EN;
Stop OTG timer
/* Disable the timer – causes TMR_CNT to be reset to 0 */

OTG_STAT_CTRL &= ~TMR_EN;
/* Clear TMR interrupt */

OTG_INT_CLR = TMR;
Suspend host on port 1
/* Write to PortSuspendStatus bit to suspend host port 1 – */

/* this example demonstrates the low-level action software needs to take. */
/* The host stack code where this is done will be somewhat more involved. */
HC_RH_PORT_STAT1 = PSS;
15.10 Clocking and power management

The OTG controller clocking is shown in Figure 81.
A clock switch controls each clock with the exception of ahb_slave_clk. When the enable
of the clock switch is asserted, its clock output is turned on and its CLK_ON output is
asserted. The CLK_ON signals are observable in the OTGClkSt register.
To conserve power, the clocks to the Device, Host, OTG, and I2C controllers can be
disabled when not in use by clearing the respective CLK_EN bit in the OTGClkCtrl
register. When the entire USB block is not in use, all of its clocks can be disabled by
clearing the PCUSB bit in the PCONP register.
When software wishes to access registers in one of the controllers, it should first ensure
that the respective controller’s 48 MHz clock is enabled by setting its CLK_EN bit in the
OTGClkCtrl register and then poll the corresponding CLK_ON bit in OTGClkSt until set.
Once set, the controller’s clock will remain enabled until CLK_EN is cleared by software.
Accessing the register of a controller when its 48 MHz clock is not enabled will result in a
data abort exception.

cclk ahb_slave_clk REGISTER

PCUSB INTERFACE
ahb_master_clk
CLOCK
SWITCH
EN AHB_CLK_ON
ahb_need_clk
AHB_CLK_EN
CLOCK dev_dma_need_clk
USB CLOCK SWITCH DEVICE
DIVIDER usbclk EN CONTROLLER dev_need_clk
DEV_CLK_ON
(48 MHz)
DEV_CLK_EN
CLOCK host_dma_need_clk
SWITCH HOST
EN CONTROLLER host_need_clk
HOST_CLK_ON
HOST_CLK_EN
CLOCK
SWITCH OTG USB_NEED_CLK
CONTROLLER
EN OTG_CLK_ON
OTG_CLK_EN
CLOCK
I2C
SWITCH
CONTROLLER
EN I2C_CLK_ON
I2C_CLK_EN
Fig 81. Clocking and power control
15.10.1 Device clock request signals

The Device controller has two clock request signals, dev_need_clk and
dev_dma_need_clk. When asserted, these signals turn on the device’s 48 MHz clock and
ahb_master_clk respectively.
The dev_need_clk signal is asserted while the device is not in the suspend state, or if the
device is in the suspend state and activity is detected on the USB bus. The dev_need_clk
signal is de-asserted if a disconnect is detected (CON bit is cleared in the SIE Get Device
Status register – Section 13.10.7). This signal allows DEV_CLK_EN to be cleared during
normal operation when software does not need to access the Device controller registers –
the Device will continue to function normally and automatically shut off its clock when it is
suspended or disconnected.

The dev_dma_need_clk signal is asserted on any Device controller DMA access to

memory. Once asserted, it remains active for 2 ms (2 frames), to help assure that DMA
throughput is not affected by any latency associated with re-enabling ahb_master_clk.
2 ms after the last DMA access, dev_dma_need_clk is de-asserted to help conserve
power. This signal allows AHB_CLK_EN to be cleared during normal operation.
15.10.1.1 Host clock request signals

The Host controller has two clock request signals, host_need_clk and
host_dma_need_clk. When asserted, these signals turn on the host’s 48 MHz clock and
ahb_master_clk respectively.
The host_need_clk signal is asserted while the Host controller functional state is not
UsbSuspend, or if the functional state is UsbSuspend and resume signaling or a
disconnect is detected on the USB bus. This signal allows HOST_CLK_EN to be cleared
during normal operation when software does not need to access the Host controller
registers – the Host will continue to function normally and automatically shut off its clock
when it goes into the UsbSuspend state.
The host_dma_need_clk signal is asserted on any Host controller DMA access to

memory. Once asserted, it remains active for 2 ms (2 frames), to help assure that DMA
throughput is not affected by any latency associated with re-enabling ahb_master_clk.
2 ms after the last DMA access, host_dma_need_clk is de-asserted to help conserve
power. This signal allows AHB_CLK_EN to be cleared during normal operation.
15.10.2 Power-down mode support

The LPC23xx can be configured to wake up from Power-down mode on any USB bus
activity. When the USBWAKE bit is set in the INTWAKE register, the assertion of the
USB_NEED_CLK signal causes the chip to wake up from Power Down.
Before Power-down mode can be entered when USBWAKE is set, USB_NEED_CLK

must be de-asserted. This is accomplished by clearing all of the CLK_EN bits in
OTGClkCtrl and putting the Host controller into the UsbSuspend functional state. If it is
necessary to wait for either of the dma_need_clk signals or the dev_need_clk to be
de-asserted, the status of USB_NEED_CLK can be polled in the USBIntSt register to
determine when they have all been de-asserted.
15.11 USB OTG controller initialization

The LPC23xx OTG device controller initialization includes the following steps:
1. Enable the device controller by setting the PCUSB bit of PCONP.

2. Configure and enable the PLL and Clock Dividers to provide 48 MHz for usbclk, and
the desired frequency for cclk. For correct operation of synchronization logic in the
device controller, the minimum cclk frequency is 18 MHz. For the procedure for
determining the PLL setting and configuration, see Section 4.6.12 “Procedure for
determining PLL settings”.
3. Enable the desired controller clocks by setting their respective CLK_EN bits in the
USBClkCtrl register. Poll the corresponding CLK_ON bits in the USBClkSt register
until they are set.

4. Enable the desired USB pin functions by writing to the corresponding PINSEL
registers.
5. Follow the appropriate steps in Section 13.13 “USB device controller initialization” to
initialize the device controller.
6. Follow the guidelines given in the OpenHCI specification for initializing the host
controller.

UM10211
Chapter 16: LPC23XX UART0/2/3

The UART0/2/3 peripherals are configured using the following registers:
1. Power: In the PCONP register (Table 56), set bits PCUART0/2/3.

Remark: On reset, UART0 is enabled (PCUART0 = 1), and UART2/3 are disabled
(PCUART2/3 = 0).
2. Peripheral clock: In the PCLK_SEL0 register (Table 49), select PCLK_UART0; in the
PCLK_SEL1 register (Table 50), select PCLK_UART2/3.
3. Baud rate: In register U0/2/3LCR (Table 359), set bit DLAB =1. This enables access
to registers DLL (Table 353) and DLM (Table 354) for setting the baud rate. Also, if
needed, set the fractional baud rate in the fractional divider register (Table 365).
4. UART FIFO: Use bit FIFO enable (bit 0) in register U0FCR (Table 358) to enable
FIFO.
5. Pins: Select UART pins and pin modes in registers PINSELn and PINMODEn (see
Section 9.5).
Remark: UART receive pins should not have pull-down resistors enabled.
6. Interrupts: To enable UART interrupts set bit DLAB =0 in register U0/2/3LCR
(Table 359). This enables access to U0/2/3IER (Table 356). Interrupts are enabled in
the VIC using the VICIntEnable register (Table 76).
16.2 Features
• 16 byte Receive and Transmit FIFOs.
• Register locations conform to ‘550 industry standard.
• Receiver FIFO trigger points at 1, 4, 8, and 14 bytes.
• Built-in baud rate generator.
• Fractional divider for baud rate control and implementation of software or hardware
flow control.
• UART3 includes an IrDA mode to support infrared communication.


Table 349. UART0 Pin description
Pin Type Description
RXD0, RXD2, RXD3 Input Serial Input. Serial receive data.
TXD0, TXD2, TXD3 Output Serial Output. Serial transmit data.

Each UART contains registers as shown in Table 350. The Divisor Latch Access Bit
(DLAB) is contained in UnLCR7 and enables access to the Divisor Latches.

xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxx x x x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xx xx xxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx x x
xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx
xxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxx xxx
User manual
UM10211
NXP Semiconductors
Table 350. UART Register Map
Generic Description Bit functions and addresses Access Reset UARTn Register
Name MSB LSB value[1] Name & Address
BIT7 BIT6 BIT5 BIT4 BIT3 BIT2 BIT1 BIT0

RBR Receiver Buffer 8 bit Read Data RO NA U0RBR -
(DLAB=0) Register 0xE000 C000
U2RBR - 0xE007 8000
U3RBR -
0xE007 C000
THR Transmit 8 bit Write Data WO NA U0THR - 0xE000 C000
(DLAB=0) Holding U2THR - 0xE007 8000
Register U3THR - 0xE007 C000
DLL Divisor Latch 8 bit Data R/W 0x01 U0DLL - 0xE000 C000
All information provided in this document is subject to legal disclaimers.
(DLAB=1) LSB U2DLL - 0xE007 8000

U3DLL - 0xE007 C000
Rev. 4.1 — 5 September 2012
DLM Divisor Latch 8 bit Data R/W 0x00 U0DLM -

(DLAB=1) MSB 0xE000 C004
U2DLM - 0xE007 8004
U3DLM -
0xE007 C004
IER Interrupt Enable Reserved Enable Enable End R/W 0x00 U0IER - 0xE000 C004
(DLAB=0) Register Auto- Baud of Auto- U2IER - 0xE007 8004
Time- Out Baud U3IER - 0xE007 C004
Interrupt Interrupt
0 Enable Enable Enable RX
RX Line THRE Data
Status Interrupt Available
Interrupt Interrupt

IIR Interrupt ID Reserved ABTOInt ABEOint RO 0x01 U0IIR - 0xE000 C008
Register FIFOs Enabled 0 IIR3 IIR2 IIR1 IIR0 U2IIR - 0xE007 8008
U3IIR - 0xE007 C008
FCR FIFO Control RX Trigger Reserved TX FIFO RX FIFO FIFO WO 0x00 U0FCR - 0xE000 C008
Register Reset Reset Enable U2FCR - 0xE007 8008
UM10211
© NXP B.V. 2012. All rights reserved.
U3FCR - 0xE007 C008

LCR Line Control DLAB Set Stick Even Parity Number Word Length Select R/W 0x00 U0LCR -
Register Break Parity Parity Enable of Stop 0xE000 C00C
Select Bits U2LCR - 0xE007 800C
414 of 708
U3LCR -
0xE007 C00C
Table 350. UART Register Map
User manual
UM10211
NXP Semiconductors
Generic Description Bit functions and addresses Access Reset UARTn Register
Name MSB LSB value[1] Name & Address
LSR Line Status RX TEMT THRE BI FE PE OE DR RO 0x60 U0LSR - 0xE000 C014

Register FIFO U2LSR - 0xE007 8014
Error U3LSR - 0xE007 C014
SCR Scratch Pad 8 bit Data R/W 0x00 U0SCR -
Register 0xE000 C01C
U2SCR -
0xE007 801C
U3SCR -
0xE007 C01C
ACR Auto-baud Reserved [31:10] ABTO ABEO R/W 0x00 U0ACR -
Control IntClr IntClr 0xE000 C020
Register Reserved [7:3] Auto Mode Start U2ACR - 0xE007 8020

Reset U3ACR -
0xE007 C020
ICR IrDA Control Reserved PulseDiv FixPulse IrDAInv IrDAEn R/W 0 U3ICR - 0xE000 C024
Register En (UART3 only)
FDR Fractional MulVal DivAddVal R/W 0x10 U0FDR - 0xE000 C028
Divider Register U2FDR - 0xE007 8028
U3FDR - 0xE007 C028
TER Transmit TXEN Reserved R/W 0x80 U0TER - 0xE000 C030
Enable Register U2TER - 0xE007 8030
U3TER - 0xE007 C030

UM10211
415 of 708
16.4.1 UARTn Receiver Buffer Register (U0RBR - 0xE000 C000, U2RBR -

0xE007 8000, U3RBR - 0xE007 C000 when DLAB = 0, Read Only)
The UnRBR is the top byte of the UARTn Rx FIFO. The top byte of the Rx FIFO contains
the oldest character received and can be read via the bus interface. The LSB (bit 0)
represents the “oldest” received data bit. If the character received is less than 8 bits, the
unused MSBs are padded with zeroes.
The Divisor Latch Access Bit (DLAB) in LCR must be zero in order to access the UnRBR.
The UnRBR is always Read Only.
Since PE, FE and BI bits correspond to the byte sitting on the top of the RBR FIFO (i.e.
the one that will be read in the next read from the RBR), the right approach for fetching the
valid pair of received byte and its status bits is first to read the content of the U0LSR
register, and then to read a byte from the UnRBR.
Table 351. UARTn Receiver Buffer Register (U0RBR - address 0xE000 C000,
U2RBR - 0xE007 8000, U3RBR - 0E007 C000 when DLAB = 0, Read Only) bit
description
Bit Symbol Description Reset Value
7:0 RBR The UARTn Receiver Buffer Register contains the oldest Undefined
received byte in the UARTn Rx FIFO.
16.4.2 UARTn Transmit Holding Register (U0THR - 0xE000 C000, U2THR -

0xE007 8000, U3THR - 0xE007 C000 when DLAB = 0, Write Only)
The UnTHR is the top byte of the UARTn TX FIFO. The top byte is the newest character in
the TX FIFO and can be written via the bus interface. The LSB represents the first bit to
transmit.
The Divisor Latch Access Bit (DLAB) in UnLCR must be zero in order to access the
UnTHR. The UnTHR is always Write Only.
Table 352. UART0 Transmit Holding Register (U0THR - address 0xE000 C000,
U2THR - 0xE007 8000, U3THR - 0xE007 C000 when DLAB = 0, Write Only) bit
description
7:0 THR Writing to the UARTn Transmit Holding Register causes the data NA
to be stored in the UARTn transmit FIFO. The byte will be sent
when it reaches the bottom of the FIFO and the transmitter is
available.
16.4.3 UARTn Divisor Latch LSB Register (U0DLL - 0xE000 C000, U2DLL -
0xE007 8000, U3DLL - 0xE007 C000 when DLAB = 1) and UARTn
Divisor Latch MSB Register (U0DLM - 0xE000 C004, U2DLL -
0xE007 8004, U3DLL - 0xE007 C004 when DLAB = 1)
The UARTn Divisor Latch is part of the UARTn Baud Rate Generator and holds the value
used to divide the APB clock (PCLK) in order to produce the baud rate clock, which must
be 16 the desired baud rate (see Equation 7). The UnDLL and UnDLM registers together
form a 16 bit divisor where UnDLL contains the lower 8 bits of the divisor and UnDLM
contains the higher 8 bits of the divisor. A 0x0000 value is treated like a 0x0001 value as

division by zero is not allowed. The Divisor Latch Access Bit (DLAB) in UnLCR must be
one in order to access the UARTn Divisor Latches. Details on how to select the right value
for UnDLL and UnDLM can be found in Section 16.4.12.
(7)
pclk
UARTn baudrate = --------------------------------------------------------------------------------
16   256  UnDLM + UnDLL 
Table 353. UARTn Divisor Latch LSB Register (U0DLL - address 0xE000 C000,
U2DLL - 0xE007 8000, U3DLL - 0xE007 C000 when DLAB = 1) bit description
7:0 DLLSB The UARTn Divisor Latch LSB Register, along with the UnDLM 0x01
register, determines the baud rate of the UARTn.
Table 354. UARTn Divisor Latch MSB Register (U0DLM - address 0xE000 C004,
U2DLM - 0xE007 8004, U3DLM - 0xE007 C004 when DLAB = 1) bit description
7:0 DLMSB The UARTn Divisor Latch MSB Register, along with the U0DLL 0x00
register, determines the baud rate of the UARTn.
16.4.4 UARTn Interrupt Enable Register (U0IER - 0xE000 C004, U2IER -

0xE007 8004, U3IER - 0xE007 C004 when DLAB = 0)
The UnIER is used to enable the three UARTn interrupt sources.
Table 355. UARTn Interrupt Enable Register (U0IER - address 0xE000 C004,
U2IER - 0xE007 8004, U3IER - 0xE007 C004 when DLAB = 0) bit description
Value
0 RBR UnIER[0] enables the Receive Data Available interrupt for 0
Interrupt UARTn. It also controls the Character Receive Time-out
Enable interrupt.
0 Disable the RDA interrupts.
1 Enable the RDA interrupts.
1 THRE 0 UnIER[1] enables the THRE interrupt for UARTn. The 0
Interrupt status of this can be read from UnLSR[5].
Enable Disable the THRE interrupts.
1 Enable the THRE interrupts.
2 RX Line 0 UnIER[2] enables the UARTn RX line status interrupts. 0
Status The status of this interrupt can be read from UnLSR[4:1].
Interrupt Disable the RX line status interrupts.
Enable
1 Enable the RX line status interrupts.

Table 355. UARTn Interrupt Enable Register (U0IER - address 0xE000 C004,
U2IER - 0xE007 8004, U3IER - 0xE007 C004 when DLAB = 0) bit description
Value
8 ABEOIntEn enables the end of auto-baud interrupt. 0
0 Disable End of Auto-baud Interrupt.
1 Enable End of Auto-baud Interrupt.
9 ABTOIntEn enables the auto-baud time-out interrupt. 0
0 Disable Auto-baud Time-out Interrupt.
1 Enable Auto-baud Time-out Interrupt.
16.4.5 UARTn Interrupt Identification Register (U0IIR - 0xE000 C008, U2IIR -

0xE007 8008, U3IIR - 0x7008 C008, Read Only)
The UnIIR provides a status code that denotes the priority and source of a pending
interrupt. The interrupts are frozen during an UnIIR access. If an interrupt occurs during
an UnIIR access, the interrupt is recorded for the next UnIIR access.
Table 356. UARTn Interrupt Identification Register (U0IIR - address 0xE000 C008,
U2IIR - 0x7008 8008, U3IIR - 0x7008 C008, Read Only) bit description
Value
0 IntStatus Interrupt status. Note that U1IIR[0] is active low. The 1
pending interrupt can be determined by evaluating
UnIIR[3:1].
0 At least one interrupt is pending.
1 No interrupt is pending.
3:1 IntId Interrupt identification. UnIER[3:1] identifies an interrupt 0
corresponding to the UARTn Rx FIFO. All other
combinations of UnIER[3:1] not listed above are reserved
(000,100,101,111).
011 1 - Receive Line Status (RLS).
010 2a - Receive Data Available (RDA).
110 2b - Character Time-out Indicator (CTI).
001 3 - THRE Interrupt
7:6 FIFO Enable These bits are equivalent to UnFCR[0]. 0
8 ABEOInt End of auto-baud interrupt. True if auto-baud has finished 0
successfully and interrupt is enabled.
9 ABTOInt Auto-baud time-out interrupt. True if auto-baud has timed 0
out and interrupt is enabled.

Bit UnIIR[9:8] are set by the auto-baud function and signal a time-out or end of auto-baud
condition. The auto-baud interrupt conditions are cleared by setting the corresponding
Clear bits in the Auto-baud Control Register.
If the IntStatus bit is 1 no interrupt is pending and the IntId bits will be zero. If the IntStatus
is 0, a non auto-baud interrupt is pending in which case the IntId bits identify the type of
interrupt and handling as described in Table 357. Given the status of UnIIR[3:0], an
interrupt handler routine can determine the cause of the interrupt and how to clear the
active interrupt. The UnIIR must be read in order to clear the interrupt prior to exiting the
Interrupt Service Routine.
The UARTn RLS interrupt (UnIIR[3:1] = 011) is the highest priority interrupt and is set
whenever any one of four error conditions occur on the UARTn Rx input: overrun error
(OE), parity error (PE), framing error (FE) and break interrupt (BI). The UARTn Rx error
condition that set the interrupt can be observed via U0LSR[4:1]. The interrupt is cleared
upon an UnLSR read.
The UARTn RDA interrupt (UnIIR[3:1] = 010) shares the second level priority with the CTI
interrupt (UnIIR[3:1] = 110). The RDA is activated when the UARTn Rx FIFO reaches the
trigger level defined in UnFCR[7:6] and is reset when the UARTn Rx FIFO depth falls
below the trigger level. When the RDA interrupt goes active, the CPU can read a block of
data defined by the trigger level.
The CTI interrupt (UnIIR[3:1] = 110) is a second level interrupt and is set when the UARTn
Rx FIFO contains at least one character and no UARTn Rx FIFO activity has occurred in
3.5 to 4.5 character times. Any UARTn Rx FIFO activity (read or write of UARTn RSR) will
clear the interrupt. This interrupt is intended to flush the UARTn RBR after a message has
been received that is not a multiple of the trigger level size. For example, if a peripheral
wished to send a 105 character message and the trigger level was 10 characters, the
CPU would receive 10 RDA interrupts resulting in the transfer of 100 characters and 1 to 5
CTI interrupts (depending on the service routine) resulting in the transfer of the remaining
5 characters.
Table 357. UARTn Interrupt Handling

U0IIR[3:0] Priority Interrupt Type Interrupt Source Interrupt Reset
value[1]
0001 - None None -
0110 Highest RX Line Status OE[2] or PE[2] or FE[2] or BI[2] UnLSR Read[2]
/ Error

Table 357. UARTn Interrupt Handling

U0IIR[3:0] Priority Interrupt Type Interrupt Source Interrupt Reset
value[1]
0100 Second RX Data Rx data available or trigger level reached UnRBR Read[3]
Available in FIFO (UnFCR0=1) or UARTn FIFO
drops below
trigger level
1100 Second Character Minimum of one character in the Rx UnRBR Read[3]
Time-out FIFO and no character input or removed
indication during a time period depending on how
many characters are in FIFO and what
the trigger level is set at (3.5 to 4.5
character times).
The exact time will be:
[(word length)  7 - 2]  8 + [(trigger level
- number of characters)  8 + 1] RCLKs
0010 Third THRE THRE[2] UnIIR Read (if
source of
interrupt) or
THR write[4]
[1] Values "0000", “0011”, “0101”, “0111”, “1000”, “1001”, “1010”, “1011”,”1101”,”1110”,”1111” are reserved.
[2] For details see Section 16.4.8 “UARTn Line Status Register (U0LSR - 0xE000 C014, U2LSR -
0xE007 8014, U3LSR - 0xE007 C014, Read Only)”
[3] For details see Section 16.4.1 “UARTn Receiver Buffer Register (U0RBR - 0xE000 C000, U2RBR -
0xE007 8000, U3RBR - 0xE007 C000 when DLAB = 0, Read Only)”
[4] For details see Section 16.4.5 “UARTn Interrupt Identification Register (U0IIR - 0xE000 C008, U2IIR -
0xE007 8008, U3IIR - 0x7008 C008, Read Only)” and Section 16.4.2 “UARTn Transmit Holding Register
(U0THR - 0xE000 C000, U2THR - 0xE007 8000, U3THR - 0xE007 C000 when DLAB = 0, Write Only)”
The UARTn THRE interrupt (UnIIR[3:1] = 001) is a third level interrupt and is activated
when the UARTn THR FIFO is empty provided certain initialization conditions have been
met. These initialization conditions are intended to give the UARTn THR FIFO a chance to
fill up with data to eliminate many THRE interrupts from occurring at system start-up. The
initialization conditions implement a one character delay minus the stop bit whenever
THRE = 1 and there have not been at least two characters in the UnTHR at one time
since the last THRE = 1 event. This delay is provided to give the CPU time to write data to
UnTHR without a THRE interrupt to decode and service. A THRE interrupt is set
immediately if the UARTn THR FIFO has held two or more characters at one time and
currently, the UnTHR is empty. The THRE interrupt is reset when a UnTHR write occurs or
a read of the UnIIR occurs and the THRE is the highest interrupt (UnIIR[3:1] = 001).
16.4.6 UARTn FIFO Control Register (U0FCR - 0xE000 C008, U2FCR -

0xE007 8008, U3FCR - 0xE007 C008, Write Only)
The UnFCR controls the operation of the UARTn Rx and TX FIFOs.

Table 358. UARTn FIFO Control Register (U0FCR - address 0xE000 C008,
U2FCR - 0xE007 8008, U3FCR - 0xE007 C008, Write Only) bit description
Bit Symbol Value Description Reset Value
0 FIFO Enable 0 UARTn FIFOs are disabled. Must not be used in the 0
application.
1 Active high enable for both UARTn Rx and TX
FIFOs and UnFCR[7:1] access. This bit must be set
for proper UARTn operation. Any transition on this
bit will automatically clear the UARTn FIFOs.
1 RX FIFO 0 No impact on either of UARTn FIFOs. 0
Reset 1 Writing a logic 1 to UnFCR[1] will clear all bytes in
UARTn Rx FIFO and reset the pointer logic. This bit
is self-clearing.
2 TX FIFO 0 No impact on either of UARTn FIFOs. 0
Reset 1 Writing a logic 1 to UnFCR[2] will clear all bytes in
UARTn TX FIFO and reset the pointer logic. This bit
is self-clearing.
5:3 - 0 Reserved, user software should not write ones to NA
not defined.
7:6 RX Trigger These two bits determine how many receiver 0
Level UARTn FIFO characters must be written before an
interrupt is activated.
00 Trigger level 0 (1 character or 0x01)
01 Trigger level 1 (4 characters or 0x04)
10 Trigger level 2 (8 characters or 0x08)
11 Trigger level 3 (14 characters or 0x0E)
16.4.7 UARTn Line Control Register (U0LCR - 0xE000 C00C, U2LCR -

0xE007 800C, U3LCR - 0xE007 C00C)
The UnLCR determines the format of the data character that is to be transmitted or
received.
Table 359. UARTn Line Control Register (U0LCR - address 0xE000 C00C,
U2LCR - 0xE007 800C, U3LCR - 0xE007 C00C) bit description
Value
1:0 Word Length 00 5 bit character length 0
Select 01 6 bit character length
10 7 bit character length
11 8 bit character length
2 Stop Bit Select 0 1 stop bit. 0
1 2 stop bits (1.5 if UnLCR[1:0]=00).
3 Parity Enable 0 Disable parity generation and checking. 0
1 Enable parity generation and checking.

Table 359. UARTn Line Control Register (U0LCR - address 0xE000 C00C,
U2LCR - 0xE007 800C, U3LCR - 0xE007 C00C) bit description
Value
5:4 Parity Select 00 Odd parity. Number of 1s in the transmitted character and 0
the attached parity bit will be odd.
01 Even Parity. Number of 1s in the transmitted character and
the attached parity bit will be even.
10 Forced "1" stick parity.
6 Break Control 0 Disable break transmission. 0
1 Enable break transmission. Output pin UART0 TXD is
forced to logic 0 when UnLCR[6] is active high.
7 Divisor Latch 0 Disable access to Divisor Latches. 0
Access Bit 1 Enable access to Divisor Latches.
(DLAB)
16.4.8 UARTn Line Status Register (U0LSR - 0xE000 C014, U2LSR -

0xE007 8014, U3LSR - 0xE007 C014, Read Only)
The UnLSR is a read-only register that provides status information on the UARTn TX and
RX blocks.
Table 360. UARTn Line Status Register (U0LSR - address 0xE000 C014,
U2LSR - 0xE007 8014, U3LSR - 0xE007 C014, Read Only) bit description
Value
0 Receiver UnLSR0 is set when the UnRBR holds an unread character 0
Data Ready and is cleared when the UARTn RBR FIFO is empty.
(RDR) 0 UnRBR is empty.
1 UnRBR contains valid data.
1 Overrun Error The overrun error condition is set as soon as it occurs. An 0
(OE) UnLSR read clears UnLSR1. UnLSR1 is set when UARTn
RSR has a new character assembled and the UARTn RBR
FIFO is full. In this case, the UARTn RBR FIFO will not be
overwritten and the character in the UARTn RSR will be lost.
0 Overrun error status is inactive.
1 Overrun error status is active.
2 Parity Error When the parity bit of a received character is in the wrong 0
(PE) state, a parity error occurs. An UnLSR read clears UnLSR[2].
Time of parity error detection is dependent on UnFCR[0].
Note: A parity error is associated with the character at the top
of the UARTn RBR FIFO.
0 Parity error status is inactive.
1 Parity error status is active.

Table 360. UARTn Line Status Register (U0LSR - address 0xE000 C014,
U2LSR - 0xE007 8014, U3LSR - 0xE007 C014, Read Only) bit description
Value
3 Framing Error When the stop bit of a received character is a logic 0, a 0
(FE) framing error occurs. An UnLSR read clears UnLSR[3]. The
time of the framing error detection is dependent on UnFCR0.
Upon detection of a framing error, the Rx will attempt to
resynchronize to the data and assume that the bad stop bit is
actually an early start bit. However, it cannot be assumed that
the next received byte will be correct even if there is no
Framing Error.
Note: A framing error is associated with the character at the
top of the UARTn RBR FIFO.
0 Framing error status is inactive.
1 Framing error status is active.
4 Break When RXDn is held in the spacing state (all 0’s) for one full 0
Interrupt character transmission (start, data, parity, stop), a break
(BI) interrupt occurs. Once the break condition has been detected,
the receiver goes idle until RXDn goes to marking state (all
1’s). An UnLSR read clears this status bit. The time of break
detection is dependent on UnFCR[0].
Note: The break interrupt is associated with the character at
the top of the UARTn RBR FIFO.
0 Break interrupt status is inactive.
1 Break interrupt status is active.
5 Transmitter THRE is set immediately upon detection of an empty UARTn 1
Holding THR and is cleared on a UnTHR write.
Register 0 UnTHR contains valid data.
Empty
(THRE)) 1 UnTHR is empty.
6 Transmitter TEMT is set when both UnTHR and UnTSR are empty; TEMT 1
Empty is cleared when either the UnTSR or the UnTHR contain valid
(TEMT) data.
0 UnTHR and/or the UnTSR contains valid data.
1 UnTHR and the UnTSR are empty.
7 Error in RX UnLSR[7] is set when a character with a Rx error such as 0
FIFO framing error, parity error or break interrupt, is loaded into the
(RXFE) UnRBR. This bit is cleared when the UnLSR register is read
and there are no subsequent errors in the UARTn FIFO.
0 UnRBR contains no UARTn RX errors or UnFCR[0]=0.
1 UARTn RBR contains at least one UARTn RX error.
16.4.9 UARTn Scratch Pad Register (U0SCR - 0xE000 C01C, U2SCR -

0xE007 801C U3SCR - 0xE007 C01C)
The UnSCR has no effect on the UARTn operation. This register can be written and/or
read at user’s discretion. There is no provision in the interrupt interface that would indicate
to the host that a read or write of the UnSCR has occurred.

Table 361. UARTn Scratch Pad Register (U0SCR - address 0xE000 C01C,
U2SCR - 0xE007 801C, U3SCR - 0xE007 C01C) bit description
Value
7:0 Pad A readable, writable byte. 0x00
16.4.10 UARTn Auto-baud Control Register (U0ACR - 0xE000 C020, U2ACR -

0xE007 8020, U3ACR - 0xE007 C020)
The UARTn Auto-baud Control Register (UnACR) controls the process of measuring the
incoming clock/data rate for the baud rate generation and can be read and written at
user’s discretion.
Table 362. UARTn Auto-baud Control Register (U0ACR - 0xE000 C020, U2ACR -
0xE007 8020, U3ACR - 0xE007 C020) bit description
0 Start This bit is automatically cleared after auto-baud 0
completion.
0 Auto-baud stop (auto-baud is not running).
1 Auto-baud start (auto-baud is running).Auto-baud run
bit. This bit is automatically cleared after auto-baud
completion.
1 Mode Auto-baud mode select bit. 0
0 Mode 0.
1 Mode 1.
2 AutoRestart 0 No restart. 0
1 Restart in case of time-out (counter restarts at next 0
UART0 Rx falling edge)
7:3 - NA Reserved, user software should not write ones to 0
defined.
8 ABEOIntClr End of auto-baud interrupt clear bit (write only 0
accessible). Writing a 1 will clear the corresponding
interrupt in the UnIIR. Writing a 0 has no impact.
9 ABTOIntClr Auto-baud time-out interrupt clear bit (write only 0
accessible). Writing a 1 will clear the corresponding
interrupt in the UnIIR. Writing a 0 has no impact.
defined.
16.4.10.1 Auto-baud
The UARTn auto-baud function can be used to measure the incoming baud-rate based on
the ”AT" protocol (Hayes command). If enabled the auto-baud feature will measure the bit
time of the receive data stream and set the divisor latch registers UnDLM and UnDLL
accordingly.
Auto-baud is started by setting the UnACR Start bit. Auto-baud can be stopped by clearing
the UnACR Start bit. The Start bit will clear once auto-baud has finished and reading the
bit will return the status of auto-baud (pending/finished).

Two auto-baud measuring modes are available which can be selected by the UnACR
Mode bit. In mode 0 the baud-rate is measured on two subsequent falling edges of the
UARTn Rx pin (the falling edge of the start bit and the falling edge of the least significant
bit). In mode 1 the baud-rate is measured between the falling edge and the subsequent
rising edge of the UARTn Rx pin (the length of the start bit).
The UnACR AutoRestart bit can be used to automatically restart baud-rate measurement
if a time-out occurs (the rate measurement counter overflows). If this bit is set the rate
measurement will restart at the next falling edge of the UARTn Rx pin.
The auto-baud function can generate two interrupts.
• The UnIIR ABTOInt interrupt will get set if the interrupt is enabled (UnIER ABToIntEn
is set and the auto-baud rate measurement counter overflows).
• The UnIIR ABEOInt interrupt will get set if the interrupt is enabled (UnIER ABEOIntEn
is set and the auto-baud has completed successfully).
The auto-baud interrupts have to be cleared by setting the corresponding UnACR

ABTOIntClr and ABEOIntEn bits.
The fractional baud-rate generator is disabled (DIVADDVAL = 0) during auto-baud. When

auto-baud is used, any write to UnDLM and UnDLL registers should be done before
UnACR register write. The minimum and the maximum baudrates supported by UARTn
are function of pclk, number of data bits, stop bits and parity bits.
(8)
2  P CLK PCLK
ratemin = -------------------------  UART n baudrate  ------------------------------------------------------------------------------------------------------------ = ratemax
16  2 15 16   2 + databits + paritybits + stopbits 
16.4.10.2 Auto-baud modes

When the software is expecting an ”AT" command, it configures the UARTn with the
expected character format and sets the UnACR Start bit. The initial values in the divisor
latches UnDLM and UnDLM don‘t care. Because of the ”A" or ”a" ASCII coding
(”A" = 0x41, ”a" = 0x61), the UARTn Rx pin sensed start bit and the LSB of the expected
character are delimited by two falling edges. When the UnACR Start bit is set, the
auto-baud protocol will execute the following phases:
1. On UnACR Start bit setting, the baud-rate measurement counter is reset and the
UARTn UnRSR is reset. The UnRSR baud rate is switch to the highest rate.
2. A falling edge on UARTn Rx pin triggers the beginning of the start bit. The rate
measuring counter will start counting pclk cycles.
3. During the receipt of the start bit, 16 pulses are generated on the RSR baud input with
the frequency of the UARTn input clock, guaranteeing the start bit is stored in the
UnRSR.
4. During the receipt of the start bit (and the character LSB for mode = 0) the rate
counter will continue incrementing with the pre-scaled UARTn input clock (pclk).
5. If Mode = 0 then the rate counter will stop on next falling edge of the UARTn Rx pin. If
Mode = 1 then the rate counter will stop on the next rising edge of the UARTn Rx pin.

6. The rate counter is loaded into UnDLM/UnDLL and the baud-rate will be switched to
normal operation. After setting the UnDLM/UnDLL the end of auto-baud interrupt
UnIIR ABEOInt will be set, if enabled. The UnRSR will now continue receiving the
remaining bits of the ”A/a" character.
'A' (0x41) or 'a' (0x61)
start bit0 bit1 bit2 bit3 bit4 bit5 bit6 bit7 parity stop
UARTn RX
start bit LSB of 'A' or 'a'
U0ACR start
rate counter
16xbaud_rate
16 cycles 16 cycles
a. Mode 0 (start bit and LSB are used for auto-baud)
'A' (0x41) or 'a' (0x61)
UARTn RX
U1ACR start
rate counter
16xbaud_rate
16 cycles
b. Mode 1 (only start bit is used for auto-baud)

Fig 82. Autobaud a) mode 0 and b) mode 1 waveform
16.4.11 IrDA Control Register for UART3 Only (U3ICR - 0xE007 C024)
The IrDA Control Register enables and configures the IrDA mode for UART3 only. The
value of U3ICR should not be changed while transmitting or receiving data, or data loss or
corruption may occur.

Table 363. IrDA Control Register for UART3 only (U3ICR - address 0xE007 C024) bit
description
0 IrDAEn 0 IrDA mode on UART3 is disabled, UART3 acts as a 0
standard UART.
1 IrDA mode on UART3 is enabled.
1 IrDAInv When 1, the serial input is inverted. This has no effect 0
on the serial output. When 0, the serial input is not
inverted.
2 FixPulseEn When 1, enabled IrDA fixed pulse width mode. 0
5:3 PulseDiv Configures the pulse when FixPulseEn = 1. See text 0
below for details.
not defined.
The PulseDiv bits in U3ICR are used to select the pulse width when the fixed pulse width
mode is used in IrDA mode (IrDAEn = 1 and FixPulseEn = 1). The value of these bits
should be set so that the resulting pulse width is at least 1.63 µs. Table 364 shows the
possible pulse widths.
Table 364. IrDA Pulse Width

FixPulseEn PulseDiv IrDA Transmitter Pulse width (µs)
0 x 3 / (16  baud rate)
1 0 2  TPCLK
1 1 4  TPCLK
1 2 8  TPCLK
1 3 16  TPCLK
1 4 32  TPCLK
1 5 64  TPCLK
1 6 128  TPCLK
1 7 256  TPCLK
16.4.12 UARTn Fractional Divider Register (U0FDR - 0xE000 C028, U2FDR -

0xE007 8028, U3FDR - 0xE007 C028)
The UART0/2/3 Fractional Divider Register (U0/2/3FDR) controls the clock pre-scaler for
the baud rate generation and can be read and written at the user’s discretion. This
pre-scaler takes the APB clock and generates an output clock according to the specified
fractional requirements.
Important: If the fractional divider is active (DIVADDVAL > 0) and DLM = 0, the value of
the DLL register must be 3 or greater.

Table 365. UARTn Fractional Divider Register (U0FDR - address 0xE000 C028,
U2FDR - 0xE007 8028, U3FDR - 0xE007 C028) bit description
Bit Function Value Description Reset
value
3:0 DIVADDVAL 0 Baud-rate generation pre-scaler divisor value. If this field is 0
0, fractional baud-rate generator will not impact the UARTn
baudrate.
7:4 MULVAL 1 Baud-rate pre-scaler multiplier value. This field must be 1
greater or equal 1 for UARTn to operate properly,
regardless of whether the fractional baud-rate generator is
used or not.
31:8 - NA Reserved, user software should not write ones to reserved 0
This register controls the clock pre-scaler for the baud rate generation. The reset value of
the register keeps the fractional capabilities of UART0/2/3 disabled making sure that
UART0/2/3 is fully software and hardware compatible with UARTs not equipped with this
feature.
UART0/2/3 baudrate can be calculated as (n = 0/2/3):
(9)
PCLK
UARTn baudrate = ----------------------------------------------------------------------------------------------------------------------------------
16   256  UnDLM + UnDLL    1 + -----------------------------
DivAddVal
 MulVal 
Where PCLK is the peripheral clock, U0/2/3DLM and U0/2/3DLL are the standard
UART0/2/3 baud rate divider registers, and DIVADDVAL and MULVAL are UART0/2/3
fractional baudrate generator specific parameters.
The value of MULVAL and DIVADDVAL should comply to the following conditions:
1. 1  MULVAL  15
2. 0  DIVADDVAL  14
3. DIVADDVAL< MULVAL
The value of the U0/2/3FDR should not be modified while transmitting/receiving data or
data may be lost or corrupted.
If the U0/2/3FDR register value does not comply to these two requests, then the fractional
divider output is undefined. If DIVADDVAL is zero then the fractional divider is disabled,
and the clock will not be divided.
16.4.12.1 Baudrate calculation

UART can operate with or without using the Fractional Divider. In real-life applications it is
likely that the desired baudrate can be achieved using several different Fractional Divider
settings. The following algorithm illustrates one way of finding a set of DLM, DLL,
MULVAL, and DIVADDVAL values. Such set of parameters yields a baudrate with a
relative error of less than 1.1% from the desired one.

Calculating UART
baudrate (BR)
PCLK,
BR
DL est = PCLK/(16 x BR)
DL est is an True
integer?
False DIVADDVAL = 0
MULVAL = 1
FR est = 1.5
Pick another FR est from

the range [1.1, 1.9] DL est = Int(PCLK/(16 x BR x FR est))
FR est = PCLK/(16 x BR x DL est)
False
1.1 < FR est < 1.9?
True
DIVADDVAL = table(FR est )

MULVAL = table(FR est )
DLM = DL est[15:8]
DLL = DL est [7:0]
End
Fig 83. Algorithm for setting UART dividers

Table 366. Fractional Divider setting look-up table

FR DivAddVal/ FR DivAddVal/ FR DivAddVal/ FR DivAddVal/
MulVal MulVal MulVal MulVal
1.000 0/1 1.250 1/4 1.500 1/2 1.750 3/4
1.067 1/15 1.267 4/15 1.533 8/15 1.769 10/13
1.071 1/14 1.273 3/11 1.538 7/13 1.778 7/9
1.077 1/13 1.286 2/7 1.545 6/11 1.786 11/14
1.083 1/12 1.300 3/10 1.556 5/9 1.800 4/5
1.091 1/11 1.308 4/13 1.571 4/7 1.818 9/11
1.100 1/10 1.333 1/3 1.583 7/12 1.833 5/6
1.111 1/9 1.357 5/14 1.600 3/5 1.846 11/13
1.125 1/8 1.364 4/11 1.615 8/13 1.857 6/7
1.133 2/15 1.375 3/8 1.625 5/8 1.867 13/15
1.143 1/7 1.385 5/13 1.636 7/11 1.875 7/8
1.154 2/13 1.400 2/5 1.643 9/14 1.889 8/9
1.167 1/6 1.417 5/12 1.667 2/3 1.900 9/10
1.182 2/11 1.429 3/7 1.692 9/13 1.909 10/11
1.200 1/5 1.444 4/9 1.700 7/10 1.917 11/12
1.214 3/14 1.455 5/11 1.714 5/7 1.923 12/13
1.222 2/9 1.462 6/13 1.727 8/11 1.929 13/14
1.231 3/13 1.467 7/15 1.733 11/15 1.933 14/15
16.4.12.1.1 Example 1: PCLK = 14.7456 MHz, BR = 9600

According to the provided algorithm DLest = PCLK/(16 x BR) = 14.7456 MHz / (16 x 9600)
= 96. Since this DLest is an integer number, DIVADDVAL = 0, MULVAL = 1, DLM = 0, and
DLL = 96.
16.4.12.1.2 Example 2: PCLK = 12 MHz, BR = 115200

According to the provided algorithm DLest = PCLK/(16 x BR) = 12 MHz / (16 x 115200) =
6.51. This DLest is not an integer number and the next step is to estimate the FR
parameter. Using an initial estimate of FRest = 1.5 a new DLest = 4 is calculated and FRest
is recalculated as FRest = 1.628. Since FRest = 1.628 is within the specified range of 1.1
and 1.9, DIVADDVAL and MULVAL values can be obtained from the attached look-up
table.
The closest value for FRest = 1.628 in the look-up Table 366 is FR = 1.625. It is
equivalent to DIVADDVAL = 5 and MULVAL = 8.
Based on these findings, the suggested UART setup would be: DLM = 0, DLL = 4,
DIVADDVAL = 5, and MULVAL = 8. According to Equation 9 UART’s is 115384. This rate
has a relative error of 0.16% from the originally specified 115200.
16.4.13 UARTn Transmit Enable Register (U0TER - 0xE000 C030, U2TER -

0xE007 8030, U3TER - 0xE007 C030)
LPC2300’s UnTER enables implementation of software flow control. When TXEn=1,
UARTn transmitter will keep sending data as long as they are available. As soon as TXEn
becomes 0, UARTn transmission will stop.

Table 367 describes how to use TXEn bit in order to achieve software flow control.
Table 367. UARTn Transmit Enable Register (U0TER - address 0xE000 C030,
U2TER - 0xE007 8030, U3TER - 0xE007 C030) bit description
Value
7 TXEN When this bit is 1, as it is after a Reset, data written to the THR is output 1
on the TXD pin as soon as any preceding data has been sent. If this bit
is cleared to 0 while a character is being sent, the transmission of that
character is completed, but no further characters are sent until this bit is
set again. In other words, a 0 in this bit blocks the transfer of characters
from the THR or TX FIFO into the transmit shift register. Software
implementing software-handshaking can clear this bit when it receives
an XOFF character (DC3). Software can set this bit again when it
receives an XON (DC1) character.
16.5 Architecture
The architecture of the UARTs 0, 2 and 3 are shown below in the block diagram.
The APB interface provides a communications link between the CPU or host and the
UART.
The UARTn receiver block, UnRX, monitors the serial input line, RXDn, for valid input.
The UARTn RX Shift Register (UnRSR) accepts valid characters via RXDn. After a valid
character is assembled in the UnRSR, it is passed to the UARTn RX Buffer Register FIFO
to await access by the CPU or host via the generic host interface.
The UARTn transmitter block, UnTX, accepts data written by the CPU or host and buffers
the data in the UARTn TX Holding Register FIFO (UnTHR). The UARTn TX Shift Register
(UnTSR) reads the data stored in the UnTHR and assembles the data to transmit via the
serial output pin, TXDn.
The UARTn Baud Rate Generator block, UnBRG, generates the timing enables used by
the UARTn TX block. The UnBRG clock input source is the APB clock (PCLK). The main
clock is divided down per the divisor specified in the UnDLL and UnDLM registers. This
divided down clock is a 16x oversample clock, NBAUDOUT.
The interrupt interface contains registers UnIER and UnIIR. The interrupt interface
receives several one clock wide enables from the UnTX and UnRX blocks.
Status information from the UnTX and UnRX is stored in the UnLSR. Control information
for the UnTX and UnRX is stored in the UnLCR.

UnTX
NTXRDY
TXDn
UnTHR UnTSR
UnBRG
UnDLL NBAUDOUT
UnDLM RCLK
UnRX
NRXRDY
INTERRUPT
RXDn
UnRBR UnRSR
UnINTR UnIER
UnIIR
UnFCR
UnLSR
UnSCR
UnLCR
PA[2:0]
PSEL
PSTB
PWRITE
APB
PD[7:0] DDIS
INTERFACE
AR
MR
PCLK
Fig 84. LPC2300 UART0, 2 and 3 block diagram

UM10211
Chapter 17: LPC23XX UART1

The UART1 peripheral is configured using the following registers:
1. Power: In the PCONP register (Table 56), set bits PCUART1.

Remark: On reset, UART1 is enabled (PCUART1 = 1).
2. Peripheral clock: In the PCLK_SEL0 register (Table 49), select PCLK_UART1.
3. Baud rate: In register U1LCR (Table 378), set bit DLAB =1. This enables access to
registers DLL (Table 372) and DLM (Table 373) for setting the baud rate. Also, if
needed, set the fractional baud rate in the fractional divider register (Table 385).
4. UART FIFO: Use bit FIFO enable (bit 0) in register U0FCR (Table 377) to enable
FIFO.
5. Pins: Select UART pins and pin modes in registers PINSELn and PINMODEn (see
Section 9.5).
Remark: UART receive pins should not have pull-down resistors enabled.
6. Interrupts: To enable UART interrupts set bit DLAB =0 in register U1LCR (Table 379).
This enables access to U1IER (Table 374). Interrupts are enabled in the VIC using the
VICIntEnable register (Table 76).
17.2 Features
• UART1 is identical to UART0/2/3, with the addition of a modem interface.
• 16 byte Receive and Transmit FIFOs.
• Register locations conform to ‘550 industry standard.
• Receiver FIFO trigger points at 1, 4, 8, and 14 bytes.
• Built-in baud rate generator.
• Standard modem interface signals included (CTS, DCD, DTS, DTR, RI, RTS).
• Either software or hardware flow control can be implemented.


Table 368. UART1 Pin Description
RXD1 Input Serial Input. Serial receive data.
TXD1 Output Serial Output. Serial transmit data.
CTS1 Input Clear To Send. Active low signal indicates if the external modem is ready to
accept transmitted data via TXD1 from the UART1. In normal operation of the
modem interface (U1MCR[4] = 0), the complement value of this signal is stored in
U1MSR[4]. State change information is stored in U1MSR[0] and is a source for a
priority level 4 interrupt, if enabled (U1IER[3] = 1).
Only CTS1 is also used in auto-cts mode to control the UART1 transmitter.
Clear to send. CTS1 is an asynchronous, active low modem status signal. Its
condition can be checked by reading bit 4 (CTS) of the modem status register. Bit
0 (DCTS) of the Modem Status Register (MSR) indicates that CTS1 has changed
states since the last read from the MSR. If the modem status interrupt is enabled
when CTS1 changes levels and the auto-cts mode is not enabled, an interrupt is
generated. CTS1 is also used in the auto-cts mode to control the transmitter.
(IP_3106)
DCD1 Input Data Carrier Detect. Active low signal indicates if the external modem has
established a communication link with the UART1 and data may be exchanged. In
normal operation of the modem interface (U1MCR[4]=0), the complement value of
this signal is stored in U1MSR[7]. State change information is stored in U1MSR3
and is a source for a priority level 4 interrupt, if enabled (U1IER[3] = 1).
DSR1 Input Data Set Ready. Active low signal indicates if the external modem is ready to
establish a communications link with the UART1. In normal operation of the
modem interface (U1MCR[4] = 0), the complement value of this signal is stored in
U1MSR[5]. State change information is stored in U1MSR[1] and is a source for a
priority level 4 interrupt, if enabled (U1IER[3] = 1).
DTR1 Output Data Terminal Ready. Active low signal indicates that the UART1 is ready to
establish connection with external modem. The complement value of this signal is
stored in U1MCR[0].
RI1 Input Ring Indicator. Active low signal indicates that a telephone ringing signal has
been detected by the modem. In normal operation of the modem interface
(U1MCR[4] = 0), the complement value of this signal is stored in U1MSR[6]. State
change information is stored in U1MSR[2] and is a source for a priority level 4
interrupt, if enabled (U1IER[3] = 1).
RTS1 Output Request To Send. Active low signal indicates that the UART1 would like to
transmit data to the external modem. The complement value of this signal is
stored in U1MCR[1].
Only in the auto-rts mode uses RTS1 to control the transmitter FIFO threshold
logic.
Request to send. RTS1 is an active low signal informing the modem or data set
that the UART is ready to receive data. RTS1 is set to the active (low) level by
setting the RTS modem control register bit and is set to the inactive (high) level
either as a result of a system reset or during loop-back mode operations or by
clearing bit 1 (RTS) of the MCR. In the auto-rts mode, RTS1 is controlled by the
transmitter FIFO threshold logic.


UART1 contains registers organized as shown in Table 369. The Divisor Latch Access Bit
(DLAB) is contained in U1LCR[7] and enables access to the Divisor Latches.

User manual
UM10211
NXP Semiconductors
Table 369. UART1 register map
Name Description Bit functions and addresses Access Reset Address
MSB LSB Value[1]
BIT7 BIT6 BIT5 BIT4 BIT3 BIT2 BIT1 BIT0

U1RBR Receiver 8 bit Read Data RO NA 0xE001 0000
Buffer (DLAB=0)
Register
U1THR Transmit 8 bit Write Data WO NA 0xE001 0000
Holding (DLAB=0)
Register
U1DLL Divisor Latch 8 bit Data R/W 0x01 0xE001 0000
LSB (DLAB=1)
U1DLM Divisor Latch 8 bit Data R/W 0x00 0xE001 0004
MSB (DLAB=1)
U1IER Interrupt Reserved Enable Enable R/W 0x00 0xE001 0004
Enable Autobaud End of (DLAB=0)

Register Time-Out Autobaud
Interrupt Interrupt
Enable 0 Enable Enable Enable Enable
CTS Modem RX Line THRE RX Data
Interrupt Status Status Interrupt Available
interrupt Interrupt Interrupt
U1IIR Interrupt ID Reserved ABTO Itn ABEO int RO 0x01 0xE001 0008
Register FIFOs Enabled 0 IIR3 IIR2 IIR1 IIR0
U1FCR FIFO Control RX Trigger Reserved TX FIFO RX FIFO FIFO WO 0x00 0xE001 0008
Register Reset Reset Enable
U1LCR Line Control DLAB Set Stick Even Parity Number Word Length Select R/W 0x00 0xE001 000C
Register Break Parity Parity Enable of Stop

Select Bits
U1MCR Modem CTSen RTSen 0 Loop 0 RTS DTR R/W 0x00 0xE001 0010
Control Back
Register
UM10211
U1LSR Line Status RX TEMT THRE BI FE PE OE DR RO 0x60 0xE001 0014

Register FIFO
Error
U1MSR Modem DCD RI DSR CTS Delta Trailing Delta Delta RO 0x00 0xE001 0018
436 of 708
Status DCD Edge RI DSR CTS

Register
Table 369. UART1 register map …continued
User manual
UM10211
NXP Semiconductors
Name Description Bit functions and addresses Access Reset Address
MSB LSB Value[1]
U1SCR Scratch Pad 8 bit Data R/W 0x00 0xE001 001C

Register
U1ACR Autobaud Reserved [31:10] ABTO ABEO R/W 0x00 0xE001 0020
Control IntClr IntClr
Register Reserved [7:3] Auto Mode Start
Reset
U1FDR Fractional Reserved [31:8] R/W 0x10 0xE001 0028
Divider Mulval DivAddVal
Register
U1TER Transmit TXEN Reserved R/W 0x80 0xE001 0030
Enable
Register

UM10211
437 of 708
17.4.1 UART1 Receiver Buffer Register (U1RBR - 0xE001 0000, when

DLAB = 0 Read Only)
The U1RBR is the top byte of the UART1 RX FIFO. The top byte of the RX FIFO contains
the oldest character received and can be read via the bus interface. The LSB (bit 0)
represents the “oldest” received data bit. If the character received is less than 8 bits, the
unused MSBs are padded with zeroes.
The Divisor Latch Access Bit (DLAB) in U1LCR must be zero in order to access the
U1RBR. The U1RBR is always Read Only.
Since PE, FE and BI bits correspond to the byte sitting on the top of the RBR FIFO (i.e.
the one that will be read in the next read from the RBR), the right approach for fetching the
valid pair of received byte and its status bits is first to read the content of the U1LSR
register, and then to read a byte from the U1RBR.
Table 370. UART1 Receiver Buffer Register (U1RBR - address 0xE001 0000 when DLAB = 0,
Read Only) bit description
7:0 RBR The UART1 Receiver Buffer Register contains the oldest undefined
received byte in the UART1 RX FIFO.
17.4.2 UART1 Transmitter Holding Register (U1THR - 0xE001 0000 when

DLAB = 0, Write Only)
The U1THR is the top byte of the UART1 TX FIFO. The top byte is the newest character in
the TX FIFO and can be written via the bus interface. The LSB represents the first bit to
transmit.
The Divisor Latch Access Bit (DLAB) in U1LCR must be zero in order to access the
U1THR. The U1THR is always Write Only.
Table 371. UART1 Transmitter Holding Register (U1THR - address 0xE001 0000 when
DLAB = 0, Write Only) bit description
7:0 THR Writing to the UART1 Transmit Holding Register causes the data NA
to be stored in the UART1 transmit FIFO. The byte will be sent
when it reaches the bottom of the FIFO and the transmitter is
available.
17.4.3 UART1 Divisor Latch LSB and MSB Registers (U1DLL - 0xE001 0000
and U1DLM - 0xE001 0004, when DLAB = 1)
The UART1 Divisor Latch is part of the UART1 Baud Rate Generator and holds the value
used to divide the APB clock (PCLK) in order to produce the baud rate clock, which must
be 16x the desired baud rate (Equation 10). The U1DLL and U1DLM registers together
form a 16 bit divisor where U1DLL contains the lower 8 bits of the divisor and U1DLM
contains the higher 8 bits of the divisor. A 0x0000 value is treated like a 0x0001 value as
division by zero is not allowed.The Divisor Latch Access Bit (DLAB) in U1LCR must be
one in order to access the UART1 Divisor Latches. Details on how to select the right value
for U1DLL and U1DLM can be found in Section 17.4.17.

(10)
pclk
UART1 baudrate = --------------------------------------------------------------------------------
16   256  U1DLM + U1DLL 
Table 372. UART1 Divisor Latch LSB Register (U1DLL - address 0xE001 0000 when
DLAB = 1) bit description
7:0 DLLSB The UART1 Divisor Latch LSB Register, along with the U1DLM 0x01
register, determines the baud rate of the UART1.
Table 373. UART1 Divisor Latch MSB Register (U1DLM - address 0xE001 0004 when
DLAB = 1) bit description
7:0 DLMSB The UART1 Divisor Latch MSB Register, along with the U1DLL 0x00
register, determines the baud rate of the UART1.
17.4.4 UART1 Interrupt Enable Register (U1IER - 0xE001 0004, when

DLAB = 0)
The U1IER is used to enable the four UART1 interrupt sources.
Table 374. UART1 Interrupt Enable Register (U1IER - address 0xE001 0004 when DLAB = 0)
bit description
Value
0 RBR U1IER[0] enables the Receive Data Available interrupt for 0
Interrupt UART1. It also controls the Character Receive Time-out
Enable interrupt.
0 Disable the RDA interrupts.
1 Enable the RDA interrupts.
1 THRE U1IER[1] enables the THRE interrupt for UART1. The 0
Interrupt status of this interrupt can be read from U1LSR[5].
Enable 0 Disable the THRE interrupts.
1 Enable the THRE interrupts.
2 RX Line U1IER[2] enables the UART1 RX line status interrupts. 0
Interrupt The status of this interrupt can be read from U1LSR[4:1].
Enable 0 Disable the RX line status interrupts.
1 Enable the RX line status interrupts.
3 Modem U1IER[3] enables the modem interrupt. The status of this 0
Status interrupt can be read from U1MSR[3:0].
Interrupt 0 Disable the modem interrupt.
Enable
1 Enable the modem interrupt.

Table 374. UART1 Interrupt Enable Register (U1IER - address 0xE001 0004 when DLAB = 0)
bit description
Value
7 CTS If auto-cts mode is enabled this bit enables/disables the 0
Interrupt modem status interrupt generation on a CTS1 signal
Enable transition. If auto-cts mode is disabled a CTS1 transition
will generate an interrupt if Modem Status Interrupt Enable
(U1IER[3]) is set.
In normal operation a CTS1 signal transition will generate
a Modem Status Interrupt unless the interrupt has been
disabled by clearing the U1IER[3] bit in the U1IER register.
In auto-cts mode a transition on the CTS1 bit will trigger an
interrupt only if both the U1IER[3] and U1IER[7] bits are
set.
0 Disable the CTS interrupt.
1 Enable the CTS interrupt.
8 ABEOIntEn enables the end of auto-baud interrupt. 0
0 Disable End of Auto-baud Interrupt.
1 Enable End of Auto-baud Interrupt.
9 ABTOIntEn enables the auto-baud time-out interrupt. 0
0 Disable Auto-baud Time-out Interrupt.
1 Enable Auto-baud Time-out Interrupt.
17.4.5 UART1 Interrupt Identification Register (U1IIR - 0xE001 0008, Read

Only)
The U1IIR provides a status code that denotes the priority and source of a pending
interrupt. The interrupts are frozen during an U1IIR access. If an interrupt occurs during
an U1IIR access, the interrupt is recorded for the next U1IIR access.
Table 375. UART1 Interrupt Identification Register (U1IIR - address 0xE001 0008, Read Only)
bit description
Value
0 IntStatus Interrupt status. Note that U1IIR[0] is active low. The 1
pending interrupt can be determined by evaluating
U1IIR[3:1].
0 At least one interrupt is pending.
1 No interrupt is pending.

Table 375. UART1 Interrupt Identification Register (U1IIR - address 0xE001 0008, Read Only)
bit description
Value
3:1 IntId Interrupt identification. U1IER[3:1] identifies an interrupt 0
corresponding to the UART1 Rx FIFO. All other
combinations of U1IER[3:1] not listed above are reserved
(100,101,111).
011 1 - Receive Line Status (RLS).
010 2a - Receive Data Available (RDA).
110 2b - Character Time-out Indicator (CTI).
001 3 - THRE Interrupt.
000 4 - Modem Interrupt.
7:6 FIFO Enable These bits are equivalent to U1FCR[0]. 0
8 ABEOInt End of auto-baud interrupt. True if auto-baud has finished 0
successfully and interrupt is enabled.
9 ABTOInt Auto-baud time-out interrupt. True if auto-baud has timed 0
out and interrupt is enabled.
Bit U1IIR[9:8] are set by the auto-baud function and signal a time-out or end of auto-baud
condition. The auto-baud interrupt conditions are cleared by setting the corresponding
Clear bits in the Auto-baud Control Register.
If the IntStatus bit is 1 no interrupt is pending and the IntId bits will be zero. If the IntStatus
is 0, a non auto-baud interrupt is pending in which case the IntId bits identify the type of
interrupt and handling as described in Table 376. Given the status of U1IIR[3:0], an
interrupt handler routine can determine the cause of the interrupt and how to clear the
active interrupt. The U1IIR must be read in order to clear the interrupt prior to exiting the
Interrupt Service Routine.
The UART1 RLS interrupt (U1IIR[3:1] = 011) is the highest priority interrupt and is set
whenever any one of four error conditions occur on the UART1RX input: overrun error
(OE), parity error (PE), framing error (FE) and break interrupt (BI). The UART1 Rx error
condition that set the interrupt can be observed via U1LSR[4:1]. The interrupt is cleared
upon an U1LSR read.
The UART1 RDA interrupt (U1IIR[3:1] = 010) shares the second level priority with the CTI
interrupt (U1IIR[3:1] = 110). The RDA is activated when the UART1 Rx FIFO reaches the
trigger level defined in U1FCR7:6 and is reset when the UART1 Rx FIFO depth falls below
the trigger level. When the RDA interrupt goes active, the CPU can read a block of data
defined by the trigger level.
The CTI interrupt (U1IIR[3:1] = 110) is a second level interrupt and is set when the UART1
Rx FIFO contains at least one character and no UART1 Rx FIFO activity has occurred in
3.5 to 4.5 character times. Any UART1 Rx FIFO activity (read or write of UART1 RSR) will
clear the interrupt. This interrupt is intended to flush the UART1 RBR after a message has
been received that is not a multiple of the trigger level size. For example, if a peripheral

wished to send a 105 character message and the trigger level was 10 characters, the
CPU would receive 10 RDA interrupts resulting in the transfer of 100 characters and 1 to 5
CTI interrupts (depending on the service routine) resulting in the transfer of the remaining
5 characters.
Table 376. UART1 Interrupt Handling

U1IIR[3:0] Priority Interrupt Interrupt Source Interrupt
value[1] Type Reset
0001 - None None -
0110 Highest RX Line OE[2] or PE[2] or FE[2] or BI[2] U1LSR
Status / Read[2]
Error
0100 Second RX Data Rx data available or trigger level reached in FIFO U1RBR
Available (U1FCR0=1) Read[3] or
UART1
FIFO drops
below
trigger level
1100 Second Character Minimum of one character in the RX FIFO and no U1RBR
Time-out character input or removed during a time period Read[3]
indication depending on how many characters are in FIFO
and what the trigger level is set at (3.5 to 4.5
character times).
The exact time will be:
[(word length)  7 - 2]  8 + [(trigger level - number
of characters)  8 + 1] RCLKs
0010 Third THRE THRE[2] U1IIR
Read[4] (if
source of
interrupt) or
THR write
0000 Fourth Modem CTS or DSR or RI or DCD MSR Read
Status
[1] Values "0000", “0011”, “0101”, “0111”, “1000”, “1001”, “1010”, “1011”,”1101”,”1110”,”1111” are reserved.
[2] For details see Section 17.4.11 “UART1 Line Status Register (U1LSR - 0xE001 0014, Read Only)”
[3] For details see Section 17.4.1 “UART1 Receiver Buffer Register (U1RBR - 0xE001 0000, when DLAB = 0
Read Only)”
[4] For details see Section 17.4.5 “UART1 Interrupt Identification Register (U1IIR - 0xE001 0008, Read Only)”
and Section 17.4.2 “UART1 Transmitter Holding Register (U1THR - 0xE001 0000 when DLAB = 0, Write
Only)”
The UART1 THRE interrupt (U1IIR[3:1] = 001) is a third level interrupt and is activated
when the UART1 THR FIFO is empty provided certain initialization conditions have been
met. These initialization conditions are intended to give the UART1 THR FIFO a chance to
fill up with data to eliminate many THRE interrupts from occurring at system start-up. The
initialization conditions implement a one character delay minus the stop bit whenever
THRE = 1 and there have not been at least two characters in the U1THR at one time
since the last THRE = 1 event. This delay is provided to give the CPU time to write data to
U1THR without a THRE interrupt to decode and service. A THRE interrupt is set
immediately if the UART1 THR FIFO has held two or more characters at one time and
currently, the U1THR is empty. The THRE interrupt is reset when a U1THR write occurs or
a read of the U1IIR occurs and the THRE is the highest interrupt (U1IIR[3:1] = 001).

It is the lowest priority interrupt and is activated whenever there is any state change on
modem inputs pins, DCD, DSR or CTS. In addition, a low to high transition on modem
input RI will generate a modem interrupt. The source of the modem interrupt can be
determined by examining U1MSR[3:0]. A U1MSR read will clear the modem interrupt.
17.4.6 UART1 FIFO Control Register (U1FCR - 0xE001 0008, Write Only)
The U1FCR controls the operation of the UART1 RX and TX FIFOs.
Table 377. UART1 FIFO Control Register (U1FCR - address 0xE001 0008, Write Only) bit
description
Value
0 FIFO 0 UART1 FIFOs are disabled. Must not be used in the application. 0
Enable 1 Active high enable for both UART1 Rx and TX FIFOs and
U1FCR[7:1] access. This bit must be set for proper UART1
operation. Any transition on this bit will automatically clear the
UART1 FIFOs.
1 RX FIFO 0 No impact on either of UART1 FIFOs. 0
Reset 1 Writing a logic 1 to U1FCR[1] will clear all bytes in UART1 Rx
FIFO and reset the pointer logic. This bit is self-clearing.
2 TX FIFO 0 No impact on either of UART1 FIFOs. 0
Reset 1 Writing a logic 1 to U1FCR[2] will clear all bytes in UART1 TX
FIFO and reset the pointer logic. This bit is self-clearing.
7:6 RX These two bits determine how many receiver UART1 FIFO 0
Trigger characters must be written before an interrupt is activated.
Level 00 Trigger level 0 (1 character or 0x01).
01 Trigger level 1 (4 characters or 0x04).
10 Trigger level 2 (8 characters or 0x08).
11 Trigger level 3 (14 characters or 0x0E).
17.4.7 UART1 Line Control Register (U1LCR - 0xE001 000C)

The U1LCR determines the format of the data character that is to be transmitted or
received.
Table 378. UART1 Line Control Register (U1LCR - address 0xE001 000C) bit description
Value
1:0 Word 00 5 bit character length. 0
Length 01 6 bit character length.
Select
10 7 bit character length.
11 8 bit character length.
2 Stop Bit 0 1 stop bit. 0
Select 1 2 stop bits (1.5 if U1LCR[1:0]=00).
3 Parity 0 Disable parity generation and checking. 0
Enable 1 Enable parity generation and checking.

Table 378. UART1 Line Control Register (U1LCR - address 0xE001 000C) bit description
Value
5:4 Parity 00 Odd parity. Number of 1s in the transmitted character and the 0
Select attached parity bit will be odd.
01 Even Parity. Number of 1s in the transmitted character and the
attached parity bit will be even.
6 Break 0 Disable break transmission. 0
Control 1 Enable break transmission. Output pin UART1 TXD is forced to
logic 0 when U1LCR[6] is active high.
7 Divisor 0 Disable access to Divisor Latches. 0
Latch 1 Enable access to Divisor Latches.
Access
Bit
(DLAB)
17.4.8 UART1 Modem Control Register (U1MCR - 0xE001 0010)

The U1MCR enables the modem loopback mode and controls the modem output signals.
Table 379. UART1 Modem Control Register (U1MCR - address 0xE001 0010) bit description
value
0 DTR Source for modem output pin, DTR. This bit reads as 0 when 0
Control modem loopback mode is active.
1 RTS Source for modem output pin RTS. This bit reads as 0 when 0
Control modem loopback mode is active.
3-2 - NA Reserved, user software should not write ones to reserved bits. 0
4 Loopback The modem loopback mode provides a mechanism to perform 0
Mode diagnostic loopback testing. Serial data from the transmitter is
Select connected internally to serial input of the receiver. Input pin,
RXD1, has no effect on loopback and output pin, TXD1 is held in
marking state. The four modem inputs (CTS, DSR, RI and DCD)
are disconnected externally. Externally, the modem outputs (RTS,
DTR) are set inactive. Internally, the four modem outputs are
connected to the four modem inputs. As a result of these
connections, the upper four bits of the U1MSR will be driven by
the lower four bits of the U1MCR rather than the four modem
inputs in normal mode. This permits modem status interrupts to
be generated in loopback mode by writing the lower four bits of
U1MCR.
0 Disable modem loopback mode.
1 Enable modem loopback mode.
5 - NA Reserved, user software should not write ones to reserved bits. 0

Table 379. UART1 Modem Control Register (U1MCR - address 0xE001 0010) bit description
value
6 RTSen 0 Disable auto-rts flow control. 0
1 Enable auto-rts flow control.
7 CTSen 0 Disable auto-cts flow control. 0
1 Enable auto-cts flow control.
17.4.9 Auto-Flow control

If auto-RTS mode is enabled the UART1‘s receiver FIFO hardware controls the RTS1
output of the UART1. If the auto-cts mode is enabled the UART1‘s U1TSR hardware will
only start transmitting if the CTS1 input signal is asserted.
17.4.9.1 Auto-RTS
The Auto-RTS function is enabled by setting the RTSen bit. Auto-RTS data flow control
originates in the U1RBR module and is linked to the programmed receiver FIFO trigger
level. If auto-RTS is enabled, the data-flow is controlled as follows:
When the receiver FIFO level reaches the programmed trigger level, RTS1 is deasserted
(to a high value). The sending UART can send an additional byte after the trigger level is
reached (assuming the sending UART has another byte to send) because it might not
recognize the deassertion of RTS1 until after it has begun sending the additional byte.
RTS1 is automatically reasserted (to a low value) once the receiver FIFO has reached the
previous trigger level. The reassertion of RTS1 signals the sending UART to continue
transmitting data.
If Auto-RTS mode is disabled, the RTS Control bit controls the RTS1 output of the
UART1. If Auto-RTS mode is enabled, hardware controls the RTS1 output, and the actual
value of RTS1 will be copied in the RTS Control bit of the UART1. As long as Auto-RTS is
enabled, the value of the RTS Control bit is read-only for software.
Example: Suppose the UART1 operating in type 550 has trigger level in U1FCR set to 0x2
then if Auto-RTS is enabled the UART1 will deassert the RTS1 output as soon as the
receive FIFO contains 8 bytes (Table 377 on page 443). The RTS1 output will be
reasserted as soon as the receive FIFO hits the previous trigger level: 4 bytes.
UART1 Rx
~
~
start byte N stop start bits0..7 stop start bits0..7 stop

~
~
RTS1 pin
UART1 Rx
FIFO read
~~
~ ~
UART1 Rx N-1 N N-1 N-2 N-1 N-2 M+2 M+1 M M-1

FIFO level
~
~
Fig 85. Auto-RTS functional timing

17.4.10 Auto-CTS
The Auto-CTS function is enabled by setting the CTSen bit. If Auto-CTS is enabled, the
transmitter circuitry in the U1TSR module checks CTS1 input before sending the next
data byte. When CTS1 is active (low), the transmitter sends the next byte. To stop the
transmitter from sending the following byte, CTS1 must be released before the middle of
the last stop bit that is currently being sent. In Auto-CTS mode a change of the CTS1
signal does not trigger a modem status interrupt unless the CTS Interrupt Enable bit is set,
Delta CTS bit in the U1MSR will be set though. Table 380 lists the conditions for
generating a Modem Status interrupt.
Table 380. Modem status interrupt generation

Enable CTSen CTS Delta CTS Delta DCD or Trailing Edge Modem
Modem (U1MCR[7]) Interrupt (U1MSR[0]) RI or Status
Status Enable Delta DSR (U1MSR[3] or Interrupt
Interrupt (U1IER[7]) U1MSR[2] or U1MSR[1])
(U1ER[3]
)
0 x x x x No
1 0 x 0 0 No
1 0 x 1 x Yes
1 0 x x 1 Yes
1 1 0 x 0 No
1 1 0 x 1 Yes
1 1 1 0 0 No
1 1 1 1 x Yes
1 1 1 x 1 Yes
The auto-CTS function reduces interrupts to the host system. When flow control is
enabled, a CTS1 state change does not trigger host interrupts because the device
automatically controls its own transmitter. Without Auto-CTS, the transmitter sends any
data present in the transmit FIFO and a receiver overrun error can result. Figure 86
illustrates the Auto-CTS functional timing.
UART1 TX
~
~
~
~
start bits0..7 stop start bits0..7 stop start bits0..7 stop

~
~
CTS1 pin
~
~
Fig 86. Auto-CTS functional timing
While starting transmission of the initial character the CTS1 signal is asserted.
Transmission will stall as soon as the pending transmission has completed. The UART will
continue transmitting a 1 bit as long as CTS1 is deasserted (high). As soon as CTS1 gets
deasserted transmission resumes and a start bit is sent followed by the data bits of the
next character.

17.4.11 UART1 Line Status Register (U1LSR - 0xE001 0014, Read Only)
The U1LSR is a read-only register that provides status information on the UART1 TX and
RX blocks.
Table 381. UART1 Line Status Register (U1LSR - address 0xE001 0014, Read Only) bit
description
Value
0 Receiver U1LSR[0] is set when the U1RBR holds an unread character and 0
Data is cleared when the UART1 RBR FIFO is empty.
Ready 0 U1RBR is empty.
(RDR)
1 U1RBR contains valid data.
1 Overrun The overrun error condition is set as soon as it occurs. An U1LSR 0
Error read clears U1LSR[1]. U1LSR[1] is set when UART1 RSR has a
(OE) new character assembled and the UART1 RBR FIFO is full. In
this case, the UART1 RBR FIFO will not be overwritten and the
character in the UART1 RSR will be lost.
0 Overrun error status is inactive.
1 Overrun error status is active.
2 Parity When the parity bit of a received character is in the wrong state, a 0
Error parity error occurs. An U1LSR read clears U1LSR[2]. Time of
(PE) parity error detection is dependent on U1FCR[0].
Note: A parity error is associated with the character at the top of
the UART1 RBR FIFO.
0 Parity error status is inactive.
1 Parity error status is active.
3 Framing When the stop bit of a received character is a logic 0, a framing 0
Error error occurs. An U1LSR read clears U1LSR[3]. The time of the
(FE) framing error detection is dependent on U1FCR0. Upon detection
of a framing error, the RX will attempt to resynchronize to the data
and assume that the bad stop bit is actually an early start bit.
However, it cannot be assumed that the next received byte will be
correct even if there is no Framing Error.
Note: A framing error is associated with the character at the top
of the UART1 RBR FIFO.
0 Framing error status is inactive.
1 Framing error status is active.
4 Break When RXD1 is held in the spacing state (all 0’s) for one full 0
Interrupt character transmission (start, data, parity, stop), a break interrupt
(BI) occurs. Once the break condition has been detected, the receiver
goes idle until RXD1 goes to marking state (all 1’s). An U1LSR
read clears this status bit. The time of break detection is
dependent on U1FCR[0].
Note: The break interrupt is associated with the character at the
top of the UART1 RBR FIFO.
0 Break interrupt status is inactive.
1 Break interrupt status is active.

Table 381. UART1 Line Status Register (U1LSR - address 0xE001 0014, Read Only) bit
description
Value
5 Transmitte THRE is set immediately upon detection of an empty UART1 1
r Holding THR and is cleared on a U1THR write.
Register 0 U1THR contains valid data.
Empty
(THRE) 1 U1THR is empty.
6 Transmitte TEMT is set when both U1THR and U1TSR are empty; TEMT is 1
r Empty cleared when either the U1TSR or the U1THR contain valid data.
(TEMT) 0 U1THR and/or the U1TSR contains valid data.
1 U1THR and the U1TSR are empty.
7 Error in RX U1LSR[7] is set when a character with a RX error such as framing 0
FIFO error, parity error or break interrupt, is loaded into the U1RBR.
(RXFE) This bit is cleared when the U1LSR register is read and there are
no subsequent errors in the UART1 FIFO.
0 U1RBR contains no UART1 RX errors or U1FCR[0]=0.
1 UART1 RBR contains at least one UART1 RX error.
17.4.12 UART1 Modem Status Register (U1MSR - 0xE001 0018)

The U1MSR is a read-only register that provides status information on the modem input
signals. U1MSR[3:0] is cleared on U1MSR read. Note that modem signals have no direct
affect on UART1 operation, they facilitate software implementation of modem signal
operations.
Table 382. UART1 Modem Status Register (U1MSR - address 0xE001 0018) bit description
Value
0 Delta Set upon state change of input CTS. Cleared on an U1MSR read. 0
CTS 0 No change detected on modem input, CTS.
1 State change detected on modem input, CTS.
1 Delta Set upon state change of input DSR. Cleared on an U1MSR read. 0
DSR 0 No change detected on modem input, DSR.
1 State change detected on modem input, DSR.
2 Trailing Set upon low to high transition of input RI. Cleared on an U1MSR 0
Edge RI read.
0 No change detected on modem input, RI.
1 Low-to-high transition detected on RI.
3 Delta Set upon state change of input DCD. Cleared on an U1MSR read. 0
DCD 0 No change detected on modem input, DCD.
1 State change detected on modem input, DCD.
4 CTS Clear To Send State. Complement of input signal CTS. This bit is 0
connected to U1MCR[1] in modem loopback mode.

Table 382. UART1 Modem Status Register (U1MSR - address 0xE001 0018) bit description
Value
5 DSR Data Set Ready State. Complement of input signal DSR. This bit is 0
6 RI Ring Indicator State. Complement of input RI. This bit is connected 0
to U1MCR[2] in modem loopback mode.
7 DCD Data Carrier Detect State. Complement of input DCD. This bit is 0
17.4.13 UART1 Scratch Pad Register (U1SCR - 0xE001 001C)

The U1SCR has no effect on the UART1 operation. This register can be written and/or
read at user’s discretion. There is no provision in the interrupt interface that would indicate
to the host that a read or write of the U1SCR has occurred.
Table 383. UART1 Scratch Pad Register (U1SCR - address 0xE001 0014) bit description
7:0 Pad A readable, writable byte. 0x00
17.4.14 UART1 Auto-baud Control Register (U1ACR - 0xE001 0020)

The UART1 Auto-baud Control Register (U1ACR) controls the process of measuring the
incoming clock/data rate for the baud rate generation and can be read and written at
user’s discretion.
Table 384. Auto-baud Control Register (U1ACR - address 0xE001 0020) bit description
0 Start This bit is automatically cleared after auto-baud 0
completion.
0 Auto-baud stop (auto-baud is not running).
1 Auto-baud start (auto-baud is running).Auto-baud run
bit. This bit is automatically cleared after auto-baud
completion.
1 Mode Auto-baud mode select bit. 0
0 Mode 0.
1 Mode 1.
2 AutoRestart 0 No restart 0
1 Restart in case of time-out (counter restarts at next 0
UART1 Rx falling edge)
defined.
8 ABEOIntClr End of auto-baud interrupt clear bit (write only 0
accessible).
0 Writing a 0 has no impact.
1 Writing a 1 will clear the corresponding interrupt in the
U1IIR.

Table 384. Auto-baud Control Register (U1ACR - address 0xE001 0020) bit description
9 ABTOIntClr Auto-baud time-out interrupt clear bit (write only 0
accessible).
0 Writing a 0 has no impact.
1 Writing a 1 will clear the corresponding interrupt in the
U1IIR.
defined.
17.4.15 Auto-baud
The UART1 auto-baud function can be used to measure the incoming baud-rate based on
the ”AT" protocol (Hayes command). If enabled the auto-baud feature will measure the bit
time of the receive data stream and set the divisor latch registers U1DLM and U1DLL
accordingly.
Auto-baud is started by setting the U1ACR Start bit. Auto-baud can be stopped by clearing
the U1ACR Start bit. The Start bit will clear once auto-baud has finished and reading the
bit will return the status of auto-baud (pending/finished).
Two auto-baud measuring modes are available which can be selected by the U1ACR
Mode bit. In mode 0 the baud-rate is measured on two subsequent falling edges of the
UART1 Rx pin (the falling edge of the start bit and the falling edge of the least significant
bit). In mode 1 the baud-rate is measured between the falling edge and the subsequent
rising edge of the UART1 Rx pin (the length of the start bit).
The U1ACR AutoRestart bit can be used to automatically restart baud-rate measurement
if a time-out occurs (the rate measurement counter overflows). If this bit is set the rate
measurement will restart at the next falling edge of the UART1 Rx pin.
The auto-baud function can generate two interrupts.
• The U1IIR ABTOInt interrupt will get set if the interrupt is enabled (U1IER ABToIntEn
is set and the auto-baud rate measurement counter overflows).
• The U1IIR ABEOInt interrupt will get set if the interrupt is enabled (U1IER ABEOIntEn
is set and the auto-baud has completed successfully).
The auto-baud interrupts have to be cleared by setting the corresponding U1ACR

ABTOIntClr and ABEOIntEn bits.
The fractional baud-rate generator is disabled (DIVADDVAL = 0) during auto-baud. When

auto-baud is used, any write to U1DLM and U1DLL registers should be done before
U1ACR register write. The minimum and the maximum baudrates supported by UART1
are function of pclk, number of data bits, stop bits and parity bits.
(11)

2  P CLK PCLK
ratemin = -------------------------  UART 1 baudrate  ------------------------------------------------------------------------------------------------------------ = ratemax
16  2 15 16   2 + databits + paritybits + stopbits 
17.4.16 Auto-baud modes

When the software is expecting an ”AT" command, it configures the UART1 with the
expected character format and sets the U1ACR Start bit. The initial values in the divisor
latches U1DLM and U1DLM don‘t care. Because of the ”A" or ”a" ASCII coding
(”A" = 0x41, ”a" = 0x61), the UART1 Rx pin sensed start bit and the LSB of the expected
character are delimited by two falling edges. When the U1ACR Start bit is set, the
auto-baud protocol will execute the following phases:
1. On U1ACR Start bit setting, the baud-rate measurement counter is reset and the
UART1 U1RSR is reset. The U1RSR baud rate is switch to the highest rate.
2. A falling edge on UART1 Rx pin triggers the beginning of the start bit. The rate
measuring counter will start counting pclk cycles.
3. During the receipt of the start bit, 16 pulses are generated on the RSR baud input with
the frequency of the UART1 input clock, guaranteeing the start bit is stored in the
U1RSR.
4. During the receipt of the start bit (and the character LSB for mode = 0) the rate
counter will continue incrementing with the pre-scaled UART1 input clock (pclk).
5. If Mode = 0 then the rate counter will stop on next falling edge of the UART1 Rx pin. If
Mode = 1 then the rate counter will stop on the next rising edge of the UART1 Rx pin.
6. The rate counter is loaded into U1DLM/U1DLL and the baud-rate will be switched to
normal operation. After setting the U1DLM/U1DLL the end of auto-baud interrupt
U1IIR ABEOInt will be set, if enabled. The U1RSR will now continue receiving the
remaining bits of the ”A/a" character.

'A' (0x41) or 'a' (0x61)
UARTn RX
U0ACR start
rate counter
16xbaud_rate
16 cycles 16 cycles
a. Mode 0 (start bit and LSB are used for auto-baud)
'A' (0x41) or 'a' (0x61)
UARTn RX
U1ACR start
rate counter
16xbaud_rate
16 cycles
b. Mode 1 (only start bit is used for auto-baud)

Fig 87. Auto-baud a) mode 0 and b) mode 1 waveform
17.4.17 UART1 Fractional Divider Register (U1FDR - 0xE001 0028)

The UART1 Fractional Divider Register (U1FDR) controls the clock pre-scaler for the
baud rate generation and can be read and written at the user’s discretion. This pre-scaler
takes the APB clock and generates an output clock according to the specified fractional
requirements.
Important: If the fractional divider is active (DIVADDVAL > 0) and DLM = 0, the value of
the DLL register must be 3 or greater.

Table 385. UART1 Fractional Divider Register (U1FDR - address 0xE001 0028) bit description
Bit Function Value Description Reset
value
3:0 DIVADDVAL 0 Baud-rate generation pre-scaler divisor value. If this field is 0
0, fractional baud-rate generator will not impact the UARTn
baudrate.
7:4 MULVAL 1 Baud-rate pre-scaler multiplier value. This field must be 1
greater or equal 1 for UARTn to operate properly,
regardless of whether the fractional baud-rate generator is
used or not.
31:8 - NA Reserved, user software should not write ones to reserved 0
This register controls the clock pre-scaler for the baud rate generation. The reset value of
the register keeps the fractional capabilities of UART1 disabled making sure that UART1
is fully software and hardware compatible with UARTs not equipped with this feature.
UART1 baudrate can be calculated as (n = 1):
(12)
PCLK
UART1 baudrate = ----------------------------------------------------------------------------------------------------------------------------------
16   256  U1DLM + U1DLL    1 + -----------------------------
DivAddVal
 MulVal 
Where PCLK is the peripheral clock, U1DLM and U1DLL are the standard UART1 baud
rate divider registers, and DIVADDVAL and MULVAL are UART1 fractional baudrate
generator specific parameters.
The value of MULVAL and DIVADDVAL should comply to the following conditions:
1. 1  MULVAL  15
2. 0  DIVADDVAL  14
3. DIVADDVAL< MULVAL
The value of the U1FDR should not be modified while transmitting/receiving data or data
may be lost or corrupted.
If the U1FDR register value does not comply to these two requests, then the fractional
divider output is undefined. If DIVADDVAL is zero then the fractional divider is disabled,
and the clock will not be divided.
17.4.17.1 Baudrate calculation

UART can operate with or without using the Fractional Divider. In real-life applications it is
likely that the desired baudrate can be achieved using several different Fractional Divider
settings. The following algorithm illustrates one way of finding a set of DLM, DLL,
MULVAL, and DIVADDVAL values. Such set of parameters yields a baudrate with a
relative error of less than 1.1% from the desired one.

Calculating UART
baudrate (BR)
PCLK,
BR
DL est = PCLK/(16 x BR)
DL est is an True
integer?
False DIVADDVAL = 0
MULVAL = 1
FR est = 1.5
Pick another FR est from

the range [1.1, 1.9] DL est = Int(PCLK/(16 x BR x FR est))
FR est = PCLK/(16 x BR x DL est)
False
1.1 < FR est < 1.9?
True
DIVADDVAL = table(FR est )

MULVAL = table(FR est )
DLM = DL est[15:8]
DLL = DL est [7:0]
End
Fig 88. Algorithm for setting UART dividers

Table 386. Fractional Divider setting look-up table

FR DivAddVal/ FR DivAddVal/ FR DivAddVal/ FR DivAddVal/
MulVal MulVal MulVal MulVal
1.000 0/1 1.250 1/4 1.500 1/2 1.750 3/4
1.067 1/15 1.267 4/15 1.533 8/15 1.769 10/13
1.071 1/14 1.273 3/11 1.538 7/13 1.778 7/9
1.077 1/13 1.286 2/7 1.545 6/11 1.786 11/14
1.083 1/12 1.300 3/10 1.556 5/9 1.800 4/5
1.091 1/11 1.308 4/13 1.571 4/7 1.818 9/11
1.100 1/10 1.333 1/3 1.583 7/12 1.833 5/6
1.111 1/9 1.357 5/14 1.600 3/5 1.846 11/13
1.125 1/8 1.364 4/11 1.615 8/13 1.857 6/7
1.133 2/15 1.375 3/8 1.625 5/8 1.867 13/15
1.143 1/7 1.385 5/13 1.636 7/11 1.875 7/8
1.154 2/13 1.400 2/5 1.643 9/14 1.889 8/9
1.167 1/6 1.417 5/12 1.667 2/3 1.900 9/10
1.182 2/11 1.429 3/7 1.692 9/13 1.909 10/11
1.200 1/5 1.444 4/9 1.700 7/10 1.917 11/12
1.214 3/14 1.455 5/11 1.714 5/7 1.923 12/13
1.222 2/9 1.462 6/13 1.727 8/11 1.929 13/14
1.231 3/13 1.467 7/15 1.733 11/15 1.933 14/15
17.4.17.1.1 Example 1: PCLK = 14.7456 MHz, BR = 9600

According to the provided algorithm DLest = PCLK/(16 x BR) = 14.7456 MHz / (16 x 9600)
= 96. Since this DLest is an integer number, DIVADDVAL = 0, MULVAL = 1, DLM = 0, and
DLL = 96.
17.4.17.1.2 Example 2: PCLK = 12 MHz, BR = 115200

According to the provided algorithm DLest = PCLK/(16 x BR) = 12 MHz / (16 x 115200) =
6.51. This DLest is not an integer number and the next step is to estimate the FR
parameter. Using an initial estimate of FRest = 1.5 a new DLest = 4 is calculated and FRest
is recalculated as FRest = 1.628. Since FRest = 1.628 is within the specified range of 1.1
and 1.9, DIVADDVAL and MULVAL values can be obtained from the attached look-up
table.
The closest value for FRest = 1.628 in the look-up Table 386 is FR = 1.625. It is
equivalent to DIVADDVAL = 5 and MULVAL = 8.
Based on these findings, the suggested UART setup would be: DLM = 0, DLL = 4,
DIVADDVAL = 5, and MULVAL = 8. According to Equation 12 UART’s is 115384. This rate
has a relative error of 0.16% from the originally specified 115200.
17.4.18 UART1 Transmit Enable Register (U1TER - 0xE001 0030)

In addition to being equipped with full hardware flow control (auto-cts and auto-rts
mechanisms described above), U1TER enables implementation of software flow control,
too. When TxEn=1, UART1 transmitter will keep sending data as long as they are
available. As soon as TxEn becomes 0, UART1 transmission will stop.

Although Table 387 describes how to use TxEn bit in order to achieve hardware flow
control, it is strongly suggested to let UART1 hardware implemented auto flow control
features take care of this, and limit the scope of TxEn to software flow control.
LPC2300’s U1TER enables implementation of software and hardware flow control. When
TXEn=1, UART1 transmitter will keep sending data as long as they are available. As soon
as TXEn becomes 0, UART1 transmission will stop.
Table 387 describes how to use TXEn bit in order to achieve software flow control.
Table 387. UART1 Transmit Enable Register (U1TER - address 0xE001 0030) bit description
7 TXEN When this bit is 1, as it is after a Reset, data written to the THR 1
is output on the TXD pin as soon as any preceding data has
been sent. If this bit cleared to 0 while a character is being sent,
the transmission of that character is completed, but no further
characters are sent until this bit is set again. In other words, a 0
in this bit blocks the transfer of characters from the THR or TX
FIFO into the transmit shift register. Software can clear this bit
when it detects that the a hardware-handshaking TX-permit
signal (CTS) has gone false, or with software handshaking,
when it receives an XOFF character (DC3). Software can set
this bit again when it detects that the TX-permit signal has gone
true, or when it receives an XON (DC1) character.
17.5 Architecture
The architecture of the UART1 is shown below in the block diagram.
The APB interface provides a communications link between the CPU or host and the
UART1.
The UART1 receiver block, U1RX, monitors the serial input line, RXD1, for valid input.
The UART1 RX Shift Register (U1RSR) accepts valid characters via RXD1. After a valid
character is assembled in the U1RSR, it is passed to the UART1 RX Buffer Register FIFO
to await access by the CPU or host via the generic host interface.
The UART1 transmitter block, U1TX, accepts data written by the CPU or host and buffers
the data in the UART1 TX Holding Register FIFO (U1THR). The UART1 TX Shift Register
(U1TSR) reads the data stored in the U1THR and assembles the data to transmit via the
serial output pin, TXD1.
The UART1 Baud Rate Generator block, U1BRG, generates the timing enables used by
the UART1 TX block. The U1BRG clock input source is the APB clock (PCLK). The main
clock is divided down per the divisor specified in the U1DLL and U1DLM registers. This
divided down clock is a 16x oversample clock, NBAUDOUT.
The modem interface contains registers U1MCR and U1MSR. This interface is
responsible for handshaking between a modem peripheral and the UART1.
The interrupt interface contains registers U1IER and U1IIR. The interrupt interface
receives several one clock wide enables from the U1TX and U1RX blocks.

Status information from the U1TX and U1RX is stored in the U1LSR. Control information
for the U1TX and U1RX is stored in the U1LCR.
MODEM U1TX
NTXRDY
TXD1
U1THR U1TSR
CTS
DSR U1MSR
RI
U1BRG
DCD
DTR
U1DLL NBAUDOUT
RTS
U1MCR
U1DLM RCLK
U1RX NRXRDY
INTERRUPT
RXD1
U1RBR U1RSR
U1INTR U1IER
U1IIR
U1FCR
U1LSR
U1SCR
U1LCR
PA[2:0]
PSEL
PSTB
PWRITE
APB
PD[7:0] INTERFACE DDIS
AR
MR
PCLK
Fig 89. LPC2300 UART1 block diagram

UM10211
Chapter 18: LPC23XX SPI

The SPI is configured using the following registers:
1. Power: In the PCONP register (Table 56), set bit PCSPI.

Remark: On reset, the SPI is enabled (PCSPI = 1).
2. Clock: In PCLK_SEL0 select PCLK_SPI (see Section 4.7.4). In master mode, the
clock must be scaled down (see Section 18.7.4).
3. Pins: Select SPI pins and their modes in PINSEL0 to PINSEL4 and PINMODE0 to
PINMODE4 (see Section 9.5).
4. Interrupts: Interrupts are enabled in the S0SPINT register Table 397. Interrupts are
enabled in the VIC using the VICIntEnable register (Table 76).
Remark: In the VIC, the SPI shares its interrupts with the SSP0 interface.
18.2 Features
• Compliant with Serial Peripheral Interface (SPI) specification.
• Synchronous, Serial, Full Duplex Communication.
• SPI master or slave.
• Maximum data bit rate of one eighth of the input clock rate.
• 8 to 16 bits per transfer
18.3 Introduction
SPI is a full duplex serial interfaces. It can handle multiple masters and slaves being
connected to a given bus. Only a single master and a single slave can communicate on
the interface during a given data transfer. During a data transfer the master always sends
8 to 16 bits of data to the slave, and the slave always sends a byte of data to the master.
18.4 SPI data transfers

Figure 90 is a timing diagram that illustrates the four different data transfer formats that
are available with the SPI. This timing diagram illustrates a single 8 bit data transfer. The
first thing you should notice in this timing diagram is that it is divided into three horizontal
parts. The first part describes the SCK and SSEL signals. The second part describes the
MOSI and MISO signals when the CPHA variable is 0. The third part describes the MOSI
and MISO signals when the CPHA variable is 1.
In the first part of the timing diagram, note two points. First, the SPI is illustrated with
CPOL set to both 0 and 1. The second point to note is the activation and de-activation of
the SSEL signal. When CPHA = 0, the SSEL signal will always go inactive between data
transfers. This is not guaranteed when CPHA = 1 (the signal can remain active).

SCK (CPOL = 0)
SCK (CPOL = 1)
SSEL
CPHA = 0
Cycle # CPHA = 0 1 2 3 4 5 6 7 8
MOSI (CPHA = 0) BIT 1 BIT 2 BIT 3 BIT 4 BIT 5 BIT 6 BIT 7 BIT 8
MISO (CPHA = 0) BIT 1 BIT 2 BIT 3 BIT 4 BIT 5 BIT 6 BIT 7 BIT 8
CPHA = 1
Cycle # CPHA = 1 1 2 3 4 5 6 7 8
MOSI (CPHA = 1) BIT 1 BIT 2 BIT 3 BIT 4 BIT 5 BIT 6 BIT 7 BIT 8
MISO (CPHA = 1) BIT 1 BIT 2 BIT 3 BIT 4 BIT 5 BIT 6 BIT 7 BIT 8
Fig 90. SPI data transfer format (CPHA = 0 and CPHA = 1)
The data and clock phase relationships are summarized in Table 388. This table
summarizes the following for each setting of CPOL and CPHA.
• When the first data bit is driven.

• When all other data bits are driven.
• When data is sampled.
Table 388. SPI Data To Clock Phase Relationship
CPOL and CPHA settings First data driven Other data driven Data sampled
CPOL = 0, CPHA = 0 Prior to first SCK rising edge SCK falling edge SCK rising edge
CPOL = 0, CPHA = 1 First SCK rising edge SCK rising edge SCK falling edge
CPOL = 1, CPHA = 0 Prior to first SCK falling edge SCK rising edge SCK falling edge
CPOL = 1, CPHA = 1 First SCK falling edge SCK falling edge SCK rising edge
The definition of when an 8 bit transfer starts and stops is dependent on whether a device
is a master or a slave, and the setting of the CPHA variable.
When a device is a master, the start of a transfer is indicated by the master having a byte
of data that is ready to be transmitted. At this point, the master can activate the clock, and
begin the transfer. The transfer ends when the last clock cycle of the transfer is complete.

When a device is a slave and CPHA is set to 0, the transfer starts when the SSEL signal
goes active, and ends when SSEL goes inactive. When a device is a slave, and CPHA is
set to 1, the transfer starts on the first clock edge when the slave is selected, and ends on
the last clock edge where data is sampled.
18.5 SPI peripheral details
18.5.1 General information

There are four registers that control the SPI peripheral. They are described in detail in
Section 18.7 “Register description” on page 463.
The SPI control register contains a number of programmable bits used to control the
function of the SPI block. The settings for this register must be set up prior to a given data
transfer taking place.
The SPI status register contains read only bits that are used to monitor the status of the
SPI interface, including normal functions, and exception conditions. The primary purpose
of this register is to detect completion of a data transfer. This is indicated by the SPIF bit.
The remaining bits in the register are exception condition indicators. These exceptions will
be described later in this section.
The SPI data register is used to provide the transmit and receive data bytes. An internal
shift register in the SPI block logic is used for the actual transmission and reception of the
serial data. Data is written to the SPI data register for the transmit case. There is no buffer
between the data register and the internal shift register. A write to the data register goes
directly into the internal shift register. Therefore, data should only be written to this register
when a transmit is not currently in progress. Read data is buffered. When a transfer is
complete, the receive data is transferred to a single byte data buffer, where it is later read.
A read of the SPI data register returns the value of the read data buffer.
The SPI clock counter register controls the clock rate when the SPI block is in master
mode. This needs to be set prior to a transfer taking place, when the SPI block is a
master. This register has no function when the SPI block is a slave.
The I/Os for this implementation of SPI are standard CMOS I/Os. The open drain SPI
option is not implemented in this design. When a device is set up to be a slave, its I/Os are
only active when it is selected by the SSEL signal being active.
18.5.2 Master operation

The following sequence describes how one should process a data transfer with the SPI
block when it is set up to be the master. This process assumes that any prior data transfer
has already completed.
1. Set the SPI clock counter register to the desired clock rate.
2. Set the SPI control register to the desired settings.
3. Write the data to transmitted to the SPI data register. This write starts the SPI data
transfer.
4. Wait for the SPIF bit in the SPI status register to be set to 1. The SPIF bit will be set
after the last cycle of the SPI data transfer.

5. Read the SPI status register.

6. Read the received data from the SPI data register (optional).
7. Go to step 3 if more data is required to transmit.
Note: A read or write of the SPI data register is required in order to clear the SPIF status
bit. Therefore, if the optional read of the SPI data register does not take place, a write to
this register is required in order to clear the SPIF status bit.
18.5.3 Slave operation

The following sequence describes how one should process a data transfer with the SPI
block when it is set up to be a slave. This process assumes that any prior data transfer
has already completed. It is required that the system clock driving the SPI logic be at least
8X faster than the SPI.
1. Set the SPI control register to the desired settings.

2. Write the data to transmitted to the SPI data register (optional). Note that this can only
be done when a slave SPI transfer is not in progress.
3. Wait for the SPIF bit in the SPI status register to be set to 1. The SPIF bit will be set
after the last sampling clock edge of the SPI data transfer.
4. Read the SPI status register.
5. Read the received data from the SPI data register (optional).
6. Go to step 2 if more data is required to transmit.
Note: A read or write of the SPI data register is required in order to clear the SPIF status
bit. Therefore, at least one of the optional reads or writes of the SPI data register must
take place, in order to clear the SPIF status bit.
18.5.4 Exception conditions

Read Overrun
A read overrun occurs when the SPI block internal read buffer contains data that has not
been read by the processor, and a new transfer has completed. The read buffer
containing valid data is indicated by the SPIF bit in the status register being active. When
a transfer completes, the SPI block needs to move the received data to the read buffer. If
the SPIF bit is active (the read buffer is full), the new receive data will be lost, and the read
overrun (ROVR) bit in the status register will be activated.
Write Collision
As stated previously, there is no write buffer between the SPI block bus interface, and the
internal shift register. As a result, data must not be written to the SPI data register when a
SPI data transfer is currently in progress. The time frame where data cannot be written to
the SPI data register is from when the transfer starts, until after the status register has
been read when the SPIF status is active. If the SPI data register is written in this time
frame, the write data will be lost, and the write collision (WCOL) bit in the status register
will be activated.
Mode Fault

If the SSEL signal goes active, when the SPI block is a master, this indicates another
master has selected the device to be a slave. This condition is known as a mode fault.
When a mode fault is detected, the mode fault (MODF) bit in the status register will be
activated, the SPI signal drivers will be de-activated, and the SPI mode will be changed to
be a slave.
If the Px.y/SSEL/... pin is assigned the SSEL function in Pin Function Select Register 0,
the SSEL signal must always be inactive when the SPI controller is a master.
Slave Abort
A slave transfer is considered to be aborted, if the SSEL signal goes inactive before the
transfer is complete. In the event of a slave abort, the transmit and receive data for the
transfer that was in progress are lost, and the slave abort (ABRT) bit in the status register
will be activated.

Table 389. SPI Pin Description
Pin Type Pin Description
Name
SCK Input/ Serial Clock. The SPI is a clock signal used to synchronize the transfer of data
Output across the SPI interface. The SPI is always driven by the master and received
by the slave. The clock is programmable to be active high or active low. The SPI
is only active during a data transfer. Any other time, it is either in its inactive
state, or tri-stated.
SSEL Input Slave Select. The SPI slave select signal is an active low signal that indicates
which slave is currently selected to participate in a data transfer. Each slave has
its own unique slave select signal input. The SSEL must be low before data
transactions begin and normally stays low for the duration of the transaction. If
the SSEL signal goes high any time during a data transfer, the transfer is
considered to be aborted. In this event, the slave returns to idle, and any data
that was received is thrown away. There are no other indications of this
exception. This signal is not directly driven by the master. It could be driven by a
simple general purpose I/O under software control.
On the LPC2300 (unlike earlier NXP ARM devices) the SSEL pin can be used
for a different function when the SPI interface is only used in Master mode. For
example, a pin hosting the SSEL function can be configured as an output digital
GPIO pin and used to select one of the SPI slaves.
MISO Input/ Master In Slave Out. The MISO signal is a unidirectional signal used to transfer
Output serial data from the slave to the master. When a device is a slave, serial data is
output on this signal. When a device is a master, serial data is input on this
signal. When a slave device is not selected, the slave drives the signal high
impedance.
MOSI Input/ Master Out Slave In. The MOSI signal is a unidirectional signal used to transfer
Output serial data from the master to the slave. When a device is a master, serial data
is output on this signal. When a device is a slave, serial data is input on this
signal.


The SPI contains 5 registers as shown in Table 390. All registers are byte, half word and
word accessible.
Table 390. SPI Register Map

Value[1]
S0SPCR SPI Control Register. This register controls the R/W 0x00 0xE002 0000
operation of the SPI.
S0SPSR SPI Status Register. This register shows the RO 0x00 0xE002 0004
status of the SPI.
S0SPDR SPI Data Register. This bi-directional register R/W 0x00 0xE002 0008
provides the transmit and receive data for the
SPI. Transmit data is provided to the SPI0 by
writing to this register. Data received by the SPI0
can be read from this register.
S0SPCCR SPI Clock Counter Register. This register R/W 0x00 0xE002 000C
controls the frequency of a master’s SCK0.
S0SPINT SPI Interrupt Flag. This register contains the R/W 0x00 0xE002 001C
interrupt flag for the SPI interface.
18.7.1 SPI Control Register (S0SPCR - 0xE002 0000)

The S0SPCR register controls the operation of the SPI0 as per the configuration bits
setting.
Table 391: SPI Control Register (S0SPCR - address 0xE002 0000) bit description
Value
defined.
2 BitEnable 0 The SPI controller sends and receives 8 bits of data per 0
transfer.
1 The SPI controller sends and receives the number of bits
selected by bits 11:8.
3 CPHA Clock phase control determines the relationship between 0
the data and the clock on SPI transfers, and controls
when a slave transfer is defined as starting and ending.
Data is sampled on the first clock edge of SCK. A transfer
0 starts and ends with activation and deactivation of the
SSEL signal.
1 Data is sampled on the second clock edge of the SCK. A
transfer starts with the first clock edge, and ends with the
last sampling edge when the SSEL signal is active.
4 CPOL Clock polarity control. 0
0 SCK is active high.
1 SCK is active low.

Table 391: SPI Control Register (S0SPCR - address 0xE002 0000) bit description
Value
5 MSTR Master mode select. 0
0 The SPI operates in Slave mode.
1 The SPI operates in Master mode.
6 LSBF LSB First controls which direction each byte is shifted 0
when transferred.
0 SPI data is transferred MSB (bit 7) first.
1 SPI data is transferred LSB (bit 0) first.
7 SPIE Serial peripheral interrupt enable. 0
0 SPI interrupts are inhibited.
1 A hardware interrupt is generated each time the SPIF or
MODF bits are activated.
11:8 BITS When bit 2 of this register is 1, this field controls the 0000
number of bits per transfer:
1000 8 bits per transfer
defined.
18.7.2 SPI Status Register (S0SPSR - 0xE002 0004)

The S0SPSR register controls the operation of the SPI0 as per the configuration bits
setting.
Table 392: SPI Status Register (S0SPSR - address 0xE002 0004) bit description
3 ABRT Slave abort. When 1, this bit indicates that a slave abort has 0
occurred. This bit is cleared by reading this register.
4 MODF Mode fault. when 1, this bit indicates that a Mode fault error has 0
occurred. This bit is cleared by reading this register, then writing
the SPI0 control register.

Table 392: SPI Status Register (S0SPSR - address 0xE002 0004) bit description
5 ROVR Read overrun. When 1, this bit indicates that a read overrun has 0
occurred. This bit is cleared by reading this register.
6 WCOL Write collision. When 1, this bit indicates that a write collision has 0
occurred. This bit is cleared by reading this register, then
accessing the SPI data register.
7 SPIF SPI transfer complete flag. When 1, this bit indicates when a SPI 0
data transfer is complete. When a master, this bit is set at the
end of the last cycle of the transfer. When a slave, this bit is set
on the last data sampling edge of the SCK. This bit is cleared by
first reading this register, then accessing the SPI data register.
Note: this is not the SPI interrupt flag. This flag is found in the
SPINT register.
18.7.3 SPI Data Register (S0SPDR - 0xE002 0008)

This bi-directional data register provides the transmit and receive data for the SPI.
Transmit data is provided to the SPI by writing to this register. Data received by the SPI
can be read from this register. When a master, a write to this register will start a SPI data
transfer. Writes to this register will be blocked from when a data transfer starts to when the
SPIF status bit is set, and the status register has not been read.
Table 393: SPI Data Register (S0SPDR - address 0xE002 0008) bit description
7:0 DataLow SPI Bi-directional data port. 0x00
15:8 DataHigh If bit 2 of the SPCR is 1 and bits 11:8 are other than 1000, some 0x00
or all of these bits contain the additional transmit and receive
bits. When less than 16 bits are selected, the more significant
among these bits read as zeroes.
18.7.4 SPI Clock Counter Register (S0SPCCR - 0xE002 000C)

This register controls the frequency of a master’s SCK. The register indicates the number
of SPI peripheral clock cycles that make up an SPI clock.
In Master mode, this register must be an even number greater than or equal to 8.
Violations of this can result in unpredictable behavior. The SPI0 SCK rate may be
calculated as: PCLK_SPI / SPCCR0 value. The SPI peripheral clock is determined by the
PCLKSEL0 register contents for PCLK_SPI.
In Slave mode, the SPI clock rate provided by the master must not exceed 1/8 of the SPI
peripheral clock selected in Section 4.7.4. The content of the S0SPCCR register is not
relevant.
Table 394: SPI Clock Counter Register (S0SPCCR - address 0xE002 000C) bit description
7:0 Counter SPI0 Clock counter setting. 0x00

18.7.5 SPI Test Control Register (SPTCR - 0xE002 0010)

Note that the bits in this register are intended for functional verification only. This register
should not be used for normal operation.
Table 395: SPI Test Control Register (SPTCR - address 0xE002 0010) bit description
0 - Reserved, user software should not write ones to reserved bits. NA
7:1 Test SPI test mode. When 0, the SPI operates normally. When 1, 0
SCK will always be on, independent of master mode select, and
data availability setting.
18.7.6 SPI Test Status Register (SPTSR - 0xE002 0014)

Note: The bits in this register are intended for functional verification only. This register
should not be used for normal operation.
This register is a replication of the SPI status register. The difference between the
registers is that a read of this register will not start the sequence of events required to
clear these status bits. A write to this register will set an interrupt if the write data for the
respective bit is a 1.
Table 396: SPI Test Status Register (SPTSR - address 0xE002 0014) bit description
3 ABRT Slave abort. 0
4 MODF Mode fault. 0
5 ROVR Read overrun. 0
6 WCOL Write collision. 0
7 SPIF SPI transfer complete flag. 0
18.7.7 SPI Interrupt Register (S0SPINT - 0xE002 001C)

This register contains the interrupt flag for the SPI0 interface.
Table 397: SPI Interrupt Register (S0SPINT - address 0xE002 001C) bit description
Value
0 SPI SPI interrupt flag. Set by the SPI interface to generate an interrupt. Cleared 0
Interrupt by writing a 1 to this bit.
Flag Note: this bit will be set once when SPIE = 1 and at least one of SPIF and
WCOL bits is 1. However, only when the SPI Interrupt bit is set and SPI0
Interrupt is enabled in the VIC, SPI based interrupt can be processed by
interrupt handling software.

18.8 Architecture
The block diagram of the SPI solution implemented in SPI0 interface is shown in the
Figure 91.
MOSI_IN
MOSI_OUT
MISO_IN
MISO_OUT
SPI SHIFT REGISTER
SCK_IN
SCK_OUT
SS_IN
SPI CLOCK
GENERATOR &
SPI Interrupt DETECTOR
SPI REGISTER
APB Bus INTERFACE
SPI STATE CONTROL
SCK_OUT_EN
MOSI_OUT_EN
MISO_OUT_EN
OUTPUT
ENABLE
LOGIC
Fig 91. SPI block diagram

UM10211
Chapter 19: LPC23XX SSP0/1 interfaces

The SSP0/1 interfaces are configured using the following registers:
1. Power: In the PCONP register (Table 56), set bit PCSSP0/1.

Remark: On reset, both SSP interfaces are enabled (PCSSP0/1 = 1).
2. Clock: In PCLK_SEL0 select PCLK_SSP1; in PCLK_SEL1 select PCLK_SSP0 (see
Section 4.7.4. In master mode, the clock must be scaled down (see Section 19.6.5).
3. Pins: Select SSP pins and their modes in PINSEL0 to PINSEL4 and PINMODE0 to
4. Interrupts: Interrupts are enabled in the SSPnIMSC register Section 19.6.6. Interrupts
are enabled in the VIC using the VICIntEnable register (Table 76).
Remark: In the VIC, the SSP0 shares its interrupts with the SPI interface.
5. Initialization: see Table 400 and Table 401.
19.2 Features
• Compatible with Motorola SPI, 4-wire TI SSI, and National Semiconductor Microwire
buses.
• Synchronous Serial Communication.
• Master or slave operation.
• 8 frame FIFOs for both transmit and receive.
• 4 to 16 bits frame.
• DMA transfers supported by GPDMA.
19.3 Description
The SSP is a Synchronous Serial Port (SSP) controller capable of operation on a SPI,
4-wire SSI, or Microwire bus. It can interact with multiple masters and slaves on the bus.
Only a single master and a single slave can communicate on the bus during a given data
transfer. Data transfers are in principle full duplex, with frames of 4 to 16 bits of data
flowing from the master to the slave and from the slave to the master. In practice it is often
the case that only one of these data flows carries meaningful data.
LPC2300 has two Synchronous Serial Port controllers -- SSP0 and SSP1.

19.4 Pin descriptions

Table 398. SSP pin descriptions
Interface pin
Pin
Type name/function Pin Description
Name
SPI SSI Microwire
SCK0/1 I/O SCK CLK SK Serial Clock. SCK/CLK/SK is a clock signal used
to synchronize the transfer of data. It is driven by
the master and received by the slave. When SPI
interface is used the clock is programmable to be
active high or active low, otherwise it is always
active high. SCK1 only switches during a data
transfer. Any other time, the SSPn either holds it in
its inactive state, or does not drive it (leaves it in
high impedance state).
SSEL0/1 I/O SSEL FS CS Frame Sync/Slave Select. When the SSPn is a
bus master, it drives this signal from shortly before
the start of serial data, to shortly after the end of
serial data, to signify a data transfer as appropriate
for the selected bus and mode. When the SSPn is
a bus slave, this signal qualifies the presence of
data from the Master, according to the protocol in
use.
When there is just one bus master and one bus
slave, the Frame Sync or Slave Select signal from
the Master can be connected directly to the slave’s
corresponding input. When there is more than one
slave on the bus, further qualification of their Frame
Select/Slave Select inputs will typically be
necessary to prevent more than one slave from
responding to a transfer.
MISO0/1 I/O MISO DR(M) SI(M) Master In Slave Out. The MISO signal transfers
DX(S) SO(S) serial data from the slave to the master. When the
SSPn is a slave, serial data is output on this signal.
When the SSPn is a master, it clocks in serial data
from this signal. When the SSPn is a slave and is
not selected by FS/SSEL, it does not drive this
signal (leaves it in high impedance state).
MOSI0/1 I/O MOSI DX(M) SO(M) Master Out Slave In. The MOSI signal transfers
DR(S) SI(S) serial data from the master to the slave. When the
SSPn is a master, it outputs serial data on this
signal. When the SSPn is a slave, it clocks in serial
data from this signal.
19.5 Bus description
19.5.1 Texas Instruments Synchronous Serial Frame Format

Figure 92 shows the 4-wire Texas Instruments synchronous serial frame format supported
by the SSP module.

CLK
FS
DX/DR MSB LSB
4 to 16 bits
a. Single frame transfer
CLK
FS
DX/DR MSB LSB MSB LSB
4 to 16 bits 4 to 16 bits
b. Continuous/back-to-back frames transfer

Fig 92. Texas Instruments Synchronous Serial Frame Format: a) Single and b) Continuous/back-to-back Two
Frames Transfer
For device configured as a master in this mode, CLK and FS are forced LOW, and the
transmit data line DX is tri-stated whenever the SSP is idle. Once the bottom entry of the
transmit FIFO contains data, FS is pulsed HIGH for one CLK period. The value to be
transmitted is also transferred from the transmit FIFO to the serial shift register of the
transmit logic. On the next rising edge of CLK, the MSB of the 4 to 16 bit data frame is
shifted out on the DX pin. Likewise, the MSB of the received data is shifted onto the DR
pin by the off-chip serial slave device.
Both the SSP and the off-chip serial slave device then clock each data bit into their serial
shifter on the falling edge of each CLK. The received data is transferred from the serial
shifter to the receive FIFO on the first rising edge of CLK after the LSB has been latched.
19.5.2 SPI Frame Format

The SPI interface is a four-wire interface where the SSEL signal behaves as a slave
select. The main feature of the SPI format is that the inactive state and phase of the SCK
signal are programmable through the CPOL and CPHA bits within the SSPCR0 control
register.
19.5.2.1 Clock Polarity (CPOL) and Phase (CPHA) Control

When the CPOL clock polarity control bit is LOW, it produces a steady state low value on
the SCK pin. If the CPOL clock polarity control bit is HIGH, a steady state high value is
placed on the CLK pin when data is not being transferred.

The CPHA control bit selects the clock edge that captures data and allows it to change
state. It has the most impact on the first bit transmitted by either allowing or not allowing a
clock transition before the first data capture edge. When the CPHA phase control bit is
LOW, data is captured on the first clock edge transition. If the CPHA clock phase control
bit is HIGH, data is captured on the second clock edge transition.
19.5.2.2 SPI Format with CPOL=0,CPHA=0

Single and continuous transmission signal sequences for SPI format with CPOL = 0,
CPHA = 0 are shown in Figure 93.
SCK
SSEL
MSB LSB
MOSI
MISO MSB LSB Q
4 to 16 bits
a. Single transfer with CPOL=0 and CPHA=0
SCK
SSEL
MOSI MSB LSB MSB LSB
MISO MSB LSB Q MSB LSB Q
b. Continuous transfer with CPOL=0 and CPHA=0

Fig 93. SPI Frame Format with CPOL=0 and CPHA=0 (a) Single and b) Continuous Transfer)
In this configuration, during idle periods:
• The CLK signal is forced LOW.

• SSEL is forced HIGH.
• The transmit MOSI/MISO pad is in high impedance.
If the SSP is enabled and there is valid data within the transmit FIFO, the start of
transmission is signified by the SSEL master signal being driven LOW. This causes slave
data to be enabled onto the MISO input line of the master. Master’s MOSI is enabled.
One half SCK period later, valid master data is transferred to the MOSI pin. Now that both
the master and slave data have been set, the SCK master clock pin goes HIGH after one
further half SCK period.
The data is now captured on the rising and propagated on the falling edges of the SCK
signal.

In the case of a single word transmission, after all bits of the data word have been
transferred, the SSEL line is returned to its idle HIGH state one SCK period after the last
bit has been captured.
However, in the case of continuous back-to-back transmissions, the SSEL signal must be
pulsed HIGH between each data word transfer. This is because the slave select pin
freezes the data in its serial peripheral register and does not allow it to be altered if the
CPHA bit is logic zero. Therefore the master device must raise the SSEL pin of the slave
device between each data transfer to enable the serial peripheral data write. On
completion of the continuous transfer, the SSEL pin is returned to its idle state one SCK
period after the last bit has been captured.
19.5.2.3 SPI Format with CPOL=0,CPHA=1

The transfer signal sequence for SPI format with CPOL = 0, CPHA = 1 is shown in
Figure 94, which covers both single and continuous transfers.
SCK
SSEL
MSB LSB
MOSI
MISO Q MSB LSB Q
4 to 16 bits
Fig 94. SPI Frame Format with CPOL=0 and CPHA=1
• The CLK signal is forced LOW.

transmission is signified by the SSEL master signal being driven LOW. Master’s MOSI pin
is enabled. After a further one half SCK period, both master and slave valid data is
enabled onto their respective transmission lines. At the same time, the SCK is enabled
with a rising edge transition.
Data is then captured on the falling edges and propagated on the rising edges of the SCK
signal.
In the case of a single word transfer, after all bits have been transferred, the SSEL line is
returned to its idle HIGH state one SCK period after the last bit has been captured.
For continuous back-to-back transfers, the SSEL pin is held LOW between successive
data words and termination is the same as that of the single word transfer.
19.5.2.4 SPI Format with CPOL = 1,CPHA = 0

Single and continuous transmission signal sequences for SPI format with CPOL=1,
CPHA=0 are shown in Figure 95.

SCK
SSEL
MSB LSB
MOSI
MISO MSB LSB Q
4 to 16 bits
a. Single transfer with CPOL=1 and CPHA=0
SCK
SSEL
MOSI MSB LSB MSB LSB
MISO MSB LSB Q MSB LSB Q
b. Continuous transfer with CPOL=1 and CPHA=0

Fig 95. SPI Frame Format with CPOL = 1 and CPHA = 0 (a) Single and b) Continuous Transfer)
• The CLK signal is forced HIGH.

transmission is signified by the SSEL master signal being driven LOW, which causes
slave data to be immediately transferred onto the MISO line of the master. Master’s MOSI
pin is enabled.
One half period later, valid master data is transferred to the MOSI line. Now that both the
master and slave data have been set, the SCK master clock pin becomes LOW after one
further half SCK period. This means that data is captured on the falling edges and be
propagated on the rising edges of the SCK signal.
In the case of a single word transmission, after all bits of the data word are transferred, the
SSEL line is returned to its idle HIGH state one SCK period after the last bit has been
captured.
However, in the case of continuous back-to-back transmissions, the SSEL signal must be
pulsed HIGH between each data word transfer. This is because the slave select pin
freezes the data in its serial peripheral register and does not allow it to be altered if the
CPHA bit is logic zero. Therefore the master device must raise the SSEL pin of the slave
device between each data transfer to enable the serial peripheral data write. On
completion of the continuous transfer, the SSEL pin is returned to its idle state one SCK
period after the last bit has been captured.

19.5.2.5 SPI Format with CPOL = 1,CPHA = 1

The transfer signal sequence for SPI format with CPOL = 1, CPHA = 1 is shown in
Figure 96, which covers both single and continuous transfers.
SCK
SSEL
MSB LSB
MOSI
MISO Q MSB LSB Q
4 to 16 bits
Fig 96. SPI Frame Format with CPOL = 1 and CPHA = 1
• The CLK signal is forced HIGH.

transmission is signified by the SSEL master signal being driven LOW. Master’s MOSI is
enabled. After a further one half SCK period, both master and slave data are enabled onto
their respective transmission lines. At the same time, the SCK is enabled with a falling
edge transition. Data is then captured on the rising edges and propagated on the falling
edges of the SCK signal.
After all bits have been transferred, in the case of a single word transmission, the SSEL
line is returned to its idle HIGH state one SCK period after the last bit has been captured.
For continuous back-to-back transmissions, the SSEL pins remains in its active LOW
state, until the final bit of the last word has been captured, and then returns to its idle state
as described above. In general, for continuous back-to-back transfers the SSEL pin is
held LOW between successive data words and termination is the same as that of the
single word transfer.
19.5.3 Semiconductor Microwire Frame Format

Figure 97 shows the Microwire frame format for a single frame. Figure 98 shows the same
format when back-to-back frames are transmitted.

SK
CS
MSB LSB
SO
8 bit control
SI 0 MSB LSB
4 to 16 bits
output data
Fig 97. Microwire Frame Format (Single Transfer)
Microwire format is very similar to SPI format, except that transmission is half-duplex
instead of full-duplex, using a master-slave message passing technique. Each serial
transmission begins with an 8 bit control word that is transmitted from the SSP to the
off-chip slave device. During this transmission, no incoming data is received by the SSP.
After the message has been sent, the off-chip slave decodes it and, after waiting one
serial clock after the last bit of the 8 bit control message has been sent, responds with the
required data. The returned data is 4 to 16 bits in length, making the total frame length
anywhere from 13 to 25 bits.
• The SK signal is forced LOW.

• CS is forced HIGH.
• The transmit data line SO is arbitrarily forced LOW.
A transmission is triggered by writing a control byte to the transmit FIFO.The falling edge
of CS causes the value contained in the bottom entry of the transmit FIFO to be
transferred to the serial shift register of the transmit logic, and the MSB of the 8 bit control
frame to be shifted out onto the SO pin. CS remains LOW for the duration of the frame
transmission. The SI pin remains tri-stated during this transmission.
The off-chip serial slave device latches each control bit into its serial shifter on the rising
edge of each SK. After the last bit is latched by the slave device, the control byte is
decoded during a one clock wait-state, and the slave responds by transmitting data back
to the SSP. Each bit is driven onto SI line on the falling edge of SK. The SSP in turn
latches each bit on the rising edge of SK. At the end of the frame, for single transfers, the
CS signal is pulled HIGH one clock period after the last bit has been latched in the receive
serial shifter, that causes the data to be transferred to the receive FIFO.
Note: The off-chip slave device can tri-state the receive line either on the falling edge of
SK after the LSB has been latched by the receive shiftier, or when the CS pin goes HIGH.
For continuous transfers, data transmission begins and ends in the same manner as a
single transfer. However, the CS line is continuously asserted (held LOW) and
transmission of data occurs back to back. The control byte of the next frame follows
directly after the LSB of the received data from the current frame. Each of the received
values is transferred from the receive shifter on the falling edge SK, after the LSB of the
frame has been latched into the SSP.

SK
CS
SO LSB MSB LSB

8 bit control
SI 0 MSB LSB MSB LSB
output data output data
Fig 98. Microwire Frame Format (Continuous Transfers)
19.5.3.1 Setup and Hold Time Requirements on CS With Respect to SK in Microwire

Mode
In the Microwire mode, the SSP slave samples the first bit of receive data on the rising
edge of SK after CS has gone LOW. Masters that drive a free-running SK must ensure
that the CS signal has sufficient setup and hold margins with respect to the rising edge of
SK.
Figure 99 illustrates these setup and hold time requirements. With respect to the SK rising
edge on which the first bit of receive data is to be sampled by the SSP slave, CS must
have a setup of at least two times the period of SK on which the SSP operates. With
respect to the SK rising edge previous to this edge, CS must have a hold of at least one
SK period.
tSETUP=2*tSK
t HOLD= tSK
SK
CS
SI
Fig 99. Microwire frame format setup and hold details
19.6 Register Description

The register offsets from the SSP controller base addresses are shown in the Table 399.
Table 399. SSP Register Map

Generic Name Description Access Reset SSPn Register
Value[1] Name & Address
CR0 Control Register 0. Selects the serial clock rate, bus R/W 0 SSP0CR0 - 0xE006 8000
type, and data size. SSP1CR0 - 0xE003 0000
CR1 Control Register 1. Selects master/slave and other R/W 0 SSP0CR1 - 0xE006 8004
modes. SSP1CR1 - 0xE003 0004
DR Data Register. Writes fill the transmit FIFO, and R/W 0 SSP0DR - 0xE006 8008
reads empty the receive FIFO. SSP1DR - 0xE003 0008

Table 399. SSP Register Map

Generic Name Description Access Reset SSPn Register
Value[1] Name & Address
SR Status Register RO SSP0SR - 0xE006 800C
SSP1SR - 0xE003 000C
CPSR Clock Prescale Register R/W 0 SSP0CPSR - 0xE006 8010
SSP1CPSR - 0xE003 0010
IMSC Interrupt Mask Set and Clear Register R/W 0 SSP0IMSC - 0xE006 8014
SSP1IMSC - 0xE003 0014
RIS Raw Interrupt Status Register R/W SSP0RIS - 0xE006 8018
SSP1RIS - 0xE003 0018
MIS Masked Interrupt Status Register R/W 0 SSP0MIS - 0xE006 801C
SSP1MIS - 0xE003 001C
ICR SSPICR Interrupt Clear Register R/W NA SSP0ICR - 0xE006 8020
SSP1ICR - 0xE003 0020
DMACR DMA Control Register R/W 0 SSP0DMACR - 0xE006 8024
SSP1DMACR - 0xE003 0024
19.6.1 SSPn Control Register 0 (SSP0CR0 - 0xE006 8000, SSP1CR0 - 0xE003

0000)
This register controls the basic operation of the SSP controller.
Table 400: SSPn Control Register 0 (SSP0CR0 - address 0xE006 8000, SSP1CR0 -
Value
3:0 DSS Data Size Select. This field controls the number of bits 0000
transferred in each frame. Values 0000-0010 are not
supported and should not be used.
0011 4 bit transfer
0100 5 bit transfer
0101 6 bit transfer
0110 7 bit transfer
0111 8 bit transfer
1000 9 bit transfer
1001 10 bit transfer

Value
5:4 FRF Frame Format. 00
00 SPI
01 TI
10 Microwire
11 This combination is not supported and should not be used.
6 CPOL Clock Out Polarity. This bit is only used in SPI mode. 0
0 SSP controller maintains the bus clock low between frames.
1 SSP controller maintains the bus clock high between frames.
7 CPHA Clock Out Phase. This bit is only used in SPI mode. 0
0 SSP controller captures serial data on the first clock transition
of the frame, that is, the transition away from the inter-frame
state of the clock line.
1 SSP controller captures serial data on the second clock
transition of the frame, that is, the transition back to the
inter-frame state of the clock line.
15:8 SCR Serial Clock Rate. The number of prescaler-output clocks per 0x00
bit on the bus, minus one. Given that CPSDVSR is the
prescale divider, and the APB clock PCLK clocks the
prescaler, the bit frequency is PCLK / (CPSDVSR  [SCR+1]).
19.6.2 SSPn Control Register 1 (SSP0CR1 - 0xE006 8004, SSP1CR1 -

0xE003 0004)
This register controls certain aspects of the operation of the SSP controller.
Value
0 LBM Loop Back Mode. 0
0 During normal operation.
1 Serial input is taken from the serial output (MOSI or MISO)
rather than the serial input pin (MISO or MOSI
respectively).
1 SSE SSP Enable. 0
0 The SSP controller is disabled.
1 The SSP controller will interact with other devices on the
serial bus. Software should write the appropriate control
information to the other SSP registers and interrupt
controller registers, before setting this bit.

Value
2 MS Master/Slave Mode.This bit can only be written when the 0
SSE bit is 0.
The SSP controller acts as a master on the bus, driving the
0 SCLK, MOSI, and SSEL lines and receiving the MISO line.
1 The SSP controller acts as a slave on the bus, driving
MISO line and receiving SCLK, MOSI, and SSEL lines.
3 SOD Slave Output Disable. This bit is relevant only in slave 0
mode (MS = 1). If it is 1, this blocks this SSP controller
from driving the transmit data line (MISO).
19.6.3 SSPn Data Register (SSP0DR - 0xE006 8008, SSP1DR - 0xE003 0008)
Software can write data to be transmitted to this register, and read data that has been
received.
Table 402: SSPn Data Register (SSP0DR - address 0xE006 8008, SSP1DR - 0xE003 0008) bit
description
15:0 DATA Write: software can write data to be sent in a future frame to this 0x0000
register whenever the TNF bit in the Status register is 1,
indicating that the Tx FIFO is not full. If the Tx FIFO was
previously empty and the SSP controller is not busy on the bus,
transmission of the data will begin immediately. Otherwise the
data written to this register will be sent as soon as all previous
data has been sent (and received). If the data length is less than
16 bits, software must right-justify the data written to this register.
Read: software can read data from this register whenever the
RNE bit in the Status register is 1, indicating that the Rx FIFO is
not empty. When software reads this register, the SSP controller
returns data from the least recent frame in the Rx FIFO. If the
data length is less than 16 bits, the data is right-justified in this
field with higher order bits filled with 0s.
19.6.4 SSPn Status Register (SSP0SR - 0xE006 800C, SSP1SR -

0xE003 000C)
This read-only register reflects the current status of the SSP controller.
Table 403: SSPn Status Register (SSP0SR - address 0xE006 800C, SSP1SR - 0xE003 000C)
bit description
0 TFE Transmit FIFO Empty. This bit is 1 is the Transmit FIFO is 1
empty, 0 if not.
1 TNF Transmit FIFO Not Full. This bit is 0 if the Tx FIFO is full, 1 if not. 1
2 RNE Receive FIFO Not Empty. This bit is 0 if the Receive FIFO is 0
empty, 1 if not.

Table 403: SSPn Status Register (SSP0SR - address 0xE006 800C, SSP1SR - 0xE003 000C)
bit description
3 RFF Receive FIFO Full. This bit is 1 if the Receive FIFO is full, 0 if 0
not.
4 BSY Busy. This bit is 0 if the SSPn controller is idle, or 1 if it is 0
currently sending/receiving a frame and/or the Tx FIFO is not
empty.
19.6.5 SSPn Clock Prescale Register (SSP0CPSR - 0xE006 8010, SSP1CPSR

- 0xE003 0010)
This register controls the factor by which the Prescaler divides the SSP peripheral clock
SSP_PCLK to yield the prescaler clock that is, in turn, divided by the SCR factor in
SSPnCR0, to determine the bit clock.
Table 404: SSPn Clock Prescale Register (SSP0CPSR - address 0xE006 8010, SSP1CPSR -
7:0 CPSDVSR This even value between 2 and 254, by which SSP_PCLK is 0
divided to yield the prescaler output clock. Bit 0 always reads
as 0.
Important: the SSPnCPSR value must be properly initialized or the SSP controller will not
be able to transmit data correctly.
In Slave mode, the SSP clock rate provided by the master must not exceed 1/12 of the
SSP peripheral clock selected in Section 4.7.4. The content of the SSPnCPSR register is
not relevant.
In master mode, CPSDVSRmin = 2 or larger (even numbers only).
19.6.6 SSPn Interrupt Mask Set/Clear Register (SSP0IMSC - 0xE006 8014,

SSP1IMSC - 0xE003 0014)
This register controls whether each of the four possible interrupt conditions in the SSP
controller are enabled. Note that ARM uses the word “masked” in the opposite sense from
classic computer terminology, in which “masked” meant “disabled”. ARM uses the word
“masked” to mean “enabled”. To avoid confusion we will not use the word “masked”.

Table 405: SSPn Interrupt Mask Set/Clear register (SSP0IMSC - address 0xE006 8014,
SSP1IMSC - 0xE003 0014) bit description
Value
0 RORIM Software should set this bit to enable interrupt when a Receive 0
Overrun occurs, that is, when the Rx FIFO is full and another frame is
completely received. The ARM spec implies that the preceding frame
data is overwritten by the new frame data when this occurs.
1 RTIM Software should set this bit to enable interrupt when a Receive 0
Timeout condition occurs. A Receive Timeout occurs when the Rx
FIFO is not empty, and no has not been read for a "timeout period".
2 RXIM Software should set this bit to enable interrupt when the Rx FIFO is at 0
least half full.
3 TXIM Software should set this bit to enable interrupt when the Tx FIFO is at 0
least half empty.
19.6.7 SSPn Raw Interrupt Status Register (SSP0RIS - 0xE006 8018,

SSP1RIS - 0xE003 0018)
This read-only register contains a 1 for each interrupt condition that is asserted,
regardless of whether or not the interrupt is enabled in the SSPnIMSC.
Table 406: SSPn Raw Interrupt Status register (SSP0RIS - address 0xE006 8018, SSP1RIS -
0 RORRIS This bit is 1 if another frame was completely received while the 0
RxFIFO was full. The ARM spec implies that the preceding
frame data is overwritten by the new frame data when this
occurs.
1 RTRIS This bit is 1 if the Rx FIFO is not empty, and has not been read 0
for a "timeout period".
2 RXRIS This bit is 1 if the Rx FIFO is at least half full. 0
3 TXRIS This bit is 1 if the Tx FIFO is at least half empty. 1
19.6.8 SSPn Masked Interrupt Status Register (SSP0MIS - 0xE006 801C,

SSP1MIS - 0xE003 001C)
This read-only register contains a 1 for each interrupt condition that is asserted and
enabled in the SSPnIMSC. When an SSP interrupt occurs, the interrupt service routine
should read this register to determine the cause(s) of the interrupt.

Table 407: SSPn Masked Interrupt Status register (SSPnMIS -address 0xE006 801C,
SSP1MIS - 0xE003 001C) bit description
0 RORMIS This bit is 1 if another frame was completely received while the 0
RxFIFO was full, and this interrupt is enabled.
1 RTMIS This bit is 1 if the Rx FIFO is not empty, has not been read for 0
a "timeout period", and this interrupt is enabled.
2 RXMIS This bit is 1 if the Rx FIFO is at least half full, and this interrupt 0
is enabled.
3 TXMIS This bit is 1 if the Tx FIFO is at least half empty, and this 0
interrupt is enabled.
19.6.9 SSPn Interrupt Clear Register (SSP0ICR - 0xE006 8020, SSP1ICR -

0xE003 0020)
Software can write one or more one(s) to this write-only register, to clear the
corresponding interrupt condition(s) in the SSP controller. Note that the other two interrupt
conditions can be cleared by writing or reading the appropriate FIFO, or disabled by
clearing the corresponding bit in SSPnIMSC.
Table 408: SSPn interrupt Clear Register (SSP0ICR - address 0xE006 8020, SSP1ICR -
0 RORIC Writing a 1 to this bit clears the “frame was received when NA
RxFIFO was full” interrupt.
1 RTIC Writing a 1 to this bit clears the "Rx FIFO was not empty and NA
has not been read for a timeout period" interrupt.
19.6.10 SSPn DMA Control Register (SSP0DMACR - 0xE006 8024,

SSP1DMACR - 0xE003 0024)
The SSPnDMACR register is the DMA control register.It is a read/write register. Table 409
shows the bit assignments of the SSPnDMACR register.
Table 409: SSPn DMA Control Register (SSP0DMACR - address 0xE006 8024, SSP1DMACR -
Value
0 Receive DMA When this bit is set to one 1, DMA for the receive FIFO is 0
Enable enabled, otherwise receive DMA is disabled.
(RXDMAE)
1 Transmit DMA When this bit is set to one 1, DMA for the transmit FIFO is 0
Enable enabled, otherwise transmit DMA is disabled
(TXDMAE)

UM10211
Chapter 20: LPC23XX SD/MMC interface

This chapter describes the SD/MMC interface for the following LPC23XX parts:
• LPC2367/68
• LPC2377/78
• LPC2387
• LPC2388
LPC2361/61/64/65/66 do not include an SD/MMC interface.

The SD/MMC is configured using the following registers:
1. Power: In the PCONP register (Table 56), set bit PCSDC.

Remark: On reset, the SD/MMC is disabled (PCMCI = 0).
2. Clock: In PCLK_SEL1 select PCLK_MCI (see Section 4.7.4).
3. Pins: Select SD/MMC pins and their modes in PINSEL0 to PINSEL4 and PINMODE0
to PINMODE4 (see Section 9.5).
(Table 76).
20.3 Introduction
The Secure Digital and Multimedia Card Interface (MCI) is an interface between the
Advanced Peripheral Bus (APB) system bus and multimedia and/or secure digital memory
cards. It consists of two parts:
• The MCI adapter block provides all functions specific to the Secure Digital/MultiMedia
memory card, such as the clock generation unit, power management control,
command and data transfer.
• The APB interface accesses the MCI adapter registers, and generates interrupt and
DMA request signals.
20.4 Features
The following features are provided by the MCI:
• Conformance to Multimedia Card Specification v2.11.

• Conformance to Secure Digital Memory Card Physical Layer Specification, v0.96.
• Use as a multimedia card bus or a secure digital memory card bus host. It can be
connected to several multimedia cards or a single secure digital memory card.
• DMA supported through the General Purpose DMA Controller.

20.5 SD/MMC card interface pin description

Table 410. SD/MMC card interface pin description
MCICLK Output Clock output
MCICMD Input Command input/output.
MCIDAT[3:0] Output Data lines. Only MCIDAT[0] is used for Multimedia cards.
MCIPWR Output Power Supply Enable for external SD/MMC power supply.
There is one additional signal needed in the interface, a power control line MCIPWR, but it
can be sourced from any GPIO signal.

The MCI may be used as a multimedia card bus host (see Section 20.6.1 “Mutimedia
card”) or a secure digital memory card bus host (see Section 20.6.2 “Secure digital
memory card”). Up to 4 multimedia cards (limited by board loading) may be connected, or
a single secure digital memory card.
20.6.1 Mutimedia card

Figure 100 shows the multimedia card system.
POWER MULTIMEDIA
CARD
SUPPLY
INTERFACE
MULTIMEDIA CARD BUS
CARD CARD CARD
MULTIMEDIA CARD STACK
Fig 100. Multimedia card system
Multimedia cards are grouped into three types according to their function:
• Read Only Memory (ROM) cards, containing pre-programmed data

• Read/Write (R/W) cards, used for mass storage
• Input/Output (I/O) cards, used for communication
The multimedia card system transfers commands and data using three signal lines:
• CLK: One bit is transferred on both command and data lines with each clock cycle.
The clock frequency varies between 0 MHz and 20 MHz (for a multimedia card) or
0 MHz and 25 MHz (for a secure digital memory card).

• CMD: Bidirectional command channel that initializes a card and transfers commands.
CMD has two operational modes:
– Open-drain for initialization
– Push-pull for command transfer
• DAT: Bidirectional data channel, operating in push-pull mode
20.6.2 Secure digital memory card

Figure 101 shows the secure digital memory card connection.
CLK
SECURE
SECURE
DIGITAL CMD
DIGITAL
MEMORY CARD
MEMORY CARD
CONTROLLER D[3:0]
Fig 101. Secure digital memory card connection
20.6.2.1 Secure digital memory card bus signals

The following signals are used on the secure digital memory card bus:
• CLK Host to card clock signal

• CMD Bidirectional command/response signal
• DAT[3:0] Bidirectional data signals
20.6.3 MCI adapter

Figure 102 shows a simplified block diagram of the MCI adapter.
MULTIMEDIA CARD INTERFACE
MCICLK
CONTROL
UNIT MCIPWR
COMMAND MCICMD
APB ADAPTER PATH
APB BUS
INTERFACE REGISTERS
MCIDATA [3:0]
DATA PATH
FIFO
Fig 102. MCI adapter
The MCI adapter is a multimedia/secure digital memory card bus master that provides an
interface to a multimedia card stack or to a secure digital memory card. It consists of five
subunits:

• Adapter register block

• Control unit
• Command path
• Data path
• Data FIFO
20.6.3.1 Adapter register block

The adapter register block contains all system registers. This block also generates the
signals that clear the static flags in the multimedia card. The clear signals are generated
when 1 is written into the corresponding bit location of the MCIClear register.
20.6.3.2 Control unit

The control unit contains the power management functions and the clock divider for the
memory card clock.
There are three power phases:
• Power-off
• Power-up
• Power-on
The power management logic controls an external power supply unit, and disables the
card bus output signals during the power-off or power-up phases. The power-up phase is
a transition phase between the power-off and power-on phases, and allows an external
power supply to reach the card bus operating voltage. A device driver is used to ensure
that the PrimeCell MCI remains in the power-up phase until the external power supply
reaches the operating voltage.
The clock management logic generates and controls the MCICLK signal. The MCICLK
output can use either a clock divide or clock bypass mode. The clock output is inactive:
• after reset
• during the power-off or power-up phases
• if the power saving mode is enabled and the card bus is in the IDLE state (eight clock
periods after both the command and data path subunits enter the IDLE phase)
20.6.3.3 Command path

The command path subunit sends commands to and receives responses from the cards.
20.6.3.4 Command path state machine

When the command register is written to and the enable bit is set, command transfer
starts. When the command has been sent, the Command Path State Machine (CPSM)
sets the status flags and enters the IDLE state if a response is not required. If a response
is required, it waits for the response (see Figure 103). When the response is received, the
received CRC code and the internally generated code are compared, and the appropriate
status flags are set.

IDLE
Enabled and Response received

Pending command or disabled or
command CRC failed
Disabled
Disabled or RECEIVE
PEND no response
Disabled
Enabled and or timeout
command start
Response
LastData
started
SEND WAIT
Wait for
response
Fig 103. Command path state machine
When the WAIT state is entered, the command timer starts running. If the time-out1 is
reached before the CPSM moves to the RECEIVE state, the time-out flag is set and the
IDLE2 state is entered.
If the interrupt bit is set in the command register, the timer is disabled and the CPSM waits
for an interrupt request from one of the cards. If a pending bit is set in the command
register, the CPSM enters the PEND state, and waits for a CmdPend signal from the data
path subunit. When CmdPend is detected, the CPSM moves to the SEND state. This
enables the data counter to trigger the stop command transmission.
Figure 104 shows the MCI command transfer.
min 8
MCICLK
MCICLK COMMAND RESPONSE COMMAND
State IDLE SEND WAIT RECEIVE IDLE SEND
MCICMD HI-Z controller drives HI-Z card drives HI-Z controller drives
Fig 104. MCI command transfer
1. The timeout period has a fixed value of 64 MCICLK clocks period.

2. The CPSM remains in the IDLE state for at least eight MCICLK periods to meet Ncc and Nrc timing constraints.

20.6.3.5 Command format

The command path operates in a half-duplex mode, so that commands and responses
can either be sent or received. If the CPSM is not in the SEND state, the MCICMD output
is in HI-Z state, as shown in Figure 104. Data on MCICMD is synchronous to the rising
MCICLK edge. All commands have a fixed length of 48 bits. Table 411 shows the
command format.
Table 411. Command format

Bit Position Width Value Description
0 1 1 End bit.
7:1 7 - CRC7
39:8 32 - Argument.
45:40 6 - Command index.
46 1 1 Transmission bit.
47 1 0 Stat bit.
The MCI adapter supports two response types. Both use CRC error checking:
• 48 bit short response (see Table 412)

• 136 bit long response (see Table 413)
Note: If the response does not contain CRC (CMD1 response), the device driver must
ignore the CRC failed status.
Table 412. Simple response format

0 1 1 End bit.
7:1 7 - CRC7 (or 1111111).
39:8 32 - Argument.
45:40 6 - Command index.
47 1 0 Start bit.
Table 413. Long response format

0 1 1 End bit.
127:1 127 - CID or CSD (including internal CRC7).
133:128 6 111111 Reserved.
135 1 0 Start bit.
The command register contains the command index (six bits sent to a card) and the
command type. These determine whether the command requires a response, and
whether the response is 48 or 136 bits long (see Section 20.7.5 “Command Register
(MCICommand - 0xE008 C00C)” for more information). The command path implements
the status flags shown in Table 414 (see Section 20.7.12 “Status Register (MCIStatus -
0xE008 C034)” for more information).

Table 414. Command path status flags

Flag Description
CmdRespEnd Set if response CRC is OK.
CmdCrcFail Set if response CRC fails.
CmdSent Set when command (that does not require response) is sent.
CmdTimeOut Response timeout.
CmdActive Command transfer in progress.
The CRC generator calculates the CRC checksum for all bits before the CRC code. This
includes the start bit, transmitter bit, command index, and command argument (or card
status). The CRC checksum is calculated for the first 120 bits of CID or CSD for the long
response format. Note that the start bit, transmitter bit and the six reserved bits are not
used in the CRC calculation.
The CRC checksum is a 7 bit value:
CRC[6:0] = Remainder [(M(x)  x7 ) / G(x)]
G(x) = x7 + x3 + 1
M(x) = (start bit)  x39 + ... + (last bit before CRC)  x0 , or
M(x) = (start bit)  x119 + ... + (last bit before CRC)  x0
20.6.3.6 Data path

The card data bus width can be programmed using the clock control register. If the wide
bus mode is enabled, data is transferred at four bits per clock cycle over all four data
signals (MCIDAT[3:0]). If the wide bus mode is not enabled, only one bit per clock cycle is
transferred over MCIDAT0.
Depending on the transfer direction (send or receive), the Data Path State Machine
(DPSM) moves to the WAIT_S or WAIT_R state when it is enabled:
• Send: The DPSM moves to the WAIT_S state. If there is data in the send FIFO, the
DPSM moves to the SEND state, and the data path subunit starts sending data to a
card.
• Receive: The DPSM moves to the WAIT_R state and waits for a start bit. When it
receives a start bit, the DPSM moves to the RECEIVE state, and the data path subunit
starts receiving data from a card.
20.6.3.7 Data path state machine

The DPSM operates at MCICLK frequency. Data on the card bus signals is synchronous
to the rising edge of MCICLK. The DPSM has six states, as shown in Figure 105.

Reset
IDLE
Disabled or Disabled or
FIFO underrun or CRC fail or
end of data or timeout
CRC fail Disabled or
Rx FIFO empty Enable and
not send Disabled or
Disabled or or timeout or
CRC fail
end of data start bit error
Enable
BUSY and send WAIT_R
Not busy
End of packet
WAIT_S or end of data
End of packet or FIFO overrun
Start bit
Data ready
SEND RECEIVE
Fig 105. Data path state machine
• IDLE: The data path is inactive, and the MCIDAT[3:0] outputs are in HI-Z. When the
data control register is written and the enable bit is set, the DPSM loads the data
counter with a new value and, depending on the data direction bit, moves to either the
WAIT_S or WAIT_R state.
WAIT_R: If the data counter equals zero, the DPSM moves to the IDLE state when
the receive FIFO is empty. If the data counter is not zero, the DPSM waits for a start
bit on MCIDAT.
The DPSM moves to the RECEIVE state if it receives a start bit before a time-out, and
loads the data block counter. If it reaches a time-out before it detects a start bit, or a start
bit error occurs, it moves to the IDLE state and sets the time-out status flag.
• RECEIVE: Serial data received from a card is packed in bytes and written to the data
FIFO. Depending on the transfer mode bit in the data control register, the data transfer
mode can be either block or stream:
– In block mode, when the data block counter reaches zero, the DPSM waits until it
receives the CRC code. If the received code matches the internally generated
CRC code, the DPSM moves to the WAIT_R state. If not, the CRC fail status flag is
set and the DPSM moves to the IDLE state.
– In stream mode, the DPSM receives data while the data counter is not zero. When
the counter is zero, the remaining data in the shift register is written to the data
FIFO, and the DPSM moves to the WAIT_R state.
If a FIFO overrun error occurs, the DPSM sets the FIFO error flag and moves to the
WAIT_R state.
• WAIT_S: The DPSM moves to the IDLE state if the data counter is zero. If not, it waits
until the data FIFO empty flag is deasserted, and moves to the SEND state.

Note: The DPSM remains in the WAIT_S state for at least two clock periods to meet Nwr
timing constraints.
• SEND: The DPSM starts sending data to a card. Depending on the transfer mode bit
in the data control register, the data transfer mode can be either block or stream:
– In block mode, when the data block counter reaches zero, the DPSM sends an
internally generated CRC code and end bit, and moves to the BUSY state.
– In stream mode, the DPSM sends data to a card while the enable bit is HIGH and
the data counter is not zero. It then moves to the IDLE state.
If a FIFO underrun error occurs, the DPSM sets the FIFO error flag and moves to the
IDLE state.
• BUSY: The DPSM waits for the CRC status flag:

– If it does not receive a positive CRC status, it moves to the IDLE state and sets the
CRC fail status flag.
– If it receives a positive CRC status, it moves to the WAIT_S state if MCIDAT0 is not
LOW (the card is not busy).
If a time-out occurs while the DPSM is in the BUSY state, it sets the data time-out flag and
moves to the IDLE state.
The data timer is enabled when the DPSM is in the WAIT_R or BUSY state, and
generates the data time-out error:
• When transmitting data, the time-out occurs if the DPSM stays in the BUSY state for
longer than the programmed time-out period
• When receiving data, the time-out occurs if the end of the data is not true, and if the
DPSM stays in the WAIT_R state for longer than the programmed time-out period.
20.6.3.8 Data counter

The data counter has two functions:
• To stop a data transfer when it reaches zero. This is the end of the data condition.
• To start transferring a pending command (see Figure 106). This is used to send the
stop command for a stream data transfer.

MCICLK
MCICMD 3 2 1 0 7 6 5 4 3 2 1
cmd state PEND SEND
MCIDAT0 Z Z Z Z Z S CMD CMD CMD CMD CMD
data
7 6
counter
CmdPend
Fig 106. Pending command start
The data block counter determines the end of a data block. If the counter is zero, the
end-of-data condition is TRUE (see Section 20.7.10 “Data Control Register (MCIDataCtrl -
0xE008 C02C)” for more information).
20.6.3.9 Bus mode

In wide bus mode, all four data signals (MCIDAT[3:0]) are used to transfer data, and the
CRC code is calculated separately for each data signal. While transmitting data blocks to
a card, only MCIDAT0 is used for the CRC token and busy signalling. The start bit must be
transmitted on all four data signals at the same time (during the same clock period). If the
start bit is not detected on all data signals on the same clock edge while receiving data,
the DPSM sets the start bit error flag and moves to the IDLE state.
The data path also operates in half-duplex mode, where data is either sent to a card or
received from a card. While not being transferred, MCIDAT[3:0] are in the HI-Z state.
Data on these signals is synchronous to the rising edge of the clock period.
If standard bus mode is selected the MCIDAT[3:1] outputs are always in HI-Z state and
only the MCIDAT0 output is driven LOW when data is transmitted.
Design note: If wide mode is selected, both nMCIDAT0EN and nMCIDATEN outputs are
driven low at the same time. If not, the MCIDAT[3:1] outputs are always in HI-Z state
(nMCIDATEN) is driven HIGH), and only the MCIDAT0 output is driven LOW when data is
transmitted.
20.6.3.10 CRC Token status

The CRC token status follows each write data block, and determines whether a card has
received the data block correctly. When the token has been received, the card asserts a
busy signal by driving MCIDAT0 LOW. Table 415 shows the CRC token status values.
Table 415. CRC token status

Token Description
010 Card has received error-free data block.
101 Card has detected a CRC error.

20.6.3.11 Status flags

Table 416 lists the data path status flags (see Section 20.7.12 “Status Register (MCIStatus
- 0xE008 C034)” on page 501 for more information).
Table 416. Data path status flags

Flag Description
TxFifoFull Transmit FIFO is full.
TxFifoEmpty Transmit FIFO is empty.
TxFifoHalfEmpty Transmit FIFO is half full.
TxDataAvlbl Transmit FIFO data available.
TxUnderrun Transmit FIFO underrun error.
RxFifoFull Receive FIFO is full.
RxFifoEmpty Receive FIFO is empty.
RxFifoHalfFull Receive FIFO is half full.
RxDataAvlbl Receive FIFO data available.
RxOverrun Receive FIFO overrun error.
DataBlockEnd Data block sent/received.
StartBitErr Start bit not detected on all data signals in wide bus mode.
DataCrcFail Data packet CRC failed.
DataEnd Data end (data counter is zero).
DataTimeOut Data timeout.
TxActive Data transmission in progress.
RxActive Data reception in progress.
20.6.3.12 CRC generator

The CRC generator calculates the CRC checksum only for the data bits in a single block,
and is bypassed in data stream mode. The checksum is a 16 bit value:
CRC[15:0] = Remainder [(M(x)  x15) / G(x)]
G(x) = x16 + x12 + x5 + 1
M(x) - (first data bit)  xn + ... + (last data bit) ¥ X0
20.6.3.13 Data FIFO

The data FIFO (first-in-first-out) subunit is a data buffer with transmit and receive logic.
The FIFO contains a 32 bit wide, 16-word deep data buffer, and transmit and receive
logic. Because the data FIFO operates in the APB clock domain (PCLK), all signals from
the subunits in the MCI clock domain (MCLK) are resynchronized.
Depending on TxActive and RxActive, the FIFO can be disabled, transmit enabled, or
receive enabled. TxActive and RxActive are driven by the data path subunit and are
mutually exclusive:
• The transmit FIFO refers to the transmit logic and data buffer when TxActive is
asserted (see Section 20.6.3.14 “Transmit FIFO”)

• The receive FIFO refers to the receive logic and data buffer when RxActive is
asserted (see Section 20.6.3.15 “Receive FIFO”).
20.6.3.14 Transmit FIFO

Data can be written to the transmit FIFO through the APB interface once the MCI is
enabled for transmission.
The transmit FIFO is accessible via 16 sequential addresses (see Section 20.7.16 “Data
FIFO Register (MCIFIFO - 0xE008 C080 to 0xE008 C0BC)”). The transmit FIFO contains
a data output register that holds the data word pointed to by the read pointer. When the
data path subunit has loaded its shift register, it increments the read pointer and drives
new data out.
If the transmit FIFO is disabled, all status flags are deasserted. The data path subunit
asserts TxActive when it transmits data. Table 417 lists the transmit FIFO status flags.
Table 417. Transmit FIFO status flags

Flag Description
TxFifoFull Set to HIGH when all 16 transmit FIFO words contain valid data.
TxFifoEmpty Set to HIGH when the transmit FIFO does not contain valid data.
TxHalfEmpty Set to HIGH when 8 or more transmit FIFO words are empty. This flag
can be used as a DMA request.
TxDataAvlbl Set to HIGH when the transmit FIFO contains valid data. This flag is the
inverse of the TxFifoEmpty flag.
TxUnderrun Set to HIGH when an underrun error occurs. This flag is cleared by
writing to the MCIClear register.
20.6.3.15 Receive FIFO

When the data path subunit receives a word of data, it drives data on the write data bus
and asserts the write enable signal. This signal is synchronized to the PCLK domain. The
write pointer is incremented after the write is completed, and the receive FIFO control
logic asserts RxWrDone, that then deasserts the write enable signal.
On the read side, the content of the FIFO word pointed to by the current value of the read
pointer is driven on the read data bus. The read pointer is incremented when the APB bus
interface asserts RxRdPrtInc.
If the receive FIFO is disabled, all status flags are deasserted, and the read and write
pointers are reset. The data path subunit asserts RxActive when it receives data. Table
353 lists the receive FIFO status flags.
The receive FIFO is accessible via 16 sequential addresses (see Section 20.7.16 “Data
FIFO Register (MCIFIFO - 0xE008 C080 to 0xE008 C0BC)”).
If the receive FIFO is disabled, all status flags are deasserted, and the read and write
pointers are reset. The data path subunit asserts RxActive when it receives data.
Table 418 lists the receive FIFO status flags.

Table 418. Receive FIFO status flags

Symbol Description
RxFifoFull Set to HIGH when all 16 receive FIFO words contain valid data.
RxFifoEmpty Set to HIGH when the receive FIFO does not contain valid data.
RxHalfFull Set to HIGH when 8 or more receive FIFO words contain valid data. This
flag can be used as a DMA request.
RxDataAvlbl Set to HIGH when the receive FIFO is not empty. This flag is the inverse
of the RxFifoEmpty flag.
RxOverrun Set to HIGH when an overrun error occurs. This flag is cleared by writing
to the MCIClear register.
20.6.3.16 APB interfaces

The APB interface generates the interrupt and DMA requests, and accesses the MCI
adapter registers and the data FIFO. It consists of a data path, register decoder, and
interrupt/DMA logic. DMA is controlled by the General Purpose DMA controller, see that
chapter for details.
20.6.3.17 Interrupt logic

The interrupt logic generates an interrupt request signal that is asserted when at least one
of the selected status flags is HIGH. A mask register is provided to allow selection of the
conditions that will generate an interrupt. A status flag generates the interrupt request if a
corresponding mask flag is set.

This section describes the MCI registers and provides programming details.
20.7.1 Summary of MCI Registers

The MCI registers are shown in Table 419.
Table 419. SPI register map

Name Description Access Width Reset Address
Value[1]
MCIPower Power control register. R/W 8 0x00 0xE008 C000
MCIClock Clock control register. R/W 12 0x000 0xE008 C004
MCIArgument Argument register. R/W 32 0x00000000 0xE008 C008
MMCCommand Command register. R/W 11 0x000 0xE008 C00C
MCIRespCmd Response command register. RO 6 0x00 0xE008 C010
MCIResponse0 Response register. RO 32 0x00000000 0xE008 C014
MCIResponse2 Response register. RO 32 0x00000000 0xE008 C01C
MCIDataTimer Data Timer. R/W 32 0x00000000 0xE008 C024
MCIDataLength Data control register. R/W 16 0x0000 0xE008 C028
MCIDataCtrl Data control register. R/W 8 0x00 0xE008 C02C
MCIDataCnt Data counter. RO 16 0x0000 0xE008 C030

Table 419. SPI register map

Name Description Access Width Reset Address
Value[1]
MCIStatus Status register. RO 22 0x000000 0xE008 C034
MCIClear Clear register. WO 11 - 0xE008 C038
MCIMask0 Interrupt 0 mask register. R/W 22 0x000000 0xE008 C03C
MCIFifoCnt FIFO Counter. RO 15 0x0000 0xE008 C048
MCIFIFO Data FIFO Register. R/W 32 0x00000000 0xE008 C080
to
0xE008 C0BC
20.7.2 Power Control Register (MCI Power - 0xE008 C000)

The MCIPower register controls an external power supply. Power can be switched on and
off, and adjust the output voltage. Table 420 shows the bit assignment of the MCIPower
register.
The active level of the MCIPWR (Power Supply Enable) pin can be selected by bit 3 of the
SCS register (see Section 3.7.2 “System Controls and Status register (SCS - 0xE01F
C1A0)” on page 42 for details).
Table 420: Power Control register (MCIPower - address 0xE008 C000) bit description
Value
1:0 Ctrl 00 Power-off 00
01 Reserved
10 Power-up
11 Power-on
defined.
6 OpenDrain MCICMD output control. 0
7 Rod Rod control. 0
defined.
When the external power supply is switched on, the software first enters the power-up
phase, and waits until the supply output is stable before moving to the power-on phase.
During the power-up phase, MCIPWR is set HIGH. The card bus outlets are disabled
during both phases.
Note: After a data write, data cannot be written to this register for three MCLK clock
periods plus two PCLK clock periods.
20.7.3 Clock Control Register (MCIClock - 0xE008 C004)

The MCIClock register controls the MCICLK output. Table 421 shows the bit assignment
of the clock control register.

Table 421: Clock Control register (MCIClock - address 0xE008 C004) bit description
Value
7:0 ClkDiv MCI bus clock period: 0x00
MCLCLK frequency = MCLK / [2(ClkDiv+1)].
8 Enable Enable MCI bus clock: 0
0 Clock disabled.
1 Clock enabled.
9 PwrSave Disable MCI clock output when bus is idle: 0
0 Always enabled.
1 Clock enabled when bus is active.
10 Bypass Enable bypass of clock divide logic: 0
0 Disable bypass.
1 Enable bypass. MCLK driven to card bus output (MCICLK).
11 WideBus Enable wide bus mode: 0
0 Standard bus mode (only MCIDAT0 used).
1 Wide bus mode (MCIDAT3:0 used)
While the MCI is in identification mode, the MCICLK frequency must be less than
400 kHz. The clock frequency can be changed to the maximum card bus frequency when
relative card addresses are assigned to all cards.
20.7.4 Argument Register (MCIArgument - 0xE008 C008)

The MCIArgument register contains a 32 bit command argument, which is sent to a card
as part of a command message. Table 422 shows the bit assignment of the MCIArgument
register.
Table 422: Argument register (MCIArgument - address 0xE008 C008) bit description
31:0 CmdArg Command argument 0x0000 0000
If a command contains an argument, it must be loaded into the argument register before
writing a command to the command register.
20.7.5 Command Register (MCICommand - 0xE008 C00C)

The MCICommand register contains the command index and command type bits:
• The command index is sent to a card as part of a command message.

• The command type bits control the Command Path State Machine (CPSM). Writing 1
to the enable bit starts the command send operation, while clearing the bit disables
the CPSM.
Table 423 shows the bit assignment of the MCICommand register.

Table 423: Command register (MCICommand - address 0xE008 C00C) bit description
Value
5:0 CmdIndex Command index. 0
6 Response If set, CPSM waits for a response. 0
7 LongRsp If set, CPSM receives a 136 bit long response. 0
8 Interrupt If set, CPSM disables command timer and waits for interrupt request. 0
9 Pending If set, CPSM waits for CmdPend before it starts sending a command. 0
10 Enable If set, CPSM is enabled. 0
Table 424 shows the response types.
Table 424: Command Response Types

Response Long Response Description
0 0 No response, expect CmdSent flag.
0 1 No response, expect CmdSent flag.
1 0 Short response, expect CmdRespEnd or CmdCrcFail flag.
1 1 Long response, expect CmdRespEnd or CmdCrcFail flag.
20.7.6 Command Response Register (MCIRespCommand - 0xE008 C010)

The MCIRespCommand register contains the command index field of the last command
response received. Table 423 shows the bit assignment of the MCIRespCommand
register.
Table 425: Command Response register (MCIRespCommand - address 0xE008 C010) bit
description
Value
5:0 RespCmd Response command index 0x00
If the command response transmission does not contain the command index field (long
response), the RespCmd field is unknown, although it must contain 111111 (the value of
the reserved field from the response).
20.7.7 Response Registers (MCIResponse0-3 - 0xE008 C014, E008 C018,

E008 C01C and E008 C020)
The MCIResponse0-3 registers contain the status of a card, which is part of the received
response. Table 426 shows the bit assignment of the MCIResponse0-3 registers.

Table 426: Response registers (MCIResponse0-3 - addresses 0xE008 0014, 0xE008 C018,
0xE008 001C and 0xE008 C020) bit description
31:0 Status Card status 0x0000 0000
The card status size can be 32 or 127 bits, depending on the response type (see
Table 427).
Table 427: Response Register Type

Description Short Response Long Response
MCIResponse0 Card status [31:0] Card status [127:96]
MCIResponse1 Unused Card status [95:64]
The most significant bit of the card status is received first. The MCIResponse3 register
LSBit is always 0.
20.7.8 Data Timer Register (MCIDataTimer - 0xE008 C024)

The MCIDataTimer register contains the data time-out period, in card bus clock periods.
Table 428 shows the bit assignment of the MCIDataTimer register.
Table 428: Data Timer register (MCIDataTimer - address 0xE008 C024) bit description
31:0 DataTime Data timeout period. 0x0000 0000
A counter loads the value from the data timer register, and starts decrementing when the
Data Path State Machine (DPSM) enters the WAIT_R or BUSY state. If the timer reaches
0 while the DPSM is in either of these states, the time-out status flag is set.
A data transfer must be written to the data timer register and the data length register
before being written to the data control register.
20.7.9 Data Length Register (MCIDataLength - 0xE008 C028)

The MCIDataLength register contains the number of data bytes to be transferred. The
value is loaded into the data counter when data transfer starts. Table 429 shows the bit
assignment of the MCIDataLength register.
Table 429: Data Length register (MCIDataLength - address 0xE008 C028) bit description
Value
15:0 DataLength Data length value 0x0000
For a block data transfer, the value in the data length register must be a multiple of the
block size (see Section 20.7.10 “Data Control Register (MCIDataCtrl - 0xE008 C02C)”).
To initiate a data transfer, write to the data timer register and the data length register
before writing to the data control register.

20.7.10 Data Control Register (MCIDataCtrl - 0xE008 C02C)

The MCIDataCtrl register controls the DPSM. Table 430 shows the bit assignment of the
MCIDataCtrl register.
Table 430: Data Control register (MCIDataCtrl - address 0xE008 C02C) bit description
Value
0 Enable Data transfer enable. 0
1 Direction Data transfer direction: 0
0 From controller to card.
1 From card to controller.
2 Mode Data transfer mode: 0
0 Block data transfer.
1 Stream data transfer.
3 DMAEnable Enable DMA: 0
0 DMA disabled.
1 DMA enabled.
7:4 BlockSize Data block length 0
Data transfer starts if 1 is written to the enable bit. Depending on the direction bit, the
DPSM moves to the WAIT_S or WAIT_R state. It is not necessary to clear the enable bit
after the data transfer. BlockSize controls the data block length if Mode is 0, as shown in
Table 431.
Table 431: Data Block Length

Block Size Block Length
0 20= 1 byte.
1 21 = 2 bytes.
... -
11 211 = 2048 bytes.
12:15 Reserved.
20.7.11 Data Counter Register (MCIDataCnt - 0xE008 C030)

The MCIDataCnt register loads the value from the data length register (see Section 20.7.9
“Data Length Register (MCIDataLength - 0xE008 C028)”) when the DPSM moves from
the IDLE state to the WAIT_R or WAIT_S state. As data is transferred, the counter
decrements the value until it reaches 0. The DPSM then moves to the IDLE state and the
data status end flag is set. Table 432 shows the bit assignment of the MCIDataCnt
register.

Table 432: Data Counter register (MCIDataCnt - address 0xE008 C030) bit description
Value
15:0 DataCount Remaining data 0x0000
Note: This register should be read only when the data transfer is complete.
20.7.12 Status Register (MCIStatus - 0xE008 C034)

The MCIStatus register is a read-only register. It contains two types of flag:
• Static [10:0]: These remain asserted until they are cleared by writing to the Clear
register (see Section 20.7.13 “Clear Register (MCIClear - 0xE008 C038)”).
• Dynamic [21:11]: These change state depending on the state of the underlying logic
(for example, FIFO full and empty flags are asserted and deasserted as data while
written to the FIFO).
Table 433 shows the bit assignment of the MCIStatus register.
Table 433: Status register (MCIStatus - address 0xE008 C034) bit description
Value
0 CmdCrcFail Command response received (CRC check failed). 0
1 DataCrcFail Data block sent/received (CRC check failed). 0
2 CmdTimeOut Command response timeout. 0
3 DataTimeOut Data timeout. 0
4 TxUnderrun Transmit FIFO underrun error. 0
5 RxOverrun Receive FIFO overrun error. 0
6 CmdRespEnd Command response received (CRC check passed). 0
7 CmdSent Command sent (no response required). 0
8 DataEnd Data end (data counter is zero). 0
9 StartBitErr Start bit not detected on all data signals in wide bus mode. 0
10 DataBlockEnd Data block sent/received (CRC check passed). 0
11 CmdActive Command transfer in progress. 0
12 TxActive Data transmit in progress. 0
13 RxActive Data receive in progress. 0
14 TxFifoHalfEmpty Transmit FIFO half empty. 0
15 RxFifoHalfFull Receive FIFO half full. 0
16 TxFifoFull Transmit FIFO full. 0
17 RxFifoFull Receive FIFO full. 0
18 TxFifoEmpty Transmit FIFO empty. 0
19 RxFifoEmpty Receive FIFO empty. 0

Table 433: Status register (MCIStatus - address 0xE008 C034) bit description
Value
20 TxDataAvlbl Data available in transmit FIFO. 0
21 RxDataAvlbl Data available in receive FIFO. 0
20.7.13 Clear Register (MCIClear - 0xE008 C038)

The MCIClear register is a write-only register. The corresponding static status flags can be
cleared by writing a 1 to the corresponding bit in the register. Table 434 shows the bit
assignment of the MCIClear register.
Table 434: Clear register (MCIClear - address 0xE008 C038) bit description
Value
0 CmdCrcFailClr Clears CmdCrcFail flag. -
1 DataCrcFailClr Clears DataCrcFail flag. -
2 CmdTimeOutClr Clears CmdTimeOut flag. -
3 DataTimeOutClr Clears DataTimeOut flag. -
4 TxUnderrunClr Clears TxUnderrun flag. -
5 RxOverrunClr Clears RxOverrun flag. -
6 CmdRespEndClr Clears CmdRespEnd flag. -
7 CmdSentClr Clears CmdSent flag. -
8 DataEndClr Clears DataEnd flag. -
9 StartBitErrClr Clears StartBitErr flag. -
10 DataBlockEndClr Clears DataBlockEnd flag. -
20.7.14 Interrupt Mask Registers (MCIMask0 - 0xE008 C03C)

The interrupt mask registers determine which status flags generate an interrupt request by
setting the corresponding bit to 1. Table 435 shows the bit assignment of the MCIMaskx
registers.
Table 435: Interrupt Mask registers (MCIMask0 - address 0xE008 C03C) bit description
Value
0 Mask0 Mask CmdCrcFail flag. 0
1 Mask1 Mask DataCrcFail flag. 0
2 Mask2 Mask CmdTimeOut flag. 0
3 Mask3 Mask DataTimeOut flag. 0
4 Mask4 Mask TxUnderrun flag. 0
5 Mask5 Mask RxOverrun flag. 0
6 Mask6 Mask CmdRespEnd flag. 0
7 Mask7 Mask CmdSent flag. 0

Table 435: Interrupt Mask registers (MCIMask0 - address 0xE008 C03C) bit description
Value
8 Mask8 Mask DataEnd flag. 0
9 Mask9 Mask StartBitErr flag. 0
10 Mask10 Mask DataBlockEnd flag. 0
11 Mask11 Mask CmdActive flag. 0
12 Mask12 Mask TxActive flag. 0
13 Mask13 Mask RxActive flag. 0
14 Mask14 Mask TxFifoHalfEmpty flag. 0
15 Mask15 Mask RxFifoHalfFull flag. 0
16 Mask16 Mask TxFifoFull flag. 0
17 Mask17 Mask RxFifoFull flag. 0
18 Mask18 Mask TxFifoEmpty flag. 0
19 Mask19 Mask RxFifoEmpty flag. 0
20 Mask20 Mask TxDataAvlbl flag. 0
21 Mask21 Mask RxDataAvlbl flag. 0
20.7.15 FIFO Counter Register (MCIFifoCnt - 0xE008 C048)

The MCIFifoCnt register contains the remaining number of words to be written to or read
from the FIFO. The FIFO counter loads the value from the data length register (see
Section 20.7.9 “Data Length Register (MCIDataLength - 0xE008 C028)”) when the Enable
bit is set in the data control register. If the data length is not word aligned (multiple of 4),
the remaining 1 to 3 bytes are regarded as a word. Table 436 shows the bit assignment of
the MCIFifoCnt register.
Table 436: FIFO Counter register (MCIFifoCnt - address 0xE008 C048) bit description
Value
14:0 DataCount Remaining data 0x0000
20.7.16 Data FIFO Register (MCIFIFO - 0xE008 C080 to 0xE008 C0BC)

The receive and transmit FIFOs can be read or written as 32 bit wide registers. The FIFOs
contain 16 entries on 16 sequential addresses. This allows the microprocessor to use its
load and store multiple operands to read/write to the FIFO. Table 437 shows the bit
assignment of the MCIFIFO register.
Table 437: Data FIFO register (MCIFIFO - address 0xE008 C080 to 0xE008 C0BC) bit
description
31:0 Data FIFO data. 0x0000 0000

UM10211
Chapter 21: LPC23XX I2C-bus interfaces I2C0/1/2

The I2C0/1/2 interfaces are configured using the following registers:
1. Power: In the PCONP register (Table 56), set bit PCI2C0/1/2.

Remark: On reset, all I2C interfaces are enabled (PCI2C0/1/2 = 1).
2. Clock: In PCLK_SEL0 select PCLK_I2C0; in PCLK_SEL1 select PCLK_I2C1/2 (see
Section 4.7.4.
3. Pins: Select I2C pins and their modes in PINSEL0 to PINSEL4 and PINMODE0 to
Remark: I2C0 pins SDA0 and SCL0 are open-drain outputs for I2C-bus compliance
(see Section 9.5.13).
4. Interrupts are enabled in the VIC using the VICIntEnable register (Table 76).
5. Initialization: see Section 21.9.12.1 and Section 21.10.1.
21.2 Features
• Standard I2C compliant bus interfaces that may be configured as Master, Slave, or
Master/Slave.
• Arbitration between simultaneously transmitting masters without corruption of serial
data on the bus.
• Programmable clock to allow adjustment of I2C transfer rates.
• Bidirectional data transfer between masters and slaves.
• Serial clock synchronization allows devices with different bit rates to communicate via
one serial bus.
• Serial clock synchronization can be used as a handshake mechanism to suspend and
resume serial transfer.
• The I2C bus may be used for test and diagnostic purposes.
21.3 Applications
Interfaces to external I2C standard parts, such as serial RAMs, LCDs, tone generators,
etc.
21.4 Description
A typical I2C bus configuration is shown in Figure 107. Depending on the state of the
direction bit (R/W), two types of data transfers are possible on the I2C bus:
• Data transfer from a master transmitter to a slave receiver. The first byte transmitted
by the master is the slave address. Next follows a number of data bytes. The slave
returns an acknowledge bit after each received byte.

• Data transfer from a slave transmitter to a master receiver. The first byte (the slave
address) is transmitted by the master. The slave then returns an acknowledge bit.
Next follows the data bytes transmitted by the slave to the master. The master returns
an acknowledge bit after all received bytes other than the last byte. At the end of the
last received byte, a “not acknowledge” is returned. The master device generates all
of the serial clock pulses and the START and STOP conditions. A transfer is ended
with a STOP condition or with a repeated START condition. Since a repeated START
condition is also the beginning of the next serial transfer, the I2C bus will not be
released.
Each of the three I2C interfaces on the LPC2300 is byte oriented, and has four operating
modes: master transmitter mode, master receiver mode, slave transmitter mode and
slave receiver mode.
The three I2C interfaces are identical except for the pin I/O characteristics. I2C0 complies
with entire I2C specification, supporting the ability to turn power off to the LPC2300
without causing a problem with other devices on the same I2C bus (see "The I2C-bus
specification" description under the heading "Fast-Mode", and notes for the table titled
"Characteristics of the SDA and SCL I/O stages for F/S-mode I2C-bus devices"). This is
sometimes a useful capability, but intrinsically limits alternate uses for the same pins if the
I2C interface is not used. Seldom is this capability needed on multiple I2C interfaces
within the same microcontroller. Therefore, I2C1 and I2C2 are implemented using
standard port pins, and do not support the ability to turn power off to the LPC2300 while
leaving the I2C bus functioning between other devices. This difference should be
considered during system design while assigning uses for the I2C interfaces.
pull-up pull-up
resistor resistor
SDA
I 2C bus
SCL
SDA SCL
OTHER DEVICE WITH OTHER DEVICE WITH

LPC2300
I 2C INTERFACE I 2C INTERFACE
Fig 107. I2C bus configuration


Table 438. I2C Pin Description
SDA0,1, 2 Input/Output I2C Serial Data.
SCL0,1, 2 Input/Output I2C Serial Clock.
Remark: Only the I2C0 pins SDA0 and SCL0 are open-drain outputs for I2C-bus
compliance.
21.6 I2C operating modes

In a given application, the I2C block may operate as a master, a slave, or both. In the slave
mode, the I2C hardware looks for its own slave address and the general call address. If
one of these addresses is detected, an interrupt is requested. If the processor wishes to
become the bus master, the hardware waits until the bus is free before the master mode is
entered so that a possible slave operation is not interrupted. If bus arbitration is lost in the
master mode, the I2C block switches to the slave mode immediately and can detect its
own slave address in the same serial transfer.
21.6.1 Master Transmitter mode

In this mode data is transmitted from master to slave. Before the master transmitter mode
can be entered, the I2CONSET register must be initialized as shown in Table 439. I2EN
must be set to 1 to enable the I2C function. If the AA bit is 0, the I2C interface will not
acknowledge any address when another device is master of the bus, so it can not enter
slave mode. The STA, STO and SI bits must be 0. The SI Bit is cleared by writing 1 to the
SIC bit in the I2CONCLR register.
Table 439. I2CnCONSET used to configure Master mode

Bit 7 6 5 4 3 2 1 0
Symbol - I2EN STA STO SI AA - -
Value - 1 0 0 0 0 - -
The first byte transmitted contains the slave address of the receiving device (7 bits) and
the data direction bit. In this mode the data direction bit (R/W) should be 0 which means
Write. The first byte transmitted contains the slave address and Write bit. Data is
transmitted 8 bits at a time. After each byte is transmitted, an acknowledge bit is received.
START and STOP conditions are output to indicate the beginning and the end of a serial
transfer.
The I2C interface will enter master transmitter mode when software sets the STA bit. The
I2C logic will send the START condition as soon as the bus is free. After the START
condition is transmitted, the SI bit is set, and the status code in the I2STAT register is
0x08. This status code is used to vector to a state service routine which will load the slave
address and Write bit to the I2DAT register, and then clear the SI bit. SI is cleared by
writing a 1 to the SIC bit in the I2CONCLR register. The STA bit should be cleared after
writing the slave address.

When the slave address and R/W bit have been transmitted and an acknowledgment bit
has been received, the SI bit is set again, and the possible status codes now are 0x18,
0x20, or 0x38 for the master mode, or 0x68, 0x78, or 0xB0 if the slave mode was enabled
(by setting AA to 1). The appropriate actions to be taken for each of these status codes
are shown in Table 454 to Table 457.
S SLAVE ADDRESS RW A DATA A DATA A/A P
“0” - write
“1” - read data transferred
(n Bytes + Acknowledge)
A = Acknowledge (SDA low)

from Master to Slave
A = Not acknowledge (SDA high)
from Slave to Master
S = START condition
P = STOP condition
Fig 108. Format in the Master Transmitter mode
21.6.2 Master Receiver mode

In the master receiver mode, data is received from a slave transmitter. The transfer is
initiated in the same way as in the master transmitter mode. When the START condition
has been transmitted, the interrupt service routine must load the slave address and the
data direction bit to the I2C Data Register (I2DAT), and then clear the SI bit. In this case,
the data direction bit (R/W) should be 1 to indicate a read.
When the slave address and data direction bit have been transmitted and an
acknowledge bit has been received, the SI bit is set, and the Status Register will show the
status code. For master mode, the possible status codes are 0x40, 0x48, or 0x38. For
slave mode, the possible status codes are 0x68, 0x78, or 0xB0. For details, refer to
Table 455.
S SLAVE ADDRESS R A DATA A DATA A P
“0” - write

S = START condition
P = STOP condition
Fig 109. Format of Master Receive mode
After a repeated START condition, I2C may switch to the master transmitter mode.

S SLA R A DATA A DATA A RS SLA W A DATA A P
data transferred

From master to slave
From slave to master
S = START condition
P = STOP condition
SLA = Slave Address
Fig 110. A master receiver switch to master Transmitter after sending repeated START
21.6.3 Slave Receiver mode

In the slave receiver mode, data bytes are received from a master transmitter. To initialize
the slave receiver mode, user write the Slave Address Register (I2ADR) and write the I2C
Control Set Register (I2CONSET) as shown in Table 440.
Table 440. I2CnCONSET used to configure Slave mode

Bit 7 6 5 4 3 2 1 0
Value - 1 0 0 0 1 - -
I2EN must be set to 1 to enable the I2C function. AA bit must be set to 1 to acknowledge
its own slave address or the general call address. The STA, STO and SI bits are set to 0.
After I2ADR and I2CONSET are initialized, the I2C interface waits until it is addressed by
its own address or general address followed by the data direction bit. If the direction bit is
0 (W), it enters slave receiver mode. If the direction bit is 1 (R), it enters slave transmitter
mode. After the address and direction bit have been received, the SI bit is set and a valid
status code can be read from the Status Register (I2STAT). Refer to Table 456 for the
status codes and actions.
S SLAVE ADDRESS W A DATA A DATA A/A P/RS
“0” - write

S = START condition
P = STOP condition
RS = Repeated START condition
Fig 111. Format of Slave Receiver mode

21.6.4 Slave Transmitter mode

The first byte is received and handled as in the slave receiver mode. However, in this
mode, the direction bit will be 1, indicating a read operation. Serial data is transmitted via
SDA while the serial clock is input through SCL. START and STOP conditions are
recognized as the beginning and end of a serial transfer. In a given application, I2C may
operate as a master and as a slave. In the slave mode, the I2C hardware looks for its own
slave address and the general call address. If one of these addresses is detected, an
interrupt is requested. When the microcontrollers wishes to become the bus master, the
hardware waits until the bus is free before the master mode is entered so that a possible
slave action is not interrupted. If bus arbitration is lost in the master mode, the I2C
interface switches to the slave mode immediately and can detect its own slave address in
the same serial transfer.
S SLAVE ADDRESS R A DATA A DATA A P
“0” - write

S = START condition
P = STOP condition
Fig 112. Format of Slave Transmitter mode
21.7 I2C implementation and operation
21.7.1 Input filters and output stages

Input signals are synchronized with the internal clock , and spikes shorter than three
clocks are filtered out.
The output for I2C is a special pad designed to conform to the I2C specification. The
outputs for I2C1 and I2C2 are standard port I/Os that support a subset of the full I2C
specification.
Figure 113 shows how the on-chip I2C bus interface is implemented, and the following text
describes the individual blocks.

ADDRESS REGISTER I2ADR
INPUT COMPARATOR
FILTER
SDA
OUTPUT
SHIFT REGISTER ACK
STAGE
I2DAT
8
APB BUS
BIT COUNTER/
ARBITRATION &
SYNC LOGIC PCLK
INPUT
FILTER TIMING &
CONTROL
LOGIC
SCL
interrupt
OUTPUT SERIAL CLOCK
STAGE GENERATOR
I2CONSET
I2CONCLR CONTROL REGISTER & SCL DUTY
I2SCLH CYCLE REGISTERS
I2SCLL
16
status STATUS
STATUS REGISTER
bus DECODER
I2STAT
8
Fig 113. I2C Bus serial interface block diagram

21.7.2 Address Register I2ADDR

This register may be loaded with the 7 bit slave address (7 most significant bits) to which
the I2C block will respond when programmed as a slave transmitter or receiver. The LSB
(GC) is used to enable general call address (0x00) recognition.
21.7.3 Comparator
The comparator compares the received 7 bit slave address with its own slave address (7
most significant bits in I2ADR). It also compares the first received 8 bit byte with the
general call address (0x00). If an equality is found, the appropriate status bits are set and
an interrupt is requested.
21.7.4 Shift register I2DAT

This 8 bit register contains a byte of serial data to be transmitted or a byte which has just
been received. Data in I2DAT is always shifted from right to left; the first bit to be
transmitted is the MSB (bit 7) and, after a byte has been received, the first bit of received
data is located at the MSB of I2DAT. While data is being shifted out, data on the bus is
simultaneously being shifted in; I2DAT always contains the last byte present on the bus.
Thus, in the event of lost arbitration, the transition from master transmitter to slave
receiver is made with the correct data in I2DAT.
21.7.5 Arbitration and synchronization logic

In the master transmitter mode, the arbitration logic checks that every transmitted logic 1
actually appears as a logic 1 on the I2C bus. If another device on the bus overrules a logic
1 and pulls the SDA line low, arbitration is lost, and the I2C block immediately changes
from master transmitter to slave receiver. The I2C block will continue to output clock
pulses (on SCL) until transmission of the current serial byte is complete.
Arbitration may also be lost in the master receiver mode. Loss of arbitration in this mode
can only occur while the I2C block is returning a “not acknowledge: (logic 1) to the bus.
Arbitration is lost when another device on the bus pulls this signal LOW. Since this can
occur only at the end of a serial byte, the I2C block generates no further clock pulses.
Figure 114 shows the arbitration procedure.
(1) (1) (2) (3)

SDA line
SCL line
1 2 3 4 8 9
ACK
(1) A device transmits serial data.

(2) Another device overrules a logic 1 (dotted line), transmitted by this I2C master, by pulling the SDA
line low. Arbitration is lost, and this I2C enters Slave Receiver mode.
(3) This I2C is in Slave Receiver mode but still generates clock pulses until the current byte has been
transmitted. This I2C will not generate clock pulses for the next byte. Data on SDA originates from
the new master once it has won arbitration.
Fig 114. Arbitration procedure

The synchronization logic will synchronize the serial clock generator with the clock pulses
on the SCL line from another device. If two or more master devices generate clock pulses,
the “mark” duration is determined by the device that generates the shortest “marks,” and
the “space” duration is determined by the device that generates the longest “spaces”.
Figure 115 shows the synchronization procedure.
SDA line
(1) (3) (1)
SCL line
(2)
high low
period period
(1) Another device pulls the SCL line low before this I2C has timed a complete high time. The other
device effectively determines the (shorter) HIGH period.
(2) Another device continues to pull the SCL line low after this I2C has timed a complete low time and
released SCL. The I2C clock generator is forced to wait until SCL goes HIGH. The other device
effectively determines the (longer) LOW period.
(3) The SCL line is released , and the clock generator begins timing the HIGH time.
Fig 115. Serial clock synchronization
A slave may stretch the space duration to slow down the bus master. The space duration
may also be stretched for handshaking purposes. This can be done after each bit or after
a complete byte transfer. the I2C block will stretch the SCL space duration after a byte has
been transmitted or received and the acknowledge bit has been transferred. The serial
interrupt flag (SI) is set, and the stretching continues until the serial interrupt flag is
cleared.
21.7.6 Serial clock generator

This programmable clock pulse generator provides the SCL clock pulses when the I2C
block is in the master transmitter or master receiver mode. It is switched off when the I2C
block is in a slave mode. The I2C output clock frequency and duty cycle is programmable
via the I2C Clock Control Registers. See the description of the I2CSCLL and I2CSCLH
registers for details. The output clock pulses have a duty cycle as programmed unless the
bus is synchronizing with other SCL clock sources as described above.
21.7.7 Timing and control

The timing and control logic generates the timing and control signals for serial byte
handling. This logic block provides the shift pulses for I2DAT, enables the comparator,
generates and detects start and stop conditions, receives and transmits acknowledge bits,
controls the master and slave modes, contains interrupt request logic, and monitors the
I2C bus status.
21.7.8 Control register I2CONSET and I2CONCLR

The I2C control register contains bits used to control the following I2C block functions: start
and restart of a serial transfer, termination of a serial transfer, bit rate, address recognition,
and acknowledgment.

The contents of the I2C control register may be read as I2CONSET. Writing to I2CONSET
will set bits in the I2C control register that correspond to ones in the value written.
Conversely, writing to I2CONCLR will clear bits in the I2C control register that correspond
to ones in the value written.
21.7.9 Status decoder and status register

The status decoder takes all of the internal status bits and compresses them into a 5 bit
code. This code is unique for each I2C bus status. The 5 bit code may be used to generate
vector addresses for fast processing of the various service routines. Each service routine
processes a particular bus status. There are 26 possible bus states if all four modes of the
I2C block are used. The 5 bit status code is latched into the five most significant bits of the
status register when the serial interrupt flag is set (by hardware) and remains stable until
the interrupt flag is cleared by software. The three least significant bits of the status
register are always zero. If the status code is used as a vector to service routines, then the
routines are displaced by eight address locations. Eight bytes of code is sufficient for most
of the service routines (see the software example in this section).

Each I2C interface contains 7 registers as shown in Table 441 below.
Table 441. I2C register map

Generic Description Access Reset I2Cn Register
Name value[1] Name & Address
I2CONSET I2C Control Set Register. When a one is written to a R/W 0x00 I2C0CONSET - 0xE001 C000
bit of this register, the corresponding bit in the I2C I2C1CONSET - 0xE005 C000
control register is set. Writing a zero has no effect on I2C2CONSET - 0xE008 0000
the corresponding bit in the I2C control register.
I2STAT I2C Status Register. During I2C operation, this RO 0xF8 I2C0STAT - 0xE001 C004
register provides detailed status codes that allow I2C1STAT - 0xE005 C004
software to determine the next action needed. I2C2STAT - 0xE008 0004
I2DAT I2C Data Register. During master or slave transmit R/W 0x00 I2C0DAT - 0xE001 C008
mode, data to be transmitted is written to this register. I2C1DAT - 0xE005 C008
During master or slave receive mode, data that has I2C2DAT - 0xE008 0008
been received may be read from this register.
I2ADR I2C Slave Address Register. Contains the 7 bit slave R/W 0x00 I2C0ADR - 0xE001 C00C
address for operation of the I2C interface in slave I2C1ADR - 0xE005 C00C
mode, and is not used in master mode. The least I2C2ADR - 0xE008 000C
significant bit determines whether a slave responds to
the general call address.

Table 441. I2C register map

Generic Description Access Reset I2Cn Register
Name value[1] Name & Address
I2SCLH SCH Duty Cycle Register High Half Word. R/W 0x04 I2C0SCLH - 0xE001 C010
Determines the high time of the I2C clock. I2C1SCLH - 0xE005 C010
I2C2SCLH - 0xE008 0010
I2SCLL SCL Duty Cycle Register Low Half Word. R/W 0x04 I2C0SCLL - 0xE001 C014
Determines the low time of the I2C clock. I2nSCLL I2C1SCLL - 0xE005 C014
and I2nSCLH together determine the clock frequency I2C2SCLL - 0xE008 0014
generated by an I2C master and certain times used in
slave mode.
I2CONCLR I2C Control Clear Register. When a one is written to WO NA I2C0CONCLR - 0xE001 C018
a bit of this register, the corresponding bit in the I2C I2C1CONCLR - 0xE005 C018
control register is cleared. Writing a zero has no effect I2C2CONCLR - 0xE008 0018
on the corresponding bit in the I2C control register.
21.8.1 I2C Control Set Register (I2C[0/1/2]CONSET: 0xE001 C000,

0xE005 C000, 0xE008 0000)
The I2CONSET registers control setting of bits in the I2CON register that controls
operation of the I2C interface. Writing a one to a bit of this register causes the
corresponding bit in the I2C control register to be set. Writing a zero has no effect.
Table 442. I2C Control Set Register (I2C[0/1/2]CONSET - addresses: 0xE001 C000,
0xE005 C000, 0xE008 0000) bit description
Value
1:0 - Reserved. User software should not write ones to reserved bits. The NA
2 AA Assert acknowledge flag. See the text below.
3 SI I2C interrupt flag. 0
4 STO STOP flag. See the text below. 0
5 STA START flag. See the text below. 0
6 I2EN I2C interface enable. See the text below. 0
7 - Reserved. User software should not write ones to reserved bits. The NA
I2EN I2C Interface Enable. When I2EN is 1, the I2C interface is enabled. I2EN can be
cleared by writing 1 to the I2ENC bit in the I2CONCLR register. When I2EN is 0, the I2C
interface is disabled.
When I2EN is “0”, the SDA and SCL input signals are ignored, the I2C block is in the “not
addressed” slave state, and the STO bit is forced to “0”.
I2EN should not be used to temporarily release the I2C bus since, when I2EN is reset, the
I2C bus status is lost. The AA flag should be used instead.
STA is the START flag. Setting this bit causes the I2C interface to enter master mode and
transmit a START condition or transmit a repeated START condition if it is already in
master mode.

When STA is 1 and the I2C interface is not already in master mode, it enters master mode,
checks the bus and generates a START condition if the bus is free. If the bus is not free, it
waits for a STOP condition (which will free the bus) and generates a START condition
after a delay of a half clock period of the internal clock generator. If the I2C interface is
already in master mode and data has been transmitted or received, it transmits a repeated
START condition. STA may be set at any time, including when the I2C interface is in an
addressed slave mode.
STA can be cleared by writing 1 to the STAC bit in the I2CONCLR register. When STA is
0, no START condition or repeated START condition will be generated.
If STA and STO are both set, then a STOP condition is transmitted on the I2C bus if it the
interface is in master mode, and transmits a START condition thereafter. If the I2C
interface is in slave mode, an internal STOP condition is generated, but is not transmitted
on the bus.
STO is the STOP flag. Setting this bit causes the I2C interface to transmit a STOP
condition in master mode, or recover from an error condition in slave mode. When STO is
1 in master mode, a STOP condition is transmitted on the I2C bus. When the bus detects
the STOP condition, STO is cleared automatically.
In slave mode, setting this bit can recover from an error condition. In this case, no STOP
condition is transmitted to the bus. The hardware behaves as if a STOP condition has
been received and it switches to “not addressed” slave receiver mode. The STO flag is
cleared by hardware automatically.
SI is the I2C Interrupt Flag. This bit is set when the I2C state changes. However, entering
state F8 does not set SI since there is nothing for an interrupt service routine to do in that
case.
While SI is set, the low period of the serial clock on the SCL line is stretched, and the
serial transfer is suspended. When SCL is high, it is unaffected by the state of the SI flag.
SI must be reset by software, by writing a 1 to the SIC bit in I2CONCLR register.
AA is the Assert Acknowledge Flag. When set to 1, an acknowledge (low level to SDA)
will be returned during the acknowledge clock pulse on the SCL line on the following
situations:
1. The address in the Slave Address Register has been received.

2. The general call address has been received while the general call bit (GC) in I2ADR is
set.
3. A data byte has been received while the I2C is in the master receiver mode.
4. A data byte has been received while the I2C is in the addressed slave receiver mode.
The AA bit can be cleared by writing 1 to the AAC bit in the I2CONCLR register. When AA
is 0, a not acknowledge (high level to SDA) will be returned during the acknowledge clock
pulse on the SCL line on the following situations:
1. A data byte has been received while the I2C is in the master receiver mode.
2. A data byte has been received while the I2C is in the addressed slave receiver mode.

21.8.2 I2C Control Clear Register (I2C[0/1/2]CONCLR: 0xE001 C018,

0xE005 C018, 0xE008 0018)
The I2CONCLR registers control clearing of bits in the I2CON register that controls
operation of the I2C interface. Writing a one to a bit of this register causes the
corresponding bit in the I2C control register to be cleared. Writing a zero has no effect.
Table 443. I2C Control Set Register (I2C[0/1/2]CONCLR - addresses 0xE001 C018,
Value
1:0 - Reserved. User software should not write ones to reserved bits. The NA
2 AAC Assert acknowledge Clear bit.
3 SIC I2C interrupt Clear bit. 0
5 STAC START flag Clear bit. 0
6 I2ENC I2C interface Disable bit. 0
AAC is the Assert Acknowledge Clear bit. Writing a 1 to this bit clears the AA bit in the
I2CONSET register. Writing 0 has no effect.
SIC is the I2C Interrupt Clear bit. Writing a 1 to this bit clears the SI bit in the I2CONSET
register. Writing 0 has no effect.
STAC is the Start flag Clear bit. Writing a 1 to this bit clears the STA bit in the I2CONSET
register. Writing 0 has no effect.
I2ENC is the I2C Interface Disable bit. Writing a 1 to this bit clears the I2EN bit in the
I2CONSET register. Writing 0 has no effect.
21.8.3 I2C Status Register (I2C[0/1/2]STAT - 0xE001 C004, 0xE005 C004,

0xE008 0004)
Each I2C Status register reflects the condition of the corresponding I2C interface. The I2C
Status register is Read-Only.
Table 444. I2C Status Register (I2C[0/1/2]STAT - addresses 0xE001 C004, 0xE005 C004,
2:0 - These bits are unused and are always 0. 0
7:3 Status These bits give the actual status information about the I2C interface. 0x1F
The three least significant bits are always 0. Taken as a byte, the status register contents
represent a status code. There are 26 possible status codes. When the status code is
0xF8, there is no relevant information available and the SI bit is not set. All other 25 status
codes correspond to defined I2C states. When any of these states entered, the SI bit will
be set. For a complete list of status codes, refer to tables from Table 454 to Table 457.

21.8.4 I2C Data Register (I2C[0/1/2]DAT - 0xE001 C008, 0xE005 C008,

0xE008 0008)
This register contains the data to be transmitted or the data just received. The CPU can
read and write to this register only while it is not in the process of shifting a byte, when the
SI bit is set. Data in I2DAT remains stable as long as the SI bit is set. Data in I2DAT is
always shifted from right to left: the first bit to be transmitted is the MSB (bit 7), and after a
byte has been received, the first bit of received data is located at the MSB of I2DAT.
Table 445. I2C Data Register ( I2C[0/1/2]DAT - addresses 0xE001 C008, 0xE005 C008,
7:0 Data This register holds data values that have been received, or are to 0
be transmitted.
21.8.5 I2C Slave Address Register (I2C[0/1/2]ADR - 0xE001 C00C,

0xE005 C00C, 0xE008 000C)
These registers are readable and writable, and is only used when an I2C interface is set to
slave mode. In master mode, this register has no effect. The LSB of I2ADR is the general
call bit. When this bit is set, the general call address (0x00) is recognized.
Table 446. I2C Slave Address register (I2C[0/1/2]ADR - addresses 0xE001 C00C,
0xE005 C00C, 0xE008 000C) bit description
0 GC General Call enable bit. 0
7:1 Address The I2C device address for slave mode. 0x00
21.8.6 I2C SCL High Duty Cycle Register (I2C[0/1/2]SCLH - 0xE001 C010,
0xE005 C010, 0xE008 0010)
Table 447. I2C SCL High Duty Cycle register (I2C[0/1/2]SCLH - addresses 0xE001 C010,
15:0 SCLH Count for SCL HIGH time period selection. 0x0004
21.8.7 I2C SCL Low Duty Cycle Register (I2C[0/1/2]SCLL - 0xE001 C014,
0xE005 C014, 0xE008 0014)
Table 448. I2C SCL Low Duty Cycle register (I2C[0/1/2]SCLL - addresses 0xE001 C014,
15:0 SCLL Count for SCL LOW time period selection. 0x0004
21.8.8 Selecting the appropriate I2C data rate and duty cycle
Software must set values for the registers I2SCLH and I2SCLL to select the appropriate
data rate and duty cycle. I2SCLH defines the number of PCLK cycles for the SCL high
time, I2SCLL defines the number of PCLK cycles for the SCL low time. The frequency is
determined by the following formula (fPCLK being the frequency of PCLK):

(13)
f PCLK
I 2 C bitfrequency = ---------------------------------------------------------
I2CSCLH + I2CSCLL
The values for I2SCLL and I2SCLH should not necessarily be the same. Software can set
different duty cycles on SCL by setting these two registers. For example, the I2C bus
specification defines the SCL low time and high time at different values for a 400 kHz I2C
rate. The value of the register must ensure that the data rate is in the I2C data rate range
of 0 through 400 kHz. Each register value must be greater than or equal to 4. Table 449
gives some examples of I2C bus rates based on PCLK frequency and I2SCLL and
I2SCLH values.
Table 449. Example I2C Clock Rates

I2SCLL + I2C Bit Frequency (kHz) at PCLK (MHz)
I2SCLH 1 5 10 16 20 40 60
8 125
10 100
25 40 200 400
50 20 100 200 320 400
100 10 50 100 160 200 400
160 6.25 31.25 62.5 100 125 250 375
200 5 25 50 80 100 200 300
400 2.5 12.5 25 40 50 100 150
800 1.25 6.25 12.5 20 25 50 75
21.9 Details of I2C operating modes

The four operating modes are:
• Master Transmitter
• Master Receiver
• Slave Receiver
• Slave Transmitter
Data transfers in each mode of operation are shown in Figures 116 to 120. Table 450 lists
abbreviations used in these figures when describing the I2C operating modes.
Table 450. Abbreviations used to describe an I2C operation

Abbreviation Explanation
S Start Condition
SLA 7 bit slave address
R Read bit (high level at SDA)
W Write bit (low level at SDA)
A Acknowledge bit (low level at SDA)

Table 450. Abbreviations used to describe an I2C operation

Abbreviation Explanation
A Not acknowledge bit (high level at SDA)
Data 8 bit data byte
P Stop condition
In Figures 116 to 120, circles are used to indicate when the serial interrupt flag is set. The
numbers in the circles show the status code held in the I2STAT register. At these points, a
service routine must be executed to continue or complete the serial transfer. These
service routines are not critical since the serial transfer is suspended until the serial
interrupt flag is cleared by software.
When a serial interrupt routine is entered, the status code in I2STAT is used to branch to
the appropriate service routine. For each status code, the required software action and
details of the following serial transfer are given in tables from Table 454 to Table 458.
21.9.1 Master Transmitter mode

In the master transmitter mode, a number of data bytes are transmitted to a slave receiver
(see Figure 116). Before the master transmitter mode can be entered, I2CON must be
initialized as follows:
Table 451. I2CONSET used to initialize Master Transmitter mode

Bit 7 6 5 4 3 2 1 0
Value - 1 0 0 0 x - -
The I2C rate must also be configured in the I2SCLL and I2SCLH registers. I2EN must be
set to logic 1 to enable the I2C block. If the AA bit is reset, the I2C block will not
acknowledge its own slave address or the general call address in the event of another
device becoming master of the bus. In other words, if AA is reset, the I2C interface cannot
enter a slave mode. STA, STO, and SI must be reset.
The master transmitter mode may now be entered by setting the STA bit. The I2C logic will
now test the I2C bus and generate a start condition as soon as the bus becomes free.
When a START condition is transmitted, the serial interrupt flag (SI) is set, and the status
code in the status register (I2STAT) will be 0x08. This status code is used by the interrupt
service routine to enter the appropriate state service routine that loads I2DAT with the
slave address and the data direction bit (SLA+W). The SI bit in I2CON must then be reset
before the serial transfer can continue.
When the slave address and the direction bit have been transmitted and an
acknowledgment bit has been received, the serial interrupt flag (SI) is set again, and a
number of status codes in I2STAT are possible. There are 0x18, 0x20, or 0x38 for the
master mode and also 0x68, 0x78, or 0xB0 if the slave mode was enabled (AA = logic 1).
The appropriate action to be taken for each of these status codes is detailed in Table 454.
After a repeated start condition (state 0x10). The I2C block may switch to the master
receiver mode by loading I2DAT with SLA+R).

21.9.2 Master Receiver mode

In the master receiver mode, a number of data bytes are received from a slave transmitter
(see Figure 117). The transfer is initialized as in the master transmitter mode. When the
start condition has been transmitted, the interrupt service routine must load I2DAT with the
7 bit slave address and the data direction bit (SLA+R). The SI bit in I2CON must then be
cleared before the serial transfer can continue.
When the slave address and the data direction bit have been transmitted and an
acknowledgment bit has been received, the serial interrupt flag (SI) is set again, and a
number of status codes in I2STAT are possible. These are 0x40, 0x48, or 0x38 for the
master mode and also 0x68, 0x78, or 0xB0 if the slave mode was enabled (AA = 1). The
appropriate action to be taken for each of these status codes is detailed in Table 455. After
a repeated start condition (state 0x10), the I2C block may switch to the master transmitter
mode by loading I2DAT with SLA+W.
21.9.3 Slave Receiver mode

In the slave receiver mode, a number of data bytes are received from a master transmitter
(see Figure 118). To initiate the slave receiver mode, I2ADR and I2CON must be loaded
as follows:
Table 452. I2C0ADR and I2C1ADR usage in Slave Receiver mode

Bit 7 6 5 4 3 2 1 0
Symbol own slave 7 bit address GC
The upper 7 bits are the address to which the I2C block will respond when addressed by a
master. If the LSB (GC) is set, the I2C block will respond to the general call address
(0x00); otherwise it ignores the general call address.
Table 453. I2C0CONSET and I2C1CONSET used to initialize Slave Receiver mode
Bit 7 6 5 4 3 2 1 0
Value - 1 0 0 0 1 - -
The I2C bus rate settings do not affect the I2C block in the slave mode. I2EN must be set
to logic 1 to enable the I2C block. The AA bit must be set to enable the I2C block to
acknowledge its own slave address or the general call address. STA, STO, and SI must
be reset.
When I2ADR and I2CON have been initialized, the I2C block waits until it is addressed by
its own slave address followed by the data direction bit which must be “0” (W) for the I2C
block to operate in the slave receiver mode. After its own slave address and the W bit
have been received, the serial interrupt flag (SI) is set and a valid status code can be read
from I2STAT. This status code is used to vector to a state service routine. The appropriate
action to be taken for each of these status codes is detailed in Table 456. The slave
receiver mode may also be entered if arbitration is lost while the I2C block is in the master
mode (see status 0x68 and 0x78).

If the AA bit is reset during a transfer, the I2C block will return a not acknowledge (logic 1)
to SDA after the next received data byte. While AA is reset, the I2C block does not
respond to its own slave address or a general call address. However, the I2C bus is still
monitored and address recognition may be resumed at any time by setting AA. This
means that the AA bit may be used to temporarily isolate the I2C block from the I2C bus.

MT
successful
transmission
S SLA W A DATA A P
to a Slave
Receiver
08H 18H 28H
next transfer
started with a
S SLA W
Repeated Start
condition
Not 10H
Acknowledge
received after A P R
the Slave
address
20H
to Master
receive
Not
mode,
Acknowledge
A P entry
received after a
= MR
Data byte
30H
arbitration lost
in Slave other Master other Master
A OR A A OR A
address or continues continues
Data byte
38H 38H
arbitration lost
and other Master
A
addressed as continues
Slave
to corresponding
68H 78H B0H
states in Slave mode
any number of data bytes and their associated Acknowledge bits

DATA
this number (contained in I2STA) corresponds to a defined state of the

n
I2C bus
Fig 116. Format and States in the Master Transmitter mode

MR
successful
transmission to S SLA R A DATA A DATA A P
a Slave
transmitter
08H 40H 50H 58H
next transfer
started with a
S SLA R
Repeated Start
condition
10H
Not Acknowledge
received after the A P W
Slave address
48H
to Master
transmit
mode, entry
= MT
arbitration lost in
Slave address or other Master other Master
A OR A A
Acknowledge bit continues continues
38H 38H
arbitration lost
other Master
and addressed A
continues
as Slave
to corresponding
68H 78H B0H states in Slave
mode
any number of data bytes and their associated

DATA A
Acknowledge bits
this number (contained in I2STA) corresponds to a defined state of

n
the I2C bus
Fig 117. Format and States in the Master Receiver mode

reception of the own

Slave address and one
S SLA R A DATA A DATA A P OR S
or more Data bytes all
are acknowledged
60H 80H 80H A0H
last data byte

received is Not A P OR S
acknowledged
88H
arbitration lost as
Master and addressed A
as Slave
68H
reception of the
General Call address
GENERAL CALL A DATA A DATA A P OR S
and one or more Data
bytes
70h 90h 90h A0H
last data byte is Not A P OR S

acknowledged
98h
arbitration lost as
Master and addressed
A
as Slave by General
Call
78h
DATA A any number of data bytes and their associated Acknowledge bits
this number (contained in I2STA) corresponds to a defined state of the 2IC

n
bus
Fig 118. Format and States in the Slave Receiver mode

reception of the own

Slave address and
one or more Data S SLA R A DATA A DATA A P OR S
bytes all are
acknowledged
A8H B8H C0H
arbitration lost as
Master and A
addressed as Slave
last data byte B0H

transmitted. Switched
to Not Addressed A ALL ONES P OR S
Slave (AA bit in
I2CON = “0”)
C8H
any number of data bytes and their associated

DATA A
Acknowledge bits
this number (contained in I2STA) corresponds to a defined state of

n
the I2C bus
Fig 119. Format and States in the Slave Transmitter mode
21.9.4 Slave Transmitter mode

In the slave transmitter mode, a number of data bytes are transmitted to a master receiver
(see Figure 119). Data transfer is initialized as in the slave receiver mode. When I2ADR
and I2CON have been initialized, the I2C block waits until it is addressed by its own slave
address followed by the data direction bit which must be “1” (R) for the I2C block to
operate in the slave transmitter mode. After its own slave address and the R bit have been
received, the serial interrupt flag (SI) is set and a valid status code can be read from
I2STAT. This status code is used to vector to a state service routine, and the appropriate
action to be taken for each of these status codes is detailed in Table 457. The slave
transmitter mode may also be entered if arbitration is lost while the I2C block is in the
master mode (see state 0xB0).
If the AA bit is reset during a transfer, the I2C block will transmit the last byte of the transfer
and enter state 0xC0 or 0xC8. The I2C block is switched to the not addressed slave mode
and will ignore the master receiver if it continues the transfer. Thus the master receiver
receives all 1s as serial data. While AA is reset, the I2C block does not respond to its own
slave address or a general call address. However, the I2C bus is still monitored, and
address recognition may be resumed at any time by setting AA. This means that the AA
bit may be used to temporarily isolate the I2C block from the I2C bus.

Table 454. Master Transmitter mode

Status Status of the I2C bus Application software response Next action taken by I2C hardware
Code and hardware To/From I2DAT To I2CON
(I2CSTAT)
STA STO SI AA
0x08 A START condition Load SLA+W X 0 0 X SLA+W will be transmitted; ACK bit will
has been transmitted. Clear STA be received.
0x10 A repeated START Load SLA+W or X 0 0 X As above.
condition has been Load SLA+R X 0 0 X SLA+W will be transmitted; the I2C block
transmitted. Clear STA will be switched to MST/REC mode.
0x18 SLA+W has been Load data byte or 0 0 0 X Data byte will be transmitted; ACK bit will
transmitted; ACK has be received.
been received. No I2DAT action 1 0 0 X Repeated START will be transmitted.
or
No I2DAT action 0 1 0 X STOP condition will be transmitted; STO
or flag will be reset.
No I2DAT action 1 1 0 X STOP condition followed by a START
condition will be transmitted; STO flag will
be reset.
0x20 SLA+W has been Load data byte or 0 0 0 X Data byte will be transmitted; ACK bit will
transmitted; NOT ACK be received.
has been received. No I2DAT action 1 0 0 X Repeated START will be transmitted.
or
be reset.
0x28 Data byte in I2DAT Load data byte or 0 0 0 X Data byte will be transmitted; ACK bit will
has been transmitted; be received.
ACK has been No I2DAT action 1 0 0 X Repeated START will be transmitted.
received. or
be reset.
0x30 Data byte in I2DAT Load data byte or 0 0 0 X Data byte will be transmitted; ACK bit will
has been transmitted; be received.
NOT ACK has been No I2DAT action 1 0 0 X Repeated START will be transmitted.
received. or
be reset.
0x38 Arbitration lost in No I2DAT action 0 0 0 X I2C bus will be released; not addressed
SLA+R/W or Data or slave will be entered.
bytes. No I2DAT action 1 0 0 X A START condition will be transmitted
when the bus becomes free.

Table 455. Master Receiver mode

(I2CSTAT)
STA STO SI AA
0x08 A START condition Load SLA+R X 0 0 X SLA+R will be transmitted; ACK bit will be
has been transmitted. received.
0x10 A repeated START Load SLA+R or X 0 0 X As above.
condition has been Load SLA+W X 0 0 X SLA+W will be transmitted; the I2C block
transmitted. will be switched to MST/TRX mode.
0x38 Arbitration lost in NOT No I2DAT action 0 0 0 X I2C bus will be released; the I2C block will
ACK bit. or enter a slave mode.
No I2DAT action 1 0 0 X A START condition will be transmitted
when the bus becomes free.
0x40 SLA+R has been No I2DAT action 0 0 0 0 Data byte will be received; NOT ACK bit
transmitted; ACK has or will be returned.
been received. No I2DAT action 0 0 0 1 Data byte will be received; ACK bit will be
returned.
0x48 SLA+R has been No I2DAT action 1 0 0 X Repeated START condition will be
transmitted; NOT ACK or transmitted.
has been received. No I2DAT action 0 1 0 X STOP condition will be transmitted; STO
be reset.
0x50 Data byte has been Read data byte or 0 0 0 0 Data byte will be received; NOT ACK bit
received; ACK has will be returned.
been returned. Read data byte 0 0 0 1 Data byte will be received; ACK bit will be
returned.
0x58 Data byte has been Read data byte or 1 0 0 X Repeated START condition will be
received; NOT ACK transmitted.
has been returned. Read data byte or 0 1 0 X STOP condition will be transmitted; STO
flag will be reset.
Read data byte 1 1 0 X STOP condition followed by a START
be reset.

Table 456. Slave Receiver Mode

(I2CSTAT)
STA STO SI AA
0x60 Own SLA+W has No I2DAT action X 0 0 0 Data byte will be received and NOT ACK
been received; ACK or will be returned.
has been returned. No I2DAT action X 0 0 1 Data byte will be received and ACK will
be returned.
0x68 Arbitration lost in No I2DAT action X 0 0 0 Data byte will be received and NOT ACK
SLA+R/W as master; or will be returned.
Own SLA+W has No I2DAT action X 0 0 1 Data byte will be received and ACK will
been received, ACK be returned.
returned.
0x70 General call address No I2DAT action X 0 0 0 Data byte will be received and NOT ACK
(0x00) has been or will be returned.
received; ACK has No I2DAT action X 0 0 1 Data byte will be received and ACK will
been returned. be returned.
0x78 Arbitration lost in No I2DAT action X 0 0 0 Data byte will be received and NOT ACK
SLA+R/W as master; or will be returned.
General call address No I2DAT action X 0 0 1 Data byte will be received and ACK will
has been received, be returned.
ACK has been
returned.
0x80 Previously addressed Read data byte or X 0 0 0 Data byte will be received and NOT ACK
with own SLV will be returned.
address; DATA has Read data byte X 0 0 1 Data byte will be received and ACK will
been received; ACK be returned.
has been returned.
0x88 Previously addressed Read data byte or 0 0 0 0 Switched to not addressed SLV mode; no
with own SLA; DATA recognition of own SLA or General call
byte has been address.
received; NOT ACK Read data byte or 0 0 0 1 Switched to not addressed SLV mode;
has been returned. Own SLA will be recognized; General call
address will be recognized if
I2ADR[0] = logic 1.
Read data byte or 1 0 0 0 Switched to not addressed SLV mode; no
recognition of own SLA or General call
address. A START condition will be
transmitted when the bus becomes free.
Read data byte 1 0 0 1 Switched to not addressed SLV mode;
Own SLA will be recognized; General call
I2ADR[0] = logic 1. A START condition
will be transmitted when the bus becomes
free.
0x90 Previously addressed Read data byte or X 0 0 0 Data byte will be received and NOT ACK
with General Call; will be returned.
DATA byte has been Read data byte X 0 0 1 Data byte will be received and ACK will
received; ACK has be returned.
been returned.

Table 456. Slave Receiver Mode

(I2CSTAT)
STA STO SI AA
0x98 Previously addressed Read data byte or 0 0 0 0 Switched to not addressed SLV mode; no
with General Call; recognition of own SLA or General call
DATA byte has been address.
received; NOT ACK Read data byte or 0 0 0 1 Switched to not addressed SLV mode;
has been returned. Own SLA will be recognized; General call
I2ADR[0] = logic 1.
Read data byte or 1 0 0 0 Switched to not addressed SLV mode; no
recognition of own SLA or General call
Read data byte 1 0 0 1 Switched to not addressed SLV mode;
free.
0xA0 A STOP condition or No STDAT action 0 0 0 0 Switched to not addressed SLV mode; no
repeated START or recognition of own SLA or General call
condition has been address.
received while still No STDAT action 0 0 0 1 Switched to not addressed SLV mode;
addressed as or Own SLA will be recognized; General call
SLV/REC or address will be recognized if
SLV/TRX. I2ADR[0] = logic 1.
No STDAT action 1 0 0 0 Switched to not addressed SLV mode; no
or recognition of own SLA or General call
No STDAT action 1 0 0 1 Switched to not addressed SLV mode;
free.

Table 457. Tad_105: Slave Transmitter mode

(I2CSTAT)
STA STO SI AA
0xA8 Own SLA+R has been Load data byte or X 0 0 0 Last data byte will be transmitted and
received; ACK has ACK bit will be received.
been returned. Load data byte X 0 0 1 Data byte will be transmitted; ACK will be
received.
0xB0 Arbitration lost in Load data byte or X 0 0 0 Last data byte will be transmitted and
SLA+R/W as master; ACK bit will be received.
Own SLA+R has been Load data byte X 0 0 1 Data byte will be transmitted; ACK bit will
received, ACK has be received.
been returned.
0xB8 Data byte in I2DAT Load data byte or X 0 0 0 Last data byte will be transmitted and
has been transmitted; ACK bit will be received.
ACK has been Load data byte X 0 0 1 Data byte will be transmitted; ACK bit will
received. be received.
0xC0 Data byte in I2DAT No I2DAT action 0 0 0 0 Switched to not addressed SLV mode; no
has been transmitted; or recognition of own SLA or General call
NOT ACK has been address.
received. No I2DAT action 0 0 0 1 Switched to not addressed SLV mode;
or Own SLA will be recognized; General call
I2ADR[0] = logic 1.
No I2DAT action 1 0 0 0 Switched to not addressed SLV mode; no
No I2DAT action 1 0 0 1 Switched to not addressed SLV mode;
free.
0xC8 Last data byte in No I2DAT action 0 0 0 0 Switched to not addressed SLV mode; no
I2DAT has been or recognition of own SLA or General call
transmitted (AA = 0); address.
ACK has been No I2DAT action 0 0 0 1 Switched to not addressed SLV mode;
received. or Own SLA will be recognized; General call
I2ADR[0] = logic 1.
No I2DAT action 1 0 0 0 Switched to not addressed SLV mode; no
No I2DAT action 1 0 0 1 Switched to not addressed SLV mode;
I2ADR.0 = logic 1. A START condition will
be transmitted when the bus becomes
free.

21.9.5 Miscellaneous states

There are two I2STAT codes that do not correspond to a defined I2C hardware state (see
Table 458). These are discussed below.
21.9.5.1 I2STAT = 0xF8

This status code indicates that no relevant information is available because the serial
interrupt flag, SI, is not yet set. This occurs between other states and when the I2C block
is not involved in a serial transfer.
21.9.5.2 I2STAT = 0x00

This status code indicates that a bus error has occurred during an I2C serial transfer. A
bus error is caused when a START or STOP condition occurs at an illegal position in the
format frame. Examples of such illegal positions are during the serial transfer of an
address byte, a data byte, or an acknowledge bit. A bus error may also be caused when
external interference disturbs the internal I2C block signals. When a bus error occurs, SI is
set. To recover from a bus error, the STO flag must be set and SI must be cleared. This
causes the I2C block to enter the “not addressed” slave mode (a defined state) and to
clear the STO flag (no other bits in I2CON are affected). The SDA and SCL lines are
released (a STOP condition is not transmitted).

Table 458. Miscellaneous states

(I2CSTAT)
STA STO SI AA
0xF8 No relevant state No I2DAT action No I2CON action Wait or proceed current transfer.
information available;
SI = 0.
0x00 Bus error during MST No I2DAT action 0 1 0 X Only the internal hardware is affected in
or selected slave the MST or addressed SLV modes. In all
modes, due to an cases, the bus is released and the I2C
illegal START or block is switched to the not addressed
STOP condition. State SLV mode. STO is reset.
0x00 can also occur
when interference
causes the I2C block
to enter an undefined
state.
21.9.6 Some special cases

The I2C hardware has facilities to handle the following special cases that may occur
during a serial transfer:
21.9.7 Simultaneous repeated START conditions from two masters

A repeated START condition may be generated in the master transmitter or master
receiver modes. A special case occurs if another master simultaneously generates a
repeated START condition (see Figure 120). Until this occurs, arbitration is not lost by
either master since they were both transmitting the same data.
If the I2C hardware detects a repeated START condition on the I2C bus before generating
a repeated START condition itself, it will release the bus, and no interrupt request is
generated. If another master frees the bus by generating a STOP condition, the I2C block
will transmit a normal START condition (state 0x08), and a retry of the total serial data
transfer can commence.
21.9.8 Data transfer after loss of arbitration

Arbitration may be lost in the master transmitter and master receiver modes (see
Figure 114). Loss of arbitration is indicated by the following states in I2STAT; 0x38, 0x68,
0x78, and 0xB0 (see Figure 116 and Figure 117).
If the STA flag in I2CON is set by the routines which service these states, then, if the bus
is free again, a START condition (state 0x08) is transmitted without intervention by the
CPU, and a retry of the total serial transfer can commence.
21.9.9 Forced access to the I2C bus

In some applications, it may be possible for an uncontrolled source to cause a bus
hang-up. In such situations, the problem may be caused by interference, temporary
interruption of the bus or a temporary short-circuit between SDA and SCL.

If an uncontrolled source generates a superfluous START or masks a STOP condition,

then the I2C bus stays busy indefinitely. If the STA flag is set and bus access is not
obtained within a reasonable amount of time, then a forced access to the I2C bus is
possible. This is achieved by setting the STO flag while the STA flag is still set. No STOP
condition is transmitted. The I2C hardware behaves as if a STOP condition was received
and is able to transmit a START condition. The STO flag is cleared by hardware (see
Figure 121).
21.9.10 I2C Bus obstructed by a Low level on SCL or SDA

An I2C bus hang-up occurs if SDA or SCL is pulled LOW by an uncontrolled source. If the
SCL line is obstructed (pulled LOW) by a device on the bus, no further serial transfer is
possible, and the I2C hardware cannot resolve this type of problem. When this occurs, the
problem must be resolved by the device that is pulling the SCL bus line LOW.
If the SDA line is obstructed by another device on the bus (e.g., a slave device out of bit
synchronization), the problem can be solved by transmitting additional clock pulses on the
SCL line (see Figure 122). The I2C hardware transmits additional clock pulses when the
STA flag is set, but no START condition can be generated because the SDA line is pulled
LOW while the I2C bus is considered free. The I2C hardware attempts to generate a
START condition after every two additional clock pulses on the SCL line. When the SDA
line is eventually released, a normal START condition is transmitted, state 0x08 is
entered, and the serial transfer continues.
If a forced bus access occurs or a repeated START condition is transmitted while SDA is
obstructed (pulled LOW), the I2C hardware performs the same action as described above.
In each case, state 0x08 is entered after a successful START condition is transmitted and
normal serial transfer continues. Note that the CPU is not involved in solving these bus
hang-up problems.
21.9.11 Bus error

A bus error occurs when a START or STOP condition is present at an illegal position in the
format frame. Examples of illegal positions are during the serial transfer of an address
byte, a data bit, or an acknowledge bit.
The I2C hardware only reacts to a bus error when it is involved in a serial transfer either as
a master or an addressed slave. When a bus error is detected, the I2C block immediately
switches to the not addressed slave mode, releases the SDA and SCL lines, sets the
interrupt flag, and loads the status register with 0x00. This status code may be used to
vector to a state service routine which either attempts the aborted serial transfer again or
simply recovers from the error condition as shown in Table 458.
OTHER MASTER
S SLA W A DATA A S P S SLA
CONTINUES
08H 18H 28H 08H
other Master sends

retry
repeated START earlier
Fig 120. Simultaneous repeated START conditions from 2 masters


time limit
STA flag
STO flag
SDA line
SCL line
start
condition
Fig 121. Forced access to a busy I2C bus
STA flag
(2) (3)
(1) (1)
SDA line
SCL line
start
condition
(1) Unsuccessful attempt to send a start condition.

(2) SDA line is released.
(3) Successful attempt to send a start condition. State 08H is entered.
Fig 122. Recovering from a bus obstruction caused by a low level on SDA
21.9.12 I2C State service routines

This section provides examples of operations that must be performed by various I2C state
service routines. This includes:
• Initialization of the I2C block after a Reset.

• I2C Interrupt Service.
• The 26 state service routines providing support for all four I2C operating modes.
21.9.12.1 Initialization
In the initialization example, the I2C block is enabled for both master and slave modes.
For each mode, a buffer is used for transmission and reception. The initialization routine
performs the following functions:
• I2ADR is loaded with the part’s own slave address and the general call bit (GC).
• The I2C interrupt enable and interrupt priority bits are set.
• The slave mode is enabled by simultaneously setting the I2EN and AA bits in I2CON
and the serial clock frequency (for master modes) is defined by loading CR0 and CR1
in I2CON. The master routines must be started in the main program.

The I2C hardware now begins checking the I2C bus for its own slave address and general
call. If the general call or the own slave address is detected, an interrupt is requested and
I2STAT is loaded with the appropriate state information.
21.9.12.2 I2C interrupt service

When the I2C interrupt is entered, I2STAT contains a status code which identifies one of
the 26 state services to be executed.
21.9.12.3 The state service routines

Each state routine is part of the I2C interrupt routine and handles one of the 26 states.
21.9.12.4 Adapting state services to an application

The state service examples show the typical actions that must be performed in response
to the 26 I2C state codes. If one or more of the four I2C operating modes are not used, the
associated state services can be omitted, as long as care is taken that the those states
can never occur.
In an application, it may be desirable to implement some kind of time-out during I2C

operations, in order to trap an inoperative bus or a lost service routine.
21.10 Software example
21.10.1 Initialization routine

Example to initialize I2C Interface as a Slave and/or Master.
1. Load I2ADR with own Slave Address, enable general call recognition if needed.
2. Enable I2C interrupt.
3. Write 0x44 to I2CONSET to set the I2EN and AA bits, enabling Slave functions. For
Master only functions, write 0x40 to I2CONSET.
21.10.2 Start master transmit function

Begin a Master Transmit operation by setting up the buffer, pointer, and data count, then
initiating a Start.
1. Initialize Master data counter.

2. Set up the Slave Address to which data will be transmitted, and add the Write bit.
3. Write 0x20 to I2CONSET to set the STA bit.
4. Set up data to be transmitted in Master Transmit buffer.
5. Initialize the Master data counter to match the length of the message being sent.
6. Exit
21.10.3 Start master receive function

Begin a Master Receive operation by setting up the buffer, pointer, and data count, then
initiating a Start.

2. Set up the Slave Address to which data will be transmitted, and add the Read bit.
3. Write 0x20 to I2CONSET to set the STA bit.
4. Set up the Master Receive buffer.
5. Initialize the Master data counter to match the length of the message to be received.
6. Exit
21.10.4 I2C interrupt routine

Determine the I2C state and which state routine will be used to handle it.
1. Read the I2C status from I2STA.

2. Use the status value to branch to one of 26 possible state routines.
21.10.5 Non mode specific states
21.10.5.1 State : 0x00

Bus Error. Enter not addressed Slave mode and release bus.
1. Write 0x14 to I2CONSET to set the STO and AA bits.

2. Write 0x08 to I2CONCLR to clear the SI flag.
3. Exit
21.10.6 Master states

State 08 and State 10 are for both Master Transmit and Master Receive modes. The R/W
bit decides whether the next state is within Master Transmit mode or Master Receive
mode.
21.10.6.1 State : 0x08

A Start condition has been transmitted. The Slave Address + R/W bit will be transmitted,
an ACK bit will be received.
1. Write Slave Address with R/W bit to I2DAT.

2. Write 0x04 to I2CONSET to set the AA bit.
4. Set up Master Transmit mode data buffer.
5. Set up Master Receive mode data buffer.
7. Exit
21.10.6.2 State : 0x10

A repeated Start condition has been transmitted. The Slave Address + R/W bit will be
transmitted, an ACK bit will be received.
1. Write Slave Address with R/W bit to I2DAT.


4. Set up Master Transmit mode data buffer.

5. Set up Master Receive mode data buffer.
7. Exit
21.10.7 Master Transmitter states
21.10.7.1 State : 0x18

Previous state was State 8 or State 10, Slave Address + Write has been transmitted, ACK
has been received. The first data byte will be transmitted, an ACK bit will be received.
1. Load I2DAT with first data byte from Master Transmit buffer.
4. Increment Master Transmit buffer pointer.
5. Exit
21.10.7.2 State : 0x20

Slave Address + Write has been transmitted, NOT ACK has been received. A Stop
condition will be transmitted.

3. Exit
21.10.7.3 State : 0x28

Data has been transmitted, ACK has been received. If the transmitted data was the last
data byte then transmit a Stop condition, otherwise transmit the next data byte.
1. Decrement the Master data counter, skip to step 5 if not the last data byte.
4. Exit
5. Load I2DAT with next data byte from Master Transmit buffer.
8. Increment Master Transmit buffer pointer
9. Exit
21.10.7.4 State : 0x30

Data has been transmitted, NOT ACK received. A Stop condition will be transmitted.

3. Exit

21.10.7.5 State : 0x38

Arbitration has been lost during Slave Address + Write or data. The bus has been
released and not addressed Slave mode is entered. A new Start condition will be
transmitted when the bus is free again.
1. Write 0x24 to I2CONSET to set the STA and AA bits.

3. Exit
21.10.8 Master Receive states
21.10.8.1 State : 0x40

Previous state was State 08 or State 10. Slave Address + Read has been transmitted,
ACK has been received. Data will be
received and ACK returned.

3. Exit
21.10.8.2 State : 0x48

Slave Address + Read has been transmitted, NOT ACK has been received. A Stop
condition will be transmitted.

3. Exit
21.10.8.3 State : 0x50

Data has been received, ACK has been returned. Data will be read from I2DAT. Additional
data will be received. If this is the last data byte then NOT ACK will be returned, otherwise
ACK will be returned.
1. Read data byte from I2DAT into Master Receive buffer.

2. Decrement the Master data counter, skip to step 5 if not the last data byte.
3. Write 0x0C to I2CONCLR to clear the SI flag and the AA bit.
4. Exit
7. Increment Master Receive buffer pointer
8. Exit
21.10.8.4 State : 0x58

Data has been received, NOT ACK has been returned. Data will be read from I2DAT. A
Stop condition will be transmitted.

1. Read data byte from I2DAT into Master Receive buffer.

4. Exit
21.10.9 Slave Receiver states
21.10.9.1 State : 0x60

Own Slave Address + Write has been received, ACK has been returned. Data will be
received and ACK returned.

3. Set up Slave Receive mode data buffer.
4. Initialize Slave data counter.
5. Exit
21.10.9.2 State : 0x68

Arbitration has been lost in Slave Address and R/W bit as bus Master. Own Slave Address
+ Write has been received, ACK has been returned. Data will be received and ACK will be
returned. STA is set to restart Master mode after the bus is free again.

5. Exit.
21.10.9.3 State : 0x70

General call has been received, ACK has been returned. Data will be received and ACK
returned.

5. Exit
21.10.9.4 State : 0x78

Arbitration has been lost in Slave Address + R/W bit as bus Master. General call has been
received and ACK has been returned. Data will be received and ACK returned. STA is set
to restart Master mode after the bus is free again.



5. Exit
21.10.9.5 State : 0x80

Previously addressed with own Slave Address. Data has been received and ACK has
been returned. Additional data will be read.
1. Read data byte from I2DAT into the Slave Receive buffer.
2. Decrement the Slave data counter, skip to step 5 if not the last data byte.
4. Exit.
7. Increment Slave Receive buffer pointer.
8. Exit
21.10.9.6 State : 0x88

Previously addressed with own Slave Address . Data has been received and NOT ACK
has been returned. Received data will not be saved. Not addressed Slave mode is
entered.

3. Exit
21.10.9.7 State : 0x90

Previously addressed with general call. Data has been received, ACK has been returned.
Received data will be saved. Only the first data byte will be received with ACK. Additional
data will be received with NOT ACK.
1. Read data byte from I2DAT into the Slave Receive buffer.
3. Exit
21.10.9.8 State : 0x98

Previously addressed with general call. Data has been received, NOT ACK has been
returned. Received data will not be saved. Not addressed Slave mode is entered.

3. Exit
21.10.9.9 State : 0xA0

A Stop condition or repeated Start has been received, while still addressed as a Slave.
Data will not be saved. Not addressed Slave mode is entered.


3. Exit
21.10.10 Slave Transmitter States
21.10.10.1 State : 0xA8

Own Slave Address + Read has been received, ACK has been returned. Data will be
transmitted, ACK bit will be received.
1. Load I2DAT from Slave Transmit buffer with first data byte.
4. Set up Slave Transmit mode data buffer.
5. Increment Slave Transmit buffer pointer.
6. Exit
21.10.10.2 State : 0xB0

Arbitration lost in Slave Address and R/W bit as bus Master. Own Slave Address + Read
has been received, ACK has been returned. Data will be transmitted, ACK bit will be
received. STA is set to restart Master mode after the bus is free again.
1. Load I2DAT from Slave Transmit buffer with first data byte.
4. Set up Slave Transmit mode data buffer.
6. Exit
21.10.10.3 State : 0xB8

Data has been transmitted, ACK has been received. Data will be transmitted, ACK bit will
be received.
1. Load I2DAT from Slave Transmit buffer with data byte.

5. Exit
21.10.10.4 State : 0xC0

Data has been transmitted, NOT ACK has been received. Not addressed Slave mode is
entered.


3. Exit
21.10.10.5 State : 0xC8

The last data byte has been transmitted, ACK has been received. Not addressed Slave
mode is entered.

3. Exit

UM10211
Chapter 22: LPC23XX I2S interface

The I2S interface is configured using the following registers:
1. Power: In the PCONP register (Table 56), set bit PCI2S.

Remark: On reset, the I2S interface is disabled (PCI2S = 0).
2. Clock: In PCLK_SEL1 select PCLK_I2S, see Section 4.7.4.
3. Pins: Select I2S pins and their modes in PINSEL0 to PINSEL4 and PINMODE0 to
22.2 Features
The I2S bus provides a standard communication interface for digital audio applications.
The I2S bus specification defines a 3-wire serial bus, having one data, one clock, and one
word select signal. The basic I2S connection has one master, which is always the master,
and one slave. The I2S interface on the LPC2300 provides a separate transmit and
receive channel, each of which can operate as either a master or a slave.
• The I2S input can operate in both master and slave mode.
The I2S output can operate in both master and slave mode, independent of the I2S
input.
• Capable of handling 8, 16, and 32 bit word sizes.
• Mono and stereo audio data supported.
• The sampling frequency can range (in practice) from 16 - 96 kHz. (16, 22.05, 32, 44.1,
48, 96 kHz) for audio applications.
• Word Select period in master mode is configurable (separately for I2S input and I2S
output).
• Two 8 byte FIFO data buffers are provided, one for transmit and one for receive.
• Generates interrupt requests when buffer levels cross a programmable boundary.
• Two DMA requests, controlled by programmable buffer levels. These are connected
to the General Purpose DMA block.
• Controls include reset, stop and mute options separately for I2S input and I2S output.
22.3 Description
The I2S performs serial data out via the transmit channel and serial data in via the receive
channel. These support the NXP Inter IC Audio format for 8, 16 and 32 bits audio data
both for stereo and mono modes. Configuration, data access and control is performed by
a APB register set. Data streams are buffered by FIFOs with a depth of 8 bytes.

The I2S receive and transmit stage can operate independently in either slave or master
mode. Within the I2S module the difference between these modes lies in the word select
(WS) signal which determines the timing of data transmissions. Data words start on the
next falling edge of the transmitting clock after a WS change. In stereo mode when WS is
low left data is transmitted and right data when WS is high. In mono mode the same data
is transmitted twice, once when WS is low and again when WS is high.
• In master mode (ws_sel = 0), word select is generated internally with a 9 bit counter.
The half period count value of this counter can be set in the control register.
• In slave mode (ws_sel = 1) word select is input from the relevant bus pin.
• When an I2S bus is active, the word select, receive clock and transmit clock signals
are sent continuously by the bus master, while data is sent continuously by the
transmitter.
• Disabling the I2S can be done with the stop or mute control bits separately for the
transmit and receive.
• The stop bit will disable accesses by the transmit channel or the receive channel to
the FIFOs and will place the transmit channel in mute mode.
• The mute control bit will place the transmit channel in mute mode. In mute mode, the
transmit channel FIFO operates normally, but the output is discarded and replaced by
zeroes. This bit does not affect the receive channel, data reception can occur
normally.
22.4 Pin descriptions

Table 459. Pin descriptions
I2SRX_CLK Input/Output Receive Clock. A clock signal used to synchronize the transfer of
data on the receive channel. It is driven by the master and received
by the slave. Corresponds to the signal SCK in the I2S bus
specification.
I2SRX_WS Input/Output Receive Word Select. Selects the channel from which data is to be
received. It is driven by the master and received by the slave.
Corresponds to the signal WS in the I2S bus specification.
WS = 0 indicates that data is being received by channel 1 (left
channel).
WS = 1 indicates that data is being received by channel 2 (right
channel).
I2SRX_SDA Input/Output Receive Data. Serial data, received MSB first. It is driven by the
transmitter and read by the receiver. Corresponds to the signal SD
in the I2S bus specification.

Table 459. Pin descriptions

I2STX_CLK Input/Output Transmit Clock. A clock signal used to synchronize the transfer of
data on the transmit channel. It is driven by the master and
received by the slave. Corresponds to the signal SCK in the I2S
bus specification.
I2STX_WS Input/Output Transmit Word Select. Selects the channel to which data is being
sent. It is driven by the master and received by the slave.
Corresponds to the signal WS in the I2S bus specification.
WS = 0 indicates that data is being sent to channel 1 (left channel).
WS = 1 indicates that data is being sent to channel 2 (right
channel).
I2STX_SDA Input/Output Transmit Data. Serial data, sent MSB first. It is driven by the
transmitter and read by the receiver. Corresponds to the signal SD
in the I2S bus specification.
SCK: serial clock SCK: serial clock

TRANSMITTER WS: word select RECEIVER TRANSMITTER WS: word select RECEIVER
(MASTER) SD: serial data (SLAVE) (SLAVE) SD: serial data (MASTER)
CONTROLLER
(MASTER)
SCK
TRANSMITTER WS RECEIVER
(SLAVE) SD (SLAVE)
SCK
WS
SD MSB LSB MSB
word n-1 word n word n+1

right channel left channel right channel
Fig 123. Simple I2S configurations and bus timing

Table 460 shows the registers associated with the I2S interface and a summary of their
functions. Following the table are details for each register.

Table 460. I2S register map

Value[1]
I2SDAO Digital Audio Output Register. Contains control R/W 0xE008 8000
bits for the I2S transmit channel.
I2SDAI Digital Audio Input Register. Contains control R/W 0xE008 8004
bits for the I2S receive channel.
I2STXFIFO Transmit FIFO. Access register for the 8  32 bit WO 0xE008 8008
transmitter FIFO.
I2SRXFIFO Receive FIFO. Access register for the 8  32 bit RO 0xE008 800C
receiver FIFO.
I2SSTATE Status Feedback Register. Contains status RO 0xE008 8010
information about the I2S interface.
I2SDMA1 DMA Configuration Register 1. Contains control R/W 0xE008 8014
information for DMA request 1.
I2SDMA2 DMA Configuration Register 2. Contains control R/W 0xE008 8018
information for DMA request 2.
I2SIRQ Interrupt Request Control Register. Contains bits R/W 0xE008 801C
that control how the I2S interrupt request is
generated.
I2STXRATE Transmit bit rate divider. This register R/W 0xE008 8020
determines the I2S transmit bit rate by specifying
the value to divide pclk by in order to produce
the transmit bit clock.
I2SRXRATE Receive bit rate divider. This register determines R/W 0xE008 8024
the I2S receive bit rate by specifying the value to
divide pclk by in order to produce the receive bit
clock.
22.5.1 Digital Audio Output Register (I2SDAO - 0xE008 8000)

The I2SDAO register controls the operation of the I2S transmit channel. The function of
bits in DAO are shown in Table 461.
Table 461: Digital Audio Output register (I2SDAO - address 0xE008 8000) bit description
Value
1:0 wordwidth Selects the number of bytes in data as follows: 01
00 8 bit data
01 16 bit data
10 Reserved, do not use this setting
11 32 bit data
2 mono When one, data is of monaural format. When zero, the 0
data is in stereo format.
3 stop Disables accesses on FIFOs, places the transmit 0
channel in mute mode.
4 reset Asynchronously reset the transmit channel and FIFO. 0

Table 461: Digital Audio Output register (I2SDAO - address 0xE008 8000) bit description
Value
5 ws_sel When 0 master mode, when 1 slave mode. 1
14:6 ws_halfperiod Word select half period minus one, i.e. WS 64clk period 0x1F
-> ws_halfperiod = 31.
15 mute When true, the transmit channel sends only zeroes. 1
22.5.2 Digital Audio Input Register (I2SDAI - 0xE008 8004)

The I2SDAI register controls the operation of the I2S receive channel. The function of bits
in DAI are shown in Table 462.
Table 462: Digital Audio Input register (I2SDAI - address 0xE008 8004) bit description
Value
1:0 wordwidth Selects the number of bytes in data as follows: 01
00 8 bit data
01 16 bit data
10 Reserved, do not use this setting
11 32 bit data
2 mono When one, data is of monaural format. When zero, the 0
data is in stereo format.
3 stop Disables accesses on FIFOs, places the transmit 0
channel in mute mode.
4 reset Asynchronously reset the transmit channel and FIFO. 0
5 ws_sel When 0 master mode, when 1 slave mode. 1
14:6 ws_halfperiod Word select half period minus one, i.e. WS 64clk period 0x1F
-> ws_halfperiod = 31.
15 Unused Unused. 1
22.5.3 Transmit FIFO Register (I2STXFIFO - 0xE008 8008)

The I2STXFIFO register provides access to the transmit FIFO. The function of bits in
I2STXFIFO are shown in Table 463.
Table 463: Transmit FIFO register (I2STXFIFO - address 0xE008 8008) bit description
31:0 I2STXFIFO 8  32 bits transmit FIFO. Level = 0
22.5.4 Receive FIFO Register (I2SRXFIFO - 0xE008 800C)

The I2SRXFIFO register provides access to the receive FIFO. The function of bits in
I2SRXFIFO are shown in Table 464.
Table 464: Receive FIFO register (I2RXFIFO - address 0xE008 800C) bit description
31:0 I2SRXFIFO 8  32 bits transmit FIFO. level = 0

22.5.5 Status Feedback Register (I2SSTATE - 0xE008 8010)

The I2SSTATE register provides status information about the I2S interface. The meaning
of bits in I2SSTATE are shown in Table 465.
Table 465: Status Feedback register (I2SSTATE - address 0xE008 8010) bit description
Value
0 irq This bit reflects the presence of Receive Interrupt or Transmit Interrupt. 0
1 dmareq1 This bit reflects the presence of Receive or Transmit DMA Request 1. 0
2 dmareq2 This bit reflects the presence of Receive or Transmit DMA Request 2. 0
7:3 Unused Unused. 0
15:8 rx_level Reflects the current level of the Receive FIFO. 0
23:16 tx_level Reflects the current level of the Transmit FIFO. 0
22.5.6 DMA Configuration Register 1 (I2SDMA1 - 0xE008 8014)

The I2SDMA1 register controls the operation of DMA request 1. The function of bits in
I2SDMA1 are shown in Table 466. Refer to the General Purpose DMA Controller chapter
for details of DMA operation.
Table 466: DMA Configuration register 1 (I2SDMA1 - address 0xE008 8014) bit description
Value
0 rx_dma1_enable When 1, enables DMA1 for I2S receive. 0
1 tx_dma1_enable When 1, enables DMA1 for I2S transmit. 0
15:8 rx_depth_dma1 Set the FIFO level that triggers a receive DMA request on 0
DMA1.
23:16 tx_depth_dma1 Set the FIFO level that triggers a transmit DMA request on 0
DMA1.
22.5.7 DMA Configuration Register 2 (I2SDMA2 - 0xE008 8018)

The I2SDMA2 register controls the operation of DMA request 2. The function of bits in
I2SDMA2 are shown in Table 461.
Value
0 rx_dma2_enable When 1, enables DMA1 for I2S receive. 0
1 tx_dma2_enable When 1, enables DMA1 for I2S transmit. 0

Value
15:8 rx_depth_dma2 Set the FIFO level that triggers a receive DMA request 0
on DMA2.
23:16 tx_depth_dma2 Set the FIFO level that triggers a transmit DMA request 0
on DMA2.
defined.
22.5.8 Interrupt Request Control Register (I2SIRQ - 0xE008 801C)

The I2SIRQ register controls the operation of the I2S interrupt request. The function of bits
in I2SIRQ are shown in Table 461.
Table 468: Interrupt Request Control register (I2SIRQ - address 0xE008 801C) bit description
Value
0 rx_Irq_enable When 1, enables I2S receive interrupt. 0
1 tx_Irq_enable When 1, enables I2S transmit interrupt. 0
15:8 rx_depth_Irq Set the FIFO level on which to create an irq request. 0
23:16 tx_depth_Irq Set the FIFO level on which to create an irq request. 0
defined.
22.5.9 Transmit Clock Rate Register (I2STXRATE - 0xE008 8020)

The bit rate for the I2S transmitter is determined by the value of the I2STXRATE register.
The value depends on the audio sample rate desired, and the data size and format
(stereo/mono) used. For example, a 48 kHz sample rate for 16 bit stereo data requires a
bit rate of 48,000162 = 1.536 MHz.
Table 469: Transmit Clock Rate register (I2TXRATE - address 0xE008 8020) bit description
Value
9:0 tx_rate I2S transmit bit rate. This value plus one is used to divide PCLK by 0
to produce the transmit bit clock. Ten bits of divide supports a wide
range of I2S rates over a wide range of pclk rates.
22.5.10 Receive Clock Rate Register (I2SRXRATE - 0xE008 8024)

The bit rate for the I2S receiver is determined by the value of the I2SRXRATE register.
The value depends on the audio sample rate, as well as the data size and format used.
The calculation is the same as for I2STXRATE.

Table 470: Receive Clock Rate register (I2SRXRATE - address 0xE008 8024) bit description
Value
9:0 rx_rate I2S receive bit rate. This value plus one is used to divide PCLK by 0
to produce the receive bit clock. Ten bits of divide supports a wide
range of I2S rates over a wide range of pclk rates.
22.6 I2S transmit and receive interfaces

The I2S interface can transmit and receive 8, 16 or 32 bits stereo or mono audio
information. Some details of I2S implementation are:
• When the FIFO is empty, the transmit channel will repeat transmitting the same data
until new data is written to the FIFO.
• When mute is true, the data value 0 is transmitted.
• When mono is false, two successive data words are respectively left and right data.
• Data word length is determined by the wordwidth value in the configuration register.
There is a separate wordwidth value for the receive channel and the transmit channel.
– 0: word is considered to contain four 8 bits data words.
– 1: word is considered to contain two 16 bits data words.
– 3: word is considered to contain one 32 bits data word.
• When the transmit FIFO contains insufficient data the transmit channel will repeat
transmitting the last data until new data is available. This can occur when the
microprocessor or the DMA at some time is unable to provide new data fast enough.
Because of this delay in new data there is a need to fill the gap, which is
accomplished by continuing to transmit the last sample. The data is not muted as this
would produce an noticeable and undesirable effect in the sound.
• The transmit channel and the receive channel only handle 32 bit aligned words, data
chunks must be clipped or extended to a multiple of 32 bits.
When switching between data width or modes the I2S must be reset via the reset bit in the
control register in order to ensure correct synchronization. It is advisable to set the stop bit
also until sufficient data has been written in the transmit FIFO. Note that when stopped
data output is muted.
All data accesses to FIFO's are 32 bits. Figure 124 shows the possible data sequences.
A data sample in the FIFO consists of:
• 132 bits in 8 or 16 bit stereo modes.

• 132 bits in mono modes.
• 232 bits, first left data, second right data, in 32 bit stereo modes.
Data is read from the transmit FIFO after the falling edge of WS, it will be transferred to
the transmit clock domain after the rising edge of WS. On the next falling edge of WS the
left data will be loaded in the shift register and transmitted and on the following rising edge
of WS the right data is loaded and transmitted.

The receive channel will start receiving data after a change of WS. When word select
becomes low it expects this data to be left data, when WS is high received data is
expected to be right data. Reception will stop when the bit counter has reached the limit
set by wordwidth. On the next change of WS the received data will be stored in the
appropriate hold register. When complete data is available it will be written into the receive
FIFO.
22.7 FIFO controller

Handling of data for transmission and reception is performed via the FIFO controller which
can generate two DMA requests and an interrupt request. The controller consists of a set
of comparators which compare FIFO levels with depth settings contained in registers. The
current status of the level comparators can be seen in the APB status register.
Table 471. Conditions for FIFO level comparison

Level Comparison Condition
dmareq_tx_1 tx_depth_dma1 >= tx_level
dmareq_rx_1 rx_depth_dma1 <= rx_level
dmareq_tx_2 tx_depth_dma2 >= tx_level
dmareq_rx_2 rx_depth_dma2 <= rx_level
irq_tx tx_depth_irq >= tx_level
irq_rx rx_depth_irq <= rx_level
System signaling occurs when a level detection is true and enabled.
Table 472. DMA and interrupt request generation

System Signaling Condition
irq (irq_rx & rx_irq_enable) | (irq_tx & tx_irq_enable
dmareq[0] (dmareq_tx_1 & tx_dma1_enable ) | (dmareq_rx_1 &
rx_dma1_enable )
dmareq[1] ( dmareq_tx_2 & tx_dma2_enable ) | (dmareq_rx_2 &
rx_dma2_enable )
Table 473. Status feedback in the I2SSTATE register

Status Feedback Status
irq irq_rx | irq_tx
dmareq1 (dmareq_tx_1 | dmareq_rx_1)
dmareq2 (dmareq_rx_2 | dmareq_tx_2)

Mono 8-bit data mode
N+3 N+2 N+1 N

7 0 7 0 7 0 7 0
Stereo 8-bit data mode
LEFT + 1 RIGHT + 1 LEFT RIGHT

7 0 7 0 7 0 7 0
N+1 N
15 0 15 0
LEFT RIGHT
15 0 15 0
N
31 0
LEFT N
31 0
RIGHT N+1
31 0
Fig 124. FIFO contents for various I2S modes

UM10211
Chapter 23: LPC23XX Timer0/1/2/3

The Timer0/1/2/3 peripherals are configured using the following registers:
1. Power: In the PCONP register (Table 56), set bits PCTIM0/1/2/3.

Remark: On reset, Timer0/1 are enabled (PCTIM0/1 = 1), and Timer2/3 are disabled
(PCTIM2/3 = 0).
2. Peripheral clock: In the PCLK_SEL0 register (Table 49), select PCLK_TIMER0/1; in
the PCLK_SEL1 register (Table 50), select PCLK_TIMER2/3.
3. Pins: Select Timer0/1/2/3 pins and pin modes in registers PINSELn and PINMODEn
(see Section 9.5).
4. Interrupts: See register T0/1/2/3MCR (Table 479) and T0/1/2/3CCR (Table 480) for
match and capture events. Interrupts are enabled in the VIC using the VICIntEnable
register (Table 76).
23.2 Features
Remark: The four Timer/Counters are identical except for the peripheral base address. A
minimum of two Capture inputs and two Match outputs are pinned out for all four timers,
with a choice of several pins for each. Timer 1 brings out a third Match output, while
Timers 2 and 3 bring out all four Match outputs.
• A 32 bit Timer/Counter with a programmable 32 bit Prescaler.

• Counter or Timer operation
• Up to two 32 bit capture channels per timer which can take a snapshot of the timer
value when an input signal transitions. A capture event may also optionally generate
an interrupt.
• Four 32 bit match registers that allow:
– Continuous operation with optional interrupt generation on match.
– Stop timer on match with optional interrupt generation.
– Reset timer on match with optional interrupt generation.
• Up to four external outputs corresponding to match registers, with the following
capabilities:
– Set low on match.
– Set high on match.
– Toggle on match.
– Do nothing on match.
23.3 Applications
• Interval Timer for counting internal events.
• Pulse Width Demodulator via Capture inputs.

• Free running timer.
23.4 Description
The Timer/Counter is designed to count cycles of the peripheral clock (PCLK) or an
externally-supplied clock, and can optionally generate interrupts or perform other actions
at specified timer values, based on four match registers. It also includes four capture
inputs to trap the timer value when an input signal transitions, optionally generating an
interrupt.

Table 474 gives a brief summary of each of the Timer/Counter related pins.
Table 474. Timer/Counter pin description

CAP0[1:0] Input Capture Signals- A transition on a capture pin can be configured to load one
CAP1[1:0] of the Capture Registers with the value in the Timer Counter and optionally
CAP2[1:0] generate an interrupt. Capture functionality can be selected from a number
CAP3[1:0] of pins. When more than one pin is selected for a Capture input on a single
TIMER0/1 channel, the pin with the lowest Port number is used
Timer/Counter block can select a capture signal as a clock source instead of
the PCLK derived clock. For more details see Section 23.6.3.
MAT0[1:0] Output External Match Output - When a match register (MR3:0) equals the timer
MAT1[1:0] counter (TC) this output can either toggle, go low, go high, or do nothing. The
MAT2[3:0] External Match Register (EMR) controls the functionality of this output.
MAT3[1:0] Match Output functionality can be selected on a number of pins in parallel.
23.5.1 Multiple CAP and MAT pins

Software can select multiple pins for most of the CAP or MAT functions in the Pin Select
registers, which are described in Section 9.3. When more than one pin is selected for a
MAT output, all such pins are driven identically. When more than one pin is selected for a
CAP input, the pin with the lowest Port number is used.

Each Timer/Counter contains the registers shown in Table 475 ("Reset Value" refers to the
data stored in used bits only; it does not include reserved bits content). More detailed
descriptions follow.

Table 475. TIMER/COUNTER0-3 register map

Generic Description Access Reset TIMERn Register/
Name Value[1] Name & Address
IR Interrupt Register. The IR can be written to R/W 0 T0IR - 0xE000 4000
clear interrupts. The IR can be read to T1IR - 0xE000 8000
identify which of eight possible interrupt T2IR - 0xE007 0000
sources are pending. T3IR - 0xE007 4000
TCR Timer Control Register. The TCR is used R/W 0 T0TCR - 0xE000 4004
to control the Timer Counter functions. T1TCR - 0xE000 8004
The Timer Counter can be disabled or T2TCR - 0xE007 0004
reset through the TCR. T3TCR - 0xE007 4004
TC Timer Counter. The 32 bit TC is R/W 0 T0TC - 0xE000 4008
incremented every PR+1 cycles of PCLK. T1TC - 0xE000 8008
The TC is controlled through the TCR. T2TC - 0xE007 0008
T3TC - 0xE007 4008
PR Prescale Register. The Prescale Counter R/W 0 T0PR - 0xE000 400C
(below) is equal to this value, the next T1PR - 0xE000 800C
clock increments the TC and clears the T2PR - 0xE007 000C
PC. T3PR - 0xE007 400C
PC Prescale Counter. The 32 bit PC is a R/W 0 T0PC - 0xE000 4010
counter which is incremented to the value T1PC - 0xE000 8010
stored in PR. When the value in PR is T2PC - 0xE007 0010
reached, the TC is incremented and the T3PC - 0xE007 4010
PC is cleared. The PC is observable and
controllable through the bus interface.
MCR Match Control Register. The MCR is used R/W 0 T0MCR - 0xE000 4014
to control if an interrupt is generated and if T1MCR - 0xE000 8014
the TC is reset when a Match occurs. T2MCR - 0xE007 0014
T3MCR - 0xE007 4014
MR0 Match Register 0. MR0 can be enabled R/W 0 T0MR0 - 0xE000 4018
through the MCR to reset the TC, stop T1MR0 - 0xE000 8018
both the TC and PC, and/or generate an T2MR0 - 0xE007 0018
interrupt every time MR0 matches the TC. T3MR0 - 0xE007 4018
MR1 Match Register 1. See MR0 description. R/W 0 T0MR1 - 0xE000 401C
T1MR1 - 0xE000 801C
T2MR1 - 0xE007 001C
T3MR1 - 0xE007 401C
MR2 Match Register 2. See MR0 description. R/W 0 T0MR2 - 0xE000 4020
T1MR2 - 0xE000 8020
T2MR2 - 0xE007 0020
T3MR2 - 0xE007 4020
MR3 Match Register 3. See MR0 description. R/W 0 T0MR3 - 0xE000 4024
T1MR3 - 0xE000 8024
T2MR3 - 0xE007 0024
T3MR3 - 0xE007 4024
CCR Capture Control Register. The CCR R/W 0 T0CCR - 0xE000 4028
controls which edges of the capture inputs T1CCR - 0xE000 8028
are used to load the Capture Registers T2CCR - 0xE007 0028
and whether or not an interrupt is T3CCR - 0xE007 4028
generated when a capture takes place.

Table 475. TIMER/COUNTER0-3 register map

Generic Description Access Reset TIMERn Register/
CR0 Capture Register 0. CR0 is loaded with the RO 0 T0CR0 - 0xE000 402C
value of TC when there is an event on the T1CR0 - 0xE000 802C
CAPn.0 (CAP0.0, CAP1.0, CAP2.0, or T2CR0 - 0xE007 002C
CAP3.0) input. T3CR0 - 0xE007 402C
CR1 Capture Register 1. CR1 is loaded with the RO 0 T0CR1 - 0xE000 4030
value of TC when there is an event on the T1CR1 - 0xE000 8030
CAPn.0 (CAP1.0, CAP1.1, CAP2.1, or T2CR1 - 0xE007 0030
CAP3.1) input. T3CR1 - 0xE007 4030
EMR External Match Register. The EMR R/W 0 T0EMR - 0xE000 403C
controls the external match pins MATn.0-3 T1EMR - 0xE000 803C
(n corresponds to timers 0 to 3). T2EMR - 0xE007 003C
T3EMR - 0xE007 403C
CTCR Count Control Register. The CTCR selects R/W 0 T0CTCR - 0xE000 4070
between Timer and Counter mode, and in T1CTCR - 0xE000 8070
Counter mode selects the signal and T2CTCR - 0xE007 0070
edge(s) for counting. T3CTCR - 0xE007 4070
23.6.1 Interrupt Register (T[0/1/2/3]IR - 0xE000 4000, 0xE000 8000,

0xE007 0000, 0xE007 4000)
The Interrupt Register consists of four bits for the match interrupts and four bits for the
capture interrupts. If an interrupt is generated then the corresponding bit in the IR will be
high. Otherwise, the bit will be low. Writing a logic one to the corresponding IR bit will reset
the interrupt. Writing a zero has no effect.
Table 476: Interrupt Register (T[0/1/2/3]IR - addresses 0xE000 4000, 0xE000 8000,
0xE007 0000, 0xE007 4000) bit description
Value
0 MR0 Interrupt Interrupt flag for match channel 0. 0
4 CR0 Interrupt Interrupt flag for capture channel 0 event. 0
5 CR1 Interrupt Interrupt flag for capture channel 1 event. 0
6 - Reserved 0
7 - Reserved 0
23.6.2 Timer Control Register (T[0/1/2/3]CR - 0xE000 4004, 0xE000 8004,

0xE007 0004, 0xE007 4004)
The Timer Control Register (TCR) is used to control the operation of the Timer/Counter.

Table 477: Timer Control Register (TCR, TIMERn: TnTCR - addresses 0xE000 4004,
0xE000 8004, 0xE007 0004, 0xE007 4004) bit description
0 Counter Enable When one, the Timer Counter and Prescale Counter are 0
enabled for counting. When zero, the counters are
disabled.
1 Counter Reset When one, the Timer Counter and the Prescale Counter 0
are synchronously reset on the next positive edge of
PCLK. The counters remain reset until TCR[1] is
returned to zero.
defined.
23.6.3 Count Control Register (T[0/1/2/3]CTCR - 0xE000 4070, 0xE000 8070,

0xE007 0070, 0xE007 4070)
The Count Control Register (CTCR) is used to select between Timer and Counter mode,
and in Counter mode to select the pin and edge(s) for counting.
When Counter Mode is chosen as a mode of operation, the CAP input (selected by the
CTCR bits 3:2) is sampled on every rising edge of the PCLK clock. After comparing two
consecutive samples of this CAP input, one of the following four events is recognized:
rising edge, falling edge, either of edges or no changes in the level of the selected CAP
input. Only if the identified event corresponds to the one selected by bits 1:0 in the CTCR
register, the Timer Counter register will be incremented.
Effective processing of the externally supplied clock to the counter has some limitations.
Since two successive rising edges of the PCLK clock are used to identify only one edge
on the CAP selected input, the frequency of the CAP input can not exceed one quarter of
the PCLK clock. Consequently, duration of the high/low levels on the same CAP input in
this case can not be shorter than 1/(2 PCLK).
Table 478: Count Control Register (T[0/1/2/3]CTCR - addresses 0xE000 4070, 0xE000 8070,
Value
1:0 Counter/ This field selects which rising PCLK edges can increment 00
Timer Timer’s Prescale Counter (PC), or clear PC and increment
Mode Timer Counter (TC).
Timer Mode: the TC is incremented when the Prescale
Counter matches the Prescale Register.
00 Timer Mode: every rising PCLK edge
01 Counter Mode: TC is incremented on rising edges on the
CAP input selected by bits 3:2.
10 Counter Mode: TC is incremented on falling edges on the
CAP input selected by bits 3:2.
11 Counter Mode: TC is incremented on both edges on the CAP
input selected by bits 3:2.

Table 478: Count Control Register (T[0/1/2/3]CTCR - addresses 0xE000 4070, 0xE000 8070,
Value
3:2 Count When bits 1:0 in this register are not 00, these bits select 00
Input which CAP pin is sampled for clocking:
Select 00 CAPn.0 for TIMERn
01 CAPn.1 for TIMERn
Note: If Counter mode is selected for a particular CAPn input
in the TnCTCR, the 3 bits for that input in the Capture
Control Register (TnCCR) must be programmed as 000.
However, capture and/or interrupt can be selected for the
other CAPn input in the same timer.
10 reserved
11 reserved
23.6.4 Timer Counter registers (T0TC - T3TC, 0xE000 4008, 0xE000 8008,
0xE007 0008, 0xE007 4008)
The 32-bit Timer Counter register is incremented when the prescale counter reaches its
terminal count. Unless it is reset before reaching its upper limit, the Timer Counter will
count up through the value 0xFFFF FFFF and then wrap back to the value 0x0000 0000.
This event does not cause an interrupt, but a match register can be used to detect an
overflow if needed.
23.6.5 Prescale register (T0PR - T3PR, 0xE000 400C, 0xE000 800C,

0xE007 000C, 0xE007 400C)
The 32-bit Prescale register specifies the maximum value for the Prescale Counter.
23.6.6 Prescale Counter register (T0PC - T3PC, 0xE000 4010, 0xE000 8010,
0xE007 0010, 0xE007 4010)
The 32-bit Prescale Counter controls division of PCLK by some constant value before it is
applied to the Timer Counter. This allows control of the relationship of the resolution of the
timer versus the maximum time before the timer overflows. The Prescale Counter is
incremented on every PCLK. When it reaches the value stored in the Prescale register,
the Timer Counter is incremented and the Prescale Counter is reset on the next PCLK.
This causes the Timer Counter to increment on every PCLK when PR = 0, every 2 PCLKs
when PR = 1, etc.
23.6.7 Match Registers (MR0 - MR3)

The Match register values are continuously compared to the Timer Counter value. When
the two values are equal, actions can be triggered automatically. The action possibilities
are to generate an interrupt, reset the Timer Counter, or stop the timer. Actions are
controlled by the settings in the MCR register.

23.6.8 Match Control Register (T[0/1/2/3]MCR - 0xE000 4014, 0xE000 8014,

0xE007 0014, 0xE007 4014)
The Match Control Register is used to control what operations are performed when one of
the Match Registers matches the Timer Counter. The function of each of the bits is shown
in Table 479.
Table 479: Match Control Register (T[0/1/2/3]MCR - addresses 0xE000 4014, 0xE000 8014,
Value
0 MR0I 1 Interrupt on MR0: an interrupt is generated when MR0 matches 0
the value in the TC.
0 This interrupt is disabled
1 MR0R 1 Reset on MR0: the TC will be reset if MR0 matches it. 0
0 Feature disabled.
2 MR0S 1 Stop on MR0: the TC and PC will be stopped and TCR[0] will be 0
set to 0 if MR0 matches the TC.
0 Feature disabled.
0 Feature disabled.
0 Feature disabled.
0 Feature disabled.
0 Feature disabled.
0 Feature disabled.
0 Feature disabled.

23.6.9 Capture Registers (CR0 and CR1)

Each Capture register is associated with a device pin and may be loaded with the Timer
Counter value when a specified event occurs on that pin. The settings in the Capture
Control Register register determine whether the capture function is enabled, and whether
a capture event happens on the rising edge of the associated pin, the falling edge, or on
both edges.
23.6.10 Capture Control Register (T[0/1/2/3]CCR - 0xE000 4028, 0xE000 8028,

0xE007 0028, 0xE007 4028)
The Capture Control Register is used to control whether one of the two Capture Registers
is loaded with the value in the Timer Counter when the capture event occurs, and whether
an interrupt is generated by the capture event. Setting both the rising and falling bits at the
same time is a valid configuration, resulting in a capture event for both edges. In the
description below, "n" represents the timer number, 0 to 3.
Note: If Counter mode is selected for a particular CAP input in the CTCR, the 3 bits for
that input in this register should be programmed as 000, but capture and/or interrupt can
be selected for the other CAP input.
Table 480: Capture Control Register (T[0/1/2/3]CCR - addresses 0xE000 4028, 0xE000 8020,
Value
0 CAP0RE 1 Capture on CAPn.0 rising edge: a sequence of 0 then 1 on 0
CAPn.0 will cause CR0 to be loaded with the contents of TC.
0 This feature is disabled.
1 CAP0FE 1 Capture on CAPn.0 falling edge: a sequence of 1 then 0 on 0
2 CAP0I Interrupt on CAPn.0 event: a CR0 load due to a CAPn.0 event 0
1 will generate an interrupt.
3 CAP1RE 1 Capture on CAPn.1 rising edge: a sequence of 0 then 1 on 0
4 CAP1FE 1 Capture on CAPn.1 falling edge: a sequence of 1 then 0 on 0
5 CAP1I Interrupt on CAPn.1 event: a CR1 load due to a CAPn.1 event 0
1 will generate an interrupt.

23.6.11 External Match Register (T[0/1/2/3]EMR - 0xE000 403C, 0xE000 803C,

0xE007 003C, 0xE007 403C)
The External Match Register provides both control and status of the external match pins.
In the descriptions below, “n” represents the Timer number, 0 to 3, and “m” represent a
Match number, 0 through 3.
Table 481: External Match Register (T[0/1/2/3]EMR - addresses 0xE000 403C, 0xE000 803C,
0xE007 003C, 0xE007 403C) bit description
Value
0 EM0 External Match 0. When a match occurs between the TC and MR0, this 0
bit can either toggle, go low, go high, or do nothing, depending on bits 5:4
of this register. This bit can be driven onto a MATn.0 pin, in a
positive-logic manner (0 = low, 1 = high).
bit can either toggle, go low, go high, or do nothing, depending on bits
11:10 of this register. This bit can be driven onto a MATn.3 pin, in a
5:4 EMC0 External Match Control 0. Determines the functionality of External Match 00
0. Table 482 shows the encoding of these bits.
Table 482. External Match Control

EMR[11:10], EMR[9:8], Function
EMR[7:6], or EMR[5:4]
00 Do Nothing.
01 Clear the corresponding External Match bit/output to 0 (MATn.m pin is
LOW if pinned out).
10 Set the corresponding External Match bit/output to 1 (MATn.m pin is
HIGH if pinned out).
11 Toggle the corresponding External Match bit/output.

23.7 Example timer operation

Figure 125 shows a timer configured to reset the count and generate an interrupt on
match. The prescaler is set to 2 and the match register set to 6. At the end of the timer
cycle where the match occurs, the timer count is reset. This gives a full length cycle to the
match value. The interrupt indicating that a match occurred is generated in the next clock
after the timer reached the match value.
Figure 126 shows a timer configured to stop and generate an interrupt on match. The
prescaler is again set to 2 and the match register set to 6. In the next clock after the timer
reaches the match value, the timer enable bit in TCR is cleared, and the interrupt
indicating that a match occurred is generated.
PCLK
prescale
2 0 1 2 0 1 2 0 1 2 0 1
counter
timer
4 5 6 0 1
counter
timer counter
reset
interrupt
Fig 125. A timer cycle in which PR=2, MRx=6, and both interrupt and reset on match are enabled.
PCLK
prescale counter 2 0 1 2 0
timer counter
4 5 6
TCR[0]
1 0
(counter enable)
interrupt
Fig 126. A Timer Cycle in Which PR=2, MRx=6, and Both Interrupt and Stop on Match are Enabled
23.8 Architecture
The block diagram for TIMER/COUNTER0 and TIMER/COUNTER1 is shown in
Figure 127.

MATCH REGISTER 0
MATCH REGISTER 1
MATCH REGISTER 2
MATCH REGISTER 3
MATCH CONTROL REGISTER
EXTERNAL MATCH REGISTER
INTERRUPT REGISTER
CONTROL
=
MAT[3:0]
INTERRUPT =
CAP[3:0]
STOP ON MATCH =
RESET ON MATCH
=
LOAD[3:0]
CAPTURE CONTROL REGISTER
CSN
CAPTURE REGISTER 0 TIMER COUNTER
CAPTURE REGISTER 1 CE
RESERVED
RESERVED
TCI
PCLK
PRESCALE COUNTER
reset enable MAXVAL
TIMER CONTROL REGISTER PRESCALE REGISTER
Fig 127. Timer block diagram

UM10211
Chapter 24: LPC23XX Pulse Width Modulator (PWM)

The PWM is configured using the following registers:
1. Power: In the PCONP register (Table 56), set bit PCPWM1.

Remark: On reset, the PWM is enabled (PCPWM1 = 1).
2. Peripheral clock: In the PCLK_SEL0 register (Table 49), select PCLK_PWM.
3. Pins: Select PWM pins and pin modes in registers PINSELn and PINMODEn (see
Section 9.5).
4. Interrupts: See register PWM1MCR (Table 490) and PWM1CCR (Table 491) for
match and capture events. Interrupts are enabled in the VIC using the VICIntEnable
register (Table 76).
24.2 Features
• Counter or Timer operation (may use the peripheral clock or one of the capture inputs
as the clock source).
• Seven match registers allow up to 6 single edge controlled or 3 double edge
controlled PWM outputs, or a mix of both types. The match registers also allow:
– Continuous operation with optional interrupt generation on match.
– Stop timer on match with optional interrupt generation.
– Reset timer on match with optional interrupt generation.
• Supports single edge controlled and/or double edge controlled PWM outputs. Single
edge controlled PWM outputs all go high at the beginning of each cycle unless the
output is a constant low. Double edge controlled PWM outputs can have either edge
occur at any position within a cycle. This allows for both positive going and negative
going pulses.
• Pulse period and width can be any number of timer counts. This allows complete
flexibility in the trade-off between resolution and repetition rate. All PWM outputs will
occur at the same repetition rate.
• Double edge controlled PWM outputs can be programmed to be either positive going
or negative going pulses.
• Match register updates are synchronized with pulse outputs to prevent generation of
erroneous pulses. Software must "release" new match values before they can
become effective.
• May be used as a standard timer if the PWM mode is not enabled.
• A 32 bit Timer/Counter with a programmable 32 bit Prescaler.
• Two 32 bit capture channels take a snapshot of the timer value when an input signal
transitions. A capture event may also optionally generate an interrupt.

24.3 Description
The PWM is based on the standard Timer block and inherits all of its features, although
only the PWM function is pinned out on the LPC2300. The Timer is designed to count
cycles of the peripheral clock (PCLK) and optionally generate interrupts or perform other
actions when specified timer values occur, based on seven match registers. The PWM
function is in addition to these features, and is based on match register events.
The ability to separately control rising and falling edge locations allows the PWM to be
used for more applications. For instance, multi-phase motor control typically requires
three non-overlapping PWM outputs with individual control of all three pulse widths and
positions.
Two match registers can be used to provide a single edge controlled PWM output. One
match register (PWMMR0) controls the PWM cycle rate, by resetting the count upon
match. The other match register controls the PWM edge position. Additional single edge
controlled PWM outputs require only one match register each, since the repetition rate is
the same for all PWM outputs. Multiple single edge controlled PWM outputs will all have a
rising edge at the beginning of each PWM cycle, when an PWMMR0 match occurs.
Three match registers can be used to provide a PWM output with both edges controlled.
Again, the PWMMR0 match register controls the PWM cycle rate. The other match
registers control the two PWM edge positions. Additional double edge controlled PWM
outputs require only two match registers each, since the repetition rate is the same for all
PWM outputs.
With double edge controlled PWM outputs, specific match registers control the rising and
falling edge of the output. This allows both positive going PWM pulses (when the rising
edge occurs prior to the falling edge), and negative going PWM pulses (when the falling
edge occurs prior to the rising edge).
Figure 128 shows the block diagram of the PWM. The portions that have been added to
the standard timer block are on the right hand side and at the top of the diagram.

MATCH REGISTER 0 SHADOW REGISTER 0

LOAD ENABLE
LOAD ENABLE
LOAD ENABLE
LOAD ENABLE
LOAD ENABLE
MATCH REGISTER 5 SHADOW REGISTER 5 Match 0 PWM1
LOAD ENABLE S Q
LOAD ENABLE Match 1 PWMENA1
R EN
PWMSEL2
PWM2
MUX S Q
Match0
Match 2 PWMENA2
R EN
LOAD ENABLE REGISTER CLEAR
PWMSEL3
MATCH CONTROL REGISTER PWM3
MUX S Q
Match 3 PWMENA3
R EN
INTERRUPT REGISTER
PWMSEL4
PWM4
MUX S Q
CONTROL
= PWMENA4
Match 4
= R EN
M[6:0]
INTERRUPT =
PWMSEL5
CAPTURE[1:0] =
PWM5
STOP ON MATCH = MUX S Q
RESET ON MATCH = Match 5 PWMENA5

LOAD[1:0] = R EN
PWMSEL6
CAPTURE CONTROL REGISTER PWM6
MUX S Q
CSN
CAPTURE REGISTER 0
Match 6 PWMENA6
TIMER COUNTER
CAPTURE REGISTER 1 R EN
RESERVED
CE
RESERVED
TCI
PRESCALE COUNTER PWMENA1..6 PWMSEL2..6

reset enable MAXVAL
TIMER CONTROL REGISTER PRESCALE REGISTER PWM CONTROL REGISTER
Fig 128. PWM block diagram

24.4 Sample waveform with rules for single and double edge control
A sample of how PWM values relate to waveform outputs is shown in Figure 129. PWM
output logic is shown in Figure 128 that allows selection of either single or double edge
controlled PWM outputs via the muxes controlled by the PWMSELn bits. The match
register selections for various PWM outputs is shown in Table 483. This implementation
supports up to N-1 single edge PWM outputs or (N-1)/2 double edge PWM outputs, where
N is the number of match registers that are implemented. PWM types can be mixed if
desired.
PWM2
PWM4
PWM5
1 27 41 53 65 78 100
(counter is reset)
The waveforms below show a single PWM cycle and demonstrate PWM outputs under the
following conditions:
The timer is configured for PWM mode (counter resets to 1).
Match 0 is configured to reset the timer/counter when a match event occurs.
All PWM related Match registers are configured for toggle on match.
Control bits PWMSEL2 and PWMSEL4 are set.
The Match register values are as follows:
MR0 = 100 (PWM rate)
MR1 = 41, MR2 = 78 (PWM2 output)
MR3 = 53, MR$ = 27 (PWM4 output)
MR5 = 65 (PWM5 output)
Fig 129. Sample PWM waveforms
Table 483. Set and reset inputs for PWM Flip-Flops

PWM Channel Single Edge PWM (PWMSELn = 0) Double Edge PWM (PWMSELn = 1)
Set by Reset by Set by Reset by
1 Match 0 Match 1 Match 0[1] Match 1[1]
2 Match 0 Match 2 Match 1 Match 2
[1] Identical to single edge mode in this case since Match 0 is the neighboring match register. Essentially,
PWM1 cannot be a double edged output.
[2] It is generally not advantageous to use PWM channels 3 and 5 for double edge PWM outputs because it
would reduce the number of double edge PWM outputs that are possible. Using PWM 2, PWM4, and
PWM6 for double edge PWM outputs provides the most pairings.

24.4.1 Rules for Single Edge Controlled PWM Outputs

1. All single edge controlled PWM outputs go high at the beginning of a PWM cycle
unless their match value is equal to 0.
2. Each PWM output will go low when its match value is reached. If no match occurs (i.e.
the match value is greater than the PWM rate), the PWM output remains continuously
high.
24.4.2 Rules for Double Edge Controlled PWM Outputs

Five rules are used to determine the next value of a PWM output when a new cycle is
about to begin:
1. The match values for the next PWM cycle are used at the end of a PWM cycle (a time
point which is coincident with the beginning of the next PWM cycle), except as noted
in rule 3.
2. A match value equal to 0 or the current PWM rate (the same as the Match channel 0
value) have the same effect, except as noted in rule 3. For example, a request for a
falling edge at the beginning of the PWM cycle has the same effect as a request for a
falling edge at the end of a PWM cycle.
3. When match values are changing, if one of the "old" match values is equal to the
PWM rate, it is used again once if the neither of the new match values are equal to 0
or the PWM rate, and there was no old match value equal to 0.
4. If both a set and a clear of a PWM output are requested at the same time, clear takes
precedence. This can occur when the set and clear match values are the same as in,
or when the set or clear value equals 0 and the other value equals the PWM rate.
5. If a match value is out of range (i.e. greater than the PWM rate value), no match event
occurs and that match channel has no effect on the output. This means that the PWM
output will remain always in one state, allowing always low, always high, or
"no change" outputs.

Table 484 gives a brief summary of each of PWM related pins.
Table 484. Pin summary

PWM1[1] Output Output from PWM channel 1.
PCAP1[1:0] Input Capture Inputs. A transition on a capture pin can be configured to load
the corresponding Capture Register with the value of the Timer
Counter and optionally generate an interrupt. PWM1 brings out 2
capture inputs.

24.6 PWM base addresses

Table 485: Addresses for PWM1
PWM Base Addresses
1 0xE001 8000

PWM1 function adds new registers and registers bits as shown in Table 486 below.
Table 486. PWM1 register map

Generic Description Access Reset PWMn Register
IR Interrupt Register. The IR can be written to clear interrupts. The R/W 0 PWM1IR - 0xE001 8000
IR can be read to identify which of eight possible interrupt
sources are pending.
TCR Timer Control Register. The TCR is used to control the Timer R/W 0 PWM1TCR - 0xE001 8004
Counter functions. The Timer Counter can be disabled or reset
through the TCR.
TC Timer Counter. The 32 bit TC is incremented every PR+1 R/W 0 PWM1TC -0xE001 8008
cycles of PCLK. The TC is controlled through the TCR.
PR Prescale Register. The TC is incremented every PR+1 cycles R/W 0 PWM1PR - 0xE001 800C
of PCLK.
PC Prescale Counter. The 32 bit PC is a counter which is R/W 0 PWM1PC - 0xE001 8010
incremented to the value stored in PR. When the value in PR is
reached, the TC is incremented. The PC is observable and
controllable through the bus interface.
MCR Match Control Register. The MCR is used to control if an R/W 0 PWM1MCR - 0xE001 8014
interrupt is generated and if the TC is reset when a Match
occurs.
MR0 Match Register 0. MR0 can be enabled in the MCR to reset the R/W 0 PWM1MR0 - 0xE001 8018
TC, stop both the TC and PC, and/or generate an interrupt
when it matches the TC. In addition, a match between this
value and the TC sets any PWM output that is in single-edge
mode, and sets PWM1 if it’s in double-edge mode.
MR1 Match Register 1. MR1 can be enabled in the MCR to reset the R/W 0 PWM1MR1 - 0xE001 801C
value and the TC clears PWM1 in either edge mode, and sets
PWM2 if it’s in double-edge mode.

Table 486. PWM1 register map

Generic Description Access Reset PWMn Register
CCR Capture Control Register. The CCR controls which edges of R/W 0 PWM1CCR - 0xE001 8028
the capture inputs are used to load the Capture Registers and
whether or not an interrupt is generated when a capture takes
place.
CR0 Capture Register 0. CR0 is loaded with the value of the TC RO 0 PWM1CR0 - 0xE001 802C
when there is an event on the CAPn.0 input.
CR1 Capture Register 1. See CR0 description. RO 0 PWM1CR1 - 0xE001 8030
MR4 Match Register 4. MR4 can be enabled in the MCR to reset the R/W 0 PWM1MR - 0xE001 8040
value and the TC clears PWM6 in either edge mode.
PCR PWM Control Register. Enables PWM outputs and selects R/W 0 PWM1PCR - 0xE001 804C
PWM channel types as either single edge or double edge
controlled.
LER Load Enable Register. Enables use of new PWM match values. R/W 0 PWM1LER - 0xE001 8050
CTCR Count Control Register. The CTCR selects between Timer and R/W 0 PWM1CTCR - 0xE001 8070
Counter mode, and in Counter mode selects the signal and
edge(s) for counting.
24.7.1 PWM Interrupt Register (PWM1IR - 0xE001 8000)

The PWM Interrupt Register consists of eleven bits (Table 487), seven for the match
interrupts and four reserved for the future use. If an interrupt is generated then the
corresponding bit in the PWMIR will be high. Otherwise, the bit will be low. Writing a logic
one to the corresponding IR bit will reset the interrupt. Writing a zero has no effect.
Table 487: PWM Interrupt Register (PWM1IR - address 0xE001 8000) bit description
Value
0 PWMMR0 Interrupt Interrupt flag for PWM match channel 0. 0

Table 487: PWM Interrupt Register (PWM1IR - address 0xE001 8000) bit description
Value
4 PWMCAP0 Interrupt flag for capture input 0 0
Interrupt
5 PWMCAP1 Interrupt flag for capture input 1. 0
Interrupt
24.7.2 PWM Timer Control Register (PWM1TCR 0xE001 8004)

The PWM Timer Control Register (PWMTCR) is used to control the operation of the PWM
Timer Counter. The function of each of the bits is shown in Table 488.
Table 488: PWM Timer Control Register (PWM1TCR address 0xE001 8004) bit description
Value
0 Counter Enable 1 The PWM Timer Counter and PWM Prescale Counter are 0
enabled for counting.
0 The counters are disabled.
1 Counter Reset 1 The PWM Timer Counter and the PWM Prescale Counter 0
are synchronously reset on the next positive edge of PCLK.
The counters remain reset until this bit is returned to zero.
0 Clear reset.
2 - Reserved, user software should not write ones to reserved NA
3 PWM Enable 1 PWM mode is enabled (counter resets to 1). PWM mode 0
causes the shadow registers to operate in connection with
the Match registers. A program write to a Match register will
not have an effect on the Match result until the
corresponding bit in PWMLER has been set, followed by the
occurrence of a PWM Match 0 event. Note that the PWM
Match register that determines the PWM rate (PWM Match
Register 0 - MR0) must be set up prior to the PWM being
enabled. Otherwise a Match event will not occur to cause
shadow register contents to become effective.
0 Timer mode is enabled (counter resets to 0).
24.7.3 PWM Count Control Register (PWM1CTCR - 0xE001 8070)

The Count Control Register (CTCR) is used to select between Timer and Counter mode,
and in Counter mode to select the pin and edge(s) for counting. The function of each of
the bits is shown in Table 489.

Table 489: PWM Count control Register (PWM1CTCR - address 0xE001 8004) bit description
Value
1:0 Counter/ 00 Timer Mode: the TC is incremented when the Prescale 00
Timer Mode Counter matches the Prescale Register.
01 Counter Mode: the TC is incremented on rising edges of
the PCAP input selected by bits 3:2.
10 Counter Mode: the TC is incremented on falling edges of
11 Counter Mode: the TC is incremented on both edges of
3:2 Count Input When bits 1:0 of this register are not 00, these bits select 00
Select which PCAP pin which carries the signal used to
increment the TC.
00 PCAP1.0
01 CAP1.1 (Other combinations are reserved)
defined.
24.7.4 PWM Match Control Register (PWM1MCR - 0xE001 8014)

The PWM Match Control Registers are used to control what operations are performed
when one of the PWM Match Registers matches the PWM Timer Counter. The function of
each of the bits is shown in Table 490.
Table 490: Match Control Register (PWM1MCR - address 0xE000 8014) bit description
Value
0 PWMMR0I 1 Interrupt on PWMMR0: an interrupt is generated when 0
PWMMR0 matches the value in the PWMTC.
0 This interrupt is disabled.
1 PWMMR0R 1 Reset on PWMMR0: the PWMTC will be reset if PWMMR0 0
matches it.
2 PWMMR0S 1 Stop on PWMMR0: the PWMTC and PWMPC will be stopped 0
and PWMTCR[0] will be set to 0 if PWMMR0 matches the
PWMTC.
0 This feature is disabled
matches it.
PWMTC.

Value
matches it.
PWMTC.
matches it.
11 PWMMR3S 1 Stop on PWMMR3: The PWMTC and PWMPC will be 0
stopped and PWMTCR[0] will be set to 0 if PWMMR3
matches the PWMTC.
12 PWMMR4I 1 Interrupt on PWMMR4: An interrupt is generated when 0
matches it.
PWMTC.
15 PWMMR5I 1 Interrupt on PWMMR5: An interrupt is generated when 0
matches it.
PWMTC.

Value
matches it.
PWMTC.
24.7.5 PWM Capture Control Register (PWM1CCR - 0xE001 8028)

The Capture Control Register is used to control whether one of the four Capture Registers
is loaded with the value in the Timer Counter when a capture event occurs, and whether
an interrupt is generated by the capture event. Setting both the rising and falling bits at the
same time is a valid configuration, resulting in a capture event for both edges. In the
descriptions below, “n” represents the Timer number, 0 or 1.
Note: If Counter mode is selected for a particular CAP input in the CTCR, the 3 bits for
that input in this register should be programmed as 000, but capture and/or interrupt can
be selected for the other 3 CAP inputs.
Table 491: PWM Capture Control Register (PWM1CCR - address 0xE001 8028) bit description
Value
0 Capture on 0 This feature is disabled. 0
CAPn.0 rising 1 A synchronously sampled rising edge on the CAPn.0 input
edge will cause CR0 to be loaded with the contents of the TC.
CAPn.0 falling 1 A synchronously sampled falling edge on CAPn.0 will
edge cause CR0 to be loaded with the contents of TC.
2 Interrupt on 0 This feature is disabled. 0
CAPn.0 event 1 A CR0 load due to a CAPn.0 event will generate an
interrupt.
CAPn.1rising 1 A synchronously sampled rising edge on the CAPn.1 input
CAPn.1falling 1 A synchronously sampled falling edge on CAPn.1 will
interrupt.

Table 491: PWM Capture Control Register (PWM1CCR - address 0xE001 8028) bit description
Value
interrupt.
edge will cause CR3 to be loaded with the contents of TC.
interrupt.
24.7.6 PWM Control Registers (PWM1PCR - 0xE001 804C)

The PWM Control Registers are used to enable and select the type of each PWM
channel. The function of each of the bits are shown in Table 492.
Table 492: PWM Control Registers (PWM1PCR - address 0xE001 804C) bit description
Bit Symbol Valu Description Reset
e Value
1:0 Unused Unused, always zero. NA
2 PWMSEL2 1 Selects double edge controlled mode for the PWM2 output. 0
0 Selects single edge controlled mode for PWM2.
9 PWMENA1 1 The PWM1 output enabled. 0
0 The PWM1 output disabled.

Table 492: PWM Control Registers (PWM1PCR - address 0xE001 804C) bit description
Bit Symbol Valu Description Reset
e Value
31:15 Unused Unused, always zero. NA
24.7.7 PWM Latch Enable Register (PWM1LER - 0xE001 8050)

The PWM Latch Enable Registers are used to control the update of the PWM Match
registers when they are used for PWM generation. When software writes to the location of
a PWM Match register while the Timer is in PWM mode, the value is captured, but not
used immediately.
When a PWM Match 0 event occurs (normally also resetting the timer in PWM mode), the
contents of shadow registers will be transferred to the shadow registers if the
corresponding bit in the Latch Enable Register has been set. At that point, the new values
will take effect and determine the course of the next PWM cycle. Once the transfer of new
values has taken place, all bits of the LER are automatically cleared. Until the
corresponding bit in the PWMLER is set and a PWM Match 0 event occurs, any value
written to the PWM Match registers has no effect on PWM operation.
For example, if the PWM is configured for double edge operation and is currently running,
a typical sequence of events for changing the timing would be:
• Write a new value to the PWM Match1 register.

• Write a new value to the PWM Match2 register.
• Write to the PWMLER, setting bits 1 and 2 at the same time.
• The altered values will become effective at the next reset of the timer (when a PWM
Match 0 event occurs).
The order of writing the two PWM Match registers is not important, since neither value will
be used until after the write to LER. This insures that both values go into effect at the
same time, if that is required. A single value may be altered in the same way if needed.
The function of each of the bits in the LER is shown in Table 493.

Table 493: PWM Latch Enable Register (PWM1LER - address 0xE001 8050) bit description
Value
0 Enable PWM Writing a one to this bit allows the last value written to the PWM 0
Match 0 Latch Match 0 register to be become effective when the timer is next reset
by a PWM Match event. See Section 24.7.4 “PWM Match Control
Register (PWM1MCR - 0xE001 8014)”.

UM10211
Chapter 25: LPC23XX WatchDog Timer (WDT)
25.1 Features
• Internally resets chip if not periodically reloaded.
• Debug mode.
• Enabled by software but requires a hardware reset or a Watchdog reset/interrupt to be
disabled.
• Incorrect/Incomplete feed sequence causes reset/interrupt if enabled.
• Flag to indicate Watchdog reset.
• Programmable 32 bit timer with internal pre-scaler.
• Selectable time period from (TWDCLK  256  4) to (TWDCLK  232  4) in multiples of
TWDCLK  4.
• The Watchdog clock (WDCLK) source can be selected from the RTC clock, the
Internal RC oscillator (IRC), or the APB peripheral clock (PCLK, see Table 49). This
gives a wide range of potential timing choices for Watchdog operation under different
power reduction conditions. It also provides the ability to run the Watchdog timer from
an entirely internal source that is not dependent on an external crystal and its
associated components and wiring, for increased reliability.
25.2 Introduction
The purpose of the Watchdog is to reset the microcontroller within a reasonable amount of
time if it enters an erroneous state. When enabled, the Watchdog will generate a system
reset if the user program fails to "feed" (or reload) the Watchdog within a predetermined
amount of time.
For interaction of the on-chip watchdog and other peripherals, especially the reset and
boot-up procedures, please read Section 3.4 “Reset” on page 31 of this document.
25.3 Description
The Watchdog consists of a divide by 4 fixed pre-scaler and a 32 bit counter. The clock is
fed to the timer via a pre-scaler. The timer decrements when clocked. The minimum value
from which the counter decrements is 0xFF. Setting a value lower than 0xFF causes 0xFF
to be loaded in the counter. Hence the minimum Watchdog interval is (TWDCLK  256  4)
and the maximum Watchdog interval is (TWDCLK  232  4) in multiples of (TWDCLK  4).
The Watchdog should be used in the following manner:
• Set the Watchdog timer constant reload value in WDTC register.

• Setup mode in WDMOD register.
• Enable the Watchdog by writing 0xAA followed by 0x55 to the WDFEED register.
• Watchdog should be fed again before the Watchdog counter underflows to prevent
reset/interrupt.

When the Watchdog counter underflows, the program counter will start from 0x0000 0000
as in the case of external reset. The Watchdog time-out flag (WDTOF) can be examined
to determine if the Watchdog has caused the reset condition. The WDTOF flag must be
cleared by software.
The watchdog timer block uses two clocks: PCLK and WDCLK. PCLK is used for the APB
accesses to the watchdog registers. The WDCLK is used for the watchdog timer counting.
There is some synchronization logic between these two clock domains. When the
WDMOD and WDTC registers are updated by APB operations, the new value will take
effect in 3 WDCLK cycles on the logic in the WDCLK clock domain. When the watchdog
timer is counting on WDCLK, the synchronization logic will first lock the value of the
counter on WDCLK and then synchronize it with the PCLK for reading as the WDTV
register by the CPU.

The Watchdog contains 4 registers as shown in Table 494 below.
Table 494. Watchdog register map

Value[1]
WDMOD Watchdog mode register. This register contains R/W 0 0xE000 0000
the basic mode and status of the Watchdog
Timer.
WDTC Watchdog timer constant register. This register R/W 0xFF 0xE000 0004
determines the time-out value.
WDFEED Watchdog feed sequence register. Writing 0xAA WO NA 0xE000 0008
followed by 0x55 to this register reloads the
Watchdog timer with the value contained in
WDTC.
WDTV Watchdog timer value register. This register RO 0xFF 0xE000 000C
reads out the current value of the Watchdog
timer.
WDCLKSEL Watchdog clock source selection register. R/W 0 0xE000 0010
25.4.1 Watchdog Mode Register (WDMOD - 0xE000 0000)

The WDMOD register controls the operation of the Watchdog as per the combination of
WDEN and RESET bits.

Table 495. Watchdog operating modes selection

WDEN WDRESET Mode of Operation
0 X (0 or 1) Debug/Operate without the Watchdog running.
1 0 Watchdog interrupt mode: debug with the Watchdog interrupt but no
WDRESET enabled.
When this mode is selected, a watchdog counter underflow will set the
WDINT flag and the Watchdog interrupt request will be generated.
1 1 Watchdog reset mode: operate with the Watchdog interrupt and
WDRESET enabled.
When this mode is selected, a watchdog counter underflow will reset
the microcontroller. Although the Watchdog interrupt is also enabled in
this case (WDEN = 1) it will not be recognized since the watchdog
reset will clear the WDINT flag.
Once the WDEN and/or WDRESET bits are set they can not be cleared by software. Both
flags are cleared by an external reset or a Watchdog timer underflow.
WDTOF The Watchdog time-out flag is set when the Watchdog times out. This flag is
cleared by software.
WDINT The Watchdog interrupt flag is set when the Watchdog times out. This flag is
cleared when any reset occurs. Once the watchdog interrupt is serviced, it can be
disabled in the VIC or the watchdog interrupt request will be generated indefinitely.
Table 496: Watchdog Mode register (WDMOD - address 0xE000 0000) bit description
0 WDEN WDEN Watchdog interrupt enable bit (Set Only). 0
1 WDRESET WDRESET Watchdog reset enable bit (Set Only). 0
2 WDTOF WDTOF Watchdog time-out flag. 0 (Only after
external reset)
3 WDINT WDINT Watchdog interrupt flag (Read Only). 0
25.4.2 Watchdog Timer Constant Register (WDTC - 0xE000 0004)

The WDTC register determines the time-out value. Every time a feed sequence occurs
the WDTC content is reloaded in to the Watchdog timer. It’s a 32 bit register with 8 LSB
set to 1 on reset. Writing values below 0xFF will cause 0x0000 00FF to be loaded to the
WDTC. Thus the minimum time-out interval is TWDCLK  256  4.
Table 497: Watchdog Constant register (WDTC - address 0xE000 0004) bit description
31:0 Count Watchdog time-out interval. 0x0000 00FF
25.4.3 Watchdog Feed Register (WDFEED - 0xE000 0008)

Writing 0xAA followed by 0x55 to this register will reload the Watchdog timer with the
WDTC value. This operation will also start the Watchdog if it is enabled via the WDMOD
register. Setting the WDEN bit in the WDMOD register is not sufficient to enable the
Watchdog. A valid feed sequence must be completed after setting WDEN before the
Watchdog is capable of generating a reset. Until then, the Watchdog will ignore feed

errors. After writing 0xAA to WDFEED, access to any Watchdog register other than writing
0x55 to WDFEED causes an immediate reset/interrupt when the Watchdog is enabled.
The reset will be generated during the second PCLK following an incorrect access to a
Watchdog register during a feed sequence.
Interrupts should be disabled during the feed sequence. An abort condition will occur if an
interrupt happens during the feed sequence.
Table 498: Watchdog Feed Register (WDFEED - address 0xE000 0008) bit description
7:0 Feed Feed value should be 0xAA followed by 0x55. NA
25.4.4 Watchdog Timer Value Register (WDTV - 0xE000 000C)

The WDTV register is used to read the current value of Watchdog timer.
When reading the value of the 32 bit timer, the lock and synchronization procedure takes
up to 6 WDCLK cycles plus 6 PCLK cycles, so the value of WDTV is older than the actual
value of the timer when it's being read by the CPU.
Table 499: Watchdog Timer Value register (WDTV - address 0xE000 000C) bit description
31:0 Count Counter timer value. 0x0000 00FF
25.4.5 Watchdog Timer Clock Source Selection Register (WDCLKSEL -

0xE000 0010)
This register allows selecting the clock source for the Watchdog timer. The possibilities are: the
Internal RC oscillator (IRC), the RTC oscillator, and the APB peripheral clock (pclk). The function of
bits in WDCLKSEL are shown in Table 500.
Table 500: Watchdog Timer Clock Source Selection register (WDCLKSEL - address
Value
1:0 WDSEL These bits select the clock source for the Watchdog timer as 0
described below.
Warning: Improper setting of this value may result in incorrect
operation of the Watchdog timer, which could adversely affect
system operation.
00 Selects the Internal RC oscillator as the Watchdog clock source
(default).
01 Selects the APB peripheral clock (PCLK) as the Watchdog clock
source.
10 Selects the RTC oscillator as the Watchdog clock source.
11 Reserved

25.5 Block diagram

The block diagram of the Watchdog is shown below in the Figure 130. The
synchronization logic (PCLK - WDCLK) is not shown in the block diagram.
feed sequence
WDTC
feed ok
WDFEED
feed error
RTC oscillator wdclk
pclk 4 32 BIT DOWN COUNTER
internal RC oscillator
underflow enable
count
WDCLKSEL
SHADOW BIT
WMOD register
WDINT WDTOF WDRESET WDEN
reset
interrupt
Fig 130. Watchdog block diagram

UM10211
Chapter 26: LPC23XX Real Time Clock (RTC) and battery RAM

The RTC alarm output pin is available on parts LPC2377, LPC2378, and LPC2388 only.

The RTC is configured using the following registers:
1. Power: In the PCONP register (Table 56), set bits PCRTC.

Remark: On reset, the RTC is enabled.
2. Clock: Select clock source in Table 505. If the peripheral clock is selected, select
PCLK_RTC in the PCLK_SEL0 register (Table 49). For the RTC, the peripheral clock
must be scaled (see Section 26.7.6).
3. Interrupts: See Section 26.7.1 for RTC interrupt handling. Interrupts are enabled in
26.3 Features
• Measures the passage of time to maintain a calendar and clock.
• Ultra Low Power design to support battery powered systems.
• Provides Seconds, Minutes, Hours, Day of Month, Month, Year, Day of Week, and
Day of Year.
• Dedicated 32 kHz oscillator or programmable prescaler from APB clock.
• Dedicated power supply pin VBAT can be connected to a battery or to the main 3.3 V.
• An alarm output pin (LPC2377/78 and LPC2388 only) is included to assist in waking
up from Power-down modes and when the chip has had power removed to all
functions except the RTC and battery RAM.
• Periodic interrupts can be generated from increments of any field of the time registers
and selected fractional second values.
• 2 kB static RAM powered by VBAT.
• RTC and Battery RAM power supply is isolated from the rest of the chip.
26.4 Description
The Real Time Clock (RTC) is a set of counters for measuring time when system power is
on, and optionally when it is off. It uses little power in Power-down or Deep power-down
modes. On the LPC2300, the RTC can be clocked by a separate 32.768 KHz oscillator or
by a programmable prescale divider based on the APB clock. Also, the RTC is powered
by its own power supply pin, VBAT, which can be connected to a battery or to the same
3.3 V supply used by the rest of the device.

The VBAT pin supplies power to the RTC and the Battery RAM. These two functions
require a minimum of power to operate, which can be supplied by an external battery.
When the CPU and the rest of chip functions are stopped and power removed, the RTC
can supply an alarm output that can be used by external hardware to restore chip power
and resume operation. The alarm output has a nominal voltage swing of 1.8 V. Note that
the PLL is disabled when waking up from power-down. See Section 4.6.10 for the PLL
start-up procedure.
26.5 Architecture
RTC OSCILLATOR
CLK32k
MUX
CLOCK GENERATOR
REFERENCE CLOCK DIVIDER
(PRESCALER)
strobe
CLK1 CCLK
ALARM
TIME COUNTERS COMPARATORS
REGISTERS
counter COUNTER INCREMENT ALARM MASK

enables INTERRUPT ENABLE REGISTER
INTERRUPT GENERATOR
Fig 131. RTC block diagram

Table 501. RTC pin description
Name Type Description
RTCX1 I Input to the RTC oscillator circuit.
RTCX2 O Output from the RTC oscillator circuit.
Remark: If the RTC is not used, the RTCX1/2 pins can be left
floating.
VBAT I RTC power supply: 3.3 V on this pin supplies the power to the
RTC.
Remark: If the RTC is used, VBAT must be connected to either pin
VDD(3V3), VDD(DCDC)(3V3), or an independent power supply (external
battery). Otherwise, VBAT should be left floating. Do not ground
VBAT.


The RTC includes a number of registers. The address space is split into four sections by
functionality. The first eight addresses are the Miscellaneous Register Group
(Section 26.7.2). The second set of eight locations are the Time Counter Group
(Section 26.7.4). The third set of eight locations contain the Alarm Register Group
(Section 26.7.5). The remaining registers control the Reference Clock Divider.
The Real Time Clock includes the registers shown in Table 502. Detailed descriptions of
the registers follow. In these descriptions, for most of the registers the Reset Value column
shows "NC", meaning that these registers are Not Changed by a Reset. Software must
initialize these registers between power-on and setting the RTC into operation.
Table 502. Real Time Clock register map

Value[1]
ILR Interrupt Location Register R/W NC 0xE002 4000
CTC Clock Tick Counter RO NC 0xE002 4004
CCR Clock Control Register R/W NC 0xE002 4008
CIIR Counter Increment Interrupt Register R/W NC 0xE002 400C
AMR Alarm Mask Register R/W NC 0xE002 4010
CTIME0 Consolidated Time Register 0 RO NC 0xE002 4014
CTIME1 Consolidated Time Register 1 RO NC 0xE002 4018
CTIME2 Consolidated Time Register 2 RO NC 0xE002 401C
SEC Seconds Counter R/W NC 0xE002 4020
MIN Minutes Register R/W NC 0xE002 4024
HOUR Hours Register R/W NC 0xE002 4028
DOM Day of Month Register R/W NC 0xE002 402C
DOW Day of Week Register R/W NC 0xE002 4030
DOY Day of Year Register R/W NC 0xE002 4034
MONTH Months Register R/W NC 0xE002 4038
YEAR Years Register R/W NC 0xE002 403C
CISS Counter Increment select mask for R/W NC 0xE002 4040
Sub-Second interrupt
ALSEC Alarm value for Seconds R/W NC 0xE002 4060
ALMIN Alarm value for Minutes R/W NC 0xE002 4064
ALHOUR Alarm value for Seconds R/W NC 0xE002 4068
ALDOM Alarm value for Day of Month R/W NC 0xE002 406C
ALDOW Alarm value for Day of Week R/W NC 0xE002 4070
ALDOY Alarm value for Day of Year R/W NC 0xE002 4074
ALMON Alarm value for Months R/W NC 0xE002 4078
ALYEAR Alarm value for Year R/W NC 0xE002 407C

Table 502. Real Time Clock register map

Value[1]
PREINT Prescaler value, integer portion R/W 0 0xE002 4080
PREFRAC Prescaler value, fractional portion R/W 0 0xE002 4084
[1] Registers in the RTC other than those that are part of the Prescaler are not affected by chip Reset. These
registers must be initialized by software if the RTC is enabled. Reset Value reflects the data stored in used
bits only. It does not include reserved bits content.
26.7.1 RTC interrupts

Interrupt generation is controlled through the Interrupt Location Register (ILR), Counter
Increment Interrupt Register (CIIR), the alarm registers, and the Alarm Mask Register
(AMR). Interrupts are generated only by the transition into the interrupt state. The ILR
separately enables CIIR and AMR interrupts. Each bit in CIIR corresponds to one of the
time counters. If CIIR is enabled for a particular counter, then every time the counter is
incremented an interrupt is generated. The alarm registers allow the user to specify a date
and time for an interrupt to be generated. The AMR provides a mechanism to mask alarm
compares. If all non-masked alarm registers match the value in their corresponding time
counter, then an interrupt is generated.
The RTC interrupt can bring the microcontroller out of power-down mode if the RTC is
operating from its own oscillator on the RTCX1-2 pins. When the RTC interrupt is enabled
for wake-up and its selected event occurs, the oscillator wake-up cycle associated with
the XTAL1/2 pins is started. For details on the RTC based wake-up process see
Section 4.8.8 “Interrupt Wakeup Register (INTWAKE - 0xE01F C144)” on page 66 and
Section 4.9 “Wakeup timer” on page 70.
26.7.2 Miscellaneous register group
26.7.2.1 Interrupt Location Register (ILR - 0xE002 4000)

The Interrupt Location Register specifies which blocks are generating an interrupt (see
Table 503). Writing a one to the appropriate bit clears the corresponding interrupt. Writing
a zero has no effect. This allows the programmer to read this register and write back the
same value to clear only the interrupt that is detected by the read.
Table 503. Interrupt Location Register (ILR - address 0xE002 4000) bit description
value
0 RTCCIF When one, the Counter Increment Interrupt block generated an interrupt. NC
Writing a one to this bit location clears the counter increment interrupt.
1 RTCALF When one, the alarm registers generated an interrupt. Writing a one to NC
this bit location clears the alarm interrupt.
2 RTSSF When one, the Counter Increment Sub-Seconds interrupt is generated. NC
The interrupt rate is determined by the CISS register.

26.7.2.2 Clock Tick Counter Register (CTCR - 0xE002 4004)

The Clock Tick Counter is read only. It can be reset to zero through the Clock Control
Register (CCR). The CTC consists of the bits of the clock divider counter.
Table 504. Clock Tick Counter Register (CTCR - address 0xE002 4004) bit description
value
15:1 Clock Tick Prior to the Seconds counter, the CTC counts 32,768 clocks per NA
Counter second. Due to the RTC Prescaler, these 32,768 time increments may
not all be of the same duration. Refer to the Section 26.7.6.1
“Reference Clock Divider (Prescaler)” on page 592 for details.
If the RTC is driven by the external 32.786 kHz oscillator, subsequent read operations of
the CTCR may yield an incorrect result. The CTCR is implemented as a 15-bit ripple
counter so that not all 15 bits change simultaneously. The LSB changes first, then the
next, and so forth. Since the 32.786 kHz oscillator is asynchronous to the CPU clock, it is
possible for a CTC read to occur during the time when the CTCR bits are changing
resulting in an incorrect large difference between back-to-back reads.
If the RTC is driven by the PCLK, the CPU and the RTC are synchronous because both of
their clocks are driven from the PLL output. Therefore, incorrect consecutive reads can
not occur.
26.7.2.3 Clock Control Register (CCR - 0xE002 4008)

The clock register controls the operation of the clock divide circuit. Each bit of the clock
register is described in Table 505.
Table 505. Clock Control Register (CCR - address 0xE002 4008) bit description
value
0 CLKEN Clock Enable. When this bit is a one the time counters are enabled. NA
When it is a zero, they are disabled so that they may be initialized.
1 CTCRST CTC Reset. When one, the elements in the Clock Tick Counter are NA
reset. The elements remain reset until CCR[1] is changed to zero.
3:2 - Internal test mode controls. These bits must be 0 for normal RTC NA
operation.
4 CLKSRC If this bit is 0, the Clock Tick Counter takes its clock from the Prescaler, NA
as on earlier devices in the NXP Embedded ARM family. See
Section 4.7.4 for selection of the peripheral clock for the RTC. If this bit
is 1, the CTC takes its clock from the 32 kHz oscillator that’s connected
to the RTCX1 and RTCX2 pins (see Section 26.10 “RTC external
32 kHz oscillator component selection” for hardware details).
26.7.2.4 Counter Increment Interrupt Register (CIIR - 0xE002 400C)

The Counter Increment Interrupt Register (CIIR) gives the ability to generate an interrupt
every time a counter is incremented. This interrupt remains valid until cleared by writing a
one to bit zero of the Interrupt Location Register (ILR[0]).

Table 506. Counter Increment Interrupt Register (CIIR - address 0xE002 400C) bit description
value
0 IMSEC When 1, an increment of the Second value generates an interrupt. NA
1 IMMIN When 1, an increment of the Minute value generates an interrupt. NA
2 IMHOUR When 1, an increment of the Hour value generates an interrupt. NA
3 IMDOM When 1, an increment of the Day of Month value generates an NA
interrupt.
4 IMDOW When 1, an increment of the Day of Week value generates an interrupt. NA
5 IMDOY When 1, an increment of the Day of Year value generates an interrupt. NA
6 IMMON When 1, an increment of the Month value generates an interrupt. NA
7 IMYEAR When 1, an increment of the Year value generates an interrupt. NA
26.7.2.5 Counter Increment Select Mask Register (CISS - 0xE002 4040)

The CISS register provides a way to obtain millisecond-range periodic CPU interrupts
from the Real Time Clock. This can allow freeing up one of the general purpose timers, or
support power saving by putting the CPU into a reduced power mode between periodic
interrupts.
Carry out signals from different stages of the Clock Tick Counter are used to generate the
sub-second interrupts. The possibilities range from 16 counts of the CTC (about
488 microseconds), up to 2,048 counts of the CTC (about 62.5 milliseconds). The
available counts and corresponding times are given in Table 507.
Table 507. Counter Increment Select Mask register (CISS - address 0xE002 4040) bit description
value
2:0 SubSecSel SubSecSelSub-Second Select. This field selects a count for the sub-second interrupt as NC
follows:
000 An interrupt is generated on every 16 counts of the Clock Tick Counter. At 32.768 kHz,
this generates an interrupt approximately every 488 microseconds.
this generates an interrupt approximately every 977 microseconds.
this generates an interrupt approximately every 1.95 milliseconds.
6:3 Unused Reserved, user software should not write ones to reserved bits. The value read from a NA

Table 507. Counter Increment Select Mask register (CISS - address 0xE002 4040) bit description
value
7 SubSecEna Subsecond interrupt enable. NC
0 The sub-second interrupt is disabled.
1 The sub-second interrupt is enabled.
26.7.2.6 Alarm Mask Register (AMR - 0xE002 4010)

The Alarm Mask Register (AMR) allows the user to mask any of the alarm registers.
Table 508 shows the relationship between the bits in the AMR and the alarms. For the
alarm function, every non-masked alarm register must match the corresponding time
counter for an interrupt to be generated. The interrupt is generated only when the counter
comparison first changes from no match to match. The interrupt is removed when a one is
written to the appropriate bit of the Interrupt Location Register (ILR). If all mask bits are
set, then the alarm is disabled.
Table 508. Alarm Mask Register (AMR - address 0xE002 4010) bit description
value
0 AMRSEC When 1, the Second value is not compared for the alarm. NA
1 AMRMIN When 1, the Minutes value is not compared for the alarm. NA
2 AMRHOUR When 1, the Hour value is not compared for the alarm. NA
3 AMRDOM When 1, the Day of Month value is not compared for the alarm. NA
4 AMRDOW When 1, the Day of Week value is not compared for the alarm. NA
5 AMRDOY When 1, the Day of Year value is not compared for the alarm. NA
6 AMRMON When 1, the Month value is not compared for the alarm. NA
7 AMRYEAR When 1, the Year value is not compared for the alarm. NA
26.7.3 Consolidated time registers

The values of the Time Counters can optionally be read in a consolidated format which
allows the programmer to read all time counters with only three read operations. The
various registers are packed into 32 bit values as shown in Table 509, Table 510, and
Table 511. The least significant bit of each register is read back at bit 0, 8, 16, or 24.
The Consolidated Time Registers are read only. To write new values to the Time
Counters, the Time Counter addresses should be used.
26.7.3.1 Consolidated Time Register 0 (CTIME0 - 0xE002 4014)

The Consolidated Time Register 0 contains the low order time values: Seconds, Minutes,
Hours, and Day of Week.
Table 509. Consolidated Time register 0 (CTIME0 - address 0xE002 4014) bit description
value
5:0 Seconds Seconds value in the range of 0 to 59 NA
13:8 Minutes Minutes value in the range of 0 to 59 NA

value
20:16 Hours Hours value in the range of 0 to 23 NA
26:24 Day Of Week Day of week value in the range of 0 to 6 NA
26.7.3.2 Consolidated Time Register 1 (CTIME1 - 0xE002 4018)

The Consolidate Time Register 1 contains the Day of Month, Month, and Year values.
value
4:0 Day of Month Day of month value in the range of 1 to 28, 29, 30, or 31 NA
(depending on the month and whether it is a leap year).
11:8 Month Month value in the range of 1 to 12. NA
27:16 Year Year value in the range of 0 to 4095. NA
26.7.3.3 Consolidated Time Register 2 (CTIME2 - 0xE002 401C)

The Consolidate Time Register 2 contains just the Day of Year value.
Table 511. Consolidated Time register 2 (CTIME2 - address 0xE002 401C) bit description
value
11:0 Day of Year Day of year value in the range of 1 to 365 (366 for leap years). NA
26.7.4 Time Counter Group

The time value consists of the eight counters shown in Table 512 and Table 513. These
counters can be read or written at the locations shown in Table 513.
Table 512. Time Counter relationships and values

Counter Size Enabled by Minimum value Maximum value
Second 6 Clk1 (see Figure 131) 0 59
Minute 6 Second 0 59
Hour 5 Minute 0 23

Table 512. Time Counter relationships and values

Counter Size Enabled by Minimum value Maximum value
Day of Month 5 Hour 1 28, 29, 30 or 31
Day of Week 3 Hour 0 6
Day of Year 9 Hour 1 365 or 366 (for leap year)
Month 4 Day of Month 1 12
Year 12 Month or day of Year 0 4095
Table 513. Time Counter registers

Name Size Description Access Address
SEC 6 Seconds value in the range of 0 to 59 R/W 0xE002 4020
MIN 6 Minutes value in the range of 0 to 59 R/W 0xE002 4024
HOUR 5 Hours value in the range of 0 to 23 R/W 0xE002 4028
DOM 5 Day of month value in the range of 1 to 28, 29, 30, R/W 0xE002 402C
or 31 (depending on the month and whether it is a
leap year).[1]
DOW 3 Day of week value in the range of 0 to 6[1] R/W 0xE002 4030
DOY 9 Day of year value in the range of 1 to 365 (366 for R/W 0xE002 4034
leap years)[1]
MONTH 4 Month value in the range of 1 to 12 R/W 0xE002 4038
YEAR 12 Year value in the range of 0 to 4095 R/W 0xE002 403C
[1] These values are simply incremented at the appropriate intervals and reset at the defined overflow point.
They are not calculated and must be correctly initialized in order to be meaningful.
26.7.4.1 Leap year calculation

The RTC does a simple bit comparison to see if the two lowest order bits of the year
counter are zero. If true, then the RTC considers that year a leap year. The RTC considers
all years evenly divisible by 4 as leap years. This algorithm is accurate from the year 1901
through the year 2099, but fails for the year 2100, which is not a leap year. The only effect
of leap year on the RTC is to alter the length of the month of February for the month, day
of month, and year counters.
26.7.5 Alarm register group

The alarm registers are shown in Table 514. The values in these registers are compared
with the time counters. If all the unmasked (See Section 26.7.2.6 “Alarm Mask Register
(AMR - 0xE002 4010)” on page 589) alarm registers match their corresponding time
counters then an interrupt is generated. The interrupt is cleared when a one is written to
bit one of the Interrupt Location Register (ILR[1]).
Table 514. Alarm registers

ALSEC 6 Alarm value for Seconds R/W 0xE002 4060
ALMIN 6 Alarm value for Minutes R/W 0xE002 4064
ALHOUR 5 Alarm value for Hours R/W 0xE002 4068
ALDOM 5 Alarm value for Day of Month R/W 0xE002 406C
ALDOW 3 Alarm value for Day of Week R/W 0xE002 4070

Table 514. Alarm registers

ALDOY 9 Alarm value for Day of Year R/W 0xE002 4074
ALMON 4 Alarm value for Months R/W 0xE002 4078
ALYEAR 12 Alarm value for Years R/W 0xE002 407C
26.7.6 RTC clock generation

The RTC may be clocked by either the 32.786 kHz RTC oscillator or by the APB
peripheral clock (PCLK) after adjustment by the reference clock divider.
26.7.6.1 Reference Clock Divider (Prescaler)

The reference clock divider (hereafter referred to as the Prescaler) may be used when the
RTC clock source is not supplied by the RTC oscillator, but comes from the APB
peripheral clock (PCLK).
The Prescaler allows generation of a 32.768 kHz reference clock from any PCLK
frequency greater than or equal to 65.536 kHz (2  32.768 kHz). This permits the RTC to
always run at the proper rate regardless of the peripheral clock rate. Basically, the
Prescaler divides PCLK by a value which contains both an integer portion and a fractional
portion. The result is not a continuous output at a constant frequency, some clock periods
will be one PCLK longer than others. However, the overall result can always be 32,768
counts per second.
The reference clock divider consists of a 13 bit integer counter and a 15 bit fractional
counter. The reasons for these counter sizes are as follows:
1. For frequencies that are expected to be supported by the LPC2300, a 13 bit integer
counter is required. This can be calculated as 160 MHz divided by 32,768 minus 1
equals 4881 with a remainder of 26,624. Thirteen bits are needed to hold the value
4881, but actually supports frequencies up to 268.4 MHz (32,768  8192).
2. The remainder value could be as large as 32,767, which requires 15 bits.
Table 515. Reference Clock Divider registers

PREINT 13 Prescale Value, integer portion R/W 0xE002 4080
PREFRAC 15 Prescale Value, fractional portion R/W 0xE002 4084
26.7.6.2 Prescaler Integer Register (PREINT - 0xE002 4080)

This is the integer portion of the prescale value, calculated as:
PREINT = int (PCLK/32768) - 1. The value of PREINT must be greater than or equal to 1.
Table 516: Prescaler Integer register (PREINT - address 0xE002 4080) bit description
Value
12:0 Prescaler Integer Contains the integer portion of the RTC prescaler value. 0

26.7.6.3 Prescaler Fraction Register (PREFRAC - 0xE002 4084)

This is the fractional portion of the prescale value, and may be calculated as:
PREFRAC = PCLK - ((PREINT + 1) x 32768).
Table 517: Prescaler Integer register (PREFRAC - address 0xE002 4084) bit description
Value
14:0 Prescaler Contains the integer portion of the RTC prescaler value. 0
Fraction
15 - Reserved, user software should not write ones to reserved NA
26.7.6.4 Example of Prescaler Usage

In a simplistic case, the PCLK frequency is 65.537 kHz. So:
PREINT = int (PCLK / 32768) - 1 = 1 and

PREFRAC = PCLK - ([PREINT + 1] x 32768) = 1
With this prescaler setting, exactly 32,768 clocks per second will be provided to the RTC
by counting 2 PCLKs 32,767 times, and 3 PCLKs once.
In a more realistic case, the PCLK frequency is 10 MHz. Then,
PREINT = int (PCLK / 32768) - 1 = 304 and

PREFRAC = PCLK - ([PREINT + 1] x 32768) = 5,760.
In this case, 5,760 of the prescaler output clocks will be 306 (305+1) PCLKs long, the rest
will be 305 PCLKs long.
In a similar manner, any PCLK rate greater than 65.536 kHz (as long as it is an even
number of cycles per second) may be turned into a 32 kHz reference clock for the RTC.
The only caveat is that if PREFRAC does not contain a zero, then not all of the 32,768 per
second clocks are of the same length. Some of the clocks are one PCLK longer than
others. While the longer pulses are distributed as evenly as possible among the remaining
pulses, this "jitter" could possibly be of concern in an application that wishes to observe
the contents of the Clock Tick Counter (CTC) directly(Section 26.7.2.2 “Clock Tick
Counter Register (CTCR - 0xE002 4004)” on page 587).

PCLK
to clock tick counter (APB clock)
CLK
CLK UNDERFLOW 15 BIT FRACTION COUNTER

13 BIT INTEGER COUNTER
(DOWN COUNTER)
RELOAD
15
COMBINATORIAL LOGIC
13 extend
reload
15
13 BIT RELOAD INTEGER 15 BIT FRACTION REGISTER

REGISTER (PREFRAC)
(PREINT)
13 15
APB bus
Fig 132. RTC prescaler block diagram
26.7.6.5 Prescaler operation

The Prescaler block labelled "Combination Logic" in Figure 132 determines when the
decrement of the 13 bit PREINT counter is extended by one PCLK. In order to both insert
the correct number of longer cycles, and to distribute them evenly, the combinatorial Logic
associates each bit in PREFRAC with a combination in the 15 bit Fraction Counter. These
associations are shown in the following Table 518.
For example, if PREFRAC bit 14 is a one (representing the fraction 1/2), then half of the
cycles counted by the 13 bit counter need to be longer. When there is a 1 in the LSB of the
Fraction Counter, the logic causes every alternate count (whenever the LSB of the
Fraction Counter=1) to be extended by one PCLK, evenly distributing the pulse widths.
Similarly, a one in PREFRAC bit 13 (representing the fraction 1/4) will cause every fourth
cycle (whenever the two LSBs of the Fraction Counter = 10) counted by the 13 bit counter
to be longer.

Table 518. Prescaler cases where the Integer Counter reload value is incremented
Fraction Counter PREFRAC Bit
14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
--- ---- ---- ---1 1 - - - - - - - - - - - - - -
--- ---- ---- --10 - 1 - - - - - - - - - - - - -
--- ---- ---- -100 - - 1 - - - - - - - - - - - -
--- ---- ---- 1000 - - - 1 - - - - - - - - - - -
--- ---- ---1 0000 - - - - 1 - - - - - - - - - -
--- ---- --10 0000 - - - - - 1 - - - - - - - - -
--- ---- -100 0000 - - - - - - 1 - - - - - - - -
--- ---- 1000 0000 - - - - - - - 1 - - - - - - -
--- ---1 0000 0000 - - - - - - - - 1 - - - - - -
--- --10 0000 0000 - - - - - - - - - 1 - - - - -
--- -100 0000 0000 - - - - - - - - - - 1 - - - -
--- 1000 0000 0000 - - - - - - - - - - - 1 - - -
--1 0000 0000 0000 - - - - - - - - - - - - 1 - -
-10 0000 0000 0000 - - - - - - - - - - - - - 1 -
100 0000 0000 0000 - - - - - - - - - - - - - - 1
26.8 RTC usage notes

The RTC may be clocked by either the 32.786 kHz RTC oscillator, or by the APB
peripheral clock (PCLK) after adjustment by the reference clock divider.
If the RTC is used, VBAT must be connected to either pin VDD(3V3) or an independent
power supply (external battery). Otherwise, VBAT should be left floating. Do not ground
VBAT. No provision is made in the LPC2300 to retain RTC status upon the VBAT power
loss, or to maintain time incrementation if the clock source is lost, interrupted, or altered.
Since the RTC operates using one of two available clocks (the APB clock (PCLK) or the
32 kHz signal coming from the RTCX1-2 pins), any interruption of the selected clock will
cause the time to drift away from the time value it would have provided otherwise. The
variance could be to actual clock time if the RTC was initialized to that, or simply an error
in elapsed time since the RTC was activated.
While the signal from RTCX1-2 pins can be used to supply the RTC clock at anytime,
selecting the PCLK as the RTC clock and entering the Power-down mode will cause a
lapse in the time update. Also, feeding the RTC with the PCLK and altering this timebase
during system operation (by reconfiguring the PLL, the APB divider, or the RTC prescaler)
will result in some form of accumulated time error. Accumulated time errors may occur in
case RTC clock source is switched between the PCLK to the RTCX pins, too.
Once the 32 kHz signal from RTCX1-2 pins is selected as a clock source, the RTC can
operate completely without the presence of the APB clock (PCLK). Therefore, power
sensitive applications (i.e. battery powered application) utilizing the RTC will reduce the

power consumption by using the signal from RTCX1-2 pins, and writing a 0 into the
PCRTC bit in the PCONP power control register (see Section 4.8 “Power control” on page
63).
Remark: Note that if the RTC is running from the 32 kHz signal and powered by VBAT, the
internal registers can be read. However, they cannot be written to unless the PCRTC bit in
the PCONP register is set to 1. This restriction does not apply to the time counter
registers.
26.8.1 Alarm output

The RTC includes an alarm output pin that reflects both the alarm comparisons and
interrupts from the RTC. This pin is in the RTC power domain, and therefore it is available
during all power saving modes as long as power is supplied to VBAT. Since the Alarm pin
combines the alarm and interrupt functions of the RTC, either a specific time/date/etc. or a
periodic interval can be provided to the outside world. For example, a time of day alarm
could be used to tell external circuitry to turn on power to the LPC2300 in order to wake up
from Deep power-down mode.
26.9 Battery RAM

The Battery RAM is a 2 kB static RAM residing on the APB bus. The address range is
0xE008 4000 to 0xE008 47FF. The SRAM can be accessed word-wise (32-bit) only.
The Battery RAM is powered from the VBAT pin along with the RTC, both of which exist in
a power domain that is isolated from the rest of the chip. This allows them to operate while
the main chip power has been removed.
26.10 RTC external 32 kHz oscillator component selection

The RTC external oscillator circuit is shown in Figure 133. Since the feedback resistance
is integrated on chip, only a crystal, the capacitances CX1 and CX2 need to be connected
externally to the microcontroller.
LPC23xx
RTCX1 RTCX2
32 kHz
CX1 CX2
Xtal
Fig 133. RTC 32 kHz crystal oscillator circuit

Table 519 gives the crystal parameters that should be used. CL is the typical load
capacitance of the crystal and is usually specified by the crystal manufacturer. The actual
CL influences oscillation frequency. When using a crystal that is manufactured for a
different load capacitance, the circuit will oscillate at a slightly different frequency
(depending on the quality of the crystal) compared to the specified one. Therefore for an
accurate time reference it is advised to use the load capacitors as specified in Table 519
that belong to a specific CL. The value of external capacitances CX1 and CX2 specified in
this table are calculated from the internal parasitic capacitances and the CL. Parasitics
from PCB and package are not taken into account.
Table 519. Recommended values for the RTC external 32 kHz oscillator CX1/X2 components
Crystal load capacitance Maximum crystal series External load capacitors CX1, CX2
CL resistance RS
11 pF < 100 k 18 pF, 18 pF
13 pF < 100 k 22 pF, 22 pF
15 pF < 100 k 27 pF, 27 pF

UM10211
Chapter 27: LPC23XX Analog-to-Digital Converter (ADC)

On the LPC23XX, the number of ADC channels is dependent on the part:
• LPC2361/62/64/65/66/67/68 and LPC2387: 6 channels

• LPC2377/78 and LPC2388: 8 channels
Registers for ADC channels 6 and 7 are reserved on the LPC2361/62/64/65/66/67/68 and
LPC2387 parts.

The ADC is configured using the following registers:
1. Power: In the PCONP register (Table 56), set bits PCADC.

Remark: On reset, the ADC is disabled. To enable the ADC, first set the PCADC bit,
and then enable the ADC in the AD0CR register (bit PDN) Table 522. To disable the
ADC, first clear the PDN bit, and then clear the PCADC bit.
2. Clock: In the PCLK_SEL0 register (Table 49), select PCLK_ADC. To scale the clock
for the ADC, see Table 522 bits CLKDIV.
3. Pins: Select ADC pins and pin modes in registers PINSELn and PINMODEn (see
Section 9.5).
4. Interrupts: To enable interrupts in the ADC, see Table 525. Interrupts are enabled in
27.3 Features
• 10 bit successive approximation analog to digital converter.
• Input multiplexing among 6 pins or 8 pins.
• Power down mode.
• Measurement range 0 to 3 V.
• 10 bit conversion time  2.44 s.
• Burst conversion mode for single or multiple inputs.
• Optional conversion on transition on input pin or Timer Match signal.
• Individual result registers for each A/D channel to reduce interrupt overhead.
27.4 Description
Basic clocking for the A/D converters is provided by the APB peripheral clock PCLK_ADC
(see Section 4.7.4). A programmable divider is included in each converter to scale this
clock to the 4.5 MHz (max) clock needed by the successive approximation process. A fully
accurate conversion requires 11 of these clocks.


Table 520 gives a brief summary of each of ADC related pins.
Table 520. A/D pin description

AD0[5:0] or Input Analog Inputs. The A/D converter cell can measure the voltage on any of these input signals.
AD0[7:0] Note: while the ADC pins are specified as 5 V tolerant (see Section 8.1), the analog multiplexing
in the ADC block is not. More than VDD(3V3)/VREF/3.3 V (VDDA) should not be applied to any pin
that is selected as an ADC input, or the ADC reading will be incorrect. If for example AD0.0 and
AD0.1 are used as the ADC0 inputs and voltage on AD0.0 = 4.5 V while AD0.1 = 2.5 V, an
excessive voltage on the AD0.0 can cause an incorrect reading of the AD0.1, although the AD0.1
input voltage is within the right range.
If the A/D converter is not used in an application then the pins associated with A/D inputs can be
used as 5V tolerant digital IO pins
VREF Reference Voltage Reference. This pin provides a voltage reference level for the A/D converter.
VDDA , Power Analog Power and Ground. These should be nominally the same voltages as VDD(3V3) and VSS
VSSA respectively but should be isolated to minimize noise and error.
Remark: When the ADC is not used, the VDDA and VREF pins must be connected to the
power supply, and pin VSSA must be grounded. These pins should not be left floating.

The base address of the ADC is 0xE003 4000. The A/D Converter includes registers as
shown in Table 521.
Table 521. A/D registers

Value[1]
AD0CR A/D Control Register. The AD0CR register R/W 0x0000 0001 0xE003 4000
must be written to select the operating mode
before A/D conversion can occur.
AD0GDR A/D Global Data Register. Contains the result R/W NA 0xE003 4004
of the most recent A/D conversion.
AD0STAT A/D Status Register. This register contains RO 0 0xE003 4030
DONE and OVERRUN flags for all of the A/D
channels, as well as the A/D interrupt flag.
AD0INTEN A/D Interrupt Enable Register. This register R/W 0x0000 0100 0xE003 400C
contains enable bits that allow the DONE flag
of each A/D channel to be included or
excluded from contributing to the generation
of an A/D interrupt.
AD0DR0 A/D Channel 0 Data Register. This register R/W NA 0xE003 4010
contains the result of the most recent
conversion completed on channel 0
conversion completed on channel 1.

Table 521. A/D registers

Value[1]
AD0DR3 A/D Channel 3 Data Register. This register R/W NA 0xE003 401C
AD0DR7 A/D Channel 7 Data Register. This register R/W NA 0xE003 402C
27.6.1 A/D Control Register (AD0CR - 0xE003 4000)

The A/D Control Register provides bits to select A/D channels to be converted, A/D timing,
A/D modes, and the A/D start trigger.
Table 522: A/D Control Register (AD0CR - address 0xE003 4000) bit description
Value
7:0 SEL Selects which of the AD0.7:0 pins is (are) to be sampled and converted. For AD0, bit 0 0x01
selects Pin AD0.0, and bit 7 selects pin AD0.7. In software-controlled mode, only one of
these bits should be 1. In hardware scan mode, any value containing 1 to 8 ones. All
zeroes is equivalent to 0x01.
15:8 CLKDIV The APB clock (PCLK) is divided by (this value plus one) to produce the clock for the A/D 0
converter, which should be less than or equal to 4.5 MHz. Typically, software should
program the smallest value in this field that yields a clock of 4.5 MHz or slightly less, but in
certain cases (such as a high-impedance analog source) a slower clock may be
desirable.
16 BURST 0 Conversions are software controlled and require 11 clocks. 0
1 The AD converter does repeated conversions at the rate selected by the CLKS field,
scanning (if necessary) through the pins selected by 1s in the SEL field. The first
conversion after the start corresponds to the least-significant 1 in the SEL field, then
higher numbered 1 bits (pins) if applicable. Repeated conversions can be terminated by
clearing this bit, but the conversion that’s in progress when this bit is cleared will be
completed.
Important: START bits must be 000 when BURST = 1 or conversions will not start.

Table 522: A/D Control Register (AD0CR - address 0xE003 4000) bit description
Value
19:17 CLKS This field selects the number of clocks used for each conversion in Burst mode, and the 000
number of bits of accuracy of the result in the LS bits of ADDR, between 11 clocks
(10 bits) and 4 clocks (3 bits).
000 11 clocks / 10 bits
20 Reserved, user software should not write ones to reserved bits. The value read from a NA
21 PDN 1 The A/D converter is operational. 0
0 The A/D converter is in power-down mode.
26:24 START When the BURST bit is 0, these bits control whether and when an A/D conversion is 0
started:
000 No start (this value should be used when clearing PDN to 0).
001 Start conversion now.
010 Start conversion when the edge selected by bit 27 occurs on P2.10/EINT0.
011 Start conversion when the edge selected by bit 27 occurs on P1.27/CAP0.1.
100 Start conversion when the edge selected by bit 27 occurs on MAT0.1.
101 Start conversion when the edge selected by bit 27 occurs on MAT0.3[1].
27 EDGE This bit is significant only when the START field contains 010-111. In these cases: 0
1 Start conversion on a falling edge on the selected CAP/MAT signal.
0 Start conversion on a rising edge on the selected CAP/MAT signal.
[1] Function not pinned out on LPC2300.
27.6.2 A/D Global Data Register (AD0GDR - 0xE003 4004)

The A/D Global Data Register contains the result of the most recent A/D conversion. This
includes the data, DONE, and Overrun flags, and the number of the A/D channel to which
the data relates.

Table 523: A/D Global Data Register (AD0GDR - address 0xE003 4004) bit description
Value
5:0 Unused These bits always read as zeroes. They provide compatible expansion 0
room for future, higher-resolution A/D converters.
15:6 V/VREF When DONE is 1, this field contains a binary fraction representing the X
voltage on the Ain pin selected by the SEL field, divided by the voltage
on the VDDA pin. Zero in the field indicates that the voltage on the Ain
pin was less than, equal to, or close to that on VSSA, while 0x3FF
indicates that the voltage on Ain was close to, equal to, or greater than
that on VREF.
23:16 Unused These bits always read as zeroes. They allow accumulation of 0
successive A/D values without AND-masking, for at least 256 values
without overflow into the CHN field.
26:24 CHN These bits contain the channel from which the LS bits were converted. X
29:27 Unused These bits always read as zeroes. They could be used for expansion of 0
the CHN field in future compatible A/D converters that can convert more
channels.
30 OVERU This bit is 1 in burst mode if the results of one or more conversions was 0
N (were) lost and overwritten before the conversion that produced the
result in the LS bits. In non-FIFO operation, this bit is cleared by reading
this register.
31 DONE This bit is set to 1 when an A/D conversion completes. It is cleared 0
when this register is read and when the ADCR is written. If the ADCR is
written while a conversion is still in progress, this bit is set and a new
conversion is started.
27.6.3 A/D Status Register (AD0STAT - 0xE003 4030)

The A/D Status register allows checking the status of all A/D channels simultaneously.
The DONE and OVERRUN flags appearing in the ADDRn register for each A/D channel
are mirrored in ADSTAT. The interrupt flag (the logical OR of all DONE flags) is also found
in ADSTAT.
Table 524: A/D Status Register (AD0STAT - address 0xE003 4030) bit description
Value
7:0 Done7:0 These bits mirror the DONE status flags that appear in the result 0
register for each A/D channel.
15:8 Overrun7:0 These bits mirror the OVERRRUN status flags that appear in the 0
result register for each A/D channel. Reading ADSTAT allows
checking the status of all A/D channels simultaneously.
16 ADINT This bit is the A/D interrupt flag. It is one when any of the individual 0
A/D channel Done flags is asserted and enabled to contribute to the
A/D interrupt via the ADINTEN register.
31:17 Unused Unused, always 0. 0

27.6.4 A/D Interrupt Enable Register (AD0INTEN - 0xE003 400C)

This register allows control over which A/D channels generate an interrupt when a
conversion is complete. For example, it may be desirable to use some A/D channels to
monitor sensors by continuously performing conversions on them. The most recent
results are read by the application program whenever they are needed. In this case, an
interrupt is not desirable at the end of each conversion for some A/D channels.
Table 525: A/D Interrupt Enable Register (AD0INTEN - address 0xE003 400C) bit description
Value
7:0 ADINTEN 7:0 These bits allow control over which A/D channels generate 0x00
interrupts for conversion completion. When bit 0 is one, completion
of a conversion on A/D channel 0 will generate an interrupt, when bit
1 is one, completion of a conversion on A/D channel 1 will generate
an interrupt, etc.
8 ADGINTEN When 1, enables the global DONE flag in ADDR to generate an 1
interrupt. When 0, only the individual A/D channels enabled by
ADINTEN 7:0 will generate interrupts.
27.6.5 A/D Data Registers (AD0DR0 to AD0DR7 - 0xE003 4010 to

0xE003 402C)
The A/D Data Register hold the result when an A/D conversion is complete, and also
include the flags that indicate when a conversion has been completed and when a
conversion overrun has occurred.
Table 526: A/D Data Registers (AD0DR0 to AD0DR7 - addresses 0xE003 4010 to
0xE003 402C) bit description
Value
These bits always read as zeroes. They provide compatible expansion
room for future, higher-resolution ADCs.
15:6 V/VREF When DONE is 1, this field contains a binary fraction representing the NA
voltage on the Ain pin, divided by the voltage on the Vref pin. Zero in
the field indicates that the voltage on the Ain pin was less than, equal
to, or close to that on VREF, while 0x3FF indicates that the voltage on
Ain was close to, equal to, or greater than that on Vref.
29:16 Unused These bits always read as zeroes. They allow accumulation of 0
successive A/D values without AND-masking, for at least 256 values
without overflow into the CHN field.
30 OVERRUN This bit is 1 in burst mode if the results of one or more conversions 0
was (were) lost and overwritten before the conversion that produced
the result in the LS bits.This bit is cleared by reading this register.
31 DONE This bit is set to 1 when an A/D conversion completes. It is cleared 0
when this register is read.

27.7 Operation
27.7.1 Hardware-triggered conversion

If the BURST bit in the ADCR is 0 and the START field contains 010-111, the A/D
converter will start a conversion when a transition occurs on a selected pin or Timer Match
signal. The choices include conversion on a specified edge of any of 4 Match signals, or
conversion on a specified edge of either of 2 Capture/Match pins. The pin state from the
selected pad or the selected Match signal, XORed with ADCR bit 27, is used in the edge
detection logic.
27.7.2 Interrupts
An interrupt is requested to the Vectored Interrupt Controller (VIC) when the ADINT bit in
the ADSTAT register is 1. The ADINT bit is one when any of the DONE bits of A/D
channels that are enabled for interrupts (via the ADINTEN register) are one. Software
can use the Interrupt Enable bit in the VIC that corresponds to the ADC to control whether
this results in an interrupt. The result register for an A/D channel that is generating an
interrupt must be read in order to clear the corresponding DONE flag.
27.7.3 Accuracy vs. Digital Receiver

While the A/D converter can be used to measure the voltage on any AIN pin, regardless of
the pin’s setting in the Pin Select register (Table 104 “Pin Connect Block Register Map” on
page 155), selecting the AIN function improves the conversion accuracy by disabling the
pin’s digital receiver.

UM10211
Chapter 28: LPC23XX Digital-to Analog Converter (DAC)

The DAC is configured using the following registers:
1. Power: The DAC is always on.

2. Clock: In the PCLK_SEL0 register (Table 49), select PCLK_DAC.
3. Pins: Select the DAC pin and pin mode in registers PINSEL1 and PINMODE1 (see
Section 9.5).
28.2 Features
• 10 bit digital to analog converter
• Resistor string architecture
• Buffered output
• Power down mode
• Selectable speed vs. power

Table 527 gives a brief summary of each of DAC related pins.
Table 527. D/A Pin Description

AOUT Output Analog Output. After the selected settling time after the DACR is
written with a new value, the voltage on this pin (with respect to
VSSA) is VALUE/1024  VREF.
VREF Reference Voltage Reference. This pin provides a voltage reference level for
the D/A converter.
VDDA, VSSA Power Analog Power and Ground. These should be nominally the same
voltages as VDD(3V3) and VSS, but should be isolated to minimize
noise and error.
Remark: When the DAC is not used, the VDDA and VREF pins must be connected to the
power supply, and pin VSSA must be grounded. These pins should not be left floating.
28.4 Register description (DACR - 0xE006 C000)

This read/write register includes the digital value to be converted to analog, and a bit that
trades off performance vs. power. Bits 5:0 are reserved for future, higher-resolution D/A
converters.

Table 528: D/A Converter Register (DACR - address 0xE006 C000) bit description
Value
15:6 VALUE After the selected settling time after this field is written with a 0
new VALUE, the voltage on the AOUT pin (with respect to VSSA)
is VALUE/1024  VREF.
16 BIAS 0 The settling time of the DAC is 1 s max, and the maximum 0
current is 700 A.
1 The settling time of the DAC is 2.5 s and the maximum
current is 350 A.
28.5 Operation
Bits 21:20 of the PINSEL1 register (Section 9.5.2 “Pin Function Select Register 1
(PINSEL1 - 0xE002 C004)” on page 157) control whether the DAC is enabled and
controlling the state of pin P0.26/AD0.3/AOUT/RXD3. When these bits are 10, the DAC is
powered on and active.
The settling times noted in the description of the BIAS bit are valid for a capacitance load
on the AOUT pin not exceeding 100 pF. A load impedance value greater than that value
will cause settling time longer than the specified time. One or more graph(s) of load
impedance vs. settling time will be included in the final data sheet.

UM10211
Chapter 29: LPC23XX Flash memory programming firmware
29.1 Introduction
The boot loader controls initial operation after reset and also provides the tools for
programming the flash memory. This could be initial programming of a blank device,
erasure and re-programming of a previously programmed device, or programming of the
flash memory by the application program in a running system.
29.2 Features
• In-System Programming: In-System programming (ISP) is programming or
reprogramming the on-chip flash memory, using the boot loader software and UART0
serial port. This can be done when the part resides in the end-user board.
• In Application Programming: In-Application (IAP) programming is performing erase
and write operation on the on-chip flash memory, as directed by the end-user
application code.
29.3 Description
The flash boot loader code is executed every time the part is powered on or reset. The
loader can execute the ISP command handler or the user application code. A LOW level
after reset at the P2.10 pin is considered as an external hardware request to start the ISP
command handler. Assuming that power supply pins are on their nominal levels when the
rising edge on RESET pin is generated, it may take up to 3 ms before P2.10 is sampled
and the decision on whether to continue with user code or ISP handler is made. If P2.10 is
sampled low and the watchdog overflow flag is set, the external hardware request to start
the ISP command handler is ignored. If there is no request for the ISP command handler
execution (P2.10 is sampled HIGH after reset), a search is made for a valid user program.
If a valid user program is found then the execution control is transferred to it. If a valid user
program is not found, the auto-baud routine is invoked.
Pin P2.10 that is used as hardware request for ISP requires special attention. Since P2.10
is in high impedance mode after reset, it is important that the user provides external
hardware (a pull-up resistor or other device) to put the pin in a defined state. Otherwise
unintended entry into ISP mode may occur.
When ISP mode is entered after a power on reset, the IRC and PLL are used to generate
the CCLK of 14.748 MHz. The baud rates that can easily be obtained in this case are:
9600 Bd, 19200 Bd, 38400 Bd, 57600 Bd, 115200 Bd, and 230400 Bd. This may not be
the case when ISP is invoked by the user application (see Section 29.8.8 “Reinvoke ISP”
on page 627).
29.3.1 Memory map after any reset

The flash portion of the boot block is 8 kB in size and resides in the top portion (starting
from 0x0007 E000) of the on-chip flash memory. After any reset the entire boot block is
also mapped to the top of the on-chip memory space i.e. the boot block is also visible in
the memory region starting from the address 0x7FFF E000. The flash boot loader is

designed to run from this memory area, but both the ISP and IAP software use parts of the
on-chip RAM. The RAM usage is described later in this chapter. The interrupt vectors
residing in the boot block of the on-chip flash memory also become active after reset, i.e.,
the bottom 64 bytes of the boot block are also visible in the memory region starting from
the address 0x0000 0000. The reset vector contains a jump instruction to the entry point
of the flash boot loader software.
2.0 GB 0x7FFF FFFF

8 kB BOOT BLOCK
(RE-MAPPED FROM TOP OF FLASH MEMORY)
2.0 GB - 8 kB (BOOT BLOCK INTERRUPT VECTORS) 0x7FFF E000
0x0007 FFFF
8 kB BOOT BLOCK RE-MAPPED TO
HIGHER ADDRESS RANGE
0x0007 E000
ON-CHIP FLASH MEMORY
ACTIVE INTERRUPT VECTORS

FROM THE BOOT BLOCK
0.0 GB 0x0000 0000
Fig 134. Map of lower memory after reset
29.3.1.1 Criterion for Valid User Code

Criterion for valid user code: The reserved ARM interrupt vector location (0x0000 0014)
should contain the 2’s complement of the check-sum of the remaining interrupt vectors.
This causes the checksum of all of the vectors together to be 0. The boot loader code
disables the overlaying of the interrupt vectors from the boot block, then checksums the
interrupt vectors in sector 0 of the flash. If the signatures match then the execution control
is transferred to the user code by loading the program counter with 0x0000 0000. Hence
the user flash reset vector should contain a jump instruction to the entry point of the user
application code.
If the signature is not valid, the auto-baud routine synchronizes with the host via serial port
0. The host should send a ’?’ (0x3F) as a synchronization character and wait for a
response. The host side serial port settings should be 8 data bits, 1 stop bit and no parity.
The auto-baud routine measures the bit time of the received synchronization character in
terms of its own frequency and programs the baud rate generator of the serial port. It also
sends an ASCII string ("Synchronized<CR><LF>") to the Host. In response to this host
should send the same string ("Synchronized<CR><LF>"). The auto-baud routine looks at
the received characters to verify synchronization. If synchronization is verified then
"OK<CR><LF>" string is sent to the host. Host should respond by sending the crystal
frequency (in kHz) at which the part is running. For example, if the part is running at 10
MHz , the response from the host should be "10000<CR><LF>". "OK<CR><LF>" string is

sent to the host after receiving the crystal frequency. If synchronization is not verified then
the auto-baud routine waits again for a synchronization character. For auto-baud to work
correctly in case of user invoked ISP, the CCLK frequency should be greater than or equal
to 10 MHz.
For more details on Reset, PLL and startup/boot code interaction see Section 4.6.2 “PLL
and startup/boot code interaction”.
Once the crystal frequency is received the part is initialized and the ISP command handler
is invoked. For safety reasons an "Unlock" command is required before executing the
commands resulting in flash erase/write operations and the "Go" command. The rest of
the commands can be executed without the unlock command. The Unlock command is
required to be executed once per ISP session. The Unlock command is explained in
Section 29.7 “ISP commands” on page 614.
29.3.2 Communication protocol

All ISP commands should be sent as single ASCII strings. Strings should be terminated
with Carriage Return (CR) and/or Line Feed (LF) control characters. Extra <CR> and
<LF> characters are ignored. All ISP responses are sent as <CR><LF> terminated ASCII
strings. Data is sent and received in UU-encoded format.
29.3.2.1 ISP command format

"Command Parameter_0 Parameter_1 ... Parameter_n<CR><LF>" "Data" (Data only for
Write commands).
29.3.2.2 ISP response format

"Return_Code<CR><LF>Response_0<CR><LF>Response_1<CR><LF> ...
Response_n<CR><LF>" "Data" (Data only for Read commands).
29.3.2.3 ISP data format

The data stream is in UU-encode format. The UU-encode algorithm converts 3 bytes of
binary data in to 4 bytes of printable ASCII character set. It is more efficient than Hex
format which converts 1 byte of binary data in to 2 bytes of ASCII hex. The sender should
send the check-sum after transmitting 20 UU-encoded lines. The length of any
UU-encoded line should not exceed 61 characters(bytes) i.e. it can hold 45 data bytes.
The receiver should compare it with the check-sum of the received bytes. If the
check-sum matches then the receiver should respond with "OK<CR><LF>" to continue
further transmission. If the check-sum does not match the receiver should respond with
"RESEND<CR><LF>". In response the sender should retransmit the bytes.
A description of UU-encode is available at the wotsit web site.
29.3.2.4 ISP flow control

A software XON/XOFF flow control scheme is used to prevent data loss due to buffer
overrun. When the data arrives rapidly, the ASCII control character DC3 (stop) is sent to
stop the flow of data. Data flow is resumed by sending the ASCII control character DC1
(start). The host should also support the same flow control scheme.

29.3.2.5 ISP command abort

Commands can be aborted by sending the ASCII control character "ESC". This feature is
not documented as a command under "ISP Commands" section. Once the escape code is
received the ISP command handler waits for a new command.
29.3.2.6 Interrupts during ISP

The boot block interrupt vectors located in the boot block of the flash are active after any
reset.
29.3.2.7 Interrupts during IAP

The on-chip flash memory is not accessible during erase/write operations. When the user
application code starts executing, the interrupt vectors from the user flash area are active.
The user should either disable interrupts, or ensure that user interrupt vectors are active in
RAM and that the interrupt handlers reside in RAM, before making a flash erase/write IAP
call. The IAP code does not use or disable interrupts.
29.3.2.8 RAM used by ISP command handler

ISP commands use on-chip RAM from 0x4000 0120 to 0x4000 01FF. The user could use
this area, but the contents may be lost upon reset. Flash programming commands use the
top 32 bytes of on-chip RAM. The stack is located at RAM top - 32. The maximum stack
usage is 256 bytes and it grows downwards.
29.3.2.9 RAM used by IAP command handler

Flash programming commands use the top 32 bytes of on-chip RAM. The maximum stack
usage in the user allocated stack space is 128 bytes and it grows downwards.
29.3.2.10 RAM used by RealMonitor

The RealMonitor uses on-chip RAM from 0x4000 0040 to 0x4000 011F. The user could
use this area if RealMonitor based debug is not required. The flash boot loader does not
initialize the stack for RealMonitor.

29.4 Boot process flowchart
RESET
INITIALIZE
no
CRP1/2/3 ENABLED?
ENABLE DEBUG
yes
yes
WATCHDOG
FLAG SET?
A
no
USER CODE yes

VALID?
no
CRP3 ENABLED?
yes
EXECUTE INTERNAL
USER CODE
Enter ISP
USER CODE VALID? MODE?
no (P2.10=LOW) no
yes
yes
A RUN AUTO-BAUD
no AUTO-BAUD
SUCCESSFUL?
yes
RECEIVE CRYSTAL RUN ISP COMMAND

FREQUENCY 1 HANDLER 2
(1) For details on handling the crystal frequency, see Section 29.8.8 “Reinvoke ISP” on page 627
(2) For details on available ISP commands based on the CRP settings see Section 29.6 “Code Read Protection (CRP)”
Fig 135. Boot process flowchart

29.5 Sector numbers

Some IAP and ISP commands operate on "sectors" and specify sector numbers. The
following table indicate the correspondence between sector numbers and memory
addresses for LPC2300 devices containing 64, 128, 256 and 512 kbytes of flash
respectively. IAP, ISP, and RealMonitor routines are located in the boot block. The boot
block is present at addresses 0x0007 E000 to 0x0007 FFFF in all devices. ISP and IAP
commands do not allow write/erase/go operation on the boot block. Because of the boot
block, the amount of flash available for user code and data is 504 K bytes in "512K"
devices.
Table 529. Sectors in a LPC2300 device

Sector Sector Address range 64 kB 128 kB 256 kB 512 kB
number size [kB] LPC2361 LPC2362/64 LPC2365/66 LPC2367/68,
LPC2377/78,
LPC2387/88
0 4 0x0000 0000 - 0x0000 0FFF x x x x
1 4 0x0000 1000 - 0x0000 1FFF x x x x
2 4 0x0000 2000 - 0x0000 2FFF x x x x
3 4 0x0000 3000 - 0x0000 3FFF x x x x
4 4 0x0000 4000 - 0x0000 4FFF x x x x
5 4 0x0000 5000 - 0x0000 5FFF x x x x
6 4 0x0000 6000 - 0x0000 6FFF x x x x
7 4 0x0000 7000 - 0x0000 7FFF x x x x
8 32 0x0000 8000 - 0x0000 FFFF x x x x
9 32 0x0001 0000 - 0x0001 7FFF x x x
10 (0x0A) 32 0x0001 8000 - 0x0001 FFFF x x x
11 (0x0B) 32 0x0002 0000 - 0x0002 7FFF x x
12 (0x0C) 32 0x0002 8000 - 0x0002 FFFF x x
13 (0x0D) 32 0x0003 0000 - 0x0003 7FFF x x
14 (0x0E) 32 0x0003 8000 - 0x0003 FFFF x x
15 (0x0F) 32 0x0004 0000 - 0x0004 7FFF x
16 (0x10) 32 0x0004 8000 - 0x0004 FFFF x
17 (0x11) 32 0x0005 0000 - 0x0005 7FFF x
18 (0x12) 32 0x0005 8000 - 0x0005 FFFF x
19 (0x13) 32 0x0006 0000 - 0x0006 7FFF x
20 (0x14) 32 0x0006 8000 - 0x0006 FFFF x
21 (0x15) 32 0x0007 0000 - 0x0007 7FFF x
22 (0x16) 4 0x0007 8000 - 0x0007 8FFF x
23 (0x17) 4 0x0007 9000 - 0x0007 9FFF x
24 (0x18) 4 0x0007 A000 - 0x0007 AFFF x
25 (0x19) 4 0x0007 B000 - 0x0007 BFFF x
26 (0x1A) 4 0x0007 C000 - 0x0007 CFFF x
27 (0x1B) 4 0x0007 D000 - 0x0007 DFFF x

29.6 Code Read Protection (CRP)

Code Read Protection is a mechanism that allows user to enable different levels of
security in the system so that access to the on-chip flash and use of the ISP can be
restricted. When needed, CRP is invoked by programming a specific pattern in flash
location at 0x000001FC. IAP commands are not affected by the code read protection.
Starting with bootloader version 3.2 three levels of CRP are implemented. Earlier
bootloader versions had only CRP2 option implemented.
Important: Any CRP change becomes effective only after the device has gone
through a power cycle.
Table 530. Code Read Protection options

Name Pattern Description
programmed
in 0x000001FC
CRP1 0x12345678 Access to chip via the JTAG pins is disabled. This mode allows partial
flash update using the following ISP commands and restrictions:
• Write to RAM command can not access RAM below 0x40000200
• Copy RAM to flash command can not write to Sector 0
• Erase command can erase Sector 0 only when all sectors are
selected for erase
• Compare command is disabled
• Read command is disabled
This mode is useful when CRP is required and flash field updates are
needed but all sectors can not be erased. Since compare command is
disabled in case of partial updates the secondary loader should
implement checksum mechanism to verify the integrity of the flash.
CRP2 0x87654321 Access to chip via the JTAG pins is disabled. The following ISP
commands are disabled:
• Read Memory command
• Write to RAM command
• Go command
• Copy RAM to flash command
• Compare command
When CRP2 is enabled the ISP erase command only allows erasure of
all user sectors.
CRP3 0x43218765 Access to chip via the JTAG pins is disabled. ISP entry by pulling P2.10
LOW is disabled if a valid user code is present in flash sector 0.
This mode effectively disables ISP override using the P2.10 pin. It is up
to the user’s application to provide for flash updates by using IAP calls or
by reinvoking ISP via UART0.
Caution: If CRP3 is selected, no future factory testing can be
performed on the device.

Table 531. Code Read Protection hardware/software interaction

CRP option User Code P2.10 pin at JTAG enabled LPC2300 partial flash
Valid reset enters ISP update in ISP
mode mode
No No X Yes Yes Yes
No Yes High Yes No NA
No Yes Low Yes Yes Yes
CRP1 Yes High No No NA
CRP1 Yes Low No Yes Yes
CRP2 Yes High No No NA
CRP2 Yes Low No Yes No
CRP3 Yes x No No NA
CRP1 No x No Yes Yes
CRP2 No x No Yes No
CRP3 No x No Yes No
If any CRP mode is enabled and access to the chip is allowed via the ISP, an unsupported
or restricted ISP command will be terminated with return code
CODE_READ_PROTECTION_ENABLED.
29.7 ISP commands

The following commands are accepted by the ISP command handler. Detailed status
codes are supported for each command. The command handler sends the return code
INVALID_COMMAND when an undefined command is received. Commands and return
codes are in ASCII format.
CMD_SUCCESS is sent by ISP command handler only when received ISP command has
been completely executed and the new ISP command can be given by the host.
Exceptions from this rule are "Set Baud Rate", "Write to RAM", "Read Memory", and "Go"
commands.
Table 532. ISP command summary

ISP Command Usage Described in
Unlock U <Unlock Code> Table 533
Set Baud Rate B <Baud Rate> <stop bit> Table 534
Echo A <setting> Table 536
Write to RAM W <start address> <number of bytes> Table 537
Read Memory R <address> <number of bytes> Table 538
Prepare sector(s) for P <start sector number> <end sector number> Table 539
write operation
Copy RAM to flash C <flash address> <RAM address> <number of bytes> Table 540
Go G <address> <Mode> Table 541
Erase sector(s) E <start sector number> <end sector number> Table 542
Blank check sector(s) I <start sector number> <end sector number> Table 543

Table 532. ISP command summary

ISP Command Usage Described in
Read Part ID J Table 544
Read Boot code version K Table 546
Compare M <address1> <address2> <number of bytes> Table 547
29.7.1 Unlock <Unlock code>

Table 533. ISP Unlock command
Command U
Input Unlock code: 2313010
Return Code CMD_SUCCESS |
INVALID_CODE |
PARAM_ERROR
Description This command is used to unlock flash Write, Erase, and Go commands.
Example "U 23130<CR><LF>" unlocks the flash Write/Erase & Go commands.
29.7.2 Set Baud Rate <Baud Rate> <stop bit>

Table 534. ISP Set Baud Rate command
Command B
Input Baud Rate: 9600 | 19200 | 38400 | 57600 | 115200 | 230400
Stop bit: 1 | 2
INVALID_BAUD_RATE |
INVALID_STOP_BIT |
PARAM_ERROR
Description This command is used to change the baud rate. The new baud rate is effective
after the command handler sends the CMD_SUCCESS return code.
Example "B 57600 1<CR><LF>" sets the serial port to baud rate 57600 bps and 1 stop bit.
Table 535. Correlation between possible ISP baudrates and CCLK frequency (in MHz)
ISP Baudrate .vs. 9600 19200 38400 57600 115200 230400
CCLK Frequency
10.0000 + + +
11.0592 + + +
12.2880 + + +
14.7456[1] + + + + + +
15.3600 +
18.4320 + + +
19.6608 + + +
24.5760 + + +
25.0000 + + +
[1] ISP entry after reset uses the on chip IRC and PLL to run the device at CCLK = 14.748 MHz

29.7.3 Echo <setting>

Table 536. ISP Echo command
Command A
Input Setting: ON = 1 | OFF = 0
PARAM_ERROR
Description The default setting for echo command is ON. When ON the ISP command handler
sends the received serial data back to the host.
Example "A 0<CR><LF>" turns echo off.
29.7.4 Write to RAM <start address> <number of bytes>

The host should send the data only after receiving the CMD_SUCCESS return code. The
host should send the check-sum after transmitting 20 UU-encoded lines. The checksum is
generated by adding raw data (before UU-encoding) bytes and is reset after transmitting
20 UU-encoded lines. The length of any UU-encoded line should not exceed
61 characters(bytes) i.e. it can hold 45 data bytes. When the data fits in less then
20 UU-encoded lines then the check-sum should be of the actual number of bytes sent.
The ISP command handler compares it with the check-sum of the received bytes. If the
check-sum matches, the ISP command handler responds with "OK<CR><LF>" to
continue further transmission. If the check-sum does not match, the ISP command
handler responds with "RESEND<CR><LF>". In response the host should retransmit the
bytes.
Table 537. ISP Write to RAM command

Command W
Input Start Address: RAM address where data bytes are to be written. This address
should be a word boundary.
Number of Bytes: Number of bytes to be written. Count should be a multiple of 4
ADDR_ERROR (Address not on word boundary) |
ADDR_NOT_MAPPED |
COUNT_ERROR (Byte count is not multiple of 4) |
PARAM_ERROR |
CODE_READ_PROTECTION_ENABLED
Description This command is used to download data to RAM. Data should be in UU-encoded
format. This command is blocked when code read protection is enabled.
Example "W 1073742336 4<CR><LF>" writes 4 bytes of data to address 0x4000 0200.
29.7.5 Read Memory <address> <no. of bytes>

The data stream is followed by the command success return code. The check-sum is sent
after transmitting 20 UU-encoded lines. The checksum is generated by adding raw data
(before UU-encoding) bytes and is reset after transmitting 20 UU-encoded lines. The
length of any UU-encoded line should not exceed 61 characters(bytes) i.e. it can hold
45 data bytes. When the data fits in less then 20 UU-encoded lines then the check-sum is
of actual number of bytes sent. The host should compare it with the checksum of the
received bytes. If the check-sum matches then the host should respond with

"OK<CR><LF>" to continue further transmission. If the check-sum does not match then
the host should respond with "RESEND<CR><LF>". In response the ISP command
handler sends the data again.
Table 538. ISP Read Memory command

Command R
Input Start Address: Address from where data bytes are to be read. This address
should be a word boundary.
Number of Bytes: Number of bytes to be read. Count should be a multiple of 4.
Return Code CMD_SUCCESS followed by <actual data (UU-encoded)> |
ADDR_ERROR (Address not on word boundary) |
ADDR_NOT_MAPPED |
COUNT_ERROR (Byte count is not a multiple of 4) |
PARAM_ERROR |
Description This command is used to read data from RAM or flash memory. This command is
blocked when code read protection is enabled.
Example "R 1073741824 4<CR><LF>" reads 4 bytes of data from address 0x4000 0000.
29.7.6 Prepare sector(s) for write operation <start sector number> <end
sector number>
This command makes flash write/erase operation a two step process.
Table 539. ISP Prepare sector(s) for write operation command

Command P
Input Start Sector Number
End Sector Number: Should be greater than or equal to start sector number.
BUSY |
INVALID_SECTOR |
PARAM_ERROR
Description This command must be executed before executing "Copy RAM to flash" or "Erase
Sector(s)" command. Successful execution of the "Copy RAM to flash" or "Erase
Sector(s)" command causes relevant sectors to be protected again. The boot
block can not be prepared by this command. To prepare a single sector use the
same "Start" and "End" sector numbers.
Example "P 0 0<CR><LF>" prepares the flash sector 0.

29.7.7 Copy RAM to flash <flash address> <RAM address> <no of bytes>
Table 540. ISP Copy command
Command C
Input Flash Address(DST): Destination flash address where data bytes are to be
written. The destination address should be a 256 byte boundary.
RAM Address(SRC): Source RAM address from where data bytes are to be read.
Number of Bytes: Number of bytes to be written. Should be 256 | 512 | 1024 |
4096.
SRC_ADDR_ERROR (Address not on word boundary) |
DST_ADDR_ERROR (Address not on correct boundary) |
SRC_ADDR_NOT_MAPPED |
DST_ADDR_NOT_MAPPED |
COUNT_ERROR (Byte count is not 256 | 512 | 1024 | 4096) |
SECTOR_NOT_PREPARED_FOR WRITE_OPERATION |
BUSY |
CMD_LOCKED |
PARAM_ERROR |
Description This command is used to program the flash memory. The "Prepare Sector(s) for
Write Operation" command should precede this command. The affected sectors are
automatically protected again once the copy command is successfully executed.
The boot block cannot be written by this command. This command is blocked when
code read protection is enabled.
Example "C 0 1073774592 512<CR><LF>" copies 512 bytes from the RAM address
0x4000 8000 to the flash address 0.
29.7.8 Go <address> <mode>

Table 541. ISP Go command
Command G
Input Address: Flash or RAM address from which the code execution is to be started.
This address should be on a word boundary.
Mode: T (Execute program in Thumb Mode) | A (Execute program in ARM mode).
ADDR_ERROR |
ADDR_NOT_MAPPED |
CMD_LOCKED |
PARAM_ERROR |
Description This command is used to execute a program residing in RAM or flash memory. It
may not be possible to return to the ISP command handler once this command is
successfully executed. This command is blocked when code read protection is
enabled.
Example "G 0 A<CR><LF>" branches to address 0x0000 0000 in ARM mode.

29.7.9 Erase sector(s) <start sector number> <end sector number>

Table 542. ISP Erase sector command
Command E
Input Start Sector Number
BUSY |
INVALID_SECTOR |
SECTOR_NOT_PREPARED_FOR_WRITE_OPERATION |
CMD_LOCKED |
PARAM_ERROR |
Description This command is used to erase one or more sector(s) of on-chip flash memory. The
boot block can not be erased using this command. This command only allows
erasure of all user sectors when the code read protection is enabled.
Example "E 2 3<CR><LF>" erases the flash sectors 2 and 3.
29.7.10 Blank check sector(s) <sector number> <end sector number>

Table 543. ISP Blank check sector command
Command I
Input Start Sector Number:
SECTOR_NOT_BLANK (followed by <Offset of the first non blank word location>
<Contents of non blank word location>) |
INVALID_SECTOR |
PARAM_ERROR |
Description This command is used to blank check one or more sectors of on-chip flash memory.
Blank check on sector 0 always fails as first 64 bytes are re-mapped to flash
boot block.
Example "I 2 3<CR><LF>" blank checks the flash sectors 2 and 3.
29.7.11 Read Part Identification number

Table 544. ISP Read Part Identification command
Command J
Input None.
Return Code CMD_SUCCESS followed by part identification number in ASCII (see Table 545
“LPC2300 part identification numbers”).
Description This command is used to read the part identification number.

Table 545. LPC2300 part identification numbers

Device ASCII/dec coding Hex coding
LPC2361 369161985 0x1600 F701
LPC2362 369164066 0x1600 FF22
LPC2364 369162498 0x1600 F902
LPC2365 369158179 0x1600 E823
LPC2366 369162531 0x1600 F923
LPC2367 369158181 0x1600 E825
LPC2368 369162533 0x1600 F925
LPC2377 385935397 0x1700 E825
LPC2378 385940773 0x1700 FD25
LPC2387 385941301 0x1700 FF35[1]
LPC2388 402718517 0x1800 FF35
[1] For parts starting with date code 0840. Older LPC2387 devices use 0x1800 F935.
In addition to the part identification numbers, the user can determine the device revision
by reading the register contents at address 0x0007 E070. The register value is encoded
as follows: 0x0 corresponds to revision ‘—’, 0x01 corresponds to revision A, 0x02
corresponds to revision B,..., 0x1A corresponds to revision Z. On all LPC23XX parts, this
feature is implemented starting with device revision D, so the register read will yield a
value of 0x04 (for revision D) or larger.
29.7.12 Read Boot code version number

Table 546. ISP Read Boot Code version number command
Command K
Input None
Return Code CMD_SUCCESS followed by 2 bytes of boot code version number in ASCII format.
It is to be interpreted as <byte1(Major)>.<byte0(Minor)>.
Description This command is used to read the boot code version number.

29.7.13 Compare <address1> <address2> <no of bytes>

Table 547. ISP Compare command
Command M
Input Address1 (DST): Starting flash or RAM address of data bytes to be compared.
This address should be a word boundary.
Address2 (SRC): Starting flash or RAM address of data bytes to be compared.
This address should be a word boundary.
Number of Bytes: Number of bytes to be compared; should be a multiple of 4.
Return Code CMD_SUCCESS | (Source and destination data are equal)
COMPARE_ERROR | (Followed by the offset of first mismatch)
ADDR_ERROR |
ADDR_NOT_MAPPED |
PARAM_ERROR |
Description This command is used to compare the memory contents at two locations.
Compare result may not be correct when source or destination address
contains any of the first 64 bytes starting from address zero. First 64 bytes
are re-mapped to flash boot sector
Example "M 8192 1073741824 4<CR><LF>" compares 4 bytes from the RAM address
0x4000 0000 to the 4 bytes from the flash address 0x2000.
29.7.14 ISP Return Codes

Table 548. ISP Return Codes Summary
Return Mnemonic Description
Code
0 CMD_SUCCESS Command is executed successfully. Sent by ISP
handler only when command given by the host has
been completely and successfully executed.
1 INVALID_COMMAND Invalid command.
2 SRC_ADDR_ERROR Source address is not on word boundary.
3 DST_ADDR_ERROR Destination address is not on a correct boundary.
4 SRC_ADDR_NOT_MAPPED Source address is not mapped in the memory map.
Count value is taken in to consideration where
applicable.
5 DST_ADDR_NOT_MAPPED Destination address is not mapped in the memory
map. Count value is taken in to consideration
where applicable.
6 COUNT_ERROR Byte count is not multiple of 4 or is not a permitted
value.
7 INVALID_SECTOR Sector number is invalid or end sector number is
greater than start sector number.
8 SECTOR_NOT_BLANK Sector is not blank.
9 SECTOR_NOT_PREPARED_FOR_ Command to prepare sector for write operation
WRITE_OPERATION was not executed.
10 COMPARE_ERROR Source and destination data not equal.
11 BUSY Flash programming hardware interface is busy.

Table 548. ISP Return Codes Summary

Return Mnemonic Description
Code
12 PARAM_ERROR Insufficient number of parameters or invalid
parameter.
13 ADDR_ERROR Address is not on word boundary.
14 ADDR_NOT_MAPPED Address is not mapped in the memory map. Count
value is taken in to consideration where applicable.
15 CMD_LOCKED Command is locked.
16 INVALID_CODE Unlock code is invalid.
17 INVALID_BAUD_RATE Invalid baud rate setting.
18 INVALID_STOP_BIT Invalid stop bit setting.
19 CODE_READ_PROTECTION_ Code read protection enabled.
ENABLED
29.8 IAP commands

For in application programming the IAP routine should be called with a word pointer in
register r0 pointing to memory (RAM) containing command code and parameters. Result
of the IAP command is returned in the result table pointed to by register r1. The user can
reuse the command table for result by passing the same pointer in registers r0 and r1. The
parameter table should be big enough to hold all the results in case if number of results
are more than number of parameters. Parameter passing is illustrated in the Figure 136.
The number of parameters and results vary according to the IAP command. The
maximum number of parameters is 5, passed to the "Copy RAM to FLASH" command.
The maximum number of results is 2, returned by the "Blankcheck sector(s)" command.
The command handler sends the status code INVALID_COMMAND when an undefined
command is received. The IAP routine resides at 0x7FFF FFF0 location and it is thumb
code.
The IAP function could be called in the following way using C.
Define the IAP location entry point. Since the 0th bit of the IAP location is set there will be
a change to Thumb instruction set when the program counter branches to this address.
#define IAP_LOCATION 0x7ffffff1
Define data structure or pointers to pass IAP command table and result table to the IAP
function:
unsigned long command[5];

unsigned long result[3];
or
unsigned long * command;

unsigned long * result;
command=(unsigned long *) 0x……
result= (unsigned long *) 0x……
Define pointer to function type, which takes two parameters and returns void. Note the IAP
returns the result with the base address of the table residing in R1.

typedef void (*IAP)(unsigned int [],unsigned int[]);

IAP iap_entry;
Setting function pointer:
iap_entry=(IAP) IAP_LOCATION;
Whenever you wish to call IAP you could use the following statement.
iap_entry (command, result);
The IAP call could be simplified further by using the symbol definition file feature
supported by ARM Linker in ADS (ARM Developer Suite). You could also call the IAP
routine using assembly code.
The following symbol definitions can be used to link IAP routine and user application:
#<SYMDEFS># ARM Linker, ADS1.2 [Build 826]: Last Updated: Wed May 08 16:12:23 2002
0x7fffff90 T rm_init_entry
0x7fffffa0 A rm_undef_handler
0x7fffffb0 A rm_prefetchabort_handler
0x7fffffc0 A rm_dataabort_handler
0x7fffffd0 A rm_irqhandler
0x7fffffe0 A rm_irqhandler2
0x7ffffff0 T iap_entry
As per the ARM specification (The ARM Thumb Procedure Call Standard SWS ESPC
0002 A-05) up to 4 parameters can be passed in the r0, r1, r2 and r3 registers
respectively. Additional parameters are passed on the stack. Up to 4 parameters can be
returned in the r0, r1, r2 and r3 registers respectively. Additional parameters are returned
indirectly via memory. Some of the IAP calls require more than 4 parameters. If the ARM
suggested scheme is used for the parameter passing/returning then it might create
problems due to difference in the C compiler implementation from different vendors. The
suggested parameter passing scheme reduces such risk.
The flash memory is not accessible during a write or erase operation. IAP commands,
which results in a flash write/erase operation, use 32 bytes of space in the top portion of
the on-chip RAM for execution. The user program should not be use this space if IAP flash
programming is permitted in the application.
Table 549. IAP Command Summary

IAP Command Command Code Described in
Prepare sector(s) for write operation 5010 Table 550
Copy RAM to flash 5110 Table 551
Erase sector(s) 5210 Table 552
Blank check sector(s) 5310 Table 553
Read Part ID 5410 Table 554
Read Boot code version 5510 Table 555
Compare 5610 Table 556
Reinvoke ISP 5710 Table 557

COMMAND CODE
command
PARAMETER 1 parameter table
PARAMETER 2
ARM REGISTER r0
PARAMETER n
ARM REGISTER r1
STATUS CODE
RESULT 1 command
result table
RESULT 2
RESULT n
Fig 136. IAP parameter passing
29.8.1 Prepare sector(s) for write operation

This command makes flash write/erase operation a two step process.
Table 550. IAP Prepare sector(s) for write operation command

Command Prepare sector(s) for write operation
Input Command code: 5010
Param0: Start Sector Number
Param1: End Sector Number (should be greater than or equal to start sector
number).
BUSY |
INVALID_SECTOR
Result None
Description This command must be executed before executing "Copy RAM to flash" or "Erase
Sector(s)" command. Successful execution of the "Copy RAM to flash" or "Erase
Sector(s)" command causes relevant sectors to be protected again. The boot
sector can not be prepared by this command. To prepare a single sector use the
same "Start" and "End" sector numbers.

29.8.2 Copy RAM to flash

Table 551. IAP Copy RAM to flash command
Command Copy RAM to flash
Param0(DST): Destination flash address where data bytes are to be written. This
address should be a 256 byte boundary.
Param1(SRC): Source RAM address from which data bytes are to be read. This
address should be a word boundary.
Param2: Number of bytes to be written. Should be 256 | 512 | 1024 | 4096.
Param3: System Clock Frequency (CCLK) in kHz.
SRC_ADDR_ERROR (Address not a word boundary) |
DST_ADDR_ERROR (Address not on correct boundary) |
SRC_ADDR_NOT_MAPPED |
DST_ADDR_NOT_MAPPED |
COUNT_ERROR (Byte count is not 256 | 512 | 1024 | 4096) |
BUSY |
Result None
Description This command is used to program the flash memory. The affected sectors should
be prepared first by calling "Prepare Sector for Write Operation" command. The
affected sectors are automatically protected again once the copy command is
successfully executed. The boot sector can not be written by this command.
29.8.3 Erase Sector(s)

Table 552. IAP Erase Sector(s) command
Command Erase Sector(s)
number).
Param2: System Clock Frequency (CCLK) in kHz.
BUSY |
INVALID_SECTOR
Result None
Description This command is used to erase a sector or multiple sectors of on-chip flash
memory. The boot sector can not be erased by this command. To erase a single
sector use the same "Start" and "End" sector numbers.

29.8.4 Blank check sector(s)

Table 553. IAP Blank check sector(s) command
Command Blank check sector(s)
number).
BUSY |
SECTOR_NOT_BLANK |
INVALID_SECTOR
Result Result0: Offset of the first non blank word location if the Status Code is
SECTOR_NOT_BLANK.
Result1: Contents of non blank word location.
Description This command is used to blank check a sector or multiple sectors of on-chip flash
memory. To blank check a single sector use the same "Start" and "End" sector
numbers.
29.8.5 Read Part Identification number

Table 554. IAP Read Part Identification command
Command Read part identification number
Parameters: None
Result Result0: Part Identification Number.
Description This command is used to read the part identification number.
29.8.6 Read Boot code version number

Table 555. IAP Read Boot Code version number command
Command Read boot code version number
Parameters: None
Result Result0: 2 bytes of boot code version number in ASCII format. It is to be
interpreted as <byte1(Major)>.<byte0(Minor)>
Description This command is used to read the boot code version number.

29.8.7 Compare <address1> <address2> <no of bytes>

Table 556. IAP Compare command
Command Compare
Param0(DST): Starting flash or RAM address of data bytes to be compared. This
Param1(SRC): Starting flash or RAM address of data bytes to be compared. This
Param2: Number of bytes to be compared; should be a multiple of 4.
COMPARE_ERROR |
ADDR_ERROR |
ADDR_NOT_MAPPED
Result Result0: Offset of the first mismatch if the Status Code is COMPARE_ERROR.
Description This command is used to compare the memory contents at two locations.
The result may not be correct when the source or destination includes any
of the first 64 bytes starting from address zero. The first 64 bytes can be
re-mapped to RAM.
29.8.8 Reinvoke ISP

Table 557. Reinvoke ISP
Command Compare
Return Code None
Result None.
Description This command is used to invoke the bootloader in ISP mode. It maps boot
vectors, sets PCLK = CCLK / 4, configures UART0 pins Rx and Tx, resets
TIMER1 and resets the U0FDR (see Section 16.4.12). This command may be
used when a valid user program is present in the internal flash memory and the
P2.10 pin is not accessible to force the ISP mode. The command does not disable
the PLL hence it is possible to invoke the bootloader when the part is running off
the PLL. In such case the ISP utility should pass the CCLK (crystal or PLL output
depending on the clock source selection Section 4.5.1) frequency after autobaud
handshake.
Another option is to disable the PLL and select the IRC as the clock source before
making this IAP call. In this case frequency sent by ISP is ignored and IRC and
PLL are used to generate CCLK = 14.748 MHz.
29.8.9 IAP Status Codes

Table 558. IAP Status Codes Summary
Status Mnemonic Description
Code
0 CMD_SUCCESS Command is executed successfully.
1 INVALID_COMMAND Invalid command.
2 SRC_ADDR_ERROR Source address is not on a word boundary.

Table 558. IAP Status Codes Summary

Status Mnemonic Description
Code
3 DST_ADDR_ERROR Destination address is not on a correct boundary.
4 SRC_ADDR_NOT_MAPPED Source address is not mapped in the memory map.
Count value is taken in to consideration where
applicable.
5 DST_ADDR_NOT_MAPPED Destination address is not mapped in the memory
map. Count value is taken in to consideration where
applicable.
6 COUNT_ERROR Byte count is not multiple of 4 or is not a permitted
value.
7 INVALID_SECTOR Sector number is invalid.
8 SECTOR_NOT_BLANK Sector is not blank.
9 SECTOR_NOT_PREPARED_ Command to prepare sector for write operation was
FOR_WRITE_OPERATION not executed.
10 COMPARE_ERROR Source and destination data is not same.
11 BUSY Flash programming hardware interface is busy.
29.9 JTAG flash programming interface

Debug tools can write parts of the flash image to the RAM and then execute the IAP call
"Copy RAM to flash" repeatedly with proper offset.

UM10211
Chapter 30: LPC23XX General Purpose DMA (GPDMA)
controller

The GPDMA is configured using the following registers:
1. Power: In the PCONP register (Table 56), set bit PCGPDMA.

Remark: On reset, the GPDMA is disabled (PCGPDMA = 0).
30.2 Introduction
The General Purpose DMA Controller (GPDMA) is an AMBA AHB compliant peripheral
allowing selected LPC23xx peripherals to have DMA support.
30.3 Features of the GPDMA

• Two DMA channels. Each channel can support a unidirectional transfer.
The GPDMA provides 16 peripheral DMA request lines. Some of these are connected
to peripheral functions that support DMA: the SD/MMC, two SSP, and I2S interfaces.
• Single DMA and burst DMA request signals. Each peripheral connected to the
GPDMA can assert either a burst DMA request or a single DMA request. The DMA
burst size is set by programming the GPDMA.
• Memory-to-memory, memory-to-peripheral, peripheral-to-memory, and
peripheral-to-peripheral transfers.
• Scatter or gather DMA is supported through the use of linked lists. This means that
the source and destination areas do not have to occupy contiguous areas of memory.
• Hardware DMA channel priority. Each DMA channel has a specific hardware priority.
DMA channel 0 has the highest priority and channel 1 has the lowest priority. If
requests from two channels become active at the same time the channel with the
highest priority is serviced first.
• AHB slave DMA programming interface. The GPDMA is programmed by writing to the
DMA control registers over the AHB slave interface.
• One AHB bus master for transferring data. This interface transfers data when a DMA
request goes active.
• 32 bit AHB master bus width.
• Incrementing or non-incrementing addressing for source and destination.
• Programmable DMA burst size. The DMA burst size can be programmed to more
efficiently transfer data. Usually the burst size is set to half the size of the FIFO in the
peripheral.
• Internal four-word FIFO per channel.

Chapter 30: LPC23XX General Purpose DMA (GPDMA) controller
• Supports 8, 16, and 32 bit wide transactions.

• Big-endian and little-endian support. The GPDMA defaults to little-endian mode on
reset.
• An interrupt to the processor can be generated on a DMA completion or when a DMA
error has occurred.
• Interrupt masking. The DMA error and DMA terminal count interrupt requests can be
masked.
• Raw interrupt status. The DMA error and DMA count raw interrupt status can be read
prior to masking.
• Test registers for use in block and integration system level testing.
• Identification registers that uniquely identify the GPDMA. These can be used by an
operating system to automatically configure itself.

This chapter describes the major functional blocks of the GPDMA. It contains the following
sections:
• GPDMA functional description

• System considerations
• System connectivity
• Use with memory management unit based systems
30.4.1 Memory regions accessible by the GPDMA

Table 559. GPDMA accessible memory
Memory region Address range Memory Type
On-chip RAM 0x7FD0 0000 - 0x7FD0 1FFF USB RAM (8 kB)
0x7FD0 0000 - 0x7FD0 3FFF USB RAM (8 kB) (LPC2387
only)
Off-Chip Memory Two static memory banks, 64 kB each
(LPC2377/78/88 only) 0x8000 0000 - 0x8000 FFFF Static memory bank 0
0x8100 0000 - 0x8100 FFFF Static memory bank 1
30.4.2 GPDMA functional description

The GPDMA enables peripheral-to-memory, memory-to-peripheral,
peripheral-to-peripheral, and memory-to-memory transactions. Each DMA stream
provides unidirectional serial DMA transfers for a single source and destination. For
example, a bidirectional port requires one stream for transmit and one for receive. The
source and destination areas can each be either a memory region or a peripheral, and
can be accessed through the AHB master.
Figure 137 shows a block diagram of the GPDMA.

GPDMA
CONTROL
AHB SLAVE
AHB BUS LOGIC AND
INTERFACE
REGISTERS
DMA
requests DMA
REQUEST CHANNEL AHB
DMA AND LOGIC AND MASTER AHB BUS
responses RESPONSE REGISTERS INTERFACE
INTERFACE
DMA
Interrupts INTERRUPT
REQUEST
Fig 137. GPDMA Block Diagram
The functions of the GPDMA are described in the following sections:
• AHB slave interface

• Control logic and register bank
• DMA request and response interface
• Channel logic and channel register bank
• Interrupt request
• AHB master interface
• Channel hardware
• DMA request priority
30.4.2.1 AHB Slave Interface

All transactions on the AHB slave programming bus of the GPDMA are 32 bit wide.
30.4.2.2 Control Logic and Register Bank

The register block stores data written, or to be read across the AHB interface.
30.4.2.3 DMA Request and Response Interface

See DMA Interface description for information on the DMA request and response
interface.
30.4.2.4 Channel Logic and Channel Register Bank

The channel logic and channel register bank contains registers and logic required for each
DMA channel.
30.4.2.5 Interrupt Request

The interrupt request generates interrupts to the ARM processor.

30.4.2.6 AHB Master Interface

The GPDMA contains a full AHB master. See Figure 138 for how the GPDMA connected
in the LPC23XX.
ARM7 GPDMA
AHB AHB
AHB SLAVE MASTER SSP1
BRIDGE
SSP0
EXTERNAL AHB1
EXTERNAL APB
MEMORY SD/MMC
MEMORY BRIDGE
CONTROLLER
I2S1
8/16 kB
SRAM
I2S0
Fig 138. GPDMA in the LPC23XX
The AHB master is capable of dealing with all types of AHB transactions, including:
• Split, retry, and error responses from slaves. If a peripheral performs a split or retry,
the GPDMA stalls and waits until the transaction can complete.
• Locked transfers for source and destination of each stream.
• Setting of protection bits for transfers on each stream.
30.4.2.7 Bus and Transfer Widths

The physical width of the AHB bus is 32 bits. Source and destination transfers can be of
differing widths, and can be the same width or narrower than the physical bus width. The
GPDMA packs or unpacks data as appropriate.
30.4.2.8 Endian Behavior

The GPDMA can cope with both little-endian and big-endian addressing. You can set the
endianness of each AHB master individually.
Internally the GPDMA treats all data as a stream of bytes instead of 16 bit or 32 bit
quantities. This means that when performing mixed-endian activity, where the endianness
of the source and destination are different, byte swapping of the data within the 32 bit data
bus is observed.
Note: If you do not require byte swapping then avoid using different endianness between
the source and destination addresses.
Table 560 shows endian behavior for different source and destination combinations.

Table 560. Endian behavior

Sourc Destinatio Sourc Destination Source Sourc Destination Destination
e n e Width Transfer no/ e Data Transfer no/ Data
Endian Endian Width byte Lane byte Lane
Little Little 8 8 1/[7:0] 21 1/[7:0] 21212121
2/[15:8] 43 2/[15:8] 43434343
3/[23:16] 65 3/[23:16] 65656565
4/[31:24] 87 4/[31:24] 87878787
Little Little 8 16 1/[7:0] 21 1/[15:0] 43214321
2/[15:8] 43 2/[31:16] 87658765
3/[23:16] 65
4/[31:24] 87
Little Little 8 32 1/[7:0] 21 1/[31:0] 87654321
2/[15:8] 43
3/[23:16] 65
4/[31:24] 87
Little Little 16 8 1/[7:0] 21 1/[7:0] 21212121
1/[15:8] 43 2/[15:8] 43434343
2/[23:16] 65 3/[23:16] 65656565
2/[31:24] 87 4/[31:24] 87878787
Little Little 16 16 1/[7:0] 21 1/[15:0] 43214321
1/[15:8] 43 2/[31:16] 87658765
2/[23:16] 65
2/[31:24] 87
Little Little 16 32 1/[7:0] 21 1/[31:0] 87654321
2/[15:8] 43
3/[23:16] 65
4/[31:24] 87
Little Little 32 8 1/[7:0] 21 1/[7:0] 21212121
1/[15:8] 43 2/[15:8] 43434343
2/[23:16] 65 3/[23:16] 65656565
2/[31:24] 87 4/[31:24] 87878787
Little Little 32 16 1/[7:0] 21 1/[15:0] 43214321
1/[15:8] 43 2/[31:16] 87658765
2/[23:16] 65
2/[31:24] 87
Little Little 32 32 1/[7:0] 21 1/[31:0] 87654321
2/[15:8] 43
3/[23:16] 65
4/[31:24] 87
Big Big 8 8 1/[31:24] 12 1/[31:24] 12121212
2/[23:16] 34 2/[23:16] 34343434
3/[15:8] 56 3/[15:8] 56565656
4/[7:0] 78 4/[7:0] 78787878

Table 560. Endian behavior

Sourc Destinatio Sourc Destination Source Sourc Destination Destination
e n e Width Transfer no/ e Data Transfer no/ Data
Endian Endian Width byte Lane byte Lane
Big Big 8 16 1/[31:24] 12 1/[15:0] 12341234
2/[23:16] 34 2/[31:16] 56785678
3/[15:8] 56
4/[7:0] 78
Big Big 8 32 1/[31:24] 12 1/[31:0] 12345678
2/[23:16] 34
3/[15:8] 56
4/[7:0] 78
Big Big 16 8 1/[31:24] 12 1/[31:24] 12121212
2/[23:16] 34 2/[23:16] 34343434
3/[15:8] 56 3/[15:8] 56565656
4/[7:0] 78 4/[7:0] 78787878
Big Big 16 16 1/[31:24] 12 1/[15:0] 12341234
2/[23:16] 34 2/[31:16] 56785678
3/[15:8] 56
4/[7:0] 78
Big Big 16 32 1/[31:24] 12 1/[31:0] 12345678
2/[23:16] 34
3/[15:8] 56
4/[7:0] 78
Big Big 32 8 1/[31:24] 12 1/[31:24] 12121212
2/[23:16] 34 2/[23:16] 34343434
3/[15:8] 56 3/[15:8] 56565656
4/[7:0] 78 4/[7:0] 78787878
Big Big 32 16 1/[31:24] 12 1/[15:0] 12341234
2/[23:16] 34 2/[31:16] 56785678
3/[15:8] 56
4/[7:0] 78
Big Big 32 32 1/[31:24] 12 1/[31:0] 12345678
2/[23:16] 34
3/[15:8] 56
4/[7:0] 78
30.4.2.9 Error Conditions

An error during a DMA transfer is flagged directly by the peripheral by asserting an Error
response on the AHB bus during the transfer. The GPDMA automatically disables the
DMA stream after the current transfer has completed, and can optionally generate an
error interrupt to the CPU. This error interrupt can be masked.

30.4.2.10 Channel Hardware

Each stream is supported by a dedicated hardware channel, including source and
destination controllers, and a FIFO. This enables better latency than a DMA controller with
only a single hardware channel shared between several DMA streams and simplifies the
control logic.
30.4.2.11 DMA Request Priority

DMA channel priority is fixed. DMA channel 0 has the highest priority and DMA channel 1
has the lowest priority.
If the GPDMA is transferring data for the lower priority channel and then the higher priority
channel goes active, it completes the number of transfers delegated to the master
interface by the lower priority channel before switching over to transfer data for the higher
priority channel. In the worst case this is as large as a one quadword. Channel 1 in the
GPDMA is designed so that it cannot saturate the AHB bus. If it goes active, the GPDMA
relinquishes control of the bus (for a bus cycle), after four transfers of the programmed
size (irrespective of the size of transfer). This enables other AHB masters to access the
bus.
It is recommended that memory-to-memory transactions use the low priority channel.

Otherwise other (lower priority) AHB bus masters are prevented from accessing the bus
during GPDMA memory-to-memory transfer.
30.4.2.12 Interrupt Generation

A combined interrupt output is generated as an OR function of the individual interrupt
requests of the GPDMA, and is connected to the LPC2300 interrupt controller.
30.4.2.13 The completion of the DMA transfer indication

The completion of the DMA transfer is indicated by:
1. The transfer count reaching 0 if the GPDMA is performing flow control, OR

2. The peripheral setting the DMA Last Word Request Input (DMACLSREQ) or the DMA
Last Burst Request Input (DMALBREQ) if the peripheral is performing flow control.
According to Table 561 “DMA Connections”, SSP0, SSP1 and I2S do not use DMA Last
Word Request Input nor DMA Last Burst Request Input. Therefore there will be no
indication of completion if SSP0, SSP1 and I2S are performing the flow control.
30.4.3 DMA System Connections

The connection of the GPDMA to the supported peripheral devices depends on the DMA
functions implemented in those peripherals. Table 561 shows the DMA Request numbers
used by the supported peripherals.
Table 561. DMA Connections

Peripheral Function DMA Single DMA Burst DMA Last Word DMA Last Burst
Request Input Request Input Request Input Request Input
SSP0 Tx 0 0 - -
SSP0 Rx 1 1 - -
SSP1 Tx 2 2 - -

Table 561. DMA Connections

Peripheral Function DMA Single DMA Burst DMA Last Word DMA Last Burst
Request Input Request Input Request Input Request Input
SSP1 Rx 3 3 - -
SD/MMC 4 4 4 4
I2S channel 0 - 5 - -
I2S channel 1 - 6 - -
30.5 Programmer’s model

This chapter describes the GPDMA registers and provides details required when
programming the microcontroller. It contains the following sections:
• About the programmer’s model.

• Programming the GPDMA.
• Summary of GPDMA registers.
• Register descriptions.
• Address generation.
• Scatter/gather.
• Interrupt requests.
• GPDMA data flow.
30.6 About the programmer’s model

The GPDMA enables peripheral-to-memory, memory-to-peripheral,
peripheral-to-peripheral, and memory-to-memory transactions. Each DMA stream is
configured to provide unidirectional DMA transfers for a single source and destination.
The source and destination areas can each be either a memory region or a peripheral
which supports the GPDMA, and must be accessible through AHB1.
30.7 Programming the GPDMA

The following applies to the registers used in the GPDMA:
• Reserved or unused address locations must not be accessed because this can result
in unpredictable behavior of the device.
• Reserved or unused bits of registers must be written as zero, and ignored on read
unless otherwise stated in the relevant text.
• All register bits are reset to a logic 0 by a system or power-on reset unless otherwise
stated in the relevant text.
• Unless otherwise stated in the relevant text, all registers support read and write
accesses. A write updates the contents of a register and a read returns the contents
of the register.
• All registers defined in this document can only be accessed using word reads and
word writes (i.e. 32 bit accesses), unless otherwise stated in the relevant text.

30.7.1 Enabling the GPDMA

To enable the GPDMA set the DMA Enable bit in the DMACConfiguration Register
(Section 30.9.13 “Configuration Register (DMACConfiguration - 0xFFE0 4030)”.
30.7.2 Disabling the GPDMA

To disable the GPDMA:
1. Read the DMACEnbldChns Register and ensure that all the DMA channels have
been disabled. If any channels are active, see Section 30.7.4 “Disabling a DMA
Channel”.
2. Disable the GPDMA by writing 0 to the DMA Enable bit in the DMACConfiguration
Register (Section 30.10.6 “Channel Configuration Registers (DMACC0Configuration -
0xFFE0 4110 and DMACC1Configuration - 0xFFE0 4130)”).
30.7.3 Enabling a DMA Channel

To enable the DMA channel set the Channel Enable bit in the relevant DMA channel
Configuration Register (Section 30.10.6 “Channel Configuration Registers
(DMACC0Configuration - 0xFFE0 4110 and DMACC1Configuration - 0xFFE0 4130)”).
Note: The channel must be fully initialized before it is enabled. Additionally, you must set
the Enable bit of the GPDMA before any channels are enabled.
30.7.4 Disabling a DMA Channel

You can disable a DMA channel in the following ways:
• Write directly to the Channel Enable bit. Any outstanding data in the FIFOs is lost if
this method is used.
• Use the Active and Halt bits in conjunction with the Channel Enable bit.
• Wait until the transfer completes. The channel is then automatically disabled.
30.7.5 Disabling a DMA Channel Without Losing Data in the FIFO

To disable a DMA channel without losing data in the FIFO:
1. Set the Halt bit in the relevant channel Configuration Register (Section 30.10.6
“Channel Configuration Registers (DMACC0Configuration - 0xFFE0 4110 and
DMACC1Configuration - 0xFFE0 4130)”). This causes any further DMA requests to
be ignored.
2. Poll the Active bit in the relevant channel Configuration Register until it reaches 0.
This bit indicates whether there is any data in the channel which has to be transferred.
3. Clear the Channel Enable bit in the relevant channel Configuration Register.
30.7.6 Setup a New DMA Transfer

To set up a new DMA transfer:
1. If the channel is not set aside for the DMA transaction:

– Read the DMACEnbldChns Register and find out which channels are inactive (see
Section 30.9.8 “Enabled Channel Register (DMACEnbldChns - 0xFFE0 401C)”).

– Choose an inactive channel that has the required priority.

2. Program the GPDMA.
30.7.7 Disabling a DMA Channel and Losing Data in the FIFO

Clear the relevant Channel Enable bit in the relevant channel Configuration Register
(Section 30.10.6 “Channel Configuration Registers (DMACC0Configuration -
0xFFE0 4110 and DMACC1Configuration - 0xFFE0 4130)”). The current AHB transfer, if
one is in progress, completes and the channel is disabled. Any data in the FIFO is lost.
30.7.8 Halting a DMA Transfer

Set the Halt bit in the relevant DMA channel Configuration Register. The current source
request is serviced. Any further source DMA requests are ignored until the Halt bit is
cleared.
30.7.9 Programming a DMA Channel

To program a DMA channel:
1. Choose a free DMA channel with the priority required. DMA channel 0 has the highest
priority and DMA channel 1 the lowest priority.
2. Clear any pending interrupts on the channel to be used by writing to the
DMACIntTCClr Register (Section 30.9.3 “Interrupt Terminal Count Clear Register
(DMACIntClear - 0xFFE0 4008)”) and DMACIntErrClr Register (Section 30.9.5
“Interrupt Error Clear Register (DMACIntErrClr - 0xFFE0 4010)”). The previous
channel operation might have left interrupts active.
3. Write the source address into the DMACCxSrcAddr Register (Section 30.10.1
“Channel Source Address Registers (DMACC0SrcAddr - 0xFFE0 4100 and
DMACC1SrcAddr - 0xFFE0 4120)”).
4. Write the destination address into the DMACCxDestAddr Register (Section 30.10.2
“Channel Destination Address Registers (DMACC0DestAddr - 0xFFE0 4104 and
DMACC1DestAddr - 0xFFE0 4124)”).
5. Write the address of the next Linked List Item (LLI) into the DMACCxLLI Register
(Section 30.10.3 “Channel Linked List Item Registers (DMACC0LLI - 0xFFE0 4108
and DMACC1LLI - 0xFFE0 4128)”). If the transfer consists of a single packet of data
then 0 must be written into this register.
6. Write the control information into the DMACCxControl Register (Section 30.10.4
“Channel Control Registers (DMACC0Control - 0xFFE0 410C and DMACC0Control -
0xFFE0 412C)”).
7. Write the channel configuration information into the DMACCxConfiguration Register
(Section 30.10.6 “Channel Configuration Registers (DMACC0Configuration -
0xFFE0 4110 and DMACC1Configuration - 0xFFE0 4130)”). If the Enable bit is set
then the DMA channel is automatically enabled.
30.8 Summary of GPDMA registers

The GPDMA registers are shown in Table 562.

Table 562. GPDMA register map

General Registers
DMACIntStatus Interrupt Status Register RO 0x0 0xFFE0 4000
DMACIntTCStatus Interrupt Terminal Count RO 0x0 0xFFE0 4004
Status Register
DMACIntTCClear Interrupt Terminal Count Clear WO - 0xFFE0 4008
Register
DMACIntErrorStatus Interrupt Error Status Register RO 0x0 0xFFE0 400C
DMACIntErrClr Interrupt Error Clear Register WO - 0xFFE0 4010
DMACRawIntTCStatus Raw Interrupt Terminal Count RO - 0xFFE0 4014
Status Register
DMACRawIntErrorStatus Raw Error Interrupt Status RO - 0xFFE0 4018
Register
DMACEnbldChns Enabled Channel Register RO 0x0 0xFFE0 401C
DMACSoftBReq Software Burst Request R/W 0x0000 0xFFE0 4020
Register
DMACSoftSReq Software Single Request R/W 0x0000 0xFFE0 4024
Register
DMACSoftLBReq Software Last Burst Request R/W 0x0000 0xFFE0 4028
Register
DMACSoftLSReq Software Last Single Request R/W 0x0000 0xFFE0 402C
Register
DMACConfiguration Configuration Register R/W 0x0000 0000 0xFFE0 4030
DMACSync Synchronization Register R/W 0x0000 0xFFE0 4034
Channel 0 Registers
DMACC0SrcAddr Channel 0 Source Address R/W 0x0000 0000 0xFFE0 4100
Register
DMACC0DestAddr Channel 0 Destination R/W 0x0000 0000 0xFFE0 4104
Address Register
DMACC0LLI Channel 0 Linked List Item R/W 0x0000 0000 0xFFE0 4108
Register
DMACC0Control Channel 0 Control Register R/W 0x0000 0000 0xFFE0 410C
DMACC0Configuration Channel 0 Configuration R/W 0x00000 [1] 0xFFE0 4110
Register
Channel 1 Registers
DMACC1SrcAddr Channel 1 Source Address R/W 0x0000 0000 0xFFE0 4120
Register
DMACC1DestAddr Channel 1 Destination R/W 0x0000 0000 0xFFE0 4124
Address Register
DMACC1LLI Channel 1 Linked List Item R/W 0x0000 0000 0xFFE0 4128
Register
DMACC1Control Channel 1 Control Register R/W 0x0000 0000 0xFFE0 412C
DMACC1Configuration Channel 1 Configuration R/W 0x00000 [1] 0xFFE0 4130
Register
[1] Bit [17] is read-only.

30.9 Register descriptions

This section describes the registers of the GPDMA.
30.9.1 Interrupt Status Register (DMACIntStatus - 0xFFE0 4000)

The DMACIntStatus Register is read-only and shows the status of the interrupts after
masking. A HIGH bit indicates that a specific DMA channel interrupt request is active. The
request can be generated from either the error or terminal count interrupt requests.
Table 563 shows the bit assignments of the DMACIntStatus Register.
Table 563. Interrupt Status register (DMACIntStatus - address 0xFFE0 4000) bit description
Value
0 IntStatus0 Status of channel 0 interrupts after masking. 0
1 IntStatus1 Status of channel 1 interrupts after masking. 0
30.9.2 Interrupt Terminal Count Status Register (DMACIntTCStatus -

0xFFE0 4004)
The DMACIntTCStatus Register is read-only and indicates the status of the terminal count
after masking. Table 564 shows the bit assignments of the DMACIntTCStatus Register.
Table 564. Interrupt Terminal Count Status register (DMACIntTCStatus - address

Value
0 IntTCStatus0 Terminal count interrupt request status for channel 0. 0
1 IntTCStatus1 Terminal count interrupt request status for channel 1. 0
30.9.3 Interrupt Terminal Count Clear Register (DMACIntClear -

0xFFE0 4008)
The DMACIntTCClear Register is write-only and clears a terminal count interrupt request.
When writing to this register, each data bit that is set HIGH causes the corresponding bit
in the status register to be cleared. Data bits that are LOW have no effect on the
corresponding bit in the register. Table 565 shows the bit assignments of the
DMACIntTCClear Register.

Table 565. Interrupt Terminal Count Clear register (DMACIntClear - address 0xFFE0 4008) bit
description
Value
0 IntTCClear0 Writing a 1 clears the terminal count interrupt request for -
channel 0 (IntTCStatus0).
1 IntTCClear1 Writing a 1 clears the terminal count interrupt request for -
channel 1 (IntTCStatus1).
30.9.4 Interrupt Error Status Register (DMACIntErrorStatus - 0xFFE0 400C)

The DMACIntErrorStatus Register is read-only and indicates the status of the error
request after masking. Table 566 shows the bit assignments of the DMACIntErrorStatus
Register.
Table 566. Interrupt Error Status register (DMACIntErrorStatus - address 0xFFE0 400C) bit
description
Value
0 IntErrorStatus0 Interrupt error status for channel 0. 0x0
1 IntErrorStatus1 Interrupt error status for channel 1. 0x0
30.9.5 Interrupt Error Clear Register (DMACIntErrClr - 0xFFE0 4010)

The DMACIntErrClr Register is write-only and clears the error interrupt requests. When
writing to this register, each data bit that is HIGH causes the corresponding bit in the
status register to be cleared. Data bits that are LOW have no effect on the corresponding
bit in the register. Table 567 shows the bit assignments of the DMACIntErrClr Register.
Table 567. Interrupt Error Clear register (DMACIntErrClr - address 0xFFE0 4010) bit
description
Value
0 IntErrClr0 Writing a 1 clears the error interrupt request for channel 0 -
(IntErrorStatus0).
1 IntErrClr1 Writing a 1 clears the error interrupt request for channel 1 -
(IntErrorStatus1).
30.9.6 Raw Interrupt Terminal Count Status Register (DMACRawIntTCStatus

- 0xFFE0 4014)
The DMACRawIntTCStatus Register is read-only and indicates which DMA channel is
requesting a transfer complete (terminal count interrupt) prior to masking. A HIGH bit
indicates that the terminal count interrupt request is active prior to masking. Table 568
shows the bit assignments of the DMACRawIntTCStatus Register.

Table 568. Raw Interrupt Terminal Count Status register (DMACRawIntTCStatus - address
Value
0 RawIntTCStatus0 Status of the terminal count interrupt for channel 0 prior to -
masking.
1 RawIntTCStatus1 Status of the terminal count interrupt for channel 1 prior to -
masking.
30.9.7 Raw Error Interrupt Status Register (DMACRawIntErrorStatus -

0xFFE0 4018)
The DMACRawIntErrorStatus Register is read-only and indicates which DMA channel is
requesting an error interrupt prior to masking. A HIGH bit indicates that the error interrupt
request is active prior to masking. Table 569 shows the bit assignments of register of the
DMACRawIntErrorStatus Register.
Table 569. Raw Error Interrupt Status register (DMACRawIntErrorStatus - address

Value
0 RawIntErrorStatus0 Status of the error interrupt for channel 0 prior to masking. -
1 RawIntErrorStatus1 Status of the error interrupt for channel 1 prior to masking. -
30.9.8 Enabled Channel Register (DMACEnbldChns - 0xFFE0 401C)

The DMACEnbldChns Register is read-only and indicates which DMA channels are
enabled, as indicated by the Enable bit in the DMACCxConfiguration Register. A HIGH bit
indicates that a DMA channel is enabled. A bit is cleared on completion of the DMA
transfer. Table 570 shows the bit assignments of the DMACEnbldChns Register.
Table 570. Enabled Channel register (DMACEnbldChns - address 0xFFE0 401C) bit
description
Value
0 EnabledChannels0 Enable status for Channel 0. 0
1 EnabledChannels1 Enable status for Channel 1. 0
30.9.9 Software Burst Request Register (DMACSoftBReq - 0xFFE0 4020)

The DMACSoftBReq Register is read/write and enables DMA burst requests to be
generated by software. A DMA request can be generated for each source by writing a 1 to
the corresponding register bit. A register bit is cleared when the transaction has
completed. Writing 0 to this register has no effect. Reading the register indicates which

sources are requesting DMA burst transfers. A request can be generated from either a
peripheral or the software request register. Table 571 shows the bit assignments of the
DMACSoftBReq Register.
Table 571. Software Burst Request register (DMACSoftBReq - address 0xFFE0 4020) bit
description
Value
0 SoftBReqSSP0Tx Software burst request flag for SSP0 Tx. 0
1 SoftBReqSSP0Rx Software burst request flag for SSP0 Rx. 0
2 SoftBReqSSP1Tx Software burst request flag for SSP1 Tx. 0
3 SoftBReqSSP1Rx Software burst request flag for SSP1 Rx. 0
4 SoftBReqSDMMC Software burst request flag for SD/MMC. 0
5 SoftBReqI2S0 Software burst request flag for I2S0. 0
6 SoftBReqI2S1 Software burst request flag for I2S1. 0
Note: It is recommended that software and hardware peripheral requests are not used at
the same time.
30.9.10 Software Single Request Register (DMACSoftSReq - 0xFFE0 4024)

The DMACSoftSReq Register is read/write and enables DMA single requests to be
sources are requesting single DMA transfers. A request can be generated from either a
peripheral or the software request register. Table 572 shows the bit assignments of the
DMACSoftSReq Register.
Table 572. Software Single Request register (DMACSoftSReq - address 0xFFE0 4024) bit
description
Value
0 SoftReqSSP0Tx Single software request flag for SSP0 Tx. 0
1 SoftReqSSP0Rx Single software request flag for SSP0 Rx. 0
2 SoftReqSSP1Tx Single software request flag for SSP1 Tx. 0
3 SoftReqSSP1Rx Single software request flag for SSP1 Rx. 0
4 SoftReqSDMMC Single software request flag for SD/MMC. 0
30.9.11 Software Last Burst Request Register (DMACSoftLBreq -

0xFFE0 4028)
The DMACSoftLBReq Register is read/write and enables DMA last burst requests to be

sources are requesting last burst DMA transfers. A request can be generated from either
a peripheral or the software request register. Table 573 shows the bit assignments of the
DMACSoftLBReq Register.
Table 573. Software Last Burst Request register (DMACSoftLBReq - address 0xFFE0 4028)
bit description
Value
4 SoftLBReqSDMMC Software last burst request flags for SD/MMC. 0
30.9.12 Software Last Single Request Register (DMACSoftLSReq -

0xFFE0 402C)
The DMACSoftLSReq Register is read/write and enables DMA last single requests to be
sources are requesting last single DMA transfers. A request can be generated from either
a peripheral or the software request register. Table 574 shows the bit assignments of the
DMACSoftLSReq Register.
Table 574. Software Last Single Request register (DMACSoftLSReq - address 0xFFE0 402C)
bit description
Value
4 SoftLSReqSDMMC Software last single request flags for SD/MMC. 0
30.9.13 Configuration Register (DMACConfiguration - 0xFFE0 4030)

The DMACConfiguration Register is read/write and configures the operation of the
GPDMA. The endianness of the AHB master interface can be altered by writing to the M
bit of this register. The AHB master interface is set to little-endian mode on reset.
Table 575 shows the bit assignments of the DMACConfiguration Register.
Table 575. Configuration register (DMACConfiguration - address 0xFFE0 4030) bit

description
Value
0 E GPDMA enable: 0
0 Disabled. Disabling the GPDMA reduces power consumption.
1 Enabled.

Table 575. Configuration register (DMACConfiguration - address 0xFFE0 4030) bit

description
Value
1 M AHB Master endianness configuration: 0
0 Little-endian mode.
1 Big-endian mode.
30.9.14 Synchronization Register (DMACSync - 0xFFE0 4034)

The DMACSync Register is read/write and enables or disables synchronization logic for
the DMA request signals. The DMA request signals consist of the DMACBREQ[15:0],
DMACSREQ[15:0], DMACLBREQ[15:0], and DMACLSREQ[15:0]. A bit set to 0 enables
the synchronization logic for a particular group of DMA requests. A bit set to 1 disables the
synchronization logic for a particular group of DMA requests. This register is reset to 0,
synchronization logic enabled.
Table 576 shows the bit assignments of the DMACSync Register.
Table 576. Synchronization register (DMACSync - address 0xFFE0 4034) bit description
Value
15:0 DMACSync DMA synchronization logic for DMA request signals enabled or 0x0000
disabled. A LOW bit indicates that the synchronization logic for
the DMACBREQ[15:0], DMACSREQ[15:0],
DMACLBREQ[15:0], and DMACLSREQ[15:0] request signals
is enabled. A HIGH bit indicates that the synchronization logic
is disabled.
30.10 Channel registers

The channel registers are used to program the two DMA channels. These registers
consist of:
• Two DMACCxSrcAddr Registers

• Two DMACCxDestAddr Registers
• Two DMACCxLLI Registers
• Two DMACCxControl Registers
• Two DMACCxConfiguration Registers
When performing scatter/gather DMA the first four registers are automatically updated.

30.10.1 Channel Source Address Registers (DMACC0SrcAddr - 0xFFE0 4100

and DMACC1SrcAddr - 0xFFE0 4120)
The two read/write DMACCxSrcAddr Registers contain the current source address
(byte-aligned) of the data to be transferred. Each register is programmed directly by
software before the appropriate channel is enabled. When the DMA channel is enabled
this register is updated:
• As the source address is incremented.

• By following the linked list when a complete packet of data has been transferred.
Reading the register when the channel is active does not provide useful information. This
is because by the time software has processed the value read, the channel might have
progressed. It is intended to be read only when the channel has stopped, in which case it
shows the source address of the last item read.
Note: The source and destination addresses must be aligned to the source and
destination widths.
Table 577 shows the bit assignments of the DMACCxSrcAddr Registers.
Table 577. Channel Source Address registers (DMACC0SrcAddr - address 0xFFE0 4100 and
DMACC1SrcAddr - address 0xFFE0 4120) bit description
31:0 SrcAddr DMA source address. 0x0000 0000
30.10.2 Channel Destination Address Registers (DMACC0DestAddr -

0xFFE0 4104 and DMACC1DestAddr - 0xFFE0 4124)
The two read/write DMACCxDestAddr Registers contain the current destination address
(byte-aligned) of the data to be transferred. Each register is programmed directly by
software before the channel is enabled. When the DMA channel is enabled the register is
updated as the destination address is incremented and by following the linked list when a
complete packet of data has been transferred. Reading the register when the channel is
active does not provide useful information. This is because by the time that software has
processed the value read, the channel might have progressed. It is intended to be read
only when a channel has stopped, in which case it shows the destination address of the
last item read. Table 578 shows the bit assignments of the DMACCxDestAddr Register.
Table 578. Channel Destination Address registers (DMACC0DestAddr - address

0xFFE0 4104 and DMACC1DestAddr - address 0xFFE0 4124) bit description
31:0 DestAddr DMA destination address 0x0000 0000
30.10.3 Channel Linked List Item Registers (DMACC0LLI - 0xFFE0 4108 and
DMACC1LLI - 0xFFE0 4128)
The two read/write DMACCxLLI Registers contain a word-aligned address of the next
Linked List Item (LLI). If the LLI is 0, then the current LLI is the last in the chain, and the
DMA channel is disabled when all DMA transfers associated with it are completed.
Note: Programming this register when the DMA channel is enabled has unpredictable
side effects.

Table 579 shows the bit assignments of the DMACCxLLI Register.
Table 579. Channel Linked List Item registers (DMACC0LLI - address 0xFFE0 4108 and
DMACC1LLI - address 0xFFE0 4128) bit description
0 Reserved Reserved, read as zero, do not modify. NA
1 R Reserved, and must be written as 0, masked on read. 0
31:2 LLI Linked list item. Bits [31:2] of the address for the next LLI. 0
Address bits [1:0] are 0.
Note: To make loading the LLIs more efficient for some systems, the LLI data structures
can be made four-word aligned.
30.10.4 Channel Control Registers (DMACC0Control - 0xFFE0 410C and

DMACC0Control - 0xFFE0 412C)
The two read/write DMACCxControl Registers contain DMA channel control information
such as the transfer size, burst size, and transfer width. Each register is programmed
directly by software before the DMA channel is enabled. When the channel is enabled the
register is updated by following the linked list when a complete packet of data has been
transferred. Reading the register while the channel is active does not give useful
information. This is because by the time software has processed the value read, the
channel might have progressed. It is intended to be read only when a channel has
stopped. Table 580 shows the bit assignments of the DMACCxControl Register.
Table 580. Channel Control registers (DMACC0Control - address 0xFFE0 410C and
DMACC1Control - address 0xFFE0 412C) bit description
11:0 TransferSize Transfer size. A write to this field sets the size of the transfer 0
when the GPDMA is the flow controller.A read from this field
indicates the number of transfers completed on the
destination bus. Reading the register when the channel is
active does not give useful information because by the time
that the software has processed the value read, the channel
might have progressed. It is intended to be used only when a
channel is enabled and then disabled.The transfer size value
is not used if the GPDMA is not the flow controller.
14:12 SBSize Source burst size. Indicates the number of transfers that 0
make up a source burst. This value must be set to the burst
size of the source peripheral, or if the source is memory, to
the memory boundary size. The burst size is the amount of
data that is transferred when the DMACBREQ signal goes
active in the source peripheral.
17:15 DBsize Destination burst size. Indicates the number of transfers that 0
make up a destination burst transfer request. This value must
be set to the burst size of the destination peripheral, or if the
destination is memory, to the memory boundary size. The
burst size is the amount of data that is transferred when the
DMACBREQ signal goes active in the destination peripheral.
20:18 SWidth Source transfer width. Transfers wider than the AHB master 0
bus width are illegal.The source and destination widths can
be different from each other. The hardware automatically
packs and unpacks the data as required.

Table 580. Channel Control registers (DMACC0Control - address 0xFFE0 410C and
DMACC1Control - address 0xFFE0 412C) bit description
23:21 DWidth Destination transfer width. Transfers wider than the AHB 0
master bus width are not supported.The source and
destination widths can be different from each other. The
hardware automatically packs and unpacks the data as
required.
26 SI Source increment. When set the source address is 0
incremented after each transfer.
27 DI Destination increment. When set the destination address is 0
incremented after each transfer.
30:28 Prot Protection. 0
31 I Terminal count interrupt enable bit. It controls whether the 0
current LLI is expected to trigger the terminal count interrupt.
Table 581 shows the value of the 3 bit DBSize or SBSize fields and the corresponding
burst sizes.
Table 581. Source or destination burst size

Bit value of DBSize or SBSize Source or distention burst transfer request size
000 1
001 4
010 8
011 16
100 32
101 64
110 128
111 256
Table 582 shows the value of the 3 bit SWidth or DWidth fields and the corresponding
transfer width.
Table 582. Source or destination transfer width

Bit value of DBWidth or SBWidth Source or distention burst transfer request size
000 Byte (8 bit)
001 Halfword (16 bit)
010 Word (32 bit)
011 and 1xxx Reserved
30.10.5 Protection and Access Information

AHB access information is provided to the source and destination peripherals when a
transfer occurs. The transfer information is provided by programming the DMA channel
(the Prot bit of the DMACCxControl Register, and the Lock bit of the
DMACCxConfiguration Register). These bits are programmed by software and
peripherals can use this information if necessary. Three bits of information are provided,
and Table 583 shows the purpose of the three protection bits.

Table 583. Protection bits

DMACC1Control Value Description Reset
Bit Value
28 Privileged or User. This bit controls the AHB HPROT[1] signal. 0
Indicates that the access is in User, or privileged mode:
0 User mode.
1 Privileged mode.
29 Bufferable or not bufferable. This bit indicates that the access 0
is bufferable. This bit can, for example, be used to indicate to
an AMBA bridge that the read can complete in zero wait states
on the source bus without waiting for it to arbitrate for the
destination bus and for the slave to accept the data. This bit
controls the AHB HPROT[2] signal.
Indicates that the access is bufferable, or not bufferable:
0 Not bufferable.
1 Bufferable.
30 Cacheable or not cacheable. This indicates that the access is 0
cacheable. This bit can, for example, be used to indicate to an
AMBA bridge that when it saw the first read of a burst of eight it
can transfer the whole burst of eight reads on the destination
bus, rather than pass the transactions through one at a time.
This bit controls the AHB HPROT[3] signal.
Indicates that the access is cacheable or not cacheable:
0 Not cacheable.
1 Cacheable.
30.10.6 Channel Configuration Registers (DMACC0Configuration -

0xFFE0 4110 and DMACC1Configuration - 0xFFE0 4130)
The two DMACCxConfiguration Registers are read/write with the exception of bit[17]
which is read-only. Used these to configure the DMA channel. The registers are not
updated when a new LLI is requested. Table 584 shows the bit assignments of the
DMACCxConfiguration Register.

Table 584. Channel Configuration registers (DMACC0Configuration - address 0xFFE0 4110 and
DMACC1Configuration - address 0xFFE0 4130) bit description
Value
0 E The Channel Enable bit status can also be found by reading the DMACEnbldChns 0
Register.
A channel is enabled by setting this bit.
A channel can be disabled by clearing the Enable bit. This causes the current AHB
transfer (if one is in progress) to complete and the channel is then disabled. Any
data in the FIFO of the relevant channel is lost. Restarting the channel by setting the
Channel Enable bit has unpredictable effects and the channel must be fully
re-initialized.
The channel is also disabled, and Channel Enable bit cleared, when the last LLI is
reached or if a channel error is encountered.
If a channel has to be disabled without losing data in the FIFO the Halt bit must be
set so that further DMA requests are ignored. The Active bit must then be polled
until it reaches 0, indicating that there is no data left in the FIFO. Finally the Channel
Enable bit can be cleared.
Channel enable -- reading this bit indicates whether a channel is currently enabled
or disabled:
0 Channel disabled.
1 Channel enabled.
4:1 SrcPeripheral Source peripheral. This value selects the DMA source request peripheral.This field 0
is ignored if the source of the transfer is from memory.
0000 SSP0 Tx
0001 SSP0 Rx
0010 SSP1 Tx
0011 SSP1 Rx
0100 SD/MMC
0101 I2S channel 0
0110 I2S channel 1
0111 These values are reserved and should not be used.
or
1xxx
5 - - Reserved, do not modify, masked on read. NA
9:6 DestPeriphera Destination peripheral. This value selects the DMA destination request peripheral. 0
l This field is ignored if the destination of the transfer is to memory. See the
SrcPeripheral symbol description for values.
10 - - Reserved, do not modify, masked on read. NA
13:11 FlowCntrl Flow control and transfer type. This value indicates the flow controller and transfer 0
type. The flow controller can be the GPDMA, the source peripheral, or the
destination peripheral.The transfer type can be memory-to-memory,
memory-to-peripheral, peripheral-to-memory, or peripheral-to-peripheral.
14 IE Interrupt error mask. When cleared this bit masks out the error interrupt of the 0
relevant channel.
15 ITC Terminal count interrupt mask. When cleared this bit masks out the terminal count 0
interrupt of the relevant channel.
16 L Lock. When set, this bit enables locked transfers. 0

Table 584. Channel Configuration registers (DMACC0Configuration - address 0xFFE0 4110 and
DMACC1Configuration - address 0xFFE0 4130) bit description
Value
17 A Active. This value can be used with the Halt and Channel Enable bits to cleanly
disable a DMA channel. Writing to this bit has no effect.
0 There is no data in the FIFO of the channel.
1 The channel FIFO has data.
18 H Halt. The contents of the channel FIFO are drained. This value can be used with the 0
Active and Channel Enable bits to cleanly disable a DMA channel.
0 Enable DMA requests.
1 Ignore further source DMA requests.
31:19 - Reserved, do not modify, masked on read. NA
30.10.7 Lock control

Set the lock bit by programming bit 16 in the DMACCxConfiguration Register.
When a burst occurs, the AHB arbiter must not de-grant the master during the burst until
the lock is deasserted. The GPDMA can be locked for a a single burst such as a long
source fetch burst or a long destination drain burst. The GPDMA does not usually assert
the lock continuously for a source fetch burst followed by a destination drain burst.
There are situations when the GPDMA asserts the lock for source transfers followed by
destination transfers. This is possible when internal conditions in the GPDMA permit it to
perform a source fetch followed by a destination drain back-to-back.
30.10.8 Flow control and transfer type

Table 585 lists the bit values of the three flow control and transfer type bits.
Table 585. Flow control and transfer type bits

Bit Value Transfer Type Controller
000 Memory to memory. DMA
001 Memory to peripheral. DMA
010 Peripheral to memory. DMA
011 Source peripheral to destination peripheral. DMA
100 Source peripheral to destination peripheral. Destination peripheral.
101 Memory to peripheral. Peripheral.
110 Peripheral to memory. Peripheral.
111 Source peripheral to destination peripheral. Source peripheral.
30.11 Address generation

Address generation can be either incrementing or non-incrementing (address wrapping is
not supported). Bursts do not cross the 1 kB address boundary.

30.12 Scatter/Gather
Scatter/gather is supported through the use of linked lists. This means that the source and
destination areas do not have to occupy contiguous areas in memory. Where
scatter/gather is not required the DMACCxLLI Register must be set to 0.
The source and destination data areas are defined by a series of linked lists. Each Linked
List Item (LLI) controls the transfer of one block of data, and then optionally loads another
LLI to continue the DMA operation, or stops the DMA stream. The first LLI is programmed
into the GPDMA.
The data to be transferred described by a LLI (referred to as the packet of data) usually
requires one or more DMA bursts (to each of the source and destination).
30.12.1 Linked List Items

A Linked List Item (LLI) consists of four words. These words are organized in the following
order:
1. DMACCxSrcAddr.
2. DMACCxDestAddr.
3. DMACCxLLI.
4. DMACCxControl.
Note: The DMACCxConfiguration DMA channel Configuration Register is not part of the
linked list item.
30.12.2 Programming the GPDMA for scatter/gather DMA

To program the GPDMA for scatter/gather DMA:
1. Write the LLIs for the complete DMA transfer to memory. Each linked list item contains
four words:
– Source address.
– Destination address.
– Pointer to next LLI.
– Control word.
The last LLI has its linked list word pointer set to 0. The LLIs must be stored in the
memory where the GPDMA has access to (i.e. AHB1 SRAM and external memory).
2. Choose a free DMA channel with the priority required. DMA channel 0 has the highest
priority and DMA channel 1 the lowest priority.
3. Write the first linked list item, previously written to memory, to the relevant channel in
the GPDMA.
4. Write the channel configuration information to the channel Configuration Register and
set the Channel Enable bit. The GPDMA then transfers the first and then subsequent
packets of data as each linked list item is loaded.

5. An interrupt can be generated at the end of each LLI depending on the Terminal
Count bit in the DMACCxControl Register. If this bit is set an interrupt is generated at
the end of the relevant LLI. The interrupt request must then be serviced and the
relevant bit in the DMACIntTCClear Register must be set to clear the interrupt.
30.12.3 Example of scatter/gather DMA

See Figure 139 for an example of an LLI. A rectangle of memory has to be transferred to
a peripheral. The addresses of each line of data are given, in hexadecimal, at the
left-hand side of the figure. The LLIs describing the transfer are to be stored contiguously
from address 0x20000.
0x--200 0x–E00
0x0A---
0x0B---
0x0C---
0x0D---
0x0E---
0x0F---
0x10---
0x11---
Fig 139. LLI example
The first LLI, stored at 0x20000, defines the first block of data to be transferred, which is
the data stored between addresses 0x0A200 and 0x0AE00:
• Source start address 0x0A200.

• Destination address set to the destination peripheral address.
• Transfer width, word (32 bit).
• Transfer size, 3 072 bytes (0XC00).
• Source and destination burst sizes, 16 transfers.
• Next LLI address, 0x20010.
The second LLI, stored at 0x20010 , describes the next block of data to be transferred:
• Source start address 0x0B200.

• Transfer size, 3 072 bytes (0xC00).

A chain of descriptors is built up, each one pointing to the next in the series. To initialize
the DMA stream, the first LLI, 0x20000, is programmed into the GPDMA. When the first
packet of data has been transferred the next LLI is automatically loaded.
The final LLI is stored at 0x20070 and contains:
• Source start address 0x11200.

• Transfer size, 3 072 bytes (0xC00).
Because the next LLI address is set to zero, this is the last descriptor, and the DMA
channel is disabled after transferring the last item of data. The channel is probably set to
generate an interrupt at this point to indicate to the ARM processor that the channel can
be reprogrammed.
30.13 Interrupt requests

Interrupt requests can be generated when an AHB error is encountered, or at the end of a
transfer (terminal count) after all the data corresponding to the current LLI has been
transferred to the destination. The interrupts can be masked by programming bits in the
relevant DMACCxControl and DMACCxConfiguration Channel Registers. Interrupt status
registers are provided which group the interrupt requests from all the DMA channels prior
to interrupt masking (DMACRawIntTCStatus and DMACRawIntErrorStatus), and after
interrupt masking (DMACIntTCStatus and DMACIntErrorStatus). The DMACIntStatus
Register combines both the DMACIntTCStatus and DMACIntErrorStatus requests into a
single register to enable the source of an interrupt to be quickly found. Writing to the
DMACIntTCClear or the DMACIntErrClr Registers with a bit set HIGH enables selective
clearing of interrupts.
30.13.1 Hardware interrupt sequence flow

When a DMA interrupt request occurs, the Interrupt Service Routine needs to:
1. Read the DMACIntStatus Register to determine which channel generated the

interrupt. If more than one request is active it is recommended that the highest priority
channels be checked first.
2. Read the DMACIntTCStatus Register to determine whether the interrupt was
generated due to the end of the transfer (terminal count). A HIGH bit indicates that the
transfer completed.
3. Read the DMACIntErrorStatus Register to determine whether the interrupt was
generated due to an error occurring. A HIGH bit indicates that an error occurred.
4. Service the interrupt request.
5. For a terminal count interrupt write a 1 to the relevant bit of the DMACIntTCClr
Register. For an error interrupt write a 1 to the relevant bit of the DMACIntErrClr
Register to clear the interrupt request.

30.13.2 Interrupt polling sequence flow

Used when the GPDMA interrupt request signal is either masked out, disabled in the
interrupt controller or disabled in the processor. When polling the GPDMA, you must:
1. Read the DMACIntStatus Register. If none of the bits are HIGH repeat this step,
otherwise go to step 2. If more than one request is active it is recommended that the
highest priority channels be checked first.
2. Read the DMACIntTCStatus Register to determine whether the interrupt was
generated due to the end of the transfer (terminal count). A HIGH bit indicates that the
transfer completed.
3. Service the interrupt request.
4. For a terminal count interrupt write a 1 to the relevant bit of the DMACIntTCClr
Register. For an error interrupt write a 1 to the relevant bit of the DMACIntErrClr
Register to clear the interrupt request.
30.14 GPDMA data flow

This section describes the GPDMA data flow sequences for the four allowed transfer
types:
• Memory-to-peripheral.
• Peripheral-to-memory.
• Memory-to-memory.
• Peripheral-to-peripheral.
Each transfer type can have either the peripheral or the GPDMA as the flow controller so
there are eight possible control scenarios.
Table 586 indicates the request signals used for each type of transfer.
Table 586. DMA request signal usage

Transfer Direction Request Generator Flow Controller
Memory-to-peripheral Peripheral GPDMA
Memory-to-peripheral Peripheral Peripheral
Peripheral-to-memory Peripheral GPDMA
Peripheral-to-memory Peripheral Peripheral
Memory-to-memory GPDMA GPDMA
Source peripheral to destination Source peripheral and Source peripheral
peripheral destination peripheral
Source peripheral to destination Source peripheral and Destination peripheral
Source peripheral to destination Source peripheral and GPDMA
30.14.1 Peripheral-to-memory, or Memory-to-peripheral DMA Flow

For a peripheral-to-memory or memory-to-peripheral DMA flow the following sequence
occurs:

1. Program and enable the DMA channel.

2. Wait for a DMA request.
3. The GPDMA starts transferring data when:
– The DMA request goes active.
– The DMA stream has the highest pending priority.
– The GPDMA is the bus master of the AHB bus.
4. If an error occurs while transferring the data, an error interrupt is generated and
disables the DMA stream, and the flow sequence ends.
5. Decrement the transfer count if the GPDMA is performing the flow control.
6. If the transfer has completed (indicated by the transfer count reaching 0 if the GPDMA
is performing flow control, or by the peripheral sending a DMA request if the
peripheral is performing flow control):
– The GPDMA responds with a DMA acknowledge.
– The terminal count interrupt is generated (this interrupt can be masked).
– If the DMACCxLLI Register is not 0, then reload the DMACCxSrcAddr,
DMACCxDestAddr, DMACCxLLI, and DMACCxControl Registers and go back to
step 2. However, if DMACCxLLI is 0, the DMA stream is disabled and the flow
sequence ends.
30.14.2 Peripheral-to-peripheral DMA Flow

For a peripheral-to-peripheral DMA flow the following sequence occurs:

2. Wait for a source DMA request.
3. The GPDMA starts transferring data when:
– The DMA request goes active.
– The DMA stream has the highest pending priority.
– The GPDMA is the bus master of the AHB bus.
4. If an error occurs while transferring the data an error interrupt is generated, then
finishes.
5. Decrement the transfer count if the GPDMA is performing the flow control.
6. If the transfer has completed (indicated by the transfer count reaching 0 if the GPDMA
is performing flow control, or by the peripheral sending a DMA request if the
peripheral is performing flow control):
– The GPDMA responds with a DMA acknowledge to the source peripheral.
– Further source DMA requests are ignored.
7. When the destination DMA request goes active and there is data in the GPDMA FIFO,
transfer data into the destination peripheral.
8. If an error occurs while transferring the data, an error interrupt is generated and
disables the DMA stream, and the flow sequence ends.
9. If the transfer has completed it is indicated by the transfer count reaching 0 if the
GPDMA is performing flow control, or by the sending a DMA request if the peripheral
is performing flow control. The following happens:

– The GPDMA responds with a DMA acknowledge to the destination peripheral.

– The terminal count interrupt is generated (this interrupt can be masked).
DMACCxDestAddr, DMACCxLLI, and DMACCxControl Registers and go to back
to step 2. However, if DMACCxLLI is 0, the DMA stream is disabled and the flow
sequence ends.
30.14.3 Memory-to-memory DMA Flow

For a memory-to-memory DMA flow the following sequence occurs:

2. Transfer data whenever the DMA channel has the highest pending priority and the
GPDMA gains mastership of the AHB bus.
3. If an error occurs while transferring the data generate an error interrupt and disable
the DMA stream.
4. Decrement the transfer count.
5. If the count has reached zero:
– Generate a terminal count interrupt (the interrupt can be masked).
DMACCxDestAddr, DMACCxLLI, and DMACCxControl Registers and go to back
to step 2. However, if DMACCxLLI is 0, the DMA stream is disabled and the flow
sequence ends.
Note: Memory-to-memory transfers should be programmed with a low channel priority,

otherwise other DMA channels cannot access the bus until the memory-to-memory
transfer has finished, or other AHB masters cannot perform any transaction.
30.15 Flow control

The peripheral that controls the length of the packet is known as the flow controller. The
flow controller is usually the GPDMA where the packet length is programmed by software
before the DMA channel is enabled. If the packet length is unknown when the DMA
channel is enabled, either the source or destination peripherals can be used as the flow
controller.
For simple or low-performance peripherals that know the packet length (that is, when the
peripheral is the flow controller), a simple way to indicate that a transaction has completed
is for the peripheral to generate an interrupt and enable the processor to reprogram the
DMA channel.
The transfer size value (in the DMACCxControl register) is ignored if a peripheral is
configured as the flow controller.
When the DMA is transferred:
1. The GPDMA issues an acknowledge to the peripheral in order to indicate that the
transfer has finished.
2. A TC interrupt is generated, if enabled.
3. The GPDMA moves on to the next LLI.

UM10211
Chapter 31: LPC23XX EmbeddedTrace Module (ETM)
31.1 Features
• Closely track the instructions that the ARM core is executing.
• One external trigger input.
• 10 pin interface.
• All registers are programmed through JTAG interface.
• Does not consume power when trace is not being used.
• THUMB instruction set support.
31.2 Applications
As the microcontroller has significant amounts of on-chip memories, it is not possible to
determine how the processor core is operating simply by observing the external pins. The
ETM provides real-time trace capability for deeply embedded processor cores. It outputs
information about processor execution to a trace port. A software debugger allows
configuration of the ETM using a JTAG interface and displays the trace information that
has been captured, in a format that a user can easily understand.
31.3 Description
The ETM is connected directly to the ARM core and not to the main AMBA system bus. It
compresses the trace information and exports it through a narrow trace port. An external
Trace Port Analyzer captures the trace information under software debugger control.
Trace port can broadcast the Instruction trace information. Instruction trace (or PC trace)
shows the flow of execution of the processor and provides a list of all the instructions that
were executed. Instruction trace is significantly compressed by only broadcasting branch
addresses as well as a set of status signals that indicate the pipeline status on a cycle by
cycle basis. Trace information generation can be controlled by selecting the trigger
resource. Trigger resources include address comparators, counters and sequencers.
Since trace information is compressed the software debugger requires a static image of
the code being executed. Self-modifying code can not be traced because of this
restriction.
31.3.1 ETM configuration

The following standard configuration is selected for the ETM macrocell.
Table 587. ETM configuration

Resource number/type Small[1]
Pairs of address comparators 1
Data Comparators 0 (Data tracing is not supported)
Memory Map Decoders 4
Counters 1
Sequencer Present No

Table 587. ETM configuration

Resource number/type Small[1]
External Inputs 2
External Outputs 0
FIFOFULL Present Yes (Not wired)
FIFO depth 10 bytes
Trace Packet Width 4/8
[1] For details refer to ARM documentation "Embedded Trace Macrocell Specification (ARM IHI 0014E)".

Table 588. ETM pin description
TRACECLK Output Trace Clock. The trace clock signal provides the clock for the trace
port. PIPESTAT[2:0], TRACESYNC, and TRACEPKT[3:0] signals are
referenced to the rising edge of the trace clock. This clock is not
generated by the ETM block. It is to be derived from the system clock.
The clock should be balanced to provide sufficient hold time for the
trace data signals. Half rate clocking mode is supported. Trace data
signals should be shifted by a clock phase from TRACECLK. Refer to
Figure 3.14 page 3.26 and figure 3.15 page 3.27 in "ETM7 Technical
Reference Manual" (ARM DDI 0158B), for example circuits that
implements both half-rateclocking and shifting of the trace data with
respect to the clock. For TRACECLK timings refer to section 5.2 on
page 5-13 in "Embedded Trace Macrocell Specification" (ARM IHI
0014E).
PIPESTAT[2:0] Output Pipe Line status. The pipeline status signals provide a cycle-by-cycle
indication of what is happening in the execution stage of the processor
pipeline.
TRACESYNC Output Trace synchronization. The trace sync signal is used to indicate the
first packet of a group of trace packets and is asserted HIGH only for
the first packet of any branch address.
TRACEPKT[3:0] Output Trace Packet. The trace packet signals are used to output packaged
address and data information related to the pipeline status. All packets
are eight bits in length. A packet is output over two cycles. In the first
cycle, Packet[3:0] is output and in the second cycle, Packet[7:4] is
output.
EXTIN[0] Input External Trigger Input

The ETM contains 29 registers as shown in Table 589 below. They are described in detail
in the ARM IHI 0014E document published by ARM Limited.

Table 589. ETM Registers

Name Description Access Register
Encoding
ETM Control Controls the general operation of the ETM. R/W 000 0000
ETM Configuration Code Allows a debugger to read the number of RO 000 0001
each type of resource.
Trigger Event Holds the controlling event. WO 000 0010
Memory Map Decode Control Eight bit register, used to statically configure WO 000 0011
the memory map decoder.
ETM Status Holds the pending overflow status bit. RO 000 0100
System Configuration Holds the configuration information using the RO 000 0101
SYSOPT bus.
Trace Enable Control 3 Holds the trace on/off addresses. WO 000 0110
Trace Enable Control 2 Holds the address of the comparison. WO 000 0111
Trace Enable Event Holds the enabling event. WO 000 1000
Trace Enable Control 1 Holds the include and exclude regions. WO 000 1001
FIFOFULL Region Holds the include and exclude regions. WO 000 1010
FIFOFULL Level Holds the level below which the FIFO is WO 000 1011
considered full.
ViewData event Holds the enabling event. WO 000 1100
ViewData Control 1 Holds the include/exclude regions. WO 000 1101
Address Comparator 1 to 16 Holds the address of the comparison. WO 001 xxxx
Address Access Type 1 to 16 Holds the type of access and the size. WO 010 xxxx
Reserved - - 000 xxxx
Reserved - - 100 xxxx
Initial Counter Value 1 to 4 Holds the initial value of the counter. WO 101 00xx
Counter Enable 1 to 4 Holds the counter clock enable control and WO 101 01xx
event.
Counter reload 1 to 4 Holds the counter reload event. WO 101 10xx
Counter Value 1 to 4 Holds the current counter value. RO 101 11xx
Sequencer State and Control Holds the next state triggering events. - 110 00xx
External Output 1 to 4 Holds the controlling events for each output. WO 110 10xx
Reserved - - 110 11xx
Reserved - - 111 0xxx
Reserved - - 111 1xxx
31.6 Reset state of multiplexed pins

On the LPC2300, the ETM pin functions are multiplexed with GPIO, PWM, UART, and
CAN functions. In order to use the trace feature, the pins must be configured to select the
function. Details may be found in Table 120.

31.7 Block diagram

The block diagram of the ETM debug environment is shown below in Figure 140.
APPLICATION PCB
CONNECTOR
TRACE TRACE
10
PORT
ANALYZER ETM
TRIGGER PERIPHERAL
PERIPHERAL
CONNECTOR
Host RAM
running
ARM
debugger JTAG 5
INTERFACE
UNIT
ROM
EMBEDDED ICE
LAN
Fig 140. ETM debug environment block diagram

UM10211
Chapter 32: LPC23XX EmbeddedICE logic
32.1 Features
• No target resources are required by the software debugger in order to start the
debugging session.
• Allows the software debugger to talk via a JTAG (Joint Test Action Group) port directly
to the core.
• Inserts instructions directly in to the ARM7TDMI-S core.
• The ARM7TDMI-S core or the System state can be examined, saved or changed
depending on the type of instruction inserted.
• Allows instructions to execute at a slow debug speed or at a fast system speed.
32.2 Applications
The EmbeddedICE logic provides on-chip debug support. The debugging of the target
system requires a host computer running the debugger software and an EmbeddedICE
protocol convertor. EmbeddedICE protocol convertor converts the Remote Debug
Protocol commands to the JTAG data needed to access the ARM7TDMI-S core present
on the target system.
32.3 Description
The ARM7TDMI-S Debug Architecture uses the existing JTAG3 port as a method of
accessing the core. The scan chains that are around the core for production test are
reused in the debug state to capture information from the databus and to insert new
information into the core or the memory. There are two JTAG-style scan chains within the
ARM7TDMI-S. A JTAG-style Test Access Port Controller controls the scan chains. In
addition to the scan chains, the debug architecture uses EmbeddedICE logic which
resides on chip with the ARM7TDMI-S core. The EmbeddedICE has its own scan chain
that is used to insert watchpoints and breakpoints for the ARM7TDMI-S core. The
EmbeddedICE logic consists of two real-time watchpoint registers, together with a control
and status register. One or both of the watchpoint registers can be programmed to halt the
ARM7TDMI-S core. Execution is halted when a match occurs between the values
programmed into the EmbeddedICE logic and the values currently appearing on the
address bus, databus and some control signals. Any bit can be masked so that its value
does not affect the comparison. Either watchpoint register can be configured as a
watchpoint (i.e. on a data access) or a break point (i.e. on an instruction fetch). The
watchpoints and breakpoints can be combined such that:
• The conditions on both watchpoints must be satisfied before the ARM7TDMI core is
stopped. The CHAIN functionality requires two consecutive conditions to be satisfied
before the core is halted. An example of this would be to set the first breakpoint to
3. For more details refer to IEEE Standard 1149.1 - 1990 Standard Test Access Port and Boundary Scan Architecture.

trigger on an access to a peripheral and the second to trigger on the code segment
that performs the task switching. Therefore when the breakpoints trigger the
information regarding which task has switched out will be ready for examination.
• The watchpoints can be configured such that a range of addresses are enabled for
the watchpoints to be active. The RANGE function allows the breakpoints to be
combined such that a breakpoint is to occur if an access occurs in the bottom
256 bytes of memory but not in the bottom 32 bytes.
The ARM7TDMI-S core has a Debug Communication Channel function in-built. The
debug communication channel allows a program running on the target to communicate
with the host debugger or another separate host without stopping the program flow or
even entering the debug state. The debug communication channel is accessed as a
co-processor 14 by the program running on the ARM7TDMI-S core. The debug
communication channel allows the JTAG port to be used for sending and receiving data
without affecting the normal program flow. The debug communication channel data and
control registers are mapped in to addresses in the EmbeddedICE logic.
For more details refer to IEEE Standard 1149.1 - 1990 Standard Test Access Port and
Boundary Scan Architecture.

Table 590. EmbeddedICE pin description
DBGEN[1] Input Debug Enable. JTAG interface control signal (see Section 32.5). This pin
is not available on all LPC23xx parts. See Section 8.1 for availability of the
DBGEN pin.
TMS[1] Input Test Mode Select. The TMS pin selects the next state in the TAP state
machine.
TCK[2] Input Test Clock. This allows shifting of the data in, on the TMS and TDI pins. It
is a positive edgetriggered clock with the TMS and TCK signals that
define the internal state of the device.
Remark: This clock must be slower than 16 of the CPU clock (CCLK) for
the JTAG interface to operate.
TDI[1] Input Test Data In. This is the serial data input for the shift register.
TDO[2] Output Test Data Output. This is the serial data output from the shift register.
Data is shifted out of the device on the negative edge of the TCK signal.
nTRST[1] Input Test Reset. The nTRST pin can be used to reset the test logic within the
EmbeddedICE logic.
RTCK[1] Output Returned Test Clock. Extra signal added to the JTAG port. Required for
designs based on ARM7TDMI-S processor core. Multi-ICE (Development
system from ARM) uses this signal to maintain synchronization with
targets having slow or widely varying clock frequency. For details refer to
"Multi-ICE System Design considerations Application Note 72 (ARM DAI
0072A)".
Board designers may need to connect a weak bias resistor to this pin as
described below.
[1] This pin has a built-in pull-up resistor.

[2] This pin has no built-in pull-up and no built-in pull-down resistor.

32.5 JTAG usage notes

Remark: JTAG access to the LPC2300 is only possible if no code read protection is
selected, see Table 530.
On devices with DBGEN pin available (see Section 8.1), the JTAG port may be used
either for debug or for boundary scan. The state of the DBGEN pin determines which
function is available. When DBGEN = 0, the JTAG port may be used for boundary scan.
When DBGEN = 1, the JTAG port may be used for debug.

The EmbeddedICE logic contains 16 registers as shown in Table 591 below. The
ARM7TDMI-S debug architecture is described in detail in "ARM7TDMI-S (rev 4) Technical
Reference Manual" (ARM DDI 0234A) published by ARM Limited.
Table 591. EmbeddedICE logic registers

Name Width Description Address
Debug Control 6 Force debug state, disable interrupts 00000
Debug Status 5 Status of debug 00001
Debug Comms Control Register 32 Debug communication control register 00100
Debug Comms Data Register 32 Debug communication data register 00101
Watchpoint 0 Address Value 32 Holds watchpoint 0 address value 01000
Watchpoint 0 Address Mask 32 Holds watchpoint 0 address mask 01001
Watchpoint 0 Data Value 32 Holds watchpoint 0 data value 01010
Watchpoint 0 Data Mask 32 Holds watchpoint 0 data mask 01011
Watchpoint 0 Control Value 9 Holds watchpoint 0 control value 01100
Watchpoint 0 Control Mask 8 Holds watchpoint 0 control mask 01101
Watchpoint 1 Address Value 32 Holds watchpoint 1 address value 10000
Watchpoint 1 Address Mask 32 Holds watchpoint 1 address mask 10001
Watchpoint 1 Data Value 32 Holds watchpoint 1 data value 10010
Watchpoint 1 Data Mask 32 Holds watchpoint 1 data mask 10011
Watchpoint 1 Control Value 9 Holds watchpoint 1 control value 10100
Watchpoint 1 Control Mask 8 Holds watchpoint 1 control mask 10101
32.7 Block diagram

The block diagram of the debug environment is shown below in Figure 141.

JTAG PORT
serial
parallel
EMBEDDED ICE
interface
INTERFACE 5
EMBEDDED ICE
PROTOCOL
CONVERTER
host running debugger
ARM7TDMI-S
TARGET BOARD
Fig 141. EmbeddedICE debug environment block diagram

UM10211
Chapter 33: LPC23XX RealMonitor
33.1 Features
Remark: RealMonitor is a configurable software module which enables real time debug.
RealMonitor is developed by ARM Inc. Information presented in this chapter is taken from
the ARM document RealMonitor Target Integration Guide (ARM DUI 0142A). It applies to
a specific configuration of RealMonitor software programmed in the on-chip ROM boot
memory of this device.
• Allows user to establish a debug session to a currently running system without halting
or resetting the system.
• Allows user time-critical interrupt code to continue executing while other user
application code is being debugged.
33.2 Applications
Real time debugging.
33.3 Description
RealMonitor is a lightweight debug monitor that allows interrupts to be serviced while user
debug their foreground application. It communicates with the host using the DCC (Debug
Communications Channel), which is present in the EmbeddedICE logic. RealMonitor
provides advantages over the traditional methods for debugging applications in ARM
systems. The traditional methods include:
• Angel (a target-based debug monitor).

• Multi-ICE or other JTAG unit and EmbeddedICE logic (a hardware-based debug
solution).
Although both of these methods provide robust debugging environments, neither is

suitable as a lightweight real-time monitor.
Angel is designed to load and debug independent applications that can run in a variety of
modes, and communicate with the debug host using a variety of connections (such as a
serial port or ethernet). Angel is required to save and restore full processor context, and
the occurrence of interrupts can be delayed as a result. Angel, as a fully functional
target-based debugger, is therefore too heavyweight to perform as a real-time monitor.
Multi-ICE is a hardware debug solution that operates using the EmbeddedICE unit that is
built into most ARM processors. To perform debug tasks such as accessing memory or
the processor registers, Multi-ICE must place the core into a debug state. While the
processor is in this state, which can be millions of cycles, normal program execution is
suspended, and interrupts cannot be serviced.
RealMonitor combines features and mechanisms from both Angel and Multi-ICE to
provide the services and functions that are required. In particular, it contains both the
Multi-ICE communication mechanisms (the DCC using JTAG), and Angel-like support for

processor context saving and restoring. RealMonitor is pre-programmed in the on-chip

ROM memory (boot sector). When enabled It allows user to observe and debug while
parts of application continue to run. Refer to Section 33.4 “How to Enable RealMonitor” on
page 669 for details.
33.3.1 RealMonitor Components

As shown in Figure 142, RealMonitor is split in to two functional components:
DEBUGGER
host RDI 1.5.1
REALMONITOR.DLL RMHOST
RDI 1.5.1 RT
RealMonitor
JTAG UNIT
protocol
DCC transmissions
over the JTAG link
RMTARGET
TARGET BOARD AND
target
PROCESSOR
APPLICATION
Fig 142. RealMonitor Components
33.3.1.1 RMHost
This is located between a debugger and a JTAG unit. The RMHost controller,
RealMonitor.dll, converts generic Remote Debug Interface (RDI) requests from the
debugger into DCC-only RDI messages for the JTAG unit. For complete details on
debugging a RealMonitor-integrated application from the host, see the ARM RMHost User
Guide (ARM DUI 0137A).
33.3.1.2 RMTarget
This is pre-programmed in the on-chip ROM memory (boot sector), and runs on the target
hardware. It uses the EmbeddedICE logic, and communicates with the host using the
DCC. For more details on RMTarget functionality, see the RealMonitor Target Integration
Guide (ARM DUI 0142A).

33.3.2 How RealMonitor Works

In general terms, the RealMonitor operates as a state machine, as shown in Figure 143.
RealMonitor switches between running and stopped states, in response to packets
received by the host, or due to asynchronous events on the target. RMTarget supports the
triggering of only one breakpoint, watchpoint, stop, or semihosting SWI at a time. There is
no provision to allow nested events to be saved and restored. So, for example, if user
application has stopped at one breakpoint, and another breakpoint occurs in an IRQ
handler, RealMonitor enters a panic state. No debugging can be performed after
RealMonitor enters this state.
SWI abort
undef
stop
SWI abort
undef
RUNNING STOPPED PANIC
go
Fig 143. RealMonitor as a State Machine
A debugger such as the ARM eXtended Debugger (AXD) or other RealMonitor aware
debugger, that runs on a host computer, can connect to the target to send commands and
receive data. This communication between host and target is illustrated in Figure 142.
The target component of RealMonitor, RMTarget, communicates with the host component,
RMHost, using the Debug Communications Channel (DCC), which is a reliable link whose
data is carried over the JTAG connection.
While user application is running, RMTarget typically uses IRQs generated by the DCC.
This means that if user application also wants to use IRQs, it must pass any
DCC-generated interrupts to RealMonitor.
To allow nonstop debugging, the EmbeddedICE-RT logic in the processor generates a

Prefetch Abort exception when a breakpoint is reached, or a Data Abort exception when a
watchpoint is hit. These exceptions are handled by the RealMonitor exception handlers
that inform the user, by way of the debugger, of the event. This allows user application to
continue running without stopping the processor. RealMonitor considers user application
to consist of two parts:
• A foreground application running continuously, typically in User, System, or SVC

mode
• A background application containing interrupt and exception handlers that are
triggered by certain events in user system, including:
– IRQs or FIQs
– Data and Prefetch aborts caused by user foreground application. This indicates an
error in the application being debugged. In both cases the host is notified and the
user application is stopped.

– Undef exception caused by the undefined instructions in user foreground

application. This indicates an error in the application being debugged. RealMonitor
stops the user application until a "Go" packet is received from the host.
When one of these exceptions occur that is not handled by user application, the following
happens:
• RealMonitor enters a loop, polling the DCC. If the DCC read buffer is full, control is
passed to rm_ReceiveData() (RealMonitor internal function). If the DCC write buffer is
free, control is passed to rm_TransmitData() (RealMonitor internal function). If there is
nothing else to do, the function returns to the caller. The ordering of the above
comparisons gives reads from the DCC a higher priority than writes to the
communications link.
• RealMonitor stops the foreground application. Both IRQs and FIQs continue to be
serviced if they were enabled by the application at the time the foreground application
was stopped.
33.4 How to Enable RealMonitor

The following steps must be performed to enable RealMonitor. A code example which
implements all the steps can be found at the end of this section.
33.4.1 Adding Stacks

User must ensure that stacks are set up within application for each of the processor
modes used by RealMonitor. For each mode, RealMonitor requires a fixed number of
words of stack space. User must therefore allow sufficient stack space for both
RealMonitor and application.
RealMonitor has the following stack requirements:
Table 592. RealMonitor stack requirement

Processor Mode RealMonitor Stack Usage (Bytes)
Undef 48
Prefetch Abort 16
Data Abort 16
IRQ 8
33.4.2 IRQ Mode

A stack for this mode is always required. RealMonitor uses two words on entry to its
interrupt handler. These are freed before nested interrupts are enabled.
33.4.3 Undef Mode

A stack for this mode is always required. RealMonitor uses 12 words while processing an
undefined instruction exception.
33.4.4 SVC Mode

RealMonitor makes no use of this stack.

33.4.5 Prefetch Abort Mode

RealMonitor uses four words on entry to its Prefetch abort interrupt handler.
33.4.6 Data Abort Mode

RealMonitor uses four words on entry to its data abort interrupt handler.
33.4.7 User/System Mode

33.4.8 FIQ Mode

33.4.9 Handling Exceptions

This section describes the importance of sharing exception handlers between
RealMonitor and user application.
33.4.9.1 RealMonitor Exception Handling

To function properly, RealMonitor must be able to intercept certain interrupts and
exceptions. Figure 144 illustrates how exceptions can be claimed by RealMonitor itself, or
shared between RealMonitor and application. If user application requires the exception
sharing, they must provide function (such as app_IRQDispatch ()). Depending on the
nature of the exception, this handler can either:
• Pass control to the RealMonitor processing routine, such as rm_irqhandler2().

• Claim the exception for the application itself, such as app_IRQHandler ().
In a simple case where an application has no exception handlers of its own, the
application can install the RealMonitor low-level exception handlers directly into the vector
table of the processor. Although the irq handler must get the address of the Vectored
Interrupt Controller. The easiest way to do this is to write a branch instruction (<address>)
into the vector table, where the target of the branch is the start address of the relevant
RealMonitor exception handler.

RealMonitor supplied exception vector handlers
RM_UNDEF_HANDLER()
RESET
RM_PREFETCHABORT_HANDLER()
RM_DATAABORT_HANDLER()
UNDEF RM_IRQHANDLER()
SWI
sharing IRQs between RealMonitor and user IRQ handler
PREFETCH
ABORT RM_IRQHANDLER2()
DATA ABORT
APP_IRQDISPATCH
RESERVED
APP_IRQHANDLER2()
OR
IRQ
FIQ
Fig 144. Exception Handlers
33.4.10 RMTarget Initialization

While the processor is in a privileged mode, and IRQs are disabled, user must include a
line of code within the start-up sequence of application to call rm_init_entry().
33.4.11 Code Example

The following example shows how to setup stack, VIC, initialize RealMonitor and share
non vectored interrupts:
IMPORT rm_init_entry
IMPORT rm_prefetchabort_handler
IMPORT rm_dataabort_handler
IMPORT rm_irqhandler2
IMPORT rm_undef_handler
IMPORT User_Entry ;Entry point of user application.
CODE32
ENTRY
;Define exception table. Instruct linker to place code at address 0x0000 0000
AREA exception_table, CODE
LDR pc, Reset_Address

LDR pc, Undefined_Address
LDR pc, SWI_Address
LDR pc, Prefetch_Address
LDR pc, Abort_Address

NOP ; Insert User code valid signature here.

LDR pc, [pc, #-0x120] ;Load IRQ vector from VIC
LDR PC, FIQ_Address
Reset_Address DCD __init ;Reset Entry point

Undefined_Address DCD rm_undef_handler ;Provided by RealMonitor
SWI_Address DCD 0 ;User can put address of SWI handler here
Prefetch_Address DCD rm_prefetchabort_handler ;Provided by RealMonitor
Abort_Address DCD rm_dataabort_handler ;Provided by RealMonitor
FIQ_Address DCD 0 ;User can put address of FIQ handler here
AREA init_code, CODE
ram_end EQU 0x4000xxxx ; Top of on-chip RAM.

__init
; /*********************************************************************
; * Set up the stack pointers for various processor modes. Stack grows
; * downwards.
; *********************************************************************/
LDR r2, =ram_end ;Get top of RAM
MRS r0, CPSR ;Save current processor mode
; Initialize the Undef mode stack for RealMonitor use

BIC r1, r0, #0x1f
ORR r1, r1, #0x1b
MSR CPSR_c, r1
;Keep top 32 bytes for flash programming routines.
;Refer to Flash Memory System and Programming chapter
SUB sp,r2,#0x1F
; Initialize the Abort mode stack for RealMonitor

BIC r1, r0, #0x1f
ORR r1, r1, #0x17
MSR CPSR_c, r1
;Keep 64 bytes for Undef mode stack
SUB sp,r2,#0x5F
; Initialize the IRQ mode stack for RealMonitor and User

BIC r1, r0, #0x1f
ORR r1, r1, #0x12
MSR CPSR_c, r1
;Keep 32 bytes for Abort mode stack
SUB sp,r2,#0x7F
; Return to the original mode.

MSR CPSR_c, r0
; Initialize the stack for user application

; Keep 256 bytes for IRQ mode stack
SUB sp,r2,#0x17F

; /*********************************************************************
; * Setup Vectored Interrupt controller. DCC Rx and Tx interrupts
; * generate Non Vectored IRQ request. rm_init_entry is aware
; * of the VIC and it enables the DBGCommRX and DBGCommTx interrupts.
; * Default vector address register is programmed with the address of
; * Non vectored app_irqDispatch mentioned in this example. User can setup
; * Vectored IRQs or FIQs here.
; *********************************************************************/
VICBaseAddr EQU 0xFFFFF000 ; VIC Base address

VICDefVectAddrOffset EQU 0x34
LDR r0, =VICBaseAddr

LDR r1, =app_irqDispatch
STR r1, [r0,#VICDefVectAddrOffset]
BL rm_init_entry ;Initialize RealMonitor

;enable FIQ and IRQ in ARM Processor
MRS r1, CPSR ; get the CPSR
BIC r1, r1, #0xC0 ; enable IRQs and FIQs
MSR CPSR_c, r1 ; update the CPSR
; /*********************************************************************
; * Get the address of the User entry point.
; *********************************************************************/
LDR lr, =User_Entry
MOV pc, lr
; /*********************************************************************
; * Non vectored irq handler (app_irqDispatch)
; *********************************************************************/
AREA app_irqDispatch, CODE

VICVectAddrOffset EQU 0x30
app_irqDispatch
;enable interrupt nesting

STMFD sp!, {r12,r14}
MRS r12, spsr ;Save SPSR in to r12
MSR cpsr_c,0x1F ;Re-enable IRQ, go to system mode
;User should insert code here if non vectored Interrupt sharing is

;required. Each non vectored shared irq handler must return to
;the interrupted instruction by using the following code.
; MSR cpsr_c, #0x52 ;Disable irq, move to IRQ mode
; MSR spsr, r12 ;Restore SPSR from r12
; STMFD sp!, {r0}
; LDR r0, =VICBaseAddr
; STR r1, [r0,#VICVectAddrOffset] ;Acknowledge Non Vectored irq has finished
; LDMFD sp!, {r12,r14,r0} ;Restore registers
; SUBS pc, r14, #4 ;Return to the interrupted instruction
;user interrupt did not happen so call rm_irqhandler2. This handler

;is not aware of the VIC interrupt priority hardware so trick

;rm_irqhandler2 to return here
STMFD sp!, {ip,pc}

LDR pc, rm_irqhandler2
;rm_irqhandler2 returns here
MSR cpsr_c, #0x52 ;Disable irq, move to IRQ mode
MSR spsr, r12 ;Restore SPSR from r12
STMFD sp!, {r0}
LDR r0, =VICBaseAddr
STR r1, [r0,#VICVectAddrOffset] ;Acknowledge Non Vectored irq has finished
LDMFD sp!, {r12,r14,r0} ;Restore registers
SUBS pc, r14, #4 ;Return to the interrupted instruction
END
33.5 RealMonitor Build Options

RealMonitor was built with the following options:
RM_OPT_DATALOGGING=FALSE
This option enables or disables support for any target-to-host packets sent on a non
RealMonitor (third-party) channel.
RM_OPT_STOPSTART=TRUE
This option enables or disables support for all stop and start debugging features.
RM_OPT_SOFTBREAKPOINT=TRUE
This option enables or disables support for software breakpoints.
RM_OPT_HARDBREAKPOINT=TRUE
Enabled for cores with EmbeddedICE-RT. This device uses ARM-7TDMI-S Rev 4 with
EmbeddedICE-RT.
RM_OPT_HARDWATCHPOINT=TRUE
Enabled for cores with EmbeddedICE-RT. This device uses ARM-7TDMI-S Rev 4 with
EmbeddedICE-RT.
RM_OPT_SEMIHOSTING=FALSE
This option enables or disables support for SWI semi-hosting. Semi-hosting provides
code running on an ARM target use of facilities on a host computer that is running an
ARM debugger. Examples of such facilities include the keyboard input, screen output,
and disk I/O.
RM_OPT_SAVE_FIQ_REGISTERS=TRUE
This option determines whether the FIQ-mode registers are saved into the registers
block when RealMonitor stops.

RM_OPT_READBYTES=TRUE
RM_OPT_WRITEBYTES=TRUE
RM_OPT_READHALFWORDS=TRUE
RM_OPT_WRITEHALFWORDS=TRUE
RM_OPT_READWORDS=TRUE
RM_OPT_WRITEWORDS=TRUE
Enables/Disables support for 8/16/32 bit read/write.
RM_OPT_EXECUTECODE=FALSE
Enables/Disables support for executing code from "execute code" buffer. The code
must be downloaded first.
RM_OPT_GETPC=TRUE
This option enables or disables support for the RealMonitor GetPC packet. Useful in
code profiling when real monitor is used in interrupt mode.
RM_EXECUTECODE_SIZE=NA
"execute code" buffer size. Also refer to RM_OPT_EXECUTECODE option.
RM_OPT_GATHER_STATISTICS=FALSE
This option enables or disables the code for gathering statistics about the internal
operation of RealMonitor.
RM_DEBUG=FALSE
This option enables or disables additional debugging and error-checking code in

RealMonitor.
RM_OPT_BUILDIDENTIFIER=FALSE
This option determines whether a build identifier is built into the capabilities table of
RMTarget. Capabilities table is stored in ROM.
RM_OPT_SDM_INFO=FALSE
SDM gives additional information about application board and processor to debug tools.
RM_OPT_MEMORYMAP=FALSE
This option determines whether a memory map of the board is built into the target and
made available through the capabilities table
RM_OPT_USE_INTERRUPTS=TRUE
This option specifies whether RMTarget is built for interrupt-driven mode or polled
mode.
RM_FIFOSIZE=NA

This option specifies the size, in words, of the data logging FIFO buffer.
CHAIN_VECTORS=FALSE
This option allows RMTarget to support vector chaining through µHAL (ARM HW
abstraction API).

UM10211
Chapter 34: Supplementary information
34.1 Abbreviations
Table 593. Acronym list
Acronym Description
ADC Analog-to-Digital Converter
AHB Advanced High-performance Bus
AMBA Advanced Microcontroller Bus Architecture
APB Advanced Peripheral Bus
BLS Byte Lane Select
BOD BrownOut Detection
CAN Controller Area Network
DAC Digital-to-Analog Converter
DCC Debug Communication Channel
DSP Digital Signal Processing
EOP End Of Packet
ETM Embedded Trace Macrocell
GPIO General Purpose Input/Output
IrDA Infrared Data Association
JTAG Joint Test Action Group
MII Media Independent Interface
PHY Physical Layer
PLL Phase-Locked Loop
PWM Pulse Width Modulator
RMII Reduced Media Independent Interface
SD/MMC Secure Digital/MultiMediaCard
SE0 Single Ended Zero
SPI Serial Peripheral Interface
SSI Synchronous Serial Interface
SSP Synchronous Serial Port
TTL Transistor-Transistor Logic
UART Universal Asynchronous Receiver/Transmitter

34.2 Legal information
34.2.1 Definitions malfunction of an NXP Semiconductors product can reasonably be expected

to result in personal injury, death or severe property or environmental
damage. NXP Semiconductors and its suppliers accept no liability for
Draft — The document is a draft version only. The content is still under
inclusion and/or use of NXP Semiconductors products in such equipment or
internal review and subject to formal approval, which may result in
applications and therefore such inclusion and/or use is at the customer’s own
modifications or additions. NXP Semiconductors does not give any
risk.
representations or warranties as to the accuracy or completeness of
information included herein and shall have no liability for the consequences of Applications — Applications that are described herein for any of these
use of such information. products are for illustrative purposes only. NXP Semiconductors makes no
representation or warranty that such applications will be suitable for the
specified use without further testing or modification.
34.2.2 Disclaimers Customers are responsible for the design and operation of their applications
and products using NXP Semiconductors products, and NXP Semiconductors
Limited warranty and liability — Information in this document is believed to accepts no liability for any assistance with applications or customer product
be accurate and reliable. However, NXP Semiconductors does not give any design. It is customer’s sole responsibility to determine whether the NXP
representations or warranties, expressed or implied, as to the accuracy or Semiconductors product is suitable and fit for the customer’s applications and
completeness of such information and shall have no liability for the products planned, as well as for the planned application and use of
consequences of use of such information. NXP Semiconductors takes no customer’s third party customer(s). Customers should provide appropriate
responsibility for the content in this document if provided by an information design and operating safeguards to minimize the risks associated with their
source outside of NXP Semiconductors. applications and products.
In no event shall NXP Semiconductors be liable for any indirect, incidental, NXP Semiconductors does not accept any liability related to any default,
punitive, special or consequential damages (including - without limitation - lost damage, costs or problem which is based on any weakness or default in the
profits, lost savings, business interruption, costs related to the removal or customer’s applications or products, or the application or use by customer’s
replacement of any products or rework charges) whether or not such third party customer(s). Customer is responsible for doing all necessary
damages are based on tort (including negligence), warranty, breach of testing for the customer’s applications and products using NXP
contract or any other legal theory. Semiconductors products in order to avoid a default of the applications and
Notwithstanding any damages that customer might incur for any reason the products or of the application or use by customer’s third party
whatsoever, NXP Semiconductors’ aggregate and cumulative liability towards customer(s). NXP does not accept any liability in this respect.
customer for the products described herein shall be limited in accordance Export control — This document as well as the item(s) described herein
with the Terms and conditions of commercial sale of NXP Semiconductors. may be subject to export control regulations. Export might require a prior
Right to make changes — NXP Semiconductors reserves the right to make authorization from competent authorities.
changes to information published in this document, including without
limitation specifications and product descriptions, at any time and without
notice. This document supersedes and replaces all information supplied prior 34.2.3 Trademarks
to the publication hereof.
Notice: All referenced brands, product names, service names and trademarks
Suitability for use — NXP Semiconductors products are not designed, are the property of their respective owners.
authorized or warranted to be suitable for use in life support, life-critical or I2C-bus — logo is a trademark of NXP B.V.
safety-critical systems or equipment, nor in applications where failure or

34.3 Tables
Table 1. LPC23xx overview . . . . . . . . . . . . . . . . . . . . . . .3 0xE01F C080) bit description. . . . . . . . . . . . . . 52
Table 2. LPC23xx features overview . . . . . . . . . . . . . . . .6 Table 38. PLL Configuration register (PLLCFG - address
Table 3. LPC23xx ordering information . . . . . . . . . . . . . .6 0xE01F C084) bit description. . . . . . . . . . . . . . 52
Table 4. LPC2361/62 Ordering options . . . . . . . . . . . . . .7 Table 39. Multiplier values for 32 kHz oscillator. . . . . . . . 53
Table 5. LPC2364/65/66/67/68 Ordering options . . . . . .7 Table 40. PLL Status register (PLLSTAT - address
Table 6. LPC2377/78 ordering options . . . . . . . . . . . . . .8 0xE01F C088) bit description. . . . . . . . . . . . . . 55
Table 7. LPC2387 ordering options . . . . . . . . . . . . . . . . .8 Table 41. PLL control bit combinations . . . . . . . . . . . . . . 55
Table 8. LPC2388 ordering options . . . . . . . . . . . . . . . . .8 Table 42. PLL Feed register (PLLFEED - address
Table 9. LPC2300 memory usage . . . . . . . . . . . . . . . . .16 0xE01F C08C) bit description . . . . . . . . . . . . . 56
Table 10. APB peripherals and base addresses . . . . . . .24 Table 43. PLL frequency parameter . . . . . . . . . . . . . . . . 56
Table 11. ARM exception vector locations . . . . . . . . . . . .25 Table 44. Additional Multiplier Values for use with a Low
Table 12. LPC2300 Memory mapping modes . . . . . . . . .25 Frequency Clock Input . . . . . . . . . . . . . . . . . . . 57
Table 13. Memory mapping control registers . . . . . . . . . .27 Table 45. Potential values for PLL example . . . . . . . . . . 59
Table 14. Memory Mapping control register (MEMMAP - Table 46. CPU Clock Configuration register (CCLKCFG -
address 0xE01F C040) bit description . . . . . . .27 address 0xE01F C104) bit description. . . . . . . 61
Table 15. Pin summary. . . . . . . . . . . . . . . . . . . . . . . . . . .30 Table 47. USB Clock Configuration register (USBCLKCFG -
Table 16. Summary of system control registers . . . . . . . .30 address 0xE01F C108) bit description. . . . . . . 61
Table 17. Reset Source Identification register (RSID - Table 48. IRC Trim register (IRCTRIM - address
address 0xE01F C180) bit description . . . . . . .33 0xE01F C1A4) bit description . . . . . . . . . . . . . 61
Table 18. External Interrupt registers . . . . . . . . . . . . . . . .35 Table 49. Peripheral Clock Selection register 0 (PCLKSEL0
Table 19. External Interrupt Flag register (EXTINT - address - address 0xE01F C1A8) bit description . . . . . 62
0xE01F C140) bit description . . . . . . . . . . . . . .36 Table 50. Peripheral Clock Selection register 1 (PCLKSEL1
Table 20. External Interrupt Mode register (EXTMODE - - address 0xE01F C1AC) bit description . . . . . 62
address 0xE01F C148) bit description . . . . . . .37 Table 51. Peripheral Clock Selection register bit values . 63
Table 21. External Interrupt Polarity register (EXTPOLAR - Table 52. Power Control registers . . . . . . . . . . . . . . . . . . 65
address 0xE01F C14C) bit description . . . . . . .37 Table 53. Power Mode Control register (PCON - address
Table 22. AHB configuration register map . . . . . . . . . . . .38 0xE01F C0C0) bit description . . . . . . . . . . . . . 65
Table 23. AHB Arbiter Configuration register 1 (AHBCFG1 - Table 54. Encoding of reduced power modes . . . . . . . . . 66
address 0xE01F C188) bit description . . . . . . .38 Table 55. Interrupt Wakeup register (INTWAKE - address
Table 24. Priority sequence (bit 0 = 0): CPU, GPDMA, 0xE01F C144) bit description. . . . . . . . . . . . . . 67
AHB1, USB. . . . . . . . . . . . . . . . . . . . . . . . . . . .39 Table 56. Power Control for Peripherals register (PCONP -
Table 25. Priority sequence (bit 0 = 0): USB, AHB1, CPU, address 0xE01F C0C4) bit description . . . . . . 68
GPDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Table 57. Memory bank selection . . . . . . . . . . . . . . . . . . 74
Table 26. Priority sequence (bit 0 = 0): GPDMA, AHB1, Table 58. Pad interface and control signal descriptions . 75
CPU, USB. . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Table 59. EMC register summary . . . . . . . . . . . . . . . . . . 75
Table 27. Priority sequence (bit 0 = 0): USB, AHB1, CPU, Table 60. EMC Control register (EMCControl - address
GPDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 0xFFE0 8000) bit description . . . . . . . . . . . . . . 76
Table 28. AHB Arbiter Configuration register 2 (AHBCFG2 - Table 61. EMC Status register (EMCStatus - address
address 0xE01F C18C) bit description . . . . . . .40 0xFFE0 8008) bit description . . . . . . . . . . . . . . 77
Table 29. Priority sequence (bit 0 = 0): Ethernet, CPU . .41 Table 62. EMC Configuration register (EMCConfig -
Table 30. Priority sequence (bit 0 = 0): Ethernet, CPU . .41 address 0xFFE0 8008) bit description . . . . . . . 78
Table 31. System Controls and Status register (SCS - Table 63. Static Memory Extended Wait register
address 0xE01F C1A0) bit description . . . . . . .42 (EMCStaticExtendedWait - address
Table 32. Summary of system control registers . . . . . . . .46 0xFFE0 8080) bit description . . . . . . . . . . . . . . 78
Table 33. Recommended values for CX1/X2 in oscillation Table 64. Static Memory Configuration registers
mode (crystal and external components (EMCStaticConfig0-1 - addresses 0xFFE0 8200,
parameters) low frequency mode (OSCRANGE = 0xFFE0 8220) bit description . . . . . . . . . . . . . . 79
0, see Table 31) . . . . . . . . . . . . . . . . . . . . . . . .48 Table 65. Static Memory Write Enable Delay registers
Table 34. Recommended values for CX1/X2 in oscillation (EMCStaticWaitWen0-1 - addresses
mode (crystal and external components 0xFFE0 8204,0xFFE0 8224) bit description . . 80
parameters) high frequency mode (OSCRANGE = Table 66. Static Memory Output Enable delay registers
1, see Table 31) . . . . . . . . . . . . . . . . . . . . . . . .48 (EMCStaticWaitOen0-1 - addresses
Table 35. Clock Source Select register (CLKSRCSEL - 0xFFE0 8208, 0xFFE0 8228) bit description . . 81
address 0xE01F C10C) bit description . . . . . . .49 Table 67. Static Memory Read Delay registers
Table 36. PLL registers . . . . . . . . . . . . . . . . . . . . . . . . . .51 (EMCStaticWaitRd0-1 - addresses 0xFFE0 820C,
Table 37. PLL Control register (PLLCON - address 0xFFE0 822C) bit description . . . . . . . . . . . . . 81

Table 68. Static Memory Page Mode Read Delay Table 96. LPC2364/68 pin allocation table . . . . . . . . . . 113
registers0-1 (EMCStaticWaitPage0-1 - addresses Table 97. LPC2364/65/66/67/68 pin description . . . . . . 115
0xFFE0 8210, 0xFFE0 8230) bit description . .82 Table 98. LPC2377/78 pin description . . . . . . . . . . . . . 124
Table 69. Static Memory Write Delay registers0-1 Table 99. LPC2387 pin description . . . . . . . . . . . . . . . . 134
(EMCStaticWaitWr - addresses 0xFFE0 8214, Table 100. LPC2388 pin description . . . . . . . . . . . . . . . 143
0xFFE0 8234) bit description . . . . . . . . . . . . . .82 Table 101. Part specific PINSEL registers . . . . . . . . . . . 154
Table 70. Static Memory Extended Wait register Table 102. Pin function select register bits . . . . . . . . . . . 155
(EMCStaticExtendedWait - address Table 103. Pin Mode Select register Bits . . . . . . . . . . . . 155
0xFFE0 8080) bit description . . . . . . . . . . . . . .83 Table 104. Pin Connect Block Register Map . . . . . . . . . 155
Table 71. Static Memory Turn Round Delay registers0-1 Table 105. Pin function select register 0 (PINSEL0 - address
(EMCStaticWaitTurn0-1- addresses 0xE002 C000) bit description
0xFFE0 8218, 0xFFE0 8238) bit description . .83 (LPC2364/65/66/67/68 and LPC2387). . . . . . 156
Table 72. VIC register map. . . . . . . . . . . . . . . . . . . . . . . .86 Table 106. Pin function select register 0 (PINSEL0 - address
Table 73. Software Interrupt register (VICSoftInt - address 0xE002 C000) bit description (LPC2377/78 and
0xFFFF F018) bit description . . . . . . . . . . . . . .88 LPC2388). . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Table 74. Software Interrupt Clear register (VICSoftIntClear Table 107. Pin function select register 1 (PINSEL1 - address
- address 0xFFFF F01C) bit description . . . . . .88 0xE002 C004) bit description
Table 75. Raw Interrupt Status register (VICRawIntr - (LPC2364/65/66/67/68 and LPC2387). . . . . . 158
address 0xFFFF F008) bit description . . . . . . .89 Table 108. Pin function select register 1 (PINSEL1 - address
Table 76. Interrupt Enable register (VICIntEnable - address 0xE002 C004) bit description (LPC2377/78 and
0xFFFF F010) bit description . . . . . . . . . . . . . .89 LPC2388). . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Table 77. Interrupt Enable Clear register (VICIntEnClear - Table 109. Pin function select register 2 (PINSEL2 - address
address 0xFFFF F014) bit description . . . . . . .89 0xE002 C008) bit description
Table 78. Interrupt Select register (VICIntSelect - address (LPC2364/65/66/67/68, LPC2377/78, LPC2387,
0xFFFF F00C) bit description . . . . . . . . . . . . . .90 LPC2388). . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Table 79. IRQ Status register (VICIRQStatus - address Table 110. Pin function select register 3 (PINSEL3 - address
0xFFFF F000) bit description . . . . . . . . . . . . . .90 0xE002 C00C) bit description
Table 80. FIQ Status register (VICFIQStatus - address (LPC2361/62/64/65/66/67/68 and LPC2387). 160
0xFFFF F004) bit description . . . . . . . . . . . . . .90 Table 111. Pin function select register 3 (PINSEL3 - address
Table 81. Vector Address registers 0-31 (VICVectAddr0-31 - 0xE002 C00C) bit description (LPC2377/78 and
addresses 0xFFFF F100 to 0xFFFF F17C) bit LPC2388). . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
description . . . . . . . . . . . . . . . . . . . . . . . . . . . .90 Table 112. Pin function select register 4 (PINSEL4 - address
Table 82. Vector Priority registers 0-31 (VICVectPriority0-31 0xE002 C010) bit description
- addresses 0xFFFF F200 to 0xFFFF F27C) bit (LPC2364/65/66/67/68 and LPC2387). . . . . . 161
description . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 Table 113. Pin function select register 4 (PINSEL4 - address
Table 83. Vector Address register (VICAddress - address 0xE002 C010) bit description (LPC2377/78 and
0xFFFF FF00) bit description . . . . . . . . . . . . . .91 LPC2388). . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Table 84. Software Priority Mask register Table 114. Pin function select register 6 (PINSEL6 - address
(VICSWPriorityMask - address 0xFFFF F024) bit 0xE002 C018) bit description (LPC2377/78 and
description . . . . . . . . . . . . . . . . . . . . . . . . . . . .91 LPC2388). . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Table 85. Protection Enable register (VICProtection - Table 115. Pin function select register 7 (PINSEL7 - address
address 0xFFFF F020) bit description . . . . . . .92 0xE002 C01C) bit description
Table 86. Connection of interrupt sources to the Vectored (LPC2364/65/66/67/68 and LPC2387). . . . . . 163
Interrupt Controller . . . . . . . . . . . . . . . . . . . . . .92 Table 116. Pin function select register 7 (PINSEL7 - address
Table 87. Interrupt sources bit allocation table . . . . . . . . .94 0xE002 C01C) bit description (LPC2377/78 and
Table 88. MAM responses to program accesses of various LPC2388). . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98 Table 117. Pin function select register 8 (PINSEL8 - address
Table 89. MAM responses to data and DMA accesses of 0xE002 C020) bit description (LPC2377/78 and
various types . . . . . . . . . . . . . . . . . . . . . . . . . .99 LPC2388). . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Table 90. Summary of Memory Acceleration Module Table 118. Pin function select register 9 (PINSEL9 - address
registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 0xE002 C024) bit description
Table 91. MAM Control Register (MAMCR - address (LPC2364/66/65/67/68 and LPC2387). . . . . . 165
0xE01F C000) bit description . . . . . . . . . . . . .100 Table 119. Pin function select register 9 (PINSEL9 - address
Table 92. MAM Timing register (MAMTIM - address 0xE002 C024) bit description (LPC2377/78 and
0xE01F C004) bit description . . . . . . . . . . . . .101 LPC2388). . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Table 93. Suggestions for MAM timing selection . . . . . .103 Table 120. Pin function select register 10 (PINSEL10 -
Table 94. LPC23xx pinning overview . . . . . . . . . . . . . . .104 address 0xE002 C028) bit description . . . . . . 166
Table 95. LPC2361/62 pin description . . . . . . . . . . . . .104 Table 121. Pin Mode select register 0 (PINMODE0 - address

0xE002 C040) bit description . . . . . . . . . . . . .167 (FIO[0/1/2/3/4]MASK - address

Table 122. Pin Mode select register 1 (PINMODE1 - address 0x3FFF C0[1/3/5/7/9]0) bit description. . . . . . 181
0xE002 C044) bit description . . . . . . . . . . . . .167 Table 148. Fast GPIO port Mask byte and half-word
Table 123. Pin Mode select register 2 (PINMODE2 - address accessible register description. . . . . . . . . . . . 181
0xE002 C048) bit description . . . . . . . . . . . . .167 Table 149. GPIO overall Interrupt Status register (IOIntStatus
Table 124. Pin Mode select register 3 (PINMODE3 - address - address 0xE002 8080) bit description . . . . . 182
0xE002 C04C) bit description . . . . . . . . . . . . .168 Table 150. GPIO Interrupt Enable for Rising edge register
Table 125. Pin Mode select register 4 (PINMODE4 - address (IO0IntEnR - address 0xE002 8090 and
0xE002 C050) bit description . . . . . . . . . . . . .168 IO2IntEnR - address 0xE002 80B0) bit description
Table 126. Pin Mode select register 5 (PINMODE5 - address 182
0xE002 C054) bit description . . . . . . . . . . . . .168 Table 151. GPIO Interrupt Enable for Falling edge register
Table 127. Pin Mode select register 6 (PINMODE6 - address (IO0IntEnF - address 0xE002 8094 and
0xE002 C058) bit description . . . . . . . . . . . . .168 IO2IntEnF - address 0xE002 80B4) bit description
Table 128. Pin Mode select register 7 (PINMODE7 - address 182
0xE002 C05C) bit description . . . . . . . . . . . . .169 Table 152. GPIO Status for Rising edge register (IO0IntStatR
Table 129. Pin Mode select register 8 (PINMODE8 - address - address 0xE002 8084 and IO2IntStatR - address
0xE002 C060) bit description . . . . . . . . . . . . .169 0xE002 80A4) bit description . . . . . . . . . . . . . 183
Table 130. Pin Mode select register 9 (PINMODE9 - address Table 153. GPIO Status for Falling edge register (IO0IntStatF
0xE002 C064) bit description . . . . . . . . . . . . .169 - address 0xE002 8088 and IO2IntStatF - address
Table 131. GPIO pin description . . . . . . . . . . . . . . . . . . .171 0xE002 80A8) bit description . . . . . . . . . . . . . 183
Table 132. GPIO register map (legacy APB accessible Table 154. GPIO Status for Falling edge register (IO0IntClr -
registers). . . . . . . . . . . . . . . . . . . . . . . . . . . . .172 address 0xE002 808C and IO2IntClr - address
Table 133. GPIO register map (local bus accessible registers 0xE002 80AC) bit description . . . . . . . . . . . . 183
- enhanced GPIO features) . . . . . . . . . . . . . .172 Table 155. Ethernet acronyms, abbreviations, and
Table 134. GPIO interrupt register map. . . . . . . . . . . . . .173 definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Table 135. GPIO port Direction register (IO0DIR - address Table 156. Example PHY Devices . . . . . . . . . . . . . . . . . 192
0xE002 8008 and IO1DIR - address Table 157. Ethernet RMII pin descriptions . . . . . . . . . . . 193
0xE002 8018) bit description . . . . . . . . . . . . .174 Table 158. Ethernet MIIM pin descriptions . . . . . . . . . . . 193
Table 136. Fast GPIO port Direction register Table 159. Register definitions . . . . . . . . . . . . . . . . . . . . 194
(FIO[0/1/2/3/4]DIR - address Table 160. MAC Configuration register 1 (MAC1 - address
0x3FFF C0[0/2/4/6/8]0) bit description . . . . . .174 0xFFE0 0000) bit description . . . . . . . . . . . . . 196
Table 137. Fast GPIO port Direction control byte and Table 161. MAC Configuration register 2 (MAC2 - address
half-word accessible register description . . . .174 0xFFE0 0004) bit description . . . . . . . . . . . . . 197
Table 138. GPIO port output Set register (IO0SET - address Table 162. Pad operation. . . . . . . . . . . . . . . . . . . . . . . . 198
0xE002 8004 and IO1SET - address Table 163. Back-to-back Inter-packet-gap register (IPGT -
0xE002 8014) bit description . . . . . . . . . . . . .175 address 0xFFE0 0008) bit description . . . . . . 198
Table 139. Fast GPIO port output Set register Table 164. Non Back-to-back Inter-packet-gap register
(FIO[0/1/2/3/4]SET - address (IPGR - address 0xFFE0 000C) bit
0x3FFF C0[1/3/5/7/9]8) bit description . . . . . .176 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Table 140. Fast GPIO port output Set byte and half-word Table 165. Collision Window / Retry register (CLRT - address
accessible register description . . . . . . . . . . . .176 0xFFE0 0010) bit description . . . . . . . . . . . . . 199
Table 141. GPIO port output Clear register (IO0CLR - Table 166. Maximum Frame register (MAXF - address
address 0xE002 800C and IO1CLR - address 0xFFE0 0014) bit description . . . . . . . . . . . . . 199
0xE002 801C) bit description . . . . . . . . . . . . .177 Table 167. PHY Support register (SUPP - address
Table 142. Fast GPIO port output Clear register 0xFFE0 0018) bit description . . . . . . . . . . . . . 200
(FIO[0/1/2/3/4]CLR - address Table 168. Test register (TEST - address 0xFFE0 ) bit
0x3FFF C0[1/3/5/7/9]C) bit description. . . . . .177 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Table 143. Fast GPIO port output Clear byte and half-word Table 169. MII Mgmt Configuration register (MCFG - address
accessible register description . . . . . . . . . . . .178 0xFFE0 0020) bit description . . . . . . . . . . . . . 200
Table 144. GPIO port Pin value register (IO0PIN - address Table 170. Clock select encoding . . . . . . . . . . . . . . . . . 201
0xE002 8000 and IO1PIN - address Table 171. MII Mgmt Command register (MCMD - address
0xE002 8010) bit description . . . . . . . . . . . . .179 0xFFE0 0024) bit description . . . . . . . . . . . . . 201
Table 145. Fast GPIO port Pin value register Table 172. MII Mgmt Address register (MADR - address
(FIO[0/1/2/3/4]PIN - address 0xFFE0 0028) bit description . . . . . . . . . . . . . 201
0x3FFF C0[1/3/5/7/9]4) bit description . . . . . .179 Table 173. MII Mgmt Write Data register (MWTD - address
Table 146. Fast GPIO port Pin value byte and half-word 0xFFE0 002C) bit description . . . . . . . . . . . . 202
accessible register description . . . . . . . . . . . .180 Table 174. MII Mgmt Read Data register (MRDD - address
Table 147. Fast GPIO port Mask register 0xFFE0 0030) bit description . . . . . . . . . . . . . 202

Table 175. MII Mgmt Indicators register (MIND - address description . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
0xFFE0 0034) bit description . . . . . . . . . . . . .202 Table 199. Hash Filter Table LSBs register (HashFilterL -
Table 176. Station Address register (SA0 - address address 0xFFE0 0210) bit description . . . . . . 214
0xFFE0 0040) bit description . . . . . . . . . . . . .203 Table 200. Hash Filter MSBs register (HashFilterH - address
Table 177. Station Address register (SA1 - address 0xFFE0 0214) bit description . . . . . . . . . . . . . 214
0xFFE0 0044) bit description . . . . . . . . . . . . .203 Table 201. Interrupt Status register (IntStatus - address
Table 178. Station Address register (SA2 - address 0xFFE0 0FE0) bit description . . . . . . . . . . . . 215
0xFFE0 0048) bit description . . . . . . . . . . . . .204 Table 202. Interrupt Enable register (intEnable - address
Table 179. Command register (Command - address 0xFFE0 0FE4) bit description . . . . . . . . . . . . 216
0xFFE0 0100) bit description . . . . . . . . . . . . .204 Table 203. Interrupt Clear register (IntClear - address
Table 180. Status register (Status - address 0xFFE0 0104) 0xFFE0 0FE8) bit description . . . . . . . . . . . . 216
bit description . . . . . . . . . . . . . . . . . . . . . . . . .205 Table 204. Interrupt Set register (IntSet - address
Table 181. Receive Descriptor Base Address register 0xFFE0 0FEC) bit description . . . . . . . . . . . . 217
(RxDescriptor - address 0xFFE0 0108) bit Table 205. Power Down register (PowerDown - address
description . . . . . . . . . . . . . . . . . . . . . . . . . . .205 0xFFE0 0FF4) bit description. . . . . . . . . . . . . 217
Table 182. receive Status Base Address register (RxStatus - Table 206. Receive Descriptor Fields . . . . . . . . . . . . . . . 219
address 0xFFE0 010C) bit description . . . . . .205 Table 207. Receive Descriptor Control Word . . . . . . . . . 219
Table 183. Receive Number of Descriptors register Table 208. Receive Status Fields . . . . . . . . . . . . . . . . . . 219
(RxDescriptor - address 0xFFE0 0110) bit Table 209. Receive Status HashCRC Word . . . . . . . . . . 220
description . . . . . . . . . . . . . . . . . . . . . . . . . . .206 Table 210. Receive status information word . . . . . . . . . . 220
Table 184. Receive Produce Index register Table 211. Transmit descriptor fields . . . . . . . . . . . . . . . 222
(RxProduceIndex - address 0xFFE0 0114) bit Table 212. Transmit descriptor control word . . . . . . . . . . 222
description . . . . . . . . . . . . . . . . . . . . . . . . . . .206 Table 213. Transmit status fields . . . . . . . . . . . . . . . . . . 222
Table 185. Receive Consume Index register Table 214. Transmit status information word . . . . . . . . . 223
(RXConsumeIndex - address 0xFFE0 0118) bit Table 215. CAN Pin descriptions . . . . . . . . . . . . . . . . . . 261
description . . . . . . . . . . . . . . . . . . . . . . . . . . .207 Table 216. Memory Map of the CAN Block. . . . . . . . . . . 265
Table 186. Transmit Descriptor Base Address register Table 217. CAN acceptance filter and central CAN
(TxDescriptor - address 0xFFE0 011C) bit registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
description . . . . . . . . . . . . . . . . . . . . . . . . . . .207 Table 218. CAN1 and CAN2 controller register map . . . 266
Table 187. Transmit Status Base Address register (TxStatus Table 219. CAN1 and CAN2 controller register map . . . 267
- address 0xFFE0 0120) bit description . . . . .207 Table 220. CAN Wake and Sleep registers. . . . . . . . . . . 267
Table 188. Transmit Number of Descriptors register Table 221. Mode register (CAN1MOD - address
(TxDescriptorNumber - address 0xFFE0 0124) bit 0xE004 4000, CAN2MOD - address
description . . . . . . . . . . . . . . . . . . . . . . . . . . .208 0xE004 8000) bit description . . . . . . . . . . . . . 268
Table 189. Transmit Produce Index register Table 222. Command Register (CAN1CMR - address
(TxProduceIndex - address 0xFFE0 0128) bit 0xE004 4004, CAN2CMR - address
Table 190. Transmit Consume Index register Table 223. Global Status Register (CAN1GSR - address
(TxConsumeIndex - address 0xFFE0 012C) bit 0xE004 4008, CAN2GSR - address
Table 191. Transmit Status Vector 0 register (TSV0 - Table 224. Interrupt and Capture Register (CAN1ICR -
address 0xFFE0 0158) bit description . . . . . .209 address 0xE004 400C, CAN2ICR - address
Table 192. Transmit Status Vector 1 register (TSV1 - address 0xE004 800C) bit description. . . . . . . . . . . . . 273
0xFFE0 015C) bit description . . . . . . . . . . . . .210 Table 225. Interrupt Enable Register (CAN1IER - address
Table 193. Receive Status Vector register (RSV - address 0xE004 4010, CAN2IER - address 0xE004 8010)
0xFFE0 0160) bit description . . . . . . . . . . . . . 211 bit description. . . . . . . . . . . . . . . . . . . . . . . . . 277
Table 194. Flow Control Counter register Table 226. Bus Timing Register (CAN1BTR - address
(FlowControlCounter - address 0xFFE0 0170) bit 0xE004 4014, CAN2BTR - address 0xE004 8014)
description . . . . . . . . . . . . . . . . . . . . . . . . . . .212 bit description. . . . . . . . . . . . . . . . . . . . . . . . . 278
Table 195. Flow Control Status register (FlowControlStatus - Table 227. Error Warning Limit register (CAN1EWL -
address 0xFFE0 8174) bit description . . . . . .212 address 0xE004 4018, CAN2EWL - address
Table 196. Receive Filter Control register (RxFilterCtrl - 0xE004 8018) bit description . . . . . . . . . . . . . 279
address 0xFFE0 0200) bit description . . . . . .212 Table 228. Status Register (CAN1SR - address
Table 197. Receive Filter WoL Status register 0xE004 401C, CAN2SR - address 0xE004 801C)
(RxFilterWoLStatus - address 0xFFE0 0204) bit bit description. . . . . . . . . . . . . . . . . . . . . . . . . 279
description . . . . . . . . . . . . . . . . . . . . . . . . . . .213 Table 229. Receive Frame Status register (CAN1RFS -
Table 198. Receive Filter WoL Clear register address 0xE004 4020, CAN2RFS - address
(RxFilterWoLClear - address 0xFFE0 0208) bit 0xE004 8020) bit description . . . . . . . . . . . . . 281

Table 230. Receive Identifier Register (CAN1RID - address Table 255. FullCAN Interrupt and Capture register 0
0xE004 4024, CAN2RID - address 0xE004 8024) (FCANIC0 - address 0xE003 C024) bit
bit description . . . . . . . . . . . . . . . . . . . . . . . . .282 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Table 231. RX Identifier register when FF = 1 . . . . . . . . .282 Table 256. FullCAN Interrupt and Capture register 1
Table 232. Receive Data register A (CAN1RDA - address (FCANIC1 - address 0xE003 C028) bit
0xE004 4028, CAN2RDA - address description . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
0xE004 8028) bit description . . . . . . . . . . . . .282 Table 257. Format of automatically stored Rx messages 301
Table 233. Receive Data register B (CAN1RDB - address Table 258. FullCAN semaphore operation . . . . . . . . . . . 301
0xE004 402C, CAN2RDB - address Table 259. Example of Acceptance Filter Tables and ID index
0xE004 802C) bit description . . . . . . . . . . . . .283 Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Table 234. Transmit Frame Information Register Table 260. Used ID-Look-up Table sections . . . . . . . . . . 313
(CAN1TFI[1/2/3] - address 0xE004 40[30/40/50], Table 261. Used ID-Look-up Table sections . . . . . . . . . . 314
CAN2TFI[1/2/3] - 0xE004 80[30/40/50]) bit Table 262. USB related acronyms, abbreviations, and
description . . . . . . . . . . . . . . . . . . . . . . . . . . .284 definitions used in this chapter. . . . . . . . . . . . 319
Table 235. Transfer Identifier Register (CAN1TID[1/2/3] - Table 263. Fixed endpoint configuration . . . . . . . . . . . . . 320
address 0xE004 40[34/44/54], CAN2TID[1/2/3] - Table 264. USB external interface . . . . . . . . . . . . . . . . . 323
address 0xE004 80[34/44/54]) bit description 285 Table 265. USB device controller clock sources. . . . . . . 324
Table 236. Transfer Identifier register when FF = 1. . . . .285 Table 266. USB device register map . . . . . . . . . . . . . . . 325
Table 237. Transmit Data Register A (CAN1TDA[1/2/3] - Table 267. USB Port Select register (USBPortSel - address
address 0xE004 40[38/48/58], CAN2TDA[1/2/3] - 0xFFE0 C110) bit description. . . . . . . . . . . . . 327
address 0xE004 80[38/48/58]) bit description 285 Table 268. USBClkCtrl register (USBClkCtrl - address
Table 238. Transmit Data Register B (CAN1TDB[1/2/3] - 0xFFE0 CFF4) bit description . . . . . . . . . . . . 327
address 0xE004 40[3C/4C/5C], CAN2TDB[1/2/3] Table 269. USB Clock Status register (USBClkSt - 0xFFE0
- address 0xE004 80[3C/4C/5C]) bit CFF8) bit description . . . . . . . . . . . . . . . . . . . 328
description . . . . . . . . . . . . . . . . . . . . . . . . . . .286 Table 270. USB Interrupt Status register (USBIntSt - address
Table 239. CAN Sleep Clear register (CANSLEEPCLR - 0xE01F C1C0) bit description . . . . . . . . . . . . 328
address 0x400F C110) bit description . . . . . .286 Table 271. USB Device Interrupt Status register
Table 240. CAN Wake-up Flags register (CANWAKEFLAGS (USBDevIntSt - address 0xFFE0 C200) bit
- address 0x400F C114) bit description . . . . .287 allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Table 241. Central Transit Status Register (CANTxSR - Table 272. USB Device Interrupt Status register
address 0xE004 0000) bit description . . . . . .288 (USBDevIntSt - address 0xFFE0 C200) bit
Table 242. Central Receive Status Register (CANRxSR - description . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
address 0xE004 0004) bit description . . . . . .289 Table 273. USB Device Interrupt Enable register
Table 243. Central Miscellaneous Status Register (CANMSR (USBDevIntEn - address 0xFFE0 C204) bit
- address 0xE004 0008) bit description . . . . .289 allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Table 244. Acceptance filter modes and access control .290 Table 274. USB Device Interrupt Enable register
Table 245. Section configuration register settings . . . . . .291 (USBDevIntEn - address 0xFFE0 C204) bit
Table 246. Acceptance Filter Mode Register (AFMR - description . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
address 0xE003 C000) bit description . . . . . .293 Table 275. USB Device Interrupt Clear register
Table 247. Standard Frame Individual Start Address Register (USBDevIntClr - address 0xFFE0 C208) bit
(SFF_sa - address 0xE003 C004) bit allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
description . . . . . . . . . . . . . . . . . . . . . . . . . . .294 Table 276. USB Device Interrupt Clear register
Table 248. Standard Frame Group Start Address Register (USBDevIntClr - address 0xFFE0 C208) bit
(SFF_GRP_sa - address 0xE003 C008) bit description . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
description . . . . . . . . . . . . . . . . . . . . . . . . . . .295 Table 277. USB Device Interrupt Set register (USBDevIntSet
Table 249. Extended Frame Start Address Register (EFF_sa - address 0xFFE0 C20C) bit allocation . . . . 331
- address 0xE003 C00C) bit description . . . . .295 Table 278. USB Device Interrupt Set register (USBDevIntSet
Table 250. Extended Frame Group Start Address Register - address 0xFFE0 C20C) bit description. . . . 331
(EFF_GRP_sa - address 0xE003 C010) bit Table 279. USB Device Interrupt Priority register
description . . . . . . . . . . . . . . . . . . . . . . . . . . .296 (USBDevIntPri - address 0xFFE0 C22C) bit
Table 251. End of AF Tables Register (ENDofTable - address description . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
0xE003 C014) bit description . . . . . . . . . . . . .296 Table 280. USB Endpoint Interrupt Status register
Table 252. LUT Error Address Register (LUTerrAd - address (USBEpIntSt - address 0xFFE0 C230) bit
0xE003 C018) bit description . . . . . . . . . . . . .297 allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Table 253. LUT Error Register (LUTerr - address Table 281. USB Endpoint Interrupt Status register
0xE003 C01C) bit description . . . . . . . . . . . . .297 (USBEpIntSt - address 0xFFE0 C230) bit
Table 254. Global FullCAN Enable register (FCANIE - description . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
address 0xE003 C020) bit description . . . . . .297 Table 282. USB Endpoint Interrupt Enable register

(USBEpIntEn - address 0xFFE0 C234) bit address 0xFFE0 C284) bit description . . . . . 344
allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . .334 Table 307. USB EP DMA Enable register (USBEpDMAEn -
Table 283. USB Endpoint Interrupt Enable register address 0xFFE0 C288) bit description . . . . . 344
(USBEpIntEn - address 0xFFE0 C234) bit Table 308. USB EP DMA Disable register (USBEpDMADis -
description . . . . . . . . . . . . . . . . . . . . . . . . . . .334 address 0xFFE0 C28C) bit description . . . . . 345
Table 284. USB Endpoint Interrupt Clear register Table 309. USB DMA Interrupt Status register
(USBEpIntClr - address 0xFFE0 C238) bit (USBDMAIntSt - address 0xFFE0 C290) bit
allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . .334 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Table 285. USB Endpoint Interrupt Clear register Table 310. USB DMA Interrupt Enable register
(USBEpIntClr - address 0xFFE0 C238) bit (USBDMAIntEn - address 0xFFE0 C294) bit
description . . . . . . . . . . . . . . . . . . . . . . . . . . .335 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Table 286. USB Endpoint Interrupt Set register Table 311. USB End of Transfer Interrupt Status register
(USBEpIntSet - address 0xFFE0 C23C) bit (USBEoTIntSt - address 0xFFE0 C2A0s) bit
Table 287. USB Endpoint Interrupt Set register Table 312. USB End of Transfer Interrupt Clear register
(USBEpIntSet - address 0xFFE0 C23C) bit (USBEoTIntClr - address 0xFFE0 C2A4) bit
Table 288. USB Endpoint Interrupt Priority register Table 313. USB End of Transfer Interrupt Set register
(USBEpIntPri - address 0xFFE0 C240) bit (USBEoTIntSet - address 0xFFE0 C2A8) bit
Table 289. USB Endpoint Interrupt Priority register Table 314. USB New DD Request Interrupt Status register
(USBEpIntPri - address 0xFFE0 C240) bit (USBNDDRIntSt - address 0xFFE0 C2AC) bit
Table 290. USB Realize Endpoint register (USBReEp - Table 315. USB New DD Request Interrupt Clear register
address 0xFFE0 C244) bit allocation . . . . . .337 (USBNDDRIntClr - address 0xFFE0 C2B0) bit
Table 291. USB Realize Endpoint register (USBReEp - description . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
address 0xFFE0 C244) bit description . . . . .337 Table 316. USB New DD Request Interrupt Set register
Table 292. USB Endpoint Index register (USBEpIn - address (USBNDDRIntSet - address 0xFFE0 C2B4) bit
0xFFE0 C248) bit description . . . . . . . . . . . .338 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Table 293. USB MaxPacketSize register (USBMaxPSize - Table 317. USB System Error Interrupt Status register
address 0xFFE0 C24C) bit description . . . . .338 (USBSysErrIntSt - address 0xFFE0 C2B8) bit
Table 294. USB Receive Data register (USBRxData - description . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
address 0xFFE0 C218) bit description . . . . .339 Table 318. USB System Error Interrupt Clear register
Table 295. USB Receive Packet Length register (USBSysErrIntClr - address 0xFFE0 C2BC) bit
(USBRxPlen - address 0xFFE0 C220) bit description . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
description . . . . . . . . . . . . . . . . . . . . . . . . . . .339 Table 319. USB System Error Interrupt Set register
Table 296. USB Transmit Data register (USBTxData - (USBSysErrIntSet - address 0xFFE0 C2C0) bit
address 0xFFE0 C21C) bit description . . . . .340 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Table 297. USB Transmit Packet Length register Table 320. SIE command code table . . . . . . . . . . . . . . . 353
(USBTxPLen - address 0xFFE0 C224) bit Table 321. Device Set Address Register bit description . 353
description . . . . . . . . . . . . . . . . . . . . . . . . . . .340 Table 322. Configure Device Register bit description . . . 354
Table 298. USB Control register (USBCtrl - address 0xFFE0 Table 323. Set Mode Register bit description . . . . . . . . . 354
C228) bit description . . . . . . . . . . . . . . . . . . .340 Table 324. Set Device Status Register bit description . . 355
Table 299. USB Command Code register (USBCmdCode - Table 325. Get Error Code Register bit description . . . . 357
address 0xFFE0 C210) bit description . . . . .341 Table 326. Read Error Status Register bit description . . 357
Table 300. USB Command Data register (USBCmdData - Table 327. Select Endpoint Register bit description . . . . 358
address 0xFFE0 C214) bit description . . . . .342 Table 328. Set Endpoint Status Register bit description . 359
Table 301. USB DMA Request Status register (USBDMARSt Table 329. Clear Buffer Register bit description . . . . . . . 360
- address 0xFFE0 C250) bit allocation . . . . .342 Table 330. DMA descriptor . . . . . . . . . . . . . . . . . . . . . . . 365
Table 302. USB DMA Request Status register (USBDMARSt Table 331. USB (OHCI) related acronyms and abbreviations
- address 0xFFE0 C250) bit description . . . .342 used in this chapter . . . . . . . . . . . . . . . . . . . . 378
Table 303. USB DMA Request Clear register (USBDMARClr Table 332. USB OTG port pins . . . . . . . . . . . . . . . . . . . . 380
- address 0xFFE0 C254) bit description . . . .343 Table 333. USB Host register address definitions . . . . . 381
Table 304. USB DMA Request Set register (USBDMARSet - Table 334. USB OTG port 1 pins . . . . . . . . . . . . . . . . . . 385
address 0xFFE0 C258) bit description . . . . .343 Table 335. USB OTG and I2C register address
Table 305. USB UDCA Head register (USBUDCAH - definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
address 0xFFE0 C280) bit description . . . . .344 Table 336. USB Interrupt Status register - (USBIntSt -
Table 306. USB EP DMA Status register (USBEpDMASt - address 0xE01F C1) bit description. . . . . . . . 390

Table 337. OTG Interrupt Status register (OTGIntSt - 0xE007 C014, Read Only) bit description . . . 422
address 0xE01F C100) bit description . . . . . .391 Table 361. UARTn Scratch Pad Register (U0SCR - address
Table 338. OTG Status Control register (OTGStCtrl - address 0xE000 C01C, U2SCR - 0xE007 801C, U3SCR -
0xFFE0 C110) bit description . . . . . . . . . . . . .392 0xE007 C01C) bit description . . . . . . . . . . . . 424
Table 339. Port function truth table . . . . . . . . . . . . . . . . .393 Table 362. UARTn Auto-baud Control Register (U0ACR -
Table 340. OTG Timer register (OTGTmr - address 0xE000 C020, U2ACR - 0xE007 8020, U3ACR -
0xFFE0 C114) bit description . . . . . . . . . . . . .393 0xE007 C020) bit description. . . . . . . . . . . . . 424
Table 341. OTG_clock_control register (OTG_clock_control Table 363. IrDA Control Register for UART3 only (U3ICR -
- address 0xFFE0 CFF4) bit description. . . . .393 address 0xE007 C024) bit description . . . . . . 427
Table 342. OTG_clock_status register (OTGClkSt - address Table 364. IrDA Pulse Width . . . . . . . . . . . . . . . . . . . . . . 427
0xFFE0 CFF8) bit description. . . . . . . . . . . . .394 Table 365. UARTn Fractional Divider Register (U0FDR -
Table 343. I2C Receive register (I2C_RX - address address 0xE000 C028, U2FDR - 0xE007 8028,
0xFFE0 C300) bit description . . . . . . . . . . . . .395 U3FDR - 0xE007 C028) bit description . . . . . 428
Table 344. I2C Transmit register (I2C_TX - address Table 366. Fractional Divider setting look-up table . . . . . 430
0xFFE0 C300) bit description . . . . . . . . . . . . .395 Table 367. UARTn Transmit Enable Register (U0TER -
Table 345. I2C status register (I2C_STS - address address 0xE000 C030, U2TER - 0xE007 8030,
0xFFE0 C304) bit description . . . . . . . . . . . . .396 U3TER - 0xE007 C030) bit description . . . . . 431
Table 346. I2C Control register (I2C_CTL - address Table 368. UART1 Pin Description . . . . . . . . . . . . . . . . . 434
0xFFE0 C308) bit description . . . . . . . . . . . . .397 Table 369. UART1 register map . . . . . . . . . . . . . . . . . . . 436
Table 347. I2C_CLKHI register (I2C_CLKHI - address Table 370. UART1 Receiver Buffer Register (U1RBR -
0xFFE0 C30C) bit description. . . . . . . . . . . . .398 address 0xE001 0000 when DLAB = 0, Read
Table 348. I2C_CLKLO register (I2C_CLKLO - address Only) bit description . . . . . . . . . . . . . . . . . . . 438
0xFFE0 C310) bit description . . . . . . . . . . . . .399 Table 371. UART1 Transmitter Holding Register (U1THR -
Table 349. UART0 Pin description. . . . . . . . . . . . . . . . . .413 address 0xE001 0000 when DLAB = 0, Write
Table 350. UART Register Map. . . . . . . . . . . . . . . . . . . .414 Only) bit description . . . . . . . . . . . . . . . . . . . . 438
Table 351. UARTn Receiver Buffer Register (U0RBR - Table 372. UART1 Divisor Latch LSB Register (U1DLL -
address 0xE000 C000, U2RBR - 0xE007 8000, address 0xE001 0000 when DLAB = 1) bit
U3RBR - 0E007 C000 when DLAB = 0, Read description . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Only) bit description . . . . . . . . . . . . . . . . . . . .416 Table 373. UART1 Divisor Latch MSB Register (U1DLM -
Table 352. UART0 Transmit Holding Register (U0THR - address 0xE001 0004 when DLAB = 1) bit
address 0xE000 C000, U2THR - 0xE007 8000, description . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
U3THR - 0xE007 C000 when DLAB = 0, Write Table 374. UART1 Interrupt Enable Register (U1IER -
Only) bit description . . . . . . . . . . . . . . . . . . . .416 address 0xE001 0004 when DLAB = 0) bit
Table 353. UARTn Divisor Latch LSB Register (U0DLL - description . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
address 0xE000 C000, U2DLL - 0xE007 8000, Table 375. UART1 Interrupt Identification Register (U1IIR -
U3DLL - 0xE007 C000 when DLAB = 1) bit address 0xE001 0008, Read Only) bit
Table 354. UARTn Divisor Latch MSB Register (U0DLM - Table 376. UART1 Interrupt Handling . . . . . . . . . . . . . . . 442
address 0xE000 C004, U2DLM - 0xE007 8004, Table 377. UART1 FIFO Control Register (U1FCR - address
U3DLM - 0xE007 C004 when DLAB = 1) bit 0xE001 0008, Write Only) bit description. . . . 443
description . . . . . . . . . . . . . . . . . . . . . . . . . . .417 Table 378. UART1 Line Control Register (U1LCR - address
Table 355. UARTn Interrupt Enable Register (U0IER - 0xE001 000C) bit description. . . . . . . . . . . . . 443
address 0xE000 C004, U2IER - 0xE007 8004, Table 379. UART1 Modem Control Register (U1MCR -
U3IER - 0xE007 C004 when DLAB = 0) bit address 0xE001 0010) bit description . . . . . . 444
description . . . . . . . . . . . . . . . . . . . . . . . . . . .417 Table 380. Modem status interrupt generation . . . . . . . . 446
Table 356. UARTn Interrupt Identification Register (U0IIR - Table 381. UART1 Line Status Register (U1LSR - address
address 0xE000 C008, U2IIR - 0x7008 8008, 0xE001 0014, Read Only) bit description . . . 447
U3IIR - 0x7008 C008, Read Only) bit description. Table 382. UART1 Modem Status Register (U1MSR -
418 address 0xE001 0018) bit description . . . . . . 448
Table 357. UARTn Interrupt Handling . . . . . . . . . . . . . . .419 Table 383. UART1 Scratch Pad Register (U1SCR - address
Table 358. UARTn FIFO Control Register (U0FCR - address 0xE001 0014) bit description . . . . . . . . . . . . . 449
0xE000 C008, U2FCR - 0xE007 8008, U3FCR - Table 384. Auto-baud Control Register (U1ACR - address
0xE007 C008, Write Only) bit description. . . .421 0xE001 0020) bit description . . . . . . . . . . . . . 449
Table 359. UARTn Line Control Register (U0LCR - address Table 385. UART1 Fractional Divider Register (U1FDR -
0xE000 C00C, U2LCR - 0xE007 800C, U3LCR - address 0xE001 0028) bit description . . . . . . 453
0xE007 C00C) bit description . . . . . . . . . . . . .421 Table 386. Fractional Divider setting look-up table . . . . . 455
Table 360. UARTn Line Status Register (U0LSR - address Table 387. UART1 Transmit Enable Register (U1TER -
0xE000 C014, U2LSR - 0xE007 8014, U3LSR - address 0xE001 0030) bit description . . . . . . 456

Table 388. SPI Data To Clock Phase Relationship . . . . .459 Table 419. SPI register map . . . . . . . . . . . . . . . . . . . . . . 495
Table 389. SPI Pin Description . . . . . . . . . . . . . . . . . . . .462 Table 420: Power Control register (MCIPower - address
Table 390. SPI Register Map. . . . . . . . . . . . . . . . . . . . . .463 0xE008 C000) bit description. . . . . . . . . . . . . 496
Table 391: SPI Control Register (S0SPCR - address Table 421: Clock Control register (MCIClock - address
0xE002 0000) bit description . . . . . . . . . . . . .463 0xE008 C004) bit description. . . . . . . . . . . . . 497
Table 392: SPI Status Register (S0SPSR - address Table 422: Argument register (MCIArgument - address
0xE002 0004) bit description . . . . . . . . . . . . .464 0xE008 C008) bit description. . . . . . . . . . . . . 497
Table 393: SPI Data Register (S0SPDR - address Table 423: Command register (MCICommand - address
0xE002 0008) bit description . . . . . . . . . . . . .465 0xE008 C00C) bit description . . . . . . . . . . . . 498
Table 394: SPI Clock Counter Register (S0SPCCR - address Table 424: Command Response Types . . . . . . . . . . . . . 498
0xE002 000C) bit description . . . . . . . . . . . . .465 Table 425: Command Response register
Table 395: SPI Test Control Register (SPTCR - address (MCIRespCommand - address 0xE008 C010) bit
0xE002 0010) bit description . . . . . . . . . . . . .466 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Table 396: SPI Test Status Register (SPTSR - address Table 426: Response registers (MCIResponse0-3 -
0xE002 0014) bit description . . . . . . . . . . . . .466 addresses 0xE008 0014, 0xE008 C018,
Table 397: SPI Interrupt Register (S0SPINT - address 0xE008 001C and 0xE008 C020) bit
0xE002 001C) bit description . . . . . . . . . . . . .466 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Table 398. SSP pin descriptions . . . . . . . . . . . . . . . . . . .469 Table 427: Response Register Type. . . . . . . . . . . . . . . . 499
Table 399. SSP Register Map . . . . . . . . . . . . . . . . . . . . .476 Table 428: Data Timer register (MCIDataTimer - address
Table 400: SSPn Control Register 0 (SSP0CR0 - address 0xE008 C024) bit description. . . . . . . . . . . . . 499
0xE006 8000, SSP1CR0 - 0xE003 0000) bit Table 429: Data Length register (MCIDataLength - address
description . . . . . . . . . . . . . . . . . . . . . . . . . . .477 0xE008 C028) bit description. . . . . . . . . . . . . 499
Table 401: SSPn Control Register 1 (SSP0CR1 - address Table 430: Data Control register (MCIDataCtrl - address
0xE006 8004, SSP1CR1 - 0xE003 0004) bit 0xE008 C02C) bit description . . . . . . . . . . . . 500
description . . . . . . . . . . . . . . . . . . . . . . . . . . .478 Table 431: Data Block Length . . . . . . . . . . . . . . . . . . . . . 500
Table 402: SSPn Data Register (SSP0DR - address Table 432: Data Counter register (MCIDataCnt - address
0xE006 8008, SSP1DR - 0xE003 0008) bit 0xE008 C030) bit description. . . . . . . . . . . . . 501
description . . . . . . . . . . . . . . . . . . . . . . . . . . .479 Table 433: Status register (MCIStatus - address
Table 403: SSPn Status Register (SSP0SR - address 0xE008 C034) bit description. . . . . . . . . . . . . 501
0xE006 800C, SSP1SR - 0xE003 000C) bit Table 434: Clear register (MCIClear - address 0xE008 C038)
description . . . . . . . . . . . . . . . . . . . . . . . . . . .479 bit description. . . . . . . . . . . . . . . . . . . . . . . . . 502
Table 404: SSPn Clock Prescale Register (SSP0CPSR - Table 435: Interrupt Mask registers (MCIMask0 - address
address 0xE006 8010, SSP1CPSR - 0xE008 C03C) bit description . . . . . . . . . . . . 502
0xE003 8010) bit description . . . . . . . . . . . . .480 Table 436: FIFO Counter register (MCIFifoCnt - address
Table 405: SSPn Interrupt Mask Set/Clear register 0xE008 C048) bit description. . . . . . . . . . . . . 503
(SSP0IMSC - address 0xE006 8014, SSP1IMSC Table 437: Data FIFO register (MCIFIFO - address
- 0xE003 0014) bit description . . . . . . . . . . . .481 0xE008 C080 to 0xE008 C0BC) bit
Table 406: SSPn Raw Interrupt Status register (SSP0RIS - description . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
address 0xE006 8018, SSP1RIS - 0xE003 0018) Table 438. I2C Pin Description . . . . . . . . . . . . . . . . . . . . 506
bit description . . . . . . . . . . . . . . . . . . . . . . . . .481 Table 439. I2CnCONSET used to configure Master
Table 407: SSPn Masked Interrupt Status register (SSPnMIS mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
-address 0xE006 801C, SSP1MIS - Table 440. I2CnCONSET used to configure Slave mode 508
0xE003 001C) bit description . . . . . . . . . . . . .482 Table 441. I2C register map . . . . . . . . . . . . . . . . . . . . . . 513
Table 408: SSPn interrupt Clear Register (SSP0ICR - Table 442. I2C Control Set Register (I2C[0/1/2]CONSET -
address 0xE006 8020, SSP1ICR - 0xE003 0020) addresses: 0xE001 C000, 0xE005 C000,
bit description . . . . . . . . . . . . . . . . . . . . . . . . .482 0xE008 0000) bit description . . . . . . . . . . . . . 514
Table 409: SSPn DMA Control Register (SSP0DMACR - Table 443. I2C Control Set Register (I2C[0/1/2]CONCLR -
address 0xE006 8024, SSP1DMACR - addresses 0xE001 C018, 0xE005 C018,
0xE003 0024) bit description . . . . . . . . . . . . .482 0xE008 0018) bit description . . . . . . . . . . . . . 516
Table 410. SD/MMC card interface pin description . . . . .484 Table 444. I2C Status Register (I2C[0/1/2]STAT - addresses
Table 411. Command format . . . . . . . . . . . . . . . . . . . . . .488 0xE001 C004, 0xE005 C004, 0xE008 0004) bit
Table 412. Simple response format . . . . . . . . . . . . . . . . .488 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Table 413. Long response format . . . . . . . . . . . . . . . . . .488 Table 445. I2C Data Register ( I2C[0/1/2]DAT - addresses
Table 414. Command path status flags . . . . . . . . . . . . . .489 0xE001 C008, 0xE005 C008, 0xE008 0008) bit
Table 415. CRC token status. . . . . . . . . . . . . . . . . . . . . .492 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Table 416. Data path status flags . . . . . . . . . . . . . . . . . .493 Table 446. I2C Slave Address register (I2C[0/1/2]ADR -
Table 417. Transmit FIFO status flags. . . . . . . . . . . . . . .494 addresses 0xE001 C00C, 0xE005 C00C,
Table 418. Receive FIFO status flags . . . . . . . . . . . . . . .495 0xE008 000C) bit description. . . . . . . . . . . . . 517

Table 447. I2C SCL High Duty Cycle register 0xE007 0014, 0xE007 4014) bit description . 559
(I2C[0/1/2]SCLH - addresses 0xE001 C010, Table 480: Capture Control Register (T[0/1/2/3]CCR -
0xE005 C010, 0xE008 0010) bit description .517 addresses 0xE000 4028, 0xE000 8020,
Table 448. I2C SCL Low Duty Cycle register (I2C[0/1/2]SCLL 0xE007 0028, 0xE007 4028) bit description . 560
- addresses 0xE001 C014, 0xE005 C014, Table 481: External Match Register (T[0/1/2/3]EMR -
0xE008 0014) bit description . . . . . . . . . . . . .517 addresses 0xE000 403C, 0xE000 803C,
Table 449. Example I2C Clock Rates . . . . . . . . . . . . . . .518 0xE007 003C, 0xE007 403C) bit description . 561
Table 450. Abbreviations used to describe an I2C Table 482. External Match Control . . . . . . . . . . . . . . . . . 561
operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . .518 Table 483. Set and reset inputs for PWM Flip-Flops. . . . 567
Table 451. I2CONSET used to initialize Master Transmitter Table 484. Pin summary . . . . . . . . . . . . . . . . . . . . . . . . . 568
mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .519 Table 485: Addresses for PWM1 . . . . . . . . . . . . . . . . . . 569
Table 452. I2C0ADR and I2C1ADR usage in Slave Receiver Table 486. PWM1 register map . . . . . . . . . . . . . . . . . . . 569
mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .520 Table 487: PWM Interrupt Register (PWM1IR - address
Table 453. I2C0CONSET and I2C1CONSET used to 0xE001 8000) bit description . . . . . . . . . . . . . 570
initialize Slave Receiver mode . . . . . . . . . . . .520 Table 488: PWM Timer Control Register (PWM1TCR
Table 454. Master Transmitter mode. . . . . . . . . . . . . . . .526 address 0xE001 8004) bit description . . . . . . 571
Table 455. Master Receiver mode. . . . . . . . . . . . . . . . . .527 Table 489: PWM Count control Register (PWM1CTCR -
Table 456. Slave Receiver Mode. . . . . . . . . . . . . . . . . . .528 address 0xE001 8004) bit description . . . . . . 572
Table 457. Tad_105: Slave Transmitter mode . . . . . . . . .530 Table 490: Match Control Register (PWM1MCR - address
Table 458. Miscellaneous states . . . . . . . . . . . . . . . . . . .532 0xE000 8014) bit description . . . . . . . . . . . . . 572
Table 459. Pin descriptions . . . . . . . . . . . . . . . . . . . . . . .544 Table 491: PWM Capture Control Register (PWM1CCR -
Table 460. I2S register map. . . . . . . . . . . . . . . . . . . . . . .546 address 0xE001 8028) bit description . . . . . . 574
Table 461: Digital Audio Output register (I2SDAO - address Table 492: PWM Control Registers (PWM1PCR - address
0xE008 8000) bit description . . . . . . . . . . . . .546 0xE001 804C) bit description. . . . . . . . . . . . . 575
Table 462: Digital Audio Input register (I2SDAI - address Table 493: PWM Latch Enable Register (PWM1LER -
0xE008 8004) bit description . . . . . . . . . . . . .547 address 0xE001 8050) bit description . . . . . . 577
Table 463: Transmit FIFO register (I2STXFIFO - address Table 494. Watchdog register map . . . . . . . . . . . . . . . . . 579
0xE008 8008) bit description . . . . . . . . . . . . .547 Table 495. Watchdog operating modes selection . . . . . . 580
Table 464: Receive FIFO register (I2RXFIFO - address Table 496: Watchdog Mode register (WDMOD - address
0xE008 800C) bit description . . . . . . . . . . . . .547 0xE000 0000) bit description . . . . . . . . . . . . . 580
Table 465: Status Feedback register (I2SSTATE - address Table 497: Watchdog Constant register (WDTC - address
0xE008 8010) bit description . . . . . . . . . . . . .548 0xE000 0004) bit description . . . . . . . . . . . . . 580
Table 466: DMA Configuration register 1 (I2SDMA1 - Table 498: Watchdog Feed Register (WDFEED - address
address 0xE008 8014) bit description . . . . . .548 0xE000 0008) bit description . . . . . . . . . . . . . 581
Table 467: DMA Configuration register 2 (I2SDMA2 - Table 499: Watchdog Timer Value register (WDTV - address
address 0xE008 8018) bit description . . . . . .548 0xE000 000C) bit description. . . . . . . . . . . . . 581
Table 468: Interrupt Request Control register (I2SIRQ - Table 500: Watchdog Timer Clock Source Selection register
address 0xE008 801C) bit description . . . . . .549 (WDCLKSEL - address 0xE000 0010) bit
Table 469: Transmit Clock Rate register (I2TXRATE - description . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
address 0xE008 8020) bit description . . . . . .549 Table 501. RTC pin description. . . . . . . . . . . . . . . . . . . . 584
Table 470: Receive Clock Rate register (I2SRXRATE - Table 502. Real Time Clock register map . . . . . . . . . . . . 585
address 0xE008 8024) bit description . . . . . .550 Table 503. Interrupt Location Register (ILR - address
Table 471. Conditions for FIFO level comparison . . . . . .551 0xE002 4000) bit description . . . . . . . . . . . . . 586
Table 472. DMA and interrupt request generation. . . . . .551 Table 504. Clock Tick Counter Register (CTCR - address
Table 473. Status feedback in the I2SSTATE register . . .551 0xE002 4004) bit description . . . . . . . . . . . . . 587
Table 474. Timer/Counter pin description . . . . . . . . . . . .554 Table 505. Clock Control Register (CCR - address
Table 475. TIMER/COUNTER0-3 register map. . . . . . . .555 0xE002 4008) bit description . . . . . . . . . . . . . 587
Table 476: Interrupt Register (T[0/1/2/3]IR - addresses Table 506. Counter Increment Interrupt Register (CIIR -
0xE000 4000, 0xE000 8000, 0xE007 0000, address 0xE002 400C) bit description . . . . . . 588
0xE007 4000) bit description . . . . . . . . . . . . .556 Table 507. Counter Increment Select Mask register (CISS -
Table 477: Timer Control Register (TCR, TIMERn: TnTCR - address 0xE002 4040) bit description . . . . . . 588
addresses 0xE000 4004, 0xE000 8004, Table 508. Alarm Mask Register (AMR - address
0xE007 0004, 0xE007 4004) bit description . .557 0xE002 4010) bit description . . . . . . . . . . . . . 589
Table 478: Count Control Register (T[0/1/2/3]CTCR - Table 509. Consolidated Time register 0 (CTIME0 - address
addresses 0xE000 4070, 0xE000 8070, 0xE002 4014) bit description . . . . . . . . . . . . . 589
0xE007 0070, 0xE007 4070) bit description . .557 Table 510. Consolidated Time register 1 (CTIME1 - address
Table 479: Match Control Register (T[0/1/2/3]MCR - 0xE002 4018) bit description . . . . . . . . . . . . . 590
addresses 0xE000 4014, 0xE000 8014, Table 511. Consolidated Time register 2 (CTIME2 - address

0xE002 401C) bit description . . . . . . . . . . . . .590 Table 553. IAP Blank check sector(s) command . . . . . . 626
Table 512. Time Counter relationships and values . . . . .590 Table 554. IAP Read Part Identification command . . . . . 626
Table 513. Time Counter registers . . . . . . . . . . . . . . . . .591 Table 555. IAP Read Boot Code version number
Table 514. Alarm registers. . . . . . . . . . . . . . . . . . . . . . . .591 command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Table 515. Reference Clock Divider registers . . . . . . . . .592 Table 556. IAP Compare command . . . . . . . . . . . . . . . . 627
Table 516: Prescaler Integer register (PREINT - address Table 557. Reinvoke ISP . . . . . . . . . . . . . . . . . . . . . . . . 627
0xE002 4080) bit description . . . . . . . . . . . . .592 Table 558. IAP Status Codes Summary . . . . . . . . . . . . . 627
Table 517: Prescaler Integer register (PREFRAC - address Table 559. GPDMA accessible memory . . . . . . . . . . . . . 630
0xE002 4084) bit description . . . . . . . . . . . . .593 Table 560. Endian behavior . . . . . . . . . . . . . . . . . . . . . . 633
Table 518. Prescaler cases where the Integer Counter Table 561. DMA Connections . . . . . . . . . . . . . . . . . . . . . 635
reload value is incremented . . . . . . . . . . . . . .595 Table 562. GPDMA register map . . . . . . . . . . . . . . . . . . 639
Table 519. Recommended values for the RTC external Table 563. Interrupt Status register (DMACIntStatus -
32 kHz oscillator CX1/X2 components . . . . . . .597 address 0xFFE0 4000) bit description . . . . . . 640
Table 520. A/D pin description. . . . . . . . . . . . . . . . . . . . .599 Table 564. Interrupt Terminal Count Status register
Table 521. A/D registers . . . . . . . . . . . . . . . . . . . . . . . . .599 (DMACIntTCStatus - address 0xFFE0 4004) bit
Table 522: A/D Control Register (AD0CR - address description . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
0xE003 4000) bit description . . . . . . . . . . . . .600 Table 565. Interrupt Terminal Count Clear register
Table 523: A/D Global Data Register (AD0GDR - address (DMACIntClear - address 0xFFE0 4008) bit
0xE003 4004) bit description . . . . . . . . . . . . .602 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Table 524: A/D Status Register (AD0STAT - address Table 566. Interrupt Error Status register
0xE003 4030) bit description . . . . . . . . . . . . .602 (DMACIntErrorStatus - address 0xFFE0 400C) bit
Table 525: A/D Interrupt Enable Register (AD0INTEN - description . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
address 0xE003 400C) bit description . . . . . .603 Table 567. Interrupt Error Clear register (DMACIntErrClr -
Table 526: A/D Data Registers (AD0DR0 to AD0DR7 - address 0xFFE0 4010) bit description . . . . . . 641
addresses 0xE003 4010 to 0xE003 402C) bit Table 568. Raw Interrupt Terminal Count Status register
description . . . . . . . . . . . . . . . . . . . . . . . . . . .603 (DMACRawIntTCStatus - address 0xFFE0 4014)
Table 527. D/A Pin Description . . . . . . . . . . . . . . . . . . . .605 bit description. . . . . . . . . . . . . . . . . . . . . . . . . 642
Table 528: D/A Converter Register (DACR - address Table 569. Raw Error Interrupt Status register
0xE006 C000) bit description . . . . . . . . . . . . .606 (DMACRawIntErrorStatus - address
Table 529. Sectors in a LPC2300 device. . . . . . . . . . . . .612 0xFFE0 4018) bit description . . . . . . . . . . . . . 642
Table 530. Code Read Protection options . . . . . . . . . . . .613 Table 570. Enabled Channel register (DMACEnbldChns -
Table 531. Code Read Protection hardware/software address 0xFFE0 401C) bit description. . . . . . 642
interaction . . . . . . . . . . . . . . . . . . . . . . . . . . . .614 Table 571. Software Burst Request register
Table 532. ISP command summary. . . . . . . . . . . . . . . . .614 (DMACSoftBReq - address 0xFFE0 4020) bit
Table 533. ISP Unlock command . . . . . . . . . . . . . . . . . .615 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Table 534. ISP Set Baud Rate command . . . . . . . . . . . .615 Table 572. Software Single Request register
Table 535. Correlation between possible ISP baudrates and (DMACSoftSReq - address 0xFFE0 4024) bit
CCLK frequency (in MHz). . . . . . . . . . . . . . . .615 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Table 536. ISP Echo command . . . . . . . . . . . . . . . . . . . .616 Table 573. Software Last Burst Request register
Table 537. ISP Write to RAM command . . . . . . . . . . . . .616 (DMACSoftLBReq - address 0xFFE0 4028) bit
Table 538. ISP Read Memory command. . . . . . . . . . . . .617 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Table 539. ISP Prepare sector(s) for write operation Table 574. Software Last Single Request register
command . . . . . . . . . . . . . . . . . . . . . . . . . . . .617 (DMACSoftLSReq - address 0xFFE0 402C) bit
Table 540. ISP Copy command . . . . . . . . . . . . . . . . . . . .618 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Table 541. ISP Go command. . . . . . . . . . . . . . . . . . . . . .618 Table 575. Configuration register (DMACConfiguration -
Table 542. ISP Erase sector command . . . . . . . . . . . . . .619 address 0xFFE0 4030) bit description . . . . . . 644
Table 543. ISP Blank check sector command . . . . . . . . .619 Table 576. Synchronization register (DMACSync - address
Table 544. ISP Read Part Identification command . . . . .619 0xFFE0 4034) bit description . . . . . . . . . . . . . 645
Table 545. LPC2300 part identification numbers. . . . . . .620 Table 577. Channel Source Address registers
Table 546. ISP Read Boot Code version number (DMACC0SrcAddr - address 0xFFE0 4100 and
command . . . . . . . . . . . . . . . . . . . . . . . . . . . .620 DMACC1SrcAddr - address 0xFFE0 4120) bit
Table 547. ISP Compare command. . . . . . . . . . . . . . . . .621 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Table 548. ISP Return Codes Summary . . . . . . . . . . . . .621 Table 578. Channel Destination Address registers
Table 549. IAP Command Summary . . . . . . . . . . . . . . . .623 (DMACC0DestAddr - address 0xFFE0 4104 and
Table 550. IAP Prepare sector(s) for write operation DMACC1DestAddr - address 0xFFE0 4124) bit
command . . . . . . . . . . . . . . . . . . . . . . . . . . . .624 description . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Table 551. IAP Copy RAM to flash command . . . . . . . . .625 Table 579. Channel Linked List Item registers (DMACC0LLI
Table 552. IAP Erase Sector(s) command . . . . . . . . . . .625 - address 0xFFE0 4108 and DMACC1LLI -

address 0xFFE0 4128) bit description . . . . . .647

Table 580. Channel Control registers (DMACC0Control -
address 0xFFE0 410C and DMACC1Control -
address 0xFFE0 412C) bit description . . . . . .647
Table 581. Source or destination burst size. . . . . . . . . . .648
Table 582. Source or destination transfer width . . . . . . .648
Table 583. Protection bits . . . . . . . . . . . . . . . . . . . . . . . .649
Table 584. Channel Configuration registers
(DMACC0Configuration - address 0xFFE0 4110
and DMACC1Configuration - address
0xFFE0 4130) bit description . . . . . . . . . . . . .650
Table 585. Flow control and transfer type bits . . . . . . . . .651
Table 586. DMA request signal usage. . . . . . . . . . . . . . .655
Table 587. ETM configuration . . . . . . . . . . . . . . . . . . . . .658
Table 588. ETM pin description . . . . . . . . . . . . . . . . . . . .659
Table 589. ETM Registers . . . . . . . . . . . . . . . . . . . . . . . .660
Table 590. EmbeddedICE pin description . . . . . . . . . . . .663
Table 591. EmbeddedICE logic registers . . . . . . . . . . . .664
Table 592. RealMonitor stack requirement . . . . . . . . . . .669
Table 593. Acronym list . . . . . . . . . . . . . . . . . . . . . . . . .677

34.4 Figures
Fig 1. LPC2361/62 block diagram . . . . . . . . . . . . . . . . . 11 Fig 46. Entry in FullCAN and individual standard identifier
Fig 2. LPC2364/65/66/67/68 block diagram . . . . . . . . .12 tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Fig 3. LPC2377/78 block diagram . . . . . . . . . . . . . . . . .13 Fig 47. Entry in standard identifier range table . . . . . . . 292
Fig 4. LPC2387 block diagram . . . . . . . . . . . . . . . . . . .14 Fig 48. Entry in either extended identifier table . . . . . . . 292
Fig 5. LPC2388 block diagram . . . . . . . . . . . . . . . . . . .15 Fig 49. ID Look-up table example explaining the search
Fig 6. LPC2461/63 memory map . . . . . . . . . . . . . . . . . .17 algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Fig 7. LPC2364/65/66/67/68 system memory map . . . .18 Fig 50. Semaphore procedure for reading an auto-stored
Fig 8. LPC2377/78 system memory map. . . . . . . . . . . .19 message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Fig 9. LPC2387 memory map . . . . . . . . . . . . . . . . . . . .20 Fig 51. FullCAN section example of the ID look-up
Fig 10. LPC2388 memory map . . . . . . . . . . . . . . . . . . . .21 table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Fig 11. Peripheral memory map. . . . . . . . . . . . . . . . . . . .22 Fig 52. FullCAN message object layout . . . . . . . . . . . . 304
Fig 12. AHB peripheral map . . . . . . . . . . . . . . . . . . . . . .23 Fig 53. Normal case, no messages lost . . . . . . . . . . . . 306
Fig 13. Map of lower memory is showing re-mapped and Fig 54. Message lost . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
re-mappable areas. . . . . . . . . . . . . . . . . . . . . . . .28 Fig 55. Message gets overwritten . . . . . . . . . . . . . . . . . 307
Fig 14. Reset block diagram including the wakeup timer.32 Fig 56. Message overwritten indicated by semaphore bits
Fig 15. Example of start-up after reset. . . . . . . . . . . . . . .33 and message lost . . . . . . . . . . . . . . . . . . . . . . . 308
Fig 16. Clock generation for the LPC2300. . . . . . . . . . . .45 Fig 57. Message overwritten indicated by message lost309
Fig 17. Oscillator modes and models: a) slave mode of Fig 58. Clearing message lost. . . . . . . . . . . . . . . . . . . . 310
operation, b) oscillation mode of operation, c) Fig 59. Detailed example of acceptance filter tables and ID
external crystal model used for CX1/X2 evaluation47 index values . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Fig 18. PLL block diagram (N = 16, M = 125, USBSEL = 6, Fig 60. ID Look-up table configuration example (no
CCLKSEL = 4) . . . . . . . . . . . . . . . . . . . . . . . . . . .51 FullCAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Fig 19. PLL and clock dividers . . . . . . . . . . . . . . . . . . . . .60 Fig 61. ID Look-up table configuration example (FullCAN
Fig 20. EMC block diagram . . . . . . . . . . . . . . . . . . . . . . .72 activated and enabled) . . . . . . . . . . . . . . . . . . . 316
Fig 21. 8-bit bank external memory interface. . . . . . . . . .84 Fig 62. USB device controller block diagram . . . . . . . . 321
Fig 22. Block diagram of the Vectored Interrupt Fig 63. USB MaxPacketSize register array indexing . . 338
Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95 Fig 64. Interrupt event handling . . . . . . . . . . . . . . . . . . 351
Fig 23. Simplified block diagram of the Memory Accelerator Fig 65. UDCA Head register and DMA Descriptors . . . 364
Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97 Fig 66. Isochronous OUT endpoint operation example. 372
Fig 24. Block diagram of the Memory Accelerator Fig 67. Data transfer in ATLE mode . . . . . . . . . . . . . . . 373
Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102 Fig 68. USB Host controller block diagram . . . . . . . . . . 379
Fig 25. LPC2361/62 pinning . . . . . . . . . . . . . . . . . . . . .104 Fig 69. USB OTG controller block diagram. . . . . . . . . . 384
Fig 26. LPC2364/65/66/67/68 LQFP100 packages . . . . 113 Fig 70. USB OTG port configuration: port U1 OTG
Fig 27. LPC2364/65/66/67/68 pinning TFBGA100 Dual-Role device, port U2 host . . . . . . . . . . . . . 386
package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Fig 71. USB OTG port configuration: VP_VM mode . . . 387
Fig 28. LPC2378 144-pin package . . . . . . . . . . . . . . . .124 Fig 72. USB OTG port configuration: port U2 host, port U1
Fig 29. LPC2387 pinning LQFP100 package . . . . . . . .134 host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Fig 30. LPC2388 pinning LQFP144 package . . . . . . . .142 Fig 73. USB OTG port configuration: port U1 host, port U2
Fig 31. Ethernet block diagram . . . . . . . . . . . . . . . . . . .188 device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Fig 32. Ethernet packet fields . . . . . . . . . . . . . . . . . . . .191 Fig 74. Port selection for PORT_FUNC bit 0 = 0 and
Fig 33. Receive descriptor memory layout. . . . . . . . . . .218 PORT_FUNC bit 1 = 0. . . . . . . . . . . . . . . . . . . . 393
Fig 34. Transmit descriptor memory layout . . . . . . . . . .221 Fig 75. USB OTG interrupt handling . . . . . . . . . . . . . . . 399
Fig 35. Transmit example memory and registers. . . . . .233 Fig 76. USB OTG controller with software stack . . . . . . 401
Fig 36. Receive Example Memory and Registers . . . . .239 Fig 77. Hardware support for B-device switching from
Fig 37. Transmit Flow Control . . . . . . . . . . . . . . . . . . . .244 peripheral state to host state . . . . . . . . . . . . . . 402
Fig 38. Receive filter block diagram. . . . . . . . . . . . . . . .246 Fig 78. State transitions implemented in software during
Fig 39. Receive Active/Inactive state machine . . . . . . .250 B-device switching from peripheral to host . . . . 403
Fig 40. Transmit Active/Inactive state machine . . . . . . .251 Fig 79. Hardware support for A-device switching from host
Fig 41. CAN controller block diagram . . . . . . . . . . . . . .261 state to peripheral state. . . . . . . . . . . . . . . . . . . 405
Fig 42. Transmit buffer layout for standard and extended Fig 80. State transitions implemented in software during
frame format configurations . . . . . . . . . . . . . . . .262 A-device switching from host to peripheral . . . . 406
Fig 43. Receive buffer layout for standard and extended Fig 81. Clocking and power control. . . . . . . . . . . . . . . . 409
frame format configurations . . . . . . . . . . . . . . . .263 Fig 82. Autobaud a) mode 0 and b) mode 1 waveform 426
Fig 44. Global Self-Test (high-speed CAN Bus Fig 83. Algorithm for setting UART dividers . . . . . . . . . 429
example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .264 Fig 84. LPC2300 UART0, 2 and 3 block diagram . . . . . 432
Fig 45. Local Self-Test (high-speed CAN Bus example) 265 Fig 85. Auto-RTS functional timing . . . . . . . . . . . . . . . . 445

Fig 86. Auto-CTS functional timing . . . . . . . . . . . . . . . .446 Fig 129. Sample PWM waveforms . . . . . . . . . . . . . . . . . 567
Fig 87. Auto-baud a) mode 0 and b) mode 1 waveform 452 Fig 130. Watchdog block diagram . . . . . . . . . . . . . . . . . 582
Fig 88. Algorithm for setting UART dividers. . . . . . . . . .454 Fig 131. RTC block diagram . . . . . . . . . . . . . . . . . . . . . . 584
Fig 89. LPC2300 UART1 block diagram . . . . . . . . . . . .457 Fig 132. RTC prescaler block diagram . . . . . . . . . . . . . . 594
Fig 90. SPI data transfer format (CPHA = 0 and Fig 133. RTC 32 kHz crystal oscillator circuit . . . . . . . . . 596
CPHA = 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .459 Fig 134. Map of lower memory after reset . . . . . . . . . . . 608
Fig 91. SPI block diagram . . . . . . . . . . . . . . . . . . . . . . .467 Fig 135. Boot process flowchart . . . . . . . . . . . . . . . . . . . 611
Fig 92. Texas Instruments Synchronous Serial Frame Fig 136. IAP parameter passing . . . . . . . . . . . . . . . . . . . 624
Format: a) Single and b) Continuous/back-to-back Fig 137. GPDMA Block Diagram . . . . . . . . . . . . . . . . . . 631
Two Frames Transfer. . . . . . . . . . . . . . . . . . . . .470 Fig 138. GPDMA in the LPC23XX . . . . . . . . . . . . . . . . . 632
Fig 93. SPI Frame Format with CPOL=0 and CPHA=0 (a) Fig 139. LLI example . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Single and b) Continuous Transfer) . . . . . . . . . .471 Fig 140. ETM debug environment block diagram . . . . . . 661
Fig 94. SPI Frame Format with CPOL=0 and CPHA=1 .472 Fig 141. EmbeddedICE debug environment block
Fig 95. SPI Frame Format with CPOL = 1 and CPHA = 0 (a) diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
Single and b) Continuous Transfer) . . . . . . . . . .473 Fig 142. RealMonitor Components . . . . . . . . . . . . . . . . 667
Fig 96. SPI Frame Format with CPOL = 1 and Fig 143. RealMonitor as a State Machine. . . . . . . . . . . . 668
CPHA = 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .474 Fig 144. Exception Handlers . . . . . . . . . . . . . . . . . . . . . 671
Fig 97. Microwire Frame Format (Single Transfer) . . . .475
Fig 98. Microwire Frame Format (Continuous
Transfers). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .476
Fig 99. Microwire frame format setup and hold details .476
Fig 100. Multimedia card system. . . . . . . . . . . . . . . . . . .484
Fig 101. Secure digital memory card connection . . . . . .485
Fig 102. MCI adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . .485
Fig 103. Command path state machine. . . . . . . . . . . . . .487
Fig 104. MCI command transfer . . . . . . . . . . . . . . . . . . .487
Fig 105. Data path state machine . . . . . . . . . . . . . . . . . .490
Fig 106. Pending command start. . . . . . . . . . . . . . . . . . .492
Fig 107. I2C bus configuration . . . . . . . . . . . . . . . . . . . . .505
Fig 108. Format in the Master Transmitter mode . . . . . .507
Fig 109. Format of Master Receive mode . . . . . . . . . . . .507
Fig 110. A master receiver switch to master Transmitter after
sending repeated START. . . . . . . . . . . . . . . . . .508
Fig 111. Format of Slave Receiver mode . . . . . . . . . . . .508
Fig 112. Format of Slave Transmitter mode . . . . . . . . . .509
Fig 113. I2C Bus serial interface block diagram. . . . . . . .510
Fig 114. Arbitration procedure . . . . . . . . . . . . . . . . . . . . . 511
Fig 115. Serial clock synchronization . . . . . . . . . . . . . . .512
Fig 116. Format and States in the Master Transmitter
mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .522
Fig 117. Format and States in the Master Receiver
mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .523
Fig 118. Format and States in the Slave Receiver mode 524
Fig 119. Format and States in the Slave Transmitter
mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .525
Fig 120. Simultaneous repeated START conditions from 2
masters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .533
Fig 121. Forced access to a busy I2C bus. . . . . . . . . . . .534
Fig 122. Recovering from a bus obstruction caused by a low
level on SDA . . . . . . . . . . . . . . . . . . . . . . . . . . .534
Fig 123. Simple I2S configurations and bus timing . . . . .545
Fig 124. FIFO contents for various I2S modes . . . . . . . .552
Fig 125. A timer cycle in which PR=2, MRx=6, and both
interrupt and reset on match are enabled. . . . . .562
Fig 126. A Timer Cycle in Which PR=2, MRx=6, and Both
Interrupt and Stop on Match are Enabled . . . . .562
Fig 127. Timer block diagram . . . . . . . . . . . . . . . . . . . . .563
Fig 128. PWM block diagram . . . . . . . . . . . . . . . . . . . . .566

34.5 Contents
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.4 Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 How to read this manual . . . . . . . . . . . . . . . . . . 3 1.5 Ordering information and options. . . . . . . . . . 6
1.3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.6 Architectural overview . . . . . . . . . . . . . . . . . . . 8
1.3.1 General features . . . . . . . . . . . . . . . . . . . . . . . . 3 1.7 ARM7TDMI-S processor . . . . . . . . . . . . . . . . . . 9
1.3.2 Features available on LPC2361/62 . . . . . . . . . 5 1.8 On-chip flash memory system. . . . . . . . . . . . 10
1.3.3 Features available in LPC2377/78 and
1.9 On-chip Static RAM. . . . . . . . . . . . . . . . . . . . . 10
LPC2388. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.3.4 Features available in LPC2387 and LPC2388 . 5 1.10 Block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.5 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.1 Memory map and peripheral addressing. . . . 16 2.5 Memory mapping control . . . . . . . . . . . . . . . . 27
2.2 Memory maps. . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.5.1 Memory Mapping Control Register (MEMMAP -
2.3 APB peripheral addresses . . . . . . . . . . . . . . . 24 0xE01F C040) . . . . . . . . . . . . . . . . . . . . . . . . 27
2.5.2 Memory mapping control usage notes. . . . . . 27
2.4 LPC2300 memory re-mapping and boot ROM 25
2.4.1 Memory map concepts and operating modes. 25 2.6 Prefetch abort and data abort exceptions . . 29
2.4.2 Memory re-mapping . . . . . . . . . . . . . . . . . . . . 26

3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 3.6.4 External Interrupt Polarity register (EXTPOLAR -
3.2 Pin description . . . . . . . . . . . . . . . . . . . . . . . . . 30 0xE01F C14C) . . . . . . . . . . . . . . . . . . . . . . . . 37
3.3 Register description . . . . . . . . . . . . . . . . . . . . 30 3.7 Other system controls and status flags . . . . 38
3.4 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 3.7.1 AHB Configuration . . . . . . . . . . . . . . . . . . . . . 38
3.4.1 Reset Source Identification Register (RSIR - 3.7.1.1 AHB Arbiter Configuration register 1 (AHBCFG1 -
0xE01F C180) . . . . . . . . . . . . . . . . . . . . . . . . 33 0xE01F C188) . . . . . . . . . . . . . . . . . . . . . . . . 38
3.7.1.1.1 Examples of AHB1 settings . . . . . . . . . . . . . . 39
3.5 Brown-out detection . . . . . . . . . . . . . . . . . . . . 34
3.7.1.2 AHB Arbiter Configuration register 2 (AHBCFG2 -
3.6 External interrupt inputs . . . . . . . . . . . . . . . . . 35 0xE01F C18C) . . . . . . . . . . . . . . . . . . . . . . . . 40
3.6.1 Register description . . . . . . . . . . . . . . . . . . . . 35 3.7.1.2.1 Examples of AHB2 settings . . . . . . . . . . . . . . 41
3.6.2 External Interrupt flag register (EXTINT - 3.7.2 System Controls and Status register (SCS -
0xE01F C140) . . . . . . . . . . . . . . . . . . . . . . . . 35 0xE01F C1A0) . . . . . . . . . . . . . . . . . . . . . . . . 42
3.6.3 External Interrupt Mode register (EXTMODE - 3.8 Code security vs. debugging . . . . . . . . . . . . . 43
0xE01F C148) . . . . . . . . . . . . . . . . . . . . . . . . 36

4.1 How to read this chapter . . . . . . . . . . . . . . . . . 44 4.6.2 PLL and startup/boot code interaction . . . . . . 50
4.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 4.6.3 Register description . . . . . . . . . . . . . . . . . . . . 50
4.3 Register description . . . . . . . . . . . . . . . . . . . . 46 4.6.4 PLL Control register (PLLCON -
0xE01F C080) . . . . . . . . . . . . . . . . . . . . . . . . 51
4.4 Oscillators . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
4.6.5 PLL Configuration register (PLLCFG -
4.4.1 Internal RC oscillator . . . . . . . . . . . . . . . . . . . 46 0xE01F C084) . . . . . . . . . . . . . . . . . . . . . . . . 52
4.4.2 Main oscillator. . . . . . . . . . . . . . . . . . . . . . . . . 47 4.6.6 PLL Status register (PLLSTAT -
4.4.2.1 XTAL1 input . . . . . . . . . . . . . . . . . . . . . . . . . . 48 0xE01F C088) . . . . . . . . . . . . . . . . . . . . . . . . 54
4.4.2.2 Printed Circuit Board (PCB) layout guidelines 48 4.6.7 PLL Interrupt: PLOCK . . . . . . . . . . . . . . . . . . 55
4.4.3 RTC oscillator . . . . . . . . . . . . . . . . . . . . . . . . . 49 4.6.8 PLL Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.5 Clock source selection multiplexer . . . . . . . . 49 4.6.9 PLL Feed register (PLLFEED - 0xE01F C08C) 56
4.5.1 Clock Source Select register (CLKSRCSEL - 4.6.10 PLL and Power-down mode. . . . . . . . . . . . . . 56
0xE01F C10C) . . . . . . . . . . . . . . . . . . . . . . . . 49 4.6.11 PLL frequency calculation . . . . . . . . . . . . . . . 56
4.6 PLL (Phase Locked Loop). . . . . . . . . . . . . . . . 49 4.6.12 Procedure for determining PLL settings. . . . . 57
4.6.1 PLL operation . . . . . . . . . . . . . . . . . . . . . . . . . 50 4.6.13 Examples of PLL settings . . . . . . . . . . . . . . . 58
4.6.14 PLL setup sequence . . . . . . . . . . . . . . . . . . . 59

4.7 Clock dividers . . . . . . . . . . . . . . . . . . . . . . . . . 60 4.8.4 Deep power-down mode . . . . . . . . . . . . . . . . 64

4.7.1 CPU Clock Configuration register (CCLKCFG - 4.8.5 Peripheral power control . . . . . . . . . . . . . . . . 65
0xE01F C104) . . . . . . . . . . . . . . . . . . . . . . . . 60 4.8.6 Register description . . . . . . . . . . . . . . . . . . . . 65
4.7.2 USB Clock Configuration register (USBCLKCFG - 4.8.7 Power Mode Control register (PCON -
0xE01F C108) . . . . . . . . . . . . . . . . . . . . . . . . 61 0xE01F C0C0) . . . . . . . . . . . . . . . . . . . . . . . . 65
4.7.3 IRC Trim Register (IRCTRIM - 0xE01F C1A4) 61 Encoding of reduced power modes . . . . . . . . . 66
4.7.4 Peripheral Clock Selection registers 0 and 1 4.8.8 Interrupt Wakeup Register (INTWAKE -
(PCLKSEL0 - 0xE01F C1A8 and PCLKSEL1 - 0xE01F C144) . . . . . . . . . . . . . . . . . . . . . . . . 66
0xE01F C1AC) . . . . . . . . . . . . . . . . . . . . . . . . 62 4.8.9 Power Control for Peripherals register (PCONP -
4.8 Power control . . . . . . . . . . . . . . . . . . . . . . . . . . 63 0xE01F C0C4) . . . . . . . . . . . . . . . . . . . . . . . . 68
4.8.1 Idle mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 4.8.10 Power control usage notes . . . . . . . . . . . . . . 69
4.8.2 Sleep mode . . . . . . . . . . . . . . . . . . . . . . . . . . 64 4.8.11 Power domains . . . . . . . . . . . . . . . . . . . . . . . 70
4.8.3 Power-down mode . . . . . . . . . . . . . . . . . . . . . 64 4.9 Wakeup timer. . . . . . . . . . . . . . . . . . . . . . . . . . 70

5.1 How to read this chapter . . . . . . . . . . . . . . . . . 71 5.11.2 EMC Status Register (EMCStatus -
5.2 Basic configuration . . . . . . . . . . . . . . . . . . . . . 71 0xFFE0 8004) . . . . . . . . . . . . . . . . . . . . . . . . 77
5.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 5.11.3 EMC Configuration Register (EMCConfig -
0xFFE0 8008) . . . . . . . . . . . . . . . . . . . . . . . . 77
5.4 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
5.11.4 Static Memory Extended Wait Register
5.5 Functional overview . . . . . . . . . . . . . . . . . . . . 71 (EMCStaticExtendedWait - 0xFFE0 8080). . . 78
5.6 EMC functional description . . . . . . . . . . . . . . 72 5.11.5 Static Memory Configuration Registers
5.7 AHB Slave register interface. . . . . . . . . . . . . . 72 (EMCStaticConfig0-1 - 0xFFE0 8200, 220) . . 79
5.7.1 AHB Slave memory interface . . . . . . . . . . . . . 73 5.11.6 Static Memory Write Enable Delay Registers
5.7.1.1 Memory transaction endianness. . . . . . . . . . . 73 (EMCStaticWaitWen0-1 - 0xFFE0 8204, 224) 80
5.7.1.2 Memory transaction size. . . . . . . . . . . . . . . . . 73 5.11.7 Static Memory Output Enable Delay Registers
5.7.1.3 Write protected memory areas . . . . . . . . . . . . 73 (EMCStaticWaitOen0-1 - 0xFFE0 8208, 228) 80
5.7.2 Data buffers . . . . . . . . . . . . . . . . . . . . . . . . . . 73 5.11.8 Static Memory Read Delay Registers
5.7.2.1 Write buffers . . . . . . . . . . . . . . . . . . . . . . . . . . 73 (EMCStaticWaitRd0-1 - 0xFFE0 820C, 22C) . 81
5.7.2.2 Read buffers . . . . . . . . . . . . . . . . . . . . . . . . . . 74 5.11.9 Static Memory Page Mode Read Delay Registers
5.7.3 Memory controller state machine . . . . . . . . . . 74 (EMCStaticwaitPage0-1 - 0xFFE0 8210, 230) 81
5.7.4 Pad interface . . . . . . . . . . . . . . . . . . . . . . . . . 74 5.11.10 Static Memory Write Delay Registers
5.8 Memory bank select . . . . . . . . . . . . . . . . . . . . 74 (EMCStaticWaitwr0-1 - 0xFFE0 8214, 234) . . 82
5.11.11 Static Memory Extended Wait Register
5.9 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
(EMCStaticExtendedWait - 0xFFE0 8080). . . 82
5.10 Pin description . . . . . . . . . . . . . . . . . . . . . . . . . 75 5.11.12 Static Memory Turn Round Delay Registers
5.11 Register description . . . . . . . . . . . . . . . . . . . . 75 (EMCStaticWaitTurn0-1 - 0xFFE0 8218, 238, 258,
5.11.1 EMC Control Register (EMCControl - 278) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
0xFFE0 8000) . . . . . . . . . . . . . . . . . . . . . . . . . 76 5.12 External memory interface . . . . . . . . . . . . . . . 84

6.1 How to read this chapter . . . . . . . . . . . . . . . . . 85 6.5.6 Interrupt Select Register (VICIntSelect -
6.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 0xFFFF F00C) . . . . . . . . . . . . . . . . . . . . . . . . 89
6.3 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 6.5.7 IRQ Status Register (VICIRQStatus -
0xFFFF F000) . . . . . . . . . . . . . . . . . . . . . . . . 90
6.4 Register description . . . . . . . . . . . . . . . . . . . . 85
6.5.8 FIQ Status Register (VICFIQStatus -
6.5 VIC registers. . . . . . . . . . . . . . . . . . . . . . . . . . . 88 0xFFFF F004) . . . . . . . . . . . . . . . . . . . . . . . . 90
6.5.1 Software Interrupt Register (VICSoftInt - 6.5.9 Vector Address Registers 0-31 (VICVectAddr0-31
0xFFFF F018). . . . . . . . . . . . . . . . . . . . . . . . . 88 - 0xFFFF F100 to 17C) . . . . . . . . . . . . . . . . . 90
6.5.2 Software Interrupt Clear Register 6.5.10 Vector Priority Registers 0-31
(VICSoftIntClear - 0xFFFF F01C). . . . . . . . . . 88 (VICVectPriority0-31 - 0xFFFF F200 to 27C). 91
6.5.3 Raw Interrupt Status Register (VICRawIntr - 6.5.11 Vector Address Register (VICAddress -
0xFFFF F008). . . . . . . . . . . . . . . . . . . . . . . . . 89 0xFFFF FF00) . . . . . . . . . . . . . . . . . . . . . . . . 91
6.5.4 Interrupt Enable Register (VICIntEnable - 6.5.12 Software Priority Mask Register
0xFFFF F010). . . . . . . . . . . . . . . . . . . . . . . . . 89 (VICSWPriorityMask - 0xFFFF F024) . . . . . . 91
6.5.5 Interrupt Enable Clear Register (VICIntEnClear - 6.5.13 Protection Enable Register (VICProtection -
0xFFFF F014). . . . . . . . . . . . . . . . . . . . . . . . . 89 0xFFFF F020) . . . . . . . . . . . . . . . . . . . . . . . . 91

6.6 Interrupt sources . . . . . . . . . . . . . . . . . . . . . . . 92

7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 7.5 MAM configuration . . . . . . . . . . . . . . . . . . . . . 99
7.2 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 7.6 Register description . . . . . . . . . . . . . . . . . . . . 99
7.3 Memory Acceleration Module blocks. . . . . . . 97 7.7 MAM Control Register (MAMCR - 0xE01F
7.3.1 Flash memory bank . . . . . . . . . . . . . . . . . . . . 97 C000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7.3.2 Instruction latches and data latches . . . . . . . . 98 7.8 MAM Timing Register (MAMTIM - 0xE01F
7.3.3 Flash programming Issues . . . . . . . . . . . . . . . 98 C004) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
7.4 Memory Accelerator Module Operating 7.9 MAM usage notes . . . . . . . . . . . . . . . . . . . . . 102
modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 8.4 LPC2377/78 144-pin package . . . . . . . . . . . . 124
8.2 LPC2361/62 100-pin packages . . . . . . . . . . . 104 8.5 LPC2387 100-pin package . . . . . . . . . . . . . . 134
8.3 LPC2364/65/66/67/68 100-pin packages. . . . 113 8.6 LPC2388 144-pin package . . . . . . . . . . . . . . 142

9.1 How to read this chapter . . . . . . . . . . . . . . . . 154 9.5.8.1 100-pin packages. . . . . . . . . . . . . . . . . . . . . 163
9.2 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 9.5.8.2 144-pin packages. . . . . . . . . . . . . . . . . . . . . 164
9.3 Pin function select register values. . . . . . . . 154 9.5.9 Pin Function Select Register 8 (PINSEL8 -
0xE002 C020) . . . . . . . . . . . . . . . . . . . . . . . 164
9.4 Pin mode select register values . . . . . . . . . . 155
9.5.9.1 100-pin packages. . . . . . . . . . . . . . . . . . . . . 164
9.5 Register description . . . . . . . . . . . . . . . . . . . 155 9.5.9.2 144-pin packages. . . . . . . . . . . . . . . . . . . . . 164
Pin control module register reset values. . . . .156 9.5.10 Pin Function Select Register 9 (PINSEL9 -
9.5.1 Pin Function Select register 0 (PINSEL0 - 0xE002 C024) . . . . . . . . . . . . . . . . . . . . . . . 165
0xE002 C000). . . . . . . . . . . . . . . . . . . . . . . . 156 9.5.10.1 100-pin packages. . . . . . . . . . . . . . . . . . . . . 165
9.5.1.1 100-pin packages . . . . . . . . . . . . . . . . . . . . . 156 9.5.10.2 144-pin packages. . . . . . . . . . . . . . . . . . . . . 166
9.5.1.2 144-pin packages . . . . . . . . . . . . . . . . . . . . . 157 9.5.11 Pin Function Select Register 10 (PINSEL10 -
9.5.2 Pin Function Select Register 1 (PINSEL1 - 0xE002 C028) . . . . . . . . . . . . . . . . . . . . . . . 166
0xE002 C004). . . . . . . . . . . . . . . . . . . . . . . . 157 9.5.12 Pin Mode select register 0 (PINMODE0 -
9.5.2.1 100-pin packages . . . . . . . . . . . . . . . . . . . . . 158 0xE002 C040) . . . . . . . . . . . . . . . . . . . . . . . 166
9.5.2.2 144-pin packages . . . . . . . . . . . . . . . . . . . . . 158 9.5.13 Pin Mode select register 1 (PINMODE1 -
9.5.3 Pin Function Select register 2 (PINSEL2 - 0xE002 C044) . . . . . . . . . . . . . . . . . . . . . . . 167
0xE002 C008). . . . . . . . . . . . . . . . . . . . . . . . 159 9.5.14 Pin Mode select register 2 (PINMODE2 -
9.5.3.1 100-pin packages and 144-pin packages . . . 159 0xE002 C048) . . . . . . . . . . . . . . . . . . . . . . . 167
9.5.4 Pin Function Select Register 3 (PINSEL3 - 9.5.15 Pin Mode select register 3 (PINMODE3 -
0xE002 C00C) . . . . . . . . . . . . . . . . . . . . . . . 159 0xE002 C04C) . . . . . . . . . . . . . . . . . . . . . . . 167
9.5.4.2 144-pin packages . . . . . . . . . . . . . . . . . . . . . 160 0xE002 C050) . . . . . . . . . . . . . . . . . . . . . . . 168
0xE002 C010). . . . . . . . . . . . . . . . . . . . . . . . 161 0xE002 C054) . . . . . . . . . . . . . . . . . . . . . . . 168
9.5.5.2 144-pin packages . . . . . . . . . . . . . . . . . . . . . 162 0xE002 C058) . . . . . . . . . . . . . . . . . . . . . . . 168
0xE002 C014). . . . . . . . . . . . . . . . . . . . . . . . 162 0xE002 C05C) . . . . . . . . . . . . . . . . . . . . . . . 168
0xE002 C018). . . . . . . . . . . . . . . . . . . . . . . . 162 0xE002 C060) . . . . . . . . . . . . . . . . . . . . . . . 169
9.5.7.2 144-pin packages . . . . . . . . . . . . . . . . . . . . . 162 0xE002 C064) . . . . . . . . . . . . . . . . . . . . . . . 169
9.5.8 Pin Function Select Register 7 (PINSEL7 -
0xE002 C01C) . . . . . . . . . . . . . . . . . . . . . . . 163

10.1 Basic configuration . . . . . . . . . . . . . . . . . . . . 170 10.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

10.2.1 Digital I/O ports . . . . . . . . . . . . . . . . . . . . . . . 170 10.5.6.2 GPIO Interrupt Enable for Rising edge register
10.2.2 Interrupt generating digital ports . . . . . . . . . . 170 (IO0IntEnR - 0xE002 8090 and IO2IntEnR -
10.3 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 171 0xE002 80B0) . . . . . . . . . . . . . . . . . . . . . . . 182
10.4 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 171 10.5.6.3 GPIO Interrupt Enable for Falling edge register
(IO0IntEnF - 0xE002 8094 and IO2IntEnF -
10.5 Register description . . . . . . . . . . . . . . . . . . . 171
0xE002 80B4) . . . . . . . . . . . . . . . . . . . . . . . 182
10.5.1 GPIO port Direction register IODIR and 10.5.6.4 GPIO Interrupt Status for Rising edge register
FIODIR(IO[0/1]DIR - 0xE002 80[0/1]8 and (IO0IntStatR - 0xE002 8084 and IO2IntStatR -
FIO[0/1/2/3/4]DIR - 0x3FFF C0[0/2/4/6/8]0) . 173 0xE002 80A4) . . . . . . . . . . . . . . . . . . . . . . . 183
10.5.2 GPIO port output Set register IOSET and 10.5.6.5 GPIO Interrupt Status for Falling edge register
FIOSET(IO[0/1]SET - 0xE002 80[0/1]4 and (IO0IntStatF - 0xE002 8088 and IO2IntStatF -
FIO[0/1/2/3/4]SET - 0x3FFF C0[1/3/5/7/9]8) 175 0xE002 80A8) . . . . . . . . . . . . . . . . . . . . . . . 183
10.5.3 GPIO port output Clear register IOCLR and 10.5.6.6 GPIO Interrupt Clear register (IO0IntClr -
FIOCLR (IO[0/1]CLR - 0xE002 80[0/1]C and 0xE002 808C and IO2IntClr - 0xE002 80AC) 183
FIO[0/1/2/3/4]CLR - 0x3FFF C0[1/3/5/7/9]C) 177
10.6 GPIO usage notes . . . . . . . . . . . . . . . . . . . . . 184
10.5.4 GPIO port Pin value register IOPIN and FIOPIN
(IO[0/1]PIN - 0xE002 80[0/1]0 and 10.6.1 Example 1: sequential accesses to IOSET and
FIO[0/1/2/3/4]PIN - 0x3FFF C0[1/3/5/7/9]4) . 178 IOCLR affecting the same GPIO pin/bit . . . . 184
10.5.5 Fast GPIO port Mask register 10.6.2 Example 2: an instantaneous output of 0s and 1s
FIOMASK(FIO[0/1/2/3/4]MASK - on a GPIO port. . . . . . . . . . . . . . . . . . . . . . . 184
0x3FFF C0[1/3/5/7/9]0) . . . . . . . . . . . . . . . . 180 10.6.3 Writing to IOSET/IOCLR vs. IOPIN . . . . . . . 185
10.5.6 GPIO interrupt registers . . . . . . . . . . . . . . . . 182 10.6.4 Output signal frequency considerations when
10.5.6.1 GPIO overall Interrupt Status register (IOIntStatus using the legacy and enhanced GPIO registers .
- 0xE002 8080) . . . . . . . . . . . . . . . . . . . . . . . 182 185

11.1 How to read this chapter . . . . . . . . . . . . . . . . 186 11.12.9 MII Mgmt Configuration Register (MCFG -
11.2 Basic configuration . . . . . . . . . . . . . . . . . . . . 186 0xFFE0 0020) . . . . . . . . . . . . . . . . . . . . . . . 200
11.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 186 11.12.10 MII Mgmt Command Register (MCMD -
0xFFE0 0024) . . . . . . . . . . . . . . . . . . . . . . . 201
11.4 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
11.12.11 MII Mgmt Address Register (MADR -
11.5 Architecture and operation . . . . . . . . . . . . . . 188 0xFFE0 0028) . . . . . . . . . . . . . . . . . . . . . . . 201
11.6 DMA engine functions . . . . . . . . . . . . . . . . . . 189 11.12.12 MII Mgmt Write Data Register (MWTD -
11.7 Overview of DMA operation . . . . . . . . . . . . . 189 0xFFE0 002C) . . . . . . . . . . . . . . . . . . . . . . . 202
11.8 Ethernet Packet . . . . . . . . . . . . . . . . . . . . . . . 190 11.12.13 MII Mgmt Read Data Register (MRDD -
0xFFE0 0030) . . . . . . . . . . . . . . . . . . . . . . . 202
11.9 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
11.12.14 MII Mgmt Indicators Register (MIND -
11.9.1 Partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . 191
0xFFE0 0034) . . . . . . . . . . . . . . . . . . . . . . . 202
11.9.2 Example PHY Devices . . . . . . . . . . . . . . . . . 192
11.12.15 Station Address 0 Register (SA0 - 0xFFE0
11.10 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 193 0040) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
11.11 Registers and software interface . . . . . . . . . 193 11.12.16 Station Address 1 Register (SA1 - 0xFFE0
11.11.1 Register map . . . . . . . . . . . . . . . . . . . . . . . . 194 0044) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
11.12 Ethernet MAC register definitions . . . . . . . . 196 11.12.17 Station Address 2 Register (SA2 - 0xFFE0
11.12.1 MAC Configuration Register 1 (MAC1 - 0048) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
0xFFE0 0000) . . . . . . . . . . . . . . . . . . . . . . . . 196 11.13 Control register definitions . . . . . . . . . . . . . 204
11.12.2 MAC Configuration Register 2 (MAC2 - 11.13.1 Command Register (Command - 0xFFE0
0xFFE0 0004) . . . . . . . . . . . . . . . . . . . . . . . . 197 0100) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
11.12.3 Back-to-Back Inter-Packet-Gap Register (IPGT - 11.13.2 Status Register (Status - 0xFFE0 0104) . . . 204
0xFFE0 0008) . . . . . . . . . . . . . . . . . . . . . . . . 198 11.13.3 Receive Descriptor Base Address Register
11.12.4 Non Back-to-Back Inter-Packet-Gap Register (RxDescriptor - 0xFFE0 0108) . . . . . . . . . . . 205
(IPGR - 0xFFE0 000C) . . . . . . . . . . . . . . . . . 198 11.13.4 Receive Status Base Address Register (RxStatus
11.12.5 Collision Window / Retry Register (CLRT - - 0xFFE0 010C) . . . . . . . . . . . . . . . . . . . . . . 205
0xFFE0 0010) . . . . . . . . . . . . . . . . . . . . . . . . 199 11.13.5 Receive Number of Descriptors Register
11.12.6 Maximum Frame Register (MAXF - 0xFFE0 (RxDescriptor - 0xFFE0 0110) . . . . . . . . . . . 206
0014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 11.13.6 Receive Produce Index Register
11.12.7 PHY Support Register (SUPP - 0xFFE0 (RxProduceIndex - 0xFFE0 0114) . . . . . . . . 206
0018) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 11.13.7 Receive Consume Index Register
11.12.8 Test Register (TEST - 0xFFE0 001C). . . . . . 200 (RxConsumeIndex - 0xFFE0 0118) . . . . . . . 206

11.13.8 Transmit Descriptor Base Address Register 11.15.3 Interrupt Clear Register (IntClear - 0xFFE0
(TxDescriptor - 0xFFE0 011C) . . . . . . . . . . . 207 0FE8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
11.13.9 Transmit Status Base Address Register (TxStatus 11.15.4 Interrupt Set Register (IntSet - 0xFFE0
- 0xFFE0 0120). . . . . . . . . . . . . . . . . . . . . . . 207 0FEC). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
11.13.10 Transmit Number of Descriptors Register 11.15.5 Power Down Register (PowerDown -
(TxDescriptorNumber - 0xFFE0 0124) . . . . . 208 0xFFE0 0FF4) . . . . . . . . . . . . . . . . . . . . . . . 217
11.13.11 Transmit Produce Index Register 11.16 Descriptor and status formats . . . . . . . . . . . 218
(TxProduceIndex - 0xFFE0 0128) . . . . . . . . 208 11.16.1 Receive descriptors and statuses . . . . . . . . 218
11.13.12 Transmit Consume Index Register 11.16.2 Transmit descriptors and statuses . . . . . . . . 221
(TxConsumeIndex - 0xFFE0 012C) . . . . . . . 208
11.17 Ethernet block functional description. . . . . 223
11.13.13 Transmit Status Vector 0 Register (TSV0 -
11.17.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
0xFFE0 0158) . . . . . . . . . . . . . . . . . . . . . . . . 209
11.17.2 AHB interface. . . . . . . . . . . . . . . . . . . . . . . . 224
11.13.14 Transmit Status Vector 1 Register (TSV1 -
0xFFE0 015C) . . . . . . . . . . . . . . . . . . . . . . . 210 11.18 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
11.13.15 Receive Status Vector Register (RSV - 11.18.1 Direct Memory Access (DMA) . . . . . . . . . . . 224
0xFFE0 0160) . . . . . . . . . . . . . . . . . . . . . . . . 210 11.18.2 Initialization . . . . . . . . . . . . . . . . . . . . . . . . . 227
11.13.16 Flow Control Counter Register 11.18.3 Transmit process . . . . . . . . . . . . . . . . . . . . . 228
(FlowControlCounter - 0xFFE0 0170). . . . . . 211 11.18.4 Receive process . . . . . . . . . . . . . . . . . . . . . 235
11.13.17 Flow Control Status Register (FlowControlStatus - 11.18.5 Transmission retry . . . . . . . . . . . . . . . . . . . . 241
0xFFE0 0174) . . . . . . . . . . . . . . . . . . . . . . . . 212 11.18.6 Status hash CRC calculations . . . . . . . . . . . 241
11.14 Receive filter register definitions . . . . . . . . . 212 11.18.7 Duplex modes . . . . . . . . . . . . . . . . . . . . . . . 242
11.18.8 IEE 802.3/Clause 31 flow control. . . . . . . . . 242
11.14.1 Receive Filter Control Register (RxFilterCtrl -
11.18.9 Half-Duplex mode backpressure . . . . . . . . . 244
0xFFE0 0200) . . . . . . . . . . . . . . . . . . . . . . . . 212
11.18.10 Receive filtering . . . . . . . . . . . . . . . . . . . . . . 245
11.14.2 Receive Filter WoL Status Register
11.18.11 Power management. . . . . . . . . . . . . . . . . . . 247
(RxFilterWoLStatus - 0xFFE0 0204). . . . . . . 213
11.18.12 Wake-up on LAN . . . . . . . . . . . . . . . . . . . . . 247
11.14.3 Receive Filter WoL Clear Register
11.18.13 Enabling and disabling receive and transmit 249
(RxFilterWoLClear - 0xFFE0 0208) . . . . . . . 213
11.18.14 Transmission padding and CRC . . . . . . . . . 251
11.14.4 Hash Filter Table LSBs Register (HashFilterL -
11.18.15 Huge frames and frame length checking . . . 252
0xFFE0 0210) . . . . . . . . . . . . . . . . . . . . . . . . 214
11.18.16 Statistics counters . . . . . . . . . . . . . . . . . . . . 252
11.14.5 Hash Filter Table MSBs Register (HashFilterH -
11.18.17 MAC status vectors . . . . . . . . . . . . . . . . . . . 252
0xFFE0 0214) . . . . . . . . . . . . . . . . . . . . . . . . 214
11.18.18 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
11.15 Module control register definitions . . . . . . . 215 11.18.19 Ethernet errors . . . . . . . . . . . . . . . . . . . . . . . 254
11.15.1 Interrupt Status Register (IntStatus -
11.19 AHB bandwidth . . . . . . . . . . . . . . . . . . . . . . . 254
0xFFE0 0FE0) . . . . . . . . . . . . . . . . . . . . . . . 215
11.19.1 DMA access. . . . . . . . . . . . . . . . . . . . . . . . . 254
11.15.2 Interrupt Enable Register (IntEnable -
11.19.2 Types of CPU access. . . . . . . . . . . . . . . . . . 256
0xFFE0 0FE4) . . . . . . . . . . . . . . . . . . . . . . . 215
11.19.3 Overall bandwidth . . . . . . . . . . . . . . . . . . . . 256
11.20 CRC calculation. . . . . . . . . . . . . . . . . . . . . . . 256

12.1 How to read this chapter . . . . . . . . . . . . . . . . 259 12.6.8 CAN controller self-tests . . . . . . . . . . . . . . . 264
12.2 Basic configuration . . . . . . . . . . . . . . . . . . . . 259 Global self test . . . . . . . . . . . . . . . . . . . . . . . . 264
12.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 259 Local self test . . . . . . . . . . . . . . . . . . . . . . . . . 264
12.4 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260 12.7 Memory map of the CAN block . . . . . . . . . . 265
12.4.1 General CAN features . . . . . . . . . . . . . . . . . 260 12.8 CAN controller registers. . . . . . . . . . . . . . . . 265
12.4.2 CAN controller features . . . . . . . . . . . . . . . . 260 12.8.1 Mode Register (CAN1MOD - 0xE004 4000,
12.4.3 Acceptance filter features . . . . . . . . . . . . . . . 260 CAN2MOD - 0xE004 8000) . . . . . . . . . . . . . 267
12.5 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 261 12.8.2 Command Register (CAN1CMR - 0xE004 x004,
CAN2CMR - 0xE004 8004) . . . . . . . . . . . . . 269
12.6 CAN controller architecture . . . . . . . . . . . . . 261
12.8.3 Global Status Register (CAN1GSR -
12.6.1 APB interface block (AIB) . . . . . . . . . . . . . . . 261 0xE004 x008, CAN2GSR - 0xE004 8008) . . 270
12.6.2 Interface management logic (IML) . . . . . . . . 262 RX error counter . . . . . . . . . . . . . . . . . . . . . . 272
12.6.3 Transmit Buffers (TXB) . . . . . . . . . . . . . . . . . 262 TX error counter. . . . . . . . . . . . . . . . . . . . . . . 272
12.6.4 Receive Buffer (RXB) . . . . . . . . . . . . . . . . . 262 12.8.4 Interrupt and Capture Register (CAN1ICR -
12.6.5 Error Management Logic (EML) . . . . . . . . . 263 0xE004 400C, CAN2ICR - 0xE004 800C) . . 273
12.6.6 Bit Timing Logic (BTL) . . . . . . . . . . . . . . . . . 263 12.8.5 Interrupt Enable Register (CAN1IER -
12.6.7 Bit Stream Processor (BSP) . . . . . . . . . . . . . 263 0xE004 4010, CAN2IER - 0xE004 8010). . . 276

12.8.6 Bus Timing Register (CAN1BTR - 0xE004 4014, 12.15.1 Acceptance Filter Mode Register (AFMR -
CAN2BTR - 0xE004 8014) . . . . . . . . . . . . . . 277 0xE003 C000) . . . . . . . . . . . . . . . . . . . . . . . 293
Baud rate prescaler . . . . . . . . . . . . . . . . . . . .278 12.15.2 Section configuration registers. . . . . . . . . . . 294
Synchronization jump width . . . . . . . . . . . . . .278 12.15.3 Standard Frame Individual Start Address Register
Time segment 1 and time segment 2 . . . . . . .278 (SFF_sa - 0xE003 C004) . . . . . . . . . . . . . . . 294
12.8.7 Error Warning Limit Register (CAN1EWL - 12.15.4 Standard Frame Group Start Address Register
0xE004 4018, CAN2EWL - 0xE004 8018) . . 279 (SFF_GRP_sa - 0xE003 C008) . . . . . . . . . . 295
12.8.8 Status Register (CAN1SR - 0xE004 401C, 12.15.5 Extended Frame Start Address Register (EFF_sa
CAN2SR - 0xE004 801C) . . . . . . . . . . . . . . . 279 - 0xE003 C00C) . . . . . . . . . . . . . . . . . . . . . . 295
12.8.9 Receive Frame Status Register (CAN1RFS - 12.15.6 Extended Frame Group Start Address Register
0xE004 4020, CAN2RFS - 0xE004 8020) . . 281 (EFF_GRP_sa - 0xE003 C010) . . . . . . . . . . 296
12.8.9.1 ID index field . . . . . . . . . . . . . . . . . . . . . . . . . 282 12.15.7 End of AF Tables Register (ENDofTable -
12.8.10 Receive Identifier Register (CAN1RID - 0xE003 C014) . . . . . . . . . . . . . . . . . . . . . . . 296
0xE004 4024, CAN2RID - 0xE004 8024) . . . 282 12.15.8 Status registers . . . . . . . . . . . . . . . . . . . . . . 296
12.8.11 Receive Data Register A (CAN1RDA - 12.15.9 LUT Error Address Register (LUTerrAd -
0xE004 4028, CAN2RDA - 0xE004 8028) . . 282 0xE003 C018) . . . . . . . . . . . . . . . . . . . . . . . 297
12.8.12 Receive Data Register B (CAN1RDB - 12.15.10 LUT Error Register (LUTerr - 0xE003 C01C) 297
0xE004 402C, CAN2RDB - 0xE004 802C). . 283 12.15.11 Global FullCANInterrupt Enable register (FCANIE
12.8.13 Transmit Frame Information Register - 0xE003 C020) . . . . . . . . . . . . . . . . . . . . . . 297
(CAN1TFI[1/2/3] - 0xE004 40[30/ 40/50], 12.15.12 FullCAN Interrupt and Capture registers
CAN2TFI[1/2/3] - 0xE004 80[30/40/50]) . . . . 283 (FCANIC0 - 0xE003 C024 and FCANIC1 -
Automatic transmit priority detection. . . . . . . .284 0xE003 C028) . . . . . . . . . . . . . . . . . . . . . . . 297
Tx DLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284 12.16 Configuration and search algorithm . . . . . . 298
12.8.14 Transmit Identifier Register (CAN1TID[1/2/3] - 12.16.1 Acceptance filter search algorithm . . . . . . . . 298
0xE004 40[34/44/54], CAN2TID[1/2/3] -
12.17 FullCAN mode . . . . . . . . . . . . . . . . . . . . . . . . 299
0xE004 80[34/44/54]) . . . . . . . . . . . . . . . . . . 285
12.17.1 FullCAN message layout . . . . . . . . . . . . . . . 301
12.8.15 Transmit Data Register A (CAN1TDA[1/2/3] -
12.17.2 FullCAN interrupts . . . . . . . . . . . . . . . . . . . . 303
0xE004 40[38/48/58], CAN2TDA[1/2/3] -
12.17.2.1 FullCAN message interrupt enable bit . . . . . 303
0xE004 80[38/48/58]) . . . . . . . . . . . . . . . . . . 285
12.17.2.2 Message lost bit and CAN channel number. 304
12.8.16 Transmit Data Register B (CAN1TDB[1/2/3] -
12.17.2.3 Setting the interrupt pending bits (IntPnd
0xE004 40[3C/4C/5C], CAN2TDB[1/2/3] -
63 to 0). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
0xE004 80[3C/4C/5C]) . . . . . . . . . . . . . . . . . 286
12.17.2.4 Clearing the interrupt pending bits (IntPnd
12.8.17 CAN Sleep Clear register (CANSLEEPCLR -
63 to 0). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
0x400F C110) . . . . . . . . . . . . . . . . . . . . . . . . 286
12.17.2.5 Setting the message lost bit of a FullCAN
12.8.18 CAN Wake-up Flags register (CANWAKEFLAGS
message object (MsgLost 63 to 0). . . . . . . . 305
- 0x400F C114) . . . . . . . . . . . . . . . . . . . . . . . 286
12.17.2.6 Clearing the message lost bit of a FullCAN
12.9 CAN controller operation . . . . . . . . . . . . . . . 287 message object (MsgLost 63 to 0). . . . . . . . 305
12.9.1 Error handling . . . . . . . . . . . . . . . . . . . . . . . . 287 12.17.3 Set and clear mechanism of the FullCAN
12.9.2 Sleep mode . . . . . . . . . . . . . . . . . . . . . . . . . 287 interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
12.9.3 Interrupts. . . . . . . . . . . . . . . . . . . . . . . . . . . . 288 12.17.3.1 Scenario 1: Normal case, no message lost . 305
12.9.4 Transmit priority . . . . . . . . . . . . . . . . . . . . . . 288 12.17.3.2 Scenario 2: Message lost. . . . . . . . . . . . . . . 306
12.10 Centralized CAN registers. . . . . . . . . . . . . . . 288 12.17.3.3 Scenario 3: Message gets overwritten indicated
12.10.1 Central Transmit Status Register (CANTxSR - by Semaphore bits . . . . . . . . . . . . . . . . . . . . 307
0xE004 0000) . . . . . . . . . . . . . . . . . . . . . . . . 288 12.17.3.4 Scenario 3.1: Message gets overwritten indicated
12.10.2 Central Receive Status Register (CANRxSR - by Semaphore bits and Message Lost. . . . . 307
0xE004 0004) . . . . . . . . . . . . . . . . . . . . . . . . 289 12.17.3.5 Scenario 3.2: Message gets overwritten indicated
12.10.3 Central Miscellaneous Status Register (CANMSR by Message Lost . . . . . . . . . . . . . . . . . . . . . 308
- 0xE004 0008) . . . . . . . . . . . . . . . . . . . . . . . 289 12.17.3.6 Scenario 4: Clearing Message Lost bit . . . . 309
12.11 Global acceptance filter . . . . . . . . . . . . . . . . 289 12.18 Examples of acceptance filter tables and ID
12.12 Acceptance filter modes . . . . . . . . . . . . . . . . 290 index values. . . . . . . . . . . . . . . . . . . . . . . . . . 310
12.12.1 Acceptance filter Off mode . . . . . . . . . . . . . . 290 12.18.1 Example 1: only one section is used . . . . . . 310
12.12.2 Acceptance filter Bypass mode . . . . . . . . . . 290 12.18.2 Example 2: all sections are used . . . . . . . . . 310
12.12.3 Acceptance filter Operating mode . . . . . . . . 290 12.18.3 Example 3: more than one but not all sections are
12.12.4 FullCAN mode . . . . . . . . . . . . . . . . . . . . . . . 291 used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
12.13 Sections of the ID look-up table RAM . . . . . 291 12.18.4 Configuration example 4 . . . . . . . . . . . . . . . . 311
12.18.5 Configuration example 5 . . . . . . . . . . . . . . . . 311
12.14 ID look-up table RAM. . . . . . . . . . . . . . . . . . . 291
12.18.6 Configuration example 6 . . . . . . . . . . . . . . . 312
12.15 Acceptance filter registers . . . . . . . . . . . . . . 293 Explicit standard frame format identifier section

(11-bit CAN ID): . . . . . . . . . . . . . . . . . . . . . . .313 12.18.7 Configuration example 7 . . . . . . . . . . . . . . . 314

Group of standard frame format identifier section FullCAN explicit standard frame format identifier
(11-bit CAN ID): . . . . . . . . . . . . . . . . . . . . . . .313 section (11-bit CAN ID) . . . . . . . . . . . . . . . . . 315
Explicit extended frame format identifier section Explicit standard frame format identifier section
(29-bit CAN ID, Figure 60) . . . . . . . . . . . . . . .313 (11-bit CAN ID) . . . . . . . . . . . . . . . . . . . . . . . 315
Group of extended frame format identifier section FullCAN message object data section . . . . . . 315
(29-bit CAN ID, Figure 60) . . . . . . . . . . . . . . .313 12.18.8 Look-up table programming guidelines . . . . 316

13.1 How to read this chapter . . . . . . . . . . . . . . . . 318 13.10.4.1 USB Endpoint Interrupt Status register
13.2 Basic configuration . . . . . . . . . . . . . . . . . . . . 318 (USBEpIntSt - 0xFFE0 C230) . . . . . . . . . . . 332
13.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 318 13.10.4.2 USB Endpoint Interrupt Enable register
(USBEpIntEn - 0xFFE0 C234) . . . . . . . . . . 333
13.4 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
13.10.4.3 USB Endpoint Interrupt Clear register
13.5 Fixed endpoint configuration . . . . . . . . . . . . 320 (USBEpIntClr - 0xFFE0 C238) . . . . . . . . . . 334
13.6 Functional description . . . . . . . . . . . . . . . . . 321 13.10.4.4 USB Endpoint Interrupt Set register (USBEpIntSet
13.6.1 Analog transceiver . . . . . . . . . . . . . . . . . . . . 321 - 0xFFE0 C23C) . . . . . . . . . . . . . . . . . . . . . 335
13.6.2 Serial Interface Engine (SIE) . . . . . . . . . . . . 321 13.10.4.5 USB Endpoint Interrupt Priority register
13.6.3 Endpoint RAM (EP_RAM) . . . . . . . . . . . . . . 321 (USBEpIntPri - 0xFFE0 C240) . . . . . . . . . . 335
13.6.4 EP_RAM access control . . . . . . . . . . . . . . . . 321 13.10.5 Endpoint realization registers. . . . . . . . . . . . 336
13.6.5 DMA engine and bus master interface . . . . . 322 13.10.5.1 EP RAM requirements . . . . . . . . . . . . . . . . . 336
13.6.6 Register interface . . . . . . . . . . . . . . . . . . . . . 322 13.10.5.2 USB Realize Endpoint register (USBReEp -
13.6.7 SoftConnect . . . . . . . . . . . . . . . . . . . . . . . . . 322 0xFFE0 C244). . . . . . . . . . . . . . . . . . . . . . . 337
13.6.8 GoodLink . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 13.10.5.3 USB Endpoint Index register (USBEpIn - 0xFFE0
13.7 Operational overview . . . . . . . . . . . . . . . . . . 322 C248) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
13.8 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 323 13.10.5.4 USB MaxPacketSize register (USBMaxPSize -
0xFFE0 C24C) . . . . . . . . . . . . . . . . . . . . . . 338
13.8.1 LPC2378 usage note . . . . . . . . . . . . . . . . . . 323
13.10.6 USB transfer registers . . . . . . . . . . . . . . . . . 339
13.8.2 LPC2388 usage note . . . . . . . . . . . . . . . . . . 323
13.10.6.1 USB Receive Data register (USBRxData -
13.9 Clocking and power management . . . . . . . . 324 0xFFE0 C218). . . . . . . . . . . . . . . . . . . . . . . 339
13.9.1 Power requirements . . . . . . . . . . . . . . . . . . . 324 13.10.6.2 USB Receive Packet Length register
13.9.2 Clocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324 (USBRxPLen - 0xFFE0 C220) . . . . . . . . . . 339
13.9.3 Power management support . . . . . . . . . . . . 324 13.10.6.3 USB Transmit Data register (USBTxData -
13.9.4 Remote wake-up . . . . . . . . . . . . . . . . . . . . . 325 0xFFE0 C21C) . . . . . . . . . . . . . . . . . . . . . . 339
13.10 Register description . . . . . . . . . . . . . . . . . . . 325 13.10.6.4 USB Transmit Packet Length register
13.10.1 Port select register . . . . . . . . . . . . . . . . . . . . 327 (USBTxPLen - 0xFFE0 C224) . . . . . . . . . . 340
13.10.1.1 USB Port Select register (USBPortSel - 0xFFE0 13.10.6.5 USB Control register (USBCtrl - 0xFFE0
C110 – LPC2378 only) . . . . . . . . . . . . . . . . . 327 C228) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
13.10.2 Clock control registers . . . . . . . . . . . . . . . . . 327 13.10.7 SIE command code registers. . . . . . . . . . . . 341
13.10.2.1 USB Clock Control register (USBClkCtrl - 13.10.7.1 USB Command Code register (USBCmdCode -
0xFFE0 CFF4) . . . . . . . . . . . . . . . . . . . . . . . 327 0xFFE0 C210). . . . . . . . . . . . . . . . . . . . . . . 341
13.10.2.2 USB Clock Status register (USBClkSt - 0xFFE0 13.10.7.2 USB Command Data register (USBCmdData -
CFF8) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 0xFFE0 C214). . . . . . . . . . . . . . . . . . . . . . . 341
13.10.3 Device interrupt registers . . . . . . . . . . . . . . . 328 13.10.8 DMA registers . . . . . . . . . . . . . . . . . . . . . . . 342
13.10.3.1 USB Interrupt Status register (USBIntSt - 13.10.8.1 USB DMA Request Status register (USBDMARSt
0xE01F C1C0) . . . . . . . . . . . . . . . . . . . . . . . 328 - 0xFFE0 C250) . . . . . . . . . . . . . . . . . . . . . 342
13.10.3.2 USB Device Interrupt Status register 13.10.8.2 USB DMA Request Clear register (USBDMARClr
(USBDevIntSt - 0xFFE0 C200) . . . . . . . . . . 329 - 0xFFE0 C254) . . . . . . . . . . . . . . . . . . . . . 342
13.10.3.3 USB Device Interrupt Enable register 13.10.8.3 USB DMA Request Set register (USBDMARSet -
(USBDevIntEn - 0xFFE0 C204). . . . . . . . . . 330 0xFFE0 C258). . . . . . . . . . . . . . . . . . . . . . . 343
13.10.3.4 USB Device Interrupt Clear register 13.10.8.4 USB UDCA Head register (USBUDCAH - 0xFFE0
(USBDevIntClr - 0xFFE0 C208). . . . . . . . . . 330 C280) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
13.10.3.5 USB Device Interrupt Set register (USBDevIntSet 13.10.8.5 USB EP DMA Status register (USBEpDMASt -
- 0xFFE0 C20C) . . . . . . . . . . . . . . . . . . . . . 331 0xFFE0 C284). . . . . . . . . . . . . . . . . . . . . . . 344
13.10.3.6 USB Device Interrupt Priority register 13.10.8.6 USB EP DMA Enable register (USBEpDMAEn -
(USBDevIntPri - 0xFFE0 C22C) . . . . . . . . . 332 0xFFE0 C288). . . . . . . . . . . . . . . . . . . . . . . 344
13.10.4 Endpoint interrupt registers. . . . . . . . . . . . . . 332 13.10.8.7 USB EP DMA Disable register (USBEpDMADis -
0xFFE0 C28C) . . . . . . . . . . . . . . . . . . . . . . 345

13.10.8.8 USB DMA Interrupt Status register (USBDMAIntSt 13.14.1 Interrupt generation . . . . . . . . . . . . . . . . . . . 362
- 0xFFE0 C290) . . . . . . . . . . . . . . . . . . . . . . 345 13.14.2 Data transfer for OUT endpoints . . . . . . . . . 362
13.10.8.9 USB DMA Interrupt Enable register 13.14.3 Data transfer for IN endpoints . . . . . . . . . . . 363
(USBDMAIntEn - 0xFFE0 C294) . . . . . . . . . 345 13.15 DMA operation. . . . . . . . . . . . . . . . . . . . . . . . 363
13.10.8.10 USB End of Transfer Interrupt Status register 13.15.1 Transfer terminology . . . . . . . . . . . . . . . . . . 363
(USBEoTIntSt - 0xFFE0 C2A0) . . . . . . . . . . 346 13.15.2 USB device communication area. . . . . . . . . 364
13.10.8.11 USB End of Transfer Interrupt Clear register 13.15.3 Triggering the DMA engine . . . . . . . . . . . . . 364
(USBEoTIntClr - 0xFFE0 C2A4) . . . . . . . . . 346 13.15.4 The DMA descriptor . . . . . . . . . . . . . . . . . . . 365
13.10.8.12 USB End of Transfer Interrupt Set register 13.15.4.1 Next_DD_pointer . . . . . . . . . . . . . . . . . . . . . 366
(USBEoTIntSet - 0xFFE0 C2A8) . . . . . . . . . 347 13.15.4.2 DMA_mode . . . . . . . . . . . . . . . . . . . . . . . . . 366
13.10.8.13 USB New DD Request Interrupt Status register 13.15.4.3 Next_DD_valid . . . . . . . . . . . . . . . . . . . . . . . 366
(USBNDDRIntSt - 0xFFE0 C2AC) . . . . . . . . 347 13.15.4.4 Isochronous_endpoint . . . . . . . . . . . . . . . . . 366
13.10.8.14 USB New DD Request Interrupt Clear register 13.15.4.5 Max_packet_size . . . . . . . . . . . . . . . . . . . . . 366
(USBNDDRIntClr - 0xFFE0 C2B0) . . . . . . . 347 13.15.4.6 DMA_buffer_length . . . . . . . . . . . . . . . . . . . 367
13.10.8.15 USB New DD Request Interrupt Set register 13.15.4.7 DMA_buffer_start_addr . . . . . . . . . . . . . . . . 367
(USBNDDRIntSet - 0xFFE0 C2B4) . . . . . . . 347 13.15.4.8 DD_retired . . . . . . . . . . . . . . . . . . . . . . . . . . 367
13.10.8.16 USB System Error Interrupt Status register 13.15.4.9 DD_status . . . . . . . . . . . . . . . . . . . . . . . . . . 367
(USBSysErrIntSt - 0xFFE0 C2B8) . . . . . . . . 348 13.15.4.10 Packet_valid . . . . . . . . . . . . . . . . . . . . . . . . 367
13.10.8.17 USB System Error Interrupt Clear register 13.15.4.11 LS_byte_extracted . . . . . . . . . . . . . . . . . . . 368
(USBSysErrIntClr - 0xFFE0 C2BC) . . . . . . . 348 13.15.4.12 MS_byte_extracted. . . . . . . . . . . . . . . . . . . 368
13.10.8.18 USB System Error Interrupt Set register 13.15.4.13 Present_DMA_count. . . . . . . . . . . . . . . . . . 368
(USBSysErrIntSet - 0xFFE0 C2C0). . . . . . . 348 13.15.4.14 Message_length_position . . . . . . . . . . . . . . 368
13.11 Interrupt handling . . . . . . . . . . . . . . . . . . . . . 349 13.15.4.15 Isochronous_packetsize_memory_address 368
Slave mode. . . . . . . . . . . . . . . . . . . . . . . . . . .349 13.15.5 Non-isochronous endpoint operation . . . . . . 368
DMA mode . . . . . . . . . . . . . . . . . . . . . . . . . . .349 13.15.5.1 Setting up DMA transfers. . . . . . . . . . . . . . . 368
13.12 Serial interface engine command 13.15.5.2 Finding DMA Descriptor. . . . . . . . . . . . . . . . 368
description . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 13.15.5.3 Transferring the data . . . . . . . . . . . . . . . . . . 369
13.12.1 Set Address (Command: 0xD0, Data: write 13.15.5.4 Optimizing descriptor fetch . . . . . . . . . . . . . 369
1 byte). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 13.15.5.5 Ending the packet transfer . . . . . . . . . . . . . . 369
13.12.2 Configure Device (Command: 0xD8, Data: write 1 13.15.5.6 No_Packet DD . . . . . . . . . . . . . . . . . . . . . . . 370
byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 13.15.6 Isochronous endpoint operation. . . . . . . . . . 370
13.12.3 Set Mode (Command: 0xF3, Data: write 13.15.6.1 Setting up DMA transfers. . . . . . . . . . . . . . . 370
1 byte). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354 13.15.6.2 Finding the DMA Descriptor. . . . . . . . . . . . . 370
13.12.4 Read Current Frame Number (Command: 0xF5, 13.15.6.3 Transferring the Data . . . . . . . . . . . . . . . . . . 370
Data: read 1 or 2 bytes) . . . . . . . . . . . . . . . . 355 OUT endpoints. . . . . . . . . . . . . . . . . . . . . . . . 371
13.12.5 Read Test Register (Command: 0xFD, Data: read IN endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . 371
2 bytes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 13.15.6.4 DMA descriptor completion . . . . . . . . . . . . . 371
13.12.6 Set Device Status (Command: 0xFE, Data: write 1 13.15.6.5 Isochronous OUT Endpoint Operation
byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
13.12.7 Get Device Status (Command: 0xFE, Data: read 1 13.15.7 Auto Length Transfer Extraction (ATLE) mode
byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
13.12.8 Get Error Code (Command: 0xFF, Data: read 1 OUT transfers in ATLE mode. . . . . . . . . . . . . 372
byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356 IN transfers in ATLE mode. . . . . . . . . . . . . . . 374
13.12.9 Read Error Status (Command: 0xFB, Data: read 1 13.15.7.1 Setting up the DMA transfer. . . . . . . . . . . . . 374
byte) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 13.15.7.2 Finding the DMA Descriptor. . . . . . . . . . . . . 374
13.12.10 Select Endpoint (Command: 0x00 - 0x1F, Data: 13.15.7.3 Transferring the Data . . . . . . . . . . . . . . . . . . 374
read 1 byte (optional)) . . . . . . . . . . . . . . . . . 358 OUT endpoints. . . . . . . . . . . . . . . . . . . . . . . . 374
13.12.11 Select Endpoint/Clear Interrupt (Command: IN endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . 374
0x40 - 0x5F, Data: read 1 byte) . . . . . . . . . . 359 13.15.7.4 Ending the packet transfer . . . . . . . . . . . . . . 375
13.12.12 Set Endpoint Status (Command: 0x40 - 0x55, OUT endpoints. . . . . . . . . . . . . . . . . . . . . . . . 375
Data: write 1 byte (optional)). . . . . . . . . . . . . 359 IN endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . 375
13.12.13 Clear Buffer (Command: 0xF2, Data: read 1 byte 13.16 Double buffered endpoint operation . . . . . . 375
(optional)) . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 13.16.1 Bulk endpoints . . . . . . . . . . . . . . . . . . . . . . . 375
13.12.14 Validate Buffer (Command: 0xFA, Data: 13.16.2 Isochronous endpoints . . . . . . . . . . . . . . . . . 377
none) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
13.13 USB device controller initialization . . . . . . . 361
13.14 Slave mode operation . . . . . . . . . . . . . . . . . . 362


14.1 How to read this chapter . . . . . . . . . . . . . . . . 378 14.4 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
14.2 Basic configuration . . . . . . . . . . . . . . . . . . . . 378 14.4.1 Pin description . . . . . . . . . . . . . . . . . . . . . . . 380
14.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 378 14.4.1.1 USB host usage note . . . . . . . . . . . . . . . . . . 380
14.3.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 14.4.2 Software interface . . . . . . . . . . . . . . . . . . . . 381
14.3.2 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . 379 14.4.2.1 Register map . . . . . . . . . . . . . . . . . . . . . . . . 381
14.4.2.2 USB Host Register Definitions . . . . . . . . . . . 382

15.1 How to read this chapter . . . . . . . . . . . . . . . . 383 15.8.10 I2C Receive Register (I2C_RX - 0xFFE0
15.2 Basic configuration . . . . . . . . . . . . . . . . . . . . 383 C300) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
15.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 383 15.8.11 I2C Transmit Register (I2C_TX - 0xFFE0
C300) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
15.4 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
15.8.12 I2C Status Register (I2C_STS - 0xFFE0
15.5 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 383 C304) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
15.6 Modes of operation . . . . . . . . . . . . . . . . . . . . 384 15.8.13 I2C Control Register (I2C_CTL - 0xFFE0
15.7 Pin configuration . . . . . . . . . . . . . . . . . . . . . . 384 C308) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
15.7.1 Connecting port U1 to an external OTG 15.8.14 I2C Clock High Register (I2C_CLKHI -
transceiver . . . . . . . . . . . . . . . . . . . . . . . . . . 385 0xFFE0 C30C) . . . . . . . . . . . . . . . . . . . . . . . 398
15.7.2 Connecting USB as a two-port host . . . . . . . 388 15.8.15 I2C Clock Low Register (I2C_CLKLO -
15.7.3 Connecting USB as one port host and one port 0xFFE0 C310) . . . . . . . . . . . . . . . . . . . . . . . 399
device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 15.8.16 Interrupt handling . . . . . . . . . . . . . . . . . . . . . 399
15.8 Register description . . . . . . . . . . . . . . . . . . . 389 15.9 HNP support . . . . . . . . . . . . . . . . . . . . . . . . . 400
15.8.1 USB Interrupt Status Register (USBIntSt - 15.9.1 B-device: peripheral to host switching . . . . . 401
0xE01F C1C0) . . . . . . . . . . . . . . . . . . . . . . . 390 Remove D+ pull-up . . . . . . . . . . . . . . . . . . . . 403
15.8.2 OTG Interrupt Status Register (OTGIntSt - Add D+ pull-up . . . . . . . . . . . . . . . . . . . . . . . . 404
0xE01F C100) . . . . . . . . . . . . . . . . . . . . . . . 391 15.9.2 A-device: host to peripheral HNP switching. 404
15.8.3 OTG Interrupt Enable Register (OTGIntEn - Set BDIS_ACON_EN in external OTG
0xFFE0 C104) . . . . . . . . . . . . . . . . . . . . . . . 391 transceiver . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
15.8.4 OTG Interrupt Set Register (OTGIntSet - Clear BDIS_ACON_EN in external OTG trans-
0xFFE0 C20C) . . . . . . . . . . . . . . . . . . . . . . . 391 ceiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
15.8.5 OTG Interrupt Clear Register (OTGIntClr - Discharge VBUS . . . . . . . . . . . . . . . . . . . . . . . 407
0xFFE0 C10C) . . . . . . . . . . . . . . . . . . . . . . . 391 Load and enable OTG timer . . . . . . . . . . . . . 408
15.8.6 OTG Status and Control Register (OTGStCtrl - Stop OTG timer . . . . . . . . . . . . . . . . . . . . . . . 408
0xFFE0 C110). . . . . . . . . . . . . . . . . . . . . . . . 391 Suspend host on port 1 . . . . . . . . . . . . . . . . . 408
15.8.7 OTG Timer Register (OTGTmr - 0xFFE0 15.10 Clocking and power management. . . . . . . . 408
C114) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 15.10.1 Device clock request signals . . . . . . . . . . . . 409
15.8.8 OTG Clock Control Register (OTGClkCtrl - 15.10.1.1 Host clock request signals . . . . . . . . . . . . . . 410
0xFFE0 CFF4) . . . . . . . . . . . . . . . . . . . . . . . 393 15.10.2 Power-down mode support . . . . . . . . . . . . . 410
15.8.9 OTG Clock Status Register (OTGClkSt - 15.11 USB OTG controller initialization . . . . . . . . 410
0xFFE0 CFF8) . . . . . . . . . . . . . . . . . . . . . . . 394

16.1 Basic configuration . . . . . . . . . . . . . . . . . . . . 412 16.4.3 UARTn Divisor Latch LSB Register (U0DLL -
16.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 0xE000 C000, U2DLL - 0xE007 8000, U3DLL -
16.3 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 413 0xE007 C000 when DLAB = 1) and UARTn
Divisor Latch MSB Register (U0DLM -
0xE000 C004, U2DLL - 0xE007 8004, U3DLL -
16.4.1 UARTn Receiver Buffer Register (U0RBR - 0xE007 C004 when DLAB = 1) . . . . . . . . . . 416
0xE000 C000, U2RBR - 0xE007 8000, U3RBR - 16.4.4 UARTn Interrupt Enable Register (U0IER -
0xE007 C000 when DLAB = 0, Read Only) . 416 0xE000 C004, U2IER - 0xE007 8004, U3IER -
16.4.2 UARTn Transmit Holding Register (U0THR - 0xE007 C004 when DLAB = 0) . . . . . . . . . . 417
0xE000 C000, U2THR - 0xE007 8000, U3THR - 16.4.5 UARTn Interrupt Identification Register (U0IIR -
0xE007 C000 when DLAB = 0, Write Only) . 416 0xE000 C008, U2IIR - 0xE007 8008, U3IIR -
0x7008 C008, Read Only) . . . . . . . . . . . . . . 418

16.4.6 UARTn FIFO Control Register (U0FCR - 16.4.10.1 Auto-baud . . . . . . . . . . . . . . . . . . . . . . . . . . 424

0xE000 C008, U2FCR - 0xE007 8008, U3FCR - 16.4.10.2 Auto-baud modes. . . . . . . . . . . . . . . . . . . . . 425
0xE007 C008, Write Only) . . . . . . . . . . . . . . 420 16.4.11 IrDA Control Register for UART3 Only (U3ICR -
16.4.7 UARTn Line Control Register (U0LCR - 0xE007 C024) . . . . . . . . . . . . . . . . . . . . . . . 426
0xE000 C00C, U2LCR - 0xE007 800C, U3LCR - 16.4.12 UARTn Fractional Divider Register (U0FDR -
0xE007 C00C) . . . . . . . . . . . . . . . . . . . . . . . 421 0xE000 C028, U2FDR - 0xE007 8028, U3FDR -
16.4.8 UARTn Line Status Register (U0LSR - 0xE007 C028) . . . . . . . . . . . . . . . . . . . . . . . 427
0xE000 C014, U2LSR - 0xE007 8014, U3LSR - 16.4.12.1 Baudrate calculation . . . . . . . . . . . . . . . . . . 428
0xE007 C014, Read Only) . . . . . . . . . . . . . . 422 16.4.12.1.1 Example 1: PCLK = 14.7456 MHz, BR =
16.4.9 UARTn Scratch Pad Register (U0SCR - 9600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
0xE000 C01C, U2SCR - 0xE007 801C U3SCR - 16.4.12.1.2 Example 2: PCLK = 12 MHz, BR = 115200 430
0xE007 C01C) . . . . . . . . . . . . . . . . . . . . . . . 423 16.4.13 UARTn Transmit Enable Register (U0TER -
16.4.10 UARTn Auto-baud Control Register (U0ACR - 0xE000 C030, U2TER - 0xE007 8030, U3TER -
0xE000 C020, U2ACR - 0xE007 8020, U3ACR - 0xE007 C030) . . . . . . . . . . . . . . . . . . . . . . . 430
0xE007 C020). . . . . . . . . . . . . . . . . . . . . . . . 424 16.5 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 431

17.1 Basic configuration . . . . . . . . . . . . . . . . . . . . 433 17.4.9.1 Auto-RTS . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
17.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 17.4.10 Auto-CTS . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
17.3 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 434 17.4.11 UART1 Line Status Register (U1LSR -
0xE001 0014, Read Only) . . . . . . . . . . . . . . 447
17.4.12 UART1 Modem Status Register (U1MSR -
17.4.1 UART1 Receiver Buffer Register (U1RBR - 0xE001 0018). . . . . . . . . . . . . . . . . . . . . . . . 448
0xE001 0000, when DLAB = 0 Read Only) . 438 17.4.13 UART1 Scratch Pad Register (U1SCR -
17.4.2 UART1 Transmitter Holding Register (U1THR - 0xE001 001C) . . . . . . . . . . . . . . . . . . . . . . . 449
0xE001 0000 when DLAB = 0, Write Only) . 438 17.4.14 UART1 Auto-baud Control Register (U1ACR -
17.4.3 UART1 Divisor Latch LSB and MSB Registers 0xE001 0020). . . . . . . . . . . . . . . . . . . . . . . . 449
(U1DLL - 0xE001 0000 and U1DLM - 17.4.15 Auto-baud . . . . . . . . . . . . . . . . . . . . . . . . . . 450
0xE001 0004, when DLAB = 1) . . . . . . . . . . 438 17.4.16 Auto-baud modes. . . . . . . . . . . . . . . . . . . . . 451
17.4.4 UART1 Interrupt Enable Register (U1IER - 17.4.17 UART1 Fractional Divider Register (U1FDR -
0xE001 0004, when DLAB = 0) . . . . . . . . . . 439 0xE001 0028). . . . . . . . . . . . . . . . . . . . . . . . 452
17.4.5 UART1 Interrupt Identification Register (U1IIR - 17.4.17.1 Baudrate calculation . . . . . . . . . . . . . . . . . . 453
0xE001 0008, Read Only) . . . . . . . . . . . . . . 440 17.4.17.1.1 Example 1: PCLK = 14.7456 MHz, BR =
17.4.6 UART1 FIFO Control Register (U1FCR - 9600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
0xE001 0008, Write Only). . . . . . . . . . . . . . . 443 17.4.17.1.2 Example 2: PCLK = 12 MHz, BR = 115200 455
17.4.7 UART1 Line Control Register (U1LCR - 17.4.18 UART1 Transmit Enable Register (U1TER -
0xE001 000C). . . . . . . . . . . . . . . . . . . . . . . . 443 0xE001 0030). . . . . . . . . . . . . . . . . . . . . . . . 455
17.4.8 UART1 Modem Control Register (U1MCR -
17.5 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 456
0xE001 0010) . . . . . . . . . . . . . . . . . . . . . . . . 444
17.4.9 Auto-Flow control . . . . . . . . . . . . . . . . . . . . . 445

18.1 Basic configuration . . . . . . . . . . . . . . . . . . . . 458 18.7.2 SPI Status Register (S0SPSR - 0xE002
18.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458 0004) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
18.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 458 18.7.3 SPI Data Register (S0SPDR - 0xE002 0008) 465
18.7.4 SPI Clock Counter Register (S0SPCCR -
18.4 SPI data transfers . . . . . . . . . . . . . . . . . . . . . 458
0xE002 000C) . . . . . . . . . . . . . . . . . . . . . . . 465
18.5 SPI peripheral details . . . . . . . . . . . . . . . . . . 460 18.7.5 SPI Test Control Register (SPTCR -
18.5.1 General information . . . . . . . . . . . . . . . . . . . 460 0xE002 0010). . . . . . . . . . . . . . . . . . . . . . . . 466
18.5.2 Master operation. . . . . . . . . . . . . . . . . . . . . . 460 18.7.6 SPI Test Status Register (SPTSR - 0xE002
18.5.3 Slave operation. . . . . . . . . . . . . . . . . . . . . . . 461 0014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
18.5.4 Exception conditions. . . . . . . . . . . . . . . . . . . 461 18.7.7 SPI Interrupt Register (S0SPINT - 0xE002
18.6 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 462 001C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
18.7 Register description . . . . . . . . . . . . . . . . . . . 463 18.8 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 467
18.7.1 SPI Control Register (S0SPCR - 0xE002
0000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463


19.1 Basic configuration . . . . . . . . . . . . . . . . . . . . 468 19.6.2 SSPn Control Register 1 (SSP0CR1 -
19.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 0xE006 8004, SSP1CR1 - 0xE003 0004) . . 478
19.3 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 19.6.3 SSPn Data Register (SSP0DR - 0xE006 8008,
SSP1DR - 0xE003 0008) . . . . . . . . . . . . . . . 479
19.4 Pin descriptions . . . . . . . . . . . . . . . . . . . . . . . 469
19.6.4 SSPn Status Register (SSP0SR - 0xE006 800C,
19.5 Bus description . . . . . . . . . . . . . . . . . . . . . . . 469 SSP1SR - 0xE003 000C). . . . . . . . . . . . . . . 479
19.5.1 Texas Instruments Synchronous Serial Frame 19.6.5 SSPn Clock Prescale Register (SSP0CPSR -
Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469 0xE006 8010, SSP1CPSR - 0xE003 0010) . 480
19.5.2 SPI Frame Format . . . . . . . . . . . . . . . . . . . . 470 19.6.6 SSPn Interrupt Mask Set/Clear Register
19.5.2.1 Clock Polarity (CPOL) and Phase (CPHA) (SSP0IMSC - 0xE006 8014, SSP1IMSC -
Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470 0xE003 0014). . . . . . . . . . . . . . . . . . . . . . . . 480
19.5.2.2 SPI Format with CPOL=0,CPHA=0 . . . . . . . 471 19.6.7 SSPn Raw Interrupt Status Register (SSP0RIS -
19.5.2.3 SPI Format with CPOL=0,CPHA=1 . . . . . . . 472 0xE006 8018, SSP1RIS - 0xE003 0018) . . . 481
19.5.2.4 SPI Format with CPOL = 1,CPHA = 0 . . . . . 472 19.6.8 SSPn Masked Interrupt Status Register
19.5.2.5 SPI Format with CPOL = 1,CPHA = 1 . . . . . 474 (SSP0MIS - 0xE006 801C, SSP1MIS -
19.5.3 Semiconductor Microwire Frame Format . . . 474 0xE003 001C) . . . . . . . . . . . . . . . . . . . . . . . 481
19.5.3.1 Setup and Hold Time Requirements on CS With 19.6.9 SSPn Interrupt Clear Register (SSP0ICR -
Respect to SK in Microwire Mode. . . . . . . . . 476 0xE006 8020, SSP1ICR - 0xE003 0020). . . 482
19.6 Register Description . . . . . . . . . . . . . . . . . . . 476 19.6.10 SSPn DMA Control Register (SSP0DMACR -
19.6.1 SSPn Control Register 0 (SSP0CR0 - 0xE006 8024, SSP1DMACR - 0xE003
0xE006 8000, SSP1CR0 - 0xE003 0000) . . 477 0024) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482

20.1 How to read this chapter . . . . . . . . . . . . . . . . 483 20.7.3 Clock Control Register (MCIClock -
20.2 Basic configuration . . . . . . . . . . . . . . . . . . . . 483 0xE008 C004) . . . . . . . . . . . . . . . . . . . . . . . 496
20.3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 483 20.7.4 Argument Register (MCIArgument -
0xE008 C008) . . . . . . . . . . . . . . . . . . . . . . . 497
20.4 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
20.7.5 Command Register (MCICommand -
20.5 SD/MMC card interface pin description . . . . 484 0xE008 C00C) . . . . . . . . . . . . . . . . . . . . . . . 497
20.6 Functional overview . . . . . . . . . . . . . . . . . . . 484 20.7.6 Command Response Register
20.6.1 Mutimedia card . . . . . . . . . . . . . . . . . . . . . . . 484 (MCIRespCommand - 0xE008 C010) . . . . . 498
20.6.2 Secure digital memory card . . . . . . . . . . . . . 485 20.7.7 Response Registers (MCIResponse0-3 -
20.6.2.1 Secure digital memory card bus signals . . . . 485 0xE008 C014, E008 C018, E008 C01C and
20.6.3 MCI adapter . . . . . . . . . . . . . . . . . . . . . . . . . 485 E008 C020) . . . . . . . . . . . . . . . . . . . . . . . . . 498
20.6.3.1 Adapter register block. . . . . . . . . . . . . . . . . . 486 20.7.8 Data Timer Register (MCIDataTimer -
20.6.3.2 Control unit . . . . . . . . . . . . . . . . . . . . . . . . . . 486 0xE008 C024) . . . . . . . . . . . . . . . . . . . . . . . 499
20.6.3.3 Command path . . . . . . . . . . . . . . . . . . . . . . . 486 20.7.9 Data Length Register (MCIDataLength -
20.6.3.4 Command path state machine . . . . . . . . . . . 486 0xE008 C028) . . . . . . . . . . . . . . . . . . . . . . . 499
20.6.3.5 Command format . . . . . . . . . . . . . . . . . . . . . 488 20.7.10 Data Control Register (MCIDataCtrl -
20.6.3.6 Data path . . . . . . . . . . . . . . . . . . . . . . . . . . . 489 0xE008 C02C) . . . . . . . . . . . . . . . . . . . . . . . 500
20.6.3.7 Data path state machine. . . . . . . . . . . . . . . . 489 20.7.11 Data Counter Register (MCIDataCnt -
20.6.3.8 Data counter . . . . . . . . . . . . . . . . . . . . . . . . . 491 0xE008 C030) . . . . . . . . . . . . . . . . . . . . . . . 500
20.6.3.9 Bus mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 492 20.7.12 Status Register (MCIStatus - 0xE008 C034) 501
20.6.3.10 CRC Token status. . . . . . . . . . . . . . . . . . . . . 492 20.7.13 Clear Register (MCIClear - 0xE008 C038) . 502
20.6.3.11 Status flags . . . . . . . . . . . . . . . . . . . . . . . . . . 493 20.7.14 Interrupt Mask Registers (MCIMask0 -
20.6.3.12 CRC generator . . . . . . . . . . . . . . . . . . . . . . . 493 0xE008 C03C) . . . . . . . . . . . . . . . . . . . . . . . 502
20.6.3.13 Data FIFO . . . . . . . . . . . . . . . . . . . . . . . . . . . 493 20.7.15 FIFO Counter Register (MCIFifoCnt -
20.6.3.14 Transmit FIFO. . . . . . . . . . . . . . . . . . . . . . . . 494 0xE008 C048) . . . . . . . . . . . . . . . . . . . . . . . 503
20.6.3.15 Receive FIFO . . . . . . . . . . . . . . . . . . . . . . . . 494 20.7.16 Data FIFO Register (MCIFIFO - 0xE008 C080 to
20.6.3.16 APB interfaces . . . . . . . . . . . . . . . . . . . . . . . 495 0xE008 C0BC) . . . . . . . . . . . . . . . . . . . . . . . 503
20.6.3.17 Interrupt logic . . . . . . . . . . . . . . . . . . . . . . . . 495
20.7.1 Summary of MCI Registers. . . . . . . . . . . . . . 495
20.7.2 Power Control Register (MCI Power -
0xE008 C000). . . . . . . . . . . . . . . . . . . . . . . . 496


21.1 Basic configuration . . . . . . . . . . . . . . . . . . . . 504 21.9.7 Simultaneous repeated START conditions from
21.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504 two masters . . . . . . . . . . . . . . . . . . . . . . . . . 532
21.3 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 504 21.9.8 Data transfer after loss of arbitration . . . . . . 532
21.9.9 Forced access to the I2C bus. . . . . . . . . . . . 532
21.4 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
21.9.10 I2C Bus obstructed by a Low level on SCL or
21.5 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 506 SDA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
21.6 I2C operating modes . . . . . . . . . . . . . . . . . . . 506 21.9.11 Bus error . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
21.6.1 Master Transmitter mode . . . . . . . . . . . . . . . 506 21.9.12 I2C State service routines. . . . . . . . . . . . . . . 534
21.6.2 Master Receiver mode . . . . . . . . . . . . . . . . . 507 21.9.12.1 Initialization . . . . . . . . . . . . . . . . . . . . . . . . . 534
21.6.3 Slave Receiver mode . . . . . . . . . . . . . . . . . . 508 21.9.12.2 I2C interrupt service . . . . . . . . . . . . . . . . . . . 535
21.6.4 Slave Transmitter mode . . . . . . . . . . . . . . . . 509 21.9.12.3 The state service routines . . . . . . . . . . . . . . 535
21.7 I2C implementation and operation . . . . . . . . 509 21.9.12.4 Adapting state services to an application. . . 535
21.7.1 Input filters and output stages. . . . . . . . . . . . 509 21.10 Software example . . . . . . . . . . . . . . . . . . . . . 535
21.7.2 Address Register I2ADDR . . . . . . . . . . . . . . 511 21.10.1 Initialization routine . . . . . . . . . . . . . . . . . . . 535
21.7.3 Comparator. . . . . . . . . . . . . . . . . . . . . . . . . . 511 21.10.2 Start master transmit function . . . . . . . . . . . 535
21.7.4 Shift register I2DAT. . . . . . . . . . . . . . . . . . . . 511 21.10.3 Start master receive function . . . . . . . . . . . . 535
21.7.5 Arbitration and synchronization logic . . . . . . 511 21.10.4 I2C interrupt routine . . . . . . . . . . . . . . . . . . . 536
21.7.6 Serial clock generator . . . . . . . . . . . . . . . . . . 512 21.10.5 Non mode specific states. . . . . . . . . . . . . . . 536
21.7.7 Timing and control . . . . . . . . . . . . . . . . . . . . 512 21.10.5.1 State : 0x00 . . . . . . . . . . . . . . . . . . . . . . . . . 536
21.7.8 Control register I2CONSET and I2CONCLR 512 21.10.6 Master states . . . . . . . . . . . . . . . . . . . . . . . . 536
21.7.9 Status decoder and status register . . . . . . . . 513 21.10.6.1 State : 0x08 . . . . . . . . . . . . . . . . . . . . . . . . . 536
21.8 Register description . . . . . . . . . . . . . . . . . . . 513 21.10.6.2 State : 0x10 . . . . . . . . . . . . . . . . . . . . . . . . . 536
21.8.1 I2C Control Set Register (I2C[0/1/2]CONSET: 21.10.7 Master Transmitter states . . . . . . . . . . . . . . 537
0xE001 C000, 0xE005 C000, 0xE008 0000) 514 21.10.7.1 State : 0x18 . . . . . . . . . . . . . . . . . . . . . . . . . 537
21.8.2 I2C Control Clear Register (I2C[0/1/2]CONCLR: 21.10.7.2 State : 0x20 . . . . . . . . . . . . . . . . . . . . . . . . . 537
0xE001 C018, 0xE005 C018, 0xE008 0018) 516 21.10.7.3 State : 0x28 . . . . . . . . . . . . . . . . . . . . . . . . . 537
21.8.3 I2C Status Register (I2C[0/1/2]STAT - 21.10.7.4 State : 0x30 . . . . . . . . . . . . . . . . . . . . . . . . . 537
0xE001 C004, 0xE005 C004, 0xE008 0004) 516 21.10.7.5 State : 0x38 . . . . . . . . . . . . . . . . . . . . . . . . . 538
21.8.4 I2C Data Register (I2C[0/1/2]DAT - 0xE001 C008, 21.10.8 Master Receive states . . . . . . . . . . . . . . . . . 538
0xE005 C008, 0xE008 0008) . . . . . . . . . . . . 517 21.10.8.1 State : 0x40 . . . . . . . . . . . . . . . . . . . . . . . . . 538
21.8.5 I2C Slave Address Register (I2C[0/1/2]ADR - 21.10.8.2 State : 0x48 . . . . . . . . . . . . . . . . . . . . . . . . . 538
0xE001 C00C, 0xE005 C00C, 0xE008 000C) 517 21.10.8.3 State : 0x50 . . . . . . . . . . . . . . . . . . . . . . . . . 538
21.8.6 I2C SCL High Duty Cycle Register 21.10.8.4 State : 0x58 . . . . . . . . . . . . . . . . . . . . . . . . . 538
(I2C[0/1/2]SCLH - 0xE001 C010, 0xE005 C010, 21.10.9 Slave Receiver states . . . . . . . . . . . . . . . . . 539
0xE008 0010) . . . . . . . . . . . . . . . . . . . . . . . . 517 21.10.9.1 State : 0x60 . . . . . . . . . . . . . . . . . . . . . . . . . 539
21.8.7 I2C SCL Low Duty Cycle Register 21.10.9.2 State : 0x68 . . . . . . . . . . . . . . . . . . . . . . . . . 539
(I2C[0/1/2]SCLL - 0xE001 C014, 0xE005 C014, 21.10.9.3 State : 0x70 . . . . . . . . . . . . . . . . . . . . . . . . . 539
0xE008 0014) . . . . . . . . . . . . . . . . . . . . . . . . 517 21.10.9.4 State : 0x78 . . . . . . . . . . . . . . . . . . . . . . . . . 539
21.8.8 Selecting the appropriate I2C data rate and duty 21.10.9.5 State : 0x80 . . . . . . . . . . . . . . . . . . . . . . . . . 540
cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 21.10.9.6 State : 0x88 . . . . . . . . . . . . . . . . . . . . . . . . . 540
21.10.9.7 State : 0x90 . . . . . . . . . . . . . . . . . . . . . . . . . 540
21.9 Details of I2C operating modes. . . . . . . . . . . 518
21.10.9.8 State : 0x98 . . . . . . . . . . . . . . . . . . . . . . . . . 540
21.9.1 Master Transmitter mode . . . . . . . . . . . . . . . 519
21.10.9.9 State : 0xA0 . . . . . . . . . . . . . . . . . . . . . . . . . 540
21.9.2 Master Receiver mode . . . . . . . . . . . . . . . . . 520
21.10.10 Slave Transmitter States . . . . . . . . . . . . . . . 541
21.9.3 Slave Receiver mode . . . . . . . . . . . . . . . . . . 520
21.10.10.1 State : 0xA8 . . . . . . . . . . . . . . . . . . . . . . . . 541
21.9.4 Slave Transmitter mode . . . . . . . . . . . . . . . . 525
21.10.10.2 State : 0xB0 . . . . . . . . . . . . . . . . . . . . . . . . 541
21.9.5 Miscellaneous states . . . . . . . . . . . . . . . . . . 531
21.10.10.3 State : 0xB8 . . . . . . . . . . . . . . . . . . . . . . . . 541
21.9.5.1 I2STAT = 0xF8 . . . . . . . . . . . . . . . . . . . . . . . 531
21.10.10.4 State : 0xC0 . . . . . . . . . . . . . . . . . . . . . . . . 541
21.9.5.2 I2STAT = 0x00 . . . . . . . . . . . . . . . . . . . . . . . 531
21.10.10.5 State : 0xC8 . . . . . . . . . . . . . . . . . . . . . . . . 542
21.9.6 Some special cases . . . . . . . . . . . . . . . . . . . 532

22.1 Basic configuration . . . . . . . . . . . . . . . . . . . . 543 22.4 Pin descriptions . . . . . . . . . . . . . . . . . . . . . . 544
22.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543 22.5 Register description . . . . . . . . . . . . . . . . . . . 545
22.3 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 543 22.5.1 Digital Audio Output Register (I2SDAO -
0xE008 8000). . . . . . . . . . . . . . . . . . . . . . . . 546

22.5.2 Digital Audio Input Register (I2SDAI - 22.5.7 DMA Configuration Register 2 (I2SDMA2 -
0xE008 8004) . . . . . . . . . . . . . . . . . . . . . . . . 547 0xE008 8018). . . . . . . . . . . . . . . . . . . . . . . . 548
22.5.3 Transmit FIFO Register (I2STXFIFO - 22.5.8 Interrupt Request Control Register (I2SIRQ -
0xE008 8008) . . . . . . . . . . . . . . . . . . . . . . . . 547 0xE008 801C) . . . . . . . . . . . . . . . . . . . . . . . 549
22.5.4 Receive FIFO Register (I2SRXFIFO - 22.5.9 Transmit Clock Rate Register (I2STXRATE -
0xE008 800C). . . . . . . . . . . . . . . . . . . . . . . . 547 0xE008 8020). . . . . . . . . . . . . . . . . . . . . . . . 549
22.5.5 Status Feedback Register (I2SSTATE - 22.5.10 Receive Clock Rate Register (I2SRXRATE -
0xE008 8010) . . . . . . . . . . . . . . . . . . . . . . . . 548 0xE008 8024). . . . . . . . . . . . . . . . . . . . . . . . 549
22.5.6 DMA Configuration Register 1 (I2SDMA1 - 22.6 I2S transmit and receive interfaces . . . . . . . 550
0xE008 8014) . . . . . . . . . . . . . . . . . . . . . . . . 548 22.7 FIFO controller . . . . . . . . . . . . . . . . . . . . . . . 551

23.1 Basic configuration . . . . . . . . . . . . . . . . . . . . 553 23.6.5 Prescale register (T0PR - T3PR, 0xE000 400C,
23.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553 0xE000 800C, 0xE007 000C, 0xE007 400C) 558
23.3 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 553 23.6.6 Prescale Counter register (T0PC - T3PC,
0xE000 4010, 0xE000 8010, 0xE007 0010,
23.4 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
0xE007 4010). . . . . . . . . . . . . . . . . . . . . . . . 558
23.5 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 554 23.6.7 Match Registers (MR0 - MR3) . . . . . . . . . . . 558
23.5.1 Multiple CAP and MAT pins . . . . . . . . . . . . . 554 23.6.8 Match Control Register (T[0/1/2/3]MCR -
23.6 Register description . . . . . . . . . . . . . . . . . . . 554 0xE000 4014, 0xE000 8014, 0xE007 0014,
23.6.1 Interrupt Register (T[0/1/2/3]IR - 0xE000 4000, 0xE007 4014). . . . . . . . . . . . . . . . . . . . . . . . 559
0xE000 8000, 0xE007 0000, 0xE007 4000) . 556 23.6.9 Capture Registers (CR0 and CR1) . . . . . . . 560
23.6.2 Timer Control Register (T[0/1/2/3]CR - 23.6.10 Capture Control Register (T[0/1/2/3]CCR -
0xE000 4004, 0xE000 8004, 0xE007 0004, 0xE000 4028, 0xE000 8028, 0xE007 0028,
0xE007 4004) . . . . . . . . . . . . . . . . . . . . . . . . 556 0xE007 4028). . . . . . . . . . . . . . . . . . . . . . . . 560
23.6.3 Count Control Register (T[0/1/2/3]CTCR - 23.6.11 External Match Register (T[0/1/2/3]EMR -
0xE000 4070, 0xE000 8070, 0xE007 0070, 0xE000 403C, 0xE000 803C, 0xE007 003C,
0xE007 4070) . . . . . . . . . . . . . . . . . . . . . . . . 557 0xE007 403C) . . . . . . . . . . . . . . . . . . . . . . . 561
23.6.4 Timer Counter . . . . . . . .registers (T0TC - T3TC, 23.7 Example timer operation . . . . . . . . . . . . . . . 562
0xE000 4008, 0xE000 8008, 0xE007 0008, 23.8 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 562
0xE007 4008) . . . . . . . . . . . . . . . . . . . . . . . . 558

24.1 Basic configuration . . . . . . . . . . . . . . . . . . . . 564 24.7.1 PWM Interrupt Register (PWM1IR - 0xE001
24.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564 8000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
24.3 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 565 24.7.2 PWM Timer Control Register (PWM1TCR
0xE001 8004). . . . . . . . . . . . . . . . . . . . . . . . 571
24.4 Sample waveform with rules for single and
24.7.3 PWM Count Control Register (PWM1CTCR -
double edge control. . . . . . . . . . . . . . . . . . . . 567
0xE001 8070). . . . . . . . . . . . . . . . . . . . . . . . 571
24.4.1 Rules for Single Edge Controlled PWM 24.7.4 PWM Match Control Register (PWM1MCR -
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 0xE001 8014). . . . . . . . . . . . . . . . . . . . . . . . 572
24.4.2 Rules for Double Edge Controlled PWM 24.7.5 PWM Capture Control Register (PWM1CCR -
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 0xE001 8028). . . . . . . . . . . . . . . . . . . . . . . . 574
24.5 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 568 24.7.6 PWM Control Registers (PWM1PCR -
24.6 PWM base addresses . . . . . . . . . . . . . . . . . . 569 0xE001 804C) . . . . . . . . . . . . . . . . . . . . . . . 575
24.7 Register description . . . . . . . . . . . . . . . . . . . 569 24.7.7 PWM Latch Enable Register (PWM1LER -
0xE001 8050). . . . . . . . . . . . . . . . . . . . . . . . 576

25.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578 25.4.2 Watchdog Timer Constant Register (WDTC -
25.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 578 0xE000 0004). . . . . . . . . . . . . . . . . . . . . . . . 580
25.3 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 578 25.4.3 Watchdog Feed Register (WDFEED -
0xE000 0008). . . . . . . . . . . . . . . . . . . . . . . . 580
25.4.4 Watchdog Timer Value Register (WDTV -
25.4.1 Watchdog Mode Register (WDMOD - 0xE000 000C) . . . . . . . . . . . . . . . . . . . . . . . 581
0xE000 0000) . . . . . . . . . . . . . . . . . . . . . . . . 579

25.4.5 Watchdog Timer Clock Source Selection Register 25.5 Block diagram . . . . . . . . . . . . . . . . . . . . . . . . 582
(WDCLKSEL - 0xE000 0010) . . . . . . . . . . . . 581
26.1 How to read this chapter . . . . . . . . . . . . . . . . 583 26.7.3.1 Consolidated Time Register 0 (CTIME0 -
26.2 Basic configuration . . . . . . . . . . . . . . . . . . . . 583 0xE002 4014). . . . . . . . . . . . . . . . . . . . . . . . 589
26.3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583 26.7.3.2 Consolidated Time Register 1 (CTIME1 -
0xE002 4018). . . . . . . . . . . . . . . . . . . . . . . . 590
26.4 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
26.7.3.3 Consolidated Time Register 2 (CTIME2 -
26.5 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 584 0xE002 401C) . . . . . . . . . . . . . . . . . . . . . . . 590
26.6 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 584 26.7.4 Time Counter Group . . . . . . . . . . . . . . . . . . 590
26.7 Register description . . . . . . . . . . . . . . . . . . . 585 26.7.4.1 Leap year calculation . . . . . . . . . . . . . . . . . . 591
26.7.1 RTC interrupts . . . . . . . . . . . . . . . . . . . . . . . 586 26.7.5 Alarm register group . . . . . . . . . . . . . . . . . . 591
26.7.2 Miscellaneous register group . . . . . . . . . . . . 586 26.7.6 RTC clock generation . . . . . . . . . . . . . . . . . 592
26.7.2.1 Interrupt Location Register (ILR - 0xE002 26.7.6.1 Reference Clock Divider (Prescaler) . . . . . . 592
4000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586 26.7.6.2 Prescaler Integer Register (PREINT -
26.7.2.2 Clock Tick Counter Register (CTCR - 0xE002 4080). . . . . . . . . . . . . . . . . . . . . . . . 592
0xE002 4004) . . . . . . . . . . . . . . . . . . . . . . . . 587 26.7.6.3 Prescaler Fraction Register (PREFRAC -
26.7.2.3 Clock Control Register (CCR - 0xE002 4008) 587 0xE002 4084). . . . . . . . . . . . . . . . . . . . . . . . 593
26.7.2.4 Counter Increment Interrupt Register (CIIR - 26.7.6.4 Example of Prescaler Usage . . . . . . . . . . . . 593
0xE002 400C). . . . . . . . . . . . . . . . . . . . . . . . 587 26.7.6.5 Prescaler operation . . . . . . . . . . . . . . . . . . . 594
26.7.2.5 Counter Increment Select Mask Register (CISS - 26.8 RTC usage notes. . . . . . . . . . . . . . . . . . . . . . 595
0xE002 4040) . . . . . . . . . . . . . . . . . . . . . . . . 588 26.8.1 Alarm output. . . . . . . . . . . . . . . . . . . . . . . . . 596
26.7.2.6 Alarm Mask Register (AMR - 0xE002 4010). 589 26.9 Battery RAM. . . . . . . . . . . . . . . . . . . . . . . . . . 596
26.7.3 Consolidated time registers . . . . . . . . . . . . . 589
26.10 RTC external 32 kHz oscillator component
selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596

27.1 How to read this chapter . . . . . . . . . . . . . . . . 598 27.6.3 A/D Status Register (AD0STAT - 0xE003
27.2 Basic configuration . . . . . . . . . . . . . . . . . . . . 598 4030) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
27.3 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598 27.6.4 A/D Interrupt Enable Register (AD0INTEN -
0xE003 400C) . . . . . . . . . . . . . . . . . . . . . . . 603
27.4 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
27.6.5 A/D Data Registers (AD0DR0 to AD0DR7 -
27.5 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 599 0xE003 4010 to 0xE003 402C) . . . . . . . . . . 603
27.6 Register description . . . . . . . . . . . . . . . . . . . 599 27.7 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
27.6.1 A/D Control Register (AD0CR - 0xE003 27.7.1 Hardware-triggered conversion . . . . . . . . . . 604
4000) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600 27.7.2 Interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
27.6.2 A/D Global Data Register (AD0GDR - 27.7.3 Accuracy vs. Digital Receiver . . . . . . . . . . . 604
0xE003 4004) . . . . . . . . . . . . . . . . . . . . . . . . 601

28.1 Basic configuration . . . . . . . . . . . . . . . . . . . . 605 28.4 Register description (DACR - 0xE006 C000) 605
28.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605 28.5 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
28.3 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 605

29.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 607 29.3.2.3 ISP data format . . . . . . . . . . . . . . . . . . . . . . 609
29.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607 29.3.2.4 ISP flow control . . . . . . . . . . . . . . . . . . . . . . 609
29.3 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 607 29.3.2.5 ISP command abort . . . . . . . . . . . . . . . . . . . 610
29.3.2.6 Interrupts during ISP . . . . . . . . . . . . . . . . . . 610
29.3.1 Memory map after any reset. . . . . . . . . . . . . 607
29.3.2.7 Interrupts during IAP . . . . . . . . . . . . . . . . . . 610
29.3.1.1 Criterion for Valid User Code . . . . . . . . . . . . 608
29.3.2.8 RAM used by ISP command handler. . . . . . 610
29.3.2 Communication protocol . . . . . . . . . . . . . . . . 609
29.3.2.9 RAM used by IAP command handler. . . . . . 610
29.3.2.1 ISP command format . . . . . . . . . . . . . . . . . . 609
29.3.2.10 RAM used by RealMonitor . . . . . . . . . . . . . . 610
29.3.2.2 ISP response format . . . . . . . . . . . . . . . . . . . 609
29.4 Boot process flowchart . . . . . . . . . . . . . . . . . 611

29.5 Sector numbers . . . . . . . . . . . . . . . . . . . . . . . 612 29.7.11 Read Part Identification number . . . . . . . . . 619
29.6 Code Read Protection (CRP) . . . . . . . . . . . . 613 29.7.12 Read Boot code version number . . . . . . . . . 620
29.7 ISP commands . . . . . . . . . . . . . . . . . . . . . . . . 614 29.7.13 Compare <address1> <address2> <no of
bytes> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
29.7.1 Unlock <Unlock code> . . . . . . . . . . . . . . . . . 615
29.7.14 ISP Return Codes . . . . . . . . . . . . . . . . . . . . 621
29.7.2 Set Baud Rate <Baud Rate> <stop bit> . . . . 615
29.7.3 Echo <setting> . . . . . . . . . . . . . . . . . . . . . . . 616 29.8 IAP commands . . . . . . . . . . . . . . . . . . . . . . . 622
29.7.4 Write to RAM <start address> <number of 29.8.1 Prepare sector(s) for write operation . . . . . . 624
bytes> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616 29.8.2 Copy RAM to flash . . . . . . . . . . . . . . . . . . . . 625
29.7.5 Read Memory <address> <no. of bytes> . . . 616 29.8.3 Erase Sector(s) . . . . . . . . . . . . . . . . . . . . . . 625
29.7.6 Prepare sector(s) for write operation <start sector 29.8.4 Blank check sector(s). . . . . . . . . . . . . . . . . . 626
number> <end sector number> . . . . . . . . . . 617 29.8.5 Read Part Identification number . . . . . . . . . 626
29.7.7 Copy RAM to flash <flash address> <RAM 29.8.6 Read Boot code version number . . . . . . . . . 626
address> <no of bytes> . . . . . . . . . . . . . . . . 618 29.8.7 Compare <address1> <address2> <no of
29.7.8 Go <address> <mode>. . . . . . . . . . . . . . . . . 618 bytes> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
29.7.9 Erase sector(s) <start sector number> <end 29.8.8 Reinvoke ISP . . . . . . . . . . . . . . . . . . . . . . . . 627
sector number>. . . . . . . . . . . . . . . . . . . . . . . 619 29.8.9 IAP Status Codes . . . . . . . . . . . . . . . . . . . . . 627
29.7.10 Blank check sector(s) <sector number> <end 29.9 JTAG flash programming interface . . . . . . . 628
sector number>. . . . . . . . . . . . . . . . . . . . . . . 619

30.1 Basic configuration . . . . . . . . . . . . . . . . . . . . 629 30.7.5 Disabling a DMA Channel Without Losing Data in
30.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 629 the FIFO. . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
30.3 Features of the GPDMA. . . . . . . . . . . . . . . . . 629 30.7.6 Setup a New DMA Transfer . . . . . . . . . . . . . 637
30.7.7 Disabling a DMA Channel and Losing Data in the
30.4 Functional overview . . . . . . . . . . . . . . . . . . . 630
FIFO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
30.4.1 Memory regions accessible by the GPDMA . 630 30.7.8 Halting a DMA Transfer . . . . . . . . . . . . . . . . 638
30.4.2 GPDMA functional description . . . . . . . . . . . 630 30.7.9 Programming a DMA Channel . . . . . . . . . . . 638
30.4.2.1 AHB Slave Interface . . . . . . . . . . . . . . . . . . . 631
30.8 Summary of GPDMA registers. . . . . . . . . . . 638
30.4.2.2 Control Logic and Register Bank . . . . . . . . . 631
30.4.2.3 DMA Request and Response Interface . . . . 631 30.9 Register descriptions . . . . . . . . . . . . . . . . . . 640
30.4.2.4 Channel Logic and Channel Register Bank . 631 30.9.1 Interrupt Status Register (DMACIntStatus -
30.4.2.5 Interrupt Request . . . . . . . . . . . . . . . . . . . . . 631 0xFFE0 4000) . . . . . . . . . . . . . . . . . . . . . . . 640
30.4.2.6 AHB Master Interface . . . . . . . . . . . . . . . . . . 632 30.9.2 Interrupt Terminal Count Status Register
30.4.2.7 Bus and Transfer Widths . . . . . . . . . . . . . . . 632 (DMACIntTCStatus - 0xFFE0 4004) . . . . . . 640
30.4.2.8 Endian Behavior . . . . . . . . . . . . . . . . . . . . . . 632 30.9.3 Interrupt Terminal Count Clear Register
30.4.2.9 Error Conditions . . . . . . . . . . . . . . . . . . . . . . 634 (DMACIntClear - 0xFFE0 4008). . . . . . . . . . 640
30.4.2.10 Channel Hardware . . . . . . . . . . . . . . . . . . . . 635 30.9.4 Interrupt Error Status Register
30.4.2.11 DMA Request Priority . . . . . . . . . . . . . . . . . . 635 (DMACIntErrorStatus - 0xFFE0 400C). . . . . 641
30.4.2.12 Interrupt Generation . . . . . . . . . . . . . . . . . . . 635 30.9.5 Interrupt Error Clear Register (DMACIntErrClr -
30.4.2.13 The completion of the DMA transfer 0xFFE0 4010) . . . . . . . . . . . . . . . . . . . . . . . 641
indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 635 30.9.6 Raw Interrupt Terminal Count Status Register
30.4.3 DMA System Connections . . . . . . . . . . . . . . 635 (DMACRawIntTCStatus - 0xFFE0 4014) . . . 641
30.5 Programmer’s model . . . . . . . . . . . . . . . . . . . 636 30.9.7 Raw Error Interrupt Status Register
(DMACRawIntErrorStatus - 0xFFE0 4018) . 642
30.6 About the programmer’s model . . . . . . . . . . 636
30.9.8 Enabled Channel Register (DMACEnbldChns -
30.7 Programming the GPDMA. . . . . . . . . . . . . . . 636 0xFFE0 401C) . . . . . . . . . . . . . . . . . . . . . . . 642
30.7.1 Enabling the GPDMA . . . . . . . . . . . . . . . . . . 637 30.9.9 Software Burst Request Register
30.7.2 Disabling the GPDMA. . . . . . . . . . . . . . . . . . 637 (DMACSoftBReq - 0xFFE0 4020) . . . . . . . . 642
30.7.3 Enabling a DMA Channel . . . . . . . . . . . . . . . 637 30.9.10 Software Single Request Register
30.7.4 Disabling a DMA Channel . . . . . . . . . . . . . . 637 (DMACSoftSReq - 0xFFE0 4024) . . . . . . . . 643
continued >>

30.9.11 Software Last Burst Request Register 30.10.6 Channel Configuration Registers
(DMACSoftLBreq - 0xFFE0 4028) . . . . . . . . 643 (DMACC0Configuration - 0xFFE0 4110 and
30.9.12 Software Last Single Request Register DMACC1Configuration - 0xFFE0 4130) . . . 649
(DMACSoftLSReq - 0xFFE0 402C) . . . . . . . 644 30.10.7 Lock control . . . . . . . . . . . . . . . . . . . . . . . . . 651
30.9.13 Configuration Register (DMACConfiguration - 30.10.8 Flow control and transfer type . . . . . . . . . . . 651
0xFFE0 4030) . . . . . . . . . . . . . . . . . . . . . . . . 644 30.11 Address generation . . . . . . . . . . . . . . . . . . . 651
30.9.14 Synchronization Register (DMACSync - 30.12 Scatter/Gather . . . . . . . . . . . . . . . . . . . . . . . . 652
0xFFE0 4034) . . . . . . . . . . . . . . . . . . . . . . . . 645
30.12.1 Linked List Items . . . . . . . . . . . . . . . . . . . . . 652
30.10 Channel registers . . . . . . . . . . . . . . . . . . . . . 645 30.12.2 Programming the GPDMA for scatter/gather
30.10.1 Channel Source Address Registers DMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
(DMACC0SrcAddr - 0xFFE0 4100 and 30.12.3 Example of scatter/gather DMA . . . . . . . . . . 653
DMACC1SrcAddr - 0xFFE0 4120) . . . . . . . . 646 30.13 Interrupt requests . . . . . . . . . . . . . . . . . . . . . 654
30.10.2 Channel Destination Address Registers
30.13.1 Hardware interrupt sequence flow . . . . . . . . 654
(DMACC0DestAddr - 0xFFE0 4104 and
30.13.2 Interrupt polling sequence flow . . . . . . . . . . 655
DMACC1DestAddr - 0xFFE0 4124) . . . . . . . 646
30.10.3 Channel Linked List Item Registers (DMACC0LLI 30.14 GPDMA data flow . . . . . . . . . . . . . . . . . . . . . 655
- 0xFFE0 4108 and DMACC1LLI - 0xFFE0 30.14.1 Peripheral-to-memory, or Memory-to-peripheral
4128) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646 DMA Flow . . . . . . . . . . . . . . . . . . . . . . . . . . 655
30.10.4 Channel Control Registers (DMACC0Control - 30.14.2 Peripheral-to-peripheral DMA Flow . . . . . . . 656
0xFFE0 410C and DMACC0Control - 30.14.3 Memory-to-memory DMA Flow . . . . . . . . . . 657
0xFFE0 412C) . . . . . . . . . . . . . . . . . . . . . . . 647 30.15 Flow control. . . . . . . . . . . . . . . . . . . . . . . . . . 657
30.10.5 Protection and Access Information . . . . . . . . 648

31.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658 31.4 Pin description . . . . . . . . . . . . . . . . . . . . . . . 659
31.2 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 658 31.5 Register description . . . . . . . . . . . . . . . . . . . 659
31.3 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 658 31.6 Reset state of multiplexed pins . . . . . . . . . . 660
31.3.1 ETM configuration . . . . . . . . . . . . . . . . . . . . 658 31.7 Block diagram . . . . . . . . . . . . . . . . . . . . . . . . 661

32.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662 32.5 JTAG usage notes . . . . . . . . . . . . . . . . . . . . . 664
32.2 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 662 32.6 Register description . . . . . . . . . . . . . . . . . . . 664
32.3 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 662 32.7 Block diagram . . . . . . . . . . . . . . . . . . . . . . . . 664
32.4 Pin description . . . . . . . . . . . . . . . . . . . . . . . . 663

33.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666 33.4.4 SVC Mode . . . . . . . . . . . . . . . . . . . . . . . . . . 669
33.2 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 666 33.4.5 Prefetch Abort Mode . . . . . . . . . . . . . . . . . . 670
33.3 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 666 33.4.6 Data Abort Mode . . . . . . . . . . . . . . . . . . . . . 670
33.4.7 User/System Mode . . . . . . . . . . . . . . . . . . . 670
33.3.1 RealMonitor Components . . . . . . . . . . . . . . . 667
33.4.8 FIQ Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
33.3.1.1 RMHost. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
33.4.9 Handling Exceptions . . . . . . . . . . . . . . . . . . 670
33.3.1.2 RMTarget . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
33.4.9.1 RealMonitor Exception Handling . . . . . . . . . 670
33.3.2 How RealMonitor Works . . . . . . . . . . . . . . . . 668
33.4.10 RMTarget Initialization . . . . . . . . . . . . . . . . . 671
33.4 How to Enable RealMonitor . . . . . . . . . . . . . 669 33.4.11 Code Example . . . . . . . . . . . . . . . . . . . . . . . 671
33.4.1 Adding Stacks . . . . . . . . . . . . . . . . . . . . . . . . 669
33.5 RealMonitor Build Options. . . . . . . . . . . . . . 674
33.4.2 IRQ Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
33.4.3 Undef Mode . . . . . . . . . . . . . . . . . . . . . . . . . 669
continued >>


34.1 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . 677 34.3 Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
34.2 Legal information. . . . . . . . . . . . . . . . . . . . . . 678 34.4 Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
34.2.1 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 678 34.5 Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
34.2.2 Disclaimers . . . . . . . . . . . . . . . . . . . . . . . . . . 678
34.2.3 Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . 678
708 Please be aware that important notices concerning this document and the product(s)
described herein, have been included in section ‘Legal information’.

For more information, please visit: http://www.nxp.com
For sales office addresses, please send an email to: [email protected]
Date of release: 5 September 2012
Document identifier: UM10211

LPC2378 PDF

Uploaded by

Copyright:

Available Formats

LPC2378 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LPC2378 PDF

Uploaded by

Copyright:

Available Formats

UM10211

LPC23XX User manual

User manual Rev. 4.1 — 5 September 2012 2 of 708

Revision history …continued

User manual Rev. 4.1 — 5 September 2012 3 of 708

1.2 How to read this manual

Table 1. LPC23xx overview

1.3.1 General features

User manual Rev. 4.1 — 5 September 2012 3 of 708

User manual Rev. 4.1 — 5 September 2012 4 of 708

1.3.2 Features available on LPC2361/62

1.3.3 Features available in LPC2377/78 and LPC2388

1.3.4 Features available in LPC2387 and LPC2388

User manual Rev. 4.1 — 5 September 2012 5 of 708

Table 2. LPC23xx features overview

1.5 Ordering information and options

• Table 4 for LPC2361/62 parts.

Table 3. LPC23xx ordering information

User manual Rev. 4.1 — 5 September 2012 6 of 708

Table 3. LPC23xx ordering information …continued

Table 4. LPC2361/62 Ordering options

LPC2361FBD100 64 8 16[1] 8 2 34 - yes yes 2 6 1 40 C to +85 C

[1] Available as general purpose SRAM for the LPC2361.

Table 5. LPC2364/65/66/67/68 Ordering options

User manual Rev. 4.1 — 5 September 2012 7 of 708

Table 6. LPC2377/78 ordering options

Table 7. LPC2387 ordering options

Table 8. LPC2388 ordering options

LPC2388FBD144 512 64 16 16 2 98 MiniBus: 8 data, 16 RMII yes 2 yes yes 8 1 40 C to

1.6 Architectural overview

User manual Rev. 4.1 — 5 September 2012 8 of 708

1.7 ARM7TDMI-S processor

The ARM7TDMI-S processor also employs a unique architectural strategy known as

• The standard 32 bit ARM instruction set.

User manual Rev. 4.1 — 5 September 2012 9 of 708

1.8 On-chip flash memory system

1.9 On-chip Static RAM

User manual Rev. 4.1 — 5 September 2012 10 of 708

1.10 Block diagram

MASTER AHB TO SLAVE USB WITH

6 × AD0 A/D CONVERTER TXD0, TXD2, TXD3

AOUT D/A CONVERTER TXD1

(1) LPC2362 only.

User manual Rev. 4.1 — 5 September 2012 11 of 708

6 × AD0 A/D CONVERTER MCICLK, MCIPWR

SCL0, SCL1, SCL2

(1) LPC2367/68 only.

User manual Rev. 4.1 — 5 September 2012 12 of 708

TRST TCK TDO RESET VDDA

EINT3 to EINT0 I2SRX_CLK

8 × AD0 A/D CONVERTER MCICLK, MCIPWR

SCL0, SCL1, SCL2

(1) LPC2378 only.

User manual Rev. 4.1 — 5 September 2012 13 of 708

MASTER AHB TO SLAVE USB WITH

6 × AD0 A/D CONVERTER MCICLK, MCIPWR

WATCHDOG TIMER RD1, RD2

SCL0, SCL1, SCL2

Fig 4. LPC2387 block diagram