cancel
Showing results for 
Search instead for 
Did you mean: 

Start debugging STM32 VS Code Extension

Dilbert K
Senior

I was using the SystemWorkbench for years and everything OK.  Recently changed to STM32CubeIDE and also able to build and debug within hours with released ST project "STM32Cube_FW_F4_V1.28.0".

Have tried to use the new "STM32 VS Code Extension" in VSCode as it is getting popular.

1. Followed the instructions to install "STM32CubeCLT", note : I installed in different location "C:\Tools\STM\STM32CubeCLT"

2. Modified the "WINDOWS_ST_CLT_PATH" and "TOOLCHAIN_DIRECTORIES" in gcc-arm-none-eabi.cmake, and the project is built successful - OK.

3. Try to "Debug" the project but it shows error message :

 

DilbertK_0-1709248326176.png

Questions :

For STM32CubeIDE, it is using OpenOCD.  

For VSCode, How to configured and setup to use the Debug Tools under STM32CubeCLT ?

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Dilbert K
Senior

Issue resolved by re-installed both 

- STM32CubeIDE and STM32CubeCLR to default location "C:\ST"

Looks like both tools are inter-connected to each other in un-documented manner.

View solution in original post

2 REPLIES 2
Dilbert K
Senior

DilbertK_0-1709253140542.png

Anyone knows how to update this for the Tools required for debugger ??

Dilbert K
Senior

Issue resolved by re-installed both 

- STM32CubeIDE and STM32CubeCLR to default location "C:\ST"

Looks like both tools are inter-connected to each other in un-documented manner.