GTS Ethernet Hard IP User Guide: Agilex™ 3 FPGAs and SoCs
ID
848477
Date
7/07/2025
Public
1. Overview
2. Install and License the GTS Ethernet Hard IP
3. Configure and Generate Ethernet Hard IP variant
4. Integrate GTS Ethernet Hard IP into Your Application
5. Simulate and Compile (MAC+PCS) Design Example
6. Simulate and Compile (MII PCS Only/PCS66 OTN/PCS66 FlexE) Design Example
7. Simulate and Compile SyncE Design Example
8. Simulate and Compile PTP1588 Design Example
9. Simulate and Compile (Dynamically Reconfigurable Ethernet Mode)
10. Simulate and Compile - Auto-Negotiation and Link Training
11. Troubleshoot and Diagnose Issues
12. Appendix A: Functional Description
13. Appendix B: Configuration Registers
14. Appendix C: Document Revision History for the GTS Ethernet Hard IP User Guide: Agilex 3 FPGAs and SoCs
4.1. Implement Required Clocking
4.2. Implement Required Resets
4.3. Connect the Status Interface
4.4. Connect the MAC Avalon Streaming Client Interface
4.5. Connect the MII PCS Only Client Interface
4.6. Connect the PCS66 Client Interface – FlexE and OTN
4.7. Connect the Precision Time Protocol Interface
4.8. Connect the Ethernet Hard IP Reconfiguration Interface
4.9. Connect the Auto-Negotiation and Link Training
4.10. Connect the Multirate Auto-Negotiation and Link Training
4.11. Connect the Dynamically Reconfigurable Ethernet Mode
4.4.1.1. Drive the Ethernet Packet to the TX MAC Avalon Streaming Client Interface with Disabled Preamble Passthrough
4.4.1.2. Drive the Ethernet Packet on the TX MAC Avalon Streaming Client Interface with Enabled Preamble Passthrough
4.4.1.3. Use i_tx_skip_crc to Control Source Address, PAD, and CRC Insertion
4.4.1.4. Assert the i_tx_error to Invalidate a Packet
4.4.2.1. Receive Ethernet Frame on the RX MAC Avalon Streaming Client Interface with Preamble Passthrough Disabled
4.4.2.2. Receive Ethernet Frame with Preamble Passthrough Enabled
4.4.2.3. Receive Ethernet Frame with Remove CRC bytes Disabled
4.4.2.4. Monitor Status and Errors on the RX MAC Avalon Streaming Client Interface
4.5.1. Connect the MII PCS Mode TX Interface
The GTS Ethernet Hard IP TX client interface in PCS variations is Media Independent Interface (MII).
Connect the TX MII interface (which is a sink) to an MII compliant source. Connect the interface according to the table below.
Signal Name | Width | Description |
---|---|---|
i_tx_mii_d[63:0] | 64 bits (10GE) | Drive MII encoded control bytes or Ethernet frame content on this input data bus.
|
i_tx_mii_c[7:0] | 8 bits (10GE) | For each control byte driven into i_tx_mii_d bus, drive the corresponding bit high. For example, i_tx_mii_c[0] corresponds to i_tx_mii_d[7:0].
|
i_tx_mii_valid | 1 bit | Drive this signal high to qualify the data or control bytes on the i_tx_mii_d bus. |
o_tx_mii_ready | 1 bit | When this signal is deasserted, stop driving valid data on the i_tx_mii_d bus since the IP core is not ready to receive. You must deassert i_tx_mii_valid within 6 clock cycles of this signal being deasserted. Refer Transmitting Data on the PCS Mode TX Interface for reference. |
i_tx_mii_am | 1 bit | Drive this signal to 0 if Firecode FEC or No FEC is enabled. |
The following waveform shows how to send packets directly to the PCS TX interface.
Figure 40. Transmitting Data on the PCS Mode TX Interface
- Drive i_tx_mii_valid according to the following rules:
- Assert the i_tx_mii_valid only when the o_tx_mii_ready is asserted, and deassert only when the o_tx_mii_ready is deasserted.
- Space the i_tx_mii_valid and o_tx_mii_ready signals by a fixed latency between one and six signals.
- Hold the values of i_tx_mii_d and i_tx_mii_c when i_tx_mii_valid is low.
- Bytes are transmitted from Least Significant Byte (LSB) to Most Significant Byte (MSB) order. The initial byte to be transferred from the interface is represented by the 8-bit value i_tx_mii_d[7:0].
- The first bit to be transmitted is the LSB of that byte, which is i_tx_mii_d[0].
Note: The PCS TX interface is not SOP aligned. Any valid ordering of packets in MII format is accepted.
Transmit a start of packet and preamble with an SFD byte according to the table below.
MII Data | MII Control | Ethernet Packet Byte | ||
---|---|---|---|---|
i_tx_mii_d[7:0] | 0xFB | i_tx_mii_c[0] | 1 | Start of Packet |
i_tx_mii_d[15:8] | 0x55 | i_tx_mii_c[1] | 0 | Preamble |
i_tx_mii_d[23:16] | 0x55 | i_tx_mii_c[2] | 0 | Preamble |
i_tx_mii_d[31:24] | 0x55 | i_tx_mii_c[3] | 0 | Preamble |
i_tx_mii_d[39:32] | 0x55 | i_tx_mii_c[4] | 0 | Preamble |
i_tx_mii_d[47:40] | 0x55 | i_tx_mii_c[5] | 0 | Preamble |
i_tx_mii_d[55:48] | 0x55 | i_tx_mii_c[6] | 0 | Preamble |
i_tx_mii_d[63:56] | 0xD5 | i_tx_mii_c[7] | 0 | SFD |