samples/doc: Fix some undefined Kconfig references

Fixes some instances of this

Signed-off-by: Jamie McCrae <[email protected]>

Author: nordicjm

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

@@ -146,13 +146,13 @@ However, you can customize it to meet specific requirements.
     - **MCUboot Kconfig option**
     - **Comments**
   * - SHA-256
-    - ``CONFIG_BOOT_HASH_ALG_SHA256``
+    - ``CONFIG_BOOT_IMG_HASH_ALG_SHA256``
     - The default hash. Compatible with all pre-hash signature types.
   * - SHA-384
-    - ``CONFIG_BOOT_HASH_ALG_SHA384``
+    - ``CONFIG_BOOT_IMG_HASH_ALG_SHA384``
     - Currently not utilized by |NCS|.
   * - SHA-512
-    - ``CONFIG_BOOT_HASH_ALG_SHA512``
+    - ``CONFIG_BOOT_IMG_HASH_ALG_SHA512``
     - Restricted to use with Ed25519 signatures.
 
 MCUboot recovery protocol

doc/nrf/app_dev/device_guides/nrf70/nrf70_fw_patch_update.rst

@@ -13,8 +13,8 @@ This guide explains the available option for updating the nRF70 Series firmware
     External memory refers to the memory that is outside the System-on-Chip (SoC), for example, an external flash memory chip, or an external nonvolatile memory (NVM) chip.
 
 .. note::
-    Currently, you cannot build an example with the both ``SB_CONFIG_WIFI_PATCHES_EXT_FLASH_STORE`` and :kconfig:option:`CONFIG_XIP_SPLIT_IMAGE` Kconfig options enabled.
-    To enable XIP support use the ``SB_CONFIG_WIFI_PATCHES_EXT_FLASH_XIP`` Kconfig option instead of the ``SB_CONFIG_WIFI_PATCHES_EXT_FLASH_STORE`` Kconfig option.
+    Currently, you cannot build an example with the both :kconfig:option:`SB_CONFIG_WIFI_PATCHES_EXT_FLASH_STORE` and :kconfig:option:`SB_CONFIG_QSPI_XIP_SPLIT_IMAGE` Kconfig options enabled.
+    To enable XIP support use the :kconfig:option:`SB_CONFIG_WIFI_PATCHES_EXT_FLASH_XIP` Kconfig option instead of the :kconfig:option:`SB_CONFIG_WIFI_PATCHES_EXT_FLASH_STORE` Kconfig option.
 
 Overview
 ========
@@ -35,7 +35,7 @@ To use this feature, ensure that the following prerequisites are met:
 * The external memory has sufficient capacity to accommodate the firmware patches.
   This includes additional space for potential patch upgrades, such as those required for DFU.
   The combined size of all firmware patches should not exceed 128 kB.
-* MCUboot is enabled, and the ``SB_CONFIG_BOOTLOADER_MCUBOOT`` Kconfig option is set to ``y``.
+* MCUboot is enabled, and the :kconfig:option:`SB_CONFIG_BOOTLOADER_MCUBOOT` Kconfig option is set to ``y``.
 
 Supported platforms
 ===================
@@ -236,7 +236,7 @@ To enable the DFU procedure for the nRF70 Series firmware patch, complete the fo
 
                         -- -Dshell_SNIPPET=nrf70-fw-patch-ext-flash -DSB_CONFIG_WIFI_PATCHES_EXT_FLASH_STORE=y -DCONFIG_NRF_WIFI_FW_PATCH_DFU=y
 
-If you want to use the :ref:`sysbuild_images` feature, you need to set the ``SB_CONFIG_DFU_MULTI_IMAGE_PACKAGE_WIFI_FW_PATCH`` Kconfig option to ``y``, and must also set the :kconfig:option:`CONFIG_DFU_MULTI_IMAGE_MAX_IMAGE_COUNT` Kconfig option to one of the following values:
+If you want to use the :ref:`sysbuild_images` feature, you need to set the :kconfig:option:`SB_CONFIG_DFU_MULTI_IMAGE_PACKAGE_WIFI_FW_PATCH` Kconfig option to ``y``, and must also set the :kconfig:option:`CONFIG_DFU_MULTI_IMAGE_MAX_IMAGE_COUNT` Kconfig option to one of the following values:
 
 * For the nRF5340 DK and nRF7002 DK without the network core: ``2``
 * For the nRF5340 DK and nRF7002 DK with the network core: ``3``

samples/bootloader/README.rst

@@ -119,7 +119,7 @@ Pre-signed variants
 
 When two slots are present, two images must be built.
 One that is executable from slot 0, and the other one from slot 1.
-Building the image for slot 1 is done by enabling the :kconfig:option:`CONFIG_BUILD_S1_VARIANT` option.
+Building the image for slot 1 is done by enabling the :kconfig:option:`SB_CONFIG_SECURE_BOOT_BUILD_S1_VARIANT_IMAGE` option.
 
 When the image for the next stage in the boot chain is upgraded, the new image is written to the slot with the oldest image version.
 See :ref:`bootloader_monotonic_counter` for more information about versioning.
@@ -171,7 +171,7 @@ Building and running
    While it is technically possible to build the NSIB by itself and merge it into other application images, this process is not supported.
    To reduce the development time and potential issues with this route, let the existing |NCS| infrastructure for sysbuild handle the integration.
 
-   The NSIB is automatically added as an image when the ``SB_CONFIG_SECURE_BOOT_APPCORE`` sysbuild Kconfig option is set.
+   The NSIB is automatically added as an image when the :kconfig:option:`SB_CONFIG_SECURE_BOOT_APPCORE` sysbuild Kconfig option is set.
 
 For building and running the NSIB with an application, see :ref:`ug_bootloader_adding_sysbuild_immutable`.
 

samples/nrf5340/extxip_smp_svr/README.rst

@@ -29,7 +29,7 @@ For more information about MCUmgr and SMP, see :ref:`device_mgmt`.
 
 The sample enables the splitting by:
 
-* Enabling the split XIP image feature through the :kconfig:option:`CONFIG_XIP_SPLIT_IMAGE` Kconfig option.
+* Enabling the split XIP image feature through the :kconfig:option:`SB_CONFIG_XIP_SPLIT_IMAGE` sysbuild Kconfig option.
   This Kconfig option sets a build-system level support for image division and adapts the image-signing support for MCUboot.
 * Using the project's CMake file which describes relocation of certain libraries or objects to an external XIP area.
 * Using a linker script that describes the external QSPI area.