This September update marks the second incremental update since the prerelease was published in May.
#1 STM32Cube for Visual Studio Code becomes STM32CubeIDE for Visual Studio Code
The STM32Cube for Visual Studio Code environment is still in its early stages. To ensure clarity and consistency between ST-developed IDEs within the STM32Cube ecosystem, we are renaming it STM32CubeIDE for Visual Studio Code.
#2 Semi-hosting for ST-LINK GDB server
The semi-hosting support can be enabled in three modes:
-
Console mode – allowing users to have I/O console interaction with the target
-
All mode – (console + file) allowing users to write data also from the target to a file on the host
The ST DAP adds a new set of attributes to enable and configure semi-hosting.
This addition into the DAP comes with a minimal TCP/IP console allowing developers to interact with the target when using the Console mode:
#3 Attach to remote debug server
Attach debug is a recent feature available in previous versions.
The attach debug mode decouples the GDB-client launch from the GDB-server launch. The main use case is to allow developers using Visual Studio Code to connect remotely to another PC where the STM32 target is connected over the network. Consequently, developers must also specify the serverHost and the serverPort.
A secondary use case is to launch the GDB server in persistent mode on the same PC as Visual Studio Code, to speed up the debug launch sequence.
More details on how to launch the GDB-server are documented in the ST-LINK GDB server manual.
What’s next
The next development sprint is already planned.
Your feedback is essential in shaping the future of STM32Cube for Visual Studio Code as it allows us to tailor it precisely to your requirements. We look forward to reading your ideas and questions on our community forum!
Additional resource
First published on Sep 29, 2025
