STM32N6570-DK does not boot after flashing signed binary using STM32CubeProgrammer.

[Radhika]

Hi,

I am working with the STM32N6570-DK board. Initially, I am using the GPIO_IOToggle example project to verify the basic board functionality.

I configured the hardware using STM32CubeMX v6.16 and generated the project using the STM32CubeIDE toolchain. The project was built successfully using STM32CubeIDE v2.0.0.
When I run the project in debug mode from CubeIDE, the LED toggles correctly.

However, the device does not boot when I flash the binary manually using STM32CubeProgrammer v2.21.0.

Signing and Flashing Details

I am using the following command to sign the output binary generated by CubeIDE:

STM32_SigningTool_CLI -bin <path to fsbl project.bin file> -nk -t fsbl -hv 2.3 \
-o <path to fsbl project-trusted.bin file> \
-dump <path to fsbl project-trusted.bin file> -align

 After generating the trusted binary, I flash it at address 0x70000000 using STM32CubeProgrammer.

Boot Configuration

• BOOT0 switch: position 1–2

• BOOT1 switch: position 1–3

After flashing the trusted binary:

1. I change the BOOT0 switch back to 1–2

2. Power cycle the board

However, after reconnecting power, the board does not boot from the external flash.

Questions

1. Are the signing command and parameters I used correct for STM32N6570?

2. Is 0x70000000 the correct flash address for flashing the FSBL trusted binary?

3. If my project contains both FSBL and Application, how should the application binary be signed?

4. What is the correct flash address for appli-trusted.bin?

5. Are there any additional steps required (option bytes, header configuration, memory layout, etc.) to boot correctly from external flash?

Any guidance or reference documentation would be greatly appreciated.

Thank you for your support.

Best regards,
Radhika