2022-12-21 03:45 AM
Hello,
maybe this might be of interest to many people using CubeIDE and HAL libraries.
I've seen many threads here complaining that after a CubeIDE update HAL-related sources didn't work anymore.
That didn't happen to me, mostly because I don't use many HAL sources.
But just in case, how can I prevent that a CubeIDE update also updates the HAL files in my project?
I usually start with CubeMX, then generate code for CubeIDE, with separate .h/.c files per peripheral, then I try not to use CubeMX again.
If necessary I start another CubeMX project so that nothing of my original project is overwritten by CubeMX.
Solved! Go to Solution.
2022-12-21 04:01 AM
In order to keep a specific version of HAL and not use the latest one, you only need to uncheck the Use Default Firmware Locations in the Project Manager. Then the currently selected version is always used.
This is very useful for projects that do not allow any changes to the libraries after certification, because otherwise they would have to be recertified.
Regards
/Peter
2022-12-21 04:01 AM
In order to keep a specific version of HAL and not use the latest one, you only need to uncheck the Use Default Firmware Locations in the Project Manager. Then the currently selected version is always used.
This is very useful for projects that do not allow any changes to the libraries after certification, because otherwise they would have to be recertified.
Regards
/Peter
2022-12-21 04:04 AM
Thanks!
So that's a setting to be done in CubeMX.
Maybe people should think of that before any updates.