Interrupts
MPC5510 Microcontroller Family Reference Manual, Rev. 1
Freescale Semiconductor
8-3
Preliminary
8.2.2
External Input: Software Vector Mode
The IVPR acts as a base register for all types of exceptions. An IVOR, unique to each type of exception,
determines the offset from the IVPR. The IVPR and IVOR are added to calculate the interrupt exception
handler address. In software vector mode, IVOR4 is used for the external input, that is, the interrupt request
to the e200z1 or e200z0 from the INTC.
shows the software vector mode interrupt exception
handler address calculation.
Figure 8-2. Software Vector Mode Interrupt Exception Handler Address Calculation
8.2.3
External Input: Hardware Vector Mode
In hardware vector mode, no IVOR is used, including IVOR4, which has no effect. The interrupt exception
handler for each vector is offset from the IVPR. The vectors for each source are shown in
Data TLB Error
IVOR 13
0x0D0
—
SRR[0:1]
Data TLB miss in MMU
Instruction TLB Error
IVOR 14
0x0E0
—
SRR[0:1]
Instruction TLB miss in MMU
Debug
IVOR 15
0x0F0
DE, IDM
CSRR[0:1] ROM Debugger when HID0[DAPUEN]=0
DSRR[0:1] ROM Debugger when HID0[DAPUEN]=1
1
IVOR 9 (Offset 0x090) is not supported.
2
CE, ME, EE, DE are in MSR. DIE, FIE, WIE are in TCR. “src” is individual enable for each INTC source. Debug interrupt IVOR15
also requires EDM = 0 (EDM and IDM are in DBCR0).
3
Software vector mode interrupts use IVOR 4. Hardware vectored mode interrupts supply an interrupt vector based upon the
vector number given in
Table 8-2., “Interrupt Summary for External Input to e200z1 or e200z0
4
Only on e200z1; not implemented on e200z0.
Table 8-1. MPC5510 Core Interrupt Vector Memory Map (continued)
Core Interrupt Type
IVOR #
1
VPR
Offset
Enables
2
State
Saved In
Examples
+
=
IVPR
0
19 20
31
Vector base
0x000
IVOR4
0
31
0x0000_0040
Software Vector Mode Interrupt Exception Handler Address
0
19 20
31
Vector base
0x040