STMicroele dehcnual yctronics has officially launched STM32CubeIDE 2.0.0 in November 2025, introducing a significant architectural shift: STM32CubeMX is now offered only as a standalone tool, separate from the STM32CubeIDE environment. This change marks a strategic move to address evolving developer needs as the STM32 portfolio has expanded to encompass more than 4,000 devices, ranging from basic MCUs to complex multi-core MPUs

.

Major Update: STM32CubeMX Becomes a Standalone Tool, No Longer Integrated into STM32CubeIDE

Since its initial release in 2019, STM32CubeIDE aimed to unify STM32 development by integrating the chip configuration and code generation tool, STM32CubeMX, into a single environment. While this integrated architecture benefited early adopters and simpler product lines, the exponential growth of the STM32 ecosystem revealed several performance bottlenecks:

  • Large installation package (approximately 3.7 GB)
  • Reduced performance and stability, with slower operation
  • Mandatory login requirements and the need for full updates during software upgrades
  • Limited project flexibility
  • Insufficient improvements to the core IDE functionality

To resolve these issues, STM32CubeIDE 2.0.0 replaces the integrated architecture with an interoperability mechanism. Both STM32CubeMX and STM32CubeIDE 2.x are now independent tools that require separate downloads and installations. In this new model:

  • STM32CubeMX focuses on STM32 chip configuration and initialization code generation.
  • STM32CubeIDE returns to its core functions: code editing, compilation, and debugging.

The two tools interoperate through a "project import - file synchronization" mechanism. This collaborative model is consistent with how STM32CubeMX already works with other IDEs like IAR EWARM, Keil MDK-ARM, and STM32CubeIDE for VS Code (3.x version), offering developers greater tooling flexibility

.

Key Benefits for Developers

This decoupling brings several advantages:

  • Enhanced Tool Management Flexibility: Developers can now independently download, install, and update STM32CubeMX and STM32CubeIDE. This supports parallel deployment of multiple versions—for instance, using a stable STM32CubeMX version for production projects while testing new features in a separate version for R&D, all without version conflicts.

  • Optimized Performance and Resource Usage: With STM32CubeMX decoupled, the installation size of STM32CubeIDE 2.x is reduced to 2.9 GB. Developers will experience lower CPU and memory usage, faster tool startup times, and notably improved stability, particularly on Linux and macOS systems.

  • Diverse Project Types: STM32CubeIDE users can now leverage Makefile projects and CMake projects generated by STM32CubeMX, providing additional project flexibility.

  • Simplified Development Operations: The login requirement within the IDE has been removed in version 2.x. A unified CubeIDE project wizard integrates all supported project types, streamlining the project creation process.

Related Functional Updates and Upgrades

Beyond the architectural change, STM32CubeIDE 2.0.0 includes several functional enhancements:

  • Support for New STM32 Products: Aligned with STM32CubeMX v6.16.0, STM32CubeIDE 2.0.0 adds support for new MCU series including STM32N6, STM32H5, STM32WBA, and STM32WL3x. It also adapts to two new development boards: NUCLEO-WL3RKB1 and NUCLEO-WL3RKB2.

  • Toolchain Upgrades: The toolchain manager update site now includes support for GCC-14 (STM32 GNU tools), available for direct acquisition. It also supports direct access to ST Arm Clang (ST's LLVM-based Arm toolchain), eliminating the need for a separate installation of the STM32CubeCLT tool.

  • Debugging Enhancements: The ST-LINK GDB server now supports semihosting functionality, and the debug configuration interface has been made more intuitive.

  • Development Environment Optimization: The IDE now supports bundled CMake/Ninja binaries and has removed the ST-MCU-FINDER-PC component.

Installation and Update Guidelines

  • Fresh Installation: Developers need to download STM32CubeIDE 2.0.0 and STM32CubeMX (v6.16.0 or later is recommended for full compatibility) separately from the ST website.

  • Version Updates: Existing installations can be upgraded via "Help > Check for updates" within the IDE. However, drivers and STLINK server tools must be updated using the full installation package. Users must add a new Eclipse P2 update site when updating to avoid unintended upgrades.

  • IOC File Association: It is necessary to set STM32CubeMX as the default application for opening .ioc files in the operating system to prevent conflicts with older versions of CubeIDE.

  • Project Synchronization: After regenerating code in STM32CubeMX, you must refresh the project (F5) in STM32CubeIDE 2.x to synchronize the file tree. Future versions plan to automate code updates.

  • Multi-Version Coexistence: You can run multiple versions of STM32CubeIDE and STM32CubeMX in parallel by installing them in different directories.

Conclusion

The release of STM32CubeIDE 2.0.0 represents a strategic adjustment to ST's STM32 software development toolchain. By decoupling STM32CubeMX and focusing STM32CubeIDE on its core competencies, STMicroelectronics provides developers with a more flexible tool combination, a more efficient development workflow, and a more stable operating experience. In the long term, this model is expected to significantly reduce development complexity and maintenance costs, particularly for complex multi-core projects and cross-platform development scenarios.

Looking ahead, ST will focus on optimizing the collaboration experience between STM32CubeIDE and VS Code to meet demands for AI-assisted programming and plugin ecosystems. Additionally, efforts will continue to enhance toolchain compatibility and automation features, including automatic project refresh after code generation and improved multi-core debugging capabilities

.