samples: bluetooth: mesh: add ble dfu as file suffix to light sample

Commit changes adding the dfu feature to mesh light sample.
DFU is added as FILE_SUFFIX sysbuild configuration.

Signed-off-by: Aleksandr Khromykh <aleksandr.khromykh@nordicsemi.no>

Author: alxelax

samples/bluetooth/mesh/light/README.rst

@@ -35,7 +35,7 @@ The sample also requires a smartphone with Nordic Semiconductor's nRF Mesh mobil
 DFU requirements
 ================
 
-The configuration overlay file :file:`overlay-dfu.conf` and the :ref:`sysbuild <configuration_system_overview_sysbuild>` configuration file :file:`sysbuild-dfu.conf` enable DFU support in the application, and apply to the following platforms:
+The configuration file :file:`prj_dfu.conf` and the :ref:`sysbuild <configuration_system_overview_sysbuild>` configuration file :file:`sysbuild_dfu.conf` enable DFU support in the application, and apply to the following platforms:
 
 * nrf52840dk/nrf52840
 * nrf21540dk/nrf52840
@@ -134,36 +134,20 @@ This sample is split into the following source files:
 DFU configuration
 =================
 
-.. tabs::
+To enable the DFU feature, use ``FILE_SUFFIX=dfu`` when building the sample.
+For example, when building from the command line, use the following command, where *board_target* is the target for the development kit for which you are building:
 
-   .. tab:: nRF52840 DK and nRF54L15 DK
+.. parsed-literal::
+   :class: highlight
 
-      To enable the DFU feature for the nRF52840 and nRF54L15 development kits, set :makevar:`SB_CONF_FILE` to :file:`sysbuild-dfu.conf` and :makevar:`EXTRA_CONF_FILE` to :file:`overlay-dfu.conf` when building the sample.
-      For example, when building from the command line, use the following command, where *board_target* is the target for the development kit for which you are building:
+   west build -b *board_target* -p -- -DFILE_SUFFIX=dfu
 
-      .. parsed-literal::
-         :class: highlight
+The configuration file :file:`prj_dfu.conf` and the sysbuild configuration file :file:`sysbuild_dfu.conf` enable the DFU feature.
+To review the required configuration alterations, open and inspect the two files.
 
-         west build -b *board_target* -p -- -DSB_CONF_FILE="sysbuild-dfu.conf" -DEXTRA_CONF_FILE="overlay-dfu.conf"
-
-      The configuration overlay file :file:`overlay-dfu.conf` and the sysbuild configuration file :file:`sysbuild-dfu.conf` enable the DFU feature.
-      To review the required configuration alterations, open and inspect the two files.
-
-   .. tab:: nRF5340 DK
-
-      To enable the DFU feature for the nRF5340 development kit, set :makevar:`SB_CONF_FILE` to :file:`sysbuild-dfu.conf` and :makevar:`EXTRA_CONF_FILE` to :file:`overlay-dfu.conf` when building the sample.
-      Additionally, you need to set the :makevar:`EXTRA_CONF_FILE` for the ipc_radio network image to :file:`overlay-dfu.conf` as well.
-      This is an additional network image specific configuration overlay file, which allocates the necessary resources to enable the DFU feature.
-      For example, when building from the command line, use the following command, where *board_target* is the target for the development kit for which you are building:
-
-      .. parsed-literal::
-         :class: highlight
-
-         west build -b *board_target* -p -- -DSB_CONF_FILE="sysbuild-dfu.conf" -DEXTRA_CONF_FILE="overlay-dfu.conf" -Dipc_radio_EXTRA_CONF_FILE="overlay-dfu.conf"
-
-      .. note::
-         Currently, the nRF5340 development kit only supports DFU for the application core.
-         This implies that all application DFU images must be compatible with the network core image running on the device.
+.. note::
+   Currently, the nRF5340 development kit only supports DFU for the application core.
+   This implies that all application DFU images must be compatible with the network core image running on the device.
 
 For more information about configuration files in the |NCS|, see :ref:`app_build_system`.
 
@@ -216,7 +200,7 @@ Make sure to complete the configuration on each of the elements on the node to e
 Running DFU
 ===========
 
-After the sample is built with the :file:`overlay-dfu.conf` file and the :file:`sysbuild-dfu.conf` file, and programmed to your development kit, support for FOTA update is enabled.
+After the sample is built with ``FILE_SUFFIX=dfu`` and programmed to your development kit, support for FOTA update is enabled.
 See :ref:`FOTA over Bluetooth Low Energy<ug_nrf52_developing_ble_fota>` for instructions on how to perform FOTA update and initiate the DFU process.
 
 External flash for settings partition

samples/bluetooth/mesh/light/boards/nrf5340dk_nrf5340_cpuapp_ns.overlay

@@ -5,51 +5,31 @@
  */
 
 /* Rebalance secure/non-secure subpartitions to fit larger mesh light NS image.
- * Aligned slot0/slot1 addresses and sizes to MCUboot defaults
- * (nrf5340_cpuapp_partition.dtsi): each slot is 0x74000 (464 KB).
- * Secure: 192 KB, Non-secure: 272 KB.
+ * MCUboot is removed; slot0 starts at 0x0 and spans 928 KB (0xe8000).
+ * Secure: 128 KB, Non-secure: 800 KB.
  */
 
+/delete-node/ &boot_partition;
 /delete-node/ &slot0_partition;
-/delete-node/ &slot1_partition;
 
 &flash0 {
 	partitions {
-		slot0_partition: partition@10000 {
+		slot0_partition: partition@0 {
 			compatible = "fixed-subpartitions";
 			label = "image-0";
-			reg = <0x10000 0x74000>;
-			ranges = <0x0 0x10000 0x74000>;
+			reg = <0x00000000 0xe8000>;
+			ranges = <0x0 0x0 0xe8000>;
 			#address-cells = <1>;
 			#size-cells = <1>;
 
 			slot0_s_partition: partition@0 {
 				label = "image-0-secure";
-				reg = <0x0 0x30000>;
+				reg = <0x00000000 0x20000>;
 			};
 
-			slot0_ns_partition: partition@30000 {
+			slot0_ns_partition: partition@20000 {
 				label = "image-0-nonsecure";
-				reg = <0x30000 0x44000>;
-			};
-		};
-
-		slot1_partition: partition@84000 {
-			compatible = "fixed-subpartitions";
-			label = "image-1";
-			reg = <0x84000 0x74000>;
-			ranges = <0x0 0x84000 0x74000>;
-			#address-cells = <1>;
-			#size-cells = <1>;
-
-			slot1_s_partition: partition@0 {
-				label = "image-1-secure";
-				reg = <0x0 0x30000>;
-			};
-
-			slot1_ns_partition: partition@30000 {
-				label = "image-1-nonsecure";
-				reg = <0x30000 0x44000>;
+				reg = <0x00020000 0xc8000>;
 			};
 		};
 	};

samples/bluetooth/mesh/light/boards/nrf5340dk_nrf5340_cpuapp_ns_dfu.overlay

@@ -0,0 +1,56 @@
+/*
+ * Copyright (c) 2026 Nordic Semiconductor ASA
+ *
+ * SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
+ */
+
+/* Rebalance secure/non-secure subpartitions to fit larger mesh light NS image.
+ * Aligned slot0/slot1 addresses and sizes to MCUboot defaults
+ * (nrf5340_cpuapp_partition.dtsi): each slot is 0x74000 (464 KB).
+ * Secure: 192 KB, Non-secure: 272 KB.
+ */
+
+/delete-node/ &slot0_partition;
+/delete-node/ &slot1_partition;
+
+&flash0 {
+	partitions {
+		slot0_partition: partition@10000 {
+			compatible = "fixed-subpartitions";
+			label = "image-0";
+			reg = <0x10000 0x74000>;
+			ranges = <0x0 0x10000 0x74000>;
+			#address-cells = <1>;
+			#size-cells = <1>;
+
+			slot0_s_partition: partition@0 {
+				label = "image-0-secure";
+				reg = <0x0 0x30000>;
+			};
+
+			slot0_ns_partition: partition@30000 {
+				label = "image-0-nonsecure";
+				reg = <0x30000 0x44000>;
+			};
+		};
+
+		slot1_partition: partition@84000 {
+			compatible = "fixed-subpartitions";
+			label = "image-1";
+			reg = <0x84000 0x74000>;
+			ranges = <0x0 0x84000 0x74000>;
+			#address-cells = <1>;
+			#size-cells = <1>;
+
+			slot1_s_partition: partition@0 {
+				label = "image-1-secure";
+				reg = <0x0 0x30000>;
+			};
+
+			slot1_ns_partition: partition@30000 {
+				label = "image-1-nonsecure";
+				reg = <0x30000 0x44000>;
+			};
+		};
+	};
+};

…oards/nrf54l15dk_nrf54l10_cpuapp.overlay …s/nrf54l15dk_nrf54l10_cpuapp_dfu.overlaysamples/bluetooth/mesh/light/boards/nrf54l15dk_nrf54l10_cpuapp.overlay renamed to samples/bluetooth/mesh/light/boards/nrf54l15dk_nrf54l10_cpuapp_dfu.overlay samples/bluetooth/mesh/light/boards/nrf54l15dk_nrf54l10_cpuapp.overlay renamed to samples/bluetooth/mesh/light/boards/nrf54l15dk_nrf54l10_cpuapp_dfu.overlay

@@ -0,0 +1,81 @@
+#
+# Copyright (c) 2026 Nordic Semiconductor ASA
+#
+# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
+#
+CONFIG_NCS_SAMPLES_DEFAULTS=y
+
+# Deferred logging helps improve LPN power consumption
+# when friendship is established.
+CONFIG_LOG_MODE_DEFERRED=y
+
+# General configuration
+CONFIG_NCS_APPLICATION_BOOT_BANNER_STRING="Mesh Light"
+CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=3072
+CONFIG_FLASH=y
+CONFIG_FLASH_MAP=y
+CONFIG_NVS=y
+CONFIG_SETTINGS=y
+CONFIG_NVS_LOOKUP_CACHE=y
+CONFIG_SETTINGS_NVS_NAME_CACHE=y
+CONFIG_HWINFO=y
+CONFIG_DK_LIBRARY=y
+CONFIG_SOC_FLASH_NRF_PARTIAL_ERASE=y
+
+# Bluetooth configuration
+CONFIG_BT=y
+CONFIG_BT_DEVICE_NAME="Mesh Light"
+CONFIG_BT_L2CAP_TX_BUF_COUNT=8
+
+CONFIG_BT_OBSERVER=y
+CONFIG_BT_PERIPHERAL=y
+CONFIG_BT_SETTINGS=y
+# Increase RX stack size to avoid overflow during provisioning
+CONFIG_BT_RX_STACK_SIZE=2700
+
+# Disable unused Bluetooth features
+CONFIG_BT_CTLR_LE_ENC=n
+CONFIG_BT_PHY_UPDATE=n
+CONFIG_BT_CTLR_CHAN_SEL_2=n
+CONFIG_BT_CTLR_MIN_USED_CHAN=n
+CONFIG_BT_CTLR_PRIVACY=n
+
+# Bluetooth Mesh configuration
+CONFIG_BT_MESH=y
+CONFIG_BT_MESH_RELAY=y
+CONFIG_BT_MESH_FRIEND=y
+CONFIG_BT_MESH_TX_SEG_MAX=10
+CONFIG_BT_MESH_PB_GATT=y
+CONFIG_BT_MESH_GATT_PROXY=y
+CONFIG_BT_MESH_PROXY_USE_DEVICE_NAME=y
+CONFIG_BT_MESH_DK_PROV=y
+
+# Bluetooth Mesh models
+CONFIG_BT_MESH_ONOFF_SRV=y
+
+# === BLE DFU configuration ===
+# Enable point to point DFU over SMP
+CONFIG_BOOTLOADER_MCUBOOT=y
+CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y
+CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU_SPEEDUP=y
+CONFIG_MCUMGR_TRANSPORT_WORKQUEUE_STACK_SIZE=3072
+# Enable Extended Advertiser to advertise BT SMP service
+CONFIG_BT_EXT_ADV=y
+CONFIG_BT_EXT_ADV_MAX_ADV_SET=6
+
+# One extra connection for mesh GATT/proxy and one for SMP BT.
+CONFIG_BT_MAX_CONN=3
+
+# One extra identity for SMP service
+CONFIG_BT_ID_MAX=2
+
+# Increase the HCI command buffers to 3 for additional SMP service
+CONFIG_BT_BUF_CMD_TX_COUNT=3
+
+# Enable MCUmgr command hooks for doing mesh reset when doing dfu upgrade and storage erase
+CONFIG_MCUMGR_MGMT_NOTIFICATION_HOOKS=y
+CONFIG_MCUMGR_SMP_COMMAND_STATUS_HOOKS=y
+CONFIG_MCUMGR_GRP_OS_RESET_HOOK=y
+
+# Force disconnect after PB-GATT provisioning for proper Proxy transition after DFU
+CONFIG_BT_MESH_DK_PROV_PB_GATT_DISCONNECT=y

…oards/nrf54l15dk_nrf54l15_cpuapp.overlay …s/nrf54l15dk_nrf54l15_cpuapp_dfu.overlaysamples/bluetooth/mesh/light/boards/nrf54l15dk_nrf54l15_cpuapp.overlay renamed to samples/bluetooth/mesh/light/boards/nrf54l15dk_nrf54l15_cpuapp_dfu.overlay samples/bluetooth/mesh/light/boards/nrf54l15dk_nrf54l15_cpuapp.overlay renamed to samples/bluetooth/mesh/light/boards/nrf54l15dk_nrf54l15_cpuapp_dfu.overlay

@@ -40,9 +40,7 @@ tests:
       - nrf54lm20dk/nrf54lm20a/cpuapp
       - nrf5340dk/nrf5340/cpuapp
       - nrf5340dk/nrf5340/cpuapp/ns
-    extra_args:
-      - EXTRA_CONF_FILE=overlay-dfu.conf
-      - SB_CONF_FILE=sysbuild-dfu.conf
+    extra_args: FILE_SUFFIX=dfu
   sample.bluetooth.mesh.light.settings_ext_flash:
     sysbuild: true
     build_only: true