1 machine check interrupt, 2 int interrupt, 2 interrupt source priorities – Freescale Semiconductor MPC8260 User Manual

Page 181: Machine check interrupt -9, Int interrupt -9, Interrupt source priorities -9

Advertising
background image

System Interface Unit (SIU)

MPC8260 PowerQUICC II Family Reference Manual, Rev. 2

Freescale Semiconductor

4-9

If the software watchdog timer is programmed to generate an interrupt, it always generates a machine
check interrupt to the core. The external IRQ0 can generate MCP as well. Note that the core takes the
machine check interrupt when MCP is asserted; it takes an external interrupt for any other interrupt
asserted by the interrupt controller.

The interrupt controller allows masking of each interrupt source. Multiple events within a CPM sub-block
event are also maskable.

All interrupt sources are prioritized and bits are set in the interrupt pending register (SIPNR). On the
PowerQUICC II, the prioritization of the interrupt sources is flexible in the following two aspects:

The relative priority of the FCCs, SCCs, and MCCs can be modified

One interrupt source can be assigned the highest priority

When an unmasked interrupt source is pending in the SIPNR, the interrupt controller sends an interrupt
request to the core. When an exception is taken, the interrupt mask bit in the machine state register
(MSR[EE]) is cleared to disable further interrupt requests until software can handle them.

The SIU interrupt vector register (SIVEC) is updated with a 6-bit vector corresponding to the sub-block
with the highest current priority.

4.2.1.1

Machine Check Interrupt

There are several sources for a machine check interrupt (MCP):

Software watchdog timer (when programmed to generate an interrupt—See

Section 4.1.5,

“Software Watchdog Timer.

)

IRQ0 signal (when the internal core is enabled)

Memory controller for parity/ECC errors (see Section 10.2.6, “Machine Check Interrupt (MCP)
Generation”)

PCI bridge (MPC8265 and MPC8266 only)

Bus monitor time out (on an address only transaction—see Section 4.1.1, “Bus Monitor”)

When the internal core is enabled, these sources cause the interrupt controller to send a MCP to the core.
When the core is disabled the MCP assertion is reflected on IRQ0/NMI_OUT so that an external core can
serve it.

4.2.1.2

INT Interrupt

Besides the MCP sources listed above, all other interrupts are taken by the core through the INT

interrupt.

If the internal core is disabled, INT is reflected on IRQ7/INT_OUT so that an external core can serve it.

The interrupt controller allows masking of each interrupt source. Multiple events within a CPM sub-block
event are also maskable.

4.2.2

Interrupt Source Priorities

The interrupt controller has 37 interrupt sources that assert one interrupt request to the core.

Table 4-2

shows prioritization of all interrupt sources. As described in following sections, flexibility exists in the

Advertising