9. Error Handling > PCIe as Originating Interface
71
PEB383 User Manual
July 25, 2011
Integrated Device Technology, Inc.
Confidential - NDA Required
9.2.3
PCI Uncorrectable Data Errors
This section describes the bridge requirements for error handling when forwarding downstream
a.non-poisoned PCIe transaction to PCI and the bridge detects an uncorrectable data error. The error is
detected on the PCI Interface.
9.2.3.1
Immediate Reads
When the PEB383 forwards a read request (I/O, Memory, or Configuration) downstream, it does the
following when it detects an uncorrectable data error on the destination interface while receiving an
immediate response from the completer:
1.
MDP_D bit is set in the
“PCI Secondary Status and I/O Limit and Base Register”
if the S_PERESP
bit is set in the
“PCI Bridge Control and Interrupt Register”
2.
D_PE in the
“PCI Control and Status Register”
is set
3.
PCI_PERRn is asserted on the PCI Interface if the S_PERESP bit is set in the
4.
UDERR bit is set in
“PCIe Secondary Uncorrectable Error Status Register”
5.
Header is logged in the
“PCIe Secondary Header Log 1 Register”
and the SUFEP field is updated
in the
“PCIe Secondary Error Capabilities and Control Register”
if UDERR Mask bit is clear in the
“PCIe Secondary Uncorrectable Error Mask Register”
and SUFEP is not valid
6.
Error Fatal or Non-Fatal message is generated on PCIe as per the severity level of UDERR bit in
“PCIe Secondary Uncorrectable Error Severity Register”
if the UDERR Mask bit is clear in
Secondary Uncorrectable Error Mask Register”
and either SERR_EN bit is set in the
or FTL_ERR_EN/NFTL_ERR_EN bit is set in the
7.
S_SERR bit is set in the
“PCI Control and Status Register”
if an error message (Fatal/Non-Fatal) is
generated and S_SERR bit is set in the
“PCI Control and Status Register”
8.
FTL_ERR_DTD/NFTL_ERR_DTD bit is set in the
“PCIe Device Control and Status Register”
For an immediate read transaction, if the PEB383 detects an uncorrectable data error on the destination
bus it continues to fetch data until the byte count is satisfied, or the target on the destination bus ends
the transaction. When the bridge creates the PCIe completion, it forwards it with successful completion
status and poisons the TLP.
9.2.3.2
Non-Posted Writes
When the PEB383 detects PCI_PERRn asserted on the PCI Interface while forwarding a non-poisoned
non-posted write transaction from PCIe, it does the following:
1.
If the target completes the transaction immediately with a data transfer, the PEB383 generates a
PCIe completion with Unsupported Request status to report the error to the requester
2.
PERR_AD bit is set in the
“PCIe Secondary Uncorrectable Error Status Register”
3.
MDP_D bit in the
“PCI Secondary Status and I/O Limit and Base Register”
is set if S_PERESP bit
is set in the