MOTOROLA
MC68349 USER'S MANUAL
3- 41
3.4.4.2 AUTOVECTOR INTERRUPT ACKNOWLEDGE CYCLE. When the interrupting
device cannot supply a vector number, it requests an automatically generated vector
(autovector). Instead of placing a vector number on the data bus and asserting DSACK≈,
the device asserts AVEC to terminate the cycle. If the DSACK≈ signals are asserted during
an interrupt acknowledge cycle terminated by AVEC, the DSACK≈ signals and data will be
ignored if AVEC is asserted before or at the same time as the DSACK≈ signals. The vector
number supplied in an autovector operation is derived from the interrupt level of the
current interrupt. When AVEC is asserted instead of DSACK≈ during an interrupt
acknowledge cycle, the MC68349 ignores the state of the data bus and internally
generates the vector number (the sum of the interrupt level plus 24 ($18)).
AVEC is multiplexed with CS0
. The FIRQ bit in the SIM49 module configuration register
controls whether the AVEC/CS0 pin is used as an autovector input or as CS0 (refer to
Section 4 System Integration Module for additional information). AVEC is only sampled
during an interrupt acknowledge cycle. During all other cycles, AVEC is ignored.
Additionally, AVEC can be internally generated for external devices by programming the
autovector register. Seven distinct autovectors can be used, corresponding to the seven
levels of interrupt available with signals IRQ7
–IRQ1 . Figure 3-28 shows the timing for an
autovector operation.
3.4.4.3 SPURIOUS INTERRUPT CYCLE. Requested interrupts, whether internal or
external, are arbitrated internally. When no internal module (including the SIM49, which
responds for external requests) responds during an interrupt acknowledge cycle by
arbitrating for the interrupt acknowledge cycle internally, the spurious interrupt monitor
generates an internal bus error signal to terminate the vector acquisition. The MC68349
automatically generates the spurious interrupt vector number (24) instead of the interrupt
vector number in this case. When an external device does not respond to an interrupt
acknowledge cycle with AVEC or DSACK≈ , a bus monitor must assert BERR , which
results in the CPU32+ taking the spurious interrupt vector. If HALT is also asserted, the
MC68349 retries the interrupt acknowledge cycle instead of using the spurious interrupt
vector.