Error reporting and data poisoning, Error reporting and data poisoning –5, Fcpe) – Altera Arria V Hard IP for PCI Express User Manual
Page 215
Chapter 14: Error Handling
14–5
Error Reporting and Data Poisoning
December 2013
Altera Corporation
Arria V Hard IP for PCI Express
User Guide
Error Reporting and Data Poisoning
How the Endpoint handles a particular error depends on the configuration registers
of the device.
f
for a description of the device signaling
and logging for an Endpoint.
The Hard IP block implements data poisoning, a mechanism for indicating that the
data associated with a transaction is corrupted. Poisoned TLPs have the
error/poisoned bit of the header set to 1 and observe the following rules:
■
Received poisoned TLPs are sent to the Application Layer and status bits are
automatically updated in the Configuration Space.
■
Received poisoned Configuration Write TLPs are not written in the Configuration
Space.
■
The Configuration Space never generates a poisoned TLP; the error/poisoned bit
of the header is always set to 0.
Poisoned TLPs can also set the parity error bits in the PCI Configuration Space Status
register.
lists the conditions that cause parity errors.
Poisoned packets received by the Hard IP block are passed to the Application Layer.
Poisoned transmit TLPs are similarly sent to the link.
Malformed TLP
(continued)
Uncorrectable
(fatal)
■
A request specifies an address/length combination that causes a
memory space access to exceed a 4 KByte boundary. The Hard IP
block checks for this violation, which is considered optional by the
PCI Express specification.
■
Messages, such as Assert_INTX, Power Management, Error
Signaling, Unlock, and Set Power Slot Limit, must be transmitted
across the default traffic class.
The Hard IP block deletes the malformed TLP; it is not presented to the
Application Layer.
Note to
:
(1) Considered optional by the
Table 14–4. Errors Detected by the Transaction Layer (Part 3 of 3)
Error
Type
Description
Table 14–5. Parity Error Conditions
Status Bit
Conditions
Detected parity error (status register bit 15)
Set when any received TLP is poisoned.
Master data parity error (status register bit 8)
This bit is set when the command register parity enable bit is set and one of
the following conditions is true:
■
The poisoned bit is set during the transmission of a Write Request TLP.
■
The poisoned bit is set on a received completion TLP.