GTS Transceiver PHY User Guide

Download PDF
ID 817660
Date 1/24/2025
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. 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
1. GTS Transceiver Overview x
1.1. GTS Transceiver Design Flow
2. GTS Transceiver Architecture x
2.1. Building Blocks 2.2. Channel Placement Rules and Design Requirements 2.3. PMA Architecture 2.4. PCS Architecture 2.5. Forward Error Correction (FEC) Architecture 2.6. Clock Architecture 2.7. Bonding and Deskew
2.1. Building Blocks x
2.1.1. PMA 2.1.2. FEC 2.1.3. PCS 2.1.4. Ethernet MAC 2.1.5. PCI Express* Hard IP 2.1.6. PLL and Clock Networks 2.1.7. Avalon® Memory-Mapped Interface
2.1.1. PMA x
2.1.1.1. Protocol Support Using PMA Direct Mode
2.1.1.1. Protocol Support Using PMA Direct Mode x
2.1.1.1.1. SDI 2.1.1.1.2. HDMI 2.1.1.1.3. DisplayPort 2.1.1.1.4. CPRI 2.1.1.1.5. OTN
2.2. Channel Placement Rules and Design Requirements x
2.2.1. Hard IP Rules 2.2.2. Use Scenario Rules 2.2.3. Unused PMA Rules 2.2.4. General Design Requirement
2.2.3. Unused PMA Rules x
2.2.3.1. Unused PMA Not Planned for Use in the Future 2.2.3.2. Unused PMA Planned for Use in the Future
2.3. PMA Architecture x
2.3.1. Transmitter PMA Architecture 2.3.2. Receiver PMA Architecture 2.3.3. PMA Loopback Modes
2.3.1. Transmitter PMA Architecture x
2.3.1.1. Transmitter Buffer 2.3.1.2. Serializer 2.3.1.3. Data Pattern Generator and Verifier
2.3.2. Receiver PMA Architecture x
2.3.2.1. Receiver Buffer and Equalizer 2.3.2.2. Deserializer 2.3.2.3. CDR Block 2.3.2.4. PMA Tuning
2.3.2.1. Receiver Buffer and Equalizer x
2.3.2.1.1. Control Unit
2.5. Forward Error Correction (FEC) Architecture x
2.5.1. FEC Loopback Mode
2.6. Clock Architecture x
2.6.1. Reference Clock Network 2.6.2. Datapath Clock Network 2.6.3. System PLL 2.6.4. Datapath Clock Cadences 2.6.5. Shared Clocking Resources Between the GTS Transceiver Bank and HVIO Bank
2.6.1. Reference Clock Network x
2.6.1.1. Single GTS Transceiver Bank Device 2.6.1.2. PMA Primary PLL Configuration
2.6.3. System PLL x
2.6.3.1. I/O PLLs in HVIO Bank as System PLL 2.6.3.2. Running PCIe* and Non- PCIe* Protocols in a GTS Transceiver Bank 2.6.3.3. System PLL Clock for FPGA Core 2.6.3.4. System PLL with HVIO Reference Clock
2.7. Bonding and Deskew x
2.7.1. Bonding Architecture 2.7.2. TX Deskew Function
3. Implementing the GTS PMA/FEC Direct PHY Intel FPGA IP x
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.1. IP Overview x
3.1.1. PMA Direct Supported Modes 3.1.2. FEC Direct Supported Modes 3.1.3. PCS Direct Supported Modes 3.1.4. Unsupported PMA/FEC/PCS Modes
3.3. Configuring the GTS PMA/FEC Direct PHY Intel FPGA IP x
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.3.3. TX Datapath Options x
3.3.3.1. TX PMA Interface Parameters
3.3.4. RX Datapath Options x
3.3.4.1. RX PMA Interface Parameters
3.3.5. PMA Configuration Rules for Specific Protocol Mode Implementations x
3.3.5.1. PMA Configuration Rules for SDI Mode 3.3.5.2. PMA Configuration Rules for HDMI Mode 3.3.5.3. PMA Configuration Rules for DisplayPort Mode 3.3.5.4. PMA Configuration Rules for CPRI Mode
3.4. Signal and Port Reference x
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
3.6. Clocking x
3.6.1. Clock Ports 3.6.2. Recommended tx/rx_coreclkin Connection and tx/rx_clkout2 Source 3.6.3. Port Widths and Recommended Connections for tx/rx_coreclkin, tx/rx_clkout, and tx/rx_clkout2 3.6.4. PMA Fractional Mode 3.6.5. Input Reference Clock Buffer Protection
3.6.5. Input Reference Clock Buffer Protection x
3.6.5.1. Reference Clock Buffer Register Information 3.6.5.2. Re-enabling the Reference Clock Buffers
3.7. Custom Cadence Generation Ports and Logic x
3.7.1. Enabling the i_tx_cadence_slow_clk_locked Port
3.8. Asserting Reset x
3.8.1. Reset Signal Requirements 3.8.2. Power On Reset Requirements 3.8.3. Reset Signals—Block Level 3.8.4. Run-time Reset Sequence—TX 3.8.5. Run-time Reset Sequence—RX 3.8.6. Run-time Reset Sequence—TX + RX 3.8.7. RX Data Loss/CDR Lock Loss (Auto-Recovery) 3.8.8. TX PLL Lock Loss 3.8.9. TX PLL Lock Loss Auto-Recovery (Soft CSR Enabled)
3.9. Bonding Implementation x
3.9.1. Bonding Placement Requirements 3.9.2. Multilane RX Simplex Implementation
3.10. Configuration Register x
3.10.1. GTS PMA and FEC Direct PHY Soft CSR Register Map 3.10.2. GTS PMA Register Map 3.10.3. Accessing Configuration Registers
3.10.2. GTS PMA Register Map x
3.10.2.1. Logical Avalon® Memory-Mapped Port Indexing
3.10.3. Accessing Configuration Registers x
3.10.3.1. Accessing GTS PMA and FEC Direct PHY Soft CSR Registers 3.10.3.2. Accessing GTS PMA Registers
3.11. Configuring the GTS PMA/FEC Direct PHY Intel FPGA IP for Hardware Testing x
3.11.1. Using Debug Endpoint Interface within the GTS PMA/FEC Direct PHY Intel FPGA IP 3.11.2. Using JTAG to Avalon Master Bridge Intel FPGA IP
3.11.1. Using Debug Endpoint Interface within the GTS PMA/FEC Direct PHY Intel FPGA IP x
3.11.1.1. RTL Connection Example for Debug Endpoint Avalon® Interface
3.11.2. Using JTAG to Avalon Master Bridge Intel FPGA IP x
3.11.2.1. RTL Connection Example for JTAG to Avalon Master Bridge Intel® FPGA IP
3.13. Hardware Configuration Using the Avalon® Memory-Mapped Interface x
3.13.1. Direct Register Method 3.13.2. GTS Attribute Access Method
3.13.1. Direct Register Method x
3.13.1.1. Direct Register Method Examples
3.13.2. GTS Attribute Access Method x
3.13.2.1. GTS Attribute Access Method Example 1 3.13.2.2. GTS Attribute Access Method Example 2 3.13.2.3. GTS Attribute Access Method Example 3
4. Implementing the GTS System PLL Clocks Intel FPGA IP x
4.1. IP Parameters 4.2. IP Port List 4.3. Mode of System PLL - System PLL Reference Clock and Output Frequencies 4.4. Guidelines for GTS System PLL Clocks Intel FPGA IP Usage 4.5. Guidelines to Indicate System PLL Reference Clock is Ready
4.5. Guidelines to Indicate System PLL Reference Clock is Ready x
4.5.1. Example Flow to Indicate System PLL Reference Clock is Ready
5. Implementing the GTS Reset Sequencer Intel FPGA IP x
5.1. IP Requirements 5.2. IP Parameters 5.3. IP Port List 5.4. GTS Reset Sequencer Intel FPGA IP General Interface 5.5. GTS Reset Sequencer Intel FPGA IP Design Flow 5.6. GTS Reset Sequencer Intel FPGA IP Use Cases
5.6. GTS Reset Sequencer Intel FPGA IP Use Cases x
5.6.1. Example Use Case 1 5.6.2. Example Use Case 2
6. GTS PMA/FEC Direct PHY Intel FPGA IP Example Design x
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
6.2. Generating the GTS PMA/FEC Direct PHY Intel FPGA IP Example Design x
6.2.1. Fast Simulation Support 6.2.2. GTS PMA/FEC Direct PHY Intel FPGA IP Example Design Directory Structure
6.4. Simulating the GTS PMA/FEC Direct PHY Intel FPGA IP Example Design Testbench x
6.4.1. Modifying the Example Design and Performing Simulation
7. Design Assistance Tools x
7.1. Clocking and Datapath Tool 7.2. TX Equalizer Tool
8. Debugging GTS Transceiver Links with Transceiver Toolkit x
8.1. GTS Transceiver Toolkit Parameter Settings 8.2. GTS Transceiver Toolkit GUI 8.3. GTS Transceiver Debugging Flow Walkthrough
8.2. GTS Transceiver Toolkit GUI x
8.2.1. Collection View
8.3. GTS Transceiver Debugging Flow Walkthrough x
8.3.1. Modifying the Design to Enable GTS Transceiver Debug Toolkit 8.3.2. Programming the Design into an Intel FPGA 8.3.3. Loading the Design to the Transceiver Toolkit 8.3.4. Creating Transceiver Links 8.3.5. Running BER Tests 8.3.6. Running Eye Viewer Tests 8.3.7. Running Link Optimization Tests
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.12. Configurable Quartus® Prime Software Settings

