Low Latency Ethernet 10G MAC IP User Guide: Agilex™ 3 and Agilex™ 5 FPGAs and SoCs

ID 813663
Date 10/24/2025
Public
Document Table of Contents

7.1. Troubleshooting Checklist

Table 48.  Troubleshooting Checklist
Issue Troubleshooting Checklist
The ethernet link fails to come up/link is unstable.

Follow these troubleshooting steps to resolve the issue:

  • Review the IP configuration in the parameter editor to ensure it matches the requirements.
  • Confirm that all required reset inputs are properly driven, as described in the reset requirements.
  • Confirm that all specified clock inputs are correct, as described in the clocking section.
  • The status signal avalon_st rx_ready should go high once the RX reset is successfully completed.
  • Check the link fault status signal link_fault_status_xgmii_tx_data/link_fault_status_xgmii_rx_data
Missing ethernet packets at the receiver side.

Follow these troubleshooting steps to resolve the issue:

  • Review the IP configuration in the parameter editor to ensure it matches the requirements.
  • Verify the MAC RX datapath clocks are working at the specified frequencies: rx_312_5_clk/rx_156_25_clk.
  • Check if avalon_st_rxstatus_error[] is asserted and the respective bit indicates the error type.
  • Check if there is congestion on the client side (avalon_st_rx_ready is deasserted).
  • Check the MAC statistics register.
Mismatch in the data rate/throughput. Follow these troubleshooting steps to resolve the issue:
  • Review the IP configuration in the parameter editor to ensure it matches the requirements.
  • Verify the MAC TX/RX datapath clocks are working at the specified frequencies:
    • tx_312_5_clk
    • tx_156_25_clk
    • rx_312_5_clk
    • rx_156_25_clk
  • Check the input clocks/enable signals expected from connected PHY for the datarate:
    • gmii_tx_clk/gmii_rx_clk
    • gmii16b_tx_clk/gmii16b_rx_clk
    • tx_clkena/rx_clkena
The IP is not responding to the data flow Follow these troubleshooting steps to resolve the issue:
  • Review the IP configuration in the parameter editor to ensure it matches the requirements.
  • Confirm that all required reset inputs are properly driven, as described in the reset requirements.
  • Confirm that all specified clock inputs are correct, as described in the clocking scheme.
  • Check if there is congestion in the client side, avalon_st_rx_ready is deasserted and avalon_st_rxstatus_error[5] is asserted.