STM32CubeIDE for Visual Studio Code (MCUs)

I'm new to using VS Code extensions and I'm quite impressed so far. However, I've hit a snag trying to change the build preset (like switching between Debug and Release modes).The first time I built my project, VS Code prompted me to choose a build type (as shown in the screenshot below). I made my selection, but now I can't find any way to change it. I've looked through the menus, settings, and documentation, but I'm coming up empty.Does anyone know how to change the build preset after the initial selection? Any help would be appreciated.Thanks in advance.

Good afternoon, I'm using Ubuntu 24.04 and whenever I start vs code while stm32cubeclt is installed then my path is filled with paths to stm32cubeclt and it's different tools. I don't have any ST related extensions. - How do I stop stm32cubeclt from prepending my path with itself?- When does this happen?- Is it only with vs code or other software as well?- Is there any other solution which allows programming stm32 MCU's using cli?If this is intended behaviour I hope it will be changed in the future. I don't know how to remove it because whenever I start vs code again it's back and I have no idea where it's being set since I can't find it in any typical configuration file like .bashrc, .profile or similar. I don't know what to do except changing all my other settings or remove cubeclt altogether.

Hi,I generated the code in CubeMX and opened it in VSCode. However, I cannot run the code because VSCode cannot find main.h. I'm not sure why this is happening. I've generated the code twice, but the problem persists. The main.h file is located in the Core > Inc folder, and main.c is in the Core > Src folder. Does anyone know what might be causing this issue? Thanks! 

I have a project that was being developed using STM32CubeIDE, and being debugged with JLink Ultra.Since all my other client work is done using VSCode, I wanted to bring this CubeIDE project into VSCode.The only option I see in VSCode to do this is "Import CMake Project", I tried this, but it does not appear to work. The build and debug tasks appear to not be set up correctly.How is this supposed to be done.Using VSCode extension v2.1.1.Sid

I am testing a very simple OLED display using the SSD1306 driver and fonts, referring to the link below. However, the code does not compile successfully.Are there any possible reasons for this issue?/* USER CODE BEGIN Includes */ #include "fonts.h" #include "ssd1306.h" /* USER CODE END Includes */ /* USER CODE BEGIN 2 */ SSD1306_Init(); SSD1306_GotoXY (0,0); SSD1306_Puts ("MICROPETA", &Font_11x18, 1); SSD1306_GotoXY (0, 30); SSD1306_Puts ("BY NIZAR", &Font_11x18, 1); SSD1306_UpdateScreen(); HAL_Delay (1000); SSD1306_ScrollRight(0,7); HAL_Delay(3000); SSD1306_ScrollLeft(0,7); HAL_Delay(3000); SSD1306_Stopscroll(); SSD1306_Clear(); int num=2024; char snum[5]; SSD1306_GotoXY (30,20); itoa(num, snum, 10); SSD1306_Puts (snum, &Font_16x26, 1); SSD1306_UpdateScreen(); //SSD1306_DrawLine(POINT1 X, POINT1 Y, POINT2 X, POINT2 Y, 1); SSD1306_DrawLine(1,54,126,54,1); SSD1306_UpdateScreen(); HAL_Delay (5000); SSD1306_Clear(); // For Rectangle, we need to use two corner points // SSD

Hi,Since a recent upgrade to STM32CubeIDE I am getting the following error when importing variables into STM Studio:Wrong version in compilation unit header (is 5 should be 2, 3, or 4)This is preventing me from debugging my system.  I tried using STM32CubeMonitor, but the charting is so rudimentary it is useless.I am assuming that the upgrade to the IDE incorporated a later version of GCC and it is this that is producing elf files in that have a CU header of 5.Is there any simple work-around that anyone knows of?I could go back to a later version of the IDE, but once you get on that merry-go-round you end up with a big mess, because inevitably something else will break.I know you can also enter the variables and their addresses into Studio manually and that's OK for small numbers of variables, but when you use structures to store different types calculating the offsets to the fields is tedious and error prone.  As I recall if the addresses of the variables changed after progr

Hello, Can someone advise me for a "blueprint" how to set up C++ in VS Code for stm32 mcu, I've changed Cmakelists.txt to be able to compile C++ and I am not getting an error at Cmakelists.txt, but I am still getting errors from undefined macros. I sense that it is related to IntelliSense and I've set all include paths in properties.json and stil it doesn't recognize some macros from different libraries. I just wanted to ask you if you know certain procedure for any type of project involving setting up C++ for STM32 in VS code.Thanks in advance  

