IPR-PCIE/1 Altera, IPR-PCIE/1 Datasheet - Page 203

• Manufacturer Part Number: IPR-PCIE/1
• Description: IP CORE Renewal Of IP-PCIE/1
• Manufacturer: Altera
• Type: MegaCorer

Specifications of IPR-PCIE/1

• Software Application: IP CORE, Interface And Protocols, PCI
• Supported Families: Arria GX, Cyclone II, HardCopy II, Stratix II
• Core Architecture: FPGA
• Core Sub-architecture: Arria, Cyclone, Stratix
• Rohs Compliant: NA
• Function: PCI Express Compiler, x1 Link Width
• License: Renewal License
• Lead Free Status / RoHS Status: na
• Lead Free Status / RoHS Status: na

Chapter 12: Error Handling
Transaction Layer Errors
Transaction Layer Errors
Table 12–4. Errors Detected by the Transaction Layer (Part 1 of 3)
December 2010 Altera Corporation
Poisoned TLP received
ECRC check failed
Unsupported request for
endpoints
Unsupported requests for
root port
Error
(1)
Table 12–4
detected
Uncorrectable
(non-fatal)
Uncorrectable
(non-fatal)
Uncorrectable
(non-fatal)
Uncorrectable fatal
describes errors detected by the transaction layer. Poisoned TLPs are
Type
This error occurs if a received transaction layer packet has the EP poison
bit set.
The received TLP is passed to the application and the application layer
logic must take appropriate action in response to the poisoned TLP. In
PCI Express 1.1, this error is treated as an advisory error. Refer to
“2.7.2.2 Rules for Use of Data Poisoning” in the
Specification 2.0
This error is caused by an ECRC check failing despite the fact that the
transaction layer packet is not malformed and the LCRC check is valid.
The IP core handles this transaction layer packet automatically. If the
TLP is a non-posted request, the IP core generates a completion with
completer abort status. In all cases the TLP is deleted in the IP core and
not presented to the application layer.
This error occurs whenever a component receives any of the following
unsupported requests:
■
■
■
■
■
■
■
■
■
If the TLP is a non-posted request, the IP core generates a completion
with unsupported request status. In all cases the TLP is deleted in the IP
core and not presented to the application layer.
This error occurs whenever a component receives an unsupported
request including:
■
■
■
■
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 transaction layer packet 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 poisoned configuration write request (CfgWr0)
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
for more information about poisoned TLPs.
Description
PCI Express Compiler User Guide
PCI Express Base
12–3