From 1c36f9c6163f8b4f2b8d94693243b78da5465fdd Mon Sep 17 00:00:00 2001 From: Grzegorz Ferenc Date: Tue, 21 Jan 2025 13:53:22 +0100 Subject: [PATCH] doc: includes: add board target info to _ns txts Updated doc txt includes for build_and_run_ns with info where to look for */ns variant. NCSDK-29828. Signed-off-by: Grzegorz Ferenc --- doc/nrf/includes/application_build_and_run_ns.txt | 3 ++- doc/nrf/includes/build_and_run_ns.txt | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/nrf/includes/application_build_and_run_ns.txt b/doc/nrf/includes/application_build_and_run_ns.txt index d2717d041bc9..94484c9b3cd8 100644 --- a/doc/nrf/includes/application_build_and_run_ns.txt +++ b/doc/nrf/includes/application_build_and_run_ns.txt @@ -1,6 +1,7 @@ This application can be found under |application path| in the |NCS| folder structure. -When built as a firmware image for a board target with the ``*/ns`` :ref:`variant `, the application has :term:`Cortex-M Security Extensions (CMSE)` enabled and separates the firmware between the :term:`Non-Secure Processing Environment (NSPE)` and the :term:`Secure Processing Environment (SPE)`. +You can build this application as firmware image for a board target with the ``*/ns`` :ref:`variant ` (see the Requirements section above). +In such cases, the sample has Cortex-M Security Extensions (CMSE) enabled and separates the firmware between Non-Secure Processing Environment (NSPE) and Secure Processing Environment (SPE). Because of this, it automatically includes the :ref:`Trusted Firmware-M (TF-M) `. To read more about CMSE, see :ref:`app_boards_spe_nspe`. diff --git a/doc/nrf/includes/build_and_run_ns.txt b/doc/nrf/includes/build_and_run_ns.txt index 21ddbed96497..b123b861c504 100644 --- a/doc/nrf/includes/build_and_run_ns.txt +++ b/doc/nrf/includes/build_and_run_ns.txt @@ -1,6 +1,7 @@ This sample can be found under |sample path| in the |NCS| folder structure. -When built as firmware image for a board target with the ``*/ns`` :ref:`variant `, the sample has Cortex-M Security Extensions (CMSE) enabled and separates the firmware between Non-Secure Processing Environment (NSPE) and Secure Processing Environment (SPE). +You can build this sample as firmware image for a board target with the ``*/ns`` :ref:`variant ` (see the Requirements section above). +In such cases, the sample has Cortex-M Security Extensions (CMSE) enabled and separates the firmware between Non-Secure Processing Environment (NSPE) and Secure Processing Environment (SPE). Because of this, it automatically includes the :ref:`Trusted Firmware-M (TF-M) `. To read more about CMSE, see :ref:`app_boards_spe_nspe`.