STM32CubeIDE for Visual Studio Code (MCUs)

Hi everyone,I'm working on an STM32 (Nucleo-F446RE to be spesific) project using the STM32Cube extension for VS Code, not CubeIDE. I'm using CMake for building the project.I encountered a few issues:printf doesn't print anything to the serial monitor, so I switched to using HAL_UART_Transmit.When I try to print a float using sprintf(msg, "value: %f\n", var);, it doesn’t work. The output just skips the float value (e.g., "value: \n").After some research, I found out I need to add "-u _printf_float" to the linker flags to enable float formatting support with printf and sprintf.However, I'm new to CMake and I couldn’t figure out which CMake file I need to modify in the project folder to add this flag.I'd really appreciate it if someone could guide me:Where exactly should I add the "-u _printf_float" flag?Is there anything else I should do

    We are pleased to announce the new  STM32Cube for Visual Studio Code Extension Pack   The

When I setup my STM32CubeProject the NUCLEO-U5A5ZJ-Q  does not show up as option. No U5 devices show up. Is there a pack or something else I need to install?Thanks

dear Community  We encountered a server issue happened 24th mid-day up to 25th early morning CET impacting some critical services required by our extension V3.X We are sorry for the disturbance it caused

STM32CubeIDE for Visual Studio Code Extension Pack promoting STM32Cube experience 3.6.2 (pre-release) Chores Removed STM32Cube Themes extension Pre-release information This release represents a major advancement in delivering a comprehensive and efficient VS Code-based development environment for STM32 microcontroller projects. ST is offering this version as a pre-release to set appropriate expectations. It introduces a new platform architecture that will serve as the basis for the evolving STM32Cube for VS Code environment. As with any innovative tool, it will undergo a maturation process. T

I created an H745ZIT6 CubeMX project and then tried to import it in VSCode. But when I try to import it, it expects me to import each core individually. How am I supposed to do it? When I try to set the project path for each of them, the only option I get is the parent folder.

Quick question - how do I get STM32CUBE Live Watch to display values in hex? I have the output radix set to 16 so normal watch shows hex values but live watch is in decimal.Latest preview versions of VSCode extensions (STLink GDB Server v0.10.1)

MCU: STM32G474xxIDE: VSCodeToolchain: ARM Compiler 6 (armclang, armlink)Question: I'm a newcomer to using armclang and armlink for compiling and linking a project for an STM32G4 MCU. I've successfully compiled a minimal project and am trying to link it using armlink. My scatter file is: LR_IROM1 0x08000000 0x00080000 { ; load region size_region ER_IROM1 0x08000000 0x00080000 { ; load address = execution address *.o (.isr_vector, +First) *(InRoot$$Sections) .ANY (+RO) .ANY (+XO) } RW_IRAM1 0x20000000 0x00020000 { ; RW data .ANY (+RW +ZI) } } I use a startup script in GNU syntax generated from CubeMX.The linker command I am using is: armlink --cpu=Cortex-M4.fp.sp *.o --scatter=STM32G474XX_FLASH.sct --map --info=summarysizes --load_addr_map_info --xref --callgraph --symbols --info=sizes --i

Hi, I followed the instructions in this post to install the STM32Cube extension for Visual Studio Code. After completing the installation, I noticed that two icons appeared in the left panel: one labeled "STM32Cube" and the other "STM32 VS Code Extension".The difference is that under "STM32Cube", there is only a "Key Actions" menu instead of the Project Manager, so I can’t i

 I am using an ST-Link V2 for debugging in VS Code. It worked before, but now it gives me an error in the GDB server terminal:"Error in initializing ST-LINK device.Reason: ST-LINK firmware upgrade required. Please upgrade the ST-LINK firmware using the upgrade tool."When I try to upgrade my ST-Link firmware version using the button in the VS Code STM32 extension, this error is displayed: "Error whilst trying to update STLink Firmware."

There are a large number of extensions that are currently available for VSCode, but I am confused on which extensions to install.For example. There are these two extensionsSTM32Cube for Visual Studio CodeSTM32Cube for Visual Studio Code CoreThese two look like they complement each other, however going into the settings, I need to to specify the path location for CubeMX and the Finder tool twice. I don't even know whether I should be installing these together now. Also, you provide STM32Cube clangd extension, however the STM32Cube for Visual Studio Code installed a C/C++ extension pack that includes the Microsoft C++ extension and this is known to conflict with clangd.There are also a plethora of extensions likeBuild AnalyzerBundles ManagerCMake SupportDebug CoreDebug STLink GDB serverProject ManagerRegister ViewRTOS viewand now it i

Hi, I use VS Studio Code for programming my STM32, but i have a problem for uploading firmware. I use STM32Cube add-on but can't communicate with my ST-Link. When I use the same code with STM32 Cube IDE (STM32 Cube programmer), the firmware can upload without problem.After compile, the windows open for choosing a program to open my .elf file. No error on compile, just my firmware file open in terminal. Thanks for help.    

I would like to use the STM32 Cube extensions for VSCode. I'm happily coding in VSCode for all my projects, but found the "CMake Tools" extension too limiting and therefore disabled it in favor of other CMake extensions.Unfortunately, the STM32 Cube extensions force the use of the "CMake Tools" as a dependency and are therefore unusable for my projects. Even though something like the "STM32Cube Debug STLink GDB Server" should not need to be aware of CMake at all.Would it be possible to remove the "CMake Tools" dependency from the GDB server extension, or can I somehow use it in some other way?

