Altera Stratix V Avalon-MM Interface for PCIe Solutions User Manual Page 122

  • Download
  • Add to my manuals
  • Print
  • Page
    / 184
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 121
Error Type Description
Malformed TLP Uncorrectable
(fatal)
This error is caused by any of the following conditions:
The data payload of a received TLP exceeds the
maximum payload size.
The TD field is asserted but no TLP digest exists, or a
TLP digest exists but the TD bit of the PCI Express
request header packet is not asserted.
A TLP violates a byte enable rule. The Hard IP block
checks for this violation, which is considered
optional by the PCI Express specifications.
A TLP in which the type and length fields do not
correspond with the total length of the TLP.
A TLP in which the combination of format and type
is not specified by the PCI Express specification.
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:
1. Considered optional by the PCI Express Base Specification Revision .
Error Reporting and Data Poisoning
How the Endpoint handles a particular error depends on the configuration registers of the device.
Refer to the PCI Express Base Specification 3.0 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.
8-6
Error Reporting and Data Poisoning
UG-01097_avmm
2014.12.15
Altera Corporation
Error Handling
Send Feedback
Page view 121
1 2 ... 117 118 119 120 121 122 123 124 125 126 127 ... 183 184

Comments to this Manuals

No comments