boot: zephyr: board: stm32h573i_dk: Add support for ext_flash_app variant #2500
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following the introduction of stm32h573i-dk 'ext_flash_app' board variant, for storing apps in external flash and chainloading them with MCUboot that's placed in internal flash, we need a devicetree overlay to designate the internal flash and flash controller as the chosen 'zephyr,flash' and 'zephyr,flash-controller' for the MCUboot zephyr application.
STM32_MEMMAP is no longer needed since it is now set on the Zephyr side in the board's 'Kconfig.defconfig' when building MCUboot app. Also, BOOT_MAX_IMG_SECTORS_AUTO is no longer needed to be disabled after including the 'soc-nv-flash' binding in the 'st,stm32-xspi-nor' binding, then adding the 'erase-block-size' and 'write-block-size' properties
in external Flash DT node. Therefore, remove the board conf file.
This PR follow along the changes for STM32H750B-DK in #2479. Aim is to get rid of the overlay in the future together with the overlay for STM32H750B-DK.