2025-11-14 7:29 PM - edited 2025-11-15 3:54 PM
Following the directions in https://docs.zephyrproject.org/latest/boards/st/stm32n6570_dk/doc/index.html images signed using STM32_SigningTool_CLI version 2.20.0 run OK on the board.
However, after upgrading to STM32CubeProgrammer 2.21.0, images no longer run (I believe the signature check is now failing on the device).
Reverting back to 2.20.0 fixes the signing issue on Windows, macOS, and Linux for the STM32N6570-DK board.
However, this is a blocker for developers using the Nucleo N657X0-Q board on Windows & Ubuntu because 2.20.0 has a bug which causes west flash to fail for this board on both Windows & Ubuntu. This west flash bug is fixed for Windows & Ubuntu in 2.21.0, but we can't use that version due to the signing issue in 2.21.0.
Solved! Go to Solution.
2025-11-17 2:35 AM
Hello @cgnd_chris,
With STM32CubeProgrammer v2.21, there has been a change where the tool doesn't align automatically the payload to 0x400 with padding bytes for N6. Here's a screenshot of where the change is in an example binary:
However, this is highlighted in this warning message:
And in signing tool help here:
To solve this, add the -align or --align to the signing CLI command and it should be fine.
Hope this solves the issue.
Aziz
2025-11-17 2:35 AM
Hello @cgnd_chris,
With STM32CubeProgrammer v2.21, there has been a change where the tool doesn't align automatically the payload to 0x400 with padding bytes for N6. Here's a screenshot of where the change is in an example binary:
However, this is highlighted in this warning message:
And in signing tool help here:
To solve this, add the -align or --align to the signing CLI command and it should be fine.
Hope this solves the issue.
Aziz
2025-11-17 10:19 PM
Thank you @Aziz BRIGUI this fixes the issue for me!
2025-12-02 9:14 AM
FYI, this issue was recently fixed in Zephyr with this PR: https://github.com/zephyrproject-rtos/zephyr/pull/99721