You can configure the GTS PMAs using the Quartus® Prime software settings (.qsf) file. You can also configure the HSSI TX and RX parameters through the Analog Parameter Options in the IP GUI. However, configuring the HSSI analog parameters through the .qsf file takes precedence over the IP GUI settings.

You can specify values for the following HSSI parameters in the Quartus® Prime settings file (.qsf) or use the Assignment Editor of the Quartus® Prime Pro Edition software to configure the GTS PMAs:

TX Equalization: 

set_instance_assignment -name HSSI_PARAMETER "tx_eq_main_tap=<parameter_value>" -to <TX_SERIAL_PIN> -entity <TOP_LEVEL_NAME>
Valid parameter settings:
  • Main_tap: 0-55
  • Pre_tap_1: 0-15
  • Pre_tap_2: 0-7
  • Post_tap_1: 0-19
Table 67.  TX Equalization HSSI Parameter Name and Values
HSSI Parameter Name Valid Parameter Values (Decimal)
tx_eq_main_tap 0-55
tx_eq_pre_tap_1 0-15
tx_eq_pre_tap_2 0-7
tx_eq_post_tap_1 0-19
Note: Refer to the TX Equalizer tool for the legal combinations.
Example assignments in .qsf file: 
  • set_instance_assignment -name HSSI_PARAMETER "tx_eq_main_tap=41" -to c12tx_serial[0] -entity top
  • set_instance_assignment -name HSSI_PARAMETER "tx_eq_pre_tap_1=1" -to c12tx_serial[0] -entity top
  • set_instance_assignment -name HSSI_PARAMETER "tx_eq_pre_tap_2=0" -to c12tx_serial[0] -entity top
  • set_instance_assignment -name HSSI_PARAMETER "tx_eq_post_tap_1=4" -to c12tx_serial[0] -entity top
