| /Zephyr-latest/modules/ |
| D | Kconfig.mcuboot | 8 config MCUBOOT config
11 Hidden option used to indicate that the current image is MCUBoot
14 bool "MCUboot bootloader support"
17 depends on !MCUBOOT
19 This option signifies that the target uses MCUboot as a bootloader,
20 or in other words that the image is to be chain-loaded by MCUboot.
22 order for the image generated to be bootable using the MCUboot open
26 for the MCUboot image header
33 the application. This removes the need by MCUboot to reset
39 string "Path to the mcuboot signing key file"
[all …]
|
| /Zephyr-latest/share/sysbuild/images/bootloader/ |
| D | Kconfig | 24 bool "MCUboot"
27 Include MCUboot (Zephyr port) as the bootloader to use
37 The operating mode of MCUboot (which will also be propagated to the application).
42 MCUboot will only boot slot0_partition placed application and does not care about other
44 all updates need to be performed using MCUboot serial recovery.
50 MCUboot expects slot0_partition and slot1_partition to be present in DT and application
52 in main application if MCUboot has been built with MCUBOOT_DOWNGRADE_PREVENTION.
57 MCUboot expects slot0_partition and slot1_partition to be present in DT and application
59 in main application if MCUboot has been built with MCUBOOT_DOWNGRADE_PREVENTION.
70 MCUboot expects slot0_partition, slot1_partition and scratch_partition to be present in
[all …]
|
| D | CMakeLists.txt | 5 # Include MCUboot if enabled.
7 set(image mcuboot)
13 # Place MCUBoot first in list to ensure it is configured and flashed before other images.
|
| /Zephyr-latest/samples/sysbuild/with_mcuboot/ |
| D | README.rst | 2 :name: MCUboot with sysbuild
4 Build a Zephyr application + MCUboot using sysbuild.
9 automatically include MCUboot as the bootloader.
16 This sample automatically includes MCUboot as bootloader when built using
25 The :file:`sysbuild/mcuboot.conf` file will be used as an extra fragment that
26 is merged together with the default configuration files used by MCUboot.
28 :file:`sysbuild/mcuboot.conf` adjusts the log level in MCUboot, as well as
29 configures MCUboot to prevent downgrades and operate in upgrade-only mode.
31 To build both the sample and MCUboot with ``west`` for the ``reel_board``, run:
48 Hello sysbuild with mcuboot! nrf52840dk
[all …]
|
| D | sample.yaml | 2 description: Sample with MCUboot built through sysbuild
3 name: with mcuboot
24 tags: mcuboot
30 - "Hello sysbuild with mcuboot!(.*)"
|
| D | CMakeLists.txt | 8 # Verify that this samnple is built through sysbuild to ensure MCUboot is
9 # automatically included and that sample specific MCUboot configurations are
10 # used when building MCUboot.
|
| /Zephyr-latest/doc/services/device_mgmt/ |
| D | dfu.rst | 37 MCUBoot API
40 The MCUboot API is provided to get version information and boot status of
54 MCUboot subsection
58 `MCUboot boot loader`_. It interfaces with MCUboot and is aware of the image
59 format required by it, so that Device Firmware Upgrade is available when MCUboot
61 `MCUboot GitHub Project`_ page.
63 In order to use MCUboot with Zephyr you need to take the following into account:
65 1. You will need to define the flash partitions required by MCUboot; see
79 be built in an MCUboot-compatible manner
80 4. You need to build and flash MCUboot itself on your device
[all …]
|
| D | ota.rst | 17 The :ref:`dfu` section discusses upgrading Zephyr firmware using MCUboot. The
20 upgraded using the :ref:`mcuboot` process.
32 TLS/DTLS, and the signed firmware binary is confirmed by MCUboot before the
44 is downloaded and installed. MCUboot can be used to verify the signature before
55 the binary is downloaded and installed. MCUboot can be used to verify the
66 firmware binary to the remote device where it is verified by MCUboot before the
80 .. _MCUboot bootloader: https://mcuboot.com/
|
| /Zephyr-latest/tests/boot/test_mcuboot/ |
| D | README.rst | 1 MCUBoot Swap Testing
4 Tests MCUBoot's image swap support. This application is built in three parts
5 using sysbuild. The first application is the MCUBoot bootloader. The second
7 from MCUBoot when booted. The third application is build with a load address
9 that MCUBoot swaps to when the image swap is requested.
11 This sequence of applications allows the test to verify support for the MCUBoot
|
| D | sysbuild.cmake | 4 # Add the mcuboot key file to the secondary swapped app
19 # - mcuboot
23 # iterations, the MCUBoot swap won't be triggered until the secondary app
26 sysbuild_add_dependencies(FLASH swapped_app mcuboot)
|
| D | testcase.yaml | 3 tags: mcuboot
14 bootloader.mcuboot:
50 bootloader.mcuboot.assert:
55 bootloader.mcuboot.swap_using_offset:
|
| /Zephyr-latest/doc/build/signing/ |
| D | index.rst | 10 MCUboot / imgtool
13 The Zephyr build system has special support for signing binaries for use with the `MCUboot`_
18 Here is an example workflow, which builds and flashes MCUboot, as well as the
19 :zephyr:code-sample:`hello_world` application for chain-loading by MCUboot. Run these commands
32 - The singing key value is the insecure default provided and used by MCUboot for development
35 loaded by MCUboot, such as the :zephyr:code-sample:`smp-svr` sample.
39 - ``SB_CONFIG_BOOTLOADER_MCUBOOT``: build the application for loading by MCUboot
56 [00:00:00.004,669] <inf> mcuboot: Starting bootloader
57 …[00:00:00.011,169] <inf> mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_…
58 [00:00:00.021,636] <inf> mcuboot: Boot source: none
[all …]
|
| /Zephyr-latest/subsys/dfu/ |
| D | Kconfig | 24 So far only mcuboot support is available.
27 bool "Image manager for mcuboot"
31 Enable support for managing DFU image downloaded using mcuboot.
38 bool "MCUboot shell"
50 "Fix double swap on interrupted revert" mcuboot patch
51 (https://github.com/JuulLabs-OSS/mcuboot/pull/485)
53 of MCUBoot.
60 that MCUboot cannot update due to being too large. This should be set from sysbuild, only
95 if !MCUBOOT
102 application is combined with MCUboot multi-image boot.
|
| /Zephyr-latest/include/zephyr/dfu/ |
| D | mcuboot.h | 10 * @brief MCUboot public API for MCUboot control of image boot process
26 * @brief MCUboot public API for MCUboot control of image boot process
28 * @defgroup mcuboot_api MCUboot image control API
38 #if BOOT_SWAP_TYPE_NONE != 1 /*ensure the same definition in MCUboot */
47 #if BOOT_SWAP_TYPE_TEST != 2 /*ensure the same definition in MCUboot */
56 #if BOOT_SWAP_TYPE_PERM != 3 /*ensure the same definition in MCUboot */
65 #if BOOT_SWAP_TYPE_REVERT != 4 /*ensure the same definition in MCUboot */
74 #if BOOT_SWAP_TYPE_FAIL != 5 /*ensure the same definition in MCUboot */
88 * @brief MCUboot image header representation for image version
90 * The header for an MCUboot firmware image contains an embedded
[all …]
|
| /Zephyr-latest/boards/ct/ctcc/doc/ |
| D | index.rst | 93 2. Using `MCUboot`_ with MCUmgr support
119 Option 2: Using MCUboot with MCUmgr support
122 It is also possible to use the MCUboot bootloader with :ref:`mcu_mgr` support to flash
126 and make sure MCUboot's ``imgtool`` is available for signing your binary
127 for MCUboot as described on :ref:`west-sign`.
129 #. Compile MCUboot as a Zephyr application with ``MCUmgr`` support.
135 To build the MCUboot:
138 :app: mcuboot/boot/zephyr
140 :build-dir: mcuboot
145 To build the MCUboot:
[all …]
|
| /Zephyr-latest/tests/boot/mcuboot_recovery_retention/ |
| D | testcase.yaml | 22 bootloader.mcuboot.recovery.retention:
25 - mcuboot
28 bootloader.mcuboot.recovery.retention.mem:
36 - mcuboot
|
| /Zephyr-latest/subsys/retention/ |
| D | Kconfig.blinfo | 16 bool "MCUboot"
17 depends on !MCUBOOT && BOOTLOADER_MCUBOOT
21 Adds a bootloader information sharing system for MCUboot and
23 MCUboot and the running image. This can be used by applications so
28 the "zephyr,bootloader-info" chosen node via device tree, MCUboot
|
| /Zephyr-latest/samples/subsys/usb/dfu/ |
| D | README.rst | 19 partition layout. You SoC must run MCUboot as the stage 1 bootloader.
20 This sample is built as an application for the MCUboot bootloader.
43 -DCONFIG_MCUBOOT_SIGNATURE_KEY_FILE=\"bootloader/mcuboot/root-rsa-2048.pem\"
45 Build and flash MCUboot bootloader for Zephyr project as it is described in
46 the `Using MCUboot with Zephyr`_ documentation. Then build, sign and flash
52 in :ref:`mcuboot`). For example:
57 …-DCONFIG_BOOTLOADER_MCUBOOT=y '-DCONFIG_MCUBOOT_SIGNATURE_KEY_FILE="bootloader/mcuboot/root-rsa-20…
77 Reset the SoC. MCUboot boot will swap the images and boot the new application,
94 Reset the SoC again and MCUboot should revert the images and boot
125 For example via a debugger or Mcuboot's recovery mode.
[all …]
|
| /Zephyr-latest/samples/subsys/usb/dfu-next/ |
| D | README.rst | 64 It is also possible to try the sample together with the MCUboot bootloader
65 library. The following example shows how to build MCUboot and this sample with
66 flash backend and MCUboot support enabled using the :ref:`sysbuild`:
80 option (as described in :ref:`mcuboot`). For example:
85 …:gen-args: -DCONFIG_MCUBOOT_SIGNATURE_KEY_FILE=\"bootloader/mcuboot/root-rsa-2048.pem\" -DCONFIG_B…
94 Reset the SoC. MCUboot boot will swap the images and boot the new application,
99 *** Booting MCUboot v2.1.0-rc1-134-gb9d69dd2a2d6 ***
114 Reset the SoC again and MCUboot should revert the images and boot
119 *** Booting MCUboot v2.1.0-rc1-134-gb9d69dd2a2d6 ***
137 .. _Using MCUboot with Zephyr: https://docs.mcuboot.com/readme-zephyr
|
| /Zephyr-latest/boards/nordic/nrf52840dongle/doc/ |
| D | index.rst | 117 2. Using MCUboot in serial recovery mode
176 Option 2: Using MCUboot in Serial Recovery Mode
179 It is also possible to use the MCUboot bootloader with this board to flash
181 MCUboot on your board. From that point on, you can build and flash other Zephyr
182 applications using MCUboot's serial recovery mode. This process does not
186 Install `nrfutil`_ and `mcumgr`_ first, and make sure MCUboot's ``imgtool`` is
187 available for signing your binary for MCUboot as described on :ref:`west-sign`.
189 Next, do the **one-time setup** to flash MCUboot. We'll assume you've cloned
190 the `MCUboot`_ repository into the directory ``mcuboot``, and that it is next
195 #. Compile MCUboot as a Zephyr application.
[all …]
|
| /Zephyr-latest/boards/nordic/nrf52840dongle/ |
| D | fstab-stock.dtsi | 15 /* MCUboot placed after Nordic MBR (this is set with the FLASH_LOAD_OFFSET
16 * Kconfig value when BOARD_HAS_NRF5_BOOTLOADER is enabled), otherwise MCUboot
17 * will be placed at 0x0. The size of this partition ensures that MCUBoot can
21 label = "mcuboot";
|
| D | Kconfig.defconfig | 16 # When building MCUBoot, MCUBoot itself will select USE_DT_CODE_PARTITION
23 depends on BOARD_HAS_NRF5_BOOTLOADER && (MCUBOOT || !USE_DT_CODE_PARTITION)
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 12 with the MCUboot bootloader, flash them both onto your device, and
67 instruct sysbuild to build the MCUboot bootloader, as well as to build and
68 link your main Zephyr application as an MCUboot-bootable image, using sysbuild's
78 the sysbuild target is prefixed with ``sysbuild_`` and if MCUboot is enabled
179 The following example shows how to build :zephyr:code-sample:`hello_world` with MCUboot enabled,
317 To debug a different domain (Zephyr application), such as ``mcuboot``, use
320 west debug --domain mcuboot
324 Building a sample with MCUboot
327 Sysbuild supports MCUboot natively.
329 To build a sample like ``hello_world`` with MCUboot,
[all …]
|
| /Zephyr-latest/boards/others/promicro_nrf52840/ |
| D | Kconfig.defconfig | 17 # When building MCUBoot, MCUBoot itself will select USE_DT_CODE_PARTITION
24 depends on BOARD_HAS_NRF5_BOOTLOADER && (MCUBOOT || !USE_DT_CODE_PARTITION)
|
| /Zephyr-latest/tests/boot/mcuboot_data_sharing/ |
| D | testcase.yaml | 9 bootloader.mcuboot.data.sharing:
12 - mcuboot
|
