STM32CubeIDE for Visual Studio Code (MCUs)

I am working with an STM32N series MCU (STM32N657 / NUCLEO-N657X0-Q) and project generated with STM32CubeMX (Toolchain = Makefile).The workspace root contains:• GPIO_IOToggle.ioc• MakefileHowever, in VS Code (latest version) with STM32 VS Code Extension installed, the option “Setup STM32Cube project(s)” remains disabled (Greyed out).The project builds and debugs correctly when .vscode/launch.json is created manually, so the project itself is valid.Expected behavior:The extension should allow setup of existing CubeMX-generated Makefile projects, not only projects created via the extension or CLT.Environment:• macOS• STM32CubeMX (GUI)• STM32CubeCLT installed• VS Code latestThis appears to be a UX limitation or detection bug.

Diving into the wild world of airdrops? This breakdown covers the hottest ones on the horizon, like Nebulai and Helios, with step-by-step tips on joining Discords, completing tasks, and snagging those $NEB or whatever tokens without getting scammed. Plus, a peek at play-to-earn games like Crypto Golf Impact on Intella X. It's all about earning smarter, not harder—kinda wish I had this when I first got into crypto, would've saved me from a few dumb moves.For more deets and fresh updates, head over to Cryptowhatsup. They've got a ton of guides that actually make sense.

When I run build in a VSCode Dev Container with STM32CubeIDE installed, the build fails and i receive an error stating arm-none-eabi-gcc and arm-none-eabi-g++ was not found in the PATH. The compilers are installed, I see them inside the bundles folder (under /root/.local/share/stm32cube/bundles/), the extension is just not picking them up.This was previously working in a separate container but I can't seem to replicate it. 

Hello, I am trying to use the STM32CUBE RTOS STATE panel within VSCode as opposed to setting a watch variable for xQueueRegistry, but the state panel does not match what is shown in the queue registry. Only the first queue is shown. Also, I am curious how to get Semaphores to show up in the semaphores portion of the tree in the state panel. The semaphores I am using are binary semaphores which under the hood are just generic queues.  

Hello,I'm not sure where to begin with this issue. When I enable the RTOS Proxy as shown below in the debug launch configuration. And I flash and debug, I get the following error/crash. And I also have to unplug and replug the stlink v2 from the computer for it to be recognized again. This behavior is consistent except when I change the code structure in some small way like commenting out a few lines of code. Changing the code in some small way appears to make it work consistently again?

I have a vscode task that allows me to just flash the application using `cube` which has worked fine until I got the lastest extensions update where now running this task will give a "The "path" argument must be of type string. Received undefined" error. The task definition (tasks.json):"type": "shell", "label": "Program flash", "command": "cube", "args": [ "programmer", "-c", "port=SWD", "-d", "${command:st-stm32-ide-debug-launch.get-projects-binary-from-context1}", "-g" ], "problemMatcher": [], Part of the error log:025-12-16 23:18:12.319 [error] TypeError: The "path" argument must be of type string. Received undefined at Object.basename (node:path:911:5) at n (c:\Users\user\.vscode\extensions\stmicroelectronics.stm32cube-ide-debug-core-1.1.0\lib\extension.js:435:4173) at c:\Users\user\.vscode\extensions\stmicroelectronics.stm32cube-ide-debug-core-1.1.0\lib\extension.js:435:4493How can I resolve this?Thanks!

Hi,Is it possible to add a MCU reset command to the debug toolbar? I.e. a button that does a pause then "monitor reset" type sequence? Of course I can do this manually in the debug console, but it'd be nice to have a button to do it, to complement the full restart button.Thanks!

As I understand it, this extension only works online? If there’s no internet, the extension stops working. Is there a solution for this or…

