1.4.6 Transceiver Clocking Use Cases
(Ask a Question)Each transceiver quad can source a global clock directly. Transceiver designs should use regional clocks for the interface logic when possible. This reduces over use of global clocks. In many cases, transceiver designs can share global clocks when multiple interfaces are used, depending on protocol requirements. Only one global clock is supported per transceiver quad. See respective PolarFire FPGA Datasheet , RT PolarFire FPGA Datasheet, or PolarFire SoC Datasheet for AC performance information. For information about connectivity of the transceivers to the global clock network, see PolarFire Family Clocking Resources User Guide.
The following table lists the transceiver interface clocking use cases in the Libero SoC software, which uses presets per protocol. See PCS/FPGA Fabric Interface for explanation of system clock source modes.
| Preset | Width | Rx | Tx1 | System Clock Source1 |
|---|---|---|---|---|
| 10GBASE-R | x1 | Regional | Global | Global from XCVR Tx |
| 10GBASE-R | Multiple | Regional | Global shared | Global from XCVR Tx shared |
| 10GBASE-KR | x1 and Multiple | Regional | Regional | |
| SGMII/1000BASE | x1 | Regional | Regional | Global from XCVR Tx |
| SGMII/1000BASE | Multiple | Regional | Global shared | Global from XCVR Tx shared |
| JESD204B | x1 | Regional | Global | Global from XCVR Tx shared |
| JESD204B | xN | Regional | Global shared | Global from XCVR Tx shared |
| CPRI | x1 | Regional | Regional | Global |
| CPRI | xN | Regional | Regional | Global shared |
| Interlaken | xN | Regional ≥ Global2 | Global shared | Global from XCVR Tx shared |
| XAUI | x4 | Regional | Global shared | Global from XCVR Tx shared |
| RXAUI | x2 | Regional | Global shared | Global from XCVR Tx shared |
| SDI3 | x1 | Global | Global | Global |
| SDI3 | Multiple | Global | Global shared | Global |
| LiteFast3 | x1 | Global | Global | Global from XCVR Tx and Rx |
| LiteFast3 | xN | Regional ≥ Global2 | Global shared | Global from XCVR Tx (shared) and Rx |
| LiteFast3 | x1 and Multiple | Global | Global shared | Global from XCVR Tx (shared) and Rx (per interface) |
| QSGMII | x1 | Regional | Regional | Global 125 MHz |
| QSGMII | Multiple | Regional | Global shared | Global 125 MHz Shared |
| SATA3 | x1 | Global Tx | Global Tx | Global Tx |
| SATA3 | Multiple | Global Tx | Global Tx | Global Tx (not shared) |
| SRIO | x1 | Regional | Global | Global |
| SRIO | xN | Regional | Global shared | Global |
| SRIO | Multiple | Regional | Global (per interface) | Global |
| Fiber Channel | x1 | Regional | Global Tx | Global Tx |
| Fiber Channel | Multiple | Regional | Global Tx shared | Global Tx Shared |
| (1) Shared implies that multiple lanes use common clock resources. (2) Uses regional clock and moves to global clock resources in the FPGA fabric. (3) Typically, these interfaces are implemented uni-directional. For full duplex, the RX interface and TX interface clock can not be global or global (Shared) at the same time as only one global clock is supported per transceiver quad. If using the RX and TX both as global is required by design, the design must use two separate XCVR configurations (instances), one in RX half duplex mode and other in TX half duplex mode. |
