sysbuild: Remove IMAGES variable
This variable was originally provided for two indended purposes: * Let users manually add a new image in a desired order in the list. * Let users set build-only images, which are excluded from the list. Given the recent additions of the `sysbuild_add_dependencies()` function and the `BUILD_ONLY` parameter, `IMAGES` should be considered obsolete. Furthermore, the list of images added to sysbuild should be updated automatically when calling `ExternalZephyrProject_Add()`. This is now possible by using a GLOBAL property internal to sysbuild. With that, the `IMAGES` variable can be removed. Its existing usage for image ordering is replaced with `sysbuild_add_dependencies()` treewide. Signed-off-by: Grzegorz Swiderski <grzegorz.swiderski@nordicsemi.no>
This commit is contained in:
parent
c323cc6fb1
commit
6640c04df6
6 changed files with 25 additions and 13 deletions
|
@ -15,11 +15,12 @@ ExternalZephyrProject_Add(
|
|||
)
|
||||
|
||||
# Add the swapped app to the list of images to flash
|
||||
# Ensure the order of images is as follows:
|
||||
# Ensure the flashing order of images is as follows:
|
||||
# - mcuboot
|
||||
# - swapped app
|
||||
# - primary app (test_mcuboot)
|
||||
# This order means that if the debugger resets the MCU in between flash
|
||||
# iterations, the MCUBoot swap won't be triggered until the secondary app
|
||||
# is actually present in flash.
|
||||
set(IMAGES "mcuboot" "swapped_app" "test_mcuboot")
|
||||
sysbuild_add_dependencies(FLASH test_mcuboot swapped_app)
|
||||
sysbuild_add_dependencies(FLASH swapped_app mcuboot)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue