michaelh/zephyr
1
0
Fork 0
Code Releases Activity

boards: nrf9160 DK: update board documentation for TF-M

Browse source 
Minor updates to the documentation of the nRF9160 DK
board, stressing that TF-M is the default Secure
firmware binary for non-secure nRF9160 builds.

Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
This commit is contained in:
Ioannis Glaropoulos 2021-04-06 19:55:52 +02:00
commit 345bf8fb64
1 changed files with 10 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

14
boards/arm/nrf9160dk_nrf9160/doc/index.rst
View file

@ -156,13 +156,17 @@ image. The Secure image can be built using either Zephyr or
`Trusted Firmware M`_ (TF-M). Non-Secure firmware images are always built
using Zephyr. The two alternatives are described below.
.. note::
By default the Secure image for nRF9160 is built using TF-M.
Building the Secure firmware using Zephyr
-----------------------------------------
The process requires the following steps:
1. Build the Secure Zephyr application using ``-DBOARD=nrf9160dk_nrf9160`` and
``CONFIG_TRUSTED_EXECUTION_SECURE=y`` in the the application project configuration file.
``CONFIG_TRUSTED_EXECUTION_SECURE=y`` in the application project configuration file.
2. Build the Non-Secure Zephyr application using ``-DBOARD=nrf9160dk_nrf9160ns``.
3. Merge the two binaries together.
@ -172,9 +176,11 @@ Building the Secure firmware with TF-M
The process to build the Secure firmware image using TF-M and the Non-Secure
firmware image using Zephyr requires the following action:
* Build the Non-Secure Zephyr application
using ``-DBOARD=nrf9160dk_nrf9160ns`` and
``CONFIG_BUILD_WITH_TFM=y`` in the application project configuration file.
1. Build the Non-Secure Zephyr application
using ``-DBOARD=nrf9160dk_nrf9160ns``.
To invoke the building of TF-M the Zephyr build system requires the
Kconfig option ``BUILD_WITH_TFM`` to be enabled, which is done by
default when building Zephyr as a Non-Secure application.
The Zephyr build system will perform the following steps automatically:
* Build the Non-Secure firmware image as a regular Zephyr application