Skip to main content
Visitor
August 14, 2026
Question

STM32N6570-DK + STM32Cube AI Studio: "Target is not responding" after successful download and verification

  • August 14, 2026
  • 1 reply
  • 23 views

Hello,

I am currently working on an AI project on the STM32N6570-DK using STM32Cube AI Studio and STM32CubeIDE.

I followed the official STM32N6 AI deployment tutorial and generated both projects:

  • FSBL
  • Appli

The AI files generated by STM32Cube AI Studio were copied into the project and the project builds successfully without errors.

The application is downloaded correctly to the board and the verification step is successful. However, when the debugger tries to start the execution, the target immediately stops responding.

The console shows:

Download verified successfully
Error in executing 'cont' command
Target is not responding, retrying...

I also get a message indicating a break at an address outside of the application code.

At this point I am not sure if:

  • the application is entering a HardFault very early during startup,
  • there is an issue with the FSBL configuration,
  • there is a problem with the linker script or the AI memory sections,
  • or if I missed a configuration step in the STM32N6 deployment procedure.

Has anyone already encountered this issue on the STM32N6570-DK?

What would be the best way to determine where the application stops before the debugger loses communication with the target?

Any help or suggestions would be greatly appreciated.

Thank you.

 

1 reply

Ghofrane GSOURI
ST Technical Moderator
August 14, 2026

Hello ​@Pepper 

Since the download and verification complete successfully, but the debugger then fails on cont with:

Download verified successfully
Error in executing 'cont' command
Target is not responding, retrying...

It would be worth checking whether the CPU is jumping to an unexpected address very early in the boot flow.

I would recommend reviewing these two official STM32 AI deployment guides first, because they describe the expected STM32Cube AI Studio generation flow, the FSBL + Appli structure, and the STM32N6 deployment procedure:

A few practical checks that may help isolate the issue:

  1. Enable “Connect under reset” in the debug configuration, so the debugger can halt the core before it runs into the fault.
  2. Put breakpoints in:
  • Reset_Handler
  • SystemInit()
  • main()
  • HardFault_Handler
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.