doc: Align sample folder names accoording to sample names

Align sample folder names accoording to sample names as mentioned in the RSTs

Signed-off-by: Uma Praseeda <[email protected]>

.github/test-spec.yml

@@ -137,7 +137,7 @@
   - "samples/cellular/fmfu_smp_svr/**/*"
   - "samples/cellular/http_update/**/*"
   - "samples/nrf5340/netboot/*"
-  - "samples/bootloader/**/*"
+  - "samples/nsib/**/*"
   - "scripts/bootloader/**/*"
   - "subsys/bootloader/**/*"
   - "subsys/nonsecure/*"
@@ -161,7 +161,7 @@
   - "modules/trusted-firmware-m/*"
   - "samples/nrf5340/netboot/**/*"
   - "samples/nrf5340/extxip_smp_svr/**/*"
-  - "samples/bootloader/**/*"
+  - "samples/nsib/**/*"
   - "scripts/bootloader/**/*"
   - "subsys/bootloader/**/*"
   - "subsys/nonsecure/*"

CODEOWNERS

@@ -422,7 +422,7 @@
 /samples/app_event_manager_profiler_tracer/ @nrfconnect/ncs-si-muffin @nrfconnect/ncs-si-bluebagel
 /samples/benchmarks/coremark/             @nrfconnect/ncs-si-bluebagel
 /samples/bluetooth/nrf_auraconfig/        @nrfconnect/ncs-audio
-/samples/bluetooth/central_and_peripheral_hr/ @nrfconnect/ncs-si-muffin
+/samples/bluetooth/central_and_peripheral_hrs/ @nrfconnect/ncs-si-muffin
 /samples/bluetooth/central_bas/           @nrfconnect/ncs-si-muffin
 /samples/bluetooth/central_hids/          @nrfconnect/ncs-si-bluebagel
 /samples/bluetooth/central_hr_coded/      @nrfconnect/ncs-si-muffin
@@ -471,7 +471,7 @@
 /samples/bluetooth/shell_bt_nus/          @nrfconnect/ncs-si-muffin
 /samples/bluetooth/subrating/             @nrfconnect/ncs-dragoon
 /samples/bluetooth/throughput/            @nrfconnect/ncs-si-muffin
-/samples/bootloader/                      @nrfconnect/ncs-pluto
+/samples/nsib/                            @nrfconnect/ncs-pluto
 /samples/caf/                             @nrfconnect/ncs-si-muffin @nrfconnect/ncs-si-bluebagel
 /samples/caf_sensor_manager/              @nrfconnect/ncs-si-muffin @nrfconnect/ncs-si-bluebagel
 /samples/cellular/                        @nrfconnect/ncs-co-networking @nrfconnect/ncs-modem
@@ -482,7 +482,7 @@
 /samples/cellular/modem_shell/            @trantanen @jhirsi @tokangas
 /samples/cellular/nidd/                   @stig-bjorlykke
 /samples/cellular/nrf_cloud_*             @nrfconnect/ncs-nrf-cloud
-/samples/cellular/nrf_provisioning/       @nrfconnect/ncs-iot-oulu
+/samples/cellular/nrf_device_provisioning/ @nrfconnect/ncs-iot-oulu
 /samples/cellular/modem_trace_flash/      @nrfconnect/ncs-modem
 /samples/cellular/slm_shell/              @nrfconnect/ncs-iot-oulu
 /samples/cellular/sms/                    @trantanen @tokangas

applications/serial_lte_modem/sysbuild/b0/prj.conf

@@ -4,7 +4,7 @@
 # SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
 #
 
-# b0 defaults from /samples/bootloader/prj.conf
+# b0 defaults from /samples/nsib/prj.conf
 CONFIG_IS_SECURE_BOOTLOADER=y
 CONFIG_MULTITHREADING=n
 CONFIG_GPIO=n

doc/_utils/redirects.py

@@ -399,6 +399,12 @@
     ("samples/samples_bl", "samples/bl"), # Bluetooth samples (landing)
     ("samples/bluetooth/connection_event_trigger/README", "samples/bluetooth/event_trigger/README"),
     ("samples/bluetooth/broadcast_config_tool/README", "samples/bluetooth/nrf_auraconfig/README"),
+    ("samples/bluetooth/central_and_peripheral_hr/README", "samples/bluetooth/central_and_peripheral_hrs/README"), # Renamed the folders to better match the sample names
+    ("samples/bootloader/README", "samples/nsib/README"),
+    ("samples/cellular/nrf_provisioning/README", "samples/cellular/nrf_device_provisioning/README"),
+    ("samples/bluetooth/mesh/light_ctrl/README", "samples/bluetooth/mesh/light_fixture/README"),
+    ("samples/bluetooth/mesh/sensor_client/README", "samples/bluetooth/mesh/sensor_observer/README"),
+    ("samples/cellular/lte_ble_gateway/README", "samples/cellular/lte_sensor_gateway/README"),
     ("samples/samples_nrf9160", "samples/cellular"), # Cellular samples (landing)
     ("samples/samples_crypto", "samples/crypto"), # Cryptography samples (landing)
     ("samples/samples_edge", "samples/edge"), # Edge Impulse samples (landing)

doc/_zoomin/ncs.tags.yml

@@ -378,7 +378,7 @@ mapping_topics:
   - nrf/libraries/networking/nrf_cloud_log.html: ["nrf-cloud"]
   - nrf/libraries/networking/nrf_cloud_pgps.html: ["nrf-cloud"]
   - nrf/libraries/networking/nrf_cloud_rest.html: ["nrf-cloud"]
-  - nrf/libraries/networking/nrf_provisioning.html: ["at-commands"]
+  - nrf/libraries/networking/nrf_device_provisioning.html: ["at-commands"]
   - nrf/libraries/networking/softap_wifi_provision: ["wifi", "nrf70-series", "nrf7002", "nrf7001",
                                                      "nrf7000"]
   - nrf/libraries/networking/lwm2m_client_utils.html: ["lte"]

doc/nrf/app_dev/bootloaders_dfu/mcuboot_nsib/bootloader_config.rst

@@ -9,7 +9,7 @@ Customizing the bootloader
 
 By default, to set Kconfig options, the |NSIB| and MCUboot bootloaders use Kconfig project configuration files, usually called :file:`prj.conf`, located in their source directories:
 
-* |NSIB| - :file:`nrf/samples/bootloader`
+* |NSIB| - :file:`nrf/samples/nsib`
 * MCUboot - :file:`bootloader/mcuboot/boot/zephyr`
 
 However, there are other ways to customize your application using Kconfig options:

doc/nrf/app_dev/companion_components.rst

@@ -47,7 +47,7 @@ The following table lists the available companion components:
    * - :ref:`bootloader`
      - Bootloader tailored for the :ref:`two-stage bootloader <immutable_bootloader>`.
      - :ref:`Bootloader requirements <bootloader_rot>`
-     - :file:`samples/bootloader`
+     - :file:`samples/nsib`
      - :ref:`ug_bootloader_adding_immutable_b0`
    * - :ref:`SUIT flash companion <suit_flash_companion>`
      - Companion image that allows the Secure Domain Firmware to access the external memory during the :ref:`Software Updates for Internet of Things (SUIT) <ug_nrf54h20_suit_dfu>` firmware upgrade.

doc/nrf/app_dev/config_and_build/multi_image.rst

@@ -284,7 +284,7 @@ See :ref:`ug_bootloader` for more details.
 .. note::
 
    The build system grabs the Kconfig fragment or configuration file specified in a CMake argument relative to that image's application directory.
