9. Error Handling > PCIe as Originating Interface
68
PEB383 User Manual
July 25, 2011
Integrated Device Technology, Inc.
Confidential - NDA Required
9.2
PCIe as Originating Interface
This section describes how the PEB383 handles error support for transactions that flow downstream
from PCIe to PCI (see
).
In the case of reception of a Write Request or Read Completion with a Poisoned TLP, the entire data
payload of the PCIe transaction is considered as corrupt and the parity is inverted on every data phase
forwarded (see
). In the case of reception of a request with ECRC error, the entire TLP is
considered as corrupt and is dropped by the bridge.
Figure 23: Transaction Error Forwarding with PCIe as Originating Interface
provides the translation a bridge has to perform when it forwards a non-posted PCIe request
(read or write) to PCI and the request is completed immediately on PCI, either normally or with an
error condition.
Table 13: Error Forwarding Requirements (Step A to Step B) for Received PCIe Errors
Received PCIe Error
(Step A)
Forwarded PCI Error Mode 1
(Parity) (Step B)
Write Request or Read Completion
with Poisoned TLP
Poisoned Data Parity
Request with ECRC (Optional
Support) Error
Do not forward
Table 14: Bridge Requirements for Transactions Requiring a Completion
(Immediate Response)
Immediate PCI Termination
PCIe Completion Status
Data transfer with uncorrectable data
error (reads)
Successful (Poisoned TLP)
Data transfer with uncorrectable data
error (non-posted writes)
Unsupported Request
Requ estor
or Delayed
Transacti on
Compl eter
PEB38x
Immediate
Completer
Step A
Ste p B
Step D
Step C
PC I
(Destin atio n Interface)
PCIe
(Ori gi nating Interface)