STM32CubeIDE for Visual Studio Code (MCUs)

Hello dear customers, We understand that many of you are experiencing difficulties integrating the STM32 extension into the DevContainer environment. Specifically, the extension is not functioning correctly due to a dependency issue message displayed in VSCode. This problem arises from an extension installation issue within VSCode. Issue and fix When installing an extension and creating a DevContainer the extension is not automatically installed /imported to the DevContainerTo add the needed extensions, you need to click on the cloud icon and select the extensions to be added to the DevContainer.   Second issue after clicking on this icon, the install process on the DevContainer is not stable, sometimes you may need to relaunch the process twice or three times to have all your extensions installed. Third issue after adding all the needed extensions to the DevContainer, you may not be able to use them as VSCode is prioritizing the local installed one, so you must disable the lo

I have an axf file generated by vscode keil studio, then I followed follwoing tutorial to debug in vscode stm32cube ide.How to debug an external .elf file in VS Code | CommunityThen it triggers hard fault, and debugger shows `SystemCoreClock` is not correctly initialized, when it enters into `main`, the value is initialized to `(uint32_t) -1`.If I terminate gdb and soft reset it in cube programmer, it works fine, it also works fine when I debug it in vscode keil studio. The project is a simple cubemx STM32F407 generated project, and enables serial wire debug, the code in main infinite loop is just two ITM_SendChar. Update:It only occurs in first time launch, if it enter hard fault then click reset target, it works fine, but data values of SystemCoreClock and uwTickFreq are still -1. 

Hi everyone,I am working with STM32H757 device and debugging from VS Code using st-link V3. how can i configure the SWO output, how can i see SWO output in vs code. in vs code complete project setup is done using STM32CubeIDE for vs code. 

As an embedded developer, I already have CMake, Ninja, and the GNU Arm Embedded Toolchain installed and properly configured in my system PATH. These are standard development tools that many of us manage ourselves.What frustrates me is that the STM32 VS Code extension seems to completely ignore the existing environment and immediately downloads its own copies of CMake, Ninja, and arm-none-eabi-gcc.Why?Why not first check whether compatible versions already exist on the system? If they do, use them. If they don't, then offer to download them. That seems like a much more reasonable approach.The current behavior feels like this: Ignore the system environment Ignore tools already installed by the user Download another copy of everything anyway The result is duplicated toolchains, wasted disk space, and less control over the development environment.I understand that bundling dependencies may simplify onboarding for beginners, but experienced developers should have the option to use their

Good morning everyone,If I explicitly set an array to a custom memory section, STM32CubeIDE for VSCode is unable to start a debug session, showing a an error popup with text: “bound doStepLoadImages Failed: Load failed”. I am using a NUCLEO-N657X0-Q board.This happens even if the section is linked to to the same memory region (and physical bank) where the the array would end up if left unspecified (linker script attached below).Example code:uint8_t img_buff[PICTURE_BUFFER_SIZE] __ALIGNED(16) __section(".image1");Examining the .map file, img_buff ends up at address 0x34006940, which is, correctly, in AXISRAM1. In this condition, debug doesn’t work.If I remove the __section(".image1")  part, the array is assigned (as expected) to section .bss.img_buff, ending up at address 0x340026b0, which is still in AXISRAM1, similarly to the other condition. Debug works as normal.The same issue arises if I place the array in AXISRAM2 (by assigning it to section .axisram2, cfr. linker script below). I

Hello,I'm sorry to bother again, but it seems there is another issue in the latest update of VSCode STM32IDE extension. While trying to Start Debugging with GDB Server (STM32Cube Debug STLink GDB Server v1.3.0), with launch.json as: "version": "0.2.0", "configurations": [ { "type": "stlinkgdbtarget", "request": "launch", "name": "STM32Cube: STM32 Launch ST-Link GDB Server", "origin": "snippet", "cwd": "${workspaceFolder}", "serverReset": "Connect under reset", "preBuild": "${command:st-stm32-ide-debug-launch.build}", "runEntry": "main", "imagesAndSymbols": [ { "imageFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}" } ], "faultUnalignedAccess": false, "liveWatch": { "enabled": true, "samplesPerSecond": "4" }, "preRunCommands": [ "set output 16" ] } ] } The Debug starts and I get an error message as:PARSE ERROR: Argument: -cp (--stm32cubeprogrammer-path) Argument already set! Brief USAGE: C:/Users/.../AppData/Local/stm3

