SAF eMCEM - Normal Operation Faults - S32G3

SHIVRAJ — Wed, 11 Jun 2025 04:30:27 GMT

Hello team!

I'm currently working on integrating SAF into BSW. While referring the eMCEM Safety Manual, there are 300+ S32G3 Faults listed.

1) Wanted to know if we are supposed to handle all of them?

2) If we can shortlist them, on what basis has it to be done?

3) On what basis do we forward them to either the Alarm Handler or the NMI Handler?

I'd really appreciate if anyone could help me out.
Thank you!

Re: SAF eMCEM - Normal Operation Faults - S32G3

chenyin_h — Thu, 12 Jun 2025 03:00:19 GMT

Hello, @SHIVRAJ

Thanks for your post.

1. The fault tables you mentioned present the FCCU fault symbolic names and their mapping to the NCFs of the S32G devices. It also contains the EIM channels. These EIM defines are valid for fault injection, which are not for fault reporting, so these EMCEM_FCCU* faults need to be handled.

2. FCCU can be configured to enter Alarm state when a fault is detected. In Alarm state, eMCEM module identifies which fault source or sources are active and calls a fault handler registered by the user for that source or sources. When the fault handler does not recover the fault before the alarm timeout interval expires, or when no fault handler is available, FCCU enters Fault State and generates a non-maskable interrupt. eMCEM module handles this interrupt and call Software Recovery (sReco) component in S32 SAF to records the fault information and issues a software functional reset.

Chenyin

S32G中的主题 Re: SAF eMCEM - Normal Operation Faults - S32G3

SAF eMCEM - Normal Operation Faults - S32G3

Re: SAF eMCEM - Normal Operation Faults - S32G3