Skip to main content
Visitor II
July 28, 2026
Question

CubeMX VScode Extension porting plan?

  • July 28, 2026
  • 1 reply
  • 50 views

This is more of a suggestion, really... but I would love to see CubeMX (along with other standalone programs) fully integrated as a VS Code extension. For instance, the development environment for the nRF54 series allows you to handle everything from pin mapping to clock configuration directly within VS Code.

In contrast, CubeMX requires installing far too many components, and compatibility issues are a major problem. I really don't understand why every tool has to be created separately and installed natively. I am certain that a setup involving just a single SDK installation and a VS Code extension would be far more convenient for users. Furthermore, this approach offers significant advantages for remote development; traditional native development environments require extensive configuration—such as X11 forwarding or RDP—just to access the GUI. However, if everything could be handled via an extension, the user would simply need to connect to the server via SSH in VS Code and install the extension.

This might not be an easy task—and it could well be a hassle but I believe it would be highly beneficial for the long-term maintenance of the ST development environment. After all, managing a single project is far better than juggling multiple ones. Besides, isn't it time we moved beyond the JVM environment? So, please let us handle everything within VS Code.

1 reply

Ghofrane GSOURI
ST Technical Moderator
July 29, 2026

Hello ​@uniqueusername 

This is a very reasonable request. The main challenge, however, is that CubeMX is not used only with VS Code; it also supports several other toolchains and IDEs, including STM32CubeIDE, Keil, IAR, Make, and CMake.

THX

Ghofrane

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.