The bootloader image format includes version fields in the McciBootloader_AppInfo_t structure, and mccibootloader_image supports --app-version for setting them. However, there's no consistent versioning scheme applied across targets:
- STM32H7 (
Makefile-stm32h7.mk) sets --app-version 1.0.0
- STM32L0 (
Makefile-stm32l0.mk) doesn't set an explicit app-version
- The
Doxyfile PROJECT_NUMBER is empty
- The
mccibootloader_image tool has its own version (0.4.0) in tools/mccibootloader_image/i/mccibootloader_image_version.h, independently managed
We should establish:
- A version numbering convention for the bootloader itself (separate from the tool)
- Consistent
--app-version usage across all family makefiles
- A scheme for keeping
Doxyfile PROJECT_NUMBER in sync
- Documentation of the versioning policy
The version infrastructure exists in the image format -- this is about making the build system use it consistently.
The bootloader image format includes version fields in the
McciBootloader_AppInfo_tstructure, andmccibootloader_imagesupports--app-versionfor setting them. However, there's no consistent versioning scheme applied across targets:Makefile-stm32h7.mk) sets--app-version 1.0.0Makefile-stm32l0.mk) doesn't set an explicit app-versionDoxyfilePROJECT_NUMBERis emptymccibootloader_imagetool has its own version (0.4.0) intools/mccibootloader_image/i/mccibootloader_image_version.h, independently managedWe should establish:
--app-versionusage across all family makefilesDoxyfile PROJECT_NUMBERin syncThe version infrastructure exists in the image format -- this is about making the build system use it consistently.