You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/nrf/app_dev/board_names.rst
+21-7Lines changed: 21 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,15 +46,27 @@ While the board name is always present, other elements, such as the board revisi
46
46
Check the Product Specification of the given SoC for more information about the available CPU clusters.
47
47
48
48
* :ref:`Variant <zephyr:glossary>` - You can use this board qualifier to build for a particular type or configuration of a build for a combination of SoC and CPU cluster.
49
-
In the |NCS|, variants are used for indicating the usage of Cortex-M Security Extensions (CMSE) (security by separation):
49
+
In the |NCS|, board variants are used for the following purposes:
50
50
51
-
* Entries without ``*/ns`` (for example, ``cpuapp``) - When you choose this target, you build the application core firmware as a single execution environment that does not use CMSE (:ref:`Trusted Firmware-M (TF-M) <ug_tfm>`).
52
-
* Entries with ``*/ns`` (for example, ``cpuapp/ns``) - Recommended for more security.
53
-
When you choose this target, you build the application with CMSE using security by separation.
54
-
The application core firmware is placed in Non-Secure Processing Environment (NSPE) and uses Secure Processing Environment (SPE) for security features.
55
-
By default, the build system automatically includes :ref:`Trusted Firmware-M (TF-M) <ug_tfm>` in SPE and merges it with NSPE.
51
+
* Changing the default memory map:
52
+
This applies to the entry for the nRF52840 Dongle with the ``*/bare`` variant (``nrf52840dongle/nrf52840/bare``).
53
+
When you select this target, the firmware does not account for the onboard USB bootloader.
54
+
This corresponds to using :zephyr:board:`flashing option 3 with an external debug probe <nrf52840dongle>`.
56
55
57
-
Read more about separation of processing environments on the :ref:`ug_tfm_security_by_separation` page.
56
+
* Indicating the use of Cortex-M Security Extensions (CMSE), also known as security by separation:
57
+
58
+
* Variants without ``*/ns`` (for example, ``cpuapp``):
59
+
When you select this target, you build the application core firmware as a single execution environment without CMSE.
60
+
See :ref:`Trusted Firmware-M (TF-M) <ug_tfm>` for more information.
61
+
62
+
* Variants with ``*/ns`` (for example, ``cpuapp/ns``):
63
+
Recommended for enhanced security.
64
+
When you select this target, you build the application with CMSE enabled, using security by separation.
65
+
66
+
The application core firmware is placed in Non-Secure Processing Environment (NSPE) and uses Secure Processing Environment (SPE) for security features.
67
+
By default, the build system automatically includes :ref:`Trusted Firmware-M (TF-M) <ug_tfm>` in SPE and merges it with NSPE.
68
+
69
+
Read more about separation of processing environments on the :ref:`ug_tfm_security_by_separation` page.
58
70
59
71
.. note::
60
72
This board name scheme was introduced in the |NCS| before the v2.7.0 release following changes in Zephyr v3.6.0.
@@ -125,6 +137,8 @@ Also see the :ref:`zephyr:boards` section in the Zephyr documentation.
0 commit comments