Device: NUCLEO-N657X0-Q Board Environment: STM32CubeIDE for Visual Studio Code Extension (v3.9.0) Description & Symptoms: The debugger loses a connection with the board with “Target not responding” and “Unable to read memory” errors.  Reverting to version v3.8.0 of the extension and all of its dependencies resolves the issue. Steps to Reproduce:Set a breakpoint on the first line of the FSBL Reset_HandlerRun the debuggerStep past the following line in the Reset_Handler: mov sp, r0 Expected Behavior: Debugger is able to continue stepping through the code Actual Behavior: The device stops responding and is unable to reconnect until unplugging and plugging back in Other Notes: When running the debugger without a breakpoint set, the program runs normally.  As soon as a breakpoint is set, it loses the connection.

I've seen the other post, but my issue is different. I'm now getting:Rolling back doesn't seem to be fixing this issue, even though nothing about my setup has changed since 2 weeks ago.I can't even figure out if it's the update causing this issue thanks to this utterly useless update information:Spoiler (Highlight to read)Breaking ChangesComplete architecture redesign: The tool architecture has been split into three major building blocks with the purpose of creating a flexible, maintainable and updatable platform consisting of the following blocks: GUI, CLI tools and STM32 device support.Breaking ChangesComplete architecture redesign: The tool architecture has been split into three major building blocks with the purpose of creating a flexible, maintainable and updatable platform consisting of the following blocks: GUI, CLI tools and STM32 device support.What changed?!How am I supposed to update my 3.8 configs to 3.9?

As the title says, the most recent 1.3.0 version of the extension breaks functionality of the debugger for the STM32G473CET3 MCU (and possibly others). By "breaks functionality", I mean that it does not even connect to the MCU anymore.

.clangd is constantly being modified appending the same compileflags: CompileFlags: Add: - '-ferror-limit=0' - '-Wno-implicit-int' CompilationDatabase: CM7/build Diagnostics: Suppress: - unused-includes - unknown_typename - unknown_typename_suggest - typename_requires_specqual If: PathMatch: CM7/.* --- CompileFlags: Add: - '-ferror-limit=0' - '-Wno-implicit-int' CompilationDatabase: CM4/build Diagnostics: Suppress: - unused-includes - unknown_typename - unknown_typename_suggest - typename_requires_specqual If: PathMatch: CM4/.* --- CompileFlags: Add: - '-ferror-limit=0' - '-Wno-implicit-int' CompilationDatabase: CM4/build Diagnostics: Suppress: - unused-includes - unknown_typename - unknown_typename_suggest - typename_requires_specqual If: PathMatch: CM4/.* --- CompileFlags: Add: - '-ferror-limit=0' - '-Wno-implicit-int' CompilationDatabase: CM7/build Diagnostics: Suppress: - unused-includes - unknown_typename - unknown_typename_suggest

I just spent some time trying to get a debug session going in VSCode ony to be given the rather obscure error message: "bound doStepConnectToTarget Failed: could not connect (error 138): The system tried to join a drive to a directory on a joined drive."Eventually I realised what it was - I had enabled RDP protection on the device (STM32C5) so of course it could not connect.May I suggest that a more appropriate error message is given in such circumstances? (this is with stlink gdb debugger, latest version.)

