Skip to content

sample/boot/mcuboot_recovery_entry: update README file #546

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eivindj-nordic merged 1 commit into from
Dec 9, 2025
Merged

sample/boot/mcuboot_recovery_entry: update README file #546

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions doc/nrf-bm/app_dev/dfu/dfu_name.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,9 @@
Setting up DFU Device Bluetooth name remotely
#############################################

.. note::
The support for this feature is currently experimental.

The Device Firmware Update (DFU) over Bluetooth® Low Energy in the single bank solution uses the loader application for firmware download support.
The firmware loader is separate application to which the remote Bluetooth LE DFU client connects to perform the firmware update.
To identify the firmware loader application over Bluetooth LE, it uses a specific advertising name provided by the remote client to the application.
Expand Down
6 changes: 4 additions & 2 deletions samples/boot/mcuboot_recovery_entry/README.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,7 @@ Overview
After the application boots, it begins advertising as ``nRF_BM_Entry``, advertising the MCUmgr service.

A mobile device can then connect and issue the OS mgmt reset command with the optional ``boot_mode`` parameter provided and set to 1.
Before the reset, the mobile device can also set up the advertising name of the firmware loader using the MCUmgr settings management commands.
The command sets the retention register for entering the firmware loader mode and reboots the device.
It then starts advertising the MCUmgr service allowing for a firmware update to be loaded.

Expand Down Expand Up @@ -76,8 +77,9 @@ Testing
#. Observe in the terminal that the device boots into application mode and then advertises with the default name ``nRF_BM_Entry``.
#. Connect to your device using the `nRF Connect Device Manager`_ mobile application.
#. Under the :guilabel:`image` tab, tap :guilabel:`Advanced`.
Then, in the reset control pane, select :guilabel:`Switch to bootloader mode` and tap :guilabel:`Send Reset Command`.
Observe in the terminal that the device reboots into Firmware Loader mode and advertises with the default Firmware Loader name ``nRF_BM_MCUmgr``.
#. In the reset control panel, select :guilabel:`Switch to Firmware Loader mode`.
Optionally, specify the advertising name in the text field below and tap :guilabel:`Send Reset Command`.
#. Observe in the terminal that the device reboots into the Firmware Loader mode and advertises with the advertising name specified or the default Firmware Loader name ``nRF_BM_MCUmgr``.
#. Using the `nRF Connect Device Manager`_ mobile application, go back to the device list and refresh it by swiping down.
Connect to your device that now advertises with the default firmware loader name ``nRF_BM_MCUmgr``.
#. Under the :guilabel:`image` tab, tap :guilabel:`Advanced`.
Expand Down