2025-05-07 7:36 AM - edited 2025-05-07 8:08 AM
We are pleased to announce the new STM32Cube for Visual Studio Code Extension Pack
The st-cube-code-pack extension for Visual Studio Code is designed to enhance the development experience for STM32 microcontrollers by providing a comprehensive and updatable set of tools. The *extension pack* allow users to install one single pack bringing a full STM32 IDE experience into VS Code.
Breaking Changes
Pre-release (New!)
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.
Features
Documentation
The STM32Cube for VS Code extension offers a wealth of resources directly accessible within your integrated development environment. By installing the extension pack, you gain access to the "STM32Cube Resources" section, which is a centralized hub for valuable information which includes:
- Manuals: Comprehensive documentation that covers various aspects of STM32 development. These manuals provide detailed insights into the functionalities and features of STM32 microcontrollers, helping you understand the hardware and software integration.
- Tutorials: Step-by-step guides designed to assist both beginners and experienced developers. These tutorials cover a wide range of topics, from basic setup and configuration to advanced programming techniques, ensuring you have the guidance needed to effectively utilize STM32Cube tools.
Feedback & Support
If you need assistance or have any questions regarding STM32 for VS Code, support is readily available. You can access a wide range of resources and get help from the STMicroelectronics support team. Additionally, your feedback is valuable to us and helps improve the STM32 for VS Code extension. If you have any suggestions, issues, or comments, we encourage you to share them with the community.
- Feedback: To give feedback and participate in discussions, visit the [STM32 VS Code Extension Forum.](https://community.st.com/t5/stm32-vscode-extension-mcus/bd-p/stm32-vscode-extension-mcus)
- Community and ST expert help: To get help through our community and our ST experts on our forum, visit the [STM32 VS Code Extension Forum.](https://community.st.com/t5/stm32-vscode-extension-mcus/bd-p/stm32-vscode-extension-mcus)
- ST Support Home: For more information about getting support, visit the [STMicroelectronics Support Home.](https://www.st.com/content/st_com/en/support/support-home.html)
Download
https://marketplace.visualstudio.com/items?itemName=stmicroelectronics.stm32-vscode-extension
2025-06-04 6:50 AM
coud you provide launch.json temple? it's the key to launch a project successfuly. Automatically generated launch.json only has few or worng information. You can not assume new user know every fields.
Peter
2025-06-04 7:56 AM
Sounds weird to me to ask for some launch.json template what promoted extension(s) has(ve) to generate ...
I guess ST is not going to promote one to one launch.json ... up to them but ?
Instead could you point what sounds "wrong information" according to you .... if bug then a chance to get something back.
About "few" same please comment more ... "few" maybe sufficient in real : what do you think ?
"You can not assume new user know every fields" ... VSCode way of working according to me ... any debugger comes with integration (dedicated extension) whatever it is (Python, C/C++, ... STLink stuff) and end user way to access is always the same : a launch.json promoting sane default to be fine tuned or not and having extra control you can get Thanks editor auto-completion ... What may be helpful as extra is either / or documentation / GUI on top launch.json : what do you think here too ?
Any extra comment appreciated will help this community to progress (I'm part of :-))
2025-06-13 4:34 AM
The text is not aligned.
2025-06-15 10:42 AM
Please consider addressing https://github.com/clangd/vscode-clangd/issues/687 and https://github.com/clangd/clangd/issues/108 issues. It is preventing efficient refactoring on Windows platform.
Custom "stm32cube-ide-clangd.arguments" value doesn't cover "arm-none-eabi-g++.exe", which used by CMake for "compile_commands.json" if I enable CXX support. "--query-driver" clangd option supports globs (https://github.com/llvm/llvm-project/issues/56623).
Also, it would be great to have HAL/LL and other libraries be available and well-behaved for inclusion as https://cmake.org/cmake/help/latest/module/FetchContent.html and/or git submodules.