STM32N6570-DK LRUN project does not boot

[Laney]

Hello! 

I have a struggle to boot the isolation LRUN project from STM32Cube_FW_N6_V1.3.0/Projects/STM32N6570-DK/Templates/Template_Isolation_LRUN. 

1. First i've performed the mass erase to remove the demo on the discovery board. 

2. I've build and add the header to the binary with the Signing Tool for all three projects. Example below for FSBL. 
STM32_SigningTool_CLI -bin Template_Isolation_LRUN_FSBL.bin -nk -of 0x80000000 -t fsbl -o Template_Isolation_LRUN_FSBL-trusted.bin -hv 2.3 -dump Template_Isolation_LRUN_FSBL-trusted.bin

3. I've Flashed the external memory in DEV mode with all three images:
FSBL flashed to 0x7000 0000 
SecApp flashed to 0x7010 0000
NonSecApp flashed to 0x7018 0000

4. I've switched the board to Boot from ext. memory mode and pressed restart. 
The board doesn't boot. 

5. I've loaded the FSBL project in DEV mode with debugger to internal RAM( 0x3418 0400 ) and it runs nicely. 

-------------------------------------------------------------------------------------------------------------------------------------------------------

1. How can i debug the booting procedure to pinpoint where it fails ? Are there any NVM registers to read where boot ROM fails ?
2. Is there any manual for Signing Tool ? 

 




 

[RomainR.]

Hello @Laney 

Could you confirm which version of STM32CubeProgrammer (STM32_SigningTool_CLI) you are using ?
Concerning the last v2.21.0 refer to this requirement in the discussion below. 

https://community.st.com/t5/stm32cubeprogrammer-mcus/signingtool-for-stm32n6-in-stm32cubeprogrammer-v2-21-0/td-p/859154

The readme.md of the example mentions that the OTP HCONF 124 (VDDIO3_HSLV) must be programmed as the external serial flash operates in 1.8V on the STM32N657-DK.  
To debug, you can configure the board in DEV_BOOT and follow this base article to configure the debugger in STM32CubeIDE.

https://community.st.com/t5/stm32-mcus/how-to-debug-stm32n6-using-stm32cubeide/ta-p/800547

Let me know if it help?

Best regards,

Romain  

[Laney · Accepted solution]

Thank you @RomainR. for helping. 

Regarding STM32_SigningTool_CLI version. I am using the latest - v2.21.0.
But in the link you have provided regarding SigningTool( link ), the author states that a new tag has to be appended when making trusted binary for STM32N6. 
"To sign binaries for STM32N6, please take care to add the -align or --align option to the signing tool command, "

>STM32_SigningTool_CLI.exe -bin Project.bin -nk -of 0x80000000 -t fsbl -o Project-trusted.bin -hv 2.3 -dump Project-trusted.bin -align

With -align now project boots normally. 

Thank you