S32K3-FCCU-EIM

[Neo1096]

I used the RTD4.0.0 library +SPD

According to the descriptions in some documents, my understanding is that after the initialization of EMCEMCHU (EMI,EMR,FCCU,DCM initialization), EMI selects the injected channel and error type, such as RAM errors, and then operates on RAM, such as reading or clearing the cache. At this point, it will jump to BusFault_Handler, and then detect whether the alarm interrupt of FCCU has occurred. If so, it will jump and clear the error.

The current problem encountered is the failure of the EIM injection error. I saw that no value was written to the EIM register after initialization, and when initiating and selecting the injection error, it would jump to the NMI error or BusFault_Handler

I think there might be problems with some of my configurations because most of the documents are done using MCAL's libraries, while I do it using Drivers.

I have uploaded the entire project to the website. Please help check where the problems are. Thank you

[danielmartynek · Accepted solution]

Hi @Neo1096,

I have tested it.

To get the alarm interrupt, set Reaction type to No reset reaction.

danielmartynek_0-1748592884283.png

danielmartynek_1-1748592924846.png

BR, Daniel

[danielmartynek]

Hello @Neo1096,

In the SafeAssure community, there is this example (It is RTD 1.0.0 though).

https://community.nxp.com/t5/SafeAssure-Community/S32K344-Example-for-EIM-and-ERM-module/m-p/1458016

Also, in S32K3 Secure files, refer to AN13323 - S32K3 + FS26 Safety Application Guide.

[danielmartynek]

Hi @Neo1096,

Let me check the project.

Anyway, the fault reaction is configurable.

danielmartynek_0-1748517473188.png

Refer to the SPD Tech overview attached.

Will you use the SAF too?

The evaluation version has a demo that you can refer to as well:

https://www.nxp.com/design/design-center/software/functional-safety-software/s32-safety-software-fra...

BR, Daniel