Hello, I'm trying to convert a project to vscode the first error I incurred to was this one: I'm trying to convert to cmake using the extension a project for the STM32U585OIYXQ, when I load the source folder and set the output folder then i push on convert and this is the output that I get :   [Error] [ide-project-convert]:Generating project... [Error] [ide-project-convert]:The specified 'STM32U585OIYxQ' device is unknown [Error] [ide-project-convert]: Project conversion failed with exit code: 35. Which has been solved with this work around: "you can enable the stm32cube-ide-project-manager.conversion.ignoreMissingDevice VS Code setting".That went through and I have the following new error: [Info] [project-manager] STM32CubeIDE project manager activation.... [Info] [ide-project-convert] Starting project conversion... [Info] [ide-project-convert] cube wrapper version: 0.10.2 [Info] [ide-project-convert] Invoking STM32CubeIDE Eclipse exporter... [Info] [ide-proje

 I noticed the following in the recent post announcing STM32CubeIDE for Visual Studio Code 3.8.0:CLI tools: A new bundle manager is enabling VS Code to download required CLI tools. This replaces the all-in-one STM32CubeCLT package. ...Now that STM32CubeCLT is no longer required by the VSCode integration, what is the future of STM32CubeCLT?  In particular, will it continue to be updated and supported?

Hi,I have a system with 11 STM32 in a single JTAG chain. I’m trying to debug device with JTAG address 10,45 (JTAG device position 10, IR -pre-length of 45) and I’m getting this error message when running my launch configuration:This is my entry in launch.json, my probe is a J-link:{            "type": "jlinkgdbtarget",            "request": "launch",            "name": "JTAG Launch Dev 10",            "origin": "snippet",            "cwd": "${workspaceFolder}",            "preBuild": "${command:st-stm32-ide-debug-launch.build}",            "runEntry": "main",            "serverInterface": "JTAG",            "serverJtagCfg": "45,10",            "imagesAndSymbols": [                {                    "imageFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}"                }                            ]        }, Debugging device 0,0 on the same chain works (has similar firmware written on STM32Cube extension for VSCode) from STM32CubeIDE extension for VS

I am reporting a specific behavior in GDB where the standard hook-stop is completely bypassed if a next (Step Over (F10)) or step (Step Into (F11)) command is interrupted by a software breakpoint instruction (BKPT) embedded within a macro.Environment:Target: STM32L475VGT (ST-Link)GDB Version: GNU gdb (GNU Tools for STM32 14.3.rel1.20251027-0700) 15.2.90.20241229-gitIDE: STM32CubeIDE for VSCode v3.9.0Steps to Reproduce:1. Define a macro in C that includes a software breakpoint instruction:#include "cmsis_gcc.h" #define DEBUGGER_ATTACHED() ((CoreDebug->DHCSR & CoreDebug_DHCSR_C_DEBUGEN_Msk) != 0) #define BREAKPOINT(arg) \ do { \ if (DEBUGGER_ATTACHED()) { \ __BKPT(arg); \ __NOP(); /* NOP to prevent the debugger from immediately stepping to the next line. */ \ } \ } while (0) int main() { int a = 0; // Click: Continue (F5) BREAKPOINT(0x01); // Click: Step Over (F10) which works correctly a++; // Click: Step Over (F10) again which works corr

I have multiple STLinks on multiple Nucleo boards.  I can debug only if I connect one at a time, but it is tedious to connect and reconnect to switch boards. When I plug in multiple devices I see them listed (bottom left) but I can’t work out how to select a specific STLink to use.  If I try to debug it fails with a “bound doStepConnectToTarget Failed: could not connect: Operation timed out.” and suggests I open launch.json.Disconnecting the cables is additionally tedious because I’m using the VCP on each, and disconnecting breaks the connection to the terminals, which then all need to be reconnected.I know that with the stand-alone STM32CubeIDE it possible to have separate configurations for each STLink (defined by Serial ID) and then I select the one to use as needed, without having to disconnect any hardware (and the VCPs for the devices I’m not debugging stay connected).Is there a way to specify the STLink serial ID to use in the launch.json file?  In VSCode I notice there is a but

Hello,I've been working with the new VS Code extensions for several weeks, and debugging feels quite unstable. I'm using a j-Link Plus. At random times, I suddenly can't debug anymore, everything seems to freeze, and in the Debug Console I see something like this:The number (6760 here) increases by hundreds per second and will never stop. Every time such a random debug freeze happens, I see this last line with the counting number box, always reading 4 bytes somewhere (different addresses), as if some read action hangs in an endless loop. Only way to get it working again is by closing the whole debug session and starting anew.Sometimes I can debug for an hour without this issue, sometimes I get this every few minutes. It's not related to some code position, happens in different debug configurations (flash / attach to running), happens in different projects, with different (or no) watched variables, on different PCBs, with different cables to the debug probe, with different clang op

I’m using the pre-release STM32Cube for Visual Studio Code (v3.5.1).After importing a project that was originally generated by STM32CubeMX with the “cmake” toolchain selected, the .vscode folder is created but contains neither tasks.json nor launch.json.When I try to add tasks.json manually, the command palette no longer offers the usual templates such as “STM32: CubeProg: Flash project (SWD)”.Could you confirm whether this is a regression in 3.5.1?If an immediate fix isn’t possible, would you mind sharing the correct tasks.json and launch.json snippets so I can paste them in by hand? Test conducted on July 28, 2025, testing platform Ubuntu 22.04+vscode(v1.102.2)+pre-release STM32Cube for Visual Studio Code (v3.5.1), test target STM32G474RET6.

Hi!I have set up a project for the STM32H523RET6 using the following setup:CubeMX: 6.15.0STM32 vscode extension: 3.5.1The project is configured to use starm-clang and starm-clang++ and the STARM_PICOLIBC toolchainI have created a .cpp file () that i added to my build and updated my CMakeLists.txt with the following: # Setup compiler settings set(CMAKE_CXX_STANDARD 23) set(CMAKE_CXX_STANDARD_REQUIRED ON) set(CMAKE_CXX_EXTENSIONS ON) ... enable_language(C CXX ASM) ... # Add sources to executable target_sources(${CMAKE_PROJECT_NAME} PRIVATE Core/Src/myclass.cpp # Add user sources here ) When building the project, it compiles fine, but clangd reports the following problem: nsupported option '-mcpu=' for target 'x86_64-pc-windows-msvc'clang(drv_unsupported_opt_for_target) Unsupported option '-mfpu=' for target 'x86_64-pc-windows-msvc'clang(drv_unsupported_opt_for_target) Unsupported option '-mfloat-abi=' for target 'x86_64-pc-windows-msvc'clang(drv_unsupported_opt_for_t

Hello,When I try to import the sample project “OEMiROT_Boot”, I get exit code 255. Error:2026-05-20 15:46:46.511 [Error] [ide-project-convert] ENOENT: no such file or directory, copyfile 'C:\Users\devst\STM32Cube\Repository\STM32Cube_FW_H7RS_V1.3.0\Projects\NUCLEO-H7S3L8\Applications\ROT\OEMiROT_Boot\STM32CubeIDE\utput.ld' -> 'd:\Projekte\Test\test\NUCLEO-H7S3L8_OEMiROT_Boot\utput.ld'2026-05-20 15:46:46.567 [Error]  [ide-project-convert]: Project conversion failed with exit code: 255.It must also be possible to convert projects with multiple contexts and multi-core support, This must be made a priority

Hello, I wrote a project maybe 2 weeks ago, at that time, everything was ok.  then i used stlink to download and debug the code yesterday, at first time, it worked ok, but later, i did download and debug again with stlink. it cannot work. the log as below.my setting as below:so what is the problem? how to fix it?thanks. 

The gui seems to not have support for viewing adding or changing watchpoints for what i can find. I am able to use watchpoints using the debug console.">watch address"however it would be nice if that would also be visualized just like breakpoints. STM32CubeIDE for Visual Studio Code: Version 3.9.0 here my launch.json file:{"type": "stlinkgdbtarget","request": "launch","name": "CM7 master STM32Cube: Launch ST-Link GDB Server","origin": "snippet","cwd": "${workspaceFolder}/XXX/","deviceName": "STM32H747BIT6","deviceCore": "Cortex-M7","serverSerialNumber": "XXX","serverInterface": "SWD","serverInterfaceFrequency": "21000","serverReset": "None","preRunCommands": ["set output 16"],"program": "${workspaceFolder}/XXX/CM7/Debug/XXX.elf","imagesAndSymbols": [{"symbolFileName": "${workspaceFolder}/XXX/CM7/Debug/XXX.elf",}],"liveWatch": {"enabled": true,"samplesPerSecond": "4"},"serverExtLoader": [{"loader": "${workspaceFolder}/XXX/CM7_ext_flash_ldr/XXX.stldr","initialize": fals

Hello, I am trying to import the RTSP example for the NUCLEO-N657X0-Q. It is not appearing in the IDE as a choice, but I see the project in D:\STM32\STM32Cube_FW_N6_V1.3.0\Projects\STM32N6570-DK\Applications\VENC\VENC_RTSP_Server 

If I add a new .c file to my project in core/src it does not get recognized and is not complled. How do I get it into the make list?Thanks