doc: doc release PR for 0.8.0

b-gent · eivindj-nordic · commit 02dccfa557ce · 2025-08-28T12:30:17.000+02:00
Add release notes and other release-related doc updates.

Signed-off-by: Bartosz Gentkowski &lt;bartosz.gentkowski@nordicsemi.no&gt;
diff --git a/doc/nrf-bm/api/api.rst b/doc/nrf-bm/api/api.rst
@@ -1,4 +1,4 @@
-.. nrf_bm_api:
+.. _nrf_bm_api:
 
 API documentation
 #################
diff --git a/doc/nrf-bm/app_dev/dfu/index.rst b/doc/nrf-bm/app_dev/dfu/index.rst
@@ -1,4 +1,4 @@
-.. _app_bootloaders:
+.. _bm_dfu:
 
 Device Firmware Update (DFU)
 ############################
diff --git a/doc/nrf-bm/app_dev/dfu/memory_partitioning.rst b/doc/nrf-bm/app_dev/dfu/memory_partitioning.rst
@@ -32,13 +32,13 @@ The memory in the device is divided into several partitions, each serving a spec
      - Begins immediately after the storage partition or the IRoT partition if the storage is not enabled.
        The size is maximized up to the start of the firmware loader.
    * - slot1_partition
-     - Serves as the location for the DFU mode and contains the Firmware Loader.
-     - This partition contains the Firmware Loader that is validated by the IRoT.
-       The Firmware Loader is started when entering the DFU mode.
+     - Serves as the location for the DFU mode and contains the firmware loader.
+     - This partition contains the firmware loader that is validated by the IRoT.
+       The firmware loader is started when entering the DFU mode.
    * - softdevice_partition
      - Used by the SoftDevice.
      - Includes an MCUboot header of size 0x800.
-       The SoftDevice is used by both the Firmware Loader and the Application that is running from ``slot0``
+       The SoftDevice is used by both the firmware loader and the application that is running from ``slot0``
    * - metadata_partition
      - Utilized by the firmware loader and IRoT for storing metadata.
      - Reserves 0.5 kB at the top of the memory.
@@ -65,7 +65,7 @@ Vector table alignment
 
 For images that are run as a `main application` that has its own interrupt vector table there is an `Vector table requirement`_ on how to place the interrupt vector table in memory.
 The table must be placed starting at the 2 kB boundary.
-An example of such images are Application and Firmware Loader.
+An example of such images are application and firmware loader.
 The SoftDevice is not affected by this requirement.
 
 SoftDevice placement
diff --git a/doc/nrf-bm/app_dev/dfu/single_bank_dfu.rst b/doc/nrf-bm/app_dev/dfu/single_bank_dfu.rst
@@ -23,20 +23,20 @@ The following are key steps in the single-bank application update.
    If the firmware is not valid, the bootloader reverts the device to DFU mode, allowing for another update attempt.
 #. **Activation**: Upon successful validation, the new firmware is activated.
 
-SoftDevice and Firmware Loader update
+SoftDevice and firmware loader update
 =====================================
 
-The following are the DFU steps when the SoftDevice and/or Firmware Loader are also updated.
+The following are the DFU steps when the SoftDevice and/or firmware loader are also updated.
 
 .. figure:: ../../images/dfu_steps_sd_fwl.svg
    :alt: DFU operations for a single-bank SoftDevice and/or FW Loader update
 
 1. **Replacement of Existing Application**: The new firmware update process begins with the replacement of the existing application by a new DFU image.
-   This image includes an Installer along with updates for the Firmware Loader and/or the SoftDevice.
-#. **Validation**: Once the new DFU image is transferred, the system validates both the Installer image and the additional image(s) (Firmware Loader and/or the SoftDevice).
+   This image includes an Installer along with updates for the firmware loader and/or the SoftDevice.
+#. **Validation**: Once the new DFU image is transferred, the system validates both the Installer image and the additional image(s) (firmware loader and/or the SoftDevice).
 #. **Installation**: After successful validation, the Installer image is activated.
-   The Installer carries out the necessary actions to copy the Firmware Loader and SoftDevice to their designated locations in the device's memory.
-#. **Device Restart and Final Validation**: Following the installation, the device restarts and performs a final validation of the newly installed Firmware Loader and SoftDevice.
+   The Installer carries out the necessary actions to copy the firmware loader and SoftDevice to their designated locations in the device's memory.
+#. **Device Restart and Final Validation**: Following the installation, the device restarts and performs a final validation of the newly installed firmware loader and SoftDevice.
 #. **Entry into DFU Mode**: Once the final validation is complete, the device enters DFU mode, ready to receive any further new images.
 
