NXP Semiconductor designed the LPC2400 microcontrollers around a 16-bit/32-bit
ARM7TDMI-S CPU core with real-time debug interfaces that include both JTAG and
embedded Trace. The LPC2400 microcontrollers have 512 kB of on-chip high-speed
Flash memory. This Flash memory includes a special 128-bit wide memory interface and
accelerator architecture that enables the CPU to execute sequential instructions from
Flash memory at the maximum 72 MHz system clock rate. This feature is available only
on the LPC2000 ARM Microcontroller family of products. The LPC2400 can execute both
32-bit ARM and 16-bit Thumb instructions. Support for the two Instruction Sets means
Engineers can choose to optimize their application for either performance or code size at
the sub-routine level. When the core executes instructions in Thumb state it can reduce
code size by more than 30 % with only a small loss in performance while executing
instructions in ARM state maximizes core performance.
The LPC2400 microcontrollers are ideal for multi-purpose communication applications. It
incorporates a 10/100 Ethernet Media Access Controller (MAC), a USB full speed
device/host/OTG controller with 4 kB of endpoint RAM, four UARTs, two Controller Area
Network (CAN) channels, an SPI interface, two Synchronous Serial Ports (SSP), three I
interfaces, and an I
interfaces are the following feature components; an on-chip 4 MHz internal precision
oscillator, 98 kB of total RAM consisting of 64 kB of local SRAM, 16 kB SRAM for
Ethernet, 16 kB SRAM for general purpose DMA, 2 kB of battery powered SRAM, and an
External Memory Controller (EMC). These features make this device optimally suited for
communication gateways and protocol converters. Complementing the many serial
communication controllers, versatile clocking capabilities, and memory features are
various 32-bit timers, an improved 10-bit ADC, 10-bit DAC, two PWM units, four external
interrupt pins, and up to 160 fast GPIO lines. The LPC2400 connect 64 of the GPIO pins
to the hardware based Vector Interrupt Controller (VIC) that means these external inputs
can generate edge-triggered, interrupt s. All of these features make the LPC2400
particularly suitable for industrial control and medical systems.
2.How to read this manual
Important: The term “LPC24XX“ in this user manual will be used as a generic name for all
LPC2400 parts. It covers the following parts: LPC2458, LPC2420, LPC2460, LPC2468,
LPC2470, and LPC2478.
2
S interface. Supporting this collection of serial communications
2
C
For information about individual parts refer to Table 1–1
– 64 kB of SRAM on the ARM local bus for high performance CPU access.
– 16 kB SRAM for Ethernet interface. Can also be used as general purpose SRAM.
– 16 kB SRAM for general purpose DMA use also accessible by the USB.
– 2 kB SRAM data storage powered from the RTC power domain.
• LPC2458/68/78 only: 512 kB on-chip Flash program memory with In-System
Programming (ISP) and In-Application Programming (IAP) capabilities. Flash program
memory is on the ARM local bus for high performance CPU access.
• Dual Advanced High-performance Bus (AHB) system allows memory access by
multiple resources and simultaneous program execution with no contention.
• EMC provides support for asynchronous static memory devices such as RAM, ROM
and Flash, as well as dynamic memories such as Single Data Rate SDRAM.
• Advanced Vectored Inter rupt Controller ( VIC), supportin g up to 32 vectored interru pt s.
• General Purpose AHB DMA controller (GPDMA) that can be used with the SSP, I
and SD/MM interface as well as for memory-to-memory transfers.
• LPC2470/78 only: LCD controller , sup porting both Super-Twisted Nematic (STN) and
Thin-Film Transistors (TFT) displays.
– Dedicated DMA controller.
– Selectable display resolution (up to 1024 × 768 pixels).
– Supports up to 24-bit true-color mode.
• Serial Interfaces:
– Ethernet MAC with MII/RMII interface and associated DMA controller. These
functions reside on an independent AHB bus.
– USB 2.0 full-speed dual port device/host/OTG controller with on-chip PHY and
associated DMA controller.
– Four UARTs with fractional baud rate generation, one with modem contro l I/O, one
• Three reduced power modes: idle, sleep, and power-down.
• Four external interrupt inputs configurable as edge/level sen sitive. All pins on POR T0
• Processor wake-up from Power-down mode via any interrupt able to operate during
• Two independent power domains allow fine tuning of power consumption based on
• Each peripheral has its own clock divider for further power saving. These dividers help
• Brownout detect with separate thresholds for interrupt and forced reset.
• On-chip power-on reset.
• On-chip crystal oscillator with an operating range of 1 MHz to 24 MHz.
• 4 MHz internal RC oscillator trimmed to 1 % ac curacy that can optionally be used as
• On-chip PLL allows CPU operation up to the maximum CPU rate without the need for
UM10237
Chapter 1: LPC24XX Introductory information
– SPI controller.
– Two SSP controllers, with FIFO and multi-protocol capabilities. One is an alternate
for the SPI port, sharing its interrupt. SSPs can be used with the GPDMA
controller.
2
– Three I
2
– I
the GPDMA.
– SD/MMC memory card interface.
– 160 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.
– Two PWM/timer blocks with support for three-phase motor control. Each PWM has
an external count inputs.
– Real-Time Clock (RTC) with separate power domain, 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.
and PORT2 can be used as edge sensitive interrupt sources.
Power-down mode (includes external interrupts, RTC interrupt, USB activity, Ethernet
wake-up interrupt, CAN bus activity, PORT0/2 pin interrupt).
needed features.
reducing active power by 20 - 30 %.
the system clock. When used as the CPU clock, does not allow CAN and USB to run.
a high frequency crystal. May be run from the main oscillator, the internal RC
oscillator, or the RTC oscillator.
C-bus interfaces (one with open-drain and two with standard port pins).
S (Inter-IC Sound) interface for digital audio input or output. It can be used with
The LPC2400 microcontroller consists of an ARM7TDMI-S CPU with emulation support,
the ARM7 local bus for closely coupled, high speed ac cess to th e ma jo rity of on- ch ip
memory, the AMBA AHB interfacing to high speed on-chip peripherals and external
memory, and the AMBA APB for connection to other on-chip peripheral functions. The
microcontroller permanently configures the ARM7TDMI-S processor for little-endian byte
order.
Ethernet USB
OTG/
OHC/
Device
+ 4 kB
FIFO
MII/RMIIyes2 yesyes81−40 °C
MII/RMIIyes2 yesyes81−40 °C
SD/
GP
MMC
DMA
CAN channels
Temp
range
ADC channels
DAC channels
to
+85 °C
to
+85 °C
The LPC2400 implements two AHB buses in order to allow the Ethernet block to operate
without interference caused by other system activity. The primary AHB, referred to as
AHB1, includes the 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 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 resid ing 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 very top of the 4 GB
ARM memory space. Each AHB peripheral is allocated a 16 kB address space within the
AHB address space. Lower speed peripheral functions are connected to the APB bus.
The AHB to APB bridge interfaces the APB bus to the AHB bus. APB peripherals are also
allocated a 2 MB range of addresses, beginning at the 3.5 GB address point. Each APB
peripheral is allocated a 16 kB address space within the APB address space.
The ARM7TDMI-S processor is a general purpose 32-bit microprocessor, which offers
high performance and very low power consumption. The ARM architecture is based on
Reduced Instruction Set Computer (RISC) principles, and the instruction set and related
decode mechanism are much simpler than those of microprogrammed complex
instruction set computers. This simplicity results in a high instruction throughput and
impressive real-time interrupt response from a small and cost-effective processor core.
UM10237
Chapter 1: LPC24XX Introductory information
Pipeline techniques are employed so that all pa rts of the p rocessing and memory systems
can operate continuously. T ypically, while one instruction is being executed, its successor
is being decoded, and a third instruction is being fetched from memory.
The ARM7TDMI-S processor also employs a unique architectural strategy known as
Thumb, which makes it ideally suited to high-volume applications with memory
restrictions, or applications where code density is an issue.
The key idea behind Thumb is that of a super-reduced instruction set. Essentially, the
ARM7TDMI-S processor has two instruction sets:
• the standard 32-bit ARM set
• a 16-bit Thumb set
The Thumb set’s 16-bit instruction length allows it to approach higher density comp ared to
standard ARM code while retaining most of the ARM’s performance.
The LPC2400 incorporates 512 kB Flash memory system. This memory may be used for
both code and data storage. Programming of the Flash memory may be accomplished in
several ways. It may be programmed In System via the serial port (UART0). The
application program may also erase and/or program the Flash while the application is
running, allowing a great degree of flexibility for data storage field and firmware upgrades.
The Flash memory is 128 bits wide and includes pre-fetching and buffering techniques to
allow it to operate at speeds of 72 MHz.
The LPC2400 provides a minimum of 100 000 writ e/ eras e cycles and 20 years of data
retention.
The LPC2400 includes a SRAM memory of 64 kB reserved for the ARM processor
exclusive use. This RAM may be used for code and/o r data sto rage and may be accessed
as 8 bits, 16 bits, and 32 bits.
A 16 kB SRAM block serving as a buffer for the Ethernet controller and a 16 kB SRAM
associated with the second AHB bus can be used both for data and code storage, too.
Remaining SRAM such as a 4 kB USB FIFO and a 2 kB RTC SRAM can be used for data
storage only . The R TC SRAM is battery powered a nd retains the content in the absence of
the main power supply.
Address rangeGeneral useAddress range details and description
0x8000 0000 to
0xDFFF FFFF
0xE000 0000 to
0xEFFF FFFF
0xF000 0000 to
0xFFFF FFFF
Off-Chip MemoryFour static memory banks, 16 MB each
0x8000 0000 - 0x80FF FFFFStatic memory bank 0
0x8100 0000 - 0x81FF FFFFStatic memory bank 1
0x8200 0000 - 0x82FF FFFFStatic memory bank 2
0x8300 0000 - 0x83FF FFFFStatic memory bank 3
Four dynamic memory banks, 256 MB each
0xA000 0000 - 0xAFFF FFFFDynamic memory bank 0
0xB000 0000 - 0xBFFF FFFFDynamic memory bank 1
0xC000 0000 - 0xCFFF FFFFDynamic memory bank 2
0xD000 0000 - 0xDFFF FFFFDynamic memory bank 3
APB Peripherals36 peripheral blocks, 16 kB each
AHB peripherals
UM10237
3.Memory maps
The LPC2400 incorporates several distinct memory regions, shown in the following
figures. Figure 2–6
program viewpoint following reset. The interrupt vector area supports address remapping,
which is described later in this section.
shows the overall map of the entire address space from the user
Figure 8 and Table 2–17 show different views of the peripheral address space. Both the
AHB and APB peripheral areas are 2 megabyte spaces which are divided up into 128
peripherals. Each peripheral space is 16 kilobytes in size. This allows simplifying the
address decoding for each peripheral.
All peripheral register addresses are word aligned (to 32 bit boundaries) regardless of
their size. This eliminates the need for byte lane mapping hardware that would be required
to allow byte (8 bit) or half-word (16 bit) accesses to occur at smaller boundaries. An
implication of this is that word and half-word registers must be accessed all at once. For
example, it is not possible to read or write the upper byte of a word register separately.
The following table shows the APB address map. No APB peripheral uses all of the 16 kB
space allocated to it. T ypically each device’ s registers are "aliased" or re peated at multiple
locations within each 16 kB range.
The basic concept on the LPC2400 is that each memory area has a "natural" location in
the memory map. This is the address range for which code residing in that area is written.
The bulk of each memory space remains permanently fixed in the same location,
eliminating the need to have portions of the code designed to run in different address
ranges.
Because of the location of the interrupt vectors on the ARM7 processor (at addresses
0x0000 0000 through 0x0000 001C, as shown in Table 2–18
Boot ROM and SRAM spaces need to be re-mapped in order to allow alternative uses of
interrupts in the differen t operating modes described in Table 2–19
interrupts is accomplished via the Memory Mapping Contro l feature (Section 2–6 “
The Boot Loader always executes after any reset. The Boot ROM
interrupt vectors are mapped to the bottom of memory to allow
handling exceptions and using interrupts during the Boot Loading
process. A sector of the flash memory (the Boot flash) is available to
hold part of the Boot Code.
For LPC2400 parts with flash only . Activated by the Boot Loader when
a valid User Program Signature is recognized in memory and Boot
Loader operation is not forced. Interrupt vectors are not re-mapped
and are found in the bottom of the flash memory.
Activated by a User Program as desired. Interrupt vectors are
re-mapped to the bottom of the Static RAM.
For LPC2400 parts with flash. Interrupt vectors are re-mapped to
external memory bank 0.
For flashless parts LPC2420/60/70 only. Interrupt vectors are
re-mapped to external memory bank 0.
[1]
[2]
[1] See EMCControl register address mirror bit in Table 5–68 for address of external memory bank 0.
[2] Connect external boot memory to chip select 1. During boot from external memory, the address mirror bit is
set and memory bank addresses 0 and 1 are swapped.
5.2 Memory re-mapping
In order to allow for compatibility with future derivatives, the entire Boot ROM is mapped
to the top of the on-chip memory space. In this manner, the use of larger or smaller flash
modules will not require changing the location of the Boot ROM (which would require
changing the Boot Loader code itself) or changing the mapping of the Boot ROM interru pt
vectors. Memory spaces other than the interrupt vectors remain in fixed locations.
Figure 2–9
The portion of memory that is re-mapped to allow interrupt processing in different modes
includes the interrupt vector area (32 bytes) and an additional 32 bytes for a total of
64 bytes, that facilitates branching to interrupt handlers at distant physical addresses. The
remapped code locations overlay addresses 0x0000 0000 through 0x0000 003F. A typical
user program in the flash memory can place the entire FIQ handler at address
0x0000 001C without any nee d to cons ide r me mory boundaries. The vector contained in
the SRAM, external memory , and Boot ROM must cont ain branches to the actual interrupt
handlers, or to other instructions that accomplish the branch to the interrupt hand lers.
There are three reasons this configuration was chosen:
1. To give the FIQ handler in the flash memory the advantage of not having to take a
2. Minimize the need to for the SRAM and Boot ROM vectors to deal with arbitrary
3. To provide space to store constants for jumping beyond the range of single word
shows the on-chip memory mapping in the modes defined above.
memory boundary caused by the remapping into account.
Re-mapped memory areas, including the Boot ROM and interrupt vectors, continue to
appear in their original location in addition to the re-mapped address.
UM10237
Chapter 2: LPC24XX Memory mapping
Details on re-mapping and examples can be found in Section 2–6 “
control” on page 25.
6.Memory mapping control
The Memory Mapping Control alters the mapping of the interrupt vectors that appear
beginning at address 0x0000 0000. This allows code running in different memory spaces
to have control of the interrupts.
6.1 Memory Mapping Control Register (MEMMAP - 0xE01F C040)
Whenever an exception handling is necessary , the microcontroller will fetch an instruction
residing on exception corresponding address as described in Table 2–18 “
vector locations” on page 23. The MEMMAP register determines the source of data that
will fill this table.
Table 20.Memory mapping control registers
NameDescriptionAccess Reset
MEMMAP Memory mapping control. Selects whether the
ARM interrupt vectors are read from the Boot
ROM, User Flash, or RAM.
Table 21.Memory Mapping control register (MEMMAP - address 0xE01F C040) bit
description
BitSymbol Value DescriptionReset
1:0 MAP00Boot Loader Mode. Interrupt vectors are re-mapped to Boot ROM. 00
01User Flash Mode. Interrupt vectors are not re-mapped and reside
10User RAM Mode. Interrupt vect ors are re-mapped to Static RAM.
11User External Memory Mode. Interrupt vectors are re-mapped to
Warning: Improper setting of this value may result in incorrect operation of
the device.
7:2 --Reserved, user software should not write ones to reserved bits.
Memory mapping
ARM exception
Address
value
R/W0x000xE01F C040
value
in Flash.
Remark: This mode is for parts with flash only. Value 01 is
reserved for flashless parts LPC2420/60/70.
external memory bank 0.
NA
The value read from a reserved bit is not defined.
6.2 Memory mapping control usage notes
Memory Mapping Control simply selects one out of three available sources of data (set s of
64 bytes each) necessary for handling ARM exceptions (interrupts).
For example, whenever a Software Interrupt request is generated, ARM core will always
fetch 32 bit data "residing" on 0x0000 0008 see Table 2–18 “
locations” on page 23. This means that when MEMMAP[1:0] = 10 (User RAM Mode),
read/fetch from 0x0000 0008 will provide data stored in 0x4000 0008. In case of
MEMMAP[1:0] = 00 (Boot Loader Mode), read/fetch from 0x0000 0008 will provide data
available also at 0x7FFF E008 (Boot ROM remapped from on-chip Bootloader).
UM10237
Chapter 2: LPC24XX Memory mapping
Fig 9.Map of lower memory is showing re-mapped and re-mappable areas for a
The LPC2400 generates the appropriate bus cycle abort exception if an access is
attempted for an address that is in a reserved or unassigned address region. The regions
are:
• Areas of the memory map that are not implemented for a specific ARM derivative. Fo r
the LPC2400, these are:
– Address space between On-Chip Non-Volatile Memory and the Special Register
space. Labelled "Reserved for On-Chip Memory" in Figure 2–6
– Address space between On-Chip Static RAM and the Boot ROM. Labelled
"Reserved Address Space" in Figure 2–6
– External Memory
– Reserved regions of the AHB and APB spaces. See Figure 2–7
• Unassigned AHB peripheral spaces. See Figure 2–8.
• Unassigned APB peripheral spaces. See Table 2–17.
For these areas, both attempted data acce ss and in struction fetch genera te an exception.
In addition, a Prefetch Abort exception is generated for an y instruction fetch that maps to
an AHB or APB peripheral address, or to the Special Register space located just below
the SRAM at addresses 0x3FFF8000 through 0x3FFFFFFF.
UM10237
Chapter 2: LPC24XX Memory mapping
.
.
.
Within the address space of an existing APB peripheral, a data abort exception is not
generated in response to an access to an undefined address. Address decoding within
each peripheral is limited to that needed to distinguish defined registers within the
peripheral itself. For example, an access to address 0xE000 D000 (an undefined address
within the UART0 space) may result in an access to the register defined at address
0xE000 C000. Details of such address aliasing within a peripheral space are not defined
in the LPC2400 documentation and are not a supported feature.
If software executes a write directly to the flash mem ory, the MAM generates a data abort
exception. Flash programming must be accomplished by using the specified flash
programming interface provided by the Boot Code.
Note that the ARM core stores the Prefetch Abort flag along with the associated
instruction (which will be meaningless) in the pipeline and processes the abort only if an
attempt is made to execute the instruction fetched from the illegal address. This prevents
accidental aborts that could be caused by prefetches that occur when code is executed
very near a memory boundary.
The System Control Block includes several system features and control registers for a
number of functions that are not related to specific peripheral devices. These include:
• Reset
• Brown-Out Detection
• External Interrupt Input s
• Miscellaneous System Controls and Status
• Code Security vs. Debugging
Each type of function has its own register(s) if any are required and unneeded bit s are
defined as reserved in order to allow future expansion. Unrelated functions never share
the same register addresses
2.Pin description
Table 3–22 shows pins that are associated with system control block functions.
Table 22.Pin summary
Pin namePin
EINT0InputExternal Interrupt Input 0 - An active low/high level or
EINT1InputExternal Interrupt Input 1 - See the EINT0 description above.
EINT2InputExternal Interrupt Input 2 - See the EINT0 description above.
EINT3InputExternal Interrupt Input 3 - See the EINT0 description above.
RESET
3.Register description
All registers, regardless of size, are on word address boundaries. Details of the registers
appear in the description of each function.
AHBCFG1Configures the AHB1 arbiterR/W0x0000 01450xE01F C188
AHBCFG2Configures the AHB2 arbiterR/W0x0000 01450xE01F C18C
[1] Reset Value reflects the data stored in used bits only. It does not include reserved bits content.
3.1 External interrupt inputs
The LPC2400 includes four External Interrupt Inputs as selectable pin functions. In
addition, external interrupts have the ability to wake up the CPU from Power down mode.
This is controlled by the register INTWAKE, which is described in the Clocking and Power
Control chapter under the Power Control heading
Register
UM10237
Chapter 3: LPC24XX System control
[1]
Address
R/Wsee text0xE01F C180
3.1.1 Register description
The external interrupt function has four registers associated with it. The EXTINT register
contains the interrupt flags. The EXTMODE and EXTPOLAR registers specify the level
and edge sensitivity parameters.
Table 24.External Interrupt registers
NameDescriptionAccess Reset
EXTINTThe External Interrupt Flag Register contains
interrupt flags for EINT0, EINT1, EINT2 and
EINT3. See Table 3–25
EXTMODEThe External Interrupt Mode Registe r control s
whether each pin is edge- or level-sensitive.
See Table 3–26
EXTPOLAR The External Interrupt Polarity Register controls
which level or edge on each pin will cause an
interrupt. See Table 3–27
[1] Reset Value reflects the data stored in used bits only. It does not include reserved bits content.
.
.
.
R/W0x000xE01F C140
R/W0x000xE01F C148
R/W0x000xE01F C14C
3.1.2 External Interrupt flag register (EXTINT - 0xE01F C140)
When a pin is selected for its external interrupt function, the level or edge on that pin
(selected by its bits in the EXTPOLAR a nd EXTMODE registers) will set its interrup t flag in
this register. This asserts the corresponding interrupt request to the VIC, which will cause
an interrupt if interrupts from the pin are enabled.
value
Address
[1]
Writing ones to bits EINT0 through EINT3 in EXTINT register clears the corresponding
bits. In level-sensitive mode the interrupt is cleared only when the pin is in its inactive
state.
Once a bit from EINT0 to EINT3 is set and an appropriate code st arts to execute (hand ling
wakeup and/or external interrupt), this bit in EXTINT register must be cleared. Otherwise
event that was just triggered by activity on the EINT pin will not be recognized in future.
Important: whenever a change of external interrupt operating mode (i.e. active
level/edge) is performed (including the initialization of an external interrupt),
corresponding bit in the EXTINT register must be cleared! For details see Section
For example, if a system wakes up from power-down using low level on external interrupt
0 pin, its post-wakeup code must reset EINT0 bit in order to allow future entry into the
power-down mode. If EINT0 bit is left set to 1, subsequent attempt(s) to invoke
power-down mode will fail. The same goes for external interrupt handling.
More details on power-down mode will be discussed in the following chapters.
Table 25.External Interrupt Flag register (EXTINT - address 0xE01F C140) bit description
Bit Symbol DescriptionReset
0EINT0In level-sensitive mode, this bit is set if the EINT0 function is selected for its
1EINT1In level-sensitive mode, this bit is set if the EINT1 function is selected for its
2EINT2In level-sensitive mode, this bit is set if the EINT2 function is selected for its
3EINT3In level-sensitive mode, this bit is set if the EINT3 function is selected for its
7:4 -Reserved, user software should not write ones to reserved bits. The value
UM10237
Chapter 3: LPC24XX System control
pin, and the pin is in its active state. In edge-sensitive mode, this bit is set if
the EINT0 function is selected for its pin, and the selected edge occurs on
the pin.
This bit is cleared by writing a one to it, except in level sensitive mode when
the pin is in its active state.
pin, and the pin is in its active state. In edge-sensitive mode, this bit is set if
the EINT1 function is selected for its pin, and the selected edge occurs on
the pin.
This bit is cleared by writing a one to it, except in level sensitive mode when
the pin is in its active state.
pin, and the pin is in its active state. In edge-sensitive mode, this bit is set if
the EINT2 function is selected for its pin, and the selected edge occurs on
the pin.
This bit is cleared by writing a one to it, except in level sensitive mode when
the pin is in its active state.
pin, and the pin is in its active state. In edge-sensitive mode, this bit is set if
the EINT3 function is selected for its pin, and the selected edge occurs on
the pin.
This bit is cleared by writing a one to it, except in level sensitive mode when
the pin is in its active state.
read from a reserved bit is not defined.
[1]
[1]
[1]
[1]
value
0
0
0
0
NA
[1] Example: If the EINTx is selected to be low level sensitive and low level is present on corresponding pin,
this bit can not be cleared; this bit can be cleared only when signal on the pin becomes high.