Skip to content

boot: zephyr: boards config of the variant stm32 disco kit #2399

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

FRASTM
Copy link
Contributor

@FRASTM FRASTM commented Jul 23, 2025

Define the stm32 disco board variant configuration to set the STM32 XIP mode that will enable the MemoryMapped mode. See Kconfig of the stm32 soc. Choose the mcu_boot partition where to build ../bootloader/mcuboot/boot/zephyr
The zephyr, chosen zephyr,flash = &flash0; is in the board dts. The zephyr,code-partition = &boot_partition; is given by the app.overlay

FRASTM added a commit to FRASTM/zephyr that referenced this pull request Jul 23, 2025
Takes the mcu-tools/mcuboot#2399

Signed-off-by: Francois Ramu <francois.ramu@st.com>
FRASTM added a commit to FRASTM/zephyr that referenced this pull request Jul 28, 2025
Takes the mcu-tools/mcuboot#2399

Signed-off-by: Francois Ramu <francois.ramu@st.com>
Define the stm32 disco board variant configuration to set
the STM32 XIP mode that will enable the MemoryMapped mode.
See Kconfig of the stm32 soc. Choose the mcu_boot partition
where to build ../bootloader/mcuboot/boot/zephyr
The zephyr, chosen zephyr,flash = &flash0; is in the board dts.
The zephyr,code-partition = &boot_partition; is given by the app.overlay

Signed-off-by: Francois Ramu <francois.ramu@st.com>
@FRASTM FRASTM force-pushed the stm32_xip_mcuboot branch from b673070 to 3a10f90 Compare July 28, 2025 15:21
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.

1 participant