Can you please add prebuilt OpenOCD to CLT package (at least for Windows)? Currently we have to extract prebuilt binaries from CubeIDE and integrate them into Windows (system env path and script bundle)

Am using the dual core STM32H747. A simple project in VScode from STMcubeMX built for CMAKE builds fine but intellisense bad. Becomes confused about which main.h, the one under CM4 or CM7. Have not been able to set up include path to make sense of this. You would think the output from STMcubeMX would work unmodified, but it does not. Could really use some help here.

When working in remote connections, such as WSL or docker the STM32 extension can not be activated with the following error:"Cannot activate the 'STM32 VS Code Extension' extension because it depends on the 'C/C++ Extension Pack' extension, which is not loaded. Would you like to reload the window to load the extension?"But the C/C++ extension is loaded and working.Is there any Work Around available?

I am a happy VSCode developer using docker devcontainers to create an easily reproducible environment for development. I am struggling with a strange bug with the "STM32 VS Code Extension" (v2.0.1).If I try to access it, after opening the container, I get the following error:"Cannot activate the 'STM32 VS Code Extension' extension because it depends on the 'C/C++ Extension Pack' extension, which is not loaded. Would you like to reload the window to load the extension?"This is strange because the C/C++ Extension Pack is loaded and part of my dev container.I have the option to "Reload Window", but hitting it only results in a reload and the same message popping back up.Has anyone been able to use this vscode extension inside a devcontainer?

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

Hi there,Im currently evaluating moving from Keil uVison to VSCode. But im missing a NVIC view. Is there anything like this in VSCode?This is how it looks in uVision: https://developer.arm.com/documentation/101407/0541/Debugging/Debug-Windows-and-Dialogs/Core-Peripherals/Armv7-M-cores/Armv7-M--Nested-Vector-Interrupt-Controller?lang=en

Does ever ST intend to open-source it's vscode extension?I don't think it would serve any purpose to hold this project as close source as all the files are already minified version of original source code, so it would not serve any security/IP protection, and ST simply just loose the opportunity of help with other contributors. For years ST was preferred for their easy to use IDEs/toolchains compared to other competitors, but nowadays, seems ST does not care about this anymore. Using STM32CubeIDE is not optimal in best case scenario and just running super slow CubeMX code generator/Pin configurator is really time consuming. All these problems would be fixed instantly if ST moves to a better IDE instead of Eclipse and VSCode seems the best choice at this point of time. I don't think with the resources ST have, it would take more than 6 month to move all the functionality of STM32CubeIDE to VSCode including configuration/code generation and everything in CubeMX. 

"I have a project A that I haven't used for some time. During that period, I was using project B, which has been working fine. However, when I tried to use project A again, I was informed that its CMake configuration failed. Can you please tell me how to solve this issue?"（The image above is of project B.）（The image above is of project A.） 

Hi,I would like to enable FreeRTOS Thread awareness in VSCode. I know it worked in CubeIDE.I can do it with Jlink GDB Server by inserting this to launch.json"rtos":"FreeRTOS",         //Change it depending on RTOS usedBut have no idea how to do for ST-Link GDB serverAt least textually through the debug console.Any Idea?Thank you.

I already posted this question on stackexchange, but unfortunately no answers, so please don't me asking here again.I'm using the last flash page (page 31: 0x0800 F800 - 0x0800 FFFF2) as eeprom emulation area on my STM32G030C8.I'm working with VScode and programming + debugging the flash with JLink over USB.Is there a way to prevent the eeprom emulation area from being erased when programming new code, as there is stored some calibration data?Where or how can I manage erasing only part of the flash, when using normal build and debugging command in VScode?Thanks!

