STM32CubeIDE for Visual Studio Code (MCUs)

Hi all,I've been in the process of switching from the GNU toolchain (which is working alright) to the ST-provided clang but I am having difficulties with the mentioned extension.The following has two links to two different branches of the same repository. First one uses GNU toolchain, and the other uses starm-clang:https://github.com/anttikes/usb-fm-radio/tree/mainhttps://github.com/anttikes/usb-fm-radio/tree/swap-to-clangdThe project can be built in both branches, and works correctly with the first but the latter one has a rather interesting problem with clangd. After configuring and building if you open e.g. "Core/Src/i2s.c" you can see an error message at the very beginning:"Unsupported option '-mcpu=' for target 'x86_64-pc-windows-msvc'".It seems as-if the cross-compilation settings for the clangd program are not set at all. For some reason it belives we are building for the host architecture.There is also a second problem with clangd, but it is related to the STM32CubeF0 repositor

Hello, Microsoft has updated their Visual Studio Marketplace Terms of Use to bar vscode forks from using extensions from their marketplace. I'm currently using the Cursor IDE, which has recently switched over to open-vsx.org for their extension marketplace and thus, I no longer have access to STM32 for Visual Studio Code extensions.Are there any plans to cross-publish the official STM32 for Visual Studio Code extension over to open-vsx.org?

Hello,With the latest release of the extension (3.6.4), the pre-release version (based on bundle manager) was moved to be the official release, thus making CLT obsolete.My original launch file (based on CLT) does not work anymore, it included a Debug script, an Attach script, and a build+flash-only script.To create a compatible launch file, I used the preset script - "STM32Cube: STM32 Launch ST-Link GDB Server" by using vscode's "create a launch.json file" option.This does work for debugging, but creates a few issues-a. Doe's not contain an "Attach" option - I could not find any help on the options for configuring the "stlinkgdbtarget" script type.b. The "Memory Inspector" which is part of the extension pack, does not work anymore with the generated launch file. I get a "No debugger attached" while debugging.c. The vscode reset debug button does not reset the core anymore - it re-flashes the device. Can anyone help me create a launch file that will contain these features based on

Linux VM 6.17.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct 18 10:10:29 UTC 2025 x86_64 GNU/Linuxvscode 1.106.3Only the ST plugin package is installed, without the Microsoft C++ plugin or clangd. The formatting function is not working properly. The attachment is the result formatted using the Microsoft C++ plugin (only the Microsoft plugin) on Windows.

It seems that the default map file is set to "folder name.map".How can I change this file name and path?I can see the analyzed view when I run "Open memories analysis" menu from the map file by force. 

Hi,The new STM32Cube for Visual Studio Code looks really nice but it suffers from (at least one) serious flaw: it does not work correctly when the target project is in a sub-folder.This means every "multi-project repository" in the world just flat out doesn't work. Especially mine, where the repository contains not only the schematic but also the firmware and a GUI application.I have attached a sample ZIP to this post which exhibits the issue. Extract both subfolders to a blank directoryIf you open "advanced-sample-cmake" from the root, everything worksIf you open "Subfolder" from the root then everything falls apartIrony is that "Subfolder" contains the exactly same files than the other. The "STM32Cube CMake build" extension says "Could not configure code indexing until an active project is set" and stops right there.Note that I can (somewhat) work around this issue by cloning my repository and then opening the subfolder in VS Code:The "git" extension really does not like this, a

When using Zephyr, commands like west debug require ST tools (e.g. ST-LINK_gdbserver) to be installed and available on the PATH. I believe this currently requires STM32CubeCLT to be installed. However, I'd like to avoid installing STM32CubeCLT since it's deprecated in favor of the new bundle manager that is installed with the VS Code extension.I'd like to request the ability to install & use the bundle manager by itself (outside of the VS Code environment) to install packages like stlink-gdbserver into a custom location on my machine. The goal would be to add these tools to my path for development. I'd also like to be able to use the bundle manager to install tools into a CI environment (e.g. for use in GitHub actions).Note: this question is similar to https://community.st.com/t5/stm32cubeide-for-visual-studio/cli-tools-of-new-stm32cube-for-visual-studio-code-extension/m-p/831932/highlight/true#M1028 however the accepted solution in that answer requires ins

