*Notice: The information in this document is subject to change without notice
Tsi301
Notes
Tsi301 HyperTransport to PCI User Manual
3-20
TRDY# timeout refers to a violation of the target latency requirements, as given by the Error/TrdyTimer
CSR. Retry timeout refers to an excessive number of retries and/or disconnects, as given by the Error/Retry-
Timer CSR.
All PCI requests issued are forwarded through the HyperTransport PCI bridge from HyperTransport. If the
HyperTransport request was nonposted, error status may be returned to the HyperTransport requester in the
response. If it was posted, the error may only be signaled by the error interrupts. A single set of error-reporting
controls is used for all posted requests, regardless of the specific error taken.
All of the above errors return all 1s data for read requests, whether or not the response Error bit is set.
3.11.3 PCI Parity Errors
All PCI devices are required to drive even parity on P_PAR when they are driving the bottom half of the
P_AD bus, and on P_PAR64 when they are driving the top half.
The HyperTransport PCI bridge checks parity on the P_AD bus during command/address phases and data
phases when it receives data. The HyperTransport PCI bridge then logs bad parity in the DetParErr bit of the
Secondary Bus Status CSR. Other action is taken only if enabled by the ParErrRespEn bit in the Bridge
Control CSR. The action taken depends on the type of information being transferred at the time of the error
and in which direction the transfer was occurring.
Table 3.7 indicates the CSR bits used to log and enable reporting of each PCI parity error.
The HyperTransport PCI bridge may also sample P_PERR_N, asserted when it is driving write data out,
indicating that a parity error was detected by the target of the write. If the ParErrRespEn bit is set and the
request was a nonposted write, it receives an error response. If the request was a posted write and the Post-
FatalEn or NonPostFatalEn bits in the Error Control CSR are enabled, the error is signaled by one of the error
interrupts.
3.12 Test Features
Several features are included in the HyperTransport PCI bridge to facilitate testing of the chip. Supported
test modes are listed in Table 3.7 and are described in the following sections.
Error
Log Bit
Nonposted
Posted
Master Abort
SecStatus/
RcvdMstrAbort
If BrCtrl/ MstrAbortMode = 1,
return Error response
If Error/PostFatalEn = 1,
assert FATAL_ERR_N.
If Error/ PostNonFatalEn = 1,
assert NONFATAL_ERR_N.
Target Abort
SecStatus/ RcvdTgtAbort
Return Error response
TRDY# Timeout
Error/TrdyTimeout
Return Error response
Retry Timeout
Error/RetryTimeout
Return Error response
Table 3.6 PCI Master Errors CSR Bits
Error In
Fatal
Interrupt
NonFatal
Interrupt
PCI
Command/
Address
Error/
CmdPerrFatalEn
Error/
CmdPerrNonFatalEn
If decode has caused the
HyperTransport PCI bridge to
drive P_DEVSEL_N, Target Abort
Write data to
HyperTransport PCI
Not Supported
Assert P_PERR_N
Read data to
HyperTransport PCI
Set SecStatus/ MstrDParErr, return
HyperTransport error response,
and assert P_PERR_N
Table 3.7 PCI Parity Errors CSR Bits