STM32CubeIDE for Visual Studio Code (MCUs)

So I have an STM32 project in VSC and when I first set up this project and started debugging, I vaguely remember being asked by VSC to create a launch.json file.Now it seems I can build a ‘debug’ session, and launch it, and debug with all the usual features like step-in, step-out, continue, and so on. But how do I now add a ‘release’ build, which strips debug info and allows me to program a device without debugging it? [I am trying to be a good citizen and get along with STM32 for VSC, but so far it seems like i) A retrograde step ii)A mix of modern UI’s and very old looking Java (MX) and iii)You need a science degree in CMAKE to understand anything. ]My launch.json looks like this:{ // 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", "requ

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.

When I use stm32cubeide for vscode open the CMake project generated by stm32cubemx, and to verify  some math functions like log, sqrt etc,static void log_function_test(void){  typedef struct  {    double input;    double expected;  } log_test_case_t;  static const log_test_case_t test_cases[] =  {    {0.5, -0.6931471805599453},    {1.0, 0.0},    {2.0, 0.6931471805599453},    {10.0, 2.302585092994046}  };  const double tolerance = 1.0e-12;  uint32_t index;  uint8_t all_passed = 1u;  printf("log() test start\r\n");  for (index = 0u; index < (sizeof(test_cases) / sizeof(test_cases[0])); ++index)  {    volatile double input = test_cases[index].input;    double actual = log(input);    double error = fabs(actual - test_cases[index].expected);    uint8_t passed = isfinite(actual) && (error <= tolerance);    printf("log(%.6f) = %.15f, expected = %.15f, error = %.3e: %s\r\n",           input,           actual,           test_cases[index].expected,           error,           passed

Hello, I trying to program my development boards (NUCLEO-L073RZ and NUCLEO-F767ZI) using VScode (1.123.0) on Ubuntu (I tried 26.04 and 22.04.3). Installation of STM32cubeIDE for VScode extensions (3.9.0) went without errors, all libraries like CMake were installed automatically. But when I connect development board to USB, start VScode and look at STM32CUBE DEVICES AND BOARDS card, there is still: No device detected. When I try build some example project, build is successful, but when I click on Run and Debug, it's end with timeout error. I was tried this on two different computers with same result. When I do the same thing on the same computer under Windows 11, VScode finds the board without any problems. Is there some known issue with STM32cubeIDE for VScode extension in Ubuntu or is something else needed under Ubuntu?

I have a project that builds two different programs with conditional compilation. (I'll call the project Foo and the programs FooA and FooB) I currently have a #define in main.h that I comment/uncomment manually to toggle between them, but I'd like to hoist that into the build system. I could probably manage it with presets, but it looks like I'd have to manually define FooADebug, FooARelease, FooBDebug & FooBRelease, which would be tedious. (If someone does know of a way to make orthogonal sets of presets, I'd be interested) A more promising approach would seem to be something along the lines of:project(Foo) add_executable(FooA) add_executable(FooB) target_compile_definitions(FooB PRIVATE FOO_B) I can see how I would do this if I was writing all the CMakeLists.txt's myself, however while the top CML says# # This file is generated only once, # and is not re-generated if converter is called multiple times. # # User is free to modify the file as much as necessary #  cmake/stm32cu

I am reporting a critical issue where the STM32Cube Debug Core extension causes the VS Code Extension Host to crash repeatedly.Through VS Code's built-in diagnostic tools (specifically the "Extension Host" profiling and crash logs), I have confirmed that the crashes originate directly from this extension. This issue severely disrupts the debugging workflow. While it appears primarily on macOS, other platforms may also be affected but require further investigation.Please note that updating VS Code to the latest version does not resolve this issue.Environment Details:OS: macOS 26.6.2 (Apple Silicon/Universal) VS Code Version: 1.133.0 (Universal) Extension Version: STM32Cube Debug Core v1.4.0 Electron: 42.8.0 Node.js: 24.18.0Steps to Reproduce:Install the STM32Cube Debug Core extension (v1.4.0) in Visual Studio Code. Enable the extension and reload the window if necessary. Wait for a short period or attempt to initialize a debug session. Observe the "Extension Host" crashing notification

I have setup STM32 VSCode extension on my PC and it is amazing. The only problem that I have encountered is that it is not possible to run the code without debugging. I removed the "runToEntryPoint": "main" line in launch.json. But every time I launch the code it attaches a debugger. How can I simply run the code without debugging? Thank you,Damiano

I am using STM32CubeIDE for Visual Studio CodeIf I create an empty project in a folder with spaces the build will fail. I suspect the spaces create a double quote somehow.In the command below, main.c is wrapped in two quotes, -c ""C:\Users\me\VSC_projects\STM first try\asdf\Src\main.c""I suspect this makes gcc look for a file named main.c” instead of main.c. Plus “C:\ instead of C:\Failing build due to spaces:C:\Users\me\AppData\Local\stm32cube\bundles\gnu-tools-for-stm32\14.3.1+st.2\bin\arm-none-eabi-gcc.exe -DDEBUG -DRTE_DEVICE_STARTUP_STM32H5XX "-I"C:/Users/me/VSC_projects/STM first try/asdf/Inc"" "-I"C:/Users/me/VSC_projects/STM first try/asdf"" -fdata-sections -ffunction-sections -Wl,--gc-sections -Wno-comment -g -std=gnu11 -mcpu=cortex-m33 -mfpu=fpv5-sp-d16 -mfloat-abi=hard -mlittle-endian -mthumb -fstack-usage -Wall -Wextra -Wpedantic -Wno-unused-parameter -O0 -g3 -ggdb -o CMakeFiles\asdf.dir\Src\main.c.obj -c ""C:\Users\me\VSC_projects\STM first try\asdf\Src\main.c""arm-none-ea

In debug mode, the variables in the watch window are by default displayed in decimal format. I couldn't find a way to set it to display in hexadecimal format. I am using the jlink debugging configuration.

Environment: Windows 11, VS Code, STM32CubeCLT 1.22.0, stm32cube-ide-build-cmake 1.46.0, stm32-vscode-extension 3.10.0Symptom: Any CubeMX CMake project fails to configure with:CMake Error: Could not find CMAKE_ROOT !!!CMake has most likely not been installed correctly.Modules directory not found inRoot cause analysis: cube-cmake.exe is a self-contained binary embedding CMake 4.4.2, deployed at <ext>/resources/cube-cmake/win32/x86_64/. CMake's FindCMakeResourcesInInstallTree requires the executable directory to end with bin and <prefix>/share/cmake-4.4/Modules/CMake.cmake to exist. The shipped layout is neither bin-suffixed nor does it include share/cmake-4.4, and the companion cmake.exe is missing — so it fails on every run.Workaround (local): rebuilding bin/ + share/cmake-4.4/ + companion cmake.exe + a junction makes it work.Request: Please ship the full CMake resource tree (Modules/Templates) and companion cmake.exe with the extension, or have cube-cmake delegate to the C

I am having a hard time to use a JLink via IP on the local LAN. I can connect, but every time I launch a debug session, a pop-up from Segger appears asking me for the JLink identifier: I have to enter the IP address, and then it works. But this is rather nerving to have to enter the IP address every time I launch a debug/run session.It seems that the extension does not officially support JLink over IP. If this is true, please add this important feature in a future update. Specifically that the jlinkgdbtarget configuration type in the launch.json schema be updated to support an ipAddress field or a generic serverArgs/serverParameters array (matching how they already handle stgdbtarget and openocdtarget).Currently because the extension forces a hardcoded string layout and uses the silent (-s) flag, it actively suppresses SEGGER's standard native fallbacks (like reading workspace JLinkGDBServer.ini files).Thank you for an otherwise excellent tool (STM extensions + VSC).  

Under this configuration, the prompt indicates that the attribute "liveWatch" is not allowed. { "type": "jlinkgdbtarget", "request": "launch", "name": "STM32Cube: Launch JLink 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}" } ], "liveWatch": { "enabled": true, "samplesPerSecond": "4" } },This is the analysis conducted by GPT.STM32CubeIDE for Visual Studio Code 3.10.0JLinkDebugTargetAdapter correctly creates the Live Watch client.However, the Live Watch client immediately issues-var-createwhile the target is running.SEGGER J-Link GDB Server returnsCannot execu

I'd like to share an open-source alternative to STM32Cube Build Analyzer, which may be useful for developers who don't use STM32CubeIDE (Eclipse or Visual Studio Code edition), or who build their projects using other tools such as Visual Studio or CMake directly.GCCMapAnalyzer | Source.(HTML file, hosted on GitHub Pages; click on GCCMapAnalyzer to run it in the browser.)FunctionalitiesTree view: Visualizes memory usage by memory region, section, and object file. Memory Map: Displays symbols and sections in an address-space line diagram. Section configuration: Allows customization of how sections are counted and grouped. NoteI hope this post does not violate Community Guideline #5. I originally developed this tool to visualize an STM32H7 .map file before I knew about STM32Cube Build Analyzer, and I thought it might be useful for other community members as well. 

In the debug mode of JLink, the usage method of LiveWatch cannot be found. Only STLink has this function. How long will it take for the relevant functions of jLink to be updated?I really enjoy using this extension plugin provided by your official side. I hope you can let me know! thank you{ // 使用 IntelliSense 了解相关属性。 // 悬停以查看现有属性的描述。 // 欲了解更多信息，请访问: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "jlinkgdbtarget", "request": "launch", "name": "STM32Cube: Launch JLink 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}" } ] } ] 

As the title describes, the conversion tool to convert Stm32CubeIDE projects over to Visual Studio Code seems to work. Apart from the fact that, at least in my case, it failed to copy over the assembly files, .s files, in the project. Which led to build errors, specifically thumb mode errors.Just posting this here so that it may help others. Not quite sure how best else to let others know.

I’m using VSC with the STM32 extensions.When running debug sessions at leat 50% of the time I get this error message:Error in initializing ST-LINK device.Reason: USB communication error. Please reconnect the ST-LINK USB cable and try again.cube has exited with code 3 I have a good quality USB lead and I’m running on macOS on a Mac Mini M2

Hi ST,Today I decided to give STM32CubeIDE for VS Code another try.I installed all 15 latest packages (Rev. 3.10).Using the STM32Cube Bundle Manager, I installed all required bundles, including Ninja 1.13.2.After opening in VS Code the folder containing the code generated by STM32CubeMX (CMake option) and trying to configure CMake for the first time (Ctrl+Shift+P → CMake: Configure), I received the error below.What am I missing? The last time I tried this several months ago, the project at least configured correctly and built successfully. Kind regards,Thomas [main] Configuring project: Firmware[driver] NOTE: You are configuring with preset Debug, but there are some overrides being applied from your VS Code settings.[proc] Executing command: "C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin\cmake.exe" -DCMAKE_BUILD_TYPE=Debug -DCMAKE_TOOLCHAIN_FILE=C:/Projects/All-purpose-Micro-Controller-2/Firmware/cmake/gcc-arm-none

Hello! I installed the extension and configured it to work through a proxy (downloading the compiler, etc.), and everything works fine, but when I try to download devices list via cube pack sync, I get the error: Failed to download with Unsupported `GLOBAL_AGENT.HTTP_PROXY` configuration value: URL protocol must be "http:" I tried adding the proxy via platform environment variables, but that didn't help. Platform: Win11 IDE pluggin: 3.6.4 Pack manager: 0.3.12

Hi, how do I configure launch.json to use hot plug?

Hi, i have custom cmake configurations in my project. I have managed to make a selection trough “CMake: Select Configure Preset”. Unfortunately it is really easy to debug wrong configuration on debug launch, as you have to remember to switch configuration from command palette.

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

Is it possible to install STM32CubeIDE and STM32CubeIDE for VS Code on one PC (Windows)?   If so, can I run both versions simultaneously?    If so, can I program two microcontrollers simultaneously with two programmers? 

Dear all, I want to evaluate a STM32H5 (NUCLEO-H653ZI) via the built in STLink (ST-LINK FW: V3J16M7). I use VS Code with STM32CubeCLT_1.18.0 as IDE and control the flashing and debugging with a .json. Checking the STLink connection to the board by executing “<Path>\STM32_Programmer_CLI.exe –list” works fine. Also, flashing the board and running a simple LED toggle application by executing “<Path>\STM32_Programmer_CLI.exe --connect port=swd --download <Path>\H563ZI_Test.elf -hardRst” works just fine. When trying to start the GDB server for debugging by executing “<Path>\ ST-LINK_gdbserver.exe -p 50000 -cp <Path>\STM32CubeProgrammer\bin --swd –halt” an error occurs and the debug process is terminated:STMicroelectronics ST-LINK GDB server. Version 7.10.0Copyright (c) 2025, STMicroelectronics. All rights reserved.Starting server with the following options: Persistent Mode : Disabled Logging Level : 1 Listen Port Numbe

I tried to use the Build analyzer in VSCode, but there are some important allocations missing:VSCode:STM32CubeIDE (using *.elf file produced by VSCode):This is probably because the VSCode plugin is using the *.map file while the STM32CubeIDE uses the *.elf file.Is there any chance to have the same Analyzer in VSCode?