IDT CPS-1848, Руководство пользователя

Страница: 149 / 450

6. Event Management > Event Notification
CPS-1848 User Manual 149 June 2, 2014
Formal Status This document is confidential and is subject to an NDA.
Integrated Device Technology
6.3.9.2 Standard (Type 1) Port-Write Format
Standard port-writes are formatted as defined in the RapidIO Specification (Rev. 2.1). The format is displayed in the following
table.
This format supports the representation of errors from more than one error source in a Standard port-write command.
However, the occurrence of errors from more than one source simultaneously is expected to be infrequent and not
characteristic of typical conditions. In general, if errors from more than one error source occur simultaneously, then multiple
port-write packets are issued such that each port-write represents an error from a single error source only.
The CPS-1848 supports corner cases to this rule however. For example, the Standard port-write format supports multiple
errors from a source in the case of logical/transport layer errors and port-level errors.
Figure 26 summarizes how errors are reported in the Standard port-write packet data payload format for each potential error
source (Note: JTAG error source is applicable to Revision A/B only).
Figure 26: Type 1 Port-Write Packet Data Payload Format
The Rank column indicates the precedence with which error source are handled in the event that they detect errors
simultaneously (for example if an LT error occurred simultaneously with a Configuration Block error, then the LT error should
be reported first). The Error source column lists the potential sources of CPS-1848 errors. All other columns represent the
values that are stored in the various fields in the port-write command definition.
In all error reporting scenarios, the field of the Standard port-write format called Component Tag CSR is assigned with the
value of the
Component Tag CSR defined in the RapidIO Specification (Rev. 2.1), Part 3. This field is filled with the current
value of the CPS-1848 register of the same name.
The method in which the remaining fields of the Type 1 port-write format are assigned is discussed in the following separate
sections per classification of the error type.
Table 55: Standard (Type 1) Port-Write Format
Data Payload
Byte Offset Word
0x0 Component Tag CSR
0x4 Port {0..17} Error Detect CSR
0x8 Implementation Specific Port ID (byte)
0xC Logical/Transport Layer Error Detect CSR
Error source
LT Error
Port
n Error
Lane Error
Config Error
I2C Error
JTAG Error
Rank
1
2
3
4
5
6
LT-Layer
1
Error Detect CSR
LT-Layer Error Detect CSR
0
0
0
0
0
Port n Error Detect CSR
0
Port n Error Detect CSR
0
0
0
0
Port ID (byte)
port number
port number
Port number
0
0
0
Implementation Specific
[23:8]=0, [7:0]=error_code
[23:8]=0, [7:0]=error_code
[23:16]=0, [15:8]=ESlane, [7:0]=EClane
[23:16]=0, [15:8]=ESconfig, [7:0]=ECconfig
[23:16]=0, [15:8]=ESI2C
2
, [7:0]=ECI2C
3
[23:16]=0, [15:8]=ESJTAG, [7:0]=ECJTAG
NOTES:
1 LT-Layer = Logical/transport layer
2
ESI2C = Error source code identifying the I2C block (same as used in error logging)
3
ECI2C = Error code for the particular I2C-related error which is detected