Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[STDS-802-3-25G] Signaling bad FEC



Below is the solution 802.3bn EPoC (D1.3) will be using to signal 64B/66B blocks which have bad FEC. This might be useful for your signaling across the AUI.

 

101.3.3.1.3 Codeword error monitor

The FEC decoder in the CNU shall provide a user-configurable option (variable CRC40ErrCtrl) to indicate an uncorrectable FEC codeword (due to an excess of symbols containing errors) to higher layers. If CRC40ErrCtrl is enabled and the calculated value of CRC40 does not match the value of CRC40 retrieved from the received FEC codeword, the FEC decoder replaces bit <0> and <1> in the sync headers in all 64B/ 66B blocks with the binary value of “11”. If CRC40ErrCtrl is set to enable and the calculated value of CRC40 does not match the value of CRC40 retrieved from the received FEC codeword the FEC decoder indicates an error to the PCS by replacing bit <0> and <1> in the sync header with the binary value of "11" in the first 64B/66B block and every 8th 64B/66B block, e.g. 1st, 9th, 17th, 25th, etc. as well as the last 64B/ 66B block from the errored FEC codeword. The BER monitor state machine as defined in Clause 49 is then disabled. This option is intended for testing purposes.

 

Best Regards,

Duane

 

FutureWei Technologies Inc.

duane.remein@xxxxxxxxxx

Director, Access R&D

919 418 4741

Raleigh, NC