Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions boot/zephyr/boards/stm32h750b_dk.conf

This file was deleted.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder why this has to be applied to a stm32h750b_dk/stm32h750xx/ext_flash_app target.
My understanding of zephyrproject-rtos/zephyr#97037, is that stm32h750b_dk/stm32h750xx is the target running on internal flash.

This way, we re-use zephyr,flash and zephyr,flash-controller, which are already defined for stm32h750b_dk.dts. And since zephyr,code-partition = &boot_partition; is already defined in app.overlay we don't have any dependency on MCUBoot anymore

Copy link
Author

@JarmouniA JarmouniA Oct 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The memory layout for running a user app from external Flash is in ext_flash_app variant dts, and we use stm32h750b_dk/stm32h750xx/ext_flash_app target when building with sysbuild.

Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
/ {
chosen {
zephyr,flash = &flash0;
zephyr,flash-controller = &flash;
zephyr,code-partition = &boot_partition;
};
};