Figure 71. Assignment Editor Example for TX Equalization
Note: It is recommended that you set some baseline values for the TX equalization parameters for your design to optimize the GTS PMA transmitter. You can use the GTS Transceiver Toolkit Parameter Settings to tune and find the optimal settings for your link.

TX Invert Pin: 38

To swap TX P and N serial lanes.

set_instance_assignment -name HSSI_PARAMETER "tx_invert_pin=<parameter_value>" -to <TX_SERIAL_PIN> -entity <TOP_LEVEL_NAME>
Table 68.  TX Invert Pin HSSI Parameter Name and Values
HSSI Parameter Name Valid Parameter Values
tx_invert_pin tx_invert_pin_enable
tx_invert_pin tx_invert_pin_disable

Example assignment in .qsf file: 

set_instance_assignment -name HSSI_PARAMETER "tx_invert_pin=tx_invert_pin_enable" -to tx_serial_data[0] -entity top

RX AC Coupling: 

set_instance_assignment -name HSSI_PARAMETER "rx_external_couple_type=<parameter_value>" -to <RX_SERIAL_PIN> -entity <TOP_LEVEL_NAME>
You must set the correct RX AC coupling type according to your RX external coupling link setup. The valid parameter settings:

  • RX_EXTERNAL_COUPLE_TYPE_AC: When you use external AC coupling capacitors in your link.

  • RX_EXTERNAL_COUPLE_TYPE_DC: When you do not use external AC coupling capacitors in your link.