Hello,Today I opened VS Code to work on my project and noticed the update was available. That's awesome, but typically we're forced to freeze our toolchain once we release the code to product, to avoid the risk that updates have unwanted side effects. Right now I've been evaluating whether we can use VS Code, or if we better stay with tried and true CubeIDE.It's fine for hobbyists to always update to the bleeding edge, but what about anyone using STM32 micro for application in automotive, medical, and defense application? It's a requirement to know that every possible change is tested before releasing code to the product, including toolchain and IDE updates. We can't know if there's a bug on day 0 of the release, of course!Can we understand if the ability to freeze version is on the development roadmap of the VS code plugin? If not ever, any safety critical application should probably avoid it, don't you think?Thanks.

The latest version of STM32CubeIDE for VSCode can have its performance affected by network conditions when working online. If the network is disconnected, the entire set of plugins may become unresponsive for a long time (ten or so minutes) before switching to offline mode. The whole plugin suite should be designed to primarily work offline, performing occasional network tasks in the background intermittently.  最新版的stm32cubeide for vscode ，在联网工作的时候，性能会被网络状态影响。如果发生了断网，则整个插件组会假死很久（十几分钟），才能切换到离线工作状态。整个插件组应该设计成离线工作为主，在背景状态、间歇性进行一些联网工作。

Hello,I'm slightly confused about the options in the STM32CUBE VSCode extension Project setup window.From the left dropdown i can select the Project, where i have options x, x_AppliSecure, x_AppliNonSecure and x_FSBL, for each of the left options, i can select Secure, Secure-only and Non-secure from the right dropdown for the Security model. I haven't found documentation which describes what do these options mean.For example, if i select x_AppliSecure from the left dropdown and Non-secure from the right drop down, which sounds like a conflict, what happens? In which scenario should i choose which of the 12 available Project-Security model combinations? Also, I assume that Secure means Secure + Non-secure, as Secure-only must mean secure only and Non-secure probably means Non-secure only?In the same window, multiple rows can be added to the list from the + button in the bottom right, what do the rows represent?Thanks! 

