6. Event Management > Event Clearing and Recovery
CPS-1848 User Manual
164
June 2, 2014
Formal Status
This document is confidential and is subject to an NDA.
Integrated Device Technology
Double link request
Port {0..17} Implementation
Specific Error Detect
Register
.LR_X2 = 0, then
.IMP_SPEC_ERR = 0
Link partner may be a device compliant to a version of the
RapidIO Specification after 2.1, or may be incorrectly
implemented.
Ignore the link request and continue normal operation. No
hardware error recovery is used.
Received EOP outside of a
packet
Port {0..17} Implementation
Specific Error Detect
Register
.UNEXP_EOP = 0, then
.IMP_SPEC_ERR = 0
Either of the following may have occurred:
• A hardware/software failure in the originating endpoint
• A (highly unlikely) transmission error
Received stomp outside of a
packet
Port {0..17} Implementation
Specific Error Detect
Register
.UNEXP_STOMP = 0,
then
.IMP_SPEC_ERR = 0
Either of the following may have occurred:
• A hardware/software failure in the originating endpoint
• A (highly unlikely) transmission error
Port initialization TX required
Port {0..17} Implementation
Specific Error Detect
Register
.PORT_INIT = 0, then
.IMP_SPEC_ERR = 0
Indicates the link completed reinitialization.
If the link partner was reset, this may indicate that ackID
synchronization has been lost. See
.
Port width downgrade
Port {0..17} Implementation
Specific Error Detect
Register
.PORT_WIDTH = 0, then
.IMP_SPEC_ERR = 0
Indicates a significant loss of bandwidth on the link.
Software may attempt reinitialization of the port to determine if
this was the result of a permanent or transient error condition.
Isolation functions may be necessary to reduce congestion
caused by loss of bandwidth.
IDLE character in packet
Port {0..17} Implementation
Specific Error Detect
Register
.IDLE_IN_PKT = 0, then
.IMP_SPEC_ERR = 0
Transmission error - hardware error recovery
Loss of alignment
Port {0..17} Implementation
Specific Error Detect
Register
.LOA = 0, then
.IMP_SPEC_ERR = 0
Multiple transmission errors have caused the link to reinitialize.
Note that no packets are lost, and link state is retained.
Table 61: Physical Layer Events and Information Capture Summary (Continued)
Event
Clearing The Event
Event Handling Discussion