2025-11-25 4:40 AM
So i was failing to properly flash my STM32N6 because in version STM32_SigningTool_CLI 2.21. I think it's because it doesn't align the payload. So when i flashed the board made with 2.21 it didn't recognize it and didn't load.
In version 2.20 this doesn't happen. I don't know if this is a bug or a failed configuration. But i used the same command for both of them and it worked in version 2.20.
Solved! Go to Solution.
2025-11-25 6:02 AM
Hello @Brenden_PLUS,
As highlighted in the warning message, with STM32CubeProgrammer v2.21, we have updated the header v2.3 preparation method because it is used for both MP21 (which doesn’t require alignment at offset 0x400) and STM32N6 (which does require alignment). A new CLI option has now been added to specify the intended platform.
To solve this please add the -align or --align option to the signing tool command:
> STM32_SigninTool_CLI -bin zephyr.bin -nk -of 0x80000000 -t fsbl -o GPIO_IOToggle_FSBL-trusted.bin -hv 2.3 -align -dump GPIO_IOToggle_FSBL-Trusted.bin
For more information about the new option, you can refer to the STM32 Signing tool User Manual.
Thanks,
Amine.
2025-11-25 6:02 AM
Hello @Brenden_PLUS,
As highlighted in the warning message, with STM32CubeProgrammer v2.21, we have updated the header v2.3 preparation method because it is used for both MP21 (which doesn’t require alignment at offset 0x400) and STM32N6 (which does require alignment). A new CLI option has now been added to specify the intended platform.
To solve this please add the -align or --align option to the signing tool command:
> STM32_SigninTool_CLI -bin zephyr.bin -nk -of 0x80000000 -t fsbl -o GPIO_IOToggle_FSBL-trusted.bin -hv 2.3 -align -dump GPIO_IOToggle_FSBL-Trusted.bin
For more information about the new option, you can refer to the STM32 Signing tool User Manual.
Thanks,
Amine.