2020-08-29 11:42 PM
Is it possible to revert a project to an earlier firmware version? I was able to upgrade, but now I can't figure out how to change back to the previous version.
I also can't create a new project with the older firmware version either (the dropdown is greyed-out / disabled), even though I have multiple firmware versions installed.
Solved! Go to Solution.
2020-08-30 07:19 AM
If you run CubeMX in standalone mode, you can select the firmware repository for the chip in Project Manager -> Project -> Mcu and Firmware Package. Just tried it.
Probably won't work for project created with STM32CubeIDE, but you could create in CubeMX and then import the project.
2020-08-30 07:19 AM
If you run CubeMX in standalone mode, you can select the firmware repository for the chip in Project Manager -> Project -> Mcu and Firmware Package. Just tried it.
Probably won't work for project created with STM32CubeIDE, but you could create in CubeMX and then import the project.
2020-08-30 08:43 AM
Thanks for the suggested workaround with CubeMX.
Seems like STM32CubeIDE is not fully baked yet.
2020-08-30 10:13 AM
Two related issues:
The workaround is to just treat CubeIDE like Atollic (and assume it has no CubeMX / .ioc capabilities), but I figured it would be helpful to note these usability issues anyway.
2020-08-30 10:39 AM
For additional clarification on the differences between CubeIDE and CubeMX:
CubeMX allows changing firmware path:
CubeIDE does NOT allow changing firmware path:
2022-06-15 01:46 PM
@Imen DAHMEN
FYI
2023-11-28 10:26 PM
I just tried to find the old version number when opening .ioc file as text, replaced it to the newer version and it worked for STM32CubeIDE. I mean, by worked I see the version number displayed in STM32CubeIDE matches. I also deleted older software pack and left only the current. The code generation feature works, the code compiles. Whether the selected version is used - I'm not sure and IDK how to test it. I noticed in git that in some headers the version was changed, but git didn't detect many changes in the project. This is a little suspicious, I'd expect more changes, but IDK, maybe it's OK.
The changed key was "ProjectManager.FirmwarePackage".