Buffer Errors - 2.4 English - PG169

Integrated Interlaken 150G LogiCORE IP Product Guide (PG169)

Document ID
PG169
Release Date
2024-06-05
Version
2.4 English

Data must be written to the TX LBUS such that there are no overflow or underflow conditions. LBUS bandwidth must always be greater than the Interlaken bandwidth to guarantee that bursts can be sent without interruption.

When writing data to the LBUS, the tx_rdyout signal must always be observed. This signal indicates whether the fill level of the TX buffer is within an acceptable range or not. If this signal is ever deasserted, you must stop writing to the TX LBUS until the signal is asserted. Because the TX LBUS has greater bandwidth than the TX Interlaken interface, it is not unusual to see this signal being frequently asserted and this is not a cause for concern.

Important: You must ensure that TX writes are stopped when tx_rdyout is deasserted.

If tx_rdyout is ignored, the tx_ovfout signal might be asserted, indicating a buffer overflow. This must not be allowed to occur.

Do not attempt to continue debugging after tx_ovfout is asserted until the cause of the overflow has been addressed.

If stat_tx_underflow_err is ever asserted, debugging must stop until the condition which caused the underflow is addressed. This can happen if the core clock is not fast enough to supply the transceiver with data and you should ensure that the minimum core clock frequency is being observed.