2.2.2.2.1. Non-Bonded Channel Configurations Using the x1 Clock Network
2.2.2.2.2. Non-Bonded Channel Configurations Using the xN Clock Network
2.2.2.2.3. Bonded Channel Configurations
2.2.2.2.4. Bonded Channel Configurations Using the xN Clock Network
2.2.2.2.5. Bonded Channel Configurations Using the PLL Feedback Compensation Path
3.2.1. User-Coded Reset Controller Signals
3.2.2. Resetting the Transmitter with the User-Coded Reset Controller During Device Power-Up
3.2.3. Resetting the Transmitter with the User-Coded Reset Controller During Device Operation
3.2.4. Resetting the Receiver with the User-Coded Reset Controller During Device Power-Up Configuration
3.2.5. Resetting the Receiver with the User-Coded Reset Controller During Device Operation
4.1. Protocols and Transceiver PHY IP Support
4.2. 10GBASE-R and 10GBASE-KR
4.3. Interlaken
4.4. PCI Express (PCIe)—Gen1, Gen2, and Gen3
4.5. XAUI
4.6. CPRI and OBSAI—Deterministic Latency Protocols
4.7. Transceiver Configurations
4.8. Native PHY IP Configuration
4.9. Stratix V GT Device Configurations
4.10. Document Revision History
4.2.1. 10GBASE-R and 10GBASE-KR Transceiver Datapath Configuration
4.2.2. 10GBASE-R and 10GBASE-KR Supported Features
4.2.3. 1000BASE-X and 1000BASE-KX Transceiver Datapath
4.2.4. 1000BASE-X and 1000BASE-KX Supported Features
4.2.5. Synchronization State Machine Parameters in 1000BASE-X and 1000BASE-KX Configurations
4.2.6. Transceiver Clocking in 10GBASE-R, 10GBASE-KR, 1000BASE-X, and 1000BASE-KX Configurations
4.4.1. Transceiver Datapath Configuration
4.4.2. Supported Features for PCIe Configurations
4.4.3. Supported Features for PCIe Gen3
4.4.4. Transceiver Clocking and Channel Placement Guidelines
4.4.5. Advanced Channel Placement Guidelines for PIPE Configurations
4.4.6. Transceiver Clocking for PCIe Gen3
6.1. Dynamic Reconfiguration Features
6.2. Offset Cancellation
6.3. PMA Analog Controls Reconfiguration
6.4. On-Chip Signal Quality Monitoring (Eye Viewer)
6.5. Decision Feedback Equalization
6.6. Adaptive Equalization
6.7. Dynamic Reconfiguration of Loopback Modes
6.8. Transceiver PLL Reconfiguration
6.9. Transceiver Channel Reconfiguration
6.10. Transceiver Interface Reconfiguration
6.11. Document Revision History
2.3.2.2. Selecting a Receiver Datapath Interface Clock
Multiple non-bonded receiver channels use a large portion of GCLK, RCLK, and PCLK resources. Selecting a common clock driver for the receiver datapath interface of all identical receiver channels saves clock resources.
Non-bonded multiple receiver channels lead to high utilization of GCLK, RCLK, and PCLK resources—one clock resource per channel. You can significantly reduce GCLK, RCLK, and PCLK resource use for the receiver datapath clocks if the receiver channels are identical.
Note: Identical receiver channels are defined as channels that have the same input reference clock source for the CDR and the same receiver PMA and PCS configuration. Identical receiver channels need to be PPM aligned with regards to their remote transmitters. These channels may have different analog settings, such as receiver common mode voltage (VICM), equalization, or DC gain setting.
To achieve clock resource savings, select a common clock driver for the receiver datapath interface of all identical receiver channels. To select a common clock driver, perform these steps:
- Instantiate the rx_coreclkin port for all the identical receiver channels.
- Connect the common clock driver to their receiver datapath interface, and receiver data and control logic.
The following figure shows eight identical channels that are clocked by a single clock (rx_clkout of channel 4).
Figure 76. Eight Identical Channels with a Single User-Selected Receiver Interface Clock
To clock eight identical channels with a single clock, perform these steps:
- Instantiate the rx_coreclkin port for all the identical receiver channels (rx_coreclkin[7:0]).
- Connect rx_clkout[4] to the rx_coreclkin[7:0] ports.
- Connect rx_clkout[4] to the receiver data and control logic for all eight channels.
Note: Resetting or powering down channel 4 leads to a loss of the clock for all eight channels.
The common clock must have a 0 ppm difference for the write side of the RX phase compensation FIFO of all the identical channels. A frequency difference causes the FIFO to under run or overflow, depending on whether the common clock is faster or slower, respectively.
You can drive the 0 ppm common clock driver from one of the following sources:
- tx_clkout of any channel in non-bonded receiver channel configurations with the rate matcher
- rx_clkout of any channel in non-bonded receiver channel configurations without the rate matcher
- tx_clkout[0] in bonded receiver channel configurations
- Dedicated refclk pins
Note: The Quartus II software does not allow gated clocks or clocks generated in the FPGA logic to drive the rx_coreclkin ports.
Note: You must ensure a 0 ppm difference. The Quartus II software is unable to ensure a 0 ppm difference because it allows you to use external pins, such as dedicated refclk pins.