S32k314 STM Clock question

dpsdprtmvl — Wed, 09 Apr 2025 10:05:54 GMT

We are currently migrating from the S32K344 environment to the S32K314.

During the GPT initialization process, a core power-down occurs.

One of the key differences we've identified between the S32K344 and the S32K314 is the generation of the STM1_CLK (STMB_CLK).
In the case of the S32K344, STMB_CLK is properly generated.

In the S32K314 environment, we forcibly added the STMB_CLK configuration to the generated Clock_Ip_PBcfg.c file.
After doing so, the GPT initialization worked correctly and the system booted without any issues.

However, we don’t understand why simply adding this configuration would cause the GPT init to work as expected.
We are trying to understand how this change alone resolves the issue.

Re: S32k314 STM Clock question

Robin_Shen — Fri, 11 Apr 2025 04:31:22 GMT

If it is a new project, it is recommended to use the latest S32K3 RTD, because many bugs are fixed.

Have you tested the latest S32K3_S32M27x Real-Time Drivers ASR R21-11 Version 5.0.0?

Best Regards,
Robin

S32KのトピックRe: S32k314 STM Clock question

S32k314 STM Clock question

Re: S32k314 STM Clock question