STM32CubeIDE 2.0 release - early heads-up!

[mattias norlander]

Starting from the release in November 2025, STM32CubeIDE and STM32CubeMX will be available exclusively in their standalone versions.

STM32CubeMX will no longer be integrated inside STM32CubeIDE. Instead, the two tools will be interoperable in the same way as with IAR EWARM, Keil MDK-ARM, and STM32Cube for VS Code.

The current integration of these two tools may seem compelling in the early prototyping phases of a project. But the integration leads to heavy/poor performance, stability issues across OSes and monolithic updates. It is time for STM32CubeIDE to go back to its roots and focus on Edit / Compile / debug.

What the STM32CubeIDE (2.0) evolution will bring to you: 

• Greater flexibility in code development thanks to purpose-built, standalone tools. 
  • Updateability: Offering the possibility to use any version of STM32CubeIDE with any version of STM32CubeMX. Separating STM32CubeMX and STM32CubeIDE allows developers to update each tool independently, lowering risks and increasing flexibility. 
  • Project type flexibility: Allowing STM32CubeIDE users to also leverage STM32CubeMX-generated Makefile projects, and CMake projects for additional project flexibility. 
  • Harmonized workflows: Interoperability instead of integration harmonizes the workflows between STM32CubeMX and all IDEs.  

• Better usability and performance for faster project completion: 
  • Faster tool launch and lower PC resource requirements. 
  • Increased stability, particularly on Linux and macOS system. 
  • No log-in required inside STM32CubeIDE. 

Next steps: what is the impact for STM32 developers?  

• STM32CubeIDE 2.0 will be available as an installer package from st.com.
• Previous versions of STM32CubeIDE and STM32CubeMX will still be available to download from st.com. 
• Updating existing installations will require adding a new Eclipse P2 update site to eliminate unintended/unaware updates.
• ST will continue providing technical support on old versions.

• On-going STM32 projects will not be impacted by this update. 
  • However, opening an existing project with a newer version of STM32CubeMX may update your project, depending on STM32Cube firmware used. This issue is not related to the STM32CubeIDE and STM32CubeMX tool split. 
  • Double-clicking on the ioc-file from inside STM32CubeIDE, will launch the standalone STM32CubeMX tool if you already have the tool installed. 

We are confident that this update will bring significant long-term benefits to your development process. Our support team is here to assist you during this transition.

Please feel free to reach out with any questions!

[vaualbus]

Can the issue that random files are opened while running or starting a debug session be solved. is so frustrating 

Anyway yeah way better to keep stuff separated.  

[mail239955_stm1_stmicro_com]

I think it is an Eclipse issue rather than a STM32IDE specific one since it happens there too with CDT Embedded.

[vaualbus]

Yeah, but there must be a solution somehow. A lot of the time I risk modifying unwanted code when I launch the application. If I recall the issue is something related to gdb or something like that. 

[rabbi141]

I am exited to know when will STM32CubeIDE 2.0 be released?

[mattias norlander]

Should be available in 2-3 weeks from now.

[dvr]

Does this mean I can now open projects created in CubeIDE in Visual Studio Code and vice versa and do builds/debug etc?

[cjay]

What the actual? Who decided this was a good idea? 

I teach using STM Cube IDE and Discovery boards, this step has invalidated *years* of teaching material and raised the bar to entry for students. 

If this carries on and I have to ultimately move to VSCode I might as well get ahead of the curve, save money and give them RPi Pico instead.

[Jorgie]

Apparently the 2.0 update has created a major road block for quick development.

I have not even downloaded 2.0, but a colleague has and he brought my attention to the fact he could not create a new project with an IOC already to start development.

Very bad idea.

Bring back the integrated system.

Have a look here: ST’s Worst Decision Yet? 

[nico23]

Does the live viewer in Debug work, or does it have the same issues with 1.19?

[cjay]

Absolutely agree, the integrated system is a major attraction and as I'm sure many people know, a differentiating feature that separates ST from competitors who rely on clunky, slow or over complex IDEs.

From my POV, with STMCube, it's possible to get from zero to hello world in less than 15 minutes and that includes the installation of the development environment, selecting products is simple and efficient, that first experience with an MCU and IDE creates a customer.