I noticed that running cube-cmake --version reports cmake version 4.0.1, but running the actual build commands with cmake 4.0.1 produces a different binary than when running with cube-cmake.Is it safe to build a binary for release using cmake instead of cube-cmake? My program seems to run just fine building with cmake but I am curious what the difference between the two is.

Hello,I created a project with an older version of the extension (v2.0.0) and everything worked fine. After coming back to it some time later, I found that I’m no longer able to run the code.I’m not sure if this is an issue with my setup or a more general problem, but I can’t select my MCU (STM32C071KBUx) in the VS Code extension’s project setup.When I manually set the deviceName property in launch.json I get an error:Is anyone else experiencing a similar issue?Thanks for any help!

Hi, I'm trying to come up to speed with the VSCode workflow, coming from experience so far only using CubeIDE.  In CubeIDE, it seems that I was encouraged to think of having a "workspace", in which several projects co-existed. I enjoyed the ability to be able to have multiple projects "open" at once, to be able to compare code and easily understand/navigate to out-of-project source code, like centralized libraries and such. The VScode workflow, in contrast, seems to want me to only open a single project at once, otherwise CMake seems to get crabby. This is slightly annoying in that it requires me to open multiple windows in order to see multiple projects simultaneously, but notably more annoying when I am trying to use out-of-project code - I need to open a second window at a higher directory level, but can't actually build anything in this second window. It's kind of cluttered and confusing. It also seems to kind of push me away from the path of having a git repo t

I used the STM32CUBE FOR VSCODE preview version and enabled FreeRTOS in STM32CUBEMX. However, during the debugging process, the STM32CUBE RTOS STATE is empty and does not display any content, even when the program is paused.  

I want to change the selected toolchain for a project by clicking on "Setup STM32Cube project(s)" and selecting the desired toolchain and clicking save.I want to change from clang to gcc to test a few things.It keeps using the old toolchain (clang). Even if I delete the build folder.If I delete CMakePresets.json I get an error that the project requires a preset.If I modify CMakePresets.json I get the following warning message when building:[cmake] Manually-specified variables were not used by the project:[cmake] [cmake] CMAKE_TOOLCHAIN_FILE [cmake]In STM32CubeMX the toolchain option is greyed out.What's the proper way to change the tool chain?

Hello, My usual workflow is to fire devcontainers with everything I need in order to have the right tools in every development computer used by the team.What I notice with the vscode for stm32 is that now it is harded to pack the tools prior to using the containers.Configuring the installed extension is not enough because then when the container runs, every st extension downloads a lot of data from the network.Working with a lot of containers and in a huge team does not scale well because everytime a devcontaner is opened more that 2GB of data are downloaded and unpacked.This is a waste of network, disk, time resource that could be better used. There is a way for having the tools packed in a devcontainer? They are the future of reproducible builds and sharing configuration between programmers. thank you in advanceAndrea

I get a Unhandled: on_readmemory_request not available in PyDevJsonCommandProcessor. error while debugging other python projects. This issue gets resolved when I disable the STM32Cub for Visual Studio Code Core extension and its related extensions.To reproduce: Open an existing python project or package (workspace)Launch the debug session. It tries to start the session and in a few seconds throws this error and stops the debugger.Unhandled: on_readmemory_request not available in PyDevJsonCommandProcessor.Please see https://github.com/microsoft/vscode/issues/249341#issuecomment-3064965337 

