6146 - CertusPro-NX: Does the SLVS-EC Receiver IP handles PAD codes automatically?

Description:

Auto computation of FIFO Depth and FIFO Delay attributes does not consider for the pad codes inserted in the packet data. The current setting may cause FIFO Empty and FIFO Full states if pad codes are present in the packet data.

Adjust manually to avoid FIFO Empty or FIFO Full states during packet transfer.

Pad codes are not considered in the default FIFO setting computations. FIFO computation formulas can be found on page-11 of SLVS-EC Receiver IP User Guide (FPGA-IPUG-02125).

Please check if you have properly set the FIFO settings when they added pad codes.

If there are pad codes, add them to the Byte Count, and re-compute for new FIFO DELAY/DEPTH (i.e. byte count is 12288 and additional 1200 bytes of pad codes per line, new byte count = 12288 + 1200 = 13488).

Related Articles
6233 - SLVS-EC Receiver IP Core: How to Set Reference Clock Frequency of SLVS-EC Rx IP core?
The “reference clock” corresponds to the IP port refclk_*. This port represents the differential clock of the internal MPCS PLL. It can be sourced from any clock signal capable of generating the MPCS clock frequency specified in the “MPCS Clock ...
6447 - CertusPro-NX PCIe: Does both Quad 0 and Quad 1 support hard IP block of PCIe link layer?
CertusPro-NX only supports the hard IP block PCIe link layer on Quad 0. For more information, refer to second paragraph of section '11.1. PCI Express Mode' on FPGA-TN-02245.
7743 - How to implement Gigabit Ethernet in Certus-NX, CertusPro-NX, MachXO5-NX and CrossLink-NX FPGAs?
Lattice currently recommends the following for implementing Gigabit Ethernet interfaces: CertusPro-NX FPGAs: Use SERDES-based SGMII or RGMII Certus-NX, MachXO5-NX, and CrossLink-NX: Use RGMII These recommendations are based on updated LVDS-based ...
6927 - PCIe for Nexus FPGAs: Using the Lattice CertusPro-NX PCIe x4 IP Core and the AXI4-Stream interface, what is the latency of read and write access through the APB interface across the Link Layer registers, Configuration Space Registers, and the Soft
Here is the latency table of the read & write through the APB interface for CertusPro-NX:
6215 - Certus Pro-NX: Does Lattice CertusPro-NX supports PCIe via PIPE + Soft PCIELL?
Solution: No, the CertusPro-NX only supports PCIe via PIPE + Hard PCIELL.

6146 - CertusPro-NX: Does the SLVS-EC Receiver IP handles PAD codes automatically?

6146 - CertusPro-NX: Does the SLVS-EC Receiver IP handles PAD codes automatically?

Related Articles

6233 - SLVS-EC Receiver IP Core: How to Set Reference Clock Frequency of SLVS-EC Rx IP core?

6447 - CertusPro-NX PCIe: Does both Quad 0 and Quad 1 support hard IP block of PCIe link layer?

7743 - How to implement Gigabit Ethernet in Certus-NX, CertusPro-NX, MachXO5-NX and CrossLink-NX FPGAs?

6927 - PCIe for Nexus FPGAs: Using the Lattice CertusPro-NX PCIe x4 IP Core and the AXI4-Stream interface, what is the latency of read and write access through the APB interface across the Link Layer registers, Configuration Space Registers, and the Soft

6215 - Certus Pro-NX: Does Lattice CertusPro-NX supports PCIe via PIPE + Soft PCIELL?