Why does the Intel® PCIe* Hard IP run into recursive replay timer timeout, replay num rollover and link recovery when sending traffic? - Why does the Intel® PCIe* Hard IP run into recursive replay timer timeout, replay num rollover and link recovery when sending traffic? Description You might see timeout, rollover, and recovery because of Start of Packet(SOP) pointer buffer overflow. The SOP pointer buffer can overflow during replay because of internal error message or TLPs submitted from user side for transmission when the following trigger conditions are met: - ACK packets are lost or not received by Intel® PCIe* Hard IP under a high bit error rate link conditions - Link partner is unable to ACK packets at regular intervals as per the spec for unknown reasons If the above trigger conditions persists, then there are chances that internal SOP pointer buffer will reach the full condition. Every replay after this will cause overflow because of error message scheduling (Replay Timeout, Replay Num Rollover) or TLPs are submitted from user side for transmission. Resolution There is no workaround to this problem. This problem will not be fixed in a future release of the Intel® Quartus® Prime software. Custom Fields values: ['novalue'] Troubleshooting FB: 567081; True ['Arria® V GZ Hard IP for PCI Express IP', 'Avalon-MM Stratix® V Hard IP for PCI Express IP', 'IP Compiler for PCI Express', 'Arria® 10 Cyclone® 10 Hard IP for PCI Express', 'Stratix® V Hard IP for PCI Express IP'] ['FPGA Dev Tools Quartus® Prime Software Pro'] novalue 16.1.2 ['Arria® V GZ FPGA', 'Arria® 10 FPGAs and SoCs', 'Stratix® IV GT FPGA', 'Stratix® IV GX FPGA', 'Stratix® V GS FPGA', 'Stratix® V GT FPGA', 'Stratix® V GX FPGA'] ['novalue'] ['novalue'] ['novalue']