| /Zephyr-Core-3.5.0/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
51 string "Path to the mcuboot signing key file"
[all …]
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/samples/application_development/sysbuild/with_mcuboot/ |
| D | README.rst | 3 Sample with MCUboot
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_nrf52840
50 The first ``Booting Zephyr OS build`` is printed by MCUboot itself and the
|
| D | sample.yaml | 2 description: Sample with MCUboot built through sysbuild
3 name: with mcuboot
14 tags: mcuboot
20 - "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-Core-3.5.0/doc/develop/west/ |
| D | sign.rst | 12 MCUboot / imgtool
16 the `MCUboot`_ bootloader using the `imgtool`_ program provided by its
24 Here is an example workflow, which builds and flashes MCUboot, as well as the
25 :ref:`hello_world` application for chain-loading by MCUboot. Run these commands
31 west build -b YOUR_BOARD bootloader/mcuboot/boot/zephyr -d build-mcuboot
34 -DCONFIG_MCUBOOT_SIGNATURE_KEY_FILE=\"bootloader/mcuboot/root-rsa-2048.pem\"
36 west flash -d build-mcuboot
43 provided and used by by MCUboot for development and testing
45 application that can be loaded by MCUboot, such as the :zephyr:code-sample:`smp-svr` sample.
50 MCUboot
[all …]
|
| /Zephyr-Core-3.5.0/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 | testcase.yaml | 13 bootloader.mcuboot:
14 tags: mcuboot
23 bootloader.mcuboot.assert:
24 tags: 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)
|
| /Zephyr-Core-3.5.0/subsys/dfu/ |
| D | Kconfig | 23 So far only mcuboot support is available.
26 bool "Image manager for mcuboot"
30 Enable support for managing DFU image downloaded using mcuboot.
35 bool "MCUboot shell"
50 "Fix double swap on interrupted revert" mcuboot patch
51 (https://github.com/JuulLabs-OSS/mcuboot/pull/485)
53 of MCUBoot.
88 if !MCUBOOT
95 application is combined with MCUboot multi-image boot.
|
| /Zephyr-Core-3.5.0/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 */
86 * @brief MCUboot image header representation for image version
88 * The header for an MCUboot firmware image contains an embedded
[all …]
|
| /Zephyr-Core-3.5.0/share/sysbuild/images/bootloader/ |
| D | CMakeLists.txt | 5 # Include MCUboot if enabled.
7 set(image mcuboot)
13 # MCUBoot default configuration is to perform a full chip erase.
14 # Placing MCUBoot first in list to ensure it is flashed before other images.
|
| D | Kconfig | 24 bool "MCUboot"
27 Include MCUboot (Zephyr port) as the bootloader to use
65 Absolute path to signing key file to use with MCUBoot.
81 Absolute path to encryption key file to use with MCUBoot.
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/tests/boot/mcuboot_recovery_retention/ |
| D | testcase.yaml | 24 bootloader.mcuboot.recovery.retention:
27 - mcuboot
30 bootloader.mcuboot.recovery.retention.mem:
38 - mcuboot
|
| /Zephyr-Core-3.5.0/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-Core-3.5.0/boards/arm/nrf52840dongle_nrf52840/doc/ |
| D | index.rst | 117 2. Using MCUboot in serial recovery mode
170 Option 2: Using MCUboot in Serial Recovery Mode
173 It is also possible to use the MCUboot bootloader with this board to flash
175 MCUboot on your board. From that point on, you can build and flash other Zephyr
176 applications using MCUboot's serial recovery mode. This process does not
180 Install `nrfutil`_ and `mcumgr`_ first, and make sure MCUboot's ``imgtool`` is
181 available for signing your binary for MCUboot as described on :ref:`west-sign`.
183 Next, do the **one-time setup** to flash MCUboot. We'll assume you've cloned
184 the `MCUboot`_ repository into the directory ``mcuboot``, and that it is next
189 #. Compile MCUboot as a Zephyr application.
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/nrf52840dongle_nrf52840/ |
| 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 | 19 # When building MCUBoot, MCUBoot itself will select USE_DT_CODE_PARTITION
26 depends on BOARD_HAS_NRF5_BOOTLOADER && (MCUBOOT || !USE_DT_CODE_PARTITION)
40 default y if !MCUBOOT && CONSOLE
|
| /Zephyr-Core-3.5.0/boards/arm/efr32_thunderboard/ |
| D | efr32bg22_brd4184.dtsi | 17 /* If enabled, MCUboot uses this for recovery mode entrance */
18 mcuboot-led0 = &led0;
19 mcuboot-button0 = &button0;
31 label = "mcuboot";
|
| /Zephyr-Core-3.5.0/modules/trusted-firmware-m/ |
| D | Kconfig.tfm | 58 default "${ZEPHYR_TRUSTED_FIRMWARE_M_MODULE_DIR}/bl2/ext/mcuboot/root-RSA-3072.pem"
67 default "${ZEPHYR_TRUSTED_FIRMWARE_M_MODULE_DIR}/bl2/ext/mcuboot/root-RSA-3072_1.pem"
183 Hidden option to mark the BL2, the MCUBoot included in TF-M, as not supported.
190 MCUBoot may be configured to prevent rollback prevention based on image
198 MCUBoot may be configured to prevent rollback prevention based on image
203 bool "Add MCUboot to TFM"
207 TFM is designed to run with MCUboot in a certain configuration.
208 This config adds MCUboot to the build - built via TFM's build system.
260 prompt "Path to MCUboot or DOWNLOAD to fetch automatically"
263 Path to MCUboot for TF-M builds. The default option
[all …]
|
| /Zephyr-Core-3.5.0/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 child image, using sysbuild's
78 the sysbuild target is prefixed with ``sysbuild_`` and if MCUboot is enabled
160 The following example shows how to build :ref:`hello_world` with MCUboot enabled,
298 To debug a different domain (Zephyr application), such as ``mcuboot``, use
301 west debug --domain mcuboot
305 Building a sample with MCUboot
308 Sysbuild supports MCUboot natively.
310 To build a sample like ``hello_world`` with MCUboot,
[all …]
|
| /Zephyr-Core-3.5.0/samples/subsys/mgmt/mcumgr/smp_svr/ |
| D | README.rst | 30 * The MCUboot bootloader is required for ``img_mgmt`` to function
32 MCUboot can be found in :ref:`mcuboot`.
59 Building and flashing MCUboot
62 The below steps describe how to build and run the MCUboot bootloader.
63 Detailed instructions can be found in the :ref:`mcuboot` documentation page.
65 The Zephyr port of MCUboot is essentially a normal Zephyr application, which means that
70 west build -b <board> -d build_mcuboot bootloader/mcuboot/boot/zephyr
156 A key feature of MCUboot is that images must be signed before they can be successfully
157 uploaded and run on a target. To sign images, the MCUboot tool :file:`imgtool` can be used.
163 west sign -t imgtool -- --key bootloader/mcuboot/root-rsa-2048.pem
[all …]
|
| /Zephyr-Core-3.5.0/tests/boot/with_mcumgr/pytest/ |
| D | test_upgrade.py | 28 Path(build_dir) / 'mcuboot' / 'zephyr' / '.config',
44 1) Device flashed with MCUboot and an application that contains SMP server
98 Verify that MCUboot will roll back an image that is not confirmed
99 1) Device flashed with MCUboot and an application that contains SMP server
106 8) Verify that MCUboot reverts update
147 logger.info('Verify that MCUboot reverts update')
160 1) Device flashed with MCUboot and an application that contains SMP server
164 b) with a different key than MCUboot was compiled with
171 Path(dut.device_config.build_dir) / 'mcuboot' / 'zephyr' / '.config',
|
