Visible to Intel only — GUID: yox1623353502642
Ixiasoft
1. Quick Start Guide
2. Design Example: Single IP Core Instantiation
3. Design Example: Single IP Core Instantiation with Precision Time Protocol
4. Design Example: Single IP Core Instantiation with Auto-Negotiation and Link Training
5. Design Example: Multiple IP Core Instantiation
6. Design Example: Two Separate Instances of Auto-Negotiation and Link Training and Ethernet IP Design
7. F-Tile Ethernet Intel® FPGA Hard IP Design Example User Guide Archives
8. Document Revision History for the F-Tile Ethernet Intel FPGA Hard IP Design Example User Guide
Visible to Intel only — GUID: yox1623353502642
Ixiasoft
5.2. Functional Description
Figure 16. Simulation Design Example Block for Multiple F-Tile Ethernet Intel FPGA Hard IPs
The F-Tile Ethernet Intel FPGA Hard IP design example includes the following components:
- F-Tile Ethernet Intel FPGA Hard IP : Generated IP core.
- F-Tile Reference and System PLL Clocks : Instantiated reference clock and system PLL clock IP. The F-Tile Reference and System PLL Clocks Intel® FPGA IP parameter editor settings align with the System PLL frequency and PMA reference frequency parameter settings in the F-Tile Ethernet Intel FPGA Hard IP. If you generate the design example using Generate Example Design button in the IP parameter editor, the IP instantiates automatically. If you create your own design example, you must manually instantiate this IP and connect all I/O ports.
For information about supported system PLL modes, refer to F-Tile Ethernet Intel FPGA Hard IP User Guide. For information about this IP, refer to F-Tile Architecture and PMA and FEC Direct PHY IP User Guide.
- Packet Client: Consists of a packet generator, a packet checker and a loopback client. The Packet Client generates various ROM-based traffic patterns for MAC mode and can loopback the RX and TX client side.
- Avalon® memory-mapped interface Decoder: Decodes the Avalon® memory-mapped interface address to Hardware IP Top and PTP blocks if PTP is enabled. For base address for each of the Avalon® memory-mapped interface accessed instances, refer to Register Maps.