Lines Matching refs:to
4 acquired the ability to be used as a bootloader for Zephyr as well.
19 It is not recommended to use the swap-using-scratch algorithm of MCUboot, but
22 and how to use the swap-using-scratch algorithm):
44 cd ~/mcuboot # or to your directory where MCUboot is cloned
51 Zephyr's point of view. There is a bit of configuration that needs to
54 guidance. It is important to select a signature algorithm, and decide
65 In addition to the partitions defined in DTS, some additional
66 information about the flash layout is currently required to build
75 to flash these binaries from the build directory. Depending
77 memory (mass erase) or only the sectors where the bootloader resides prior to
82 In addition to flash partitions in DTS, some additional configuration
83 is required to build applications for MCUboot.
91 board and then just make a copy of it to get started on your own
96 provides additional details regarding the changes it makes to the image
97 placement and generation in order for an application to be bootable by MCUboot.
103 In order to upgrade to an image (or even boot it, if
106 keys. It is important to stress that these should never be used for
108 repository. See below on how to make your own signatures.
111 to look at `samples/zephyr/Makefile` for examples on how to use this.
116 need to be programmed at the offset of the primary slot for this particular
117 target. Depending on the platform and flash tool you might need to manually
118 specify a flash offset corresponding to the primary slot starting address. This
121 information. Additionally you will need to make sure that the flash tool does
125 at which point the bootloader should perform an upgrade. It is up to
126 the image to mark the primary slot as "image ok" before the next reboot,
133 `scripts/imgtool.py` is able to generate key pairs in all of the
146 The argument to `-t` should be the desired key type. See the
152 key. It is necessary to extract the public key and insert it into the
153 bootloader. Use the ``CONFIG_BOOT_SIGNATURE_KEY_FILE`` Kconfig option to
154 provide the path to the key file so the build system can extract
159 Currently, the Zephyr RTOS port limits its support to one keypair at the time,
163 example) can be used to sign images.
167 To use the swap-using-scratch flash algorithm, a scratch partition needs to be
175 needs adding to the .dts file for the board, e.g. for the nrf52dk_nrf52832
202 times per image upgrade/revert). To configure MCUboot to work in
206 Note that it is possible for an application to get into a stuck state when
219 Which interface belongs to the protocol shall be set by the devicetree-chosen node:
225 To enter the serial recovery mode, the device has to initiate rebooting, and a triggering event has…
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…
231 Select ``CONFIG_BOOT_SERIAL_WAIT_FOR_DFU=y`` to use this mode. ``CONFIG_BOOT_SERIAL_WAIT_FOR_DFU_TI…
240 The mapping of image number to partition is as follows:
250 Use the ``CONFIG_ENABLE_MGMT_PERUSER=y`` Kconfig option to enable the following additional commands: