32-bit Arm Cortex®-M3 microcontroller; up to 512 kB flash and
64 kB SRAM with Ethernet, USB 2.0 Host/Device/OTG, CAN
Rev. 9.8 — 4 May 2018Product data sheet
1. General description
The LPC1769/68/67/66/65/64/63 are ARM Cortex-M3 based microcontrollers for
embedded applications featuring a high level of integration and low power consumption.
The Arm Cortex-M3 is a next generation core that offers system enhancements such as
enhanced debug features and a higher level of support block integration.
The LPC1768/67/66/65/64/63 operate at CPU frequencies of up to 100 MHz. The
LPC1769 operates at CPU frequencies of up to 120 MHz. The Arm Cortex-M3 CPU
incorporates a 3-stage pipeline and uses a Harvard arc hit ec tu re with s eparate loca l
instruction and data buses as well as a third bus for peripher als. The Arm Cortex-M3 CPU
also includes an internal prefetch unit that supports speculative branching.
The peripheral complement of the LPC1769/68/67 /66/65/64/63 includes up to 512 kB of
flash memory, up to 64 kB of data memory, Ethernet MAC, USB Device/Host/OTG
interface, 8-channel general purpose DMA controller, 4 UARTs, 2 CAN channels, 2 SSP
controllers, SPI interface, 3 I
8-channel 12-bit ADC, 10-bit DAC, motor control PWM, Quadrature Encoder interface,
four general purpose timers, 6-output general purpose PWM, ultra-low power Real-Time
Clock (RTC) with separate battery supply, and up to 70 general purpose I/O pins.
The LPC1769/68/67/66/65/64/63 are pin-co mpatible to the 100-pi n LPC236x Arm7-base d
microcontroller series.
For additional documentation, see Section 19 “
2. Features and benefits
Arm Cortex-M3 processor, running at frequencies of up to 100 MHz
(LPC1768/67/66/65/64/63) or of up to 120 MHz (LPC1769) . A Memory Pro tection Unit
(MPU) supporting eight regions is included.
Arm Cortex-M3 built-in Nested Vectored Interrupt Controller (NVIC).
Up to 512 kB on-chip flash programming memory. Enhanced flash memory accelerator
enables high-speed 120 MHz operation with zero wait states.
In-System Programming (ISP) and In-Application Programming (IAP) via on-chip
bootloader software.
On-chip SRAM includes:
32/16 kB of SRAM on the CPU with local code/data bus for high-performance CPU
access.
2
C-bus interfaces, 2-input plus 2-output I2S-bus interface,
References”.
NXP Semiconductors
Eight channel General Purpose DMA controller (GPDMA) on the AHB multilayer
Multilayer AHB matrix interconnect provides a separate bus for each AHB master.
Split APB bus allows high throughput with few stalls between the CPU and DMA.
Serial interfaces:
Other peripherals:
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
Two/one 16 kB SRAM blocks with separate access paths for higher throughput.
These SRAM blocks may be used for Ethernet, USB, and DMA memory, as well as
for general purpose CPU instruction and data storage.
matrix that can be used with SSP, I
Digital-to-Analog converter peripherals, timer match signals, and for
memory-to-memory transfers.
AHB masters include the CPU, General Purpose DMA controller, Ethernet MAC, and
the USB interface. This interconnect provides communication with no arbitration
delays.
Ethernet MAC with RMII interface and dedicated DMA controller. (Not available on
all parts, see Table 2
.)
USB 2.0 full-speed device/Host/OTG controller with de dic at ed DMA contr o ller and
on-chip PHY for device, Host, and OTG functions. (Not available on all parts, see
Table 2
.)
Four UARTs with fractional baud rate generation, internal FIFO, and DMA support.
One UART has modem control I/O and RS-485/EIA-485 support, and one UART
has IrDA support.
CAN 2.0B controller with two channels. (Not available on all parts, see Table 2
SPI controller with synchronous, serial, full duplex communication and
programmable data length.
Two SSP controllers with FIFO and multi-protocol capabilities. The SSP interfaces
can be used with the GPDMA controller.
Three enhanced I
2
I
C specification and Fast mode plus with data rates of 1 Mbit/s, two with standard
2
C bus interfaces, one with an open-drain output supporting full
port pins. Enhancements include multiple address recognition and monitor mode.
2
I
S (Inter-IC Sound) interface for digital audio input or output, with fractional rate
control. The I
2
S-bus interface can be used with the GPDMA. The I2S-bus interface
supports 3-wire and 4-wire data transmit and receive as well as master clock
input/output. (Not available on all parts, see Table 2
70 (100 pin package) General Purpose I/O (GPIO) pins with configurable
pull-up/down resistors. All GPIOs support a new , configurable o pen-drain operating
mode. The GPIO block is accessed through the AHB multilayer bus for fast access
and located in memory such that it supports Cortex-M3 bit banding and use by the
General Purpose DMA Controller.
12-bit Analog-to-Digital Converter (ADC) with input multiplexing among eight pins,
conversion rates up to 200 kHz, and multiple result registers. The 12-bit ADC can
be used with the GPDMA controller.
10-bit Digital-to-Analog Converter (DAC) with dedicated conversion timer and DMA
support. (Not available on all parts, see Table 2
Four general purpose timers/counters, with a total of eight capture inputs and ten
compare outputs. Each timer block has an external count input. Specific timer
events can be selected to generate DMA requests.
One motor control PWM with support for three-phase motor control.
Four reduced power modes: Sleep, Deep-sleep, Power-down, and Deep power-down.
Single 3.3 V power supply (2.4 V to 3.6 V).
Four external interrupt inputs configurable as edge/level sensitive. All pins on Port 0
Non-maskable Interrupt (NMI) input.
Clock output function that can reflect the main oscillator clock, IRC clock, RTC clock,
The Wake-up Interrupt Controller (WIC) allows the CPU to automatically wake up from
Processor wake-up from Power-down mode via any interrupt able to operate during
Brownout detect with separate threshold for interrupt and forced reset.
Power-On Reset (POR).
Crystal oscillator with an operating range of 1 MHz to 25 MHz.
4 MHz internal RC oscillator trimmed to 1 % accuracy that can optionally be used as a
PLL allows CPU operation up to the maximum CPU rate without the need for a
USB PLL for added flexibility.
Code Read Protection (CRP) with different security levels.
Unique device serial number for identification purposes.
Available as LQFP100 (14 mm 14 mm 1.4 mm), TFBGA100
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
Quadrature encoder interface that can monitor one external quadrature encoder.
One standard PWM/timer block with external count input.
RTC with a separate power domain and dedicated RTC oscillator. The RTC block
includes 20 bytes of battery-powered backup registers.
WatchDog Timer (WDT). The WDT can be clocked from the internal RC oscillator,
the RTC oscillator, or the APB clock.
Arm Cortex-M3 system tick timer, including an external clock input option.
Repetitive interrupt timer provides programmable and repeating timed interrupts.
Each peripheral has its own clock divider for further power savings.
and Serial Wire Trace Port options. Boundary Scan Description Language (BSDL) is
not available for this device.
instruction execution.
minimize power consumption during Sleep, Deep sleep, Power-down, and Deep
power-down modes.
and Port 2 can be used as edge sensitive interrupt sources.
CPU clock, and the USB clock.
any priority interrupt that can occur while the clocks are stopped in deep sleep,
Power-down, and Deep power-down modes.
Power-down mode (includes external interrupts, RTC interrupt, USB activity, Ethernet
wake-up interrupt, CAN bus activity, Port 0/2 pin interrupt, and NMI).
system clock.
high-frequency crystal. May be run from the main oscillator, the internal RC oscillator,
or the RTC oscillator.
1
(9 mm 9 mm 0.7
mm), and WLCSP100 (5.07 5.07 0.53 mm) package.
The LPC176x devices typically have the following top-side marking:
LPC176xxxx
xxxxxxx
xxYYWWR[x]
The last/second to last letter in the third line (field ‘R’) will identify the device revision. This
data sheet covers the following revisions of the LPC176x:
P0[0] to P0[31]I/OPort 0: Port 0 is a 32-bit I/O port with individual direction controls for
P0[0]/RD1/TXD3/
SDA1
P0[1]/TD1/RXD3/
SCL1
P0[2]/TXD0/AD0[7] 98C4B1
P0[3]/RXD0/AD0[6] 99A2C3
LQFP100
TFBGA100
WLCSP100
46K8H10
47J8H9
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.
[1]
I/OP0[0] — General purpose digital input/output pin.
IRD1 — CAN1 receiver input. (LPC1769/68/66/65/64 only).
OTXD3 — Transmitter output for UART3.
2
I/OSDA1 — I
C1 data input/output. (This is not an I2C-bus compliant
open-drain pin).
[1]
I/OP0[1] — General purpose digital input/output pin.
OTD1 — CAN1 transmitter output. (LPC1769/68/66/65/64 only).
IRXD3 — Receiver input for UART3.
2
I/OSCL1 — I
C1 clock input/output. (This is not an I2C-bus compliant
open-drain pin).
[2]
I/OP0[2] — General purpose digital input/output pin.
OTXD0 — Transmitter output for UART0.
IAD0[7] — A/D converter 0, input 7.
[2]
I/OP0[3] — General purpose digital input/output pin.
IRXD0 — Receiver input for UART0.
IAD0[6] — A/D converter 0, input 6.
I/OP0[6] — General purpose digital input/output pin.
I/OI2SRX_SDA — Receive data. It is driven by the transmitter and read
by the receiver. Corresponds to the signal SD in the I
specification. (LPC1769/68/67/66/65/63 only).
I/OSSEL1 — Slave Select for SSP1.
OMAT2[0] — Match output for Timer 2, channel 0.
[1]
P0[7]/
I2STX_CLK/
SCK1/MAT2[1]
78A9J1
I/OP0[7] — General purpose digital input/output pin.
I/OI2STX_CLK — Transmit Clock. It is driven by the master and
received by the slave. Corresponds to the signal SCK in the I
specification. (LPC1769/68/67/66/65/63 only).
I/OSCK1 — Serial Clock for SSP1.
OMAT2[1] — Match output for Timer 2, channel 1.
[1]
P0[8]/
I2STX_WS/
MISO1/MAT2[2]
77C8H2
I/OP0[8] — General purpose digital input/output pin.
I/OI2STX_WS — Transmit Word Select. It is driven by the master and
received by the slave. Corresponds to the signal WS in the I
specification. (LPC1769/68/67/66/65/63 only).
I/OMISO1 — Master In Slave Out for SSP1.
OMAT2[2] — Match output for Timer 2, channel 2.
[1]
P0[9]/
I2STX_SDA/
MOSI1/MAT2[3]
76A10 H3
I/OP0[9] — General purpose digital input/output pin.
I/OI2STX_SDA — Transmit data. It is driven by the transmitter and
read by the receiver. Corresponds to the signal SD in the I
specification. (LPC1769/68/67/66/65/63 only).
I/OMOSI1 — Master Out Slave In for SSP1.
OMAT2[3] — Match output for Timer 2, channel 3.
[1]
P0[10]/TXD2/
SDA2/MAT3[0]
48H7H8
I/OP0[10] — General purpose digital input/output pin.
OTXD2 — Transmitter output for UART2.
I/OSDA2 — I
OMAT3[0] — Match output for Timer 3, channel 0.
2
S-bus
2
2
C2 data input/output (this is not an open-drain pin).
I/OP0[11] — General purpose digital input/output pin.
IRXD2 — Receiver input for UART2.
I/OSCL2 — I
OMAT3[1] — Match output for Timer 3, channel 1.
[1]
P0[15]/TXD1/
SCK0/SCK
62F10 H6
I/OP0[15] — General purpose digital input/output pin.
OTXD1 — Transmitter output for UART1.
I/OSCK0 — Serial clock for SSP0.
I/OSCK — Serial clock for SPI.
[1]
P0[16]/RXD1/
SSEL0/SSEL
63F8J5
I/OP0[16] — General purpose digital input/output pin.
IRXD1 — Receiver input for UART1.
I/OSSEL0 — Slave Select for SSP0.
I/OSSEL — Slave Select for SPI.
[1]
P0[17]/CTS1/
MISO0/MISO
61F9K6
I/OP0[17] — General purpose digital input/output pin.
ICTS1 — Clear to Send input for UART1.
I/OMISO0 — Master In Slave Out for SSP0.
I/OMISO — Master In Slave Out for SPI.
[1]
P0[18]/DCD1/
MOSI0/MOSI
60F6J6
I/OP0[18] — General purpose digital input/output pin.
IDCD1 — Data Carrier Detect input for UART1.
I/OMOSI0 — Master Out Slave In for SSP0.
I/OMOSI — Master Out Slave In for SPI.
[1]
P0[19]/DSR1/
SDA1
59G10 K7
I/OP0[19] — General purpose digital input/output pin.
IDSR1 — Data Set Ready input for UART1.
I/OSDA1 — I
open-drain pin).
[1]
P0[20]/DTR1/SCL1 58G9J7
I/OP0[20] — General purpose digital input/output pin.
ODTR1 — Data Termina l Ready output for UART1. Can also be
configured to be an RS-485/EIA-485 output enable signal.
I/OSCL1 — I
open-drain pin).
[1]
P0[21]/RI1/RD157G8H7
I/OP0[21] — General purpose digital input/output pin.
IRI1 — Ring Indicator input for UART1.
IRD1 — CAN1 receiver input. (LPC1769/68/66/65/64 only).
[1]
P0[22]/RTS1/TD156H10 K8
I/OP0[22] — General purpose digital input/output pin.
ORTS1 — Request to Send output for UART1. Can also be
configured to be an RS-485/EIA-485 output enable signal.
OTD1 — CAN1 transmitter output. (LPC1769/68/66/65/64 only).
2
C2 clock input/output (this is not an open-drain pin).
2
C1 data input/output (this is not an I2C-bus compliant
2
C1 clock input/output (this is not an I2C-bus compliant
I/OP0[24] — General purpose digital input/output pin.
IAD0[1] — A/D converter 0, input 1.
I/OI2SRX_WS — Receive Word Select. It is driven by the master and
received by the slave. Corresponds to the signal WS in the I
I/OP0[25] — General purpose digital input/output pin.
IAD0[2] — A/D converter 0, input 2.
I/OI2SRX_SDA — Receive data. It is driven by the transmitter and read
by the receiver. Corresponds to the signal SD in the I
specification. (LPC1769/68/67/66/65/63 only).
OTXD3 — Transmitter output for UART3.
[3]
P0[26]/AD0[3]/
AOUT/RXD3
6D3C5
I/OP0[26] — General purpose digital input/output pin.
IAD0[3] — A/D converter 0, input 3.
OAOUT — DAC output (LPC1769/68/67/66/65/63 only).
IRXD3 — Receiver input for UART3.
[4]
P0[27]/SDA0/
USB_SDA
25J2C8
I/OP0[27] — General purpose digital inpu t/output pin. Output is
open-drain.
I/OSDA0 — I
compliance).
I/OUSB_SDA — USB port I
LPC1769/68/66/65 only).
[4]
P0[28]/SCL0/
USB_SCL
24J1B9
I/OP0[28] — General purpose digital inpu t/output pin. Output is
open-drain.
I/OSCL0 — I
compliance).
I/OUSB_SCL — USB port I
LPC1769/68/66/65 only).
[5]
P0[29]/USB_D+29J3B10
I/OP0[29] — General purpose digital input/output pin.
I/OUSB_D+ — USB bidirectional D+ line. (LPC1769/68/66/65/64 only).
[5]
P0[30]/USB_D30G4C9
I/OP0[30] — General purpose digital input/output pin.
I/OUSB_D — USB bidirectional D line. (LPC1769/68/66/65/64 only).
2
2
S-bus
2
C0 data input/output. Open-drain output (for I2C-bus
I/OP1[20] — General purpose digital input/output pin.
IMCI0 — Motor control PWM channel 0, input. Also Quadrature
Encoder Interface PHA input.
OPWM1[2] — Pulse Width Modulator 1, channel 2 output.
I/OSCK0 — Serial clock for SSP0.
P1[21]/MCABORT
PWM1[3]/
SSEL0
/
35F5E9
[1]
I/OP1[21] — General purpose digital input/output pin.
OMCABORT
OPWM1[3] — Pulse Width Modulator 1, channel 3 output.
I/OSSEL0 — Slave Select for SSP0.
[1]
P1[22]/MCOB0/
USB_PWRD/
MAT1[0]
36J5D10
I/OP1[22] — General purpose digital input/output pin.
OMCOB0 — Motor control PWM channel 0, output B.
IUSB_PWRD — Power Status for USB port (host power switch,
LPC1769/68/66/65 only).
OMAT1[0] — Match output for Timer 1, channel 0.
[1]
P1[23]/MCI1/
PWM1[4]/MISO0
37K5E7
I/OP1[23] — General purpose digital input/output pin.
IMCI1 — Motor control PWM channel 1, input. Also Quadrature
Encoder Interface PHB input.
OPWM1[4] — Pulse Width Modulator 1, channel 4 output.
I/OMISO0 — Master In Slave Out for SSP0.
[1]
P1[24]/MCI2/
PWM1[5]/MOSI0
38H5F8
I/OP1[24] — General purpose digital input/output pin.
IMCI2 — Motor control PWM channel 2, input. Also Quadrature
Encoder Interface INDEX input.
OPWM1[5] — Pulse Width Modulator 1, channel 5 output.
I/OMOSI0 — Master Out Slave in for SSP0.
I/OP1[25] — General purpose digital input/output pin.
OMCOA1 — Motor control PWM channel 1, output A.
OMAT1[1] — Match output for Timer 1, channel 1.
[1]
P1[26]/MCOB1/
PWM1[6]/CAP0[0]
40K6E10
I/OP1[26] — General purpose digital input/output pin.
OMCOB1 — Motor control PWM channel 1, output B.
OPWM1[6] — Pulse Width Modulator 1, channel 6 output.
ICAP0[0] — Capture input for Timer 0, channel 0.
P1[27]/CLKOUT
/USB_OVRCR
CAP0[1]
43K7G9
/
[1]
I/OP1[27] — General purpose digital input/output pin.
OCLKOUT — Clock output pin.
IUSB_OVRCR
— USB port Over-Current status. (LPC1769/68/66/65
only).
ICAP0[1] — Capture input for Timer 0, channel 1.
[1]
P1[28]/MCOA2/
PCAP1[0]/
MAT0[0]
44J7G10
I/OP1[28] — General purpose digital input/output pin.
OMCOA2 — Motor control PWM channel 2, output A.
IPCAP1[0] — Capture input for PWM1, channel 0.
OMAT0[0] — Match output for Timer 0, channel 0.
[1]
P1[29]/MCOB2/
PCAP1[1]/
MAT0[1]
45G6G8
I/OP1[29] — General purpose digital input/output pin.
OMCOB2 — Motor control PWM channel 2, output B.
IPCAP1[1] — Capture input for PWM1, channel 1.
OMAT0[1] — Match output for Timer 0, channel 1.
P1[30]/V
AD0[4]
BUS
/
21H1B8
[2]
I/OP1[30] — General purpose digital input/output pin.
IV
— Monitors the presence of USB bus power.
BUS
(LPC1769/68/66/65/64 only).
Note: This signal must be HIGH for USB reset to occur.
IAD0[4] — A/D converter 0, input 4.
[2]
P1[31]/SCK1/
AD0[5]
20F4C7
I/OP1[31] — General purpose digital input/output pin.
I/OSCK1 — Serial Clock for SSP1.
IAD0[5] — A/D converter 0, input 5.
P2[0] to P2[31]I/OPort 2: Port 2 is a 32-bit I/O port with individual direction controls for
each bit. The operation of port 2 pins depends upon the pin function
selected via the pin connect block. Pins 14 through 31 of this port
are not available.
[1]
P2[0]/PWM1[1]/
TXD1
75B9K1
I/OP2[0] — General purpose digital input/output pin.
OPWM1[1] — Pulse Width Modulator 1, channel 1 output.
OTXD1 — Transmitter output for UART1.
[1]
P2[1]/PWM1[2]/
RXD1
74B10 J2
I/OP2[1] — General purpose digital input/output pin.
OPWM1[2] — Pulse Width Modulator 1, channel 2 output.
IRXD1 — Receiver input for UART1.
I/OP2[2] — General purpose digital input/output pin.
OPWM1[3] — Pulse Width Modulator 1, channel 3 output.
ICTS1 — Clear to Send input for UART1.
OTRACEDATA[3] — Trace data, bit 3.
[1]
P2[3]/PWM1[4]/
DCD1/
TRACEDATA[2]
70E7K3
I/OP2[3] — General purpose digital input/output pin.
OPWM1[4] — Pulse Width Modulator 1, channel 4 output.
IDCD1 — Data Carrier Detect input for UART1.
OTRACEDATA[2] — Trace data, bit 2.
[1]
P2[4]/PWM1[5]/
DSR1/
TRACEDATA[1]
69D9J3
I/OP2[4] — General purpose digital input/output pin.
OPWM1[5] — Pulse Width Modulator 1, channel 5 output.
IDSR1 — Data Set Ready input for UART1.
OTRACEDATA[1] — Trace data, bit 1.
[1]
P2[5]/PWM1[6]/
DTR1/
TRACEDATA[0]
68D10 H4
I/OP2[5] — General purpose digital input/output pin.
OPWM1[6] — Pulse Width Modulator 1, channel 6 output.
ODTR1 — Data Termina l Ready output for UART1. Can also be
configured to be an RS-485/EIA-485 output enable signal.
OTRACEDATA[0] — Trace data, bit 0.
[1]
P2[6]/PCAP1[0]/
RI1/TRACECLK
67E8K4
I/OP2[6] — General purpose digital input/output pin.
IPCAP1[0] — Capture input for PWM1, channel 0.
IRI1 — Ring Indicator input for UART1.
OTRACECLK — Trace Clock.
[1]
P2[7]/RD2/
RTS1
66E9J4
I/OP2[7] — General purpose digital input/output pin.
IRD2 — CAN2 receiver input. (LPC1769/68/66/65/64 only).
ORTS1 — Request to Send output for UART1. Can also be
configured to be an RS-485/EIA-485 output enable signal.
[1]
P2[8]/TD2/
TXD2
65E10 H5
I/OP2[8] — General purpose digital input/output pin.
OTD2 — CAN2 transmitter output. (LPC1769/68/66/65/64 only).
OTXD2 — Transmitter output for UART2.
[1]
P2[9]/
USB_CONNECT/
RXD2
64F7K5
I/OP2[9] — General purpose digital input/output pin.
OUSB_CONNECT — Signal used to switch an external 1.5 k
resistor under software control. Used with the SoftConnect USB
feature. (LPC1769/68/66/65/64 only).
IRXD2 — Receiver input for UART2.
P2[10]/EINT0
/NMI53J10 K9
[6]
I/OP2[10] — General purpose digital input/output pin. A LOW level on
this pin during reset starts the ISP command handler.
IEINT0
I/OP2[11] — General purpose digital input/output pin.
IEINT1
— External interrupt 1 input.
I/OI2STX_CLK — Transmit Clock. It is driven by the master and
2
received by the slave. Corresponds to the signal SCK in the I
S-bus
specification. (LPC1769/68/67/66/65/63 only).
P2[12]/EINT2
I2STX_WS
/
51K10 K10
[6]
I/OP2[12] — General purpose digital input/output pin.
IEINT2
— External interrupt 2 input.
I/OI2STX_WS — Transmit Word Select. It is driven by the master and
2
received by the slave. Corresponds to the signal WS in the I
S-bus
specification. (LPC1769/68/67/66/65/63 only).
P2[13]/EINT3
I2STX_SDA
/
50J9J9
[6]
I/OP2[13] — General purpose digital input/output pin.
IEINT3
— External interrupt 3 input.
I/OI2STX_SDA — Transmit data. It is driven by the transmitter and
2
read by the receiver. Corresponds to the signal SD in the I
S-bus
specification. (LPC1769/68/67/66/65/63 only).
P3[0] to P3[31]I/OPort 3: Port 3 is a 32-bit I/O port with individual direction controls for
each bit. The operation of port 3 pins depends upon the pin function
selected via the pin connect block. Pins 0 through 24, and 27
through 31 of this port are not available.
[1]
P3[25]/MAT0[0]/
PWM1[2]
27H3D8
I/OP3[25] — General purpose digital input/output pin.
OMAT0[0] — Match output for Timer 0, channel 0.
OPWM1[2] — Pulse Width Modulator 1, output 2.
[1]
P3[26]/STCLK/
MAT0[1]/PWM1[3]
26K1A10
I/OP3[26] — General purpose digital input/output pin.
ISTCLK — System tick timer clock input. The maximum STCLK
frequency is 1/4 of the Arm processor clock frequency CCLK.
OMAT0[1] — Match output for Timer 0, channel 1.
OPWM1[3] — Pulse Width Modulator 1, output 3.
P4[0] to P4[31]I/OPort 4: Port 4 is a 32-bit I/O port with individual direction controls for
each bit. The operation of port 4 pins depends upon the pin function
selected via the pin connect block. Pins 0 through 27, 30, and 31 of
this port are not available .
[1]
P4[28]/RX_MCLK/
MAT2[0]/TXD3
82C7G1
I/OP4[28] — General purpose digital input/output pin.
2
ORX_MCLK — I
S receive master clock. (LPC1769/68/67/66/65
only).
OMAT2[0] — Match output for Timer 2, channel 0.
OTXD3 — Transmitter output for UART3.
[1]
P4[29]/TX_MCLK/
MAT2[1]/RXD3
85E6F1
I/OP4[29] — General purpose digital input/output pin.
2
OTX_MCLK — I
S transmit master clock. (LPC1769/68/67/66/65
only).
OMAT2[1] — Match output for Timer 2, channel 1.
IRXD3 — Receiver input for UART3.
VREFN15F1A6IADC negative reference voltage: This should be nominally the
same voltage as VSS but should be isolated to minimize noise and
error. Level on this pin is used as a reference for ADC and DAC.
[10][12]
VBAT19G2A8
IRTC pin power supply: 3.3 V on this pin supplies the power to the
RTC peripheral.
n.c.13D4, E4B6,
-not connected.
D6
[1] 5 V tolerant pad providing digital I/O functions with TTL levels and hysteresis. This pin is pulled up to a voltage level of 2.3 V to 2.6 V.
[2] 5 V tolerant pad providing digital I/O functions (with TTL levels and hysteresis) and analog input. When configured as a ADC input,
digital section of the pad is disabled and the pin is not 5 V tolerant. This pin is pulled up to a voltage level of 2.3 V to 2.6 V.
[3] 5 V tolerant pad providing digital I/O with TTL levels and hysteresis and analog output function. When configured as the DAC output,
digital section of the pad is disabled. This pin is pulled up to a voltage level of 2.3 V to 2.6 V.
[4] Open-drain 5 V tolerant digital I/O pad, compatible with I
output functionality. When power is switched off, this pin connected to the I
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). This pad is not 5 V tolerant.
[6] 5 V tolerant pad with 10 ns glitch filter providing digital I/O functions with TTL levels and hysteresis. This pin is pulled up to a voltage
level of 2.3 V to 2.6 V.
[7] 5 V tolerant pad with TTL levels and hysteresis. Internal pull-up and pull-down resistors disabled.
[8] 5 V tolerant pad with TTL levels and hysteresis and internal pull-up resistor.
[9] 5 V tolerant pad with 20 ns glitch filter providing digital I/O function with TTL levels and hysteresis.
[10] Pad provides special analog functionality. A 32 kHz crystal oscillator must be used with the RTC.
[11] When the system oscillator is not used, connect XTAL1 and XTAL2 as follows: XTAL1 can be left floating or can be grounded (grounding
is preferred to reduce susceptibility to noise). XTAL2 should be left floating.
[12] When the RTC is not used, connect VBAT to V
DD(REG)(3V3)
2
C-bus 400 kHz specification. This pad requires an external pull-up to provide
and leave RTCX1 floating.
2
C-bus is floating and does not disturb the I2C lines.
Remark: In the following, the notation LPC17xx refers to all parts:
LPC1769/68/67/66/65/64/63.
The Arm Cortex-M3 includes three AHB-Lite buses: the system bus, the I-code bus, and
the D-code bus (see Figure 1
system bus and are used similarly to TCM interfaces: one bus dedicated for instruction
fetch (I-code) and one bus for data access (D-c ode). The use of two core buses allows for
simultaneous operations if concurrent operations target different devices.
The LPC17xx use a multi-layer AHB matrix to connect the Arm Cortex-M3 buses and
other bus masters to peripherals in a flexible mann e r tha t op tim ize s pe rfo rm a nc e by
allowing peripherals that are on different slaves ports of the matrix to be accessed
simultaneously by different bus masters.
8.2 Arm Cortex-M3 processor
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
). The I-code and D-code core buses are faster than the
The Arm Cortex-M3 is a general purpose, 32-bit microprocessor, which offers hig h
performance and very low power consumption. The Arm Cortex-M3 offers many new
features, including a Thumb-2 instruction set, low interrupt latency, hardware divide,
interruptible/continuable multiple load and store instructions, automatic state save and
restore for interrupts, tightly integrated interrupt controller with wake-up interrupt
controller, and multiple core buses capable of simultaneous accesses.
Pipeline techniques are employed so that all part s of the pro cessing and memory systems
can operate continuously. Typically, while one instruction is being executed, its successor
is being decoded, and a third instruction is being fetched from memory.
The Arm Cortex-M3 processor is described in detail in the Cortex-M3 Technical Reference Manual that can be found on official Arm website.
8.3 On-chip flash program memory
The LPC17xx contain up to 512 kB of on-chip flash memory. A new two-port flash
accelerator maximizes performance for use with the two fast AHB-Lite buses.
8.4 On-chip SRAM
The LPC17xx contain a total of 64 kB on-chip st atic RAM memory. This includes the main
32 kB SRAM, accessible by the CPU and DMA controller on a higher-speed bus, and two
additional 16 kB each SRAM blocks situated on a separate slave port on the AHB
multilayer matrix.
This architecture allows CPU and DMA accesses to be spread over three separate RAMs
that can be accessed simultaneously.
8.5 Memory Protection Unit (MPU)
The LPC17xx have a Memory Protection Unit (MPU) which can be used to improve the
reliability of an embedded system by protecting critical data within the user application.
The MPU allows separating processing tasks by disallowing access to each other's data,
disabling access to memory regions, allowing memory regions to be defined as re ad -onl y
and detecting unexpected memory accesses that could potentially break the system.
The MPU separates the memory into distinct regions and implements protection by
preventing disallowed accesses. The MPU supports up to 8 regions each of which can be
divided into 8 subregions. Accesses to memory locations that are not defined in the MPU
regions, or not permitted by the region settin g , will ca use the Memory Management Fault
exception to take place.
8.6 Memory map
The LPC17xx incorporates several distinct memory regions, shown in the following
figures. Figure 5
program viewpoint following reset. The interrupt vector area supports address remapping.
The AHB peripheral area is 2 MB in size and is divided to allow for up to 128 peripherals.
The APB peripheral area is 1 MB in size and is divided to allow for up to 64 peripherals.
Each peripheral of either type is allocated 16 kB of space. This allows simplifying the
address decoding for each peripheral.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
shows the overall map of the entire address space from the user
xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxx x x x xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xx xx xxxxx
xxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxx xxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxx x x
xxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxx xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxx
The NVIC is an integral part of the Cortex-M3. The tight coup ling to the CPU allows for low
interrupt latency and efficient processing of late arriving interrupts.
8.7.1 Features
• Controls system exceptions and peripheral interrupts
• In the LPC17xx, the NVIC supports 33 vectored interrupts
Each peripheral device has one interrupt line con nected to the NVIC but may have several
interrupt flags. Individual interrupt flags may also represent more than one interrupt
source.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
Any pin on Port 0 and Port 2 (total of 42 pins) regardless of the selected function, can be
programmed to generate an interrupt on a rising edge, a falling edge, or both.
8.8 Pin connect block
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 interrupt(s) being enabled. Activity of any enabled peripheral function that is
not mapped to a related pin should be considered undefined.
Most pins can also be configured as open-drain outpu ts or to have a pull-up, pull- down, or
no resistor enabled.
8.9 General purpose DMA controller
The GPDMA is an AMBA AHB compliant peripheral allowing selected peripherals to have
DMA support.
The GPDMA enables peripheral-to-memory, memory-to-peripheral,
peripheral-to-peripheral, and memory-to-memory transactions. The source and
destination areas can each be either a memory region or a peripheral, and can be
accessed through the AHB master. The GPDMA controller allows data transfers between
the USB and Ethernet controllers and the various on-chip SRAM areas. The supported
APB peripherals are SSP0/1, all UARTs, the I
Two match signals for each timer can be used to trigger DMA transfers.
2
S-bus interface, the ADC, and the DAC.
Remark: The Ethernet controller is available on parts LPC1769/68/67/66/64. The USB
controller is available on parts LPC1769/68/66/65/64. The I
parts LPC1769/68/67/66/65. The DAC is available on parts LPC1769/68/67/66/65/63.
• Eight DMA channels. Each channel can support an unidirectional transfer.
• 16 DMA request lines.
• Single DMA and burst DMA request signals. Each peripheral connected to the DMA
• Memory-to-memory, memory-to-peripheral, peripheral-to-memory, and
• Scatter or gather DMA is supported through the use of linked lists. This means that
• Hardware DMA channel priority.
• AHB slave DMA programming interface. The DMA Controller is programmed by
• One AHB bus master for transferring data. The interface transfers data when a DMA
• 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
• Internal four-word FIFO per channel.
• Supports 8, 16, and 32-bit wide tra n sactions.
• Big-endian and little-endian support. The DMA Controller defaults to little-endian
• An interrupt to the processor can be generated on a DMA completion or when a DMA
• Raw interrupt status. The DMA error and DMA count raw interrupt status can be read
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
Controller can assert either a burst DMA request or a single DMA request. The DMA
burst size is set by programming the DMA Controller.
peripheral-to-peripheral transfers are supported.
the source and destination areas do not have to occupy contiguous areas of memory.
writing to the DMA control registers over the AHB slave interface.
request goes active.
efficiently transfer data.
mode on reset.
error has occurred.
prior to masking.
8.10 Fast general purpose parallel I/O
Device pins that are not connected to a specific peripheral function are controlled by the
GPIO registers. Pins may be dynamically configured as inputs or outputs. Separate
registers allow setting or clearing any nu mber of outputs simultaneously. The value of the
output register may be read back as well as the current state of the port pins.
LPC17xx use accelerated GPIO functions:
• GPIO registers are ac ce sse d th ro ug h the AHB mu ltilaye r bu s so th at th e fa ste st
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.
Additionally, any pin on Port 0 and Port 2 (total of 42 pins) providing a digital function can
be programmed to generate an interrupt on a rising edge, a falling edge, or both. The
edge detection is asynchronous, so it may operate when clocks are not present such as
during Power-down mode. Each enabled interrupt can be used to wake up the chip from
Power-down mode.
8.10.1 Features
• Bit level set and clear registers allow a single instruction to set or clear any number of
• Direction control of individual bits.
• All I/O default to inputs after reset.
• Pull-up/pull-down resistor configuration and open-drain configuration can be
8.11 Ethernet
Remark: The Ethernet controller is available on part s LPC1769/68/67/66/64. The
Ethernet block supports bus clock rates of up to 100 MHz (LPC1768/67/66/64) or 120
MHz (LPC1769). See Table 2
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
bits in one port.
programmed through the pin connect block for each GPIO pin.
.
The Ethernet block contains a full featured 10 Mbit/s or 100 Mbit/s Ethernet MAC
designed to provide optimized performance through the use of DMA hardware
acceleration. 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 the Arm Cortex-M3 D-code and system bus
through the AHB-multilayer matrix to access the various on-chip SRAM blocks for
Ethernet data, control, and status information.
The Ethernet block interfaces between an off-chip Ethernet PHY using the Reduced MII
(RMII) protocol and the on-chip Media Independent Interface Management (MIIM) serial
bus.
8.11.1 Features
• Ethernet standards support:
– Supports 10 Mbit/s or 100 Mbit/s 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.
– Virtual Local Area Network (VLAN) frame support.
• Memory management:
– Independent transmit and receive buffer s memory mapped to shared SRAM.
– DMA managers with scatter/gather DMA and arrays of frame descriptors.
– Memory traffic optimized by buffering and pre-fetching.
– Receive filtering.
– Multicast and broadcast frame support for both transmit and receive.
– Optional automatic Frame Check Sequence (FCS) insertion with Cyclic
Redundancy Check (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 back-off 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.
– Attachment of external PHY chip through stan dard RMII interface.
– PHY register access is available via the MIIM interface.
8.12 USB interface
Remark: The USB controller is available as device/Host/OTG controller on parts
LPC1769/68/66/65 and as device-only controller on part LPC1764.
The Universal Serial Bus (USB) is a 4-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 USB interface includes a device, Host, and OTG controller with on-chip PHY for
device and Host functions. The OTG switching protocol is supported through the use of an
external controller. Details on typical USB interfacing solutions can be found in
Section 15.1
8.12.1 USB device controller
The device controller enables 12 Mbit/s data exchange with a USB Host controller. It
consists of a register interface, serial interface engine, endpoint buffer memory, and a
DMA controller. The seria l interface eng ine decod es the USB dat a strea m and writes dat a
to the appropriate endpoint buffer. The status of a completed USB transfer or error
condition is indicated via status registers. An interrupt is also generated if enabled. When
enabled, the DMA controller transfers data between the endpoint buffer and the on-chip
SRAM.
.
8.12.1.1 Features
• Fully compliant with USB 2.0 specification (full speed).
• Supports 32 physical (16 logical) endpoints with a 4 kB endpoint buffer RAM.
• Supports Control, Bulk, Interrupt and Isochronous endpoints.
• Endpoint Maximum packet size selection (up to USB maximum specification) by
• Supports SoftConnect and GoodLink features.
• While USB is in the Suspend mode, the part can ente r one of the re du ce d power
• Supports DMA transfers with all on-c hip SRAM blo cks on all non-control endpoints.
• Allows dynamic switching between CPU-controlled slave and DMA modes.
• Double buffer implementation for Bulk and Isochronous endpoints.
8.12.2 USB host controller
The host controller enables full- and low-speed dat a exchange with USB devices attached
to the bus. It consists of a register interface, a serial interface engine, and a DMA
controller. The register interface complies with the OHCI specification.
8.12.2.1 Features
• OHCI compliant.
• One downstream port.
• Supports port power switchin g .
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
software at run time.
modes and wake up on USB activity.
8.12.3 USB OTG controller
USB OTG 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 OTG Controller integrates the host controller, device controller, and a master-only
2
C-bus interface to implement OTG dual-role device functionality. The dedicated I2C-bus
I
interface controls an external OTG transceiver.
8.12.3.1 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 Session Request Protocol
(SRP).
• Supports any OTG transceiver compliant with the OTG Transceiver Specification
(CEA-2011), Rev. 1.0.
8.13 CAN controller and acceptance filters
Remark: The CAN controllers are available on parts LPC1769/68/66/65/64. See Table 2.
The Controller Area Network (CAN) is a serial communications protocol which efficiently
supports distributed real-time control with a very high level of security. Its domain of
application ranges from high-speed networks to low cost multiplex wiring.
The CAN block is intended to support multiple CAN buses simultaneously, allowing the
device to be used as a gateway, switch, or router among a number of CAN buses in
industrial or automotive applications.
The LPC17xx each contain four UARTs. In addition to standard transmit and receive data
lines, UART1 also provides a full modem control handshake interface and support for
RS-485/9-bit mode allowing both software address detection and automatic address
detection using 9-bit mode.
The UARTs include a fractional baud rate generator. Standard baud rates such as
115200 Bd can be achieved with any crystal frequency above 2 MHz.
8.16.1 Features
• Maximum UART data bit rate of 6.25 Mbit/s.
• 16 B Receive and Transmit FIFOs.
• Register locations conform to 16C550 industry standard.
• Receiver FIFO trigger points at 1 B, 4 B, 8 B, and 14 B.
• Built-in fractional baud rate generator covering wide range of baud rates without a
• Auto baud capabilities and FIFO control mechanism that enables software flow
• UART1 equipped with standard modem interface signals. This module also provides
• Support for RS-485 /9 -b it/EIA-485 mode (UART1).
• UART3 includes an IrDA mode to support infrared communication.
• All UARTs have DMA support.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
need for external crystals of particular values.
control implementation.
full support for hardware flow control (auto-CTS/RTS).
8.17 SPI serial I/O controller
The LPC17xx contain one SPI controller. SPI is a full duplex serial interface designed to
handle multiple masters and slaves connected to a given bus. Only a single maste r and a
single slave can communicate on the interface during a given data transfer. During a data
transfer the master always sends 8 bits to 16 bits of data to the slave, and the slave
always sends 8 bits to 16 bits of data to the master.
8.17.1 Features
• Maximum SPI data bit rate of 12.5 Mbit/s
• Compliant with SPI specification
• Synchronous, serial, full duplex communication
• Combined SPI master and slave
• Maximum data bit rate of one eighth of the input clock rate
• 8 bits to 16 bits per transfer
8.18 SSP serial I/O controller
The LPC17xx contain two SSP controllers. The SSP controller is 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. The SSP supports full duplex transfers, with frames of 4 bits to 16 bits of
data flowing from the master to the slave and from the slave to the master. In practice,
often only one of these data flows carries meaningful data.
8.18.1 Features
• Maximum SSP speed of 33 Mbit/s (master) or 8 Mbit/s (slave)
• Compatible with Motorola SPI, 4-wire Texas Instruments SSI, and National
• Synchronous serial communication
• Master or slave operation
• 8-frame FIFOs for both transmit and receive
• 4-bit to 16-bit frame
• DMA transfers supporte d by GP DMA
8.19 I2C-bus serial I/O controllers
The LPC17xx each contain three I2C-bus controllers.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
Semiconductor Microwire buses
2
C-bus is bidirectional for inter-IC control using only two wires: a Serial Clock line
The I
(SCL) and a Serial DAta line (SDA). Each device is recognized by a unique address and
can operate as either a receiver-only device (e.g., an LCD driver) or a tra nsmitter with the
capability to both receive and send information (such as memory). Transmitters and/or
receivers can operate in either master or sla ve mode, de pendin g on wheth er the chip has
to initiate a data transfer or is only addressed. The I
controlled by more than one bus master connected to it.
8.19.1 Features
2
• I
C0 is a standard I2C compliant bus interface with open-drain pins. I2C0 also
supports Fast mode plus with bit rates up to 1 Mbit/s.
2
• I
C1 and I2C2 use standard I/O pins with bit rates of up to 400 kbit/s (Fast I2C-bus).
• Easy to configure as master, slave, or master/slave.
Remark: The I2S-bus interface is available on parts LPC1769/68/67/66/65/63. See
Table 2
The I
The I
and one word select signal. The basic I
always the master , and one sla ve. The I
receive channel, each of which can operate as either a master or a slave.
8.20.1 Features
• The interface has separate input/output channels each of which can operate in master
• Capable of handling 8-bit, 16-bit, and 32-bit word sizes.
• Mono and stereo audio data supported.
• The sampling frequency can range from 16 kHz to 96 kHz (16, 22.05, 32, 44.1, 48,
• Support for an audio ma st er clock.
• Configurable word select period in master mode (separately for I
• Two 8-word 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
• Controls include reset, stop and mute options separately for I
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
.
2
S-bus provides a standard communication interface for digital audio applications.
2
S-bus specification defines a 3-wire serial bus using one data line, one clock line,
or slave mode.
96) kHz.
output).
to the GPDMA block.
output.
2
S-bus connection has one master, which is
2
S-bus interface provides a separate transmit and
2
S-bus input and
2
S-bus input and I2S-bus
8.21 General purpose 32-bit timers/external event counters
The LPC17xx include four 32-bit timer/counters. The timer/counter is designed to count
cycles of the system derived clock or an externally-supplied clock. It can optionally
generate interrupts, generate timed DMA requests, or perform other actions at specified
timer values, based on four match registers. Each timer/counter also includes two capture
inputs to trap the timer value when an input signal transitions, optionally generating an
interrupt.
8.21.1 Features
• A 32-bit timer/counter with a programmable 32-bit prescaler.
• Counter or timer oper a tion .
• Two 32-bit capture channels per timer, that can take a snapshot of the timer value
when an input signal transitions. A capture event may also generate an interrupt.
• Four 32-bit match re gist er s tha t allo w:
– Continuous operation with optional interrupt generation on match.
– St op 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
• Up to two match registers can be used to generate timed DMA requests.
8.22 Pulse width modulator
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 LPC17xx. The Timer is designed to count
cycles of the system derived clock and optionally switch pins, generate interrupts or
perform other actions when specified timer values occur , based on se ven 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.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
capabilities:
– Set LOW on match.
– Set HIGH on match.
– Toggle on match.
– Do nothing on match.
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 re gister 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).
8.22.1 Features
• One PWM block with Counter or Timer ope ration (may use the peripheral clock or on e
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.
– St op 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
• Pulse period and width can be any number of timer counts. This allows complete
• Double edge controlled PWM outputs can be programmed to be either positive going
• Match register updates are synchronized with pulse outputs to prevent generation of
• May be used as a standard 32-bit timer/counter with a programma ble 32-bit pre scaler
8.23 Motor control PWM
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
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.
flexibility in the trade-off between resolution and repetition rate. All PWM outputs will
occur at the same repetition rate.
or negative going pulses.
erroneous pulses. Software must ‘release’ new match values before they can b ecome
effective.
if the PWM mode is not enabled.
The motor control PWM is a specialized PWM supporting 3-phase motors and other
combinations. Feedback inputs are provided to automatically sense rotor position and use
that information to ramp speed up or down. An abort input is also provided that causes the
PWM to immediately release all motor drive outputs. At the same time, the motor control
PWM is highly configurable for other generalized timing, counting, capture, and compare
applications.
8.24 Quadrature Encoder Interface (QEI)
A quadrature encoder, also known as a 2-channel incremental encoder, converts angular
displacement into two pulse signals. By monitoring both the number of pulses and the
relative phase of the two signals, the user ca n tr ack th e position, d ire ction of r otation, and
velocity. In addition, a third channel, or index signal, can be used to reset the position
counter. The quadrature encoder interface decodes the digital pulses from a quadrature
encoder wheel to integrate position over time and determine direction of rotation. In
addition, the QEI can capture the velocity of the encoder wheel.
8.24.1 Features
• Tracks encoder position.
• Increments/decrements depending on direction.
• Programmable for 2 or 4 position counting.
• Velocity capture using built-in timer.
• Velocity compare function with “less than” interrupt.
• Uses 32-bit register s for pos ition an d ve locity.
• Three position compare regis te rs with inte rr up ts.
• Index counter for revolution counting.
• Index compare register w ith int er ru p ts.
• Can combine index and position interrupts to produce an interrupt for whole and
• Digital filter with programmable delays for encoder input signals.
• Can accept decoded signal inputs (clk and direction).
• Connected to APB.
8.25 Repetitive Interrupt (RI) timer
The repetitive interrupt timer provides a free-running 32-bit counter which is compared to
a selectable value, generating an interrupt when a match occurs. Any bits of the
timer/compare can be masked such that they do no t contribute to the match detection.
The repetitive interrupt timer can be used to create an interrupt that repeats at
predetermined intervals.
8.25.1 Features
• 32-bit counter running from PCLK. Counter can be free-running or be reset by a
• 32-bit compare value.
• 32-bit compare mask. An interrupt is generated when the counter value equals the
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
generated interrupt.
compare value, after masking. This allows for combinations not possible with a simple
compare.
8.26 Arm Cortex-M3 system tick timer
The Arm Cortex-M3 includes a system tick timer (SYSTICK) that is intended to generate a
dedicated SYSTICK exception at a 10 ms interval. In the LPC17xx, this timer can be
clocked from the internal AHB clock or from a device pin.
8.27 Watchdog timer
The purpose of the watchdog is to reset the microcontroller within a reasonable amoun t 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.
8.27.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 prescaler.
• Selectable time period from (T
multiples of T
cy(WDCLK)
4.
cy(WDCLK)
• The Watchdog Clock (WDCLK) source can be selected from the Internal RC (IRC)
oscillator, the RTC oscillator, or the APB peripheral clock. This gives a wide range of
potential timing choices of Watchdog operation under different power reduction
The RTC is a set of counters for measuring ti me when system power is on, and op tionally
when it is off. The RTC on the LPC17xx is designed to have extremely low power
consumption, i.e. less than 1 A. The RTC will typically run from the main chip power
supply, conserving battery power while the rest of the device is powered up. When
operating from a battery, the RTC will continue working down to 2.1 V. Battery power can
be provided from a standard 3 V Lithium button cell.
An ultra-low power 32 kHz oscillator will provide a 1 Hz clock to the time counting portion
of the RTC, moving most of the power consumption out of the time counting function.
The RTC includes a calibration mechanism to allow fine-tuning the count rate in a way
that will provide less than 1 second per day error when operated at a constant voltage and
temperature. A clock output function (see Section 8.29.4
rate easy and accurate.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
conditions. It also provides the ability to run the WDT from an entirely internal source
that is not dependent on an external cryst al and it s associated component s and wiring
for increased reliability.
) makes measuring the oscillator
The RTC contains a small set of backup registers (20 bytes) for holding data while the
main part of the LPC17xx is powered off.
The RTC includes an alarm function that can wake up the LPC17xx from all reduced
power modes with a time resolution of 1 s.
8.28.1 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 power supply pin can be connected to a battery or to the main 3.3 V.
• Periodic interrupts can be generated from increment s of a ny field of th e time registe rs.
• Backup registers (20 by te s) po we re d by VBAT.
• RTC power supply is isolated from the rest of the chip.
8.29 Clocking and power control
8.29.1 Crystal oscillators
The LPC17xx include three independent oscillators. These are the main oscillator , the IRC
oscillator, and the RTC oscillator. Each oscillator can be used for more than one purpose
as required in a particular application. Any of the three clock sources can be chosen by
software to drive the main PLL and ultimately the CPU.
Following reset, the LPC17xx will operate from the Internal RC oscillator until switched by
software. This allows systems to operate without any external crystal and the bootloader
code to operate at a known frequency.
See Figure 6 for an overview of the LPC17xx clock generation.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
Fig 6.LPC17xx clocking generation block diagram
8.29.1.1 Internal RC oscillator
The IRC may be used as the clock source for the WDT, and/or as the clock that drives the
PLL and subsequently the CPU. The nominal IRC frequency is 4 MHz. The IRC is
trimmed to 1 % accuracy over the entire voltage and temperature range.
Upon power-up or any chip reset, the LPC17xx use the IRC as the clock sour ce. Sof tware
may later switch to one of the other available clock sources.
8.29.1.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 also provides the clock source for the dedicated USB PLL.
The main oscillator operates at frequencies of 1 MHz to 25 MHz. This frequency can be
boosted to a higher frequency, up to the maximum CPU operating frequency, by the main
PLL. The clock selected as the PLL input is PLLCLKIN. The Arm processor clock
frequency is referred to as CCLK elsewhere in this document. The frequencies of
PLLCLKIN and CCLK are the same value unless the PLL is active and connected. The
clock frequency for each peripheral can be selected individually and is referred to as
PCLK. Refer to Section 8.29.2
8.29.1.3 RTC oscillator
The RTC oscillator can be used as the clock source for the RTC block, the main PLL,
and/or the CPU.
The PLL0 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/or the USB block.
The PLL0 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 wide range
of output frequencies from the same input frequency.
Following the PLL0 input divider is the PLL0 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.
The PLL0 is turned off and bypassed following a chip Reset and by entering Power -down
mode. PLL0 is enabled by software only. The program must configure and activate the
PLL0, wait for the PLL0 to lock, and then connect to the PLL0 as a clock source.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
8.29.3 USB PLL (PLL1)
The LPC17xx contain a second, dedicated USB PLL1 to provide clocking for the USB
interface.
The PLL1 receives its clock input from the main oscillator only and provides a fixed
48 MHz clock to the USB block only. The PLL1 is disabled and powered of f on reset. If the
PLL1 is left disabled, the USB clock will be supplied by the 48 MHz clock from the main
PLL0.
The PLL1 accepts an input clock frequency in the range of 10 MHz to 25 MHz only. The
input frequency is multiplied up the range of 48 MHz for the USB clock using a Current
Controlled Oscillators (CCO). It is insured that the PLL1 output has a 50 % duty cycle.
8.29.4 RTC clock output
The LPC17xx feature a clock output function intended for synchronizing with external
devices and for use during system development to allow checking the internal clocks
CCLK, IRC clock, main crystal, RTC clock, and USB clock in the outside world. The RTC
clock output allows tuning the RTC frequency without probing the pin, which would distort
the results.
8.29.5 Wake-up timer
The LPC17xx begin operation at power-up and when awakened from Power-down mode
by using the 4 MHz IRC oscillator as the clock source. This allows chip operation to
resume quickly . If the main oscillator or the PLL is needed by the application, sof tware 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 wake-up timer allows sof twa re 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 rea son. Since the
oscillator and other functions are turned off during Power-down mode, any wake-up of the
processor from Power-down mode makes use of the wake-up timer.
The Wake-up Timer monitors the crystal oscillator to check whether it is safe to begin
code execution. When power is applied to the chip, or when 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 man y factors,
including the rate of V
electrical characteristics (if a quartz cryst al is used) , as well as any other external circuitry
(e.g., capacitors), and the characteristics of the oscillator itself under the existing ambient
conditions.
8.29.6 Power control
The LPC17xx support a variety of power control features. Th ere are four special modes of
processor power reduction: Sleep mode, Deep-sleep mode, Power-down mode, and
Deep power-down mode. The CPU clock rate may also be controlled as needed by
changing clock sources, reconfiguring PLL values, and/or altering the CPU clock divider
value. This allows a trade-off of power versus processing speed based on application
requirements. In addition, Peripheral Power Control allows shutting down the clocks to
individual on-chip peripherals, allowing fine tuning of power consumption by eliminating all
dynamic power use in any peripherals that are not required for th e application. Each of the
peripherals has its own clock divider which provides even better power control.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
ramp (in the case of power on), the type of crystal and its
DD(3V3)
Integrated PMU (Power Management Unit) automatically adjust internal regulators to
minimize power consumption during Sleep, Deep sleep, Power-down, and Deep
power-down modes.
The LPC17xx also implement a separate power domain to allow turning of f power to the
bulk of the device while maintaining operation of the RTC and a small set of registers for
storing data during any of the power-down modes.
8.29.6.1 Sleep mode
When Sleep mode is entered, the clock to the core is stopped. Resumption from the Sleep
mode does not need any special sequence but re-enabling th e clock to the Arm core.
In Sleep mode, execution of instructions is suspended until either a Reset or interrupt
occurs. Peripheral functions continue operation during Sleep mode and may generate
interrupts to cause the processor to resume execution. Sleep mode eliminates dynamic
power used by the processor itself, memory systems and related controllers, and internal
buses.
8.29.6.2 Deep-sleep mode
In Deep-sleep mode, the oscillator is shut down and the chip receives no internal clocks.
The processor state and registers, peripheral registers, and internal SRAM values are
preserved throughout Deep-sleep mode and the logic levels of chip pins remain static.
The output of the IRC is disabled but the IRC is not powered down for a fast wake-up later.
The RTC oscillator is not stopped because the RTC interrupts may be used as the
wake-up source. The PLL is automatically turned off and disconnected. The CCLK and
USB clock dividers automatically get reset to zero.
The Deep-sleep mode can be terminated and normal operation resumed by either a
Reset or certain specific interrupts that are able to function without clocks. Since all
dynamic operation of the chip is suspended, Deep-sleep mode reduces chip power
consumption to a very low value. Power to the flash memory is left on in Deep-sleep
mode, allowing a very quick wake-up.
On wake-up from Deep-sleep mode, the code execution and peripherals activities will
resume after 4 cycles expire if the IRC was used before entering Deep-sleep mode. If the
main external oscillator was used, the code execution will resume when 4096 cycles
expire. PLL and clock dividers need to be reconfigured accordingly.
8.29.6.3 Power-down mode
Power-down mode does everything that Deep-sleep mode does, but also turns off the
power to the IRC oscillator and the flash memory. This saves more power but requires
waiting for resumption of flash operation before execution of code or data access in the
flash memory can be accomplished.
On the wake-up of Power-down mode, if the IRC was used before entering Power-down
mode, it will take IRC 60 s to start-up. After this 4 IRC cycles will expire before the code
execution can then be resumed if the code was running from SRAM. In the meantime, the
flash wake-up timer then counts 4 MHz IRC clock cycles to make the 100 s flash start-up
time. When it times out, access to the flash will be allowed. Users need to reconfigure the
PLL and clock dividers accordingly.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
8.29.6.4 Deep power-down mode
The Deep power-down mode can only be entered from the RTC block. In Deep
power-down mode, power is shut off to the entire chip with the exception of the RTC
module and the RESET
The LPC17xx can wake up from Deep power-down mode via the RESET
match event of the RTC.
8.29.6.5 Wake-up interrupt controller
The Wake-up Interrupt Controller (WIC) allows the CPU to automatically wake up from
any enabled priority interrupt that can occur while the clocks are stopped in Deep sleep,
Power-down, and Deep power-down modes.
The WIC works in connection with the Nested Vectored Interrupt Cont roller (NVIC). When
the CPU enters Deep sleep, Power-down, or Deep power-down mode, the NVIC sends a
mask of the current interrupt situation to the WIC.This mask includes all of the interrupts
that are both enabled and of sufficient priority to be serviced immediately. With this
information, the WIC simply notices when one of the interrupts has occurred and then it
wakes up the CPU.
The WIC eliminates the need to periodically wake up the CPU and poll the interrupts
resulting in additional power savings.
pin.
8.29.7 Peripheral power control
pin or an alarm
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.
The LPC17xx provide two independent power domains that allow the bulk o f the device to
have power removed while maintaining operation of the RTC and the backup Regi sters.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
On the LPC17xx, I/O pads are powered by the 3.3 V (V
V
DD(REG)(3V3)
pin powers the on-chip voltage regulator which in turn provides po wer to the
) pins, while the
DD(3V3)
CPU and most of the peripherals.
Depending on the LPC17xx application, a design can use two power options to manage
power consumption.
The first option assumes that power consumption is not a concern and the design ties the
V
DD(3V3)
and V
DD(REG)(3V3)
pins together. This app roach requires only one 3.3 V power
supply for both pads, the CPU, and peripherals. While this solution is simple, it does not
support powering down the I/O pad ring “on the fly” while keeping the CPU and
peripherals alive.
The second option uses two power supplies; a 3.3 V supply for the I/O pads (V
a dedicated 3.3 V supply for the CPU (V
DD(REG)(3V3)
). Having the on-chip voltage regulator
DD(3V3)
) and
powered independently from the I/O pad ring enables shutting down of the I/O p a d power
supply “on the fly”, while the CPU and peripherals stay active.
The VBAT pin supplies power only to the RTC domain. The RTC requires a minimum of
power to operate, which can be supplied by an external battery. The device core power
(V
DD(REG)(3V3)
there is no power drain from the RTC battery when V
Reset has four sources on the LPC17xx: the RESET pin, the Watchdog reset, power-on
reset (POR), and the BrownOut Detection (BOD) circuit. The RESET
trigger input pin. Assertion of chip Reset by any source, once the operating voltag e attains
a usable level, causes the RSTOUT
description in Section 8.29.5
). The wake-up timer ensures that reset remains asserted
pin to go LOW and starts the wake-up timer (see
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. Once reset is
de-asserted, or, in case of a BOD-triggered reset, once the voltage rises above the BOD
threshold, the RSTOUT
pin goes HIGH.
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.
The LPC17xx include 2-stage monitoring of the voltage on the V
voltage falls below 2.2 V, the BOD asserts an interrupt signal to the Vectored Interrupt
Controller. This signal can be enabled for interrupt in the Interrupt Enable Register in the
NVIC in order to cause a CPU interrupt; if not, software can monitor the signal by reading
a dedicated status register.
The second stage of low-voltage detection asserts reset to inactivate the LPC17xx when
the voltage on the V
DD(REG)(3V3)
pins falls below 1.85 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.2 V and 1.85 V thresholds include some hysteresis. In normal operation, this
hysteresis allows the 2.2 V detection to reliably interrupt, or a regularly executed event
loop to sense the condition.
8.30.3 Code security (Code Read Protection - CRP)
This feature of the LPC17xx allows user to enable dif ferent levels of securi ty in the system
so that access to the on-chip flash and use of the JTAG and ISP can be restricted. When
needed, CRP is invoked by programming a specific pattern into a dedicated flash location.
IAP commands are not affected by the CRP.
There are three levels of the Code Read Protection.
CRP1 disables access to chip via the JTAG and allows partial flash update (excluding
flash sector 0) using a limited set of the ISP commands. This mode is useful when CRP is
required and flash field updates are needed but all sectors can not be erased.
DD(REG)(3V3)
pins. If this
CAUTION
CRP2 disables access to chip via the JTAG and only allows full flash erase and update
using a reduced set of the ISP commands.
Running an application with level CRP3 selected fully disables any access to chip via the
JT AG pins and the ISP. This mode effectively disables ISP override using P2[10] pin, too.
It is up to the user’s application to provide (if needed) flash update mechanism using IAP
calls or call reinvoke ISP command to enable flash update via UART0.
If level three Code Read Protection (CRP3) is selected, no future factory testing can be
performed on the device.
8.30.4 APB interface
The APB peripherals are split into two separate APB buses in order to distribute the bus
bandwidth and thereby reducing stalls caused by contention between the CPU and the
GPDMA controller.
The LPC17xx use an AHB multilayer matrix. This matrix connects the instruction (I-code)
and data (D-code) CPU buses of the Arm Cortex-M3 to the flash memory, the main
(32 kB) static RAM, and the Boot ROM. The GPDMA can also access all of these
memories. The peripheral DMA controllers, Ethernet, and USB can access all SRAM
blocks. Additionally, the matrix connects the CPU system bus and all of the DMA
controllers to the various peripheral function s.
8.30.6 External interrupt inputs
The LPC17xx include up to 46 edge sensitive interrupt inputs combined with up to four
level sensitive external interrupt inputs as selectable pin functions. The external interrupt
inputs can optionally be used to wake up the processor from Power-down mode.
8.30.7 Memory mapping control
The Cortex-M3 incorporates a mechanism that allows remapping the interrupt vector table
to alternate locations in the memory map. This is controlled via the Vector Table Offset
Register contained in the NVIC.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
The vector table may be located anywhere within the bottom 1 GB of Cortex-M3 address
space. The vector table must be located on a 128 word (512 byte) boundary because the
NVIC on the LPC17xx is configured for 128 total interrupts.
8.31 Emulation and debugging
Debug and trace functions are integrated into the Arm Cortex-M3. Serial wire debug and
trace functions are supported in addition to a standard JTAG debug and parallel trace
functions. The Arm Cortex-M3 is configured to support up to eight breakpoints and four
watch points.
65+150C
maximum junction temperature150C
total power dissipation (per
package)
based on package heat
transfer, not device power
-1.5W
consumption
V
ESD
electrostatic discharge voltagehuman body model; all pins
[7]
4000+4000V
I
[1] The following applies to the limiting values:
a) This product includes circuitry specifically designed for the protection of its internal devices from the damaging effects of excessive
static charge. Nonetheless, it is suggested that conventional precautions be taken to avoid applying greater than the rated
maximum.
b) Parameters are valid over operating temperature range unless otherwise specified. All voltages are with respect to V
otherwise noted.
c) The limiting values are stress ratings only. Operating the part at these values is not recommended, and proper operation is not
guaranteed. The conditions for functional operation are specified in Table 8
[2] Maximum/minimum voltage above the maximum operating voltage (see Table 8
(< 10 ms) to a device without leading to irrecoverable failure. Failure includes the loss of reliability and shorter lifetime of the device.
[3] See Table 19
[4] Including voltage on outputs in 3-state mode.
[5] V
[6] The maximum non-operating storage temperature is different than the temperature for required shelf life which should be determined
[7] Human body model: equivalent to discharging a 100 pF capacitor through a 1.5 k series resistor.
[1] Typical ratings are not guaranteed. The values listed are at room temperature (25 C), nominal supply voltages.
[2] For USB operation 3.0 V V
[3] V
[4] V
[7] Applies to LPC1768/67/66/65/64/63.
[8] Applies to LPC1769 only.
CCLK
[9] IRC running at 4 MHz; main oscillator and PLL disabled; PCLK =
⁄8.
[10] BOD disabled.
. I
[11] On pin V
DD(REG)(3V3)
[12] On pin VBAT; I
[13] On pin VBAT; V
DD(REG)(3V3)
BAT
= 530 nA. V
BAT
= 630 nA; V
= 3.0 V; T
amb
DD(REG)(3V3)
DD(REG)(3V3)
=25C.
[14] All internal pull-ups disabled. All pins configured as output and driven LOW. V
= 3.0 V; V
= 3.0 V; V
= 3.0 V; T
BAT
= 3.0 V; T
BAT
amb
amb
=25C.
=25C.
DD(3V3)
= 3.3 V; T
amb
=25C.
[15] TCK/SWDCLK pin needs to be externally pulled LOW.
[16] On pin V
DDA
=3.3V; T
DDA
=25C. The ADC is powered if the PDN bit in the AD0CR register is set to 1 and in Power-down mode
amb
; V
of the PDN bit is set to 0.
[17] The ADC is powered if the PDN bit in the AD0CR register is set to 1. See LPC17xx user manual UM10360_1.
[18] The ADC is in Power-down mode if the PDN bit in the AD0CR register is set to 0. See LPC17xx user manual UM10360_1.
[19] V
i(VREFP)
= 3.3 V; T
amb
=25C.
[20] Including voltage on outputs in 3-state mode.
[21] V
supply voltages must be present.
DD(3V3)
[22] 3-state outputs go into 3-state mode in Deep power-down mode.
[23] Allowed as long as the current limit does not exceed the maximum current allowed by the device.
[24] To V
.
SS
[25] Includes external resistors of 33 1 % on D+ and D.
1 1.1 Power consumption
Conditions: BOD disabled.
Fig 8.Deep-sleep mode: typical regulato r supply current I
The supply current per peripheral is measured a s the difference in supply current between
the peripheral block enabled and the peripheral block disabled in the PCONP register. All
other blocks are disabled and no code is executed. Measured on a typical sample at
T
=25C. The peripheral clock PCLK = CCLK/4.
amb
Table 9.Power consumption for individual analog and digital blocks
PeripheralConditionsTypical supply current in mA;
12 MHz48 MHz100 MHz
Timer0.030.110.23Average current per timer
UART0.070.260.53Average current per UART
PWM0.050.200.41
Motor control
PWM
I2C0.020.080.16Average current per I2C
SPI0.020.060.13
SSP10.040.160.32
ADCPCLK = 12 MHz for CCLK = 12 MHz
CANPCLK = CCLK/60.130.491.00Average current per CAN
CAN0, CAN1,
acceptance filter
DMAPCLK = CCLK1.335.1010.36
QEI0.050.200.41
GPIO0.331.272.58
I2S0.090.340.70
USB and PLL10.941.321.94
EthernetEthernet block ena bled in the PCONP
Ethernet
connected
Notes
CCLK =
0.050.210.42
2.122.092.07
and 48 MHz; PCLK = 12.5 MHz for
CCLK = 100 MHz
PCLK = CCLK/60.220.851.73Both CAN blocks and
acceptance filter
0.491.873.79
register; Ethernet not connected.
Ethernet initialized, connected to
network, and running web server
example.
--5.19
[1]
[1] The combined current of several peripherals running at the same time can be less than the sum of each individual peripheral current
[1] Number of program/erase cycles.
[2] Programming times are given for writing 256 bytes from RAM to the flash. Data must be written to the flash in blocks of 256 bytes.
[1] Parameters are valid over operating temperature range unless otherwise specified.
[2] Typical ratings are not guaranteed. The values listed are at room temperature (25 C), nominal supply voltages.
Fig 16. External clock timing (with an amplitude of at least V
[1] Parameters are valid over operating temperature range unless otherwise specified.
[2] Typical ratings are not guaranteed. The values listed are at room temperature (25 C), nominal supply voltages.
[1] See the I2C-bus specification UM10204 for details.
[2] Parameters are valid over operating temperature range unless otherwise specified.
[3] A device must internally provide a hold time of at least 300 ns for the SDA signal (with respect to the
(min) of the SCL signal) to bridge the undefined region of the falling edge of SCL.
V
IH
[4] C
= total capacitance of one bus line in pF.
b
[5] The maximum t
output stage t
SDA and the SCL pins and the SDA/SCL bus lines without exceeding the maximum specified t
[6] In Fast-mode Plus, fall time is specified the same for both output stage and bus timing. If series resistors
are used, designers should allow for this when considering bus timing.
[7] tHD;DA T is the data hold time that is measured from the falling edge of SCL; applies to data in transmission
and the acknowledge.
[8] The maximum t
the maximum of t
maximum must only be met if the device does not stretch the LOW period (t
clock stretches the SCL, the data must be valid by the set-up time before it releases the clock.
[9] tSU;DAT is the data set-up time that is measured with respect to the rising edge of SCL; applies to data in
transmission and the acknowledge.
[10] A Fast-mode I
250 ns must then be met. This will automatically be the case if the device does not stretch the LOW period
of the SCL signal. If such a device does stretch the LOW period of the SCL signal, it must output the next
data bit to the SDA line t
specification) before the SCL line is released. Also the acknowledge timing must meet this set-up time.
The maximum SSP speed is 33 Mbit/s in master mode or 8 Mbit/s in slave mod e. In slave
mode, the maximum SSP clock rate must be 1/12 of the SSP PCLK clock rate.
Table 16.Dynamic characteristics: SSP pins in SPI mode
= 30 pF for all SSP pins; T
C
L
sampled at 10 % and 90 % of the signal level. Values guaranteed by design.
SymbolParameterConditionsMinMaxUnit
SSP master
t
DS
t
DH
t
v(Q)
t
h(Q)
SSP slave
t
DS
t
DH
t
v(Q)
t
h(Q)
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
=40C to 85C; V
amb
data set-up time in SPI mode16.1-ns
data hold timein SPI mode0-ns
data output valid timein SPI mode-2.5ns
data output hold timein SPI mode0-ns
data set-up time in SPI mode16.1-ns
data hold timein SPI mode0-ns
data output valid timein SPI mode-3*T
data output hold timein SPI mode0-ns
Remark: The USB controller is available as a device/Host/OTG controller on parts
LPC1769/68/66/65 and as device-only controller on part LPC1764.
Table 17. Dynamic characteristics: USB pins (full-speed)
= 50 pF; Rpu = 1.5 k on D+ to V
C
L
SymbolParameterConditionsMinTypMaxUnit
t
r
t
f
t
FRFM
V
CRS
t
FEOPT
t
FDEOP
t
JR1
t
JR2
t
EOPR1
t
EOPR2
DD(3V3)
; 3.0 V V
DD(3V3)
3.6 V.
rise time10 % to 90 %8.5-13.8ns
fall time10 % to 90 %7.7-13.7ns
differential rise and fall time
tr/t
f
--109%
matching
output signal crossover voltage1.3-2.0V
source SE0 interval of EOPsee Figure 23160-175ns
source jitter for differential transition
see Figure 232-+5ns
to SE0 transition
receiver jitter to next transition18.5-+18.5ns
receiver jitter for paired transitions10 % to 90 %9-+9ns
EOP width at receivermust reject as
[1]
40 --ns
EOP; see
Figure 23
EOP width at receivermust accept as
[1]
82 --ns
EOP; see
Figure 23
[1] Characterized but not implemented as production test. Guaranteed by design.
Fig 23. Differential data -to-EOP transition skew and EOP width
15.2 Crystal oscillator XTAL input and component selection
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
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 thro ugh a cap acitor wi th
C
= 100 pF. To limit the input voltage to the specified range, choose an additional
i
capacitor to ground C
which attenuates the input voltage by a factor Ci/(Ci + Cg). In slave
g
mode, a minimum of 200 mV(RMS) is needed.
Fig 36. Slave mode operation of the on-chip oscillator
In slave mode the input clock signal should be coupled by means of a capacitor of 100 pF
(Figure 36
), with an amplitude between 200 mV(RMS) and 1000 mV(RMS). This
corresponds to a square wave signal with a signal swing of between 280 mV and 1.4 V.
The XTALOUT pin in this configuration can be left unconnected.
External components and models used in oscillation mode are shown in Figure 37
Table 23
and the capacitances C
fundamental mode oscillation (the fundamental frequency is represented by L, C
R
not be larger than 7 pF. Parameters F
manufacturer.
15.3 XTAL and RTCX 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 C
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
, Cx2, and Cx3 in case of
x1
X1
, C
X2
NXP Semiconductors
PIN
V
DD
V
DD
ESD
V
SS
ESD
strong
pull-up
strong
pull-down
V
DD
weak
pull-up
weak
pull-down
open-drain enable
output enable
repeater mode
enable
pull-up enable
pull-down enable
data output
data input
analog input
select analog input
002aaf272
pin configured
as digital output
driver
pin configured
as digital input
pin configured
as analog input
order to keep the noise coupled in via the PCB as small as possible. Also parasitic s
should stay as small as possible. Values of C
accordingly to the increase in parasitics of the PCB layout.
15.4 Standard I/O pin configuration
Figure 38 shows the possible pin modes for standard I/O pins with analog input function:
• Digital output driver: Open-dra in mo d e en ab le d/ disa b led
• Digital input: Pull-up enabled/disabled
• Digital input: Pull-down enabled/disabled
• Digital input: Repeater mode enabled/disabled
• Analog input
The default configuration for standard I/O pins is input with pull-up enabled. The weak
MOS devices provide a drive capability equivalent to pull-up and pull-down resistors.
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
and Cx2 should be chosen smaller
x1
Fig 38. Standard I/O pin configuration with analog input
ADCA nalog-to-Digital Converter
AHBAdvanced High-performance Bus
AMBAAdvanced Microcontroller Bus Architecture
APBAdvanced Peripheral Bus
BODBrownOut Detection
CANController Area Network
DACDigital-to-Analog Converter
DMADirect Memory Access
EOPEnd Of Packet
GPIOGeneral Purpose Input/Output
IRCInternal RC
IrDAInfrared Data Association
JTAGJoint Test Action Group
MACMedia Access Control
MIIMMedia Independent Interface Management
OHCIOpen Host Controller Interface
OTGOn-The-Go
PHYPhysical Layer
PLLPhase-Locked Loop
PWMPulse Width Modulator
RITRepetitive Interrupt Timer
RMIIReduced Media Independent Interface
SE0Single Ended Zero
SPISerial Peripheral Interface
SSISerial Synchronous Interface
SSPSynchronous Serial Port
TCMTightly Coupled Memory
TTLTransistor-Transisto r Lo g i c
UARTUniversal Asynchronous Receiver/Transmitter
USBUniversal Serial Bus
• Removed footnote 1: “5 V tolerant pad providing digital I/O functions with TTL
• Added a column for GPIO pins and device order part number to the ordering
LPC1769_68_67_66_65_64_63 v.9.5 <tbd>Product data sheet-LPC1769_68_67_66_65_64 v.9.4
Modifications:
• SSP timing diagram updated. SSP timing parameters t
• Parameter T
• SSP maximum bit rate in master mode corrected to 33 Mbit/s.
LPC1769_68_67_66_65_64_63 v.9.4 20140404 Product da ta sheet-LPC1769_68_67_66_65_64 v.9.3
Modifications:
• Added LPC1768UK.
• Table 5 “Pin description”: Changed RX_MCLK and TX_MCLK type from INPUT
LPC1769_68_67_66_65_64_63 v.9.3 20140108 Product da ta sheet-LPC1769_68_67_66_65_64 v.9.2
Modifications:
• Table 7 “Thermal resistance (±15 %)”:
Data sheet statusChange
notice
46 “Reflow soldering of the WLCSP100 package (part 2)”, and Figure 47
“Reflow soldering of the WLCSP100 package (part 3)”.
x 5.07 x 0.53mm; was 5.074 x 5.074 x 0.6mm.
(data output valid time) in SPI mode to 3*T
2.5 ns. See Table 16 “Dynamic characteristics: SSP pins in SPI mode”.
Language (BSDL) is not available for this device.
"reserved" and changed it to I2C0.
description”.
levels and hysteresis. This pin is pulled up to a voltage level of 2.3 V to 2.6 V”
from TDO/SWO, TCK/SWDCLK, and RTCK, pins. See T able 5 “Pin description”.
and VREFP should be tied to VDD(3V3) if the ADC and DAC are not used.”
LPC1769_68_67_66_65_64_63 v.9.1 20130916 Product data sheet-LPC1769_68_67_66_65_64 v.9
Modifications:
Objective [short] data sheetDevelopmentThis document contains data from the objective specification for product development.
Preliminary [short] data sheet QualificationThis document contains data from the preliminary specification.
Product [short] data sheetProductionThis document contains the product specification.
[1] Please consult the most recently issued document before initiating or completing a design.
[2] The term ‘short data sheet’ is explained in section “Definitions”.
[3] The product status of device(s) d escribed i n this docume nt may have changed since this docume nt was publis hed and ma y dif fer in case of multiple devices. The latest product statu s
information is available on the Internet at URL http://www.nxp.com.
[1][2]
Product status
[3]
Definition
21.2 Definitions
Draft — The document is a draft version only. The content is still under
internal review and subject to formal approval, which may result in
modifications or additions. NXP Semiconductors does not give any
representations or warranties as to the accuracy or completeness of
information included herein and shall have no liability for the consequences of
use of such information.
Short data sheet — A short data sheet is an extract from a full data sheet
with the same product type number(s) and title. A short data sheet is intended
for quick reference only and should not be relied u pon to co nt ain det ailed and
full information. For detailed and full information see the relevant full data
sheet, which is available on request via the local NXP Semiconductors sales
office. In case of any inconsistency or conflict with the short data sheet, the
full data sheet shall prevail.
Product specification — The information and data provided in a Product
data sheet shall define the specification of the product as agreed between
NXP Semiconductors and its customer, unless NXP Semiconductors and
customer have explicitly agreed otherwise in writing. In no event however,
shall an agreement be valid in which the NXP Semiconductors product is
deemed to offer functions and qualities beyond those described in the
Product data sheet.
21.3 Disclaimers
Limited warranty and liability — Information in this document is believed to
be accurate and reliable. However, NXP Semiconductors does not give any
representations or warranties, expressed or implied, as to the accuracy or
completeness of such information and shall have no liability for the
consequences of use of such information. NXP Semiconductors takes no
responsibility for the content in this document if provided by an information
source outside of NXP Semiconductors.
In no event shall NXP Semiconductors be lia ble for any indirect, incidental,
punitive, special or consequential damages (including - without limitation - lost
profits, lost savings, business interruption, costs related to the removal or
replacement of any products or rework charges) whether or not such
damages are based on tort (including negligence), warranty, breach of
contract or any other legal theory.
Notwithstanding any damages that customer might incur for any reason
whatsoever, NXP Semi conductors’ aggregat e and cumulative liabil ity towards
customer for the products described herein shall be limited in accordance
with the Terms and conditions of commercial sale of NXP Semiconductors.
Right to make changes — NXP Semiconductors reserves the right to make
changes to information published in this document, including without
limitation specifications and product descriptions, at any time and without
notice. This document supersedes and replaces all information supplied prior
to the publication hereof.
Suitability for use — NXP Semiconductors products are not designed,
authorized or warranted to be suitable for use in life support, life-critical or
safety-critical systems or equipment, nor in applications where failure or
malfunction of an NXP Semiconductors product can reasonabl y be expected
to result in personal injury, death or severe property or environmental
damage. NXP Semiconductors and its suppliers accept no liability for
inclusion and/or use of NXP Semiconductors products in such equipment or
applications and therefore such inclusion and/or use is at the cu stomer’s own
risk.
Applications — Applications that are described herein for any of these
products are for illustrative purposes only. NXP Semiconductors makes no
representation or warranty that such applications will be suitable for the
specified use without further testing or modification.
Customers are responsible for the design and operation of their applications
and products using NXP Semiconductors products, and NXP Semiconductors
accepts no liability for any assistance with applications or customer product
design. It is customer’s sole responsibility to determine whether the NXP
Semiconductors product is suitable and fit for the customer’s applications and
products planned, as well as for the planned application and use of
customer’s third party customer(s). Customers should provide appropriate
design and operating safeguards to minimize the risks associated with their
applications and products.
NXP Semiconductors does not accept any liability related to any default ,
damage, costs or problem which is based on any weakness or default in the
customer’s applications or products, or the application or use by customer’s
third party customer(s). Customer is responsible for doing all necessary
testing for the customer’s applications and products using NXP
Semiconductors products in order to avoid a default of the applications and
the products or of the application or use by customer’s third part y
customer(s). NXP does not accept any liability in this respect.
Limiting values — Stress above one or more limiting values (as defined in
the Absolute Maximum Ratings System of IEC 60134) will cause permanent
damage to the device. Limiting values are stress ratings only and (proper)
operation of the device at these or any other conditions above those given in
the Recommended operating conditions section (if present) or the
Characteristics sections of this document is not warranted. Constant or
repeated exposure to limiting values will permanently and irreversibly affect
the quality and reliability of the device.
Terms and conditions of commercial sale — NXP Semiconductors
products are sold subject to the general terms and conditions of commercial
sale, as published at http://www.nxp.com/profile/terms
agreed in a valid written individual agreement. In case an individual
agreement is concluded only the terms and conditions of the respective
agreement shall apply. NXP Semiconductors hereby expressly objects to
applying the customer’s general terms and conditions with regard to the
purchase of NXP Semiconductors products by customer.
No offer to sell or license — Nothing in this document may be interpreted or
construed as an offer to sell product s that is ope n for accept ance or the gr ant,
conveyance or implication of any license under any copyrights, patents or
other industrial or intellectual property rights.
, unless otherwise
Product data sheetRev. 9.8 — 4 May 2018 90 of 93
NXP Semiconductors
LPC1769/68/67/66/65/64/63
32-bit ARM Cortex-M3 microcontroller
Export control — This document as well as the item(s) described herein
may be subject to export control regulations. Export might require a prior
authorization from competent authorities.
Non-automotive qualified products — Unless this data sheet expressly
states that this specific NXP Semiconductors product is automotive qualified,
the product is not suitable for automotive use. It i s neither qua lif ied nor test ed
in accordance with automotive testing or application requirements. NXP
Semiconductors accepts no liability for inclusion and/or use of
non-automotive qualified products in automotive equ ipment or applications.
In the event that customer uses the product for design-in and use in
automotive applications to automotive specifications and standards, customer
(a) shall use the product without NXP Semiconductors’ warranty of the
product for such automotive applications, use and specifications, and (b)
whenever customer uses the product for automotive applications beyond
NXP Semiconductors’ specifications such use shall be solely at customer’s
own risk, and (c) customer fully indemnifies NXP Semiconductors for any
liability, da mages or failed produ ct cl aims resulting from custome r design and
use of the product for automotive applications beyond NXP Semiconductors’
standard warranty and NXP Semiconductors’ product specifications.
21.4 Trademarks
Notice: All referenced brands, prod uct names, service names and trad emarks
are the property of their respective owners.
2
I
C-bus — logo is a trademark of NXP B.V.
22. Contact information
For more information, please visit: http://www.nxp.com
For sales office addresses, please send an email to: salesaddresses@nxp.com
Please be aware that important notices concerning this docum ent and the product(s)
described herein, have been included in section ‘Legal information’.