S2009
1.6 GBPS QUAD SERIAL BACKPLANE DEVICE
Table 7. Error and Status Reporting, Channel Lock and Independent Mode
ERR
EOF KFLAG
Description
Rank
0
0
0
0
1
Normal Character. Indicates that a valid data character has been detected.
7
K Character (not K28.5). Indicates that a K Character other than K28.5 has
been detected.
0
7
Channel Lock Detected1. Asserts for one parallel word on the ERRx, EOFx,
and KFLAGx signals that all four channels have identified the "Re-sync"
sequence within the byte deskew window. When in the "In Sync" state, the
S2009 will continue to report status, but will not re-deskew the output FIFOs.
0
1
0
2
K28.5+ or K28.5-. Indicates that a K28.5 character of arbitrary parity has been
detected.
0
1
1
0
1
0
5
4
Codeword Violation. Indicates that a word not corresponding to any valid Dx.x
or Kx.x mapping has been received.
Loss of Sync.
Independent Mode (CH_LOCK = 0)
In Independent Mode, this status will assert to indicate that loss of CRU bit
lock has occured on a specific channel. Individual reporting on ERRx, EOFx,
and KFLAGx will indicate which channel's CRU has lost bit lock. This reporting
will remain asserted until its CRU has locked to data. "Loss of Sync" will also
assert when the run length checker criterion is exceeded.
Channel Lock Mode (CH_LOCK = 1)
1
0
1
1
In Channel Lock Mode, this status will assert for at least one parallel word to
indicate that a condition has occured on a channel (or channels) which results
in loss of channel lock. Note, when channel locked, the user must monitor all
four channels' status reporting to know when the Channel Lock link has been
broken between the four channels. The non-errored channels will continue to
report normal status. "Loss of Sync" status will also be reported for a channel
until its CRU has locked to data. Another case in which this status will assert
is when the run length checker criterion is exceeded.
1
1
1
1
0
1
Parity Error. Indicates that a running disparity error has been observed.
6
3
Re-sync1 (K28.5 x 4 + Valid non-errored codeword (or data character) other
than a K28.5). If any channel(s) have to be delayed for word alignment,
multiple "Re-syncs" (111 status) can occur on these channel(s) having to delay
themselves for proper word alignment. This function (deskewing) is performed
within the S2009. If the S2009 does not have to delay any of the channels for
word alignment, "Re-sync" reporting will not be seen and channel lock status
will be reported simultaneously on all four channels. "Re-sync" reporting
indicates that four or more consecutive K28.5 characters followed by a valid
non-errored codeword (or data character) other than a K28.5 has been
received. Each channel reports this condition independently and all four
channels must identify the re-sync within the allowed byte deskew time before
channel lock can be achieved and be indicated with Channel Lock Detected
(see above).
LOL
Description
0
Indicates that the CRU is locked to data.
Indicates that the CRU has lost bit lock. This reporting will deassert when the CRU
has locked to data.
1
Note: LOL is an asynchronous, unfiltered signal.
1. This status reporting is not available in Independent Mode (CH_LOCK = 0).
14
February 9, 2001 / Revision C