Altera SerialLite II Protocol User Manual
Page 70
70
Altera Corporation
SerialLite II Protocol Reference Manual
Error Events & Handling
error results in the packet being marked as bad, before being forwarded
to the user, or in a request for retransmission from the remote port
(retry-on-error).
summarizes all errors and their handling.
Most errors originate from two sources: protocol violation at the Link
layer, or bit errors at the Physical layer. Physical layer bit errors most
likely involve 8b/10b coding violations and may affect one or multiple
lanes. Bit errors at the Physical layer result in Link layer protocol errors or
CRC errors. Severe physical lane errors or bursts of errors result in
multiple coding violations, loss of 8b/10b code alignment, or loss of lane
alignment.
Table 2–25. Error Summary
Error Type
Cause
Action
Catastrophic
●
Link state machine cannot
reverse polarity
●
Link state machine cannot
reorder lanes
●
Lanes in non-sequential order
SerialLite II enters
non-recoverable state;
requires manual reset
Link
●
Eight consecutive {|TS1|}
sequences received in all
lanes simultaneously
●
Loss of character alignment
●
Loss of lane alignment
●
Loss of characters from
underflow/overflow
●
Data error threshold exceeded
●
Retry-on-error timer expired
three times
Trigger link initialization
Data
●
Invalid 8b/10b codes groups
●
Running disparity errors
●
Unsupported valid code
groups
●
Link protocol violation
●
LMP with BIP error
●
CRC error
●
Unexpected channel number
●
Out of order packet
●
Out of order acknowledgment
(if retry-on-error enabled)
Two possibilities:
●
If retry-on-error is
enabled and the packet
is a priority packet,
request retransmission
●
Otherwise, mark the
packet as bad and
forward it to the user link
layer
Packets
Marked Bad
{EBP} marked packet
Received packet is marked
as bad and forwarded to
the user link layer