Lines Matching full:mcuboot

1 # Building and using MCUboot with Zephyr
3 MCUboot began its life as the bootloader for Mynewt.  It has since
15 - `boot_partition`: for MCUboot itself
19 It is not recommended to use the swap-using-scratch algorithm of MCUboot, but
27 MCUboot as your stage 1 bootloader, `boot_partition` must be configured
41 Install additional packages required for development with MCUboot:
44   cd ~/mcuboot  # or to your directory where MCUboot is cloned
57 To build MCUboot, create a build directory in boot/zephyr, and build
67 MCUboot itself. All the needed configuration is collected in
70 MCUboot on a per-SoC family basis.
83 is required to build applications for MCUboot.
89 The directory `samples/zephyr/hello-world` in the MCUboot tree contains
97 placement and generation in order for an application to be bootable by MCUboot.
105 To make development easier, MCUboot is distributed with some example
123 deleting MCUboot.
131 The signing keys used by MCUboot are represented in standard formats,
160 although MCUboot's key management infrastructure supports multiple keypairs.
162 Once MCUboot is built, this new keypair file (`mykey.pem` in this
181         label = "mcuboot";
202 times per image upgrade/revert). To configure MCUboot to work in
208 and marked it as test/confirmed but MCUboot will not swap the images and
228 Use the ``mcuboot_button0`` devicetree button alias to assign the GPIO pin to the MCUboot.
230 Alternatively, MCUboot can wait for a limited time to check if DFU is invoked by receiving an MCUmg…
238 …PDATEABLE_IMAGE_NUMBER`` Kconfig option adjusts the number of image-pairs supported by the MCUboot.