doc: Update documentation for v0.7.0

Release notes and other doc updates.

Signed-off-by: Bartosz Gentkowski <bartosz.gentkowski@nordicsemi.no>

Author: b-gent

doc/nrf-bm/conf.py

@@ -17,7 +17,7 @@
 
 # -- Project information -----------------------------------------------------
 
-project = 'nRF Connect SDK Bare Metal option - 0.1.99'
+project = 'nRF Connect SDK Bare Metal option - 0.7.0'
 copyright = '2025, Nordic Semiconductor'
 author = 'Nordic Semiconductor'
 
@@ -55,4 +55,4 @@
 # Add any paths that contain custom static files (such as style sheets) here,
 # relative to this directory. They are copied after the builtin static files,
 # so a file named "default.css" will overwrite the builtin "default.css".
-# html_static_path = ['../_static']
+html_static_path = ['_static', 'pdfs']

doc/nrf-bm/gen_docs.py

@@ -9,6 +9,9 @@
 static_dir = os.path.abspath("../_static")  # Path to the _static directory
 requirements_path = os.path.join(script_dir, "requirements.txt")  # Path to the requirements.txt file
 includes_dir = os.path.join(script_dir, "includes")  # Path to the includes directory
+sample_dir = os.path.join(script_dir, "sample")  # Path to the sample directory
+pdf_source_dir = os.path.abspath('../../subsys/softdevice/hex/s115')  # Path to the PDF source directory
+pdf_destination_dir = os.path.join(source_dir, 'pdfs')  # Destination directory within _static
 images_dir = os.path.join(script_dir, "images")  # Path to the images directory
 
 # Install packages from requirements.txt
@@ -21,16 +24,30 @@
 
 # Create the source directory if it doesn't exist
 os.makedirs(source_dir, exist_ok=True)
+os.makedirs(pdf_destination_dir, exist_ok=True)
 
-# Copy RST files
+# Copy RST files and maintain directory structure
 for root, dirs, files in os.walk(".", topdown=True):
     # Exclude the source directory from the search
     dirs[:] = [d for d in dirs if os.path.abspath(os.path.join(root, d)) != source_dir]
     for file in files:
         if file.endswith(".rst"):
             src_file_path = os.path.join(root, file)
-            if os.path.abspath(src_file_path) != os.path.join(source_dir, file):
-                shutil.copy2(src_file_path, source_dir)
+            relative_path = os.path.relpath(root, ".")
+            dest_dir = os.path.join(source_dir, relative_path)
+            os.makedirs(dest_dir, exist_ok=True)
+            shutil.copy2(src_file_path, dest_dir)
+
+# Copy PDFs
+if os.path.exists(pdf_source_dir):
+    for file in os.listdir(pdf_source_dir):
+        if file.endswith(".pdf"):
+            src_file_path = os.path.join(pdf_source_dir, file)
+            shutil.copy2(src_file_path, pdf_destination_dir)
+            print(f"Copied PDFs to {pdf_destination_dir}")
+else:
+    print("PDF source directory not found.")
+    exit()
 
 # Copy sample READMEs
 if os.path.exists(samples_dir):

doc/nrf-bm/images/create_new_application_from_sample_quick_pick_menu.png

@@ -7,15 +7,15 @@ Follow these steps to create your first build configuration for this sample:
 
    You will need the following information:
 
-   * The |NCS| version and toolchain version the current |BMshort| release is based on: v3.0.1
-   * The board target onto which you want to program the firmware (**Requirements** section).
+   * The |NCS| version and toolchain version that the current |BMshort| release is based on: |ncs_release|
+   * The board target onto which you want to program the firmware (see `Requirements`_).
 
    This information will be used in the steps that follow.
 
    .. note::
       The following steps will use the **Hello SoftDevice** sample as reference.
 
-#. In the `Applications View`_, click on :guilabel:`Add build configuration`.
+#. In the `Applications View`_, click :guilabel:`Add build configuration`.
 
    .. figure:: /images/add_build_configuration.png
       :alt: Add Build Configuration
@@ -33,7 +33,7 @@ Follow these steps to create your first build configuration for this sample:
 
 #. Select the board target onto which you want to program the firmware.
 
-   For your very first build configuration, select a compatible board target from the drop down menu.
+   For your very first build configuration, select a compatible board target from the drop-down menu.
 
    .. figure:: /images/board_target.png
       :alt: Board target drop-down menu
@@ -44,11 +44,12 @@ Follow these steps to create your first build configuration for this sample:
 
    For more details on how to configure builds, see `How to build an application`_ in |VSC| extension documentation.
 
-#. Click the :guilabel:`Generate and Build` button.
+#. Click :guilabel:`Generate and Build`.
 
    The |VSC| extension generates the configuration file and triggers the build process, which can take some time. You can monitor its progress in the notification that appears.
 
-   When the process is complete, the `Actions View`_ appears. In this View, you can trigger the build process again, flash the built application, start a debug session, or generate a memory report.
+   When the process is complete, the `Actions View`_ appears.
+   In this View, you can trigger the build process again, flash the built application, start a debug session (if debug options were set when building), or generate a memory report.
    The build files appear in the build's `Details View`_, which is named after your application.
 
    .. figure:: /images/show_build_configuration_files.png

doc/nrf-bm/includes/configure_and_build_sample.txt

