Skip to main content
Explorer
April 17, 2024
Solved

STM32 extension for vscode is not working.

  • April 17, 2024
  • 5 replies
  • 7449 views

Greetings, I'm trying to set up Visual Studio Code to work with STM32 microcontrollers. I've installed the STM32 VS Code Extension, as well as CubeCLT, CubeMX, and FINDER as requested, all with the correct versions to ensure functionality. I've also defined the correct paths. However, the issue I'm facing is that it doesn't detect the workspace libraries like those in CubeCLT, nor does it seem to find the compilation path. I'm encountering many errors. I've tried including absolute paths in c_cpp_properties.json, and some of the issues seem to be resolved, but I've tried a bunch of addresses and not all of them are fixed. It doesn't recognize uint36_t or GPIO defines. Does anyone know what might be happening?

    This topic has been closed for replies.
    Best answer by luxae

    Hello Nawres,

    Yes, I've reconfigured the CLT path and now it's working. However, it only worked after compiling in Debug mode. Thanks for your help.

    5 replies

    Technical Moderator
    April 18, 2024

    Hi @luxae 

    could you please open VSCode settings type CLT and check if the correct path is set here ? 

     

    NawresGHARBI_0-1713430400040.png

     

    luxaeAuthorAnswer
    Explorer
    April 18, 2024

    Hello Nawres,

    Yes, I've reconfigured the CLT path and now it's working. However, it only worked after compiling in Debug mode. Thanks for your help.

    Explorer
    September 29, 2025

    I'm hitting a similar problem. Can I ask what the correct path should be? I have installed the CLT (RPM package), but could not find an executable named "stm32cubeclt". The files the package installed are in "/opt/st/stm32cubeclt_1.19.0". Using that path does not work.

    Technical Moderator
    September 29, 2025

    Hi @tmoerschell 

    which version you are running of the extension ? 

     

    Explorer
    October 6, 2025

    Sorry for the late reply. I think it was version 3.5. I then discovered the pre-release version, which was working without the dependency. However, I decided to move to openOCD, which works very well.