Altera Stratix V Avalon-ST - Manual (Page 120)

Transaction Layer Errors
Table 8-4: Errors Detected by the Transaction Layer
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 for more information about poisoned
TLPs.
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 and function number.
• 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
BAR match.
• 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.
UG-01097_sriov
2014.12.15
Transaction Layer Errors 8-3
Error Handling Altera Corporation
Send Feedback