Visible to Intel only — GUID: efm1605490983075
Ixiasoft
1. About the Low Latency 50G Ethernet IP Core
2. Getting Started
3. Low Latency 50G Ethernet Intel® FPGA IP Parameters
4. Functional Description
5. Interfaces and Signal Descriptions
6. IP Core Register Descriptions
7. Document Revision History for the Low Latency 50G Ethernet Intel® FPGA IP User Guide: Stratix® 10 Devices
6.6.1. AN/LT Sequencer Config
6.6.2. AN/LT Sequencer Status
6.6.3. Auto Negotiation Config Register 1
6.6.4. Auto Negotiation Config Register 2
6.6.5. Auto Negotiation Status Register
6.6.6. Auto Negotiation Config Register 3
6.6.7. Auto Negotiation Config Register 4
6.6.8. Auto Negotiation Config Register 5
6.6.9. Auto Negotiation Config Register 6
6.6.10. Auto Negotiation Status Register 1
6.6.11. Auto Negotiation Status Register 2
6.6.12. Auto Negotiation Status Register 3
6.6.13. Auto Negotiation Status Register 4
6.6.14. Auto Negotiation Status Register 5
6.6.15. Link Training Config Register 1
6.6.16. Link Training Config Register 2
6.6.17. Link Training Status Register 1
6.6.18. Link Training Config Register for Lane 0
6.6.19. Link Training Frame Contents for Lane 0
6.6.20. Local Transceiver TX EQ 1 Settings for Lane 0
6.6.21. Local Transceiver TX EQ 2 Settings for Lane 0
6.6.22. Local Link Training Parameters
6.6.23. Link Training Config Register for Lane 1
6.6.24. Link Training Frame Contents for Lane 1
6.6.25. Local Transceiver TX EQ 1 Settings for Lane 1
6.6.26. Local Transceiver TX EQ 2 Settings for Lane 1
6.6.27. Link Training Config Register for Lane 2
6.6.28. Link Training Frame Contents for Lane 2
6.6.29. Local Transceiver TX EQ 1 Settings for Lane 2
6.6.30. Local Transceiver TX EQ 2 Settings for Lane 2
6.6.31. Link Training Config Register for Lane 3
6.6.32. Link Training Frame Contents for Lane 3
6.6.33. Local Transceiver TX EQ 1 Settings for Lane 3
6.6.34. Local Transceiver TX EQ 2 Settings for Lane 3
Visible to Intel only — GUID: efm1605490983075
Ixiasoft
4.3.5. RX CRC Checking and Dynamic Forwarding
The RX MAC checks the incoming CRC32 for errors. It asserts l2_rx_error[1] in the same cycle as l2_rx_endofpacket when it detects an error. CRC checking takes several cycles. The packet frame is delayed to align the CRC output with the end of the frame.
By default, the RX MAC strips off the CRC bytes before forwarding the packet to the MAC client. You can configure the core to retain the RX CRC and forward it to the client by updating the MAC_CRC_CONFIG register.