Boards: STM32H750B-DK: Introduce App in Ext Flash variant #97037
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
Member
erwango
left a comment
erwango
left a comment
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.
Contributor
Author
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... |
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:
✅ All manifest checks OK 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
2 times, most recently
from
00106a2 to
b26dafd
Compare
zephyrbot
added
area: Samples
zephyrbot
requested review from
57300,
FRASTM,
GeorgeCGV,
d3zd3z,
de-nordic,
djiatsaf-st,
etienne-lms,
gautierg-st and
kartben
erwango
approved these changes
Oct 21, 2025
erwango
requested changes
Oct 21, 2025
boards/st/stm32h750b_dk/stm32h750b_dk_stm32h750xx_ext_flash_app.dts
Outdated
Show resolved
Hide resolved
Contributor
Author
|
@erwango You should probably take the PR assignment, as it is only touching STM32 area (except for the minor tests' changes to add the board variant to |
JarmouniA
force-pushed
the
fix_h750b-dk_ext_flash_app
branch
from
519cd25 to
693af83
Compare
erwango
previously approved these changes
Oct 21, 2025
Contributor
Author
|
@etienne-lms Could you take a look, thanks! |
maass-hamburg
requested changes
Oct 22, 2025
JarmouniA
force-pushed
the
fix_h750b-dk_ext_flash_app
branch
from
693af83 to
00aedda
Compare
maass-hamburg
previously approved these changes
Oct 22, 2025
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 in place (uses MCUboot's swap-using-offset mode, set via Sysbuild). The new variant requires on MCUboot app side: a board/SoC DT overlay to set the internal Flash & Flash controller as the chosen 'zephyr,flash' & 'zephyr,flash-controller', and CONFIG_STM32_MEMMAP=y (this was upstreamed to MCUboot.) Change external Flash memory attribute "zephyr,memory-attr" to DT_MEM_ARM_MPU_FLASH, since ATTR_MPU_IO (corresponds to "DEVICE_NON_SHAREABLE & P_RW_U_NA") is actually for memory-mapped devices (with registers...) and was causing access issues with apps like LVGL that would freeze the target. Also, change the size of the external flash "zephyr,memory-region" node, since we only need to define accesss rights to the memory space actually used by the external flash chips, not the total addresssable QSPI memory. The 2nd QSPI NOR contoller node was removed, since it does not reflect the actual hardware layout, that has only one controller and the 2 NOR flash chips are connected to it in parallel with a shift register. Signed-off-by: Abderrahmane JARMOUNI <git@jarmouni.me>
Add stm32h750b_dk/stm32h750xx/ext_flash_app target to CI platforms Signed-off-by: Abderrahmane JARMOUNI <git@jarmouni.me>
Add stm32h750b_dk/stm32h750xx/ext_flash_app target to CI platforms. Signed-off-by: Abderrahmane JARMOUNI <git@jarmouni.me>
Add stm32h750b_dk/stm32h750xx/ext_flash_app target to CI platforms of the Hawkbit sample. Signed-off-by: Abderrahmane JARMOUNI <git@jarmouni.me>
JarmouniA
force-pushed
the
fix_h750b-dk_ext_flash_app
branch
from
00aedda to
ba20a2e
Compare
|
erwango
reviewed
Oct 23, 2025
erwango
approved these changes
Oct 23, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
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 in place (XiP).
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.
Board doc preview https://builds.zephyrproject.io/zephyr/pr/97037/docs/boards/st/stm32h750b_dk/doc/index.html