STM32CubeIDE for Visual Studio Code (MCUs)

Hello,I'm trying to get familiar with the STM32Cube extension for VSCode.I generated a basic STM32 project using STM32CubeMX, for my NUCLEO-H723ZG board.I then imported the generated cmake project using the extension tool, and configured it using the "setup STM32Cube project(s)" button of the extension, which created a launch.json file.When I try to run the debug config, I get the following error : bound doStepSettingsValidation Failed: Device not found: Error: Missing CMSIS_PACK_ROOTHere is the STM32Cube core output :025-10-20 16:19:33.002 [Info] Adding STM32Cube CLI path to environment: c:\Users\Jacques\.vscode\extensions\stmicroelectronics.stm32cube-ide-core-1.0.3\resources\binaries\win32\x86_64 2025-10-20 16:19:33.057 [Info] Configuring CMSIS_PACK_ROOT environment: C:\Users\Jacques\AppData\Local\stm32cube\packs 2025-10-20 16:19:33.099 [Info] Configuring CUBE_BUNDLE_PATH en

bound doStepSettingsValidation 失败：找不到设备：缺少CMSIS_PACK_ROOT 

hi dear,I created a project by selecting CMake as the toolchain and ST-ARM-CLANG as the compiler using the STM32Cube extension for VS Code (3.7.0) on macOS. Attached below are my configuration settings.   

I had a Windows account with a space in user folder name (between forename and surname). VScode was installed under AppData subfolder. As a result CMake generated paths like this into compile_commands.json:"command": "C:\\Users\\MIKKLE~1\\AppData\\Local\\STM32C~1\\bundles\\GNU-TO~2\\1431_S~1.2\\bin\\AR19DD~1.EXE -DDEBUG....Most of the things worked (compiling and debugging), but vscode highlighted that it can't find includes like these:#include <stdio.h>#include <assert.h>To be correct, clangd language server couldn't find them. Absence of these headers caused further errors. But when resolving other headers like stdint.h, clangd found them from st-arm-clangd bundle folder instead of compiler folder.The workaround was to add the very same shortened path as query driver into .vscode\settings.json: "--query-driver=C:\\Users\\MIKKLE~1\\AppData\\Local\\STM32C~1\\bundles\\GNU-TO~2\\1431_S~1

Hello, In my STM32WBA65 + FreeRTOS project that I work on in VSCode, with the STM32CubeIDE for VScode extension, I came accross a rather strange and annoying behaviour:It seems that when we enable liveWatch in our debug configuation in .vscode/launch.json, the breakpoints are still active after the debug session ends. My minimal debug configuration:{ "type": "stlinkgdbtarget", "request": "launch", "name": "Build+Prog+Debug", "origin": "snippet", "cwd": "${workspaceFolder}", "preBuild": "${command:st-stm32-ide-debug-launch.build}", "imagesAndSymbols": [ { "imageFileName": "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}" } ], "liveWatch": { "enabled": true, "samplesPerSecond": "4" }, } I have the same behaviour with a hot-attach debug configuration if it has liveWatch enabled.Here is how I test:In one thread, I

With Apple planning to deprecate Rosetta 2 after macOS Tahoe, I’d like to ask about the future of ST tools on macOS. As far as I understand, some of the current tools still rely on Rosetta, so this could become a problem for Apple Silicon users going forward.Are there any plans to provide native ARM versions of the ST tools? And for long-term use, would you recommend staying with the current `stlink-server`, or is it safer to start migrating to OpenOCD to avoid being blocked once Rosetta support is gone?Thanks!

Hello, In a paused debugging session, in the Run and Debug > Variables > Local list, if I right-click the varaible, the context menu has an item "Show in Memory Inspector".Clicking it opens the Memory Inspector, but with the name of the variable as the adress ( &(pRxData) for example), which the memory viewer cannot resolve into the actual address (0x20003DC0 for example). For this functionality to be most useful, I would expect either the Memory Inspector to be able to resolve the variable, or the command to open the Memory Inspector with the already-resolved address. Best regards,Nicolas

