9-10
MPC106 PCIB/MC User's Manual
MOTOROLA
If ErrEnR1[1] and PICR1[MCP_EN] are both set and the MPC106 terminates a transaction
with a master-abort, the MPC106 reports the error to the 60x processor by asserting MCP
and TEA.
9.3.3.4 Received Target-Abort Error
If a PCI transaction initiated by the MPC106 is terminated by target-abort, the received
target-abort flag (bit 12) of the PCI status register is set. If ErrEnR1[7] and
PICR1[MCP_EN] are both set and the MPC106 receives a target-abort, the MPC106
reports the error to the 60x processor by asserting MCP and TEA.
Note that any data transferred in a target-aborted transaction may be corrupt.
9.3.3.5 NMI (Nonmaskable Interrupt)
If PICR1[MCP_EN] is set and a PCI agent (typically the system interrupt controller) asserts
the NMI signal to the MPC106, the MPC106 reports the error to the 60x processor by
asserting MCP.
When the NMI signal is asserted, no error flags are set in the status registers of the MPC106.
The agent that drives NMI should provide the error flag for the system and the mechanism
to reset that error flag. The NMI signal should then remain asserted until the error flag is
cleared.
9.4 Interrupt Latencies
Latencies for taking various interrupts are variable based on the state of the MPC106 when
the conditions to produce an interrupt occur. The minimum latency is one cycle. In this
case, the interrupt is signaled in the cycle following the appearance of the interrupt-
producing conditions.
9.5 Example Signal Connections
This section provides two examples of connecting the interrupt signals between the 60x
processor, the MPC106, and an interrupt controller on the PCI bus. Typically the interrupt
controller is integrated into the PCI-to-ISA bridge. Figure 9-2 shows a PowerPC 603
microprocessor- or PowerPC 604 microprocessor-based system design. Figure 9-3 shows a
PowerPC 601 microprocessor-based system design.