Boot: Zephyr: Boards: Fix STM32H750B-DK App in Ext Flash support #2479
+7
−4
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 stm32h750b-dk 'ext_flash_app' board variant (zephyrproject-rtos/zephyr#97037), for storing apps in external Flash and chainloading them with MCUboot that's placed in internal Flash, we need a DT overlay to designate internal Flash & controller as the chosen 'zephyr,flash' & 'zephyr,flash-controller' for the MCUboot Zephyr Application. This way, no DT overlay will be needed at the Zephyr user app level.
Also, remove board conf file, as enabling STM32_MEMMAP is no longer needed here since it is now set on the Zephyr side in the board's 'Kconfig.defconfig' when building MCUboot app. And BOOT_MAX_IMG_SECTORS_AUTO no longer need to be disabled, after including the 'soc-nv-flash' binding in the 'st,stm32-qspi-nor' binding, then adding the 'erase-block-size' & 'write-block-size' properties in external Flash DT node.