Use Cases

This topic describes use cases that can be demonstrated with the current implementation of the component.

Reporting Software-detected Errors from CCPLEX to SEH (FSI) and MCU

1. Call NvEplInit() API so that the connection of the client is established with the driver.

2. Use NvEpl_ReportError() to report errors to FSI.

3. Refer DemoAppSwErr.c to check sample usage of above API.

Reporting software-detected errors from FSI SWC to SEH (FSI) and MCU

EPS provides a sender-receiver port interface P_SR_SW_ERR_REPORT, to which any SWC can connect and report software detected error.

User Error Reporting

1. User can report software error (similar to use cases above) with reporter id and error codes defined by them. For user defined reporter IDs, MSBs should be 001, which will indicate that this reporter id is defined by customer. refer below image for reporter Id format:

2. 

Error Handling

1. Default error handling: 1. All software detected errors are notified to System Error Handler, and SOC error pin is asserted. 2. HSM uncorrected errors are notified to System Error Handler, SOC error pin is asserted and further interrupt notification for the error lines are disabled. 3. HSM corrected errors are notified to System Error Handler. SOC error pin is not asserted, interrupt notifications for the error lines are re-enabled after clearing the HSM/EC error status registers.