
7-12
MPC105 PCIB/MC User's Manual
MOTOROLA
Target-initiated termination occurs for two reasons:
Disconnect
Disconnect refers to termination requested because the target is unable
to respond within eight PCI clocks (not including the first data phase).
Disconnect implies that some data was transferred. The master may
restart the transaction at a later time starting with the address of the
next untransferred data. (That is, data transfer may resume where it
left off.)
Retry
Retry refers to termination requested because the target is currently in
a state where it is unable to process the transaction. Retry implies that
no data was transferred. The master may start the entire transaction
over again at a later time.
Note that as a target, the MPC105 executes a target disconnect after the first data phase
completes if AD1–AD0
≠
0b00 during the address phase of a system memory access. See
Section 7.3.3, “Addressing,” for more information.
When a transaction is terminated by STOP, the master must negate its REQ signal for a
minimum of two PCI clocks, one being when the bus goes to the idle state (FRAME and
IRDY negated). If the master intends to complete the transaction, it must reassert its REQ
immediately following the two clocks or potential starvation may occur. If the master does
not intend to complete the transaction, then it can assert REQ whenever it needs to use the
PCI bus again.
Target-abort is an abnormal case of target-initiated termination. Target-abort is used when
a fatal error has occurred, or when a target will never be able to respond. Target-abort is
indicated by asserting STOP and negating DEVSEL. This indicates that the target requires
termination of the transaction and does not want the transaction retried. If a transaction is
terminated by target-abort, the received target-abort bit (bit 12) of the master’s status
register and the signaled target-abort bit (bit 11) of the target’s status register is set. Note
that any data transferred in a target-aborted transaction may be corrupt.
7.4.4 Fast Back-to-Back Transactions
The PCI bus allows fast back-to-back transactions by the same master. During a fast back-
to-back transaction, the master starts the next transaction immediately without an idle state.
The last data phase completes when FRAME is negated, and IRDY and TRDY are asserted.
The current master starts another transaction on the clock immediately following the last
data transfer for the previous transaction.
Fast back-to-back transactions must avoid contention on the TRDY, DEVSEL, PERR, and
STOP signals. There are two types of fast back-to-back transactions—those that access the
same target, and those that access multiple targets (sequentially). The first type places the
burden of avoiding contention on the master; the second type places the burden of avoiding
contention on all potential targets.