patrick/zephyr
1
0
Fork 0
Code Issues Pull requests Actions 8 Packages Projects Releases Wiki Activity

boards: st: tfm: Update board documentation

Browse source 
regression.sh path is now tfm/api_ns/regression.sh, reflect it in the
doc.
Remove duplicate TF-M material.

Signed-off-by: Erwan Gouriou <erwan.gouriou@st.com>
This commit is contained in:
Erwan Gouriou 2024-03-14 16:51:56 +01:00 committed by Fabio Baltieri
parent 83369d7b7c
commit 0014ec9f33
4 changed files with 8 additions and 96 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
boards/st/b_u585i_iot02a/doc/index.rst
View file

@ -230,11 +230,11 @@ option bit TZEN will be set).
.. code-block:: bash
$ ./build/tfm/regression.sh
$ ./build/tfm/api_ns/regression.sh
$ west flash
Please note that, after having run a TFM sample on the board, you will need to
run `./build/tfm/regression.sh` once more to clean up the board from secure
run `./build/tfm/api_ns/regression.sh` once more to clean up the board from secure
options and get back the platform back to a "normal" state and be able to run
usual, non-TFM, binaries.
Also note that, even then, TZEN will remain set, and you will need to use
@ -335,34 +335,6 @@ Here is an example for the :zephyr:code-sample:`blinky` application.
:board: b_u585i_iot02a
:goals: debug
Building a secure/non-secure with Arm |reg| TrustZone |reg|
===========================================================
The TF-M applications can be run on this board, thanks to its Arm |reg| TrustZone |reg|
support.
In TF-M configuration, Zephyr is run on the non-secure domain. A non-secure image
can be generated using ``b_u585i_iot02a/stm32u585xx/ns`` as build target.
.. code-block:: bash
$ west build -b b_u585i_iot02a/stm32u585xx/ns path/to/source/directory
Note: When building the ``*_ns`` image with TF-M, ``build/tfm/api_ns/postbuild.sh`` bash script
is run automatically in a post-build step to make some required flash layout changes.
Once the build is completed, run the following script to initialize the option bytes.
.. code-block:: bash
$ build/tfm/api_ns/regression.sh
Finally, to flash the board, run:
.. code-block:: bash
$ west flash
Disabling TrustZone |reg| on the board
======================================

34
boards/st/nucleo_l552ze_q/doc/nucleol552ze_q.rst
View file

@ -209,11 +209,11 @@ option bit TZEN will be set).
.. code-block:: bash
$ ./build/tfm/regression.sh
$ ./build/tfm/api_ns/regression.sh
$ west flash
Please note that, after having run a TFM sample on the board, you will need to
run `./build/tfm/regression.sh` once more to clean up the board from secure
run `./build/tfm/api_ns/regression.sh` once more to clean up the board from secure
options and get back the platform back to a "normal" state and be able to run
usual, non-TFM, binaries.
Also note that, even then, TZEN will remain set, and you will need to use
@ -327,36 +327,6 @@ You should see the following message on the console:
Hello World! arm
Building a secure/non-secure with Arm |reg| TrustZone |reg|
-----------------------------------------------------------
The TF-M integration sample :ref:`tfm_ipc` can be run on a ST Nucleo L552ZE Q.
In TF-M configuration, Zephyr is run on the non-secure domain. A non-secure image
can be generated using ``nucleo_l552ze_q/stm32l552xx/ns`` as build target.
.. code-block:: bash
$ west build -b nucleo_l552ze_q/stm32l552xx/ns path/to/source/directory
Note: When building the ``*_ns`` image with TF-M, ``build/tfm/api_ns/postbuild.sh`` bash script
is run automatically in a post-build step to make some required flash layout changes.
Once the build is completed, run the following script to initialize the option bytes.
.. code-block:: bash
$ build/tfm/regression.sh
Finally, to flash the board, run:
.. code-block:: bash
$ west flash
Note: Check the ``build/tfm`` directory to ensure that the commands required by these scripts
(``readlink``, etc.) are available on your system. Please also check ``STM32_Programmer_CLI``
(which is used for initialization) is available in the PATH.
Debugging
=========

34
boards/st/stm32l562e_dk/doc/index.rst
View file

@ -235,11 +235,11 @@ option bit TZEN will be set).
.. code-block:: bash
$ ./build/tfm/regression.sh
$ ./build/tfm/api_ns/regression.sh
$ west flash
Please note that, after having run a TFM sample on the board, you will need to
run `./build/tfm/regression.sh` once more to clean up the board from secure
run `./build/tfm/api_ns/regression.sh` once more to clean up the board from secure
options and get back the platform back to a "normal" state and be able to run
usual, non-TFM, binaries.
Also note that, even then, TZEN will remain set, and you will need to use
@ -329,36 +329,6 @@ You should see the following message on the console:
Hello World! stm32l562e_dk
Building Secure/Non-Secure Zephyr applications with Arm |reg| TrustZone |reg|
-----------------------------------------------------------------------------
The TF-M integration sample :ref:`tfm_ipc` can be run on a ST STM32L562E-DK Discovery.
In TF-M configuration, Zephyr is run on the non-secure domain. A non-secure image
can be generated using ``stm32l562e_dk/stm32l562xx/ns`` as build target.
.. code-block:: bash
$ west build -b stm32l562e_dk/stm32l562xx/ns path/to/source/directory
Note: When building the ``*_ns`` image with TF-M, ``build/tfm/api_ns/postbuild.sh`` bash script
is run automatically in a post-build step to make some required flash layout changes.
Once the build is completed, run the following script to initialize the option bytes.
.. code-block:: bash
$ build/tfm/regression.sh
Finally, to flash the board, run:
.. code-block:: bash
$ west flash --hex-file build/tfm_merged.hex
Note: Check the ``build/tfm`` directory to ensure that the commands required by these scripts
(``readlink``, etc.) are available on your system. Please also check ``STM32_Programmer_CLI``
(which is used for initialization) is available in the PATH.
Debugging
=========

4
samples/tfm_integration/tfm_ipc/README.rst
View file

@ -124,7 +124,7 @@ Build Zephyr with a non-secure configuration:
.. code-block:: bash
$ west build -b stm32l562e_dk_ns samples/tfm_integration/tfm_ipc/
$ west build -b stm32l562e_dk/stm32l562xx/ns samples/tfm_integration/tfm_ipc/
The script to initialize the device is available in the ``build/tfm`` folder:
@ -134,7 +134,7 @@ Run them in the following order to flash the board:
.. code-block:: bash
$ ./build/tfm/regression.sh
$ ./build/tfm/api_ns/regression.sh
$ west flash
.. note::