Visible to Intel only — GUID: gmj1490746689754
Ixiasoft
Visible to Intel only — GUID: gmj1490746689754
Ixiasoft
4.6.2. Logical Layer Error Management
The Logical layer modules only need to process Logical layer errors because errors detected by the Physical layer are masked from the Logical layer module. Any packet with an error detected in the Physical layer is dropped in the Physical layer or the Transport layer before it reaches the Logical layer modules.
The RapidIO specification defines the following common errors and the protocols for managing them:
- Malformed request or response packets
- Unexpected Transaction ID
- Missing response (time-out)
- Response with ERROR status
The RapidIO IP core implements part of the optional Error Management Extensions as defined in Part 8 of the RapidIO Interconnect Specification Revision 2.1. However, because the registers defined in the Error Management Extension specification are not all implemented in the RapidIO IP core, the error management registers are mapped in the Implementation Defined Space instead of being mapped in the Extended Features Space.
The following Error Management registers are implemented in the RapidIO IP core and provide the most useful information for error management:
- Logical/Transport Layer Error Detect CSR
- Logical/Transport Layer Error Enable CSR
- Logical/Transport Layer Address Capture CSR
- Logical/Transport Layer Device ID Capture CSR
- Logical/Transport Layer Control Capture CSR
When enabled, each error defined in the Error Management Extensions triggers the assertion of an interrupt on the sys_mnt_s_irq output signal of the System Maintenance Avalon® -MM slave interface and causes the capture of various packet header fields in the appropriate capture CSRs.
In addition to the errors defined by the RapidIO specification, each Logical layer module has its own set of error conditions that can be detected and managed.