Data Sheet

Interconnects—Ethernet Controller I210
51
3.1.7.3 Error Forwarding (TLP Poisoning)
If a TLP is received with an error-forwarding trailer, the transaction can be re-sent a number of times as
programmed in the GCR register. If transaction still fails the packet is dropped and is not delivered to
its destination. The I210 then reacts as listed in Table 3-12.
The I210 does not initiate any additional master requests for that PCI function until it detects an
internal software reset for the LAN port. Software is able to access device registers after such a fault.
System logic is expected to trigger a system-level interrupt to inform the operating system of the
problem. Operating systems can then stop the process associated with the transaction, re-allocate
memory instead of the faulty area, etc.
3.1.7.4 ECRC
The I210 supports End to End CRC (ECRC) as defined in the PCIe specification. The following
functionality is provided:
• Inserting an ECRC in all transmitted TLPs:
— The I210 indicates support for inserting ECRC in the ECRC Generation Capable bit of the PCIe
configuration registers. This bit is loaded from the ECRC Generation Flash bit.
— Inserting an ECRC is enabled by the ECRC Generation Enable bit of the PCIe configuration
registers. For MCTP packets, it is also controlled by the ECRC Generation for MCTP in PCIe
Control 2 Flash word.
• ECRC is checked on all incoming TLPs. A packet received with an ECRC error is dropped. Note that
for completions, a completion timeout occurs later (if enabled), which would result in re-issuing the
request.
— The I210 indicates support for ECRC checking in the ECRC Check Capable bit of the PCIe
configuration registers. This bit is loaded from the ECRC Check Flash bit.
— ECRC checking is enabled by the ECRC Check Enable bit of the PCIe configuration registers.
• ECRC errors are reported.
Malformed TLP (MP)
• Data payload exceed
Max_Payload_Size
• Received TLP data size does not
match length field
• TD field value does not
correspond with the observed
size
• Power management messages
that doesn’t use TC0.
• Usage of unsupported VC.
Uncorrectable.
ERR_FATAL
Log header
Drop the packet and free FC credits.
Completion with
unsuccessful
completion status
No action (already done
by originator of
completion).
Free FC credits.
Byte count integrity in
completion process.
When byte count isn’t compatible
with the length field and the actual
expected completion length. For
example, length field is 10 (in
Dword), actual length is 40, but the
byte count field that indicates how
many bytes are still expected is
smaller than 40, which is not
reasonable.
No action
The I210 doesn't check for this error and
accepts these packets.
This might cause a completion timeout
condition.
Table 3-12. Response and Reporting of PCIe Error Events (Continued)
Error Name Error Events Default Severity Action