1G/2.5G/5G/10G Multirate Ethernet PHY Intel® FPGA IP User Guide: Agilex™ 5 FPGAs and SoCs

Download PDF
ID 813667
Date 7/08/2024
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents
Document Table of Contents x
1. About the 1G/2.5G/5G/10G Multirate Ethernet PHY Intel® FPGA IP for Agilex™ 5 Devices 2. Getting Started 3. Functional Description 4. Parameter Settings for 1G/2.5G/5G/10G Multirate Ethernet PHY Intel® FPGA IP 5. Interface Signals 6. Configuration Registers 7. 1G/2.5G/5G/10G Multirate Ethernet PHY Intel® FPGA IP User Guide: Agilex™ 5 FPGAs and SoCs Archives 8. Document Revision History for the 1G/2.5G/5G/10G Multirate Ethernet PHY Intel® FPGA IP User Guide: Agilex™ 5 FPGAs and SoCs
1. About the 1G/2.5G/5G/10G Multirate Ethernet PHY Intel® FPGA IP for Agilex™ 5 Devices x
1.1. Release Information 1.2. Features 1.3. Device Family Support 1.4. Device Speed Grade Support 1.5. Resource Utilization
2. Getting Started x
2.1. Introduction to Intel® FPGA IP 2.2. Installing and Licensing Intel® FPGA IPs 2.3. Specifying the IP Core Parameters and Options 2.4. Generated File Structure 2.5. Simulating Intel® FPGA IPs 2.6. Integrating Your IP Core in Your Design
2.2. Installing and Licensing Intel® FPGA IPs x
2.2.1. Intel® FPGA IP Evaluation Mode
2.6. Integrating Your IP Core in Your Design x
2.6.1. Adding the Agilex™ 5 Reference and System PLL IP
3. Functional Description x
3.1. Architecture 3.2. Clocking and Reset Sequence 3.3. Timing Constraints 3.4. Operation Speed Switching 3.5. USXGMII 3.6. Fmax Requirement
3.2. Clocking and Reset Sequence x
3.2.1. Clocking 3.2.2. Reset Sequence System Considerations
4. Parameter Settings for 1G/2.5G/5G/10G Multirate Ethernet PHY Intel® FPGA IP x
4.1. Core Configuration 4.2. Analog Parameters
5. Interface Signals x
5.1. Clock Signals 5.2. Reset Signals 5.3. Serial Interface Signals 5.4. Avalon Memory-Mapped Interface Signals 5.5. XGMII Signals 5.6. GMII Signals 5.7. PHY Status Signals 5.8. Transceiver Mode and Operating Speed Signals 5.9. Transceiver Status and Reconfiguration Signals 5.10. GTS Reset Sequencer Signals 5.11. Dynamic Reconfiguration SRC Signals
6. Configuration Registers x
6.1. Register Map 6.2. PHY Registers
1. About the 1G/2.5G/5G/10G Multirate Ethernet PHY Intel® FPGA IP for Agilex™ 5 Devices
2. Getting Started
3. Functional Description
4. Parameter Settings for 1G/2.5G/5G/10G Multirate Ethernet PHY Intel® FPGA IP
5. Interface Signals
6. Configuration Registers
7. 1G/2.5G/5G/10G Multirate Ethernet PHY Intel® FPGA IP User Guide: Agilex™ 5 FPGAs and SoCs Archives
8. Document Revision History for the 1G/2.5G/5G/10G Multirate Ethernet PHY Intel® FPGA IP User Guide: Agilex™ 5 FPGAs and SoCs

3.2.2. Reset Sequence

Figure 10. MGBASE-T Reset Block Diagram
Figure 11. MGBASE-T Reset Sequence (8-bit Option)
The following describes the reset sequence for MGBASE-T (8-bit) as shown in the figure above:
  • i_rst_n and o_rst_ack_n pair follows a handshake flow as shown in the figure above. i_tx_rst_n and o_tx_ack_n pair, and i_rx_rst_n and o_rx_ack_n pair follow the same flow for TX and RX paths respectively.
  • tx_ready is asserted by the IP several cycles after the i_rst_n is de-asserted. The assertion of tx_ready causes PLL to come out of reset and locked to reference. Locking is signalled by mrphy_pll_lock as shown in the MGBASE-T Reset Sequence (8-bit Option).
  • reset, tx_digitalreset and rx_digitalreset can be asserted at any point. After the mrphy_pll_lock is asserted, you can deassert reset, tx_digitalreset and rx_digitalreset to reset all soft logic.
Figure 12. MGBASE-T Reset Sequence (16-bit Option)
The following describes the reset sequence for MGBASE-T (16-bit) as shown in the figure above:
  • i_rst_n and o_rst_ack_n pair follows a handshake flow as shown in the figure above. i_tx_rst_n and o_tx_ack_n pair, and i_rx_rst_n and o_rx_ack_n pair follow the same flow for TX and RX paths respectively.
  • reset, tx_digitalreset and rx_digitalreset can be asserted at any point. Once tx_ready and rx_ready is asserted, you can deassert reset, tx_digitalreset and rx_digitalreset to reset all soft logic.
  • When the soft logic PLL is locked (mrphy_pll_lock is asserted) or when the rx_ready goes low, rx_digitalreset should be applied.
Figure 13. NBASE-T Reset Block Diagram
Figure 14. NBASE-T Reset Sequence
The following steps describe the reset sequence for NBASE-T as shown in the figure above:
  1. Drive the i_rst_n reset signal high while i_tx_rst_n and i_rx_rst_n reset signals are already deasserted.
  2. The o_rst_ack_n reset signal deasserts. This indicates that the IP core is no longer in the full reset.
    Note: This step doesn't indicate that the IP core is in fully functional state.
    Note: The o_tx_rst_ack_n and o_rx_rst_ack_n reset signals also deassert. The exact sequence and timing is not guaranteed.
  3. The IP core is fully out of reset. Assert o_tx_lanes_stable and o_rx_pcs_ready to indicate that the TX and RX datapaths are ready for use.
  4. Assert the i_tx_rst_n reset signal.
  5. The o_tx_lanes_stable signal deasserts to indicate that the TX datapath is no longer operational.
  6. The o_tx_rst_ack_n signal asserts indicating that the TX datapath is fully in reset. Then, deassert the i_tx_rst_n signal to bring the TX datapath out of the reset.
  7. Assert the i_rx_rst_n reset signal.
  8. The o_rx_pcs_ready signal deasserts to indicate that the RX datapath is no longer operational.
  9. The o_rx_rst_ack_n signal asserts indicating that the RX datapath is fully in reset. Then, deassert the i_rx_rst_n signal to bring the RX datapath out of the reset.
  10. Assert the i_rst_n reset signal.
  11. The o_tx_lanes_stable and o_rx_pcs_ready signals deassert to indicate that TX and RX datapath are no longer operational.
  12. The o_rst_ack_n signals assert to indicate the IP core is fully in reset. To bring the IP core out of the reset, deassert the i_rst_n reset signal.
  13. Assert tx_digital_reset once the tx_lane_stable assert.
  14. Assert rx_digital_reset once the rx_pcs_ready assert.

System Considerations

  • During the reset, hold the i_reconfig_reset signal asserted for several valid reconfiguration clock cycles to ensure the Avalon® memory-mapped interface and soft CSRs are fully reset.
  • Access to any Avalon® memory-mapped interface is available while the i_reconfig_reset signal is low.
Level Two Title