AT91M63200-25AI Atmel, AT91M63200-25AI Datasheet - Page 42

• Manufacturer Part Number: AT91M63200-25AI
• Description: IC ARM7 MCU 176 TQFP
• Manufacturer: Atmel
• Series: AT91SAMr

Specifications of AT91M63200-25AI

• Core Processor: ARM7
• Core Size: 16/32-Bit
• Speed: 25MHz
• Connectivity: EBI/EMI, SPI, UART/USART
• Peripherals: POR, WDT
• Number Of I /o: 58
• Program Memory Type: OTP
• Ram Size: 2K x 8
• Voltage - Supply (vcc/vdd): 1.8 V ~ 3.6 V
• Oscillator Type: External
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 176-TQFP, 176-VQFP
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant
• Eeprom Size: -
• Program Memory Size: -
• Data Converters: -

Spurious Interrupt
When the AIC asserts the NIRQ line, the ARM7TDMI
enters IRQ mode and the interrupt handler reads the IVR. It
may happen that the AIC de-asserts the NIRQ line after the
core has taken into account the NIRQ assertion and before
the read of the IVR.
This behavior is called a spurious interrupt.
The AIC is able to detect these spurious interrupts and
returns the spurious vector when the IVR is read. The spu-
rious vector can be programmed by the user when the vec-
tor table is initialized.
A spurious interrupt may occur in the following cases:
•
•
The same mechanism of spurious interrupt occurs if the
ARM7TDMI reads the IVR (application software or ICE)
when there is no interrupt pending. This mechanism is also
valid for the FIQ interrupts.
Once the AIC enters the spurious interrupt management, it
asserts neither the NIRQ nor the NFIQ lines to the
ARM7TDMI as long as the spurious interrupt is not
acknowledged. Therefore, it is mandatory for the spurious
interrupt service routine to acknowledge the “spurious”
behavior by writing to the AIC_EOICR (End of Interrupt)
before returning to the interrupted software. It also can per-
form other operation(s), e.g. trace possible undesirable
behavior.
Protect Mode
The protect mode permits reading of the Interrupt Vector
Register without performing the associated automatic oper-
ations. This is necessary when working with a debug sys-
tem.
When a debug monitor or an ICE reads the AIC user inter-
face, the IVR can be read. This has the following conse-
quences in normal mode:
•
•
In either case, an End-of-Interrupt command would be nec-
essary to acknowledge and to restore the context of the
AIC. This operation is generally not performed by the
debug system. Hence, the debug system would become
42
With any sources programmed to be level sensitive, if the
interrupt signal of the AIC input is de-asserted at the
same time as it is taken into account by the ARM7TDMI.
If an interrupt is asserted at the same time as the
software is disabling the corresponding source through
AIC_IDCR (this can happen due to the pipelining of the
ARM core).
If an enabled interrupt with a higher priority than the
current one is pending, it will be stacked.
If there is no enabled pending interrupt, the spurious
vector will be returned.
AT91M63200
strongly intrusive, and could cause the application to enter
an undesired state.
This is avoided by using Protect Mode.
The protect mode is enabled by setting the AIC bit in the
SF Protect Mode register (see "SF: Special Function Reg-
isters" on page 145).
When protect mode is enabled, the AIC performs interrupt
stacking only when a write access is performed on the
AIC_IVR. Therefore, the interrupt service routines must
write (arbitrary data) to the AIC_IVR just after reading it.
The new context of the AIC, including the value of the Inter-
rupt Status Register (AIC_ISR), is updated with the current
interrupt only when IVR is written.
An AIC_IVR read on its own (e.g. by a debugger) modifies
neither the AIC context nor the AIC_ISR.
Extra AIC_IVR reads performed in between the read and
the write can cause unpredictable results. Therefore, it is
strongly recommended not to set a breakpoint between
these 2 actions, nor to stop the software.
The debug system must not write to the AIC_IVR as this
would cause undesirable effects.
The following table shows the main steps of an interrupt
and the order in which they are performed according to the
mode:
Notes:
Action
Calculate active interrupt
(higher than current or spurious)
Determine and return the vector of
the active interrupt
Memorize interrupt
Push on internal stack the current
priority level
Acknowledge the interrupt
No effect
1. NIRQ de-assertion and automatic interrupt clearing if
2. Note that software which has been written and
(2)
the source is programmed as level sensitive.
debugged using protect mode will run correctly in
normal mode without modification. However, in nor-
mal mode the AIC_IVR write has no effect and can
be removed to optimize the code.
(1)
Normal
Mode
AIC_IVR
AIC_IVR
AIC_IVR
AIC_IVR
AIC_IVR
AIC_IVR
Read
Read
Read
Read
Read
Write
Protect
Mode
AIC_IVR
AIC_IVR
AIC_IVR
AIC_IVR
AIC_IVR
Read
Read
Read
Write
Write
–