Visible to Intel only — GUID: vgo1461076501588
Ixiasoft
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
Visible to Intel only — GUID: vgo1461076501588
Ixiasoft
2.8.15. Error Handling
The SerialLite II IP core does error checking and has an interface to view local errors. The errors are categorized, and the effect of an error depends on the type of error that occurs.
The SerialLite II IP core has three error types:
- Data error
- Link error
- Catastrophic error
Error Type | Cause | Action |
---|---|---|
Data |
|
Two possibilities:
|
Link |
|
Trigger link initialization |
Catastrophic |
|
SerialLite II enters nonrecoverable state |
Packets Marked Bad | {EBP} marked packet | Received packet is marked as bad through the rxrdp_err or rxhpp_err signals, and forwarded to the user link layer. |
Error signals, such as txrdp_err and txhpp_err, are asserted by user logic.
- When txrdp_err is asserted with txrdp_eop, the packet is marked with the end of bad packet {EBP} marker.
- The txrdp_err signal is ignored when it is not asserted with txrdp_eop.
- When the txhpp_err is asserted and the Retry-on-error feature is turned off, the packet is marked with the {EBP} marker.
- When the txhpp_err is asserted and the Retry-on-error feature is turned on, the packet is not transmitted and is silently dropped.