Skip to content

Conversation

@nvlsianpu
Copy link
Contributor

@nvlsianpu nvlsianpu commented Nov 19, 2025

@nvlsianpu nvlsianpu requested review from a team as code owners November 19, 2025 15:43
@github-actions
Copy link

You can find the documentation preview for this PR here.

@nvlsianpu nvlsianpu changed the title Retentionloader DFU: support for App -> Loader ADV name setup over settings retention backend Nov 19, 2025
@nvlsianpu nvlsianpu added this to the v1.0.0 milestone Nov 19, 2025
@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
3 Security Hotspots

See analysis details on SonarQube Cloud

@nvlsianpu nvlsianpu changed the title DFU: support for App -> Loader ADV name setup over settings retention backend [WIP] DFU: support for App -> Loader ADV name setup over settings retention backend Nov 20, 2025
@nvlsianpu nvlsianpu force-pushed the retentionloader branch 4 times, most recently from 7dde0be to aaa5c05 Compare November 21, 2025 17:19
@nvlsianpu nvlsianpu requested a review from a team as a code owner November 21, 2025 18:32
@github-actions github-actions bot added the doc-required PR must not be merged without tech writer approval. label Nov 21, 2025
@nvlsianpu nvlsianpu changed the title [WIP] DFU: support for App -> Loader ADV name setup over settings retention backend DFU: support for App -> Loader ADV name setup over settings retention backend Nov 21, 2025
@nvlsianpu nvlsianpu force-pushed the retentionloader branch 5 times, most recently from c2e85d1 to fca3dfa Compare November 25, 2025 10:38
@nvlsianpu nvlsianpu requested a review from peknis November 25, 2025 10:39
@@ -0,0 +1,18 @@
#
# Copyright (c) 2023 Nordic Semiconductor ASA
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# Copyright (c) 2023 Nordic Semiconductor ASA
# Copyright (c) 2025 Nordic Semiconductor ASA

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was copied from zephtr-rtos. What time stamp should be there.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was copied from zephtr-rtos. What time stamp should be there.

Up to you.

Comment on lines 18 to 20
1.
To enable this feature for a sysbuild project, use the :kconfig:option:`SB_CONFIG_BM_APP_CAN_SETUP_FIRMWARE_LOADER_NAME` Kconfig option.
Otherwise, enable the following Kconfig options in both the application and the firmware loader configuration:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1.
To enable this feature for a sysbuild project, use the :kconfig:option:`SB_CONFIG_BM_APP_CAN_SETUP_FIRMWARE_LOADER_NAME` Kconfig option.
Otherwise, enable the following Kconfig options in both the application and the firmware loader configuration:
To enable this feature for a sysbuild project, use the :kconfig:option:`SB_CONFIG_BM_APP_CAN_SETUP_FIRMWARE_LOADER_NAME` Kconfig option.
Also enable the following Kconfig options in both the application and the firmware loader configuration:

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise - Alternatively?
I mean that actually SB_CONFIG_BM_APP_CAN_SETUP_FIRMWARE_LOADER_NAME enables all of these CONFIG_xyx.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively sounds better.

* :kconfig:option:`CONFIG_SETTINGS_RETENTION`- Enables retention backend implementation of settings subsystem.
* :kconfig:option:`CONFIG_NCS_BM_SETTINGS_BLUETOOTH_NAME`- Enables setting handlers required for Bluetooth name sharing support.

#.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
#.

Comment on lines 33 to 35
Usage example
*************

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Usage example
*************

@nvlsianpu nvlsianpu force-pushed the retentionloader branch 2 times, most recently from 4308f64 to 699da59 Compare November 26, 2025 08:38
Copy link

@peknis peknis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with a couple of nits.

********************

To enable this feature for a sysbuild project, use the :kconfig:option:`SB_CONFIG_BM_APP_CAN_SETUP_FIRMWARE_LOADER_NAME` Kconfig option.
Otherwise, enable the following Kconfig options in both the application and the firmware loader configuration:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Otherwise, enable the following Kconfig options in both the application and the firmware loader configuration:
Alternatively, enable the following Kconfig options in both the application and the firmware loader configuration:

* :kconfig:option:`CONFIG_SETTINGS_RETENTION`- Enables retention backend implementation of settings subsystem.
* :kconfig:option:`CONFIG_NCS_BM_SETTINGS_BLUETOOTH_NAME`- Enables setting handlers required for Bluetooth name sharing support.

Additionally, the application must enable the MCUmgr settings group using the following Kconfig options:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Additionally, the application must enable the MCUmgr settings group using the following Kconfig options:
Additionally, the application must enable the MCUmgr settings group using the following Kconfig options:

@@ -0,0 +1,18 @@
#
# Copyright (c) 2023 Nordic Semiconductor ASA
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was copied from zephtr-rtos. What time stamp should be there.

Up to you.

nordicjm and others added 7 commits November 27, 2025 10:46
Adds a settings subsystem file to add a bluetooth name setting

Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
Allows usage of this from BM applications

Files taken from zephyr commit:
  0fe59bf1e4b96122c3467295b09a034e399c5ee6

Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
Adds code to get bluetooth name from retention backend of
the settings subsystem.

Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
Adds code to set bluetooth name to retention settings

Signed-off-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
Added enabler for coherent setup of the BLE name from the application
to the firmware loader using the settings subsystem with retention memory
backend.

Applied usage of this to configuration of the mcuboot_recovery_entry sample
and the BLE firmware loader.

Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
Documented feature of setup the firmware loader BLE name by the remote
MCUmgr client using the application's MCUmgr and the settings.

Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
Signed-off-by: Pekka Niskanen <pekka.niskanen@nordicsemi.no>
Assigns this to eris

Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

doc-required PR must not be merged without tech writer approval.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants