The program runs normally with a debugger, but the program runs flying without a debugger

[SethWang]

Hi,

Using S32K312, I found that when debugging on FLASH with a debugger, the program ran normally. Without a debugger, when running the ADC to initialize the operation on the MCR registers, the program runaway. After doing some debugging, I found that when operating the registers of PWM or SPI without a debugger, the program will also runaway, but with a debugger, the program runs normally.

The program are all running on FLASH, I don't know the difference between with and without a debuger? Do you know why the program runaway without a debugger?

Thank you

[danielmartynek]

Hi @SethWang,

What does it actually do? Do you see a fault exception or a system reset?

The debugger can typically disable the WDOG or initialize SRAM ECC.

Can you double-check the SRAM ECC?

Thanks,

BR, Daniel

[erinc]

how can I check them without debugger?
My app also runs OK with debugger but goes to hard fault handler but I am not sure.
I put below code to my app and my test rgb led goes to red(error).

void HardFault_Handler(void)
{
set_rgb_status(ERROR);
while(TRUE){};
}

[danielmartynek]

Hi @erinc,

What debugger do you have?

Multilink can be attached to the running MCU stuck in the exception handler.

Make sure the clocks are configured precisely to one of the clock options.

RM, 24.7.2 System clocking configurations

Regards,

Daniel

[SethWang · Accepted solution]

Thank you.
The reasons is the configuration problem of PLL .The problem has solved.

[DouDou1]

Can you tell me how you solved the problem?