@@ -8,7 +8,7 @@ Follow these steps to create a new application based on this sample:
 
    A quick pick menu appears.
 
-#. Choose the option :guilabel:`Copy a sample` - This will create a `freestanding application`_ from a sample in |BMlong|.
+#. Select :guilabel:`Copy a sample` - this will create a `freestanding application`_ from a sample in |BMlong|.
 
    A quick pick menu appears showing a list of available samples to choose from.
 
@@ -39,6 +39,7 @@ Follow these steps to create a new application based on this sample:
 
    A prompt appears asking to enter the location for the application.
    You can also use the folder button at the top of the quick pick to open a folder picker.
+
    The application creation process starts after you enter the name.
    When the application is created, a prompt appears.
-   Click on :guilabel:`Open` or :guilabel:`Open in New Window` to open the new application.
+   Click :guilabel:`Open` or :guilabel:`Open in New Window` to open the new application.

doc/nrf-bm/includes/create_sample.txt

@@ -4,7 +4,7 @@ Programming the sample
 Follow these steps to program this sample:
 
 1. Plug in your device to the serial terminal using a USB cable.
-   Your device appears on the Connected Devices View list in |VSC|.
+   Your device appears on the `Connected Devices View`_ list in |VSC|.
 #. To flash the application you have built, click :guilabel:`Flash` in the `Actions View`_ after connecting the device to the terminal.
 
 For more details, see `How to flash an application`_ in |VSC| extension documentation.

doc/nrf-bm/includes/program_sample.txt

@@ -8,19 +8,19 @@ To flash the S115 SoftDevice binary to your device, open the terminal and run th
 
          .. code-block:: console
 
-            cd C:/ncs/v0.7.0/nrf-bm
+            cd C:/ncs/bm_v0.7.0/nrf-bm
 
       .. group-tab:: Linux
 
          .. code-block:: console
 
-            cd ~/ncs/v0.7.0/nrf-bm
+            cd ~/ncs/bm_v0.7.0/nrf-bm
 
       .. group-tab:: macOS
 
          .. code-block:: console
 
-            cd /opt/nordic/ncs/v0.7.0/nrf-bm
+            cd /opt/nordic/ncs/bm_v0.7.0/nrf-bm
 
 #. Then, make sure that your device is erased:
 
@@ -49,3 +49,7 @@ To flash the S115 SoftDevice binary to your device, open the terminal and run th
          .. code-block:: console
 
             nrfutil device program --firmware subsys/softdevice/hex/s115/s115_9.0.0-2.prototype+offset-0x05D000_softdevice.hex
+
+   .. note::
+      Keep in mind that the flashed SoftDevice variant must be in sync with the board target that you are planning to use in the build configuration of the sample.
+      For example, for the ``bm_nrf54l15dk/nrf54l15/cpuapp/softdevice_s115`` board target, you must use the SoftDevice binary :file:`s115_9.0.0-2.prototype+offset-0x15D000_softdevice.hex` .

doc/nrf-bm/includes/softdevice_flash.txt

@@ -4,17 +4,36 @@
 Introduction
 ############
 
-|BMlong| is an enhancement to the |NCS|, offering an optional configuration for developing Bluetooth LE applications that do not benefit from utilizing an RTOS nor require advanced features.
+The |BMlong| is a streamlined enhancement of the |NCS|, tailored for developers who are working on Bluetooth® LE applications that do not require the complexities of an RTOS or the full suite of advanced features.
+This option is particularly beneficial for applications that require a lightweight, responsive solution.
 
-You can use this development option for the following:
+A major component of the |BMshort| configuration is the SoftDevice.
+To facilitate Bluetooth LE operations without an RTOS, a new SoftDevice variant supporting the latest nRF54L devices has been released.
+This new variant maintains a similar functionality and API to those found in the existing nRF52 SoftDevices, ensuring a smooth transition and familiarity for developers.
 
-* Development of threadless applications without the use of Zephyr RTOS.
-* Migration of applications originally created for the nRF52 devices using the nRF5 SDK.
+The |BMshort| codebase is structured to include libraries and modules that are specifically designed to operate without an RTOS.
+This ensures that all included components are optimized for threadless, bare metal environments.
+
+The |BMshort| option is ideal for:
+
+* Developing simple, threadless applications without the need for Zephyr RTOS.
+* Migrating applications initially developed for nRF52 devices using the nRF5 SDK.
+
+Integration and structure
+*************************
+
+The |BMlong| is a distinct repository that incorporates elements from the existing |NCS|:
+
+* **Repository-Level Filtering:** |BMshort| utilizes a repository-level filtering mechanism designed to include components beneficial for bare metal development.
+  However, this approach is based on the best possible method available, which means that some components that are not ideally suited for bare metal applications will also be included.
+  Developers should be aware of these limitations and exercise discretion when utilizing the repository.
+* **Tools:** Tools such as the compiler and linker from the original |NCS| are reused in the Bare Metal option.
+  The existing nRF Connect extension in |VSC| is the recommended IDE for working with Bare Metal.
 
 .. toctree::
-   :maxdepth: 2
+   :maxdepth: 3
    :caption: Contents
 
    install_nrf_bm.rst
    samples.rst
-   release_notes_0.1.0.rst
+   release_notes.rst