After generating the CMake project using STM32CubeMX (with the MCU being stm32f412ret6), how can FPU support be enabled in VSCode(STM32CubeIDE for Visual Studio Code)?

Hello, after updating to 3.7.0, my system no longer works. I can't debug and now get an error message. It was still working an hour ago. 

Hi,I wrote my own source file. It is located in the Core/Src directory. I have also entered it accordingly in cmakelists.txt.my cmakelists.txtNow I get an error saying that the include files from the Drivers directory are missing.

When I was using Keil and VSCode with the same piece of code, I found that I couldn't enter the ADC_DMA interrupt callback function when using VSCode. I was looking up the information and debugging in two software programs. I found that the address of the array where I stored the data was 0x20 in VSCode, while it was 0x24 in Keil. I attempted to adjust the array address to the correct one, but found that it couldn't be adjusted properly.If there is a solution, please let me know. Thank you.

Hello, In my STM32WBA65 project using FreeRTOS, I tried to create a hot-attach debug configuration.It works OK except for one problem : the RTOS proxy does not know what it is working on, as it seems to rely on the parameter imageFileName in imagesAndSymbols. Since replacing imageFileName with symbolFileName is necessary to get a hot-attach configuration (along with "serverReset": "None"), this is a problem. The problem seems to be that imageFileName has two roles : 1) providing the binary used by the RTOS Proxy and by the loading mechanism and 2) telling the system that we want to load said binary into the target. Is there a way to hot-attach the debugger with RTOS awareness that I missed ?  Below, my launch configuration in launch.json:{ "type": "stlinkgdbtarget", "request": "launch", "name": "Hot Attach", "origin": "snip

Current Setup:MCU: STM32H7 with FreeRTOSToolchain: VSCode + STM32 VS Code Extension + ST-LinkThe Problem: Currently, the STM32Cube RTOS panel and the RTOS STATE view only update when the debug session is paused. When the CPU is running, the RTOS table either shows "No RTOS detected" or is filled with ??? and 0x????????.For a complex H7 project with LwIP and multiple tasks, I need to monitor stack usage (especially EthIf which has hit 0B free stack) and task states in real-time to catch the exact moment of a crash that occurs after 1 hour of operation.Questions for the Community:VSCode Limitation: Is there any hidden setting in the official STM32 VS Code Extension to enable automatic/live refreshing of the RTOS thread table

The STM32Cube CMake Support extension blocks the VSCode UI when multi-root VSCode workspace are opened. Specifically, if a multi-root workspace is opened, the STM32Cube CMake Support extension continuously shows the Select hardware window. Even if the user closes the window by pressing Esc, it immediately reappears, preventing the user from doing anything, since that window has the highest priority.This happens because the extension detects the CMakeLists.txt file in th

The STM32Cube CMake Support extension treats workspaces as STM32Cube projects when a folder higher up in the directory tree (above the workspace folder) contains the files .settings/bundles.store.json and .settings/bundles-lock.store.json.For example, given a tree like this:/ ├── .settings │ ├── bundles.store.json │ └── bundles-lock.store.json │ └── path └── to └── generic_cmake_project ├── CMakeLists.txt ├── generic_cmake_project.code-workspace └── lib.cIf the user opens the workspace generic_cmake_project.code-workspace, the STM32Cube CMake Support extension automatically creates the file .vscode/settings.json with the following content:{ "cmake.cmakePath": "cube-cmake", "cmake.configure

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

After several days of wasted time trying to understand what was causing this issue, I finally realized that if I use the add_library() command in a CMake file, the build analyzer tool, without any reasonable explanation, searches for the *.map file with the wrong name. Specifically, if my VSCodeSTM32 project is located in the my_folder directory, then the build analyzer tool looks for the file my_folder/build/Debug/my_folder.map instead of my_folder/build/Debug/project_name.map.I ran into this problem because our project is generated by STM32CubeMX, which uses the add_library() command several times in the cmake/stm32cubemx/CMakeLists.txt file.This is the piece of code that is causing this issue in my main CMakeLists.txt (look in the attached project)################################################################################################################ if(true) # <-- Use false to fix this BUG set(STM32

Dear Community Members,   Please be informed that the Server Update Pack will be temporarily unavailable on February 26 due to scheduled maintenance. Date: February 26 Time: From 7:00 AM (for approximately 1 hour) Central European Time (CET)   During this maintenance window, you will not be able to access the server or download packs and bundles. other services are expected to operate normally. We apologize for any inconvenience this may cause and appreciate your understanding and patience.

I'm encountering a persistent issue when setting up an STM32Cube project in VS Code. Even when reverting to a previously working commit or starting a fresh setup from scratch (using the "Setup as an STM32Cube project" button), the process fails.The following error message appears:"Cube project discovery CMake configure step failed. Setup might be incomplete. Please check output logs"I have tested this on two different machines running both Linux and Windows, but the result is the same. Here are the relevant logs: 2026-02-20 08:41:11.309 [Info] Adding cube-cmake path to environment: /home/user/.vscode/extensions/stmicroelectronics.stm32cube-ide-build-cmake-1.43.0/resources/cube-cmake/linux2026-02-20 08:41:19.016 [Info] Running STM32Cube commands 'cube pack sync + cube pack install STMicroelectronics.stm32f4xx_

STM32CubeIDE for VS Code is there a memory window? like MDK Memory window   

stm32cube-ide-clangd.arguments are written to settings.json on every startup/setup with .exe or no extension depending on platform. settings.json contains important settings we want to share across collaborators but now it's getting constantly modified between platforms. 

c_cpp_properties is constantly being modified with additional compiler commands configurations:  { "configurations": [ { "name": "STM32_CM7", "compileCommands": "${workspaceFolder}/CM7/build/compile_commands.json" }, { "name": "STM32_CM4", "compileCommands": "${workspaceFolder}/CM4/build/compile_commands.json" }, { "name": "STM32_CM4", "compileCommands": "${workspaceFolder}/CM4/build/compile_commands.json" }, { "name": "STM32_CM7", "compileCommands": "${workspaceFolder}/CM7/build/compile_commands.json" }, { "name": "STM32_CM7", "compileCommands": "${workspaceFolder}/CM7/build/compile_commands.json" } ], "version": 4 } 

When opening a project directory in VS Code, the STM32CubeIDE for Visual Studio Code extension gets stuck in an infinite loading state (as shown in the screenshot below).Symptoms:"Go to Definition" does not work.The Build Analyzer view does not appear. clicking the "Build" button still triggers a successful compilation.Most dependent extensions, such as STM32Cube CMake Support, remain inactive

I get this type of error when I'm trying to setup a project with Nucleo-H563ZI and GCC here:I also get information that gdb is not running, while I've installed everything in the same way as I did on my previos laptop im my work. I've even changed system env for not checking tls

Dear all,I have extracted the XSPI_PSRAM_MemoryMapped for STM32N6570-DK from CubeMX without modification and created cmake code to integrate it into VSCode.Compiling it works, but the linker fails:simon@europa:~/STM32Cube/Example/XSPI_PSRAM_MemoryMapped/FSBL/build$ cube ninja [1/1] Linking C executable XSPI_PSRAM_MemoryMapped_FSBL.elf FAILED: [code=1] XSPI_PSRAM_MemoryMapped_FSBL.elf : && /home/simon/.local/share/stm32cube/bundles/gnu-tools-for-stm32/14.3.1+st.2/bin/arm-none-eabi-gcc -mcpu=cortex-m55 -mfpu=fpv5-d16 -mfloat-abi=hard -mcmse -Wall -fdata-sections -ffunction-sections -O0 -g3 -mcpu=cortex-m55 -mfpu=fpv5-d16 -mfloat-abi=hard -mcmse -T "/home/simon/STM32Cube/Example/XSPI_PSRAM_MemoryMapped/FSBL/STM32N657XX_AXISRAM2_fsbl.ld" --specs=nano.specs -Wl,-Map=XSPI_PSRAM_MemoryMapped_FSBL.map -Wl,--gc-sections -Wl,--print-memory-usage CMakeFiles/STM32_Drivers.dir/home/simon/STM32Cube/Example/XSPI_PSRAM_Me