S32KのトピックRe: S32K344 Bootloader. Deinit Mcu

S32K344 Bootloader. Deinit Mcu

myst — Thu, 17 Apr 2025 20:56:23 GMT

I am implementing a bootloader in S32K344 and encountering some issues after the jump to the application firmware.
1 - I have verified that the jump is occurring correctly, but there are problems during the MCU initialization, its goes to HardFault. However, this does not always happen; often, the jump to the production firmware occurs without any issues. The times when this problem occurs are during the following sections of the MCU initialization:

The peripherals that the bootloader initialize uses are:
MCU, OsIf, Siul2_Port_Ip_Init, IntCtrl_Ip, Gpt, Spi, Sbc_fs26, Wdg_43_fs26, Lpuart_Uart, flash_c40.

The deinit function in bootloader:

How do I perform deinitialization in MCU functions?
Is there any additional step I need to take? Perhaps in the .mex?

2) I use the PTE13 port as an input. I have already used the solution of disabling the LMBCTLEN register, and it worked in the production firmware. However, when the production firmware is initialized by the bootloader, this register remains selected. In other words, the MCU initialization in the bootloader is not redone when I call Mcu_Init / Mcu_InitClock / Mcu_SetMode at production firmware. What do I suposto do?

3) As with question 2, the same issue is occurring with the PTA24 and PTA25 pins. In the production firmware, they have been configured correctly and work normally. However, when initialized by the bootloader, the SOSC source configuration is lost. What do I suposto do?

Re: S32K344 Bootloader. Deinit Mcu

danielmartynek — Wed, 23 Apr 2025 12:22:07 GMT

Hi @myst,

It is important to identify the fault exception. There can be many possible root caused.

Follow these documents:

https://community.nxp.com/t5/S32K-Knowledge-Base/Example-S32K312-HARDFAULT-Handling-Interrupt-DS3-5-RTD300/ta-p/1806259

https://community.nxp.com/t5/S32K-Knowledge-Base/How-To-Debug-A-Fault-Exception-On-ARM-Cortex-M-V7M-MCU-S32K3XX/ta-p/1595570
https://community.nxp.com/t5/S32K-Knowledge-Base/Fault-handling-on-S32K14x/ta-p/1114447

2 & 3.

Which RTD revision is this?

Thanks,

BR, Daniel

Re: S32K344 Bootloader. Deinit Mcu

myst — Thu, 24 Apr 2025 14:03:31 GMT

Hello, @danielmartynek

I'm glad your reply.
1. We going to identify the fault exception. When we identify, I will reply here.
2 & 3. RTD 5.0

Re: S32K344 Bootloader. Deinit Mcu

myst — Thu, 31 Jul 2025 18:24:47 GMT

Sorry for delay.
The solution was put the same config from .mex of bootloader fw on application fw. Don't initialize MUC in application fw, only initialize in the bootloader fw.
A tip: Don't put optimization on Startup_Code