Platform: macOS 11.7.10 (BigSur)   I wanted to try out the recently announced STM32Cube plugin for VSCODE. Did so but from my understanding I have to install/configure STM32CubeCLT within VSCODE. Not knowing whether I had installed it with STM32CubeIDE already I downloaded the package (again?). After the installation had run  successfully I went into VSCODE to configure STM32CubeCLT.An installation directory has to be specified. I have no idea, where this directory can be found. Can anyone help?

The extension signals the conflict as in subject and suggests to disable intellisense altogether.MS C++ (cpptools) is a very popular extension required by many others, so disabling it is not an option.Another solution might be to disable the individual stm32-cube-clangd extension, but does it have any drawback? What's the point of having an useless and incompatible extension?

Hi, I am debugging an STM32H563ZI with the following environment:OS: Ubuntu 20.04 LTSSTM32CubeMX: 6.15.0Visual Studio Code: 1.102.3Extensions:STM32Cube Bundles Manager: 0.23.3STM32Cube Debug STLink GDB Server: 0.10.1STM32Cube Registers View: 0.3.0Board: NUCLEO-H563ZIIn this setup, after launching the debugger, I cannot find a way to inspect the values in Flash, RAM, or the registers of the Cortex-M33 peripherals.Regarding memory, I tried installing the "MemoryView" extension, but I am still unable to view the values. Are there any alternative extensions with similar functionality?

like keil "periodic window updata",now i can see the data by pausingSTM32Cube for Visual Studio Code V3.5.1

Hello everyone,I understand that  bundle manager replaced STM32CubeCLT  with "New STM32Cube for Visual Studio Code extenstion".Is there an option to download the bundles outside VSCode environment for offline installation? Similar to STM32CubeCLT?Rationale here is to use the same toolchain in an headless automated build system with no internet connection.Thanks

编译正常，也能识别到stlink，但是没办法运行调试烧录，也没办法升级stlink固件 ，一烧录就显示以下报错，目前没找到解决办法，但网上已有与我相同问题的用户 Translationn: The compilation is normal and stlink can be recognized, but I can't run the debug burn, nor can I upgrade the stlink firmware. The following error is displayed when burning. I haven't found a solution yet, but there are users with the same problem as me on the Internet

While uploading application or FSBL ELF File it is showing a dwarf error!! I tried downloading new version of STM Studio but similar problem occurred in that too; Could you suggest other alternate method so that I can fetch data.

Hi,In the bundles manager for my project is it possible to view at a glance items where there is an update available? Currently the status column icon doesn't differentiate between updatable items - only when I open the version drop-down does it become clear there are newer version(s) available (or I select all then hover over the update button).Also, same goes for "cube pack list" command - can this show a list of updatable items?Thanks.

I am using the STM32Cube VS Code extension (Preview) with the official ST-ARM-CLANG and clangd for code completion. Just ran into two issues:1. Incomplete --query-driver config breaks C++ IntelliSenseThe extension adds--query-driver=${env:CUBE_BUNDLE_PATH}/st-arm-clang/19.1.6+st.8/bin/starm-clang.exeto settings.json by default, but this is not enough for C++ files.Unless you also add--query-driver=${env:CUBE_BUNDLE_PATH}/st-arm-clang/19.1.6+st.8/bin/starm-clang++.exeC++ IntelliSense will be broken (red squiggles, no symbols, etc).Same issue for GCC toolchain: you need both gcc and g++ in the driver list.2. --multi-lib-config triggers errors in clangdIf you enable --multi-lib-config, clangd just starts throwing errors about missing headers and stuff, even

Newly installed Ubuntu 25.04Newly installed VSCode with STM32Cube for Visual Studio Code(preview)The project generated by STM32CubeMX can be compiled, but cannot be debugged.    

Hi everyone,I’m still having an issue with my STM32F746G-Discovery board. I want to run the program using VSCode, but I’m encountering errors in my main.c file. Specifically, it can't find main.h, and as a result, the code isn’t running.I want to build and run the code directly in VSCode, but it’s not working as expected. Could it be that the compiler is misconfigured? I’m currently using the GCC compiler for C/C++.I also switched the toolchain in CubeMX to Makefile. After that, I installed CubeCLT and tried to run and build the code, but nothing happened. 

I am trying to use VScode to debug code on a STM32U5 nucleo board connected to another machine.To do that, I start VScode on my machine and use the "connect to Host" command, open the project on the distant machine and try to launch debug. Both machine run Ubuntu 22.04.Does it work for anyone ?At that point I get this:[2025-08-04T10:02:54.896Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session connected. You can switch to "DEBUG CONSOLE" to see GDB interactions. /usr/bin/stlink-server -p 50000 -cp /opt/pqs/STMicroelectronics/STM32Cube/STM32CubeProgrammer/bin/STM32CubeProgrammer --swd --serial-number 002400233532510831333430 --halt -m 0 /usr/bin/stlink-server: invalid option -- 'c' /usr/bin/stlink-server: unrecognized option '--swd' /usr/bin/stlink-server: unrecognized option '--serial-number' /usr/bin/stlink-server: unrecognized option '--halt' /usr/bin/stlink-server: invalid option -- 'm' Info : default