In NUCLEO-N657X0-Q model is not getting Flashed to the board correctly.

[VinaySankar]

Initially I was having issues in generating the project file for ai models because of CUBE AI withe the latest update it got fixed. But while trying to build an flash the code to the Board there was issue while flashing the code the debugger was giving output as target is not responding. for checking there was no issue with the connection or debugger I tried creating a sample example from CUBE MX and while running that one it was working fine.

I have given below the screen shot of the error that i was getting.

Thanks and Regards,

Vinay

[Julian E.]

Hello @VinaySankar,

 

Could you please describe the exact steps you followed for me to reproduce it please?

You confirm using X Cube AI version 10.1.0 and cubeIDE version > 18.0.0

 

Have a good day,

Julian

[VinaySankar]

From STmodelzoo I took an model compactible with STM32N6 and created a project file with CUBE MX with Cube AI. The CUBE AI version is 10.1.0,while uploading the model to the Cube MX it showed clock configuration issues, and it got self resolved the issue by itself. Then after generating the project file. I tried building the project file and flashing it to the NUCLEO board, the build was successful but while flashing the code I had the above issue.

Thanks and Regards,

Vinay

 

[Julian E.]

Hello @VinaySankar,

 

I would suggest you looking at this: https://community.st.com/t5/stm32-mcus/how-to-create-an-stm32n6-fsbl-load-and-run/ta-p/768206 

We are also working on a tutorial to create a basic AI app from scratch with CubeAI for the DK and Nucleo boards.

 

The issue regarding the FSBL you described is rooted in security and boot configuration mechanisms enforced by the STM32N6's TrustZone and BootROM setup.

 

FSBL Must Be Signed and Authenticated
The STM32N6, when TrustZone is enabled, expects the FSBL to be:

• Signed with the correct key.
• Authenticated by the boot ROM.
• Executed from a specific memory location, typically at boot, via secure boot path.

When you "Run" from CubeIDE:

• The debugger bypasses the boot ROM process.
• The signature verification does not happen.
• The security attributes of the memory regions may be unset or invalid.
• The debugger starts the code without going through the required secure boot process, which may cause the boot to hang, reset, or result in no response.

 

To use the FSBL app generated by cubeMX, you need to manually sign it as described in the link above then download it using STM32CubeProgrammer (don't forget to check the external loader for the nucleo).

 

Have a good day,

Julian

[VinaySankar]

Hi @Julian E.,
Thanks for the feedback, I will check with these documents try it this way as well, does this solve the issues for creating Ai application. Or did you say that you guys are currently in work to create the Ai application for the DK and Nucleo boards with Cube AI and CubeMX, is my understanding correct.

Thanks and Regards,

Vinay

[Julian E.]

Hello @VinaySankar,

 

These are two different points:

• We are creating more tutorial for the DK and Nucleo
• Please look at the document linked to solve your issue.

 

Have a good day,

Julian

[Alex410]

Thanks for sharing the update, Vinay! Since the CUBE MX sample worked, it could be something special in the generated AI project code or configuration. Maybe double check the linker settings or clock configuration in the AI ​​project. Let us know if you find a solution!