Hard Processor System Technical Reference Manual: Agilex™ 5 SoCs

ID 814346
Date 7/19/2024
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents

5.8.7.6.7.1. S0-S5 Error Handling

Detection and recovery from S0-S5 errors summarized in section 5.1.10 Table 52 of version 1.0 of the MIPI I3C specification is supported by the controller. Detection and recovery are transparent to the slave application and is internally handled by the controller.

S0-S5 error is supported in Slave IP S6 is not a mandatory feature, therefore, it is not supported. Handling of S0-S5 is internal to the slave and transparent to the application that is, it does not require the intervention of the slave application and is not reported in the response.

In case of:

  • S0 and S1: All transfers are ignored until HDR Exit Pattern is detected.
  • S2: For CCC parity error, the CCC value is not updated and the old values are retained. For private read and write transfer, the appropriate error filed in response is updated.
  • S3-S4: Updates due to CCCs is halted and the slave retains the current values (without updating) until a STOP/START is observed.
  • S5: Illegally formatted CCC are handled internally. The CCC value is not updated and the old values are retained. No information is provided to the application.
Note: All slaves require an HDR Exit Pattern detector, even slaves that are not HDR capable.