MPC563XM Reference Manual, Rev. 1
Freescale Semiconductor
415
Preliminary—Subject to Change Without Notice
14.3.1.2
Hardware Vector Mode
In hardware vector mode, the hardware is the interrupt vector signal from the INTC in conjunction with a
processor with the capability to use that vector. In hardware vector mode, this hardware causes the first
instruction to be executed in handling the interrupt request to the processor to be specific to that vector.
Therefore the interrupt exception handler is specific to a peripheral or software setable interrupt request
rather than being common to all of them. The INTC will use hardware vector mode for a given processor
when its associated the HVEN_PRC0 or HVEN_PRC1 bit in the INTC_BCR is asserted. The hardware
vector enable signal to the associated processor is driven as asserted. When the interrupt request to the
associated processor asserts, the interrupt vector signal is updated. The value of that interrupt vector is the
unique vector associated with the preempting peripheral or software setable interrupt request. The vector
value matches the value of the INTVEC_PRC0 field in the INTC_IACKR_PRC0 or the INTVEC_PRC1
field in the INTC_IACKR_PRC1, depending on which processor was assigned to handle a given interrupt
source.
The processor negates the interrupt request to the processor driven by the INTC by asserting the interrupt
acknowledge signal for one clock. Even if a higher priority interrupt request arrived while waiting for this
interrupt acknowledge, the interrupt request to the processor will negate for at least one clock.
The assertion of the interrupt acknowledge signal for a given processor pushes the associated PRI value in
the associated INTC_CPR_PRC
x
register onto the associated LIFO and updates the associated PRI in the
associated INTC_CPR_PRC
x
register with the new priority. This pushing of the PRI value onto the
associated LIFO and updating PRI in the associated INTC_CPR_PRC
x
does not occur when the associated
interrupt acknowledge signal asserts and the
Section 14.5.10, “INTC Software Set/Clear Interrupt
Registers (INTC_SSCIR0_3 - INTC_SSCIR4_7)
” is written at a time such that the PRI value in the
associated INTC_CPR_PRC
x
register would need to be pushed and the previously last pushed PRI value
would need to be popped simultaneously. In this case, PRI in the associated INTC_CPR_PRC
x
is updated
with the new priority, and the associated LIFO is neither pushed or popped.
14.3.2
Debug Mode
The INTC operation in debug mode is identical to its operation in normal mode.
14.3.3
Stop Mode
The INTC supports the stop mode mechanism. The INTC can have its clock input disabled at any time by
the clock driver on the SoC. While its clocks are disabled, the INTC registers are not accessible.
Some SoC applications require that any peripheral interrupt request source be able to awaken a portion or
all of the SoC from stop mode. Since the INTC requires clocking in order for a peripheral interrupt request
to generate an interrupt request to the processor, it does not support that requirement if it is not clocked.
14.3.4
Factory Test Mode
All INTC registers are accessible in factory test mode.