You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/nrf-bm/app_dev/dfu/dfu_name.rst
+3-8Lines changed: 3 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,15 +7,14 @@ The Device Firmware Update (DFU) over Bluetooth® Low Energy in the single bank
7
7
The firmware loader is separate application to which the remote Bluetooth LE DFU client connects to perform the firmware update.
8
8
To identify the firmware loader application over Bluetooth LE, it uses a specific advertising name provided by the remote client to the application.
9
9
10
-
You can configure the name at application runtime using the MCUmgr settings commands group.
10
+
You can configure the name at application runtime using the MCUmgr settings command group.
11
11
12
12
Write the name using the MCUmgr write setting request for ``fw_loader/adv_name`` key and export the key value to retention memory using the MCUmgr save settings request.
13
-
Once the device is rebooted into the firmware loader application, the name can be read back from the retention memory and use as the advertising name of the firmware loader.
13
+
Once the device is rebooted into the firmware loader application, the name can be read back from the retention memory and used as the advertising name of the firmware loader.
14
14
15
15
Enabling the feature
16
16
********************
17
17
18
-
1.
19
18
To enable this feature for a sysbuild project, use the :kconfig:option:`SB_CONFIG_BM_APP_CAN_SETUP_FIRMWARE_LOADER_NAME` Kconfig option.
20
19
Otherwise, enable the following Kconfig options in both the application and the firmware loader configuration:
21
20
@@ -25,12 +24,8 @@ Otherwise, enable the following Kconfig options in both the application and the
25
24
* :kconfig:option:`CONFIG_SETTINGS_RETENTION`- Enables retention backend implementation of settings subsystem.
26
25
* :kconfig:option:`CONFIG_NCS_BM_SETTINGS_BLUETOOTH_NAME`- Enables setting handlers required for Bluetooth name sharing support.
27
26
28
-
#.
29
-
Additionally, the application must enabled the MCumgr settings group by enabling the following Kconfig option:
27
+
Additionally, the application must enable the MCUmgr settings group using the following Kconfig options:
30
28
* :kconfig:option:`CONFIG_MCUMGR_GRP_SETTINGS`- Enables the MCUmgr settings group.
31
29
* :kconfig:option:`CONFIG_SETTINGS_RUNTIME`- Allows runtime modification of settings.
32
30
33
-
Usage example
34
-
*************
35
-
36
31
This feature is used in the :ref:`ble_mcuboot_recovery_entry_sample`.
0 commit comments