Hi, I am really struggling to get clangd to work correctly in a setup I am trying to get going. I'm new to this VSCode workflow, and am finding VSCode seems to have a lot of persnickety behaviors that really require a lot of specificity to get things working right. Here is what I am trying to do:I start with a fresh workspace, and ONLY the STM32Cube vscode extension pack installed. I add two folders to my workspace:an stm32 project folder, as created by cubeMXa shared_code folder, which contains multiple subfolders, each of which contain .c/.h files. Nothing particularly fancy here. I can get this setup compiling fine, but clangd is complaining about various #include files in my shared code area. I understand that the reason for this is because there is no .clangd file in my shared_code area, so clangd can't "see" it from my project area. Intrepid internet searching has led me to adding this to my code-workspace file:{ "folders": [ { "name": "stm32_project", "pa

Hello,I used vscode with st externsion Ver3.6.4. One day, suddenly, VSCode started showing many red lines and warnings, including "main.h" source file is not valid UTF-8 clang (invalid_utf8).the file looks like:and many other redlines, because of clangd.how can fix it?  it makes file very ugly, evenif it can be compiled no error.Thanks. 

Hi, the current STM32CubeIDE for Visual Studio Code 3.6.4. (and maybe before) "Create empty project" generates in CMakeLists.txt # Core MCU flags, CPU type, instruction set and FPU setup set(cpu_PARAMS # Other parameters # -mthumb # -mcpu, -mfloat, -mfloat-abi, ... )The comments are misleading, because in cmake\vscode_generated.cmake:set(cpu_PARAMS ${cpu_PARAMS} ${CPU_FLAGS})and therefore, my cpu_PARAMS will be combined with the CPU_FLAGS which already include -mcpu etc.which effectively overwrites my settings.hthKnarfB

Dear community we are pleased to announce the new release of STM32CubeIDE for VSCode   Features Added active debug session reset by adding an extra button to the debug toolbar. Added device manager capability to edit connected devices' names. Added capability to break on a specific line using the runEntry attribute. Added quickReset attribute controlling debug session reset button behavior. Added serverJtagCfg attribute to specify a device in the JTAG chain by its position and IRpre-length. Added serverIncrementalFlashing attribute enabling incremental programming. Chores Updated license terms to reflect dependency updates. Forced CMake Tools to use the active folder on debug session launch. Removed support for blank characters in project names. Bug Fixes Fixed cpu_PARAMS management to correctly handle end user contributions.   This thread is locked. Please start a new topic to ask your question.

Here: https://wiki.st.com/stm32mcu/wiki/Software_development_kit 

Hi all,Dwelving deeper into the life and soul of the STM32Cube extensions I have come across a rather evil little bug. Luckily it is quite easy to reproduce.Use CubeMX to generate a boilerplate CMake project for any STM32 chipOpen VS Code, and open the folderIn VS Code, disable STM32Cube CMake Support extensionIn VS Code, hit "F1" and type "edit user". Select "Preferences: Open User Settings (JSON)"In the JSON editor, remove the "cmake.environment" keyIn VS Code, re-enable the STM32Cube CMake SupportExpected outcome:The "cmake.environment" setting should be put into the ".vscode\settings.json" file, similar to how "cmake.cmakePath" is placed there by the extension.Observed outcome:The "cmake.environment" setting stays in the user's local settings file and affects all projects, ST and non-ST alike. The "${env:PATH}" evaluation is at the end of the line but nevertheless the setting gives preference to ST-sourced tools and executables if they happen to be found from from the folders that

The code completion provided by clangd automatically introduces the header file corresponding to the functionThis is a very bad thing !A configuration item needs to be added to the setting.json to disable automatic header file insertion  

I wanted to inspect the memory using the built-in Memory View window in VS Code, but the option is unavailable even though the debugging is on at that time, and it says "Add a new view using the plus button in the Toolbar with the debugger paused. Supported debuggers: cspy, cortex-debug, cppdbg."Is this a limitation of the current ST-Link GDB debugger in STM32 VS Code extension version?

i've just installed all necessary requirements for the STM32 vscode extension however it doesn't seem to launch cube mx or mcu finder when i click launch from vscode. not sure if its incorrect paths or permission issues?please see the screenshot for the path settings

It seems that the linker file is always corrupted when is generated by CubeMX for VS Code. I have done a workaround if needed. Beste regards,

When writing code, it is common to encounter the automatic inclusion of some unnecessary #include statements. For example, when I input "NULL" and press the Enter key, it will automatically add " #include <cstddef> ".

Hello,we thoroughly use STM32H750 DK systems on our faculty and install VSCode and STM32 plugins on all classroom computers each school year. We have noticed, that plugin is installed in home directory of each user, which is a big struggle for our situtation. Can we somehow create "per system" installations of CubeIDE and as alternative IDE VSCode + STM32 plugin to be installed in some common folders for all students that work on PCs?Thanks in advance,Robert. 

Hi,I have existing projects under the tried-and-trusted STM32CubeIde which I have previously built using the headless build option from GitHub actions, with CubeIDE pre-installed. This works well.I'm investigating use of the Stm32Cube for VS Code extension, that will enable us to use the Cursor AI fork of VS Code and have got the projects building correctly on my dev machine, using cmake files. All works well on my machine, but am trying to work out what steps are needed to get this working on GitHub actions. I understand (I think) that I need to have the extension installed to provide the 'cube' executable wrapper for cmake, setting up the correct path for the toolchain. So, do I need to install VS Code and the ST extension under my GitHub action yaml file to allow this all to build? I'm expecting to use the command line: `cube cmake --preset Release`  followed by `cube cmake --build --preset Release` or similar. But I'm not sure what I need to install/configure prior t

I installed STM32Cube for VS Code extension and then created an empty project.But the "Setup STM32Cube project(s)" on the STM32CUBE KEY ACTIONS is still in gray color. Is there something that I missed? My environment is as follows. - Windows 11 - VSCode: 1.106.3 - STM32Cube for VS Code:  3.6.4