NUCLEO-H755ZI-Q "bound doStepSettingsValidation Failed: Device not found", eventhough board is connected and shows under devices and boards

[Magnys]

I have followed the following guide step by step (Except using the NUCLEO-H755ZI-Q board which I have):

 

I have copied the exact launch.json used in the guide, as well as ran the Project Setup as described in the guide. I also selected “DualCore_Debug” as debug configuration. When I start to debug the code the following error occurs pretty much instantly:

bound doStepSettingsValidation Failed: Device not found: run "Setup STM32Cube project(s)" command or set "deviceName"attribute

When clicking any of the two buttons the same error pops up a second time, I suspect that’s because of the two cores, but that’s only a guess.

When connecting the NUCLEO-board it is being detected by the operating system and is also listed under “STM32CUBE DEVICES AND BOARDS”:

NUCLEO-Board being detected by VS Code/STM32CubeIDE

When I re-run the Project setup I see the Projects correctly assigned to each core, although for the M7 another project has been automatically added, which I did not add myself:

Porjects being assigned to each Cortex-Core

Even when I remove the “Dual_Core_Test_4”-Project from the Cortex-M7 and click “Save and close”, it will reappear next time I run the Project Setup.

 

I am unsure how to proceed. I am also unsure what to set the “deviceName” attribute to in the launch.json (like the error message suggested), I haven’t tried that yet. I have started over twice and followed the guide again, nothing changed, I still get the same error. The board is connected to my computer via the USB debug connector, the LEDs light up and the MCU is running its example program it was shipped with. I have no extensions installed except the ones the STM32CubeIDE extension installed. I am using Linux (Arch) if that makes any difference.

I would greatly appreciate any help or directions.

 

Edit: I forgot to mention, the same error message also appears when the NUCLEO-board is not connected to the computer.

[Florent V]

Hi ​@Magnys,

 

To help you better, could you please verify that your ST Extensions are up to date?

Regarding the “second project” for the Cortex-M7 in the configuration Setup panel, there is indeed a bug that is currently being fixed. However, it should not affect debugging.

Do you get the same message if you launch only the CM7_debug debug configuration instead of the compound one?

 

KR,
/Flo

[Florent V]

Another point:
Have you updated the binary paths in your debug configuration?
Because in the guide’s launch.json, it is: ${workspaceFolder}/CM4/build/STM32H745ZI_DualCore_Example_CM…
But the binary name of your project may be different.

/Flo

[Magnys]

Thanks, that’s a good catch. No, I didn’t change them, that was certainly a problem. I did change the lines to

"imageFileName": "${workspaceFolder}/CM4/build/Dual_Core_Test_4_CM4.elf" // Loads the CM4.elf image

and

"imageFileName": "${workspaceFolder}/CM7/build/Dual_Core_Test_4_CM7.elf" // Loads the CM7.elf image

in all three cases (two lines for the CM7_Debug and one for the CM4_Debug).

 

When running the debug the error no longer persists and I am able to start the debug session and step through some of the startup code. But after some time I get various error messages. Most of the time I receive the message “bound doStepConnectToTarget Failed: could not connect: Connection timed out.” The errors are very different with each restart of the debugging session, I can’t make out any pattern. I can give further information if neccesary.

One thing I might suspect is that in the launch.json there is another path that will be different from mine:

"svdPath": "C:/ST/STM32CubeCLT_1.19.0/STMicroelectronics_CMSIS_SVD/STM32H745_CM7.svd"

and

"svdPath": "C:/ST/STM32CubeCLT_1.19.0/STMicroelectronics_CMSIS_SVD/STM32H745_CM4.svd"

But I can’t really find information about what to replace these with. Since I’m running Linux I don’t know where to look for SVD files.