Skip to content

Conversation

JarmouniA
Copy link

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.

…rlay

Following the introduction of stm32h750b-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 DT overlay to designate internal Flash & controller as the chosen
'zephyr,flash' & 'zephyr,flash-controller' for the MCUboot Zephyr Application.

Signed-off-by: Abderrahmane JARMOUNI <[email protected]>
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 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.

Signed-off-by: Abderrahmane JARMOUNI <[email protected]>
@JarmouniA
Copy link
Author

Cc @erwango @FRASTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants