The TX must observe the LBUS rules which are required for compliance to the Interlaken Protocol Definition, Revision 1.2, October 7, 2008 and the Integrated Interlaken IP core requirements.
If a burst rule violation occurs, the stat_tx_burst_err signal is
asserted. You must ensure that the rules governing the scheduling of bursts are
observed. In particular, the segmented LBUS protocol should be given careful
reading.
One common issue is having written data where more than one Burst Control Word is generated during one clock cycle. Carefully review the segmented LBUS rules. Ensure that an SOP or a channel change does not occur in the same cycle as an implied Burst Control Word resulting from BurstMax having been reached.
This can be avoided by implementing the enhanced scheduling algorithm, which uses the
tx_bctlin<N> signals to force Burst Control Words in such a way
as to avoid two in one clock cycle.
In summary, Burst Control Words can be implied or generated by the following cases:
- BurstMax reached (implied)
- EOP/SOP (implied)
- Channel Change (implied)
- bctlin assertion (forced)