Table 69.  RX AC Coupling HSSI Parameter Name and Values
HSSI Parameter Name Valid Parameter Values Use Case
rx_external_couple_type RX_EXTERNAL_COUPLE_TYPE_AC When AC coupling capacitor is used externally in the link.
rx_external_couple_type RX_EXTERNAL_COUPLE_TYPE_DC When AC coupling capacitor is not used externally in the link.
Example assignment in .qsf file: 
set_instance_assignment -name HSSI_PARAMETER "rx_external_couple_type=RX_EXTERNAL_COUPLE_TYPE_AC" -to c12rx_serial[0] -entity top
Figure 72. Assignment Editor Example for RX AC Coupling

RX Termination Mode: 

set_instance_assignment -name HSSI_PARAMETER "rx_termination_mode=<parameter_value> -to <RX_SERIAL_PIN> -entity
<TOP_LEVEL_NAME>
Valid parameter settings:

  • RX_TERMINATION_MODE_GROUNDED: Grounded termination mode for AC coupled link

  • RX_TERMINATION_MODE_DIFFERENTIAL: Differential termination mode for DC coupled link39

Table 70.  RX Termination Mode HSSI Parameter Name and Values
HSSI Parameter Name Valid Parameter Values Use Case
rx_termination_mode RX_TERMINATION_MODE_GROUNDED For AC coupled link (when you enable AC coupling externally)
rx_termination_mode RX_TERMINATION_MODE_DIFFERENTIAL For DC coupled link (when you do not enable AC coupling externally)
Example assignment in .qsf file: 
set_instance_assignment -name HSSI_PARAMETER "rx_termination_mode=RX_TERMINATION_MODE_GROUNDED" -to c12rx_serial[0]” -entity top
set_instance_assignment -name HSSI_PARAMETER "rx_termination_mode=RX_TERMINATION_MODE_DIFFERENTIAL" -to c12rx_serial[0]” -entity top
Note: The rx_termination_mode is currently set by default to the GROUNDED mode in the GTS PMA/FEC Direct PHY Intel FPGA IP.

RX On-Chip Termination: 

set_instance_assignment -name HSSI_PARAMETER "rx_onchip_termination_setting=<parameter_value>" -to <RX_SERIAL_PIN> -entity <TOP_LEVEL_NAME>
Valid parameter settings:

  • RX_ONCHIP_TERMINATION_SETTING_R_1: 85 Ohms

  • RX_ONCHIP_TERMINATION_SETTING_R_2: 100 Ohms

Table 71.  RX On-Chip Termination HSSI Parameter Name and Values
HSSI Parameter Name Valid Parameter Values Use Case
rx_onchip_termination_setting RX_ONCHIP_TERMINATION_SETTING_R_1 85 Ohm
rx_onchip_termination_setting RX_ONCHIP_TERMINATION_SETTING_R_2 100 Ohm
Example assignment in .qsf file: 
set_instance_assignment -name HSSI_PARAMETER "rx_onchip_termination_setting=RX_ONCHIP_TERMINATION_SETTING_R_2" -to  c12rx_serial[0] -entity top
Figure 73. Assignment Editor Example for RX On-Chip Termination
Note: It is recommended that you set the rx_onchip_termination_setting parameter based on your transmission link characteristic impedance.

