MX95 M7 safety functional

hankwang

Hi, Regarding the functional safety of i.MX95, I noticed that there is a safety manual available, but it requires an NDA. Could I know what content is in this document? How do I sign an NDA?

Additionally, does the i.MX95 M7 core support the Safety Software Framework (SAF)? As far as I know, this feature is available for the S32 series. I would like to check if it is also supported on the i.MX95.

Regarding SAF framework, my understanding is that it provides APIs for users to monitor the current SoC health status (such as memory ECC, CPU voltage, or unresponsive GPIOs...etc).
Is my understanding correct? Please kindly clarify if there is any misunderstanding.

yipingwang

1. The i.MX95 Safety Manual is indeed an NDA-protected document.

You could sing a new NDA from https://www.nxp.com/webapp-signup/ndaReqForm

Once the NDA is in place, the document can be shared with you. The safety manual typically covers topics such as safety architecture, safety mechanisms, failure mode analysis, and guidance for achieving functional safety certifications (e.g., IEC 61508 / ISO 26262).

2. Yes. The i.MX95 functional safety solution includes SAF, and the Cortex-M7 safety execution environment is designed to run safety applications using SAF services. The Cortex-M33 acts as the primary safety processor running SysMgr and SAF infrastructure, while the Cortex-M7 serves as the auxiliary safety processor for executing the safety application and optional SAF services.

3. Your description is largely correct — SAF provides APIs to monitor SoC health, including features like memory ECC monitoring, voltage supervision, and GPIO diagnostics, among others. SAF is a safety middleware/framework that sits between the application and the underlying safety mechanisms of the SoC. It helps collect diagnostic results, manage fault events, execute safety checks, and coordinate the system reaction when a fault is detected.

View solution in original post

yipingwang

1. The i.MX95 Safety Manual is indeed an NDA-protected document.

You could sing a new NDA from https://www.nxp.com/webapp-signup/ndaReqForm

Once the NDA is in place, the document can be shared with you. The safety manual typically covers topics such as safety architecture, safety mechanisms, failure mode analysis, and guidance for achieving functional safety certifications (e.g., IEC 61508 / ISO 26262).

2. Yes. The i.MX95 functional safety solution includes SAF, and the Cortex-M7 safety execution environment is designed to run safety applications using SAF services. The Cortex-M33 acts as the primary safety processor running SysMgr and SAF infrastructure, while the Cortex-M7 serves as the auxiliary safety processor for executing the safety application and optional SAF services.

3. Your description is largely correct — SAF provides APIs to monitor SoC health, including features like memory ECC monitoring, voltage supervision, and GPIO diagnostics, among others. SAF is a safety middleware/framework that sits between the application and the underlying safety mechanisms of the SoC. It helps collect diagnostic results, manage fault events, execute safety checks, and coordinate the system reaction when a fault is detected.

hankwang

@yipingwang Thank you for the information.

hankwang

Can anyone help?