LPC2377 78
LPC2377 78
LPC2377 78
1. General description
The LPC2377/78 microcontrollers are based on a 16-bit/32-bit ARM7TDMI-S CPU with
real-time emulation that combines the microcontroller with 512 kB of embedded
high-speed flash memory. A 128-bit wide memory interface and a unique accelerator
architecture enable 32-bit code execution at the maximum clock rate. For critical
performance in interrupt service routines and DSP algorithms, this increases performance
up to 30 % over Thumb mode. For critical code size applications, the alternative 16-bit
Thumb mode reduces code by more than 30 % with minimal performance penalty.
General Purpose DMA controller (GPDMA) on AHB that can be used with the SSP
serial interfaces, the I2S port, and the Secure Digital/MultiMediaCard (SD/MMC) card
port, as well as for memory-to-memory transfers.
Serial Interfaces:
Ethernet MAC with associated DMA controller. These functions reside on an
independent AHB.
USB 2.0 full-speed device with on-chip PHY and associated DMA controller
(LPC2378 only).
Four UARTs with fractional baud rate generation, one with modem control I/O, one
with IrDA support, all with FIFO.
CAN controller with two channels (LPC2378 only).
SPI controller.
Two SSP controllers with FIFO and multi-protocol capabilities. One is an alternate
for the SPI port, sharing its interrupt and pins. These controllers can be used with
the GPDMA controller.
Three I2C-bus interfaces (one with open-drain and two with standard port pins).
I2S (Inter-IC Sound) interface for digital audio input or output. It can be used with
the GPDMA.
Other peripherals:
SD/MMC memory card interface.
104 General purpose I/O pins with configurable pull-up/down resistors.
10-bit ADC with input multiplexing among 8 pins.
10-bit DAC.
Four general purpose timers/counters with 8 capture inputs and 10 compare
outputs. Each timer block has an external count input.
One PWM/timer block with support for three-phase motor control. The PWM has
two external count inputs.
Real-Time Clock (RTC) with separate power pin, clock source can be the RTC
oscillator or the APB clock.
2 kB SRAM powered from the RTC power pin, allowing data to be stored when the
rest of the chip is powered off.
WatchDog Timer (WDT). The WDT can be clocked from the internal RC oscillator,
the RTC oscillator, or the APB clock.
Standard ARM test/debug interface for compatibility with existing tools.
Emulation trace module supports real-time trace.
Single 3.3 V power supply (3.0 V to 3.6 V).
Four reduced power modes: idle, sleep, power-down, and deep power-down.
Four external interrupt inputs configurable as edge/level sensitive. All pins on Port 0
and Port 2 can be used as edge sensitive interrupt sources.
Processor wake-up from Power-down mode via any interrupt able to operate during
Power-down mode (includes external interrupts, RTC interrupt, USB activity, Ethernet
wake-up interrupt).
Two independent power domains allow fine-tuning of power consumption based on
needed features.
Each peripheral has its own clock divider for further power saving.
Brownout detect with separate thresholds for interrupt and forced reset.
On-chip power-on reset.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
3. Applications
Industrial control
Medical systems
Protocol converter
Communications
4. Ordering information
Table 1. Ordering information
Type number Package
Name Description Version
LPC2377FBD144 LQFP144 plastic low profile quad flat package; 144 leads; body 20 20 1.4 mm SOT486-1
LPC2378FBD144 LQFP144 plastic low profile quad flat package; 144 leads; body 20 20 1.4 mm SOT486-1
CAN channels
ADC channels
DAC channels
+ 4 kB
FIFO
Local bus
GP/USB
Total
RTC
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
5. Block diagram
XTAL1
TMS TDI trace signals XTAL2 VDD(3V3)
VREF
LPC2377/78 SYSTEM
P0, P1, P2, 32 kB 512 kB PLL VSSA, VSS
TRACE MODULE
TEST/DEBUG FUNCTIONS
P3, P4 VDD(DCDC)(3V3)
EMULATION
SRAM FLASH INTERFACE
system INTERNAL RC
HIGH-SPEED clock
INTERNAL OSCILLATOR
GPI/O ARM7TDMI-S
104 PINS CONTROLLERS
TOTAL SRAM FLASH D[7:0]
VECTORED EXTERNAL
INTERRUPT MEMORY A[15:0]
CONTROLLER CONTROLLER OE, CS0, CS1,
BLS0
AHB2 AHB1
AHB AHB
BRIDGE BRIDGE
VBUS
16 kB MASTER AHB TO SLAVE USB WITH
ETHERNET 8 kB
4 kB RAM 2 × USB_D+/USB_D−
SRAM PORT AHB BRIDGE PORT
RMII(8) MAC WITH SRAM
AND DMA(1) 2 × USB_CONNECT
DMA 2 × USB_UP_LED
AHB TO
APB BRIDGE GP DMA
CONTROLLER
SCK1
LEGACY GPI/O MOSI1
P0, P1 SSP1 INTERFACE
56 PINS TOTAL MISO1
SSEL1
002aac574
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
6. Pinning information
6.1 Pinning
144
109
1 108
LPC2377FBD144
LPC2378FBD144
36 73
37
72
002aac584
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
[1] 5 V tolerant pad providing digital I/O functions with TTL levels and hysteresis.
[2] 5 V tolerant pad providing digital I/O functions (with TTL levels and hysteresis) and analog input. When configured as a DAC input,
digital section of the pad is disabled.
[3] 5 V tolerant pad providing digital I/O with TTL levels and hysteresis and analog output function. When configured as the DAC output,
digital section of the pad is disabled.
[4] Open-drain, 5 V tolerant digital I/O pad compatible with I2C-bus 400 kHz specification. It requires an external pull-up to provide output
functionality. When power is switched off, this pin connected to the I2C-bus is floating and does not disturb the I2C lines. Open-drain
configuration applies to all functions on this pin.
[5] Pad provides digital I/O and USB functions (LPC2378 only). It is designed in accordance with the USB specification, revision 2.0
(Full-speed and Low-speed mode only).
[6] 5 V tolerant pad with 10 ns glitch filter providing digital I/O functions with TTL levels and hysteresis.
[7] 5 V tolerant pad with 20 ns glitch filter providing digital I/O function with TTL levels and hysteresis.
[8] Pad provides special analog functionality.
[9] This pin has a built-in pull-up resistor.
[10] This pin has no built-in pull-up and no built-in pull-down resistor.
[11] When the main 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] If the RTC is not used, these pins can be left floating.
[13] Pad provides special analog functionality.
[14] Pad provides special analog functionality.
[15] Pad provides special analog functionality.
[16] Pad provides special analog functionality.
[17] Pad provides special analog functionality.
[18] Pad provides special analog functionality.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
7. Functional description
The LPC2377/78 implement two AHBs in order to allow the Ethernet block to operate
without interference caused by other system activity. The primary AHB, referred to as
AHB1, includes the VIC, GPDMA controller, and EMC.
The second AHB, referred to as AHB2, includes only the Ethernet block and an
associated 16 kB SRAM. In addition, a bus bridge is provided which allows the secondary
AHB to be a bus master on AHB1, allowing expansion of Ethernet buffer space into
off-chip memory or unused space in memory residing on AHB1.
In summary, bus masters with access to AHB1 are the ARM7 itself, the GPDMA function,
and the Ethernet block (via the bus bridge from AHB2). Bus masters with access to AHB2
are the ARM7 and the Ethernet block.
AHB peripherals are allocated a 2 MB range of addresses at the top of the 4 GB ARM
memory space. Each AHB peripheral is allocated a 16 kB address space within the AHB
address space. Lower speed peripheral functions are connected to the APB bus. The
AHB to APB bridge interfaces the APB to the AHB. APB peripherals are also allocated a
2 MB range of addresses, beginning at the 3.5 GB address point. Each APB peripheral is
allocated a 16 kB address space within the APB address space.
Pipeline techniques are employed so that all parts of the processing and memory systems
can operate continuously. Typically, while one instruction is being executed, its successor
is being decoded, and a third instruction is being fetched from memory.
The key idea behind Thumb is that of a super-reduced instruction set. Essentially, the
ARM7TDMI-S processor has two instruction sets:
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
The 16-bit instruction length of the Thumb set allows it to approach twice the density of
standard ARM code, while retaining most of the ARM performance advantage over a
traditional 16-bit processor using 16-bit registers. This increase is possible because
Thumb code operates on the same 32-bit register set as ARM code.
Thumb code is able to provide up to 65 % of the code size of ARM, and 160 % of the
performance of an equivalent ARM processor connected to a 16-bit memory system.
The flash memory is 128 bits wide and includes pre-fetching and buffering techniques to
allow it to operate at SRAM speeds of 72 MHz.
A 16 kB SRAM block serving as a buffer for the Ethernet controller and an 8 kB SRAM
used by the GPDMA controller or the USB device can be used for data and code storage.
The 2 kB RTC SRAM can be used for data storage only. The RTC SRAM is battery
powered and retains the content in the absence of the main power supply.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
In addition, the CPU interrupt vectors may be remapped to allow them to reside in either
flash memory (default), boot ROM, or SRAM (see Section 7.26.6).
APB PERIPHERALS
3.5 GB 0xE000 0000
0x8100 FFFF
EXTERNAL MEMORY BANK 1 (64 kB)
0x8100 0000
0x8000 FFFF
EXTERNAL MEMORY BANK 0 (64 kB)
2.0 GB 0x8000 0000
BOOT ROM AND BOOT FLASH
(BOOT FLASH REMAPPED FROM ON-CHIP FLASH)
0x4000 8000
0x4000 7FFF
32 kB LOCAL ON-CHIP STATIC RAM
1.0 GB 0x4000 0000
0x0008 0000
0x0007 FFFF
002aac585
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
FIQs have the highest priority. If more than one request is assigned to FIQ, the VIC ORs
the requests to produce the FIQ signal to the ARM processor. The fastest possible FIQ
latency is achieved when only one request is classified as FIQ, because then the FIQ
service routine can simply start dealing with that device. But if more than one request is
assigned to the FIQ class, the FIQ service routine can read a word from the VIC that
identifies which FIQ source(s) is (are) requesting an interrupt.
Vectored IRQs, which include all interrupt requests that are not classified as FIQs, have a
programmable interrupt priority. When more than one interrupt is assigned the same
priority and occur simultaneously, the one connected to the lowest numbered VIC channel
will be serviced first.
The VIC ORs the requests from all of the vectored IRQs to produce the IRQ signal to the
ARM processor. The IRQ service routine can start by reading a register from the VIC and
jumping to the address supplied by that register.
Any pin on Port 0 and Port 2 (total of 46 pins) regardless of the selected function, can be
programmed to generate an interrupt on a rising edge, a falling edge, or both. Such
interrupt requests coming from Port 0 and/or Port 2 will be combined with the EINT3
interrupt requests.
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.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
7.7.1 Features
• Asynchronous static memory device support including RAM, ROM, and flash, with or
without asynchronous page mode
• Low transaction latency
• Read and write buffers to reduce latency and to improve performance
• 8 data and 16 address lines wide static memory support
• Two chip selects for static memory devices
• Static memory features include:
– Asynchronous page mode read
– Programmable Wait States (WST)
– Bus turnaround delay
– Output enable and write enable delays
– Extended wait
7.8.1 Features
• Two DMA channels. Each channel can support a unidirectional transfer.
• The GPDMA can transfer data between the 8 kB SRAM and peripherals such as the
SD/MMC, two SSP, and I2S-bus interfaces.
• Single DMA and burst DMA request signals. Each peripheral connected to the
GPDMA can assert either a burst DMA request or a single DMA request. The DMA
burst size is set by programming the GPDMA.
• Memory-to-memory, memory-to-peripheral, peripheral-to-memory, and
peripheral-to-peripheral transfers.
• Scatter or gather DMA is supported through the use of linked lists. This means that
the source and destination areas do not have to occupy contiguous areas of memory.
• Hardware DMA channel priority. Each DMA channel has a specific hardware priority.
DMA channel 0 has the highest priority and channel 1 has the lowest priority. If
requests from two channels become active at the same time, the channel with the
highest priority is serviced first.
• AHB slave DMA programming interface. The GPDMA is programmed by writing to the
DMA control registers over the AHB slave interface.
• One AHB master for transferring data. This interface transfers data when a DMA
request goes active.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
• GPIO registers are relocated to the ARM local bus so that the fastest possible I/O
timing can be achieved.
• Mask registers allow treating sets of port bits as a group, leaving other bits
unchanged.
• All GPIO registers are byte and half-word addressable.
• Entire port value can be written in one instruction.
Additionally, any pin on Port 0 and Port 2 (total of 46 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.
7.9.1 Features
• Bit level set and clear registers allow a single instruction to set or clear any number of
bits in one port.
• Direction control of individual bits.
• All I/O default to inputs after reset.
• Backward compatibility with other earlier devices is maintained with legacy Port 0 and
Port 1 registers appearing at the original addresses on the APB bus.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
7.10 Ethernet
The Ethernet block contain 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 a dedicated AHB subsystem that is used to access
the Ethernet SRAM for Ethernet data, control, and status information. All other AHB traffic
in the LPC2377/78 takes place on a different AHB subsystem, effectively separating
Ethernet activity from the rest of the system. The Ethernet DMA can also access off-chip
memory via the EMC, as well as the SRAM located on another AHB, if it is not being used
by the USB block. However, using memory other than the Ethernet SRAM, especially
off-chip memory, will slow Ethernet access to memory and increase the loading of its AHB.
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.
7.10.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 buffers memory mapped to shared SRAM.
– DMA managers with scatter/gather DMA and arrays of frame descriptors.
– Memory traffic optimized by buffering and pre-fetching.
• Physical interface:
– Attachment of external PHY chip through standard RMII interface.
– PHY register access is available via the MIIM interface.
The two sets of pins needed by a USB device are named VBUS, USB_D+1, USB_D1,
USB_UP_LED1, USB_CONNECT1, and USB_D+2, USB_D2, USB_UP_LED2, and
USB_CONNECT2 respectively. At any given time only one of these two sets can be active
and used by the application.
7.11.1.1 Features
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
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.
Each CAN controller has a register structure similar to the NXP SJA1000 and the PeliCAN
Library block, but the 8-bit registers of those devices have been combined in 32-bit words
to allow simultaneous access in the ARM environment. The main operational difference is
that the recognition of received Identifiers, known in CAN terminology as Acceptance
Filtering, has been removed from the CAN controllers and centralized in a global
Acceptance Filter.
7.12.1 Features
• Two CAN controllers and buses.
• Data rates to 1 Mbit/s on each bus.
• 32-bit register and RAM access.
• Compatible with CAN specification 2.0B, ISO 11898-1.
• Global Acceptance Filter recognizes 11-bit and 29-bit receive identifiers for all CAN
buses.
• Acceptance Filter can provide FullCAN-style automatic reception for selected
Standard Identifiers.
• FullCAN messages can generate interrupts.
7.13.1 Features
• 10-bit successive approximation ADC
• Input multiplexing among 8 pins
• Power-down mode
• Measurement range 0 V to Vi(VREF)
• 10-bit conversion time 2.44 s
• Burst conversion mode for single or multiple inputs
• Optional conversion on transition of input pin or Timer Match signal
• Individual result registers for each ADC channel to reduce interrupt overhead
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
7.14.1 Features
• 10-bit DAC
• Resistor string architecture
• Buffered output
• Power-down mode
• Selectable output drive
7.15 UARTs
The LPC2377/78 contain four UARTs. In addition to standard transmit and receive data
lines, UART1 also provides a full modem control handshake interface.
The UARTs include a fractional baud rate generator. Standard baud rates such as 115200
can be achieved with any crystal frequency above 2 MHz.
7.15.1 Features
• 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
need for external crystals of particular values.
• Fractional divider for baud rate control, auto baud capabilities and FIFO control
mechanism that enables software flow control implementation.
• UART1 equipped with standard modem interface signals. This module also provides
full support for hardware flow control (auto-CTS/RTS).
• UART3 includes an IrDA mode to support infrared communication.
7.16.1 Features
• 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
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
7.17.1 Features
• Compatible with Motorola SPI, 4-wire TI SSI, and National Semiconductor Microwire
buses
• Synchronous serial communication
• Master or slave operation
• 8-frame FIFOs for both transmit and receive
• 4-bit to 16-bit frame
• DMA transfers supported by GPDMA
7.18.1 Features
• The MCI provides all functions specific to the SD/MMC memory card. These include
the clock generation unit, power management control, and command and data
transfer.
• Conforms to Multimedia Card Specification v2.11.
• Conforms to Secure Digital Memory Card Physical Layer Specification, v0.96.
• Can be used as a multimedia card bus or a secure digital memory card bus host. The
SD/MMC can be connected to several multimedia cards or a single secure digital
memory card.
• DMA supported through the GPDMA controller.
The I2C-bus is bidirectional, for inter-IC control using only two wires: a Serial Clock Line
(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 transmitter with the
capability to both receive and send information (such as memory). Transmitters and/or
receivers can operate in either master or slave mode, depending on whether the chip has
to initiate a data transfer or is only addressed. The I2C-bus is a multi-master bus and can
be controlled by more than one bus master connected to it.
The I2C-bus implemented in LPC2377/78 supports bit rates up to 400 kbit/s (Fast
I2C-bus).
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
7.19.1 Features
• I2C0 is a standard I2C compliant bus interface with open-drain pins.
• I2C1 and I2C2 use standard I/O pins and do not support powering off of individual
devices connected to the same bus lines.
• Easy to configure as master, slave, or master/slave.
• Programmable clocks allow versatile rate control.
• Bidirectional data transfer between masters and slaves.
• Multi-master bus (no central master).
• Arbitration between simultaneously transmitting masters without corruption of serial
data on the bus.
• Serial clock synchronization allows devices with different bit rates to communicate via
one serial bus.
• Serial clock synchronization can be used as a handshake mechanism to suspend and
resume serial transfer.
• The I2C-bus can be used for test and diagnostic purposes.
The I2S-bus specification defines a 3-wire serial bus using one data line, one clock line,
and one word select signal. The basic I2S connection has one master, which is always the
master, and one slave. The I2S interface on the LPC2377/78 provides a separate transmit
and receive channel, each of which can operate as either a master or a slave.
7.20.1 Features
• The interface has separate input/output channels each of which can operate in master
or slave mode.
• 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 48 kHz (16 kHz, 22.05 kHz,
32 kHz, 44.1 kHz or 48 kHz).
• Configurable word select period in master mode (separately for I2S input and output).
• 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
to the GPDMA block.
• Controls include reset, stop and mute options separately for I2S input and I2S output.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
7.21.1 Features
• A 32-bit Timer/Counter with a programmable 32-bit prescaler.
• Counter or Timer operation.
• Up to four 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 optionally generate
an interrupt.
• Four 32-bit match registers that allow:
– Continuous operation with optional interrupt generation on match.
– Stop timer on match with optional interrupt generation.
– Reset timer on match with optional interrupt generation.
• Up to four external outputs corresponding to match registers, with the following
capabilities:
– Set LOW on match.
– Set HIGH on match.
– Toggle on match.
– Do nothing on match.
The ability to separately control rising and falling edge locations allows the PWM to be
used for more applications. For instance, multi-phase motor control typically requires
three non-overlapping PWM outputs with individual control of all three pulse widths and
positions.
Two match registers can be used to provide a single edge controlled PWM output. One
match register (PWMMR0) controls the PWM cycle rate, by resetting the count upon
match. The other match register controls the PWM edge position. Additional single edge
controlled PWM outputs require only one match register each, since the repetition rate is
the same for all PWM outputs. Multiple single edge controlled PWM outputs will all have a
rising edge at the beginning of each PWM cycle, when a PWMMR0 match occurs.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
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).
7.22.1 Features
• The LPC2377/78 have one PWM block with Counter or Timer operation (may use the
peripheral clock or one of the capture inputs as the clock source).
• Seven match registers allow up to 6 single edge controlled or 3 double edge
controlled PWM outputs, or a mix of both types. The match registers also allow:
– Continuous operation with optional interrupt generation on match.
– Stop timer on match with optional interrupt generation.
– Reset timer on match with optional interrupt generation.
• Supports single edge controlled and/or double edge controlled PWM outputs. Single
edge controlled PWM outputs all go high at the beginning of each cycle unless the
output is a constant low. Double edge controlled PWM outputs can have either edge
occur at any position within a cycle. This allows for both positive going and negative
going pulses.
• Pulse period and width can be any number of timer counts. This allows complete
flexibility in the trade-off between resolution and repetition rate. All PWM outputs will
occur at the same repetition rate.
• Double edge controlled PWM outputs can be programmed to be either positive going
or negative going pulses.
• Match register updates are synchronized with pulse outputs to prevent generation of
erroneous pulses. Software must ‘release’ new match values before they can become
effective.
• May be used as a standard timer if the PWM mode is not enabled.
• A 32-bit Timer/Counter with a programmable 32-bit Prescaler.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
7.23.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 (Tcy(WDCLK) 256 4) to (Tcy(WDCLK) 232 4) in
multiples of Tcy(WDCLK) 4.
• The Watchdog Clock (WDCLK) source can be selected from the RTC clock, the
Internal RC oscillator (IRC), or the APB peripheral clock. This gives a wide range of
potential timing choices of watchdog operation under different power reduction
conditions. It also provides the ability to run the WDT from an entirely internal source
that is not dependent on an external crystal and its associated components and
wiring, for increased reliability.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
The VBAT pin supplies power only to the RTC and the battery RAM. These two functions
require a minimum of power to operate, which can be supplied by an external battery.
When the CPU and the rest of chip functions are stopped and power removed, the RTC
can supply an alarm output that can be used by external hardware to restore chip power
and resume operation.
7.24.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 32 kHz oscillator or programmable prescaler from APB clock.
• Dedicated power supply pin can be connected to a battery or to the main 3.3 V.
• An alarm output pin is included to assist in waking up from Power-down mode, or
when the chip has had power removed to all functions except the RTC and battery
RAM.
• Periodic interrupts can be generated from increments of any field of the time registers,
and selected fractional second values.
• 2 kB data SRAM powered by VBAT.
• RTC and battery RAM power supply is isolated from the rest of the chip.
Following reset, the LPC2377/78 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.
Upon power-up or any chip reset, the LPC2377/78 use the IRC as the clock source.
Software may later switch to one of the other available clock sources.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
7.25.2 PLL
The PLL accepts an input clock frequency in the range of 32 kHz to 25 MHz. The input
frequency is multiplied up to a high frequency, then divided down to provide the actual
clock used by the CPU and the USB block.
The PLL input, in the range of 32 kHz to 25 MHz, may initially be divided down by a value
‘N’, which may be in the range of 1 to 256. This input division provides a wide range of
output frequencies from the same input frequency.
Following the PLL input divider is the PLL multiplier. This can multiply the input divider
output through the use of a Current Controlled Oscillator (CCO) by a value ‘M’, in the
range of 1 through 32768. The resulting frequency must be in the range of 275 MHz to
550 MHz. The multiplier works by dividing the CCO output by the value of M, then using a
phase-frequency detector to compare the divided CCO output to the multiplier input. The
error value is used to adjust the CCO frequency.
The PLL is turned off and bypassed following a chip Reset and by entering Power-down
mode. PLL is enabled by software only. The program must configure and activate the PLL,
wait for the PLL to lock, then connect to the PLL as a clock source.
When the main oscillator is initially activated, the wake-up timer allows software to ensure
that the main oscillator is fully functional before the processor uses it as a clock source
and starts to execute instructions. This is important at power-on, all types of Reset, and
whenever any of the aforementioned functions are turned off for any reason. Since the
oscillator and other functions are turned off during Power-down and Deep power-down
modes, any 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
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
amplitude to drive the clock logic. The amount of time depends on many factors, including
the rate of VDD(3V3) ramp (in the case of power-on), the type of crystal and its electrical
characteristics (if a quartz crystal is used), as well as any other external circuitry (e.g.,
capacitors), and the characteristics of the oscillator itself under the existing ambient
conditions.
The LPC2377/78 also implement a separate power domain in order to allow turning off
power to the bulk of the device while maintaining operation of the RTC and a small SRAM,
referred to as the battery RAM.
The Sleep mode can be terminated and normal operation resumed by either a Reset or
certain specific interrupts that are able to function without clocks. Since all dynamic
operation of the chip is suspended, Sleep mode reduces chip power consumption to a
very low value. The flash memory is left on in Sleep mode, allowing a very quick wake-up.
On the wake-up of Sleep mode, if the IRC was used before entering Sleep mode, the
code execution and peripherals activities will resume after 4 cycles expire. If the main
external oscillator was used, the code execution will resume when 4096 cycles expire.
The customers need to reconfigure the PLL and clock dividers accordingly.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
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. The customers need to
reconfigure the PLL and clock dividers accordingly.
If power is supplied to the LPC2377/78 during Deep power-down mode, wake-up can be
caused by the RTC Alarm interrupt or by external Reset.
While in Deep power-down mode, external device power may be removed. In this case,
the LPC2377/78 will start up when external power is restored.
Essential data may be retained through Deep power-down mode (or through complete
powering off of the chip) by storing data in the Battery RAM, as long as the external power
to the VBAT pin is maintained.
On the LPC2377/78, I/O pads are powered by the 3.3 V (VDD(3V3)) pins, while the
VDD(DCDC)(3V3) pin powers the on-chip DC-to-DC converter which in turn provides power to
the CPU and most of the peripherals.
Depending on the LPC2377/78 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
VDD(3V3) and VDD(DCDC)(3V3) pins together. This approach 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 (VDD(3V3)) and
a dedicated 3.3 V supply for the CPU (VDD(DCDC)(3V3)). Having the on-chip DC-to-DC
converter powered independently from the I/O pad ring enables shutting down of the I/O
pad power supply “on the fly”, while the CPU and peripherals stay active.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
The VBAT pin supplies power only to the RTC and the battery RAM. These two functions
require a minimum of power to operate, which can be supplied by an external battery.
When the CPU and the rest of chip functions are stopped and power removed, the RTC
can supply an alarm output that may be used by external hardware to restore chip power
and resume operation.
7.26.1 Reset
Reset has four sources on the LPC2377/78: the RESET pin, the watchdog reset,
power-on reset, and the BrownOut Detection (BOD) circuit. The RESET pin is a Schmitt
trigger input pin. Assertion of chip Reset by any source, once the operating voltage attains
a usable level, starts the wake-up timer (see description in Section 7.25.3 “Wake-up
timer”), causing reset to remain asserted until the external Reset is de-asserted, the
oscillator is running, a fixed number of clocks have passed, and the flash controller has
completed its initialization.
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 second stage of low-voltage detection asserts Reset to inactivate the LPC2377/78
when the voltage on the VDD(DCDC)(3V3) pins falls below 2.65 V. This Reset prevents
alteration of the flash as operation of the various elements of the chip would otherwise
become unreliable due to low voltage. The BOD circuit maintains this reset down below
1 V, at which point the power-on reset circuitry maintains the overall Reset.
Both the 2.95 V and 2.65 V thresholds include some hysteresis. In normal operation, this
hysteresis allows the 2.95 V detection to reliably interrupt, or a regularly executed event
loop to sense the condition.
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.
CRP2 disables access to chip via the JTAG and only allows full flash erase and update
using a reduced set of the ISP commands.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
Running an application with level CRP3 selected fully disables any access to chip via the
JTAG 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.
CAUTION
If level three Code Read Protection (CRP3) is selected, no future factory testing can be
performed on the device.
7.26.4 AHB
The LPC2377/78 implement two AHBs in order to allow the Ethernet block to operate
without interference caused by other system activity. The primary AHB, referred to as
AHB1, includes the Vectored Interrupt Controller, GPDMA controller, USB interface, and
8 kB SRAM primarily intended for use by the USB.
The second AHB, referred to as AHB2, includes only the Ethernet block and an
associated 16 kB SRAM. In addition, a bus bridge is provided that allows the secondary
AHB to be a bus master on AHB1, allowing expansion of Ethernet buffer space into
off-chip memory or unused space in memory residing on AHB1.
In summary, bus masters with access to AHB1 are the ARM7 itself, the USB block, the
GPDMA function, and the Ethernet block (via the bus bridge from AHB2). Bus masters
with access to AHB2 are the ARM7 and the Ethernet block.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
7.27.1 EmbeddedICE
The EmbeddedICE logic provides on-chip debug support. The debugging of the target
system requires a host computer running the debugger software and an EmbeddedICE
protocol convertor. The EmbeddedICE protocol convertor converts the Remote Debug
Protocol commands to the JTAG data needed to access the ARM7TDMI-S core present
on the target system.
The ARM core has a Debug Communication Channel (DCC) function built-in. The DCC
allows a program running on the target to communicate with the host debugger or another
separate host without stopping the program flow or even entering the debug state. The
DCC is accessed as a coprocessor 14 by the program running on the ARM7TDMI-S core.
The DCC allows the JTAG port to be used for sending and receiving data without affecting
the normal program flow. The DCC data and control registers are mapped in to addresses
in the EmbeddedICE logic.
The JTAG clock (TCK) must be slower than 1⁄6 of the CPU clock (CCLK) for the JTAG
interface to operate.
The ETM is connected directly to the ARM core and not to the main AMBA system bus. It
compresses the trace information and exports it through a narrow trace port. An external
Trace Port Analyzer captures the trace information under software debugger control. The
trace port can broadcast the Instruction trace information. Instruction trace (or PC trace)
shows the flow of execution of the processor and provides a list of all the instructions that
were executed. Instruction trace is significantly compressed by only broadcasting branch
addresses as well as a set of status signals that indicate the pipeline status on a cycle by
cycle basis. Trace information generation can be controlled by selecting the trigger
resource. Trigger resources include address comparators, counters and sequencers.
Since trace information is compressed the software debugger requires a static image of
the code being executed. Self-modifying code can not be traced because of this
restriction.
7.27.3 RealMonitor
RealMonitor is a configurable software module, developed by ARM Inc., which enables
real-time debug. It is a lightweight debug monitor that runs in the background while users
debug their foreground application. It communicates with the host using the DCC, which is
present in the EmbeddedICE logic. The LPC2377/78 contain a specific configuration of
RealMonitor software programmed into the on-chip ROM memory.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
8. Limiting values
Table 4. Limiting values
In accordance with the Absolute Maximum Rating System (IEC 60134).[1]
Symbol Parameter Conditions Min Max Unit
VDD(3V3) supply voltage (3.3 V) core and external 3.0 3.6 V
rail
VDD(DCDC)(3V3) DC-to-DC converter supply voltage 3.0 3.6 V
(3.3 V)
VDDA analog 3.3 V pad supply voltage 0.5 +4.6 V
Vi(VBAT) input voltage on pin VBAT for the RTC 0.5 +4.6 V
Vi(VREF) input voltage on pin VREF 0.5 +4.6 V
VIA analog input voltage on ADC related 0.5 +5.1 V
pins
VI input voltage 5 V tolerant I/O [2] 0.5 +6.0 V
pins; only valid
when the VDD(3V3)
supply voltage is
present
other I/O pins [2][3] 0.5 VDD(3V3) + 0.5 V
IDD supply current per supply pin [4] - 100 mA
ISS ground current per ground pin [4] - 100 mA
Tstg storage temperature non-operating [5] 65 +150 C
Ptot(pack) total power dissipation (per package) based on package - 1.5 W
heat transfer, not
device power
consumption
VESD electrostatic discharge voltage human body [6] 2500 +2500 V
model; all pins
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
9. Thermal characteristics
The average chip junction temperature, Tj (C), can be calculated using the following
equation:
T j = T amb + P D R th j – a (1)
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
mode DC-to-DC
converter supply
current (3.3 V) - 20 - A
IBATact active mode battery [4]
supply current - 20 - A
IBAT battery supply current Deep power-down mode [3] - 20 - A
Standard port pins, RESET, RTCK
IIL LOW-level input VI = 0 V; no pull-up - - 3 A
current
IIH HIGH-level input VI = VDD(3V3); no pull-down - - 3 A
current
IOZ OFF-state output VO = 0 V; VO = VDD(3V3); - - 3 A
current no pull-up/down
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
[1] Typical ratings are not guaranteed. The values listed are at room temperature (25 C), nominal supply voltages.
[2] The RTC typically fails when Vi(VBAT) drops below 1.6 V.
[3] VDD(DCDC)(3V3) = 3.3 V; VDD(3V3) = 3.3 V; Vi(VBAT) = 3.3 V; Tamb = 25 C.
[4] On pin VBAT.
[5] Including voltage on outputs in 3-state mode.
[6] VDD(3V3) supply voltages must be present.
[7] 3-state outputs go into 3-state mode when VDD(3V3) is grounded.
[8] Please also see the errata note in errata sheet.
[9] Accounts for 100 mV voltage drop in all supply lines.
[10] Allowed as long as the current limit does not exceed the maximum current allowed by the device.
[11] Minimum condition for VI = 4.5 V, maximum condition for VI = 5.5 V.
[12] To VSS.
[13] Includes external resistors of 33 1 % on D+ and D.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
002aae049
4
IDD(IO)
(μA)
2
VDD(3V3) = 3.3 V
VDD(3V3) = 3.0 V
−2
−4
−40 −15 10 35 60 85
temperature (°C)
002aae050
40
IBAT
(μA)
30
Vi(VBAT) = 3.3 V
Vi(VBAT) = 3.0 V
20
10
0
−40 −15 10 35 60 85
temperature (°C)
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
002aae051
800
IDD(DCDC)pd(3v3)
(μA)
600
400
VDD(DCDC)(3V3) = 3.3 V
0
−40 −15 10 35 60 85
temperature (°C)
002aae046
300
IDD(IO)
(μA)
200
100
VDD(3V3) = 3.3 V
VDD(3V3) = 3.0 V
0
−40 −15 10 35 60 85
temperature (°C)
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
002aae047
40
IBAT
(μA)
30
Vi(VBAT) = 3.3 V
Vi(VBAT) = 3.0 V
20
10
0
−40 −15 10 35 60 85
temperature (°C)
002aae048
100
IDD(DCDC)dpd(3v3)
(μA)
80
60
VDD(DCDC)(3V3) = 3.3 V
40
VDD(DCDC)(3V3) = 3.0 V
20
0
−40 −15 10 35 60 85
temperature (°C)
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
002aaf112
3.6
VOH
(V)
T = 85 °C
3.2 25 °C
−40 °C
2.8
2.4
2.0
0 8 16 24
IOH (mA)
002aaf111
15
IOL T = 85 °C
(mA) 25 °C
−40 °C
10
0
0 0.2 0.4 0.6
VOL (V)
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
[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.
[3] Bus capacitance Cb in pF, from 10 pF to 400 pF.
tCHCX
tCHCL tCLCX tCLCH
Tcy(clk)
002aaa907
Fig 12. External clock timing (with an amplitude of at least Vi(RMS) = 200 mV)
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
[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.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
NXP Semiconductors
11.5 Static external memory interface
Table 13. Dynamic characteristics: Static external memory interface
CL = 30 pF, Tamb = 40 C to 85 C, VDD(DCDC)(3V3) = VDD(3V3) = 3.0 V to 3.6 V
Symbol Parameter Conditions Min Typ Max Unit
Common to read and write cycles[1]
tCSLAV CS LOW to address valid 0.29 0.20 2.54 ns
time
Read cycle parameters[1][2]
tOELAV OE LOW to address valid 0.29 0.20 2.54 ns
time
tCSLOEL CS LOW to OE LOW time 0.78 + Tcy(CCLK) WAITOEN 0 + Tcy(CCLK) WAITOEN 0.49 + Tcy(CCLK) WAITOEN ns
tam memory access time [3][4] (WAITRD WAITOEN + 1) (WAITRD WAITOEN + 1) (WAITRD WAITOEN + 1) ns
All information provided in this document is subject to legal disclaimers.
LPC2377/78
tBLSHDNV BLS HIGH to data invalid [3] 0.78 2.54 5.96 ns
time
© NXP B.V. 2013. All rights reserved.
11.6 Timing
tCSLAV tCSHOEH
CS
addr
tam th(D)
data
tCSLOEL
tOELAV tOEHANV
tOELOEH
OE
002aaf489
CS
tCSLAV
tBLSLBLSH
BLS
addr
tCSLDV
tBLSHDNV
data
OE
002aaf490
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
002aab561
shifting edges
SCK
sampling edges
MOSI
MISO
tsu(SPI_MISO)
002aad326
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
offset gain
error error
EO EG
1023
1022
1021
1020
1019
1018
(2)
7
code (1)
out
6
(5)
4
(4)
3
(3)
2
1 1 LSB
(ideal)
0
1 2 3 4 5 6 7 1018 1019 1020 1021 1022 1023 1024
VIA (LSBideal)
offset error
EO Vi(VREF) − VSSA
1 LSB =
1024
002aae604
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC23XX
20 kΩ Rvsi
AD0[y]
AD0[y]SAMPLE
3 pF 5 pF
VEXT
VSS
002aac610
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
VDD(3V3)
USB_UP_LED
USB_CONNECT
LPC23XX
SoftConnect switch
R1
1.5 kΩ
VBUS
USB_D+ RS = 33 Ω USB-B
connector
USB_D− RS = 33 Ω
VSS
002aac578
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
VDD(3V3)
R2
LPC23XX R1
USB_UP_LED 1.5 kΩ
VBUS
USB_D+ RS = 33 Ω USB-B
connector
USB_D− RS = 33 Ω
VSS
002aac579
LPC2xxx
XTAL1
Ci Cg
100 pF
002aae718
In slave mode the input clock signal should be coupled by means of a capacitor of 100 pF
(Figure 21), 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 22 and in
Table 16 and Table 17. Since the feedback resistance is integrated on chip, only a crystal
and the capacitances CX1 and CX2 need to be connected externally in case of
fundamental mode oscillation (the fundamental frequency is represented by L, CL and
RS). Capacitance CP in Figure 22 represents the parallel package capacitance and should
not be larger than 7 pF. Parameters FOSC, CL, RS and CP are supplied by the crystal
manufacturer.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2xxx
XTALIN XTALOUT
= CL CP
XTAL
RS
CX1 CX2
002aaf494
Fig 22. Oscillator modes and models: oscillation mode of operation and external crystal
model used for CX1/CX2 evaluation
Table 16. Recommended values for CX1/CX2 in oscillation mode (crystal and external
components parameters): low frequency mode
Fundamental oscillation Crystal load Maximum crystal External load
frequency FOSC capacitance CL series resistance RS capacitors CX1/CX2
1 MHz to 5 MHz 10 pF < 300 18 pF, 18 pF
20 pF < 300 39 pF, 39 pF
30 pF < 300 57 pF, 57 pF
5 MHz to 10 MHz 10 pF < 300 18 pF, 18 pF
20 pF < 200 39 pF, 39 pF
30 pF < 100 57 pF, 57 pF
10 MHz to 15 MHz 10 pF < 160 18 pF, 18 pF
20 pF < 60 39 pF, 39 pF
15 MHz to 20 MHz 10 pF < 80 18 pF, 18 pF
Table 17. Recommended values for CX1/CX2 in oscillation mode (crystal and external
components parameters): high frequency mode
Fundamental oscillation Crystal load Maximum crystal External load
frequency FOSC capacitance CL series resistance RS capacitors CX1, CX2
15 MHz to 20 MHz 10 pF < 180 18 pF, 18 pF
20 pF < 100 39 pF, 39 pF
20 MHz to 25 MHz 10 pF < 160 18 pF, 18 pF
20 pF < 80 39 pF, 39 pF
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2xxx
RTCX1 RTCX2
= CL CP
32 kHz XTAL
RS
CX1 CX2
002aaf495
Fig 23. RTC oscillator modes and models: oscillation mode of operation and external
crystal model used for CX1/CX2 evaluation
The RTC external oscillator circuit is shown in Figure 23. Since the feedback resistance is
integrated on chip, only a crystal, the capacitances CX1 and CX2 need to be connected
externally to the microcontroller.
Table 18 gives the crystal parameters that should be used. CL is the typical load
capacitance of the crystal and is usually specified by the crystal manufacturer. The actual
CL influences oscillation frequency. When using a crystal that is manufactured for a
different load capacitance, the circuit will oscillate at a slightly different frequency
(depending on the quality of the crystal) compared to the specified one. Therefore for an
accurate time reference it is advised to use the load capacitors as specified in Table 18
that belong to a specific CL. The value of external capacitances CX1 and CX2 specified in
this table are calculated from the internal parasitic capacitances and the CL. Parasitics
from PCB and package are not taken into account.
Table 18. Recommended values for the RTC external 32 kHz oscillator CX1/CX2 components
Crystal load capacitance Maximum crystal series External load capacitors CX1/CX2
CL resistance RS
11 pF < 100 k 18 pF, 18 pF
13 pF < 100 k 22 pF, 22 pF
15 pF < 100 k 27 pF, 27 pF
14.4 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 CX1, CX2, and CX3 in case
of third overtone crystal usage have a common ground plane. The external components
must also be connected to the ground plain. Loops must be made as small as possible in
order to keep the noise coupled in via the PCB as small as possible. Also parasitics
should stay as small as possible. Values of CX1 and CX2 should be chosen smaller
accordingly to the increase in parasitics of the PCB layout.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
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.
VDD
ESD
VDD VSS
weak
pull-up
pull-up enable
weak
pin configured pull-down
as digital input pull-down enable
data input
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
VDD
VDD
VDD
Rpu ESD
20 ns RC
reset PIN
GLITCH FILTER
ESD
VSS
002aaf274
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LQFP144: plastic low profile quad flat package; 144 leads; body 20 x 20 x 1.4 mm SOT486-1
c
y
X
108 73
109 72
ZE
E HE A A2
A1 (A 3)
wM θ
Lp
bp
L
pin 1 index
detail X
144 37
1 36
wM ZD v M A
e bp
D B
HD v M B
0 5 10 mm
scale
mm
0.15 1.45 0.27 0.20 20.1 20.1 22.15 22.15 0.75 1.4 1.4 7o
1.6 0.25 0.5 1 0.2 0.08 0.08 o
0.05 1.35 0.17 0.09 19.9 19.9 21.85 21.85 0.45 1.1 1.1 0
Note
1. Plastic or metal protrusions of 0.25 mm maximum per side are not included.
00-03-14
SOT486-1 136E23 MS-026
03-02-20
16. Abbreviations
Table 19. Acronym list
Acronym Description
ADC Analog-to-Digital Converter
AHB Advanced High-performance Bus
AMBA Advanced Microcontroller Bus Architecture
APB Advanced Peripheral Bus
BLS Byte Lane Select
BOD BrownOut Detection
CAN Controller Area Network
CTS Clear To Send
DAC Digital-to-Analog Converter
DCC Debug Communication Channel
DMA Direct Memory Access
DSP Digital Signal Processing
EOP End Of Packet
ETM Embedded Trace Macrocell
GPIO General Purpose Input/Output
JTAG Joint Test Action Group
MII Media Independent Interface
MIIM Media Independent Interface Management
PHY Physical Layer
PLL Phase-Locked Loop
PWM Pulse Width Modulator
RMII Reduced Media Independent Interface
RTS Request To Send
SE0 Single Ended Zero
SPI Serial Peripheral Interface
SSI Synchronous Serial Interface
SSP Synchronous Serial Port
TTL Transistor-Transistor Logic
UART Universal Asynchronous Receiver/Transmitter
USB Universal Serial Bus
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
[1] Please consult the most recently issued document before initiating or completing a design.
[2] The term ‘short data sheet’ is explained in section “Definitions”.
[3] The product status of device(s) described in this document may have changed since this document was published and may differ in case of multiple devices. The latest product status
information is available on the Internet at URL http://www.nxp.com.
18.2 Definitions 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
Draft — The document is a draft version only. The content is still under
malfunction of an NXP Semiconductors product can reasonably be expected
internal review and subject to formal approval, which may result in
to result in personal injury, death or severe property or environmental
modifications or additions. NXP Semiconductors does not give any
damage. NXP Semiconductors and its suppliers accept no liability for
representations or warranties as to the accuracy or completeness of
inclusion and/or use of NXP Semiconductors products in such equipment or
information included herein and shall have no liability for the consequences of
applications and therefore such inclusion and/or use is at the customer’s own
use of such information.
risk.
Short data sheet — A short data sheet is an extract from a full data sheet
Applications — Applications that are described herein for any of these
with the same product type number(s) and title. A short data sheet is intended
products are for illustrative purposes only. NXP Semiconductors makes no
for quick reference only and should not be relied upon to contain detailed and
representation or warranty that such applications will be suitable for the
full information. For detailed and full information see the relevant full data
specified use without further testing or modification.
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 Customers are responsible for the design and operation of their applications
full data sheet shall prevail. and products using NXP Semiconductors products, and NXP Semiconductors
accepts no liability for any assistance with applications or customer product
Product specification — The information and data provided in a Product design. It is customer’s sole responsibility to determine whether the NXP
data sheet shall define the specification of the product as agreed between Semiconductors product is suitable and fit for the customer’s applications and
NXP Semiconductors and its customer, unless NXP Semiconductors and products planned, as well as for the planned application and use of
customer have explicitly agreed otherwise in writing. In no event however, customer’s third party customer(s). Customers should provide appropriate
shall an agreement be valid in which the NXP Semiconductors product is design and operating safeguards to minimize the risks associated with their
deemed to offer functions and qualities beyond those described in the applications and products.
Product data sheet.
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
18.3 Disclaimers 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
Limited warranty and liability — Information in this document is believed to
Semiconductors products in order to avoid a default of the applications and
be accurate and reliable. However, NXP Semiconductors does not give any
the products or of the application or use by customer’s third party
representations or warranties, expressed or implied, as to the accuracy or
customer(s). NXP does not accept any liability in this respect.
completeness of such information and shall have no liability for the
consequences of use of such information. NXP Semiconductors takes no Limiting values — Stress above one or more limiting values (as defined in
responsibility for the content in this document if provided by an information the Absolute Maximum Ratings System of IEC 60134) will cause permanent
source outside of NXP Semiconductors. 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
In no event shall NXP Semiconductors be liable for any indirect, incidental,
the Recommended operating conditions section (if present) or the
punitive, special or consequential damages (including - without limitation - lost
Characteristics sections of this document is not warranted. Constant or
profits, lost savings, business interruption, costs related to the removal or
repeated exposure to limiting values will permanently and irreversibly affect
replacement of any products or rework charges) whether or not such
the quality and reliability of the device.
damages are based on tort (including negligence), warranty, breach of
contract or any other legal theory. Terms and conditions of commercial sale — NXP Semiconductors
Notwithstanding any damages that customer might incur for any reason products are sold subject to the general terms and conditions of commercial
whatsoever, NXP Semiconductors’ aggregate and cumulative liability towards sale, as published at http://www.nxp.com/profile/terms, unless otherwise
customer for the products described herein shall be limited in accordance agreed in a valid written individual agreement. In case an individual
with the Terms and conditions of commercial sale of NXP Semiconductors. agreement is concluded only the terms and conditions of the respective
agreement shall apply. NXP Semiconductors hereby expressly objects to
Right to make changes — NXP Semiconductors reserves the right to make applying the customer’s general terms and conditions with regard to the
changes to information published in this document, including without purchase of NXP Semiconductors products by customer.
limitation specifications and product descriptions, at any time and without
notice. This document supersedes and replaces all information supplied prior No offer to sell or license — Nothing in this document may be interpreted or
to the publication hereof. construed as an offer to sell products that is open for acceptance or the grant,
conveyance or implication of any license under any copyrights, patents or
other industrial or intellectual property rights.
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
Export control — This document as well as the item(s) described herein whenever customer uses the product for automotive applications beyond
may be subject to export control regulations. Export might require a prior NXP Semiconductors’ specifications such use shall be solely at customer’s
authorization from competent authorities. own risk, and (c) customer fully indemnifies NXP Semiconductors for any
liability, damages or failed product claims resulting from customer design and
Non-automotive qualified products — Unless this data sheet expressly
use of the product for automotive applications beyond NXP Semiconductors’
states that this specific NXP Semiconductors product is automotive qualified,
standard warranty and NXP Semiconductors’ product specifications.
the product is not suitable for automotive use. It is neither qualified nor tested
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 equipment or applications.
18.4 Trademarks
In the event that customer uses the product for design-in and use in Notice: All referenced brands, product names, service names and trademarks
automotive applications to automotive specifications and standards, customer are the property of their respective owners.
(a) shall use the product without NXP Semiconductors’ warranty of the I2C-bus — logo is a trademark of NXP B.V.
product for such automotive applications, use and specifications, and (b)
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
20. Contents
1 General description . . . . . . . . . . . . . . . . . . . . . . 1 7.21 General purpose 32-bit timers/external event
2 Features and benefits . . . . . . . . . . . . . . . . . . . . 1 counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 7.21.1 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
7.22 Pulse width modulator . . . . . . . . . . . . . . . . . . 28
4 Ordering information . . . . . . . . . . . . . . . . . . . . . 3
7.22.1 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.1 Ordering options . . . . . . . . . . . . . . . . . . . . . . . . 3 7.23 Watchdog timer . . . . . . . . . . . . . . . . . . . . . . . 30
5 Block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 4 7.23.1 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
6 Pinning information . . . . . . . . . . . . . . . . . . . . . . 5 7.24 RTC and battery RAM . . . . . . . . . . . . . . . . . . 31
6.1 Pinning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 7.24.1 Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
6.2 Pin description . . . . . . . . . . . . . . . . . . . . . . . . . 6 7.25 Clocking and power control . . . . . . . . . . . . . . 31
7 Functional description . . . . . . . . . . . . . . . . . . 16 7.25.1 Crystal oscillators . . . . . . . . . . . . . . . . . . . . . . 31
7.1 Architectural overview . . . . . . . . . . . . . . . . . . 16 7.25.1.1 Internal RC oscillator . . . . . . . . . . . . . . . . . . . 31
7.2 On-chip flash programming memory . . . . . . . 17 7.25.1.2 Main oscillator . . . . . . . . . . . . . . . . . . . . . . . . 32
7.3 On-chip SRAM . . . . . . . . . . . . . . . . . . . . . . . . 17 7.25.1.3 RTC oscillator . . . . . . . . . . . . . . . . . . . . . . . . 32
7.4 Memory map. . . . . . . . . . . . . . . . . . . . . . . . . . 18 7.25.2 PLL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
7.5 Interrupt controller . . . . . . . . . . . . . . . . . . . . . 19 7.25.3 Wake-up timer . . . . . . . . . . . . . . . . . . . . . . . . 32
7.5.1 Interrupt sources. . . . . . . . . . . . . . . . . . . . . . . 19 7.25.4 Power control . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.6 Pin connect block . . . . . . . . . . . . . . . . . . . . . . 19 7.25.4.1 Idle mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.7 External memory controller. . . . . . . . . . . . . . . 19 7.25.4.2 Sleep mode . . . . . . . . . . . . . . . . . . . . . . . . . . 33
7.7.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 7.25.4.3 Power-down mode . . . . . . . . . . . . . . . . . . . . . 34
7.8 General purpose DMA controller . . . . . . . . . . 20 7.25.4.4 Deep power-down mode . . . . . . . . . . . . . . . . 34
7.8.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 7.25.4.5 Power domains . . . . . . . . . . . . . . . . . . . . . . . 34
7.9 Fast general purpose parallel I/O . . . . . . . . . . 21 7.26 System control . . . . . . . . . . . . . . . . . . . . . . . . 35
7.9.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 7.26.1 Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
7.10 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 7.26.2 Brownout detection . . . . . . . . . . . . . . . . . . . . 35
7.10.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 7.26.3 Code security
7.11 USB interface (LPC2378 only) . . . . . . . . . . . . 23 (Code Read Protection - CRP) . . . . . . . . . . . 35
7.11.1 USB device controller . . . . . . . . . . . . . . . . . . . 23 7.26.4 AHB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
7.11.1.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 7.26.5 External interrupt inputs . . . . . . . . . . . . . . . . . 36
7.12 CAN controller and acceptance filters 7.26.6 Memory mapping control . . . . . . . . . . . . . . . . 36
(LPC2378 only). . . . . . . . . . . . . . . . . . . . . . . . 24 7.27 Emulation and debugging . . . . . . . . . . . . . . . 36
7.12.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.27.1 EmbeddedICE . . . . . . . . . . . . . . . . . . . . . . . . 37
7.13 10-bit ADC . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.27.2 Embedded trace. . . . . . . . . . . . . . . . . . . . . . . 37
7.13.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 7.27.3 RealMonitor . . . . . . . . . . . . . . . . . . . . . . . . . . 37
7.14 10-bit DAC . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 8 Limiting values . . . . . . . . . . . . . . . . . . . . . . . . 38
7.14.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 9 Thermal characteristics . . . . . . . . . . . . . . . . . 39
7.15 UARTs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 10 Static characteristics . . . . . . . . . . . . . . . . . . . 40
7.15.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 10.1 Power-down mode . . . . . . . . . . . . . . . . . . . . . 43
7.16 SPI serial I/O controller. . . . . . . . . . . . . . . . . . 25 10.2 Deep power-down mode . . . . . . . . . . . . . . . . 44
7.16.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 10.3 Electrical pin characteristics. . . . . . . . . . . . . . 46
7.17 SSP serial I/O controller . . . . . . . . . . . . . . . . . 26
11 Dynamic characteristics. . . . . . . . . . . . . . . . . 47
7.17.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
11.1 Internal oscillators . . . . . . . . . . . . . . . . . . . . . 48
7.18 SD/MMC card interface . . . . . . . . . . . . . . . . . 26
11.2 I/O pins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.18.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
11.3 USB interface. . . . . . . . . . . . . . . . . . . . . . . . . 48
7.19 I2C-bus serial I/O controllers. . . . . . . . . . . . . . 26
11.4 Flash memory . . . . . . . . . . . . . . . . . . . . . . . . 49
7.19.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
11.5 Static external memory interface . . . . . . . . . . 50
7.20 I2S-bus serial I/O controllers. . . . . . . . . . . . . . 27
11.6 Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7.20.1 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
continued >>
LPC2377_78 All information provided in this document is subject to legal disclaimers. © NXP B.V. 2013. All rights reserved.
Please be aware that important notices concerning this document and the product(s)
described herein, have been included in section ‘Legal information’.