STM32CubeIDE 2.0.0 is out: interoperability instead of integration [New Update]
Device configuration is now removed from CubeIDE and must be done using the stand-alone STM32CubeMX tool. Developers will now use CubeMX and CubeIDE separately, without breaking existing project compatibility.
What does this change mean for developers?
What does this change mean for developers?
- Separate download and installation: CubeMX is now a stand-alone tool, requiring separate download alongside CubeIDE 2.x for configuration and code generation.
- Tool update flexibility: Developers can update and freeze CubeMX and CubeIDE independently, with multiple versions of each installed side-by-side.
- Multiple project types: CubeMX can now generate Makefile and CMake projects in addition to CubeIDE projects.
- IOC-file association: The OS controls which app opens ioc-files; ensure CubeMX stand-alone is associated to avoid conflicts with older CubeIDE versions.
- Refreshing the IDE project: After code regeneration, refresh the project explorer (F5) to sync file trees; automation is planned for future versions.
- Harmonized CubeIDE project wizard: A single STM32 project wizard simplifies project creation for all supported types.
- Memory footprint and performance: Removing CubeMX integration reduces installation size (~3.7GB to 2.9GB) and lowers CPU/RAM usage, improving stability especially on Linux and Mac.
- No more log-in requirement: The login from CubeMX is removed since it's no longer integrated.
Focus on edit/compile/debug: Decoupling CubeMX allows more development focus on improving core CubeIDE workflows.
With this release, device configuration, previously handled within CubeIDE via CubeMX, is now exclusively available through the stand-alone CubeMX tool. Users will configure microcontroller peripherals and generate initialization code separately in CubeMX, then import the generated projects into Cub...