RX Invert Pin: 38

To swap RX P and N serial lanes.

set_instance_assignment -name HSSI_PARAMETER "rx_invert_pin=<parameter_value>" -to <RX_SERIAL_PIN> -entity <TOP_LEVEL_NAME>
Table 72.  RX Invert Pin HSSI Parameter Name and Values
HSSI Parameter Name Valid Parameter Values
rx_invert_pin rx_invert_pin_enable
rx_invert_pin rx_invert_pin_disable

Example assignment in .qsf file: 

set_instance_assignment -name HSSI_PARAMETER "rx_invert_pin=rx_invert_pin_enable" -to rx_serial_data[0] -entity top

Manual Tuning:

If you want to bypass the RX auto adaptation mode for the PMA lane you are using in the GTS PMA/FEC Direct PHY Intel® FPGA IP, you can change the PMA lane adaptation to RX manual adaptation mode by using the following .qsf settings shown below: 
set_instance_assignment -name HSSI_PARAMETER "flux_mode=FLUX_MODE_FLUX_MODE_BYPASS" -to <RX_SERIAL_PIN> -entity <TOP_LEVEL_NAME>
set_instance_assignment -name HSSI_PARAMETER "rx_adaptation_mode=RX_ADAPTATION_MODE_MANUAL_ADAPTATION" -to <RX_SERIAL_PIN> -entity <TOP_LEVEL_NAME>

RX Manual Tuning:

If you configure the RX link to manual tuning mode (RX adaptation mode is set to manual mode in the IP GUI), you must provide the RX PMA analog settings. You can use the GTS Transceiver Toolkit Parameter Settings to tune the link during manual adaptation mode to find the optimal setting for the RX analog parameters. You can control the VGA gain, High frequency boost, and DFE Tap 1 PMA settings by selecting the value in the Analog Parameters tab or by using the following .qsf settings shown below:

  • VGA gain:
    set_instance_assignment -name HSSI_PARAMETER "rx_eq_vga_gain=<parameter_value>" -to <RX_SERIAL_PIN> -entity <TOP_LEVEL_NAME>
    Valid parameter values (decimal) are 0-63.
  • High frequency boost:
    set_instance_assignment -name HSSI_PARAMETER "rx_eq_hf_boost=<parameter_value>" -to <RX_SERIAL_PIN> -entity <TOP_LEVEL_NAME>
    Valid parameter values (decimal) are 0-63.
  • DFE Tap 1:
    set_instance_assignment -name HSSI_PARAMETER "rx_eq_dfe_tap_1=<parameter_value>" -to <RX_SERIAL_PIN> -entity <TOP_LEVEL_NAME>
    Valid parameter values (decimal) are 0-63.
    Note: If you are using the auto adaptation mode, do not configure the VGA gain, High frequency boost, and DFE Tap 1 PMA settings in the .qsf file, as it results in a compilation error.

VSR Mode: 

set_instance_assignment -name HSSI_PARAMETER "vsr_mode=<parameter_value>" -to <RX_SERIAL_PIN> -entity <TOP_LEVEL_NAME>
Table 73.  VSR Mode HSSI Parameter Name and Values
HSSI Parameter Name Valid Parameter Values Recommended Use Case
vsr_mode vsr_mode_low_loss Data rate >= 23 Gbps, RX auto adaptation mode is selected, Insertion loss < 8 dB.
vsr_mode_high_loss Data rate >= 23 Gbps, RX auto adaptation mode is selected, Insertion loss > 8 dB and < 10 dB.
vsr_mode_disabled All other conditions not mentioned above.

Example assignment in .qsf file: 

set_instance_assignment -name HSSI_PARAMETER "vsr_mode=vsr_mode_low_loss" -to rx_serial_data[0] -entity top
38 This feature support is preliminarily and not supported in hardware in the current Quartus® Prime Pro Edition software release.
39 Preliminary setting pending hardware verification.
Level Two Title