Skip to content

Commit c11cd3d

Browse files
akredalenBalaklaka
authored andcommitted
doc: samples: bluetooth: mesh: small update in DFU procedure
Updated DFU Target and DFU Distributor procedure descriptions. Signed-off-by: Stine Åkredalen <[email protected]>
1 parent f446215 commit c11cd3d

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed

samples/bluetooth/mesh/dfu/distributor/README.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -183,11 +183,11 @@ Then, in the mobile app, do the following:
183183

184184
* Find and select the :guilabel:`Mesh DFU Distributor` device.
185185
* Go to the :guilabel:`Image` tab.
186-
* Press the :guilabel:`ADVANCED` button in the right top corner.
186+
* Tap the :guilabel:`Advanced` button in the right top corner.
187187
This will allow uploading the image to slot-1 without swapping the image on the Distributor.
188-
* Under the :guilabel:`Firmware Upload` area, press the :guilabel:`SELECT FILE` button and select the copied image.
189-
* Press the :guilabel:`UPLOAD` button.
190-
* Select :guilabel:`Application Core (0)` and tap :guilabel:`OK`.
188+
* Under the :guilabel:`Image Upload` area, tap the :guilabel:`Select File` button and select the copied image.
189+
* Tap the :guilabel:`Start` button.
190+
* Select :guilabel:`target.signed.bin`.
191191

192192
Once the image upload is done, the :guilabel:`State` field is set to UPLOAD COMPLETE.
193193

samples/bluetooth/mesh/dfu/target/README.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,9 @@ The sample can also be the Target node updated by any firmware image that is com
141141
In both cases, the firmware needs to be signed and the firmware version increased to pass the validation when the MCUboot swaps the images.
142142

143143
To set a new version, alter the Kconfig option :kconfig:option:`CONFIG_MCUBOOT_IMGTOOL_SIGN_VERSION` to a version that is higher than the default version of: ``"1.0.0+0"``.
144-
Then, after rebuilding the sample, the binary of the updated sample can be found in :file:`samples/bluetooth/mesh_dfu/target/build/zephyr/app_update.bin`.
144+
Then, after rebuilding the sample, the binary of the updated sample can be found in :file:`samples/bluetooth/mesh/dfu/target/build/target/zephyr/zephyr.signed.bin` or
145+
:file:`samples/bluetooth/mesh/dfu/target/build/dfu_application.zip`.
146+
The file format to use depends on the tool you are using for the DFU procedure.
145147

146148
To perform a DFU with this sample, the following additional information is required:
147149

0 commit comments

Comments
 (0)