Triple-Speed Ethernet IP User Guide: Agilex™ 3 and Agilex™ 5 FPGAs and SoCs

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

10.1. Troubleshooting and Diagnosing Issues

Table 106.  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 scheme.
  • Confirm if tx_pll_locked, rx_is_lockedtoref, and rx_is_lockedtodata are asserted.
  • Confirm if rx_ready is asserted.
  • The status signal led_link should go high once the RX reset is successfully completed.
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.
  • Once the link is up, led_crs when asserted will indicate the confirmation of some activity on transmit and receive path.
  • Verify the MAC RX datapath clocks (rx_clk_125) are working at specified frequencies.
  • Check if rx_err_stat[] is asserted and the respective bit indicates the error type.
  • Check if there is congestion on the client side, ff_rx_rdy and ff_rx_a_full 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 specified frequencies:
    • tx_clk_125
    • rx_clk_125
  • Check the input clocks/enable signals expected from connected PHY for the datarate:
    • tx_clk/rx_clk
    • tx_clkena/rx_clkena
  • Check if the frame is received with error: gmii_rx_err/mii_rx_err/rx_err
  • Check is the frame received is valid using ff_rx_mod.
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, ff_rx_rdy is deasserted and rx_err is asserted
PTP: Measure valid is not being asserted. Recheck that the proper clock is given and resets are de-asserted.
Figure 73. Troubleshooting the Reset Sequence