S32KのトピックHardfault when we are not using debugger in S32K344

Hardfault when we are not using debugger in S32K344

MVR — Tue, 12 Aug 2025 21:10:12 GMT

Hello everyone,

I'm facing a weird issue. When I run my code in the debug mode, everything works properly (CAN, UART and so on).

But when I remove the debugger and reset the board, I can see that the CAN and other peripherals don't work as I expected.

Then, I attached the debugger activating this option:

And I could see that the system reaches the hardfault:

Before, I was facing the same issue (with debugger) and I could find out that the problem was the Interrupt Monitor into the Platform_Init(), when I removed this configuration on Tresos 29.0.0 (disable the INTM), I started to get hardfault in this new point into Mcl_Init(), showed below.

Also, I could see that if I commented out the Mcl_init(), I get hardfault as well in the Uart_Init(), in this point:

Again, using the system in debug mode, it doesn't happened. Can anyone help me with this problem?

I could see some topics related this issue and the people saying that HSE_CLK should be CORE_CLK/2, but it is already configured this way:

Thank you,

MVR

Re: Hardfault when we are not using debugger in S32K344

Senlent — Wed, 13 Aug 2025 05:33:27 GMT

Hi@MVR

"When I run my code in the debug mode, everything works properly (CAN, UART and so on)."

Most of these problems should be related to the clock configuration.

If you can provide a complete project, I can help you check it.

Re: Hardfault when we are not using debugger in S32K344

MVR — Wed, 13 Aug 2025 12:14:22 GMT

Sent you via private message due to confidentiality...

But as soon as we fixed this issue, I will post the solution here to help the community.

Thanks.

Re: Hardfault when we are not using debugger in S32K344

Senlent — Thu, 14 Aug 2025 08:43:18 GMT

Hi@MVR

I tested your code, you need to use "MCU_SetMode()" to turn on the peripheral clock, this is the reason for entering hardfault