SPRUIE9D May 2017 – May 2024 DRA74P , DRA75P , DRA76P , DRA77P
When a parity error occurs, the faulty data is consumed by the requester. VCOP may fetch and process bad data from IBUF or WBUF. ARP32 may try to execute a faulty instruction from the program cache, or read a faulty pointer from DMEM. To avoid these problems, the subsystem parity error interrupt scheme notifies ARP32 or the host of any parity errors (see Section 8.1.3.10.1, EVE Interrupt Sources – Memory Switch and Parity Error Interrupts).
To minimize corruption of the system, and to let the system host query the error detection registers, a user selectable parity error disconnect scheme is provided. This mechanism lets the user disconnect the ARP32 from the neighboring EVE system, and/or disconnect the OCP initiator port from the device interconnect. Each of these disconnects can be manually initiated by setting the EVE_DISC_CONFIG register, or EVE_DISC_CONFIG can be initiated when a specific parity error is detected based on requestor and memory. The disconnect sequence is enabled in the EVE_ED_OCPI_DISC_EN and EVE_ED_ARP32_DISC_EN registers. Figure 8-8 shows an overview of the disconnection request.