-After a successful update of the SoftDevice and/or Firmware Loader, the application must be updated again following the process described in `Application update`_.
+After a successful update of the SoftDevice and/or firmware loader, the application must be updated again following the process described in `Application update`_.
diff --git a/doc/nrf-bm/app_dev/dfu/ug_dfu.rst b/doc/nrf-bm/app_dev/dfu/ug_dfu.rst
@@ -75,20 +75,20 @@ When DFU is enabled in the application, the build system outputs the following f
 +--------------------------------------------------------------------------------+----------------------------------------------+--------------------------------+
 | File                                                                           | Description                                  | Programming scenario           |
 +================================================================================+==============================================+================================+
-| :file:`<build_dir>/firmware_loader/zephyr/zephyr.signed.hex`                   | Firmware Loader Image.                       | Programming board targets.     |
+| :file:`<build_dir>/firmware_loader/zephyr/zephyr.signed.hex`                   | Firmware loader image.                       | Programming board targets.     |
 +--------------------------------------------------------------------------------+----------------------------------------------+                                |
-| :file:`<build_dir>/mcuboot/zephyr/zephyr_signed_softdevice_flash_metadata.hex` | MCUBoot Image with SoftDevice.               |                                |
+| :file:`<build_dir>/mcuboot/zephyr/zephyr_signed_softdevice_flash_metadata.hex` | MCUBoot image with SoftDevice.               |                                |
 +--------------------------------------------------------------------------------+----------------------------------------------+                                |
-| :file:`<build_dir>/<app_name>/zephyr/zephyr.signed.hex`                        | Application Image.                           |                                |
+| :file:`<build_dir>/<app_name>/zephyr/zephyr.signed.hex`                        | Application image.                           |                                |
 +--------------------------------------------------------------------------------+----------------------------------------------+--------------------------------+
 | :file:`<build_dir>/production.hex`                                             | Production hex file, containing: MCUboot,    | Production device programming. |
 |                                                                                | firmware loader, SoftDevice and main         |                                |
 |                                                                                | application images.                          |                                |
 +--------------------------------------------------------------------------------+----------------------------------------------+--------------------------------+
-| :file:`<build_dir>/installer_softdevice_firmware_loader.bin`                   | Installer Update Image (DFU) with SoftDevice | DFU process for board targets. |
+| :file:`<build_dir>/installer_softdevice_firmware_loader.bin`                   | Installer Update image (DFU) with SoftDevice | DFU process for board targets. |
 |                                                                                | and firmware loader updates.                 |                                |
 +--------------------------------------------------------------------------------+----------------------------------------------+                                |
-| :file:`<build_dir>/<app_name>/zephyr/zephyr.signed.bin`                        | Application Update Image (DFU).              |                                |
+| :file:`<build_dir>/<app_name>/zephyr/zephyr.signed.bin`                        | Application Update image (DFU).              |                                |
 +--------------------------------------------------------------------------------+----------------------------------------------+--------------------------------+
 
 Running DFU in your application
diff --git a/doc/nrf-bm/conf.py b/doc/nrf-bm/conf.py
@@ -17,7 +17,7 @@
 
 # -- Project information -----------------------------------------------------
 
-project = 'nRF Connect SDK Bare Metal option - 0.7.99'
+project = 'nRF Connect SDK Bare Metal option - 0.8.0'
 copyright = '2025, Nordic Semiconductor'
 author = 'Nordic Semiconductor'
 
diff --git a/doc/nrf-bm/index.rst b/doc/nrf-bm/index.rst
@@ -46,6 +46,5 @@ The |BMlong| is a distinct repository that incorporates elements from the existi
    samples.rst
    app_dev/dfu/index.rst
    release_notes.rst
-   migration/nrf5_bm_migration.rst
    s115_docs.rst
    api/api.rst
diff --git a/doc/nrf-bm/install_nrf_bm.rst b/doc/nrf-bm/install_nrf_bm.rst
@@ -146,11 +146,13 @@ Next steps
 
 You can now proceed to test the :ref:`samples` included in this version of |BMshort|.
 
