
ERR004298
Chip Errata for the i.MX 6Dual/6Quad and i.MX 6DualPlus/6QuadPlus, Rev. 6.1, 06/2016
154
NXP Semiconductors
Description:
Figure 3-15 in Section 3.5.2.2. “Handling of Received DLLPs” of the PCI Express base
Specification 3.0, indicates when a bad DLLP error should be reported. It should occur when the
calculated CRC is not equal to the received value. The core correctly reports a bad DLLP error
under this scenario. However, it also sets it if the Physical Layer reports a packet error during
reception of the DLLP or if the DLLP ends with an ENDB symbol and not an END symbol. These
extra conditions should not result in the reporting of a bad DLLP error.
Projected Impact:
A bad DLLP error is reported when it should not be. However, in this scenario, the core has
received a bad DLLP. There are no adverse side effects.
Workarounds:
None required, there are no adverse side effects.
Proposed Solution:
No fix scheduled
Linux BSP Status:
Software workaround cannot be implemented to mask or workaround this SoC issue. This erratum
will result in impacted or reduced functionality as described above.
ERR004298
PCIe: 9000471173—Bad DLLP error status checking is too strict