
Interrupt Controller (INTC)
MPC5644A Microcontroller Reference Manual, Rev. 6
368
Freescale Semiconductor
15.5.1.1
Peripheral interrupt requests
An interrupt event in a peripheral’s hardware sets a flag bit, which resides in that peripheral. The interrupt
request from the peripheral is driven by that flag bit.
The time from when the peripheral starts to drive its peripheral interrupt request to the INTC to the time
that the INTC starts to drive the interrupt request to the processor is three clocks.
15.5.1.2
Software configurable interrupt requests
The software set/clear interrupt registers (INTC_SSCIR
x_x
) support the setting or clearing of
software-configurable interrupt requests. These registers contain eight independent sets of bits to set and
clear a corresponding flag bit by software. With the exception of being set by software, this flag bit behaves
the same as a flag bit set within a peripheral. This flag bit generates an interrupt request within the INTC
just like a peripheral interrupt request.
An interrupt request is triggered by software writing a 1 to the SET
n
bit in INTC software set/clear
interrupt registers (INTC_SSCIR0–INTC_SSCIR7). This write sets a CLR
n
flag bit that generates an
interrupt request. The interrupt request is cleared by writing a 1 to the CLR
n
bit. Specific behavior includes
the following:
•
Writing a 1 to SET
n
leaves SET
n
unchanged at 0 but sets the flag bit (CLR
n
bit).
•
Writing a 0 to SET
n
has no effect.
•
Writing a 1 to CLR
n
clears the flag (CLR
n
) bit.
•
Writing a 0 to CLR
n
has no effect.
•
If a 1 is written to a pair of SET
n
and CLR
n
bits at the same time, the flag (CLR
n
) is set, regardless
of whether CLR
n
was asserted before the write.
The time from the write to the SET
n
bit to the time that the INTC starts to drive the interrupt request to the
processor is four clocks.
15.5.1.3
Unique vector for each interrupt request source
Each peripheral and software configurable interrupt request is assigned a hardwired unique 9-bit vector.
Software configurable interrupts 0–7 are assigned vectors 0–7, respectively. The peripheral interrupt
requests are assigned vectors 8 to as high as needed to cover all of the peripheral interrupt requests.
15.5.2
Priority management
The asserted interrupt requests are compared to each other based on their PRI
n
values in INTC priority
select registers (INTC_PSR0–INTC_PSR485). The result of the comparison also is compared to PRI in
INTC current priority register (INTC_CPR). The results of those comparisons are used to manage the
priority of the ISR being executed by the processor. The LIFO also assists in managing the priority.
15.5.2.1
Current priority and preemption
The priority arbitrator, selector, encoder, and comparator submodules shown in
are used to
compare the priority of the asserted interrupt requests to the current priority. If the priority of any asserted
Summary of Contents for MPC5644A
Page 2: ...MPC5644A Microcontroller Reference Manual Rev 6 2 Freescale Semiconductor...
Page 24: ...MPC5644A Microcontroller Reference Manual Rev 6 24 Freescale Semiconductor...
Page 26: ...MPC5644A Microcontroller Reference Manual Rev 6 26 Freescale Semiconductor...
Page 52: ...Introduction MPC5644A Microcontroller Reference Manual Rev 6 52 Freescale Semiconductor...
Page 56: ...Memory Map MPC5644A Microcontroller Reference Manual Rev 6 56 Freescale Semiconductor...
Page 1228: ...Decimation Filter MPC5644A Microcontroller Reference Manual Rev 6 1228 Freescale Semiconductor...
Page 1440: ...FlexCAN Module MPC5644A Microcontroller Reference Manual Rev 6 1440 Freescale Semiconductor...