-The samples can be found in the :file:`nrf-bm/samples` folder, and are divided into two subfolders:
+The samples can be found in the :file:`nrf-bm/samples` folder, and are divided into subfolders:
 
 * :file:`bluetooth` for the samples showcasing Bluetooth® LE functionalities using the SoftDevice.
   See :ref:`ble_samples`.
 * :file:`peripherals` for the samples showcasing various peripheral functionalities that do not require the SoftDevice.
   See :ref:`peripheral_samples`.
+* :file:`boot` for the samples showcasing the functionalities related to Device Firmware Update.
+  See :ref:`dfu_samples`.
 
 Each sample documentation contains full information on how to build, flash, and test the respective sample.
diff --git a/doc/nrf-bm/links.txt b/doc/nrf-bm/links.txt
@@ -11,6 +11,7 @@
 .. ### Source: docs.nordicsemi
 
 .. _`nRF54L15 DK`: https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/boards/nordic/nrf54l15dk/doc/index.html#nrf54l15dk-nrf54l15
+.. _`nRF54L15 DK v0.9.3`: https://docs.nordicsemi.com/bundle/comp_matrix_nrf54l15/page/COMP/nrf54l15/nrf54l15_ic_rev_comp_with_dev_hw.html
 
 .. ### Installation
 
@@ -74,3 +75,5 @@
 .. ### Release notes and migration
 
 .. _`nrfx migration guides`: https://github.com/NordicSemiconductor/nrfx/wiki/nrfx-2.11.0-to-3.0.0
+.. _`Migration notes - nRF5 SDK to nRF Connect SDK Bare Metal option`: https://docs.nordicsemi.com/bundle/nrf-bm-latest/page/migration/nrf5_bm_migration.html
+.. _`S115 9.0.0-3.prototype API reference`: https://docs.nordicsemi.com/bundle/s115_9.0.0-3.prototype_api/page/topics.html
diff --git a/doc/nrf-bm/migration/nrf5_bm_migration.rst b/doc/nrf-bm/migration/nrf5_bm_migration.rst
@@ -1,3 +1,5 @@
+:orphan:
+
 .. _nrf5_bm_migration:
 
 Migration notes - nRF5 SDK to nRF Connect SDK Bare Metal
diff --git a/doc/nrf-bm/release_notes.rst b/doc/nrf-bm/release_notes.rst
@@ -9,5 +9,6 @@ The following is a list of all release notes documents for various releases of t
    :maxdepth: 1
    :caption: Subpages:
 
