Altera Arria V Hard IP for PCI Express - Manual (Page 213)

Chapter 14: Error Handling 14–3
Transaction Layer Errors
December 2013 Altera Corporation Arria V Hard IP for PCI Express
User Guide
Transaction Layer Errors
Table 14–4 describes errors detected by the Transaction Layer.
Table 14–4. Errors Detected by the Transaction Layer (Part 1 of 3)
Error Type Description
Poisoned TLP received
Uncorrectable
(non-fatal)
This error occurs if a received Transaction Layer packet has the EP
poison bit set.
The received TLP is passed to the Application Layer and the Application
Layer logic must take appropriate action in response to the poisoned
TLP. Refer to “2.7.2.2 Rules for Use of Data Poisoning” in the
PCI
Express Base Specification 2.1 for more information about poisoned
TLPs.
ECRC check failed (1)
Uncorrectable
(non-fatal)
This error is caused by an ECRC check failing despite the fact that the
TLP is not malformed and the LCRC check is valid.
The Hard IP block handles this TLP automatically. If the TLP is a
non-posted request, the Hard IP block generates a completion with
completer abort status. In all cases the TLP is deleted in the Hard IP
block and not presented to the Application Layer.
Unsupported Request for
Endpoints Uncorrectable
(non-fatal)
This error occurs whenever a component receives any of the following
Unsupported Requests:
■ Type 0 Configuration Requests for a non-existing function.
■ Completion transaction for which the Requester ID does not match
the bus/device.
■ Unsupported message.
■ A Type 1 Configuration Request TLP for the TLP from the PCIe link.
■ A locked memory read (MEMRDLK) on Native Endpoint.
■ A locked completion transaction.
■ A 64-bit memory transaction in which the 32 MSBs of an address are
set to 0.
■ A memory or I/O transaction for which there is no matching BAR.
■ A memory transaction when the Memory Space Enable bit (bit [1] of
the PCI Command register at Configuration Space offset 0x4) is set to
0.
■ A poisoned configuration write request ( CfgWr0 )
In all cases the TLP is deleted in the Hard IP block and not presented to
the Application Layer. If the TLP is a non-posted request, the Hard IP
block generates a completion with Unsupported Request status.
Unsupported Requests for
Root Port
Uncorrectable fatal
This error occurs whenever a component receives an Unsupported
Request including:
■ Unsupported message
■ A Type 0 Configuration Request TLP
■ A 64-bit memory transaction which the 32 MSBs of an address are
set to 0.
■ A memory transaction that does not match a Windows address