Boards: STM32H750B-DK: Introduce App in Ext Flash variant #97037
+402
−258
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 6, 2025
erwango
reviewed
Oct 6, 2025
There was a problem hiding this comment.
@JarmouniA I was wondering if snippets could be used instead of adding a target each time we need to introduce an ext_mem app. Did you look at this possibility ?
Just thinking out loud, maybe the combination with sysbuild doesn't work great.
Not sure what we would put in them, maybe an ext Flash-specific snippet, but then the internal Flash is not necessarily the same, its sector size... |
Many Zephyr subsystems as well MCUboot rely on the write-block-size and erase-block-size properties, of the chosen Flash device in DT, to determine the optimal parameters for using the flash & its partitions. Include the soc-nv-flash binding in STM32 External NOR Flash binding so that those two properties can be specified in the external Flash node in board DT. Until now, the workaround for STM32 boards using MCUboot has been to disable CONFIG_BOOT_MAX_IMG_SECTORS_AUTO in MCUboot's board extra conf and to set CONFIG_BOOT_MAX_IMG_SECTORS manually depending on the app slot size & the NOR Flash sector size. Signed-off-by: Abderrahmane JARMOUNI <[email protected]>
Pull in the necessary MCUboot bits, will be removed before merging the PR. Signed-off-by: Abderrahmane JARMOUNI <[email protected]>
JarmouniA
force-pushed
the
fix_h750b-dk_ext_flash_app
branch
from
95ac7ff to
573417e
Compare
|
The following west manifest projects have changed revision in this Pull Request:
Additional metadata changed:
⛔ DNM label due to: 1 project with PR revision and 1 project with metadata changes Note: This message is automatically posted and updated by the Manifest GitHub Action. |
github-actions
bot
added
manifest
manifest-mcuboot
DNM (manifest)
JarmouniA
force-pushed
the
fix_h750b-dk_ext_flash_app
branch
from
573417e to
00106a2
Compare
Introduce a board variant for storing an app in external QSPI NOR Flash and chainloading it with MCUboot (placed in internal Flash) to be executed either in place (XiP) (set by default, MCUBOOT_MODE_DIRECT_XIP) or to be loaded to RAM and be executed there (MCUBOOT_MODE_RAM_LOAD). The new variant requires a board DT overlay on the MCUboot side to set the internal Flash & Flash controller as the chosen 'zephyr,flash' & 'zephyr,flash-controller'. Signed-off-by: Abderrahmane JARMOUNI <[email protected]>
Add stm32h750b_dk/stm32h750xx/ext_flash_app target to CI platforms Signed-off-by: Abderrahmane JARMOUNI <[email protected]>
Add stm32h750b_dk/stm32h750xx/ext_flash_app target to CI platforms. Signed-off-by: Abderrahmane JARMOUNI <[email protected]>
JarmouniA
force-pushed
the
fix_h750b-dk_ext_flash_app
branch
from
00106a2 to
b26dafd
Compare
|
Please retry analysis of this Pull-Request directly on SonarQube Cloud |
zephyrbot
added
area: Samples
zephyrbot
requested review from
djiatsaf-st,
etienne-lms,
FRASTM,
gautierg-st,
GeorgeCGV,
kartben,
marwaiehm-st,
mathieuchopstm,
nordicjm,
rghaddab and
tejlmand
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Introduce a board variant for storing an app in external QSPI NOR Flash and chainloading it with MCUboot (which is placed in internal Flash) to be executed either in place (XiP) (MCUBOOT_MODE_DIRECT_XIP, set by default in board's
Kconfig.sysbuild) or to be loaded to RAM and be executed there (MCUBOOT_MODE_RAM_LOAD).The ext Flash memory partition also allows for using the Swap-using-offset & swap-using-move MCUboot image upgrade algorithms, eventhough it's not optimal as it has same-sized slots.
The new variant requires a board DT overlay on the MCUboot side (mcu-tools/mcuboot#2479) to set the internal Flash & Flash controller as the chosen 'zephyr,flash' & 'zephyr,flash-controller'. This way, no overlay will be needed at the Zephyr user app level.