STM32CubeMX2 (MCUs)

A few direct questions about the current CubeMX2/HAL2 split. Are older STM32 series expected to stay on HAL1 + CubeMX permanently, or is there an actual plan to migrate them to HAL2 + CubeMX2? What is the long-term support model here?Are these two stacks supposed to coexist for years, or is HAL1/CubeMX effectively going into maintenance mode? Is there any official migration guide planned?Both for HAL1 → HAL2 API migration and CubeMX project → CubeMX2 project migration. How is the VS Code extension supposed to work with both ecosystems in practice?If one project is on CubeMX/HAL1 and another is on CubeMX2/HAL2, what is the intended workflow?Is proper support planned for both, or is the tooling mainly targeting the new stack? Where is the actual HAL1 vs HAL2 side-by-side data?Flash usage, RAM usage, performance, code size, same project, same MCU class, comparable build settings. Right now this looks like a major ecosystem split without a clear migration plan or hard technical

Recently I’ve been learning about the updated STM32 software ecosystem, including the new HAL2 library and STM32CubeMX 2 tool. I have a few practical questions and would like to start a discussion with all STM32 developers here.   What are the new characteristics, improvements and advantages of HAL2 compared with the traditional HAL library?   Can STM32CubeMX 2 still support earlier and older STM32 MCUs, or does it only serve the latest chip series?   For those legacy STM32 microcontrollers, are they able to use the new HAL2 library, or can they only run the classic HAL as before?   If you have relevant development experience or official information, welcome to share your views and explanations.    

Hi all,   in the release note of the STM32C5 family it is mentioned that the family will be supported with STM32CubeMX2. May I please ask when is it going to be available?    With best regards, Dmitry

Hi everyone, I have a quick question regarding the upcoming release of CubeMX2 and its backward compatibility. Once CubeMX2 is released, will the older series before C5 (like the F4) support MX2 and HAL2? Also, if they do support it, will we be forced to bundle HAL2 for these older models, or will there be some flexibility? Thanks in advance for any insights or official clarification! Best,Leo

Hi, I was just reading about the new STM32C5 processors. The press release states: Enhancements to the development ecosystem include a new STM32CubeMX flavor, STM32CubeMX2, which introduces a preview feature that allows faster access to reference code thereby accelerating development and easing code reuse. Also new in the STM32CubeC5 embedded software offer, the latest code-size optimized hardware abstraction layer (HAL2), gives access to all MCU features and allows more of the MCU’s memory to be used for application code. What is CubeMX2 and HAL2?   A