-   For example, the build system uses ``nrf/samples/bootloader/my-fragment.conf`` when building with the ``-Db0_EXTRA_CONF_FILE=my-fragment.conf`` option, whereas ``-DEXTRA_CONF_FILE=my-fragment.conf`` grabs the fragment from the main application's directory, such as ``zephyr/samples/hello_world/my-fragment.conf``.
+   For example, the build system uses file:`nrf/samples/nsib/my-fragment.conf` when building with the ``-Db0_EXTRA_CONF_FILE=my-fragment.conf`` option, whereas ``-DEXTRA_CONF_FILE=my-fragment.conf`` grabs the fragment from the main application's directory, such as ``zephyr/samples/hello_world/my-fragment.conf``.
 
 You can also merge multiple fragments into the overall configuration for an image by giving a list of Kconfig fragments as a string, separated using ``;``.
 The following example shows how to combine ``abc.conf``, Kconfig fragment of the ``childimageone`` child image, with the ``extrafragment.conf`` fragment:
@@ -327,7 +327,7 @@ The build system does also automatically apply any devicetree overlay located in
 .. note::
 
    The build system grabs the devicetree overlay files specified in a CMake argument relative to that image's application directory.
-   For example, the build system uses ``nrf/samples/bootloader/my-dts.overlay`` when building with the ``-Db0_DTC_OVERLAY_FILE=my-dts.overlay`` option, whereas ``-DDTC_OVERLAY_FILE=my-dts.overlay`` grabs the fragment from the main application's directory, such as ``zephyr/samples/hello_world/my-dts.overlay``.
+   For example, the build system uses ``nrf/samples/nsib/my-dts.overlay`` when building with the ``-Db0_DTC_OVERLAY_FILE=my-dts.overlay`` option, whereas ``-DDTC_OVERLAY_FILE=my-dts.overlay`` grabs the fragment from the main application's directory, such as ``zephyr/samples/hello_world/my-dts.overlay``.
 
 .. _ug_multi_image_permanent_changes:
 

samples/bluetooth/central_and_peripheral_hr/CMakeLists.txt → samples/bluetooth/central_and_peripheral_hrs/CMakeLists.txt

@@ -5,7 +5,7 @@
 #
 cmake_minimum_required(VERSION 3.20.0)
 find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