I’m trying to set up STM32 development on Zorin OS using Visual Studio Code, but I’ve encountered some issues. Here's an overview of my setup and the problem I'm facing:System Information:OS: Zorin OS 17.2 Core(based on Ubuntu)IDE: Visual Studio CodeToolchain: ARM GCC (installed through apt)Debugging Tool: OpenOCDSTM32CubeMX for project generationI choose Makefile in Cubemx and it creates a project folder. I am opening it in VS Code, and open a terminal in it, write make and it yields:  ~/Codes/ST/blinkyy/blinkyy$ make arm-none-eabi-gcc build/main.o build/stm32f4xx_it.o build/stm32f4xx_hal_msp.o build/stm32f4xx_hal_tim.o build/stm32f4xx_hal_tim_ex.o build/stm32f4xx_hal_rcc.o build/stm32f4xx_hal_rcc_ex.o build/stm32f4xx_hal_flash.o build/stm32f4xx_hal_flash_ex.o build/stm32f4xx_hal_flash_ramfunc.o build/stm32f4xx_hal_gpio.o build/stm32f4xx_hal_dma_ex.o build/stm32f4xx_hal_dma.o build/stm32f4xx_hal_pwr.o build/stm32f4xx_hal_pwr_ex.o build/stm32f4xx_hal_cortex.o build/stm32f4xx_

I just switched back to a different client project, one that is built in the STM32 VSCode extension. This was after working on a different project with STM32CubeIDE and updating it to the latest version (1.16.1).Unfortunately, when I try to compile the VSCode-based project, it does not compile. The build task starts up but then reports the discovered compiler cannot build a simple test program. Here is the contents of the terminal window: Executing task: Build build task started.... C:\ST\STM32CubeCLT_1.15.0\CMake\bin\cmake.EXE --build D:/DataRoot/Projects/Equla/_Vert2-Firmware/STM32/Vert2-STM32/build/debug/build -- [0/1] Re-running CMake... -- Found multiple STM32CubeIDE installations. Using "C:/ST/STM32CubeIDE_1.11.0/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.12.3.rel1.win32_1.0.100.202403111256/tools/bin". -- The C compiler identification is GNU 12.3.1 -- The CXX compiler identification is GNU 12.3.1 -- Detecting C compiler ABI info -

I encountered an STLINK connection error when developing with VSCODE + STM32 VSCODE EXTENSION using the NUCLEO-H503RB MR2 board.(MR1 is no problem)#Development Tool 1: STM32CubeMX 6.12.1#Development Tool 3: Visual Studio Code#Extension: STM32 VSCode Extension Pack#Development Tool 4: STM32Cube CLT 1.16.0However, when installing STM32Cube CLT, I did not install STLINK. Instead, I separately installed Development Tool 2: STM32IDE 1.16.1 and installed STLINK, which resulted in normal operation. Since I don't actually use the IDE, it would ideally be better to install STLINK when installing CLT. Is there a difference in the STLINK version or other factors between IDE and CLT?I will proceed with development using this environment, but since I suspect it might be a tool-related issue, I wanted to report it.

 To make life a little easier for those who use vscode with PyOCD and DAPLink.There are two files that should be placed inside .vscode folder. // tasks.json { "version": "2.0.0", "tasks": [ { "label": "PyOCD Flash", "type": "shell", "command": "pyocd load -t STM32G030F6Px ${workspaceFolder}/build/Debug/blink.elf", "presentation": {"echo": true, "reveal": "always", "focus": false, "panel": "shared", "showReuseMessage": false, "clear": true}, }, { "label": "STLINK Flash", "type": "shell", "command": "STM32_Programmer_CLI.exe -c port=SWD freq=4000 mode=normal -w ${workspaceFolder}/build/Debug/blink.elf -v -g", "presentation": {"echo": true, "reveal": "always", "focus": false, "panel": "shared", "showReuseMessage": false, "clear": true}, }, { "label": "CMAKE clean", "type": "shell", "command": "C:/STM32CubeCLT_1.16.0/CMake/bin/cmake.exe --build ${workspaceFolder}/build/Debug --target clean --", "presentation": {"echo": true, "reveal": "always", "focus": false,

"After configuring a CMake project for STM32F407ZGT6 using STM32CubeMX, I imported it into VSCode, but encountered numerous errors and could not use it properly. However, projects for the H7 and F1 series work fine. What could be the issue?" 

Hi, I see that extension version 2.1.0 claims support for dual-core H7 devices, but I'm not seeing stm32h745 listed -- is this particular device not supported for some reason, or am I missing something?

Dear users   After upgrading to STM32CubeMX 6.12.1 some of you reported limitations for CMAKE generated projects. We encourage you therefore to stick with the 6.12.0 for those encountering this limitation until the publication of the 6.13.0.    Thanks for your comprehension  Enjoy our VSCode extension 

I noticed there are no STM32H747xx devices available for project creation from VS Code (it lists only through STM32H743xx). Is there any timeline on getting that device support in VS Code?