STM32CubeIDE for Visual Studio Code (MCUs)

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 

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

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

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

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.)

Hi,I’m trying to use VSCode extensions but i find it hard to understand and debug my workflow constantly. When i want to create new project i first generate code scaffold in CubeMX. Then i use VSCode extension to configure the project, then i try to build or flash my project to the board and im met with huge amount of errors with cmake, toolchains etc. I Think im missing something here becouse it’s impossbile to work like that. If you have any ideas what am i doing wrong please leave your suggestions. Id be happy to provide any additional details too.

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?

I have a complex product where I am running multiple micros with firmware that needs to be debugged. I have 2 stlinks plugged in. But I am stumped at trying to get the VSCode STM32 extensions to target a specific stlink. My launch.json is using stlinkgdbtarget as the debug type."serverArgs" is where I have tried ["-i","<stlinkserial>"] but the debug session launches and in the debug output it prints multiple stlink devices detected, so the session fails. Is there a way to debug if the serverArgs are even being used?Is there a different way to select a stlink?

Hi, My projet has been working fine until the last week or so where I can no longer debug. When I press F5 I get a "Missing CMSIS_PACK_ROOT" with a notification toast message of "gdb is not running".Nothing has changed in terms of project settings, launch.json, etc. as far as I'm aware. All STM32 extensions and packs are the latest (these might have updated recently - i've tried older versions as a test but that didn't help).Target device is STM32C562.Using ST-Link GDB Server.Windows 11 OSHere is the log of "STM32Cube core" at startup.2026-05-13 08:23:08.715 [Info] Adding STM32Cube CLI path to environment: c:\Users\ZZZ\.vscode\extensions\stmicroelectronics.stm32cube-ide-core-1.3.0-win32-x64\resources\binaries\win32\x86_64 2026-05-13 08:23:09.984 [Info] Configuring CUBE_BUNDLE_PATH environment: C:\Users\ZZZ\AppData\Local\stm32cube\bundles 2026-05-13 08:23:09.985 [Info] NODE_EXTRA_CA_CERTS is not set 2026-05-13 08:23:10.369 [Info] CMSIS_PACK_ROOT=C:\Users\ZZZ\AppData\Local\stm32cube

Hello, I'm using a NUCLEO-C5A3ZG. Not sure it's the right place to write but my goal is to setup the debugger using the STM32CubeCLT_1.21.0 Package under a VSCode environment (already using cortex-debug extension for other projects).I am able to reach the target using the embedded stlink for example with a reading of the flash : /c/Program Files (x86)/ST/STM32CubeCLT_1.21.0/STM32CubeProgrammer $ ./bin/STM32_Programmer_CLI.exe -c port=SWD freq=1000 mode=UR -r32 0x08000000 10 ------------------------------------------------------------------- STM32CubeProgrammer v2.22.0 ------------------------------------------------------------------- ST-LINK SN : 005100353235511237333439 ST-LINK FW : V3J17M10 Board : NUCLEO-C5A3ZG Voltage : 3.29V SWD freq : 1000 KHz Connect mode: Under Reset Reset mode : Hardware reset Device ID : 0x45A Revision ID : Rev Z Device name : STM32C59x/5A3 NVM size : 1 MBytes Device type : MCU Device CPU : Cortex-M33 BL Version : 0x100 Debug in Low Power mode enabl

Hello Team,  Since SCB and other core registers are not included in the SVD file for STM32H5, could you please advise on the best way to access or monitor SCB registers (e.g., VTOR, AIRCR, ICSR) during debugging in VS Code with PlatformIO? Specifically, I'm looking for guidance on: How to inspect SCB register values during a debug session (e.g., trap cause, exception entry). Recommended approach to capture trap/exception information like: HardFault status (HFSR) Configurable Fault Status (CFSR) Bus Fault (BFAR) MemManage Fault (MMFAR) Any suggestions for manual mapping or watch expressions in the debugger that would allow me to monitor these registers, since they’re not shown in the peripheral view. Any tips or best practices for bare-metal Cortex-M33 debugging without full SVD support would be greatly appreciated. Best regards,Manikanta 

My situation:Trying to step through/debug a project that will run from the QSPI on the STM32H750B-DK in VS Code (on linux, if that matters). In order to test out the toolchain, I've started with two (separate) workspaces: on has the ExtMem_Boot project, the other the LTDC_Paint demo.What works:A/ Building both projectsB/ Flashing (via tasks.json and STM32CubeProgrammer) the ExtMem_Boot projectC/ Debugging the ExtMem_Boot project via the VS Code debug viewD/ Flashing (via tasks.json, STM32CubeProgrammer and the ExtLoader MT25TL01G_STM32H750B-DISCO.stldr) the LTDC_Paint demo.E/ Launching the debug flow of LTDC_Paint (after modifying launch.json to include the serverExtLoader)What fails:The debugging automatically halts at the Reset_Handler of the startup file, the instruction for loading the stack pointer. But at this point I can't seem to step through it. Even just pressing the run arrow seems to result in a crash, rather than the actual execution.What I find suspicious:The debug consol

There does not seem to be any way of viewing a debug variable in hex.The closest workaround is to prefix (void*) before the expression in the watch window. This is no good for viewing an array of hex digits like for example a CAN bus message.

General The stm32-vscode-extension extension for Visual Studio Code is designed to enhance the development experience for STM32 microcontrollers by providing a comprehensive and updatable set of tools. The extension pack allow users to install one single pack bringing a full STM32 IDE experience into VS Code. Breaking Changes Complete 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. GUI: The platform's single extension has been transformed into an extension pack, offering a more modular, updatable and flexible setup. CLI tools: A new bundle manager is enabling VS Code to download required CLI tools. This replaces the all-in-one STM32CubeCLT package. The bundle manager will provide developers flexibility, updatability and

Hi all,What is the recommended way to not crush our repository and dynamically pull/generate the project's Drivers and Middleware folders?  For instance, our repository has both Bootloader + Application code projects in a repo (and other MCU projects/layouts for the same board).Is there something similar to Platform.IO (or C#'s NuGet packages) where the platform maintains those 3rd-party files in a volatile location and pulls them if they don't exist on your machine? Especially for the sake of not checking into the repo duplication of +15 MB worth of files for each project.Please excuse me if this was already asked. I didn't quite find a solid answer.I'm ok with making a command line script that auto-pulls them too, if that's a possibility.

I'm trying to install the ST-Link USB Drivers following the instructions here. However, the STM32Cube Resources section does not include ST-Link USB Drivers.I'm running the latest versions on VS Code and STM32CodeIDE extension. 

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.

Hi, the extension version is 3.8.0, and it usually takes 5min to load, is that normal? Also, is there any CDN or dedicated server for Chinese users? cuz it's troublesome to download those bundles here. Thx

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.