Skip to content

modules: Add Kconfigs for bootloader requests #93669

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

modules: Add Kconfigs for bootloader requests #93669

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
26 changes: 26 additions & 0 deletions modules/Kconfig.mcuboot
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -331,6 +331,32 @@ config BOOT_IMAGE_ACCESS_HOOKS
It is up to the application project to add source file which
implements hooks to the build.

config MCUBOOT_BOOT_REQUEST
bool "MCUboot bootloader requests"
help
Handle bootloader requests.

if MCUBOOT_BOOT_REQUEST

choice MCUBOOT_BOOT_REQUEST_IMPL
prompt "Shared memory backend"
default MCUBOOT_BOOT_REQUEST_IMPL_RETENTION if RETENTION

config MCUBOOT_BOOT_REQUEST_IMPL_RETENTION
bool "Retention"
depends on RETENTION
help
Use zephyr,bootloader-request chosen node compatible with the
zephyr,retention driver as the memory area to store and read from the
bootloader requests.
The built-in prefix property should be used to indicate the request
structure version to ensure compatibility between the bootloader and
the application.

endchoice

endif # MCUBOOT_BOOT_REQUEST

if MCUBOOT_BOOTLOADER_MODE_DIRECT_XIP_WITH_REVERT

config MCUBOOT_BOOTUTIL_LIB_FOR_DIRECT_XIP
Expand Down
Loading