
PRELIMINARY
63
A
82454KX/GX (PB)
3.4.2.1 PB Master Operation on PCI
Master Abort. When the PB performs a master abort, if the command was not a Special Cycle, the event is
logged by setting the Received Master Abort bit (bit 13) in the PCISTS Register. An interrupt can be generated
on this event. Special Cycle commands, which are broadcast to all PCI targets, are always terminated with
master abort. Therefore, master aborts during Special Cycle commands are not considered errors, and are
never logged or reported.
Target Disconnect and Target Retry. Target disconnects and target retries are not errors, and are not logged
or reported.
Target Abort. The PB logs a target abort by setting the Received Target Abort bit (bit 12) in the PCISTS
Register. If the SERR# enable bit (bit 8) of the PCICMD Register is set, and the SERR# on Receiving Target
Abort bit (bit 7) of the ERRCMD Register is set, this event is reported by asserting SERR#. When the PB
asserts SERR#, the Signalled System Error bit (bit 14) in the PCISTS Register is set. Optionally, the PB reports
a hard failure response to the host bus transaction (PB EXERRST Register). Note that this is not possible for
posted writes because the response phase has already occurred.
Data Parity Errors. As a PCI bus master, the PB checks the data parity provided during read data cycles and
monitors PERR# during write data cycles. The errors are logged by setting the appropriate status bits. If a
parity error is detected, the Detected Parity Error bit (bit 15) in the PCISTS Register is set. To distinguish
between read data parity errors and write data parity errors, the appropriate bit (bit 6 for writes, bit 5 for reads)
is set in the ERRSTS Register. Errors are reported via the SERR# and PERR# signals. The conditions causing
the assertion of SERR# due to data parity errors are summarized in Figure 5. The conditions causing the
assertion of PERR# and the Detected Parity Error Status bit are summarized in Figure 3 and Figure 4. Note
that for read data parity errors, the PB returns the corrupted data (with good parity/ECC) as the CPU read
response data. For write data parity errors, the corrupted data has already been delivered to the target; it is not
retried by the PB.
3.4.2.2 PB Target Operation on PCI
Target Disconnect. PB generated target disconnect is not considered an error and is not logged or reported.
Target Retry. Target retry is not an error and is not logged or reported. The PCI master is responsible for deter-
mining the maximum number of retries.
Target Abort. When the PB issues a target abort it sets the Signaled Target Abort bit (bit 11) in the PCISTS
Register. No further reporting or logging is done by the PB. The PCI initiator logs the target abort and may
report the error.
Data Parity Errors. As a target on the PCI bus, the PB checks the data parity provided during write data
cycles. If a parity error is detected during write data cycle, PERR# is asserted and bit 15 of the PCISTS
Register is set. No further reporting or logging is done by the PB.
.
Figure 3. Logic Diagram of the Assertion of PERR#
data parity error
parity error responses enabled
PERR#
04h[6]
70h[3]
PERR# on data parity error enabled