-project(central_and_peripheral_hr)
+project(central_and_peripheral_hrs)
 
 # NORDIC SDK APP START
 target_sources(app PRIVATE

samples/bluetooth/central_and_peripheral_hr/README.rst → samples/bluetooth/central_and_peripheral_hrs/README.rst

@@ -80,7 +80,7 @@ User interface
 
 Building and running
 ********************
-.. |sample path| replace:: :file:`samples/bluetooth/central_and_peripheral_hr`
+.. |sample path| replace:: :file:`samples/bluetooth/central_and_peripheral_hrs`
 
 .. include:: /includes/build_and_run_ns.txt
 
@@ -174,15 +174,15 @@ Testing with Bluetooth Low Energy app
       #. Open the `Bluetooth Low Energy app`_ and select the connected dongle that is used for communication.
       #. Open the **SERVER SETUP** tab.
       #. Click the dongle configuration and select :guilabel:`Load setup`.
-      #. Load the :file:`hr_service.ncs` file that is located under :file:`samples/bluetooth/central_and_peripheral_hr` in the |NCS| folder structure.
+      #. Load the :file:`hr_service.ncs` file that is located under :file:`samples/bluetooth/central_and_peripheral_hrs` in the |NCS| folder structure.
       #. Click :guilabel:`Apply to device`.
       #. Open the **CONNECTION MAP** tab.
       #. Click the dongle configuration (gear icon) and select :guilabel:`Advertising setup`.
 
          The current version of nRF Connect can store the advertising setup.
 
       #. Click :guilabel:`Load setup`.
-         Load the :file:`hrs_adv_setup.ncs` file that is located under :file:`samples/bluetooth/central_and_peripheral_hr` in the |NCS| folder structure.
+         Load the :file:`hrs_adv_setup.ncs` file that is located under :file:`samples/bluetooth/central_and_peripheral_hrs` in the |NCS| folder structure.
       #. Click :guilabel:`Apply` and :guilabel:`Close`.
       #. Click the gear icon to open the Adapter settings and select :guilabel:`Start advertising`.
       #. Wait until the development kit running the Central and Peripheral HRS connects.
@@ -220,15 +220,15 @@ Testing with Bluetooth Low Energy app
       #. Open the `Bluetooth Low Energy app`_ and select the connected dongle that is used for communication.
       #. Open the **SERVER SETUP** tab.
       #. Click the dongle configuration and select :guilabel:`Load setup`.
-      #. Load the :file:`hr_service.ncs` file that is located under :file:`samples/bluetooth/central_and_peripheral_hr` in the |NCS| folder structure.
+      #. Load the :file:`hr_service.ncs` file that is located under :file:`samples/bluetooth/central_and_peripheral_hrs` in the |NCS| folder structure.
       #. Click :guilabel:`Apply to device`.
       #. Open the **CONNECTION MAP** tab.
       #. Click the dongle configuration (gear icon) and select :guilabel:`Advertising setup`.
 
          The current version of nRF Connect can store the advertising setup.
 
       #. Click :guilabel:`Load setup`.
-         Load the :file:`hrs_adv_setup.ncs` file that is located under :file:`samples/bluetooth/central_and_peripheral_hr` in the |NCS| folder structure.
+         Load the :file:`hrs_adv_setup.ncs` file that is located under :file:`samples/bluetooth/central_and_peripheral_hrs` in the |NCS| folder structure.
       #. Click :guilabel:`Apply` and :guilabel:`Close`.
       #. Click the gear icon to open the Adapter settings and select :guilabel:`Start advertising`.
       #. Wait until the development kit running the Central and Peripheral HRS connects.

samples/bluetooth/central_and_peripheral_hr/sample.yaml → samples/bluetooth/central_and_peripheral_hrs/sample.yaml

@@ -2,7 +2,7 @@ sample:
   description: Bluetooth Low Energy central and peripheral heart rate relay sample
   name: Bluetooth LE Central and Peripheral HRS
 tests:
-  sample.bluetooth.central_and_peripheral_hr.build:
+  sample.bluetooth.central_and_peripheral_hrs.build:
     sysbuild: true
     build_only: true
     integration_platforms:

samples/bluetooth/mesh/light_ctrl/README.rst → samples/bluetooth/mesh/light_fixture/README.rst

@@ -200,7 +200,7 @@ For more information about configuration files in the |NCS|, see :ref:`app_build
 Building and running
 ********************
 
-.. |sample path| replace:: :file:`samples/bluetooth/mesh/light_ctrl`
+.. |sample path| replace:: :file:`samples/bluetooth/mesh/light_fixture`
 
 .. include:: /includes/build_and_run_ns.txt
 

samples/bluetooth/mesh/light_ctrl/sample.yaml → samples/bluetooth/mesh/light_fixture/sample.yaml

@@ -2,7 +2,7 @@ sample:
   description: Bluetooth Mesh light fixture sample
   name: Bluetooth Mesh light fixture
 tests:
-  sample.bluetooth.mesh.light_ctrl:
+  sample.bluetooth.mesh.light_fixture:
     sysbuild: true
     build_only: true
     integration_platforms:
@@ -33,7 +33,7 @@ tests:
       - bluetooth
       - ci_build
       - sysbuild
-  sample.bluetooth.mesh.light_ctrl.emds:
+  sample.bluetooth.mesh.light_fixture.emds:
     sysbuild: true
     extra_args: OVERLAY_CONFIG="overlay-emds.conf"
     build_only: true

samples/bluetooth/mesh/sensor_client/README.rst → samples/bluetooth/mesh/sensor_observer/README.rst

@@ -1,4 +1,5 @@
 .. _bluetooth_mesh_sensor_client:
+.. _bluetooth_mesh_sensor_observer:
 
 Bluetooth Mesh: Sensor observer
 ###############################
@@ -153,11 +154,11 @@ FEM support
 Building and running
 ********************
 
-.. |sample path| replace:: :file:`samples/bluetooth/mesh/sensor_client`
+.. |sample path| replace:: :file:`samples/bluetooth/mesh/sensor_observer`
 
 .. include:: /includes/build_and_run.txt
 
-.. _bluetooth_mesh_sensor_client_testing:
+.. _bluetooth_mesh_sensor_observer_testing:
 
 Testing
 =======

samples/bluetooth/mesh/sensor_client/sample.yaml → samples/bluetooth/mesh/sensor_observer/sample.yaml

@@ -2,7 +2,7 @@ sample:
   description: Bluetooth Mesh sensor observer sample
   name: Bluetooth Mesh sensor observer
 tests:
-  sample.bluetooth.mesh.sensor_client:
+  sample.bluetooth.mesh.sensor_observer:
     sysbuild: true
     build_only: true
     integration_platforms:

samples/cellular/lte_ble_gateway/README.rst → samples/cellular/lte_sensor_gateway/README.rst

@@ -81,7 +81,7 @@ All LEDs (1-4):
 Building and running
 ********************
 
-.. |sample path| replace:: :file:`samples/cellular/lte_ble_gateway`
+.. |sample path| replace:: :file:`samples/cellular/lte_sensor_gateway`
 
 .. include:: /includes/build_and_run_ns.txt
 

samples/cellular/lte_ble_gateway/sample.yaml → samples/cellular/lte_sensor_gateway/sample.yaml

@@ -1,7 +1,7 @@
 sample:
   name: LTE-Bluetooth LE gateway sample
 tests:
-  sample.cellular.lte_ble_gateway:
+  sample.cellular.lte_sensor_gateway:
     sysbuild: true
     build_only: true
     integration_platforms:

samples/cellular/nrf_provisioning/README.rst → samples/cellular/nrf_device_provisioning/README.rst

@@ -119,7 +119,7 @@ The following files are available:
 Building and running
 ********************
 
-.. |sample path| replace:: :file:`samples/cellular/nrf_provisioning`
+.. |sample path| replace:: :file:`samples/cellular/nrf_device_provisioning`
 
 .. include:: /includes/build_and_run_ns.txt
 

samples/cellular/nrf_provisioning/sample.yaml → samples/cellular/nrf_device_provisioning/sample.yaml

@@ -1,7 +1,7 @@
 sample:
   name: nRF Device Provisioning
 tests:
-  sample.cellular.nrf_provisioning:
+  sample.cellular.nrf_device_provisioning:
     sysbuild: true
     build_only: true
     integration_platforms:

samples/bootloader/CMakeLists.txt → samples/nsib/CMakeLists.txt

@@ -7,6 +7,6 @@
 cmake_minimum_required(VERSION 3.20.0)
 
 find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
-project(bootloader)
+project(nsib)
 
 zephyr_library_sources(src/main.c)

samples/bootloader/README.rst → samples/nsib/README.rst

@@ -93,7 +93,7 @@ For information how to erase the entire flash memory when flashing, see :ref:`pr
 Flash memory layout
 ===================
 
-The flash memory layout is defined by the :file:`samples/bootloader/pm.yml` file, which establishes four main partitions:
+The flash memory layout is defined by the :file:`samples/nsib/pm.yml` file, which establishes four main partitions:
 
 * *B0* - The NSIB image.
 * *Provision* - The provisioned data.
@@ -164,7 +164,7 @@ To set options for child images, such as NSIB and MCUboot, see the :ref:`ug_mult
 Building and running
 ********************
 
-.. |sample path| replace:: :file:`samples/bootloader`
+.. |sample path| replace:: :file:`samples/nsib`
 
 .. include:: /includes/build_and_run.txt
 

samples/bootloader/sample.yaml → samples/nsib/sample.yaml

@@ -1,7 +1,7 @@
 sample:
   name: Bootloader Sample
 tests:
-  sample.bootloader:
+  sample.nsib:
     sysbuild: true
     build_only: true
     integration_platforms:

scripts/ci/tags.yaml

@@ -691,7 +691,7 @@ ci_tests_subsys_bootloader:
     - nrf/lib/identity_key/
     - nrf/lib/modem_antenna/
     - nrf/lib/nrf_modem_lib/
-    - nrf/samples/bootloader/
+    - nrf/samples/nsib/
     - nrf/subsys/bootloader/
     - nrf/subsys/fw_info/
     - nrf/subsys/nrf_security/
@@ -1294,7 +1294,7 @@ ci_tests_drivers_egpio:
 ci_tests_drivers_fprotect:
   files:
     - nrf/lib/fprotect/
-    - nrf/samples/bootloader/
+    - nrf/samples/nsib/
     - nrf/subsys/bootloader/
     - nrf/tests/drivers/fprotect/
     - zephyr/subsys/storage/
@@ -1327,7 +1327,7 @@ ci_samples_peripheral_lpuart:
 ci_samples_bootloader:
   files:
     - nrf/lib/fprotect/
-    - nrf/samples/bootloader/
+    - nrf/samples/nsib/
     - nrf/subsys/bootloader/
     - nrf/subsys/fw_info/
 

scripts/partition_manager/partition_manager.rst

@@ -741,7 +741,7 @@ For example, if you generate a partition placement report on the build of :file:
    | 0xff000: EMPTY_2 (0x1000)                |
    +------------------------------------------+
 
-The sizes of each partition are determined by the associated :file:`pm.yml` file, such as :file:`nrf/samples/bootloader/pm.yml` for |NSIB| and :file:`bootloader/mcuboot/boot/zephyr/pm.yml` for MCUboot.
+The sizes of each partition are determined by the associated :file:`pm.yml` file, such as :file:`nrf/samples/nsib/pm.yml` for |NSIB| and :file:`bootloader/mcuboot/boot/zephyr/pm.yml` for MCUboot.
 
 .. _ug_pm_static:
 

scripts/quarantine_integration.yaml

@@ -212,7 +212,7 @@
   comment: "Configurations excluded to limit resources usage in integration builds"
 
 - scenarios:
-    - sample.bluetooth.mesh.sensor_client
+    - sample.bluetooth.mesh.sensor_observer
   platforms:
     - nrf21540dk/nrf52840
     - nrf52840dk/nrf52840
@@ -926,7 +926,7 @@
   comment: "Configurations excluded to limit resources usage in integration builds"
 
 - scenarios:
-    - sample.bluetooth.central_and_peripheral_hr.build
+    - sample.bluetooth.central_and_peripheral_hrs.build
   platforms:
     - nrf52840dk/nrf52840
     - nrf5340dk/nrf5340/cpuapp

subsys/net/lib/Kconfig

@@ -46,7 +46,7 @@ rsource "softap_wifi_provision/Kconfig"
 rsource "wifi_mgmt_ext/Kconfig"
 rsource "wifi_ready/Kconfig"
 rsource "mqtt_helper/Kconfig"
-rsource "nrf_provisioning/Kconfig"
+rsource "nrf_device_provisioning/Kconfig"
 rsource "mcumgr_smp_client/Kconfig"
 rsource "nrf70_fw_ext/Kconfig"
 rsource "hostap_crypto/Kconfig"

sysbuild/secureboot.cmake

@@ -39,7 +39,7 @@ if(SB_CONFIG_SECURE_BOOT)
   endif()
 
   if(SB_CONFIG_SECURE_BOOT_APPCORE)
-    set(secure_boot_source_dir ${ZEPHYR_NRF_MODULE_DIR}/samples/bootloader)
+    set(secure_boot_source_dir ${ZEPHYR_NRF_MODULE_DIR}/samples/nsib)
 
     ExternalZephyrProject_Add(
       APPLICATION b0

tests/subsys/bluetooth/mesh/light_ctrl/testcase.yaml

@@ -1,5 +1,5 @@
 tests:
-  bluetooth.mesh.light_ctrl:
+  bluetooth.mesh.light_fixture:
     sysbuild: true
     platform_allow:
       - native_sim