-   release_notes_0.7.0
-   release_notes_0.1.0
+   release_notes/release_notes_0.8.0
+   release_notes/release_notes_0.7.0
+   release_notes/release_notes_0.1.0
diff --git a/doc/nrf-bm/release_notes/release_notes_0.1.0.rst b/doc/nrf-bm/release_notes/release_notes_0.1.0.rst
diff --git a/doc/nrf-bm/release_notes/release_notes_0.7.0.rst b/doc/nrf-bm/release_notes/release_notes_0.7.0.rst
diff --git a/doc/nrf-bm/release_notes/release_notes_0.8.0.rst b/doc/nrf-bm/release_notes/release_notes_0.8.0.rst
@@ -0,0 +1,244 @@
+.. _nrf_bm_release_notes_080:
+
+Release Notes for |BMlong| v0.8.0
+#################################
+
+.. contents::
+   :local:
+   :depth: 2
+
+|BMshort| v0.8.0 is the public launch release of this product, demonstrating a set of samples for the `nRF54L15 DK`_ with build targets supporting the following SoCs:
+
+* `nRF54L15`_
+* `nRF54L10`_ (emulated on the nRF54L15 DK)
+* `nRF54L05`_ (emulated on the nRF54L15 DK)
+
+The supported DK version is `nRF54L15 DK v0.9.3`_.
+
+The release includes a prototype version of the S115 SoftDevice - a proprietary Bluetooth® LE stack to be used on the nRF54L15 DK.
+
+Product maturity
+****************
+
+As this is version 0.8.0 of |BMshort|, please note that the solution is still under development and not production ready.
+Modules and libraries are subject to changes.
+This includes potential modifications to the organization of the folder structure.
+Although the memory partition structure is expected to remain consistent, the sizes of individual partitions might be refined as progress is made towards a stable release.
+
+The documentation for |BMshort| is still in development and might not cover all libraries and modules available in the codebase.
+Some sections are incomplete and lacking detailed information as content is being developed.
+
+IDE and tool support
+********************
+
+`nRF Connect extension for Visual Studio Code <nRF Connect for Visual Studio Code_>`_ is the recommended IDE for |BMshort| v0.8.0.
+See the :ref:`install_nrf_bm` section for more information about supported operating systems and toolchain.
+
+Supported boards
+****************
+
+* PCA10156 (`nRF54L15 DK`_)
+
+Migration from nRF5 SDK
+***********************
+
+For guidelines on how to migrate an application built on nRF5 SDK to |BMshort|, refer to `Migration notes - nRF5 SDK to nRF Connect SDK Bare Metal option`_.
+
+Changelog
+*********
+
+The following sections provide detailed lists of changes by component.
+
+SDK installation
+================
+
+* The default way to install |BMshort| is through the |nRFVSC| user interface, using either the :guilabel:`Pre-packaged SDK & Toolchain` option or a GitHub installation.
+  For detailed steps, see :ref:`cloning_the_repositories_nrf_bm`.
+
+S115 SoftDevice
+===============
+
+* Updated the S115 SoftDevice version to ``s115_9.0.0-3.prototype``.
+  The SoftDevice comes in three variants to support different SoCs of the nRF54L Series: nRF54L15, nRF54L10, and nRF54L05.
+
+  * :file:`s115_9.0.0-3.prototype_nrf54l15_softdevice.hex`
+  * :file:`s115_9.0.0-3.prototype_nrf54l10_softdevice.hex`
+  * :file:`s115_9.0.0-3.prototype_nrf54l05_softdevice.hex`
+
+  For more details about this release of the SoftDevice, see :ref:`s115_docs`.
+
+  For API documentation, see `S115 9.0.0-3.prototype API reference`_.
+
+SoftDevice Handler
+==================
+
+* Added support for seeding the SoftDevice RNG when requested by the SoftDevice.
+
+* Fixed the maximum MTU Kconfig option.
+
+Boards
+======
+
+* Added the following ``bm_nrf54l15dk`` board variants for MCUboot (DFU-enabled board variants):
+
+  * ``bm_nrf54l15dk/nrf54l05/s115_softdevice/mcuboot``
+  * ``bm_nrf54l15dk/nrf54l10/s115_softdevice/mcuboot``
+  * ``bm_nrf54l15dk/nrf54l15/s115_softdevice/mcuboot``
+
+..
+
+* Renamed the ``bm_nrf54l15dk`` board variants:
+
+  * ``bm_nrf54l15dk/nrf54l05/softdevice_s115`` to ``bm_nrf54l15dk/nrf54l05/s115_softdevice``
+  * ``bm_nrf54l15dk/nrf54l10/softdevice_s115`` to ``bm_nrf54l15dk/nrf54l10/s115_softdevice``
+  * ``bm_nrf54l15dk/nrf54l15/softdevice_s115`` to ``bm_nrf54l15dk/nrf54l15/s115_softdevice``
+
+..
+
+* Fixed:
+
+  * Fixed wrong RRAM size on the nRF54L10 emulation target from 1022 to 1012 KiB.
+
+..
+
+* Removed:
+
+  * The template board variants.
+  * The ``no_softdevice`` variants of the ``bm_nRF54l15dk``.
+
+DFU
+===
+
+* DFU using MCUboot firmware loader mode is now introduced in the SDK:
+
+  * Added experimental support for single-bank DFU, using the MCUboot bootloader and a firmware loader which is tasked to receive the new firmware image.
+    The DFU supports updating either the application or the SoftDevice with the firmware loader.
+
+  For more details, see :ref:`bm_dfu`.
+
+Logging
+=======
+
+* Fixed an issue with the minimal log mode.
+
+Drivers
+=======
+
+* Added the following drivers:
+
+  * The :ref:`driver_lpuarte` driver.
+  * A SoftDevice-based flash driver implementing the Zephyr flash interface.
+    This is added exclusively for DFU and is not expected to be used by other parts of the application.
+    Instead, use the :ref:`lib_bm_zms` and ``bm_storage`` libraries.
+
+Libraries
+=========
+
+* Added the following libraries:
+
+  * The :ref:`lib_bm_zms` library.
+  * The ``bm_storage`` library.
+  * A queue library (modified library from Zephyr).
+    This library has been added as a dependency for MCUmgr (used in DFU) offering support for threadless applications.
+
+..
+
+* ``ble_adv`` library:
+
+  * Changed the default advertising name to ``nRF_BM_device``.
+  * Corrected the :kconfig:option:`BLE_ADV_DIRECTED_ADVERTISING_HIGH_DUTY` Kconfig option.
+
+..
+
+* ``ble_conn_params library`` library:
+
+  * Updated connection parameter values to the :c:enumerator:`BLE_CONN_PARAMS_EVT_UPDATED` event.
+  * Renamed slave latency to peripheral latency according to specification.
+
+  * Fixed:
+
+    * An issue where the ATT MTU could be set to a lower value than the current value.
+    * An issue where the list of PHYs supported by the SoftDevice was not respected by the library when doing PHY updates.
+    * Data length timeout issue and the :c:func:`data_length_get` function returning wrong value.
+    * Incorrectly stated maximum ATT MTU value.
+
+Samples
+=======
+
+* General changes:
+
+  * All samples now use the logging module instead of ``printk``.
+
+  * Updated:
+
+    * The main loop sleep instructions as the :c:func:`sd_app_evt_wait` function is deprecated.
+    * Updated the main function flow to always end up in a loop with sleep instructions and deferred log processing instead of returning from the main function.
+      This ensures that log messages are printed and that the device goes into sleep mode.
+      Returning from main leaves the device in a state that prevents low power sleep and unhandled deferred log messages are not processed.
+
+Bluetooth samples
+-----------------
+
+* Added the :ref:`ble_pwr_profiling_sample` sample.
+
+..
+
+* :ref:`ble_cgms_sample` sample:
+
+  * Fixed an issue with responding twice to a PHY update request.
+
+..
+
+* :ref:`ble_hrs_sample` sample:
+
+  * Removed the unused Coded PHY Kconfig fragment.
+
+..
+
+* :ref:`ble_nus_sample` sample:
+
+  * Added support for :ref:`driver_lpuarte`.
+
+..
+
+  * Fixed:
+
+    * The pin configuration to use the pins from the :file:`board_config.h` board header.
+    * An issue in the :c:func:`ble_nus_data_send` function where passing NULL as the NUS instance could cause a segmentation fault.
+
+Peripheral samples
+------------------
+
+* Added the following samples:
+
+  * :ref:`bm_zms_sample` sample.
+  * :ref:`bm_lpuarte_sample` sample.
+  * :ref:`storage_sample` sample.
+
+DFU samples
+-----------
+
+* Added the following samples:
+
+  * :ref:`ble_mcuboot_recovery_entry_sample` sample that demonstrates how to activate DFU mode on the device using Bluetooth LE on a mobile application.
+  * :ref:`ble_mcuboot_recovery_retention_sample` sample that demonstrates how to switch a device into DFU mode on embedded application's request and execute DFU over UART or Bluetooth LE.
+
+Known issues and limitations
+============================
+
+* Some issues are observed when using iPhone as the peer during testing of the Bluetooth samples.
+* Some issues are observed when using Linux with the Bluetooth Low Energy app in nRF Connect for Desktop as the peer during testing of the Bluetooth samples.
+* There are no samples or libraries available to demonstrate or support the Bluetooth LE Pairing and bonding functionality in the SoftDevice.
+* The samples are not optimized for power consumption unless explicitly stated.
+
+Documentation
+=============
+
+* First public release of product documentation.
+* Added:
+
+  * Top-level sections for :ref:`drivers`, :ref:`libraries`, :ref:`bm_dfu`, and :ref:`s115_docs`.
+  * Documentation for the :ref:`lib_ble_conn_params` library.
+  * :ref:`nrf_bm_api` section.
+
+* :ref:`s115_docs` are now integrated with the |BMshort| documentation.
diff --git a/doc/nrf-bm/s115_docs.rst b/doc/nrf-bm/s115_docs.rst
diff --git a/samples/peripherals/bm_zms/README.rst b/samples/peripherals/bm_zms/README.rst

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-.. nrf_bm_api:`
	`1`	`+.. _nrf_bm_api:`
`2`	`2`
`3`	`3`	`API documentation`
`4`	`4`	`#################`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-.. _app_bootloaders:`
	`1`	`+.. _bm_dfu:`
`2`	`2`
`3`	`3`	`Device Firmware Update (DFU)`
`4`	`4`	`############################`
Original file line number	Diff line number	Diff line change
`@@ -1,3 +1,5 @@`
	`1`	`+:orphan:`
	`2`	`+`
`1`	`3`	`.. _nrf5_bm_migration:`
`2`	`4`
`3`	`5`	`Migration notes - nRF5 SDK to nRF Connect SDK Bare Metal`