S32K344 chip, failed to download using bootloader after adding eMCEM_1 module in spd

XPW — Fri, 03 Jul 2026 08:57:37 GMT

Sort out the logic and rewrite: As the title suggests, when I enabled eMCEM_1 in the app code, downloading the app using the official bootloader failed. If I didn't erase the chip, I couldn't enter the boot again, and even after powering it back on, it wouldn't solve the problem. I suspect that after powering it back on, the boot jumped to the app, but the app didn't run. When I disable eMCEM_1, this issue does not occur. How can I use boot to flash the app when eMCEM_1 is enabled

Re: S32K344 chip, failed to download using bootloader after adding eMCEM_1 module in spd

danielmartynek — Fri, 03 Jul 2026 11:05:33 GMT

Hi @XPW,

The problem description is not entirely clear.
If the application is being programmed through the bootloader, the eMCEM_1 configuration contained in the application should not affect the programming process itself, since the application is not executed during download, it is just a binary.
Only after the bootloader transfers execution to the application would eMCEM/FCCU-related configuration become relevant, and at that point, it would be useful to check:

FCCU status registers
DCM flags, MC_RGM flags.
Or whether the application actually reaches main()

Based on the current description, it is unclear whether the programming operation fails, or whether programming succeeds and the issue occurs later when the application starts executing.

Could you clarify the exact sequence of events?

Regards,

Daniel

S32KのトピックRe: S32K344 chip, failed to download using bootloader after adding eMCEM_1 module in spd

S32K344 chip, failed to download using bootloader after adding eMCEM_1 module in spd

Re: S32K344 chip, failed to download using bootloader after adding eMCEM_1 module in spd