Visible to Intel only — GUID: qob1683057123780
Ixiasoft
1. GTS Transceiver Overview
2. GTS Transceiver Architecture
3. Implementing the GTS PMA/FEC Direct PHY Intel FPGA IP
4. Implementing the GTS System PLL Clocks Intel FPGA IP
5. Implementing the GTS Reset Sequencer Intel FPGA IP
6. GTS PMA/FEC Direct PHY Intel FPGA IP Example Design
7. Design Assistance Tools
8. Debugging GTS Transceiver Links with Transceiver Toolkit
9. Document Revision History for the GTS Transceiver PHY User Guide
3.1. IP Overview
3.2. Designing with the GTS PMA/FEC Direct PHY Intel FPGA IP
3.3. Configuring the GTS PMA/FEC Direct PHY Intel FPGA IP
3.4. Signal and Port Reference
3.5. Bit Mapping for PMA, FEC, and PCS Mode PHY TX and RX Datapath
3.6. Clocking
3.7. Custom Cadence Generation Ports and Logic
3.8. Asserting reset
3.9. Bonding Implementation
3.10. Configuration Register
3.11. Configuring the GTS PMA/FEC Direct PHY Intel FPGA IP for Hardware Testing
3.12. Configurable Quartus® Prime Software Settings
3.13. Hardware Configuration Using the Avalon® Memory-Mapped Interface
3.3.1. Preset IP Parameter Settings
3.3.2. Common Datapath Options
3.3.3. TX Datapath Options
3.3.4. RX Datapath Options
3.3.5. PMA Configuration Rules for Specific Protocol Mode Implementations
3.3.6. FEC Options
3.3.7. PCS Options
3.3.8. Avalon® Memory-Mapped Interface Options
3.3.9. Register Map IP-XACT Support
3.3.10. Analog Parameter Options
3.4.1. TX and RX Parallel and Serial Interface Signals
3.4.2. TX and RX Reference Clock and Clock Output Interface Signals
3.4.3. Reset Signals
3.4.4. FEC Signals
3.4.5. Custom Cadence Control and Status Signals
3.4.6. RX PMA Status Signals
3.4.7. TX and RX PMA and Core Interface FIFO Signals
3.4.8. Avalon Memory-Mapped Interface Signals
6.1. Instantiating the GTS PMA/FEC Direct PHY Intel FPGA IP
6.2. Generating the GTS PMA/FEC Direct PHY Intel FPGA IP Example Design
6.3. GTS PMA/FEC Direct PHY Intel FPGA IP Example Design Functional Description
6.4. Simulating the GTS PMA/FEC Direct PHY Intel FPGA IP Example Design Testbench
6.5. Compiling the GTS PMA/FEC Direct PHY Intel FPGA IP Example Design
6.6. Hardware Testing the GTS PMA/FEC Direct PHY Intel FPGA IP Example Design
Visible to Intel only — GUID: qob1683057123780
Ixiasoft
4.4. Guidelines for GTS System PLL Clocks Intel FPGA IP Usage
You must adhere to the following guidelines to correctly use the GTS System PLL Clock Intel FPGA IP:
- The GTS System PLL Clock Intel FPGA IP cannot be compiled or simulated as a standalone IP. When you use the GTS System PLL Clock Intel FPGA IP, it must always connect to the GTS PMA/FEC Direct PHY Intel FPGA IP or protocol IPs.
- You must connect the system PLL output ports of GTS System PLL Clocks Intel FPGA IP to input of GTS PMA/FEC Direct PHY Intel FPGA IP as shown in Port Connection Guidelines between GTS System PLL Clock Intel FPGA IP and GTS PMA/FEC Direct PHY Intel FPGA IP or protocol IPs.
- You must ensure the reference clock and system PLL frequencies specified in GTS System PLL Clocks Intel FPGA IP match reference clock and system PLL frequencies specified in GTS PMA/FEC Direct PHY Intel FPGA IP or protocol IPs.
- You must instantiate one GTS System PLL Clocks Intel FPGA IP for every system PLL you intend to use in the design.
- Each system PLL can be used by the channels in its own transceiver bank, or by channels in the transceiver banks immediately above or below its own transceiver bank. The location of the system PLL is automatically assigned by Quartus® Prime Pro Edition software.
- You must inform the IP when all reference clocks are ready after device configuration is complete.
- An input port i_refclk_ready is available, and you must assert this port once the reference clock is ready after device configuration. If you do not assert this port, the system PLL does not attempt to lock to the reference clock, and the o_pll_lock status output does not assert.
- You can connect this input port to a GPIO pin to control this externally. You can also control this input port internally by setting it from your RTL logic.
- If the reference clock signal is ready before device configuration, this input port can be tied high.
- You must bring up all the reference clocks in your design that feed the system PLLs before any of the GTS transceivers are used. You can do a logical AND of all the reference clock ready signals for multiple GTS System PLL Clocks Intel FPGA IPs together as shown in the following figure.
Figure 74. Logical And of Reference Clock Signals
- An exception is made in the case of PCIe* , where PCIe* must have its system PLLs reference clock ready by the time of device configuration for PCIe* link up compliance. In this case, the transceiver is configured for PCIe* operation prior to other system PLLs and transceivers being up and running.
- Once the reference clock for the system PLL is up; it must be stable; it must be present throughout the device operation and must not go down. If you are not able to adhere to this, you must reconfigure the device. After a temporary loss of the system PLL reference clock, you may observe that the first try of device reconfiguration fails. If that happens, you should try to reconfigure the device a second time.