External Data Abort when calling Clock_Ip_Init()

jonnyWHIS — Fri, 07 Aug 2026 09:37:39 GMT

Hi there,

I'm attempting to initialise some peripheral clocks using the RTD and S32 DS mex tool. (Note im generating the code in a M7 project, but actually building and running for a A53 project)

However, an external data abort occurs inside Clock_Ip_Init(). Specifically, the call stack looks like this:

Clock_Ip_Init -> Clock_Ip_InitClock() -> Clock_Ip_DisableCmuFcFceRefCntLfrefHfref().

This appears to be the first attempt to actually write to the CMU peripheral memory. The fault occurs on a LDR instruction on memory 0x4005'C028 which according the S32G3 memory map correctly resides within the CMU memory area.

At this stage, the MMU is not enabled, but my understanding is an external data abort occurs outside the CPU/MMU and is probably linked to secure access or a "locked" peripheral.

Am i right in saying the CMU needs to be made "accessible" from the A53 core in some manner prior calling Clock_Ip_Init()? If so, could you advise on the steps to do so?

Best regards,

Jonny

Device = S32G399A

Compiler = S32DS_GCC _11_4

Core = Cortex A53

S32GのトピックExternal Data Abort when calling Clock_Ip_Init()

External Data Abort when calling Clock_Ip_Init()