topic Re: s32k1 AIPS-Lite error message location in S32K

s32k1 AIPS-Lite error message location

baichuan — Wed, 31 Dec 2025 06:15:44 GMT

Hello

I have restricted access to some registers through AIPS-Lite. My understanding is that if there is an unauthorized access to these registers, the system will enter the HardFault interrupt.

Now, I want to record these unauthorized access attempts. How should I do this? I did not see any related registers in the S32K-RM.pdf for AIPS-Lite to store this error information.

Re: s32k1 AIPS-Lite error message location

danielmartynek — Tue, 06 Jan 2026 15:40:52 GMT

Hello @baichuan,

As you mentioned, there is no dedicated AIPS error status register.
When an access violation occurs, the core signals a BusFault exception.
You can read the stacked Program Counter (PC) value as described in this NXP document:

https://community.nxp.com/t5/S32K-Knowledge-Base/Fault-handling-on-S32K14x/ta-p/1114447

However, if the exception is Imprecise (indicated by CFSR[IMPRECISERR]), the stacked PC does not correspond to the actual instruction that caused the fault. This happens because the fault was detected after the write buffer committed the access.
To obtain precise fault information, you would need to disable the write buffer, but doing so will reduce system performance.

Regards,

Daniel

Re: s32k1 AIPS-Lite error message location

baichuan — Wed, 07 Jan 2026 06:23:59 GMT

Hello @danielmartynek

Thank you very much for your patient explanations. Perhaps I didn't express myself clearly. What I actually want to do is log this unauthorized access attempt within the BusFault handler. For example: `pflash:0x00001a74 failed to access peripheral[CAN0]:0x40024000`. Based on your description, the PC pointer can indeed provide the address in pflash, but how can I retrieve the destination address it attempted to access?

Re: s32k1 AIPS-Lite error message location

danielmartynek — Wed, 07 Jan 2026 08:58:51 GMT

Hi @baichuan,

It was clear to me from the start.
Unfortunately, the BusFault is imprecise, which means the BFAR register is invalid.
If the fault were precise, BFAR would contain the address of the peripheral register that caused the access violation.
When the BusFault is imprecise, the PC value saved on the stack is also not the exact instruction that triggered the fault.
In such cases, the only option is to retrieve the stacked PC and then analyze the preceding instructions to identify the most recent load or store operation and extract the target address.

BR, Daniel