samples: bluetooth: mesh: target: Add a note how to create new cdp0

Add a note how to easily create a new composition data and see how device becomes unprovisioned after DFU. Signed-off-by: Pavel Vasilyev <[email protected]>
nrfconnect · Apr 8, 2024 · 41b7795 · 41b7795
1 parent d1a087d
commit 41b7795
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 0 deletions.
diff --git a/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst b/doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
@@ -251,6 +251,10 @@ Bluetooth Mesh samples
 
   * Added support for the :ref:`zephyr:nrf54l15pdk_nrf54l15` board.
 
+* :ref:`ble_mesh_dfu_target` sample:
+
+  * Added a note on how to compile the sample with new Composition Data.
+
 Cellular samples
 ----------------
 

diff --git a/samples/bluetooth/mesh/dfu/target/README.rst b/samples/bluetooth/mesh/dfu/target/README.rst
@@ -167,6 +167,9 @@ Only 2 options are supported by this sample:
    In this case, the device unprovisions itself before programming the new firmware.
    The unprovisioning happens before the device reboots, so if the MCUboot fails to validate the new firmware, the device will boot unprovisioned anyway.
 
+.. note::
+   To create the new Composition Data and see the :c:enum:`BT_MESH_DFU_EFFECT_UNPROV` effect, you can, for example, turn off the Friend feature in the :file:`prj.conf` file by setting the :kconfig:option:`CONFIG_BT_MESH_FRIEND` option to ``n``.
+
 In this sample, the device flash is split into partitions using the :ref:`partition_manager`.
 When the DFU transfer starts, the sample stores the new firmware at the MCUboot secondary slot using the :ref:`zephyr:flash_map_api`.