Hi, I've mostly come up to speed with the STM32 environment by way of CubeIDE (with integrated MX, prior to the recent 2.0 switch). With this most recent update, it seems like the forward-looking direction is to migrate to VScode.So, I tried that - I installed the extension and all its associated extension pack siblings. I can see the ST logo on the left of the pane, with a clock icon on it that doesn't seem to ever go away. Clicking on it reveals three panels, with clickable buttons. The top two - launching cubeMX or Finder - seem to work (albeit with a bit of a lag), but nothing in the Cube Resources pane seems to work, everything gives an error like:command 'stm32cube-ide-core.command.open-user-guide' not foundAnd there are these moving blue lines above each pane that seem to suggest something is happening int he background, but after a half hour of sitting, they don't go away. Basically, I'm fairly confused how I'm meant to be interacting with this, and how to make the leap fr

Changelog Version 2.0.0 V2.0.0 implies a breaking change: CMake project generation has been moved from VS Code to STM32CubeMX v6.11.0 (and later). VS Code solution no longer has dependency on STM32CubeIDE (.cproject-files) VS Code solution no longer relies on STM32CubeIDE provided toolchains and debugger tools VS Code solution no longer has dependency on vcpkg, Added support to import STM32CubeMX v6.11.0 CMake projects and bootstrap edit/compile/debug in VS Code Added support to create empty projects Depends on STM32CubeCLT v1.15.0 for empty project creation, build and debug tools Documentation update: The User Guide has increased coverage Better OS platform support   https://marketplace.visualstudio.com/items?itemName=stmicroelectronics.stm32-vscode-extension

Hello,I have a small problem here. When I run a clean in git, the directories .vscode, .settings, and build are deleted. If the project needs to be rebuilt, the Setup STM32Cude project function has to be executed manually, and the board/device has to be specified manually again. This is very error-prone. Is there a way to start this project setup from CMake or from CMakePresets.json?For example, if no compiler was found?In CMake, the correct settings are already known.

I have problem that most headers are not visible so a lot of dependent problems occured.All files are present - the same project compoiled in STM32CubeIDE works.There is note that "clang(pp_file_not_found)"Tried to add paths in CMakeLists.txt but no luck.

Hi,I'm trying to set launch.json to use SWO. I can do it with cortex-debug, but what about the stlinkgdbtarget?{ // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "stlinkgdbtarget", "request": "launch", "name": "STM32Cube: STM32 Launch ST-Link GDB Server", "origin": "snippet", "cwd": "${workspaceFolder}", "preBuild": "${command:st-stm32-ide-debug-launch.build}", "runEntry": "main", "imagesAndSymbols": [ { "imageFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}" } ], "swoConfig": { "enabled": true, "cpuFrequency": 170000000, "swoFrequency": 2000000, "source": "probe", "decoders": [ { "label": "ITM Port 0", "type": "console", "port": 0, "encoding": "ascii" } ] }, } ] } But it shows syntax error:"Property swoConfig is not a

Hi,I have a toubles with a debuging my program.I started from the begining... so I create a empty project in VSCode for this MCU (setup is CLANG only). I build the empty program. It has 702 B. Debuging is working at this point.But after create a "data" in flash with this code: #include <stdint.h> #include <sys/cdefs.h> #define TARGET_FLASH_SIZE_B (64*1024) extern const uint8_t size_filler[TARGET_FLASH_SIZE_B]; void __attribute__((noinline)) force_data_use(void) { volatile const uint8_t *ptr = size_filler; uint8_t dummy = ptr[0]; } const uint8_t size_filler[TARGET_FLASH_SIZE_B] = { [0] = 0xAA, [TARGET_FLASH_SIZE_B - 1] = 0x55 }; int main(void) { /* Loop forever */ force_data_use(); for(;;); }​Debug can't be launched... But if you replace line 4 with:#define TARGET_FLASH_SIZE_B (63*1024)it works... So I think there is some problem with flash size erasing / flashing. The MCU has 2 kB per page and two banks. Here is DEBUG CONSOLE: STMicroe

Hi all,This is my first time posting here.I have a problem with STM32 VSCode Extension v3.5.1 where the DMA on my STM32 H7 (STM32H725RGV6) doesnt work.I tested this with UART TX and ADC Circular DMA mode.The function HAL_UART_Transmit_DMA() returns HAL_OK at first, and then returns HAL_BUSY for the next calls. No data was transmitted at all recieved on the serial terminal.  UART and DMA blocking functions and with IT works fine.The same setup with CubeIDE and with the older extension v2.5.1 works fine. Any input is greatly appreciated.Many thanks Steps to replicate:Start a new stm32 vscode project with STM32H7 like normal and enable uart1 (with all interrupts) and sw debug, max clock 550MHz with HSI.call HAL_UART_Transmit_DMA() and it doesnt work :)Here is my full main.c code though:/* USER CODE BEGIN Header */ /** ****************************************************************************** * @file : main.c * @brief : Main program body **************

During a debugging session, when `tx_thread_create` is called with a "big" stack size (1024*10 for example) and the "serverRtos" is enabled, the debugger is disconnected with an error: "Remote communication error. Target disconnected: No error." Here the debug console logs (full log attached): Spoiler (Highlight to read)To client: {"seq":0,"type":"event","event":"output","body":{"category":"proxy","output":"RTOS proxy: Lost connection to GDB Server\r\n"}}RTOS proxy: Lost connection to GDB ServerTo client: {"seq":0,"type":"event","event":"output","body":{"category":"stdout","output":"{\"label\":\"\",\"value\":[{\"label\":\"Driver\",\"value\":\"ThreadX\"},{\"label\":\"Kernel state\",\"value\":\"Not started\"}]}\n"}}{"label":"","value":[{"label":"Driver","value":"ThreadX"},{"label":"Kernel state","value":"Not started"}]}GDB result: 36 doneTo client: {"seq":0,"type":"response","request_seq":25,"command":"cdt-gdb-tests/executeCommand","success":true,"body":{"status":"Ok","result":

Currently, STM32Cube for Visual Studio Code introduces a new bundled package manager which replaces STM32CubeCLT.However, when developing STM32 projects with other IDEs (e.g. CLion), STM32CubeCLT is still required to provide the build environment.This leads to several problems when using multiple IDEs (VS Code + CLion):Separate installations of toolchains (STM32Cube for VS Code and STM32CubeCLT) consume extra disk space.STM32CubeCLT cannot be updated incrementally; users must download the whole package.STM32Cube for VS Code currently cannot manage STM32CubeCLT packages, leading to duplicated toolchain management.By default, tools are installed on C:\ drive, which is inconvenient for users with limited system disk space.Feature request:Allow STM32Cube for VS Code’s package manager to use and manage STM32CubeCLT packages.Benefits:Reduce disk usage by avoiding duplicated toolchains.Simplify updates and package management.Improve developer experience when using multiple IDEs (VS Code + CLi

Hi All,I have been working with the STM32H7R7 MCU for a while.  I used the getting started manual of the application notes for Eclipse, but I could not set up the right debug environment for the STM32H7R7 deviceI used the cubemx to generate the boot, appli and ext memory. I used exactly the same ioc file (except the setting of the cmake vs cubeide), however I could not flash and debug the device without the right json file.I tried to build by myself, but I was not lucky enough to be succesfull. Also I have not found any examples on the web.Could somebody help me with a json file, environment for debug and flashing? Thank you very much in advance

Hi,I'm trying to move towards developing in VSCode to not rely on VMs for the IDE. While code generation via CubeMX and flashing the device works as expected, I'm having issues trying to use the debugger on my STM32H747 DISCO board.When using the latest (v3.6.4) It kept prompting command not found error.Downgrading it to v2.1.1 seems to fix the issue and the debugger manages to run. However, it seems to always timed out waiting for the other core (CM4) to enters in stop mode. p.s. I am trying to debug the CM7 at the moment.Is there something that needs to be done on the STLink server or .ioc file to make the debugger works? Any help will be be much appreciated