MSC8144E Reference Manual, Rev. 3
16-26
Freescale
Semiconductor
Serial RapidIO
®
Controller
the RapidIO Interconnect Specification, Revision 1.2, part VII (Error Management Extensions
Specifications).
16.2.10.1 RapidIO Error Description
RapidIO errors are classified under three categories: recoverable errors, notification errors, and
fatal errors.
Recoverable errors. Non-fatal transmission errors, such as a corrupt packet or corrupt
control symbols and general protocol errors, for which there is hardware detection and
recovery as described in the RapidIO Interconnect Specification, Revision 1.2. In these
cases, the appropriate bit is set in the Port 0 Error Detect CSR. Only the packet containing
the first detected recoverable error that is enabled for error capture (by the Port 0 Error
Enable CSR) is captured in the Port 0 Error Capture CSRs. No interrupt is generated or
actions required for a recoverable error. Recoverable errors are detected only in the
physical layer.
Notification errors. Non-recoverable non-fatal errors detected by RapidIO, such as
degraded threshold, port-write received, and all logical/transport layer (LTL) errors
captured. Because they are non-recoverable and in some cases have caused a packet to be
dropped, notification by interrupt is available. However, because they are non-fatal, a
response to the interrupt is not crucial to port performance. The port is still functional.
When a notification error is detected, the appropriate bit is set in the error-specific register,
an interrupt is generated, and in some cases, the error is captured. In all cases, the RapidIO
port continues operating. Notification errors are detected in both the physical and logical
layers.
Fatal errors. There are two types of fatal errors:
— Exceeded failed threshold. The port fails because its recoverable error rate has
exceeded a predefined failed threshold. RapidIO sets the Output Failed-encountered
bit in the Port0 Error and Status CSR; the RapidIO output hardware may or may not
stop (based on Stop-on-Port-Failed-Encounter-Enable and Drop-Packet-Enable bits).
— Exceeded consecutive retry. The port fails because it has received too many packet
retries in a row. The RapidIO controller sets the Retry Counter Threshold Trigger
Exceeded bit in the Port 0 Implementation Error CSR; the RapidIO hardware continues
to operate.
In both cases, an interrupt is generated, and while the port continues operating at least
partially, a system-level fix (such as reset) is recommended to clean up the RapidIO
controller internal queues and resume normal operation. Fatal errors are detected only in
the physical layer.
16.2.10.2 Physical Layer RapidIO Errors
Table 16-8 lists all the RapidIO link errors detected by the RapidIO endpoint physical layer and
the actions taken by the RapidIO endpoint. The Error Enable column lists the control bits that can
Summary of Contents for MSC8144E
Page 1: ...MSC8144E Reference Manual Quad Core Media Signal Processor MSC8144ERM Rev 3 July 2009 ...
Page 48: ...MSC8144E Reference Manual Rev 3 xlviii Freescale Semiconductor ...
Page 86: ...MSC8144E Reference Manual Rev 3 1 38 Freescale Semiconductor Overview ...
Page 168: ...MSC8144E Reference Manual Rev 3 3 60 Freescale Semiconductor External Signals ...
Page 242: ...MSC8144E Reference Manual Rev 3 5 26 Freescale Semiconductor Reset ...
Page 314: ...MSC8144E Reference Manual Rev 3 8 24 Freescale Semiconductor General Configuration Registers ...
Page 414: ...MSC8144E Reference Manual Rev 3 10 14 Freescale Semiconductor MSC8144E SC3400 DSP Subsystem ...
Page 452: ...MSC8144E Reference Manual Rev 3 11 38 Freescale Semiconductor Internal Memory Subsystem ...
Page 520: ...MSC8144E Reference Manual Rev 3 12 68 Freescale Semiconductor DDR SDRAM Memory Controller ...
Page 1070: ...MSC8144E Reference Manual Rev 3 21 28 Freescale Semiconductor Timers ...