SPRUIE9D May 2017 – May 2024 DRA74P , DRA75P , DRA76P , DRA77P
The procedure listed in Table 16-28 describes protection violation error identification and where it is logged in the control module registers. Two types of errors are logged: application errors and debug errors.
Step | Register/Bit Field/Programming Model | Value |
---|---|---|
Read the burst violation. | ERROR_LOG_k[23] 2D_BURST_VIOLATION | xxx |
Read the initiator ID. | ERROR_LOG_k[3:0] ConnID | xxx |
Read the command that caused the error. | ERROR_LOG_k[7] MCMD | xxx |
Read the address of the request that caused the error. | ERROR_LOG_k[31:12] SLVOFS_LOGICAL | xxx |
IF: Is it an application error? | L3_FLAGMUX_REGERR0 [31:0] REGERROR0 | 0x0 |
Read the status bits to see which module firewall has worked. | CONTROL.SEC_ERR_STATUS_FUNC_1[20:0] | xxx |
Clear the status bits. | CONTROL.SEC_ERR_STATUS_FUNC_1[20:0] | xxx |
Clear the status bit. | L3_TARG_STDERRLOG_MAIN [31] STDERRLOG_MAIN_CLRLOG | 0x0 |
ELSE IF | L3_FLAGMUX_REGERR1[7:0] REGERROR1 | = 0x1 |
Read the status bits to see the module. | CONTROL.SEC_ERR_STATUS_DEBUG_1[20:0] | xxx |
Clear the status bits. | CONTROL.SEC_ERR_STATUS_DEBUG_1[20:0] | xxx |
Clear the status bit. | L3_TARG_STDERRLOG_MAIN[31] STDERRLOG_MAIN_CLRLOG | 0x0 |
ENDIF | ||
Clear the burst violation. | ERROR_LOG_k[23] 2D_BURST_VIOLATION | 0x0 |
Clear the error status. | ERROR_LOG_k[21:17] REGION_START_ERRLOG | 0x00 |