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.16.2. Minimizing Logic Utilization
The amount of logic required for a SerialLite II link depends heavily on the features you choose.
Features | Description |
---|---|
Lane count | Running fewer lanes at higher bit rates, if possible, uses less logic (but places more of a burden on meeting performance). |
CRC | Significant savings can be made by eliminating CRC, or in particular, moving from CRC-32 to CRC-16 in high-lane-count designs. If you are using CRC- 32, evaluate carefully whether the extra protection over CRC-16 is really worthwhile, because CRC-16 uses far fewer resources. |
Flow control | This feature requires logic to monitor the FIFO buffer levels and to generate and act upon PAUSE instructions. |
Streaming mode | Use this mode if packet encapsulation is not required. The link-layer portion of the SerialLite II IP core contains a significant amount of logic, which is reduced to zero in streaming mode. |