2.8.1. Link Consistency
2.8.2. Data Rate
2.8.3. Reference Clock Frequency
2.8.4. Port Type
2.8.5. Self Synchronized Link Up
2.8.6. Scramble
2.8.7. Broadcast Mode
2.8.8. Lane Polarity and Order Reversal
2.8.9. Data Type
2.8.10. Packet Type
2.8.11. Flow Control Operation
2.8.12. Transmit/Receive FIFO Buffers
2.8.13. Data Integrity Protection: CRC
2.8.14. Transceiver Configuration
2.8.15. Error Handling
2.8.16. Optimizing the Implementation
2.8.14.4. Transceiver Reconfiguration Block
When you use an Arria® II GX, Arria® V, Intel® Arria® 10, Cyclone® V, Stratix® IV, or a Stratix® V device, you can instantiate a transceiver reconfiguration block.
The transceiver reconfiguration block dynamically changes the following physical media attachment (PMA) settings:
- Pre-emphasis
- Equalization
- VOD
- Offset cancellation
Note: For analog settings, there are no restrictions on using dynamic reconfiguration.
When you use a transceiver-based device, the ALTGX interface allows you to modify the parameter interface with a reconfiguration block. The altgx_reconfig block is not instantiated, but the Quartus-generated wrapper provides the ports that interface to the altgx_reconfig block.
If you choose to use an altgx_reconfig block, you must instantiate the altgx_reconfig block and connect the associated signals to the corresponding SerialLite II IP core top-level signals (tie the reconfig_fromgxb, reconfig_clk, and reconfig_togxb ports to the altgx_reconfig block).
Note: For Intel® Arria® 10, Arria® II GX, and Stratix® IV devices, you must instantiate the transceiver reconfiguration block on the devices, because these device transceivers require offset cancellation. Your Arria® II GX or Stratix® IV design can compile without the dynamic reconfiguration block but it cannot function correctly in hardware. For Arria® V, Cyclone® V, and Stratix® V devices, you need to include a dynamic reconfiguration block for the offset cancellation to occur.