Lines Matching +full:image +full:- +full:0
3 .. zephyr:code-sample:: smp-svr
53 Bluetooth Low Energy (BLE) and do not have a built-in or pluggable BLE radio,
55 :ref:`bluetooth-hci-uart-bluez`.
66 .. code-block:: console
68 west build -b <board> -d build_mcuboot bootloader/mcuboot/boot/zephyr
69 west flash -d build_mcuboot
84 .. group-tab:: Bluetooth
88 .. code-block:: console
91 -b nrf52dk/nrf52832 \
93 -- \
94 -DEXTRA_CONF_FILE=overlay-bt.conf
96 .. group-tab:: Serial
98 To build the serial sample with file-system and shell management support:
100 .. code-block:: console
103 -b frdm_k64f \
105 -- \
106 -DEXTRA_CONF_FILE='overlay-serial.conf;overlay-fs.conf;overlay-shell-mgmt.conf'
108 .. group-tab:: USB CDC_ACM
112 .. code-block:: console
115 -b nrf52840dk/nrf52840 \
117 -- \
118 -DEXTRA_CONF_FILE=overlay-cdc.conf \
119 -DDTC_OVERLAY_FILE=usb.overlay
121 .. group-tab:: Shell
125 .. code-block:: console
128 -b frdm_k64f \
130 -- \
131 -DEXTRA_CONF_FILE='overlay-shell.conf'
133 .. group-tab:: UDP
141 .. code-block:: console
144 -b frdm_k64f \
146 -- \
147 -DEXTRA_CONF_FILE=overlay-udp.conf
151 Signing the sample image
157 To sign the sample image built in the previous step:
159 .. code-block:: console
161 west sign -t imgtool -- --key bootloader/mcuboot/root-rsa-2048.pem
163 The above command creates an image file called :file:`zephyr.signed.bin` in the
166 For more information on image signing and ``west sign``, see the :ref:`west-sign`
169 Flashing the sample image
172 Upload the :file:`zephyr.signed.bin` file from the previous to image slot-0 of your
175 To upload the initial image file to an empty slot-0, use ``west flash`` like normal.
176 ``west flash`` will automatically detect slot-0 address and confirm the image.
178 .. code-block:: console
180 west flash --bin-file build/zephyr/zephyr.signed.bin
182 The *signed* image file needs to be used specifically, otherwise the non-signed version
183 will be used and the image won't be runnable.
185 Sample image: hello world!
192 J-Link Virtual MSD Interaction Note
195 On boards where a J-Link OB is present which has both CDC and MSC (virtual Mass
196 Storage Device, also known as drag-and-drop) support, the MSD functionality can
198 endpoints are configured in the J-Link firmware (for example on the Nordic
200 when using image management commands for updating firmware). This issue can be
201 resolved by disabling MSD functionality on the J-Link device, follow the
209 "OTA DFU", or Over-The-Air Device Firmware Upgrade. This works for both BT and UDP.
214 * Sign the application image, see :ref:`smp_svr_sample_sign`
215 * Upload the signed image using :file:`mcumgr`
217 * Mark the uploaded image for testing using :file:`mcumgr`
219 * Confirm the uploaded image using :file:`mcumgr` (optional)
221 Direct image upload and Image mapping to MCUboot slot
225 into MCUboot primary (slot-0) and secondary (slot-1) respectively.
227 For clarity, here is DTS label to slot to ``<image>`` translation table:
229 +-----------+--------+------------+
230 | DTS label | Slot | -n <image> |
232 | "image-0" | slot-0 | 1 |
233 +-----------+--------+------------+
234 | "image-1" | slot-1 | 0, 1 |
235 +-----------+--------+------------+
236 | "image-2" | | 2 |
237 +-----------+--------+------------+
238 | "image-3" | | 3 |
239 +-----------+--------+------------+
241 Upload the signed image
244 To upload the signed image, refer to the documentation for your chosen tool, select the new
250 the image slot, taking several dozen seconds for some targets.
255 A list of images (slot-0 and slot-1) that are present can now be obtained on the remote target devi…
259 Test the image
262 In order to instruct MCUboot to swap the images, the image needs to be tested first, making sure it
264 image.
267 There is not yet any way of getting the image hash without actually uploading the
268 image and getting the hash.
274 check the documentation in the tool of your choice. Upon reset MCUboot will swap slot-0 and
275 slot-1.
277 Confirm new image
280 The new image is now loaded into slot-0, but it will be swapped back into slot-1 on the next
281 reset unless the image is confirmed. Confirm the image using the tool of your choice.
283 Note that if you try to send the very same image that is already flashed in
284 slot-0 then the procedure will not complete successfully since the hash values
292 non-volatile memory. Build and flash both MCUboot and smp_svr applications and