Visible to Intel only — GUID: hjw1698653010964
Ixiasoft
Visible to Intel only — GUID: hjw1698653010964
Ixiasoft
3.3.2. Reset Sequence
- 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_rst_ack_n pair, and i_rx_rst_n and o_rx_rst_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 Reset Sequence (8-bit Option).
- In variants with GMII8B adapter, reset, tx_digitalreset, and rx_digitalreset can be asserted at any point. Once the soft logic PLL is locked (mrphy_pll_lock is asserted) or rx_ready is asserted, you can deassert reset, tx_digitalreset, and rx_digitalreset to clear all the soft logic, TX soft logic, or RX soft logic respectively. When the soft logic PLL is locked (mrphy_pll_lock is asserted) or rx_ready goes low, then rx_digitalreset should be applied.
- In variants without the GMII8B adapter, the IP does not instantiate the soft logic PLL so mrphy_pll_lock signal is not available. tx_digitalreset should be deasserted after tx_ready is asserted, rx_digitalreset should be deasserted after rx_ready is asserted as shown in the MGBASE Reset Sequence (16-bit Option).
The following describe the reset sequence for MGBASE PCS only mode variant as shown in the figure above.
The tx_ready is the ready signal of the external GTS transceiver PHY. It indicates that the TX PMA PLL is locked, the clocks are stable, and the TX PMA is ready for transmission. When the TX PMA goes to reset, the 1G/2.5G/5G/10G Multirate Ethernet PHY tx_digital reset should be asserted after the PMA is ready.
The rx_ready is the ready signal of the external GTS transceiver PHY. It indicates that the RX PMA is locked to the data and the RX PMA is ready for data transfer. The 1G/2.5G/5G/10G Multirate Ethernet PHY RX side modules should be given reset using rx_digital_reset once the GTS transceiver PHY RX is ready.
Refer to GTS Transceiver PHY User Guide for more details.
- Drive the i_rst_n reset signal high while i_tx_rst_n and i_rx_rst_n reset signals are already deasserted.
- 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.
- 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.
- Assert the i_tx_rst_n reset signal.
- The o_tx_lanes_stable signal deasserts to indicate that the TX datapath is no longer operational.
- 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.
- Assert the i_rx_rst_n reset signal.
- The o_rx_pcs_ready signal deasserts to indicate that the RX datapath is no longer operational.
- 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.
- Assert the i_rst_n reset signal.
- The o_tx_lanes_stable and o_rx_pcs_ready signals deassert to indicate that TX and RX datapath are no longer operational.
- 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.
- Assert and deassert tx_digitalreset once the o_tx_lane_stable assert.
- Assert and deassert rx_digitalreset once the rx_pcs_ready assert.
System Considerations
- During the reset, hold the 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 reconfig_reset signal is low.