michaelh/zephyr
1
0
Fork 0
Code Releases Activity

boards: stm32l562e_dk: Add non secure target

Browse source 
This commit adds a second target for the stm32l562e_dk board.
The non secure target can be configured for TFM IPC application.

Signed-off-by: Yestin Sun <sunyi0804@gmail.com>
This commit is contained in:
Yestin Sun 2021-01-05 15:08:05 -08:00 • committed by Ioannis Glaropoulos
commit 19d397d88e
7 changed files with 137 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

16
boards/arm/stm32l562e_dk/doc/index.rst
View file

@ -166,6 +166,8 @@ The Zephyr stm32l562e_dk board configuration supports the following hardware fea
+-----------+------------+-------------------------------------+
| SPI | on-chip | spi |
+-----------+------------+-------------------------------------+
| TrustZone | on-chip | Trusted Firmware-M |
+-----------+------------+-------------------------------------+
Other hardware features are not yet supported on this Zephyr port.
@ -254,6 +256,20 @@ 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 STM32L562E-DK Discovery,
using the ``stm32l562e_dk_ns`` target. When building a ``*_ns`` image with TF-M,
a ``build/tfm/postbuild.sh`` bash script will be run automatically as a post-build step
to make some required flash layout changes. The ``build/tfm/regression.sh`` script will
need to be run to perform device initialization, and then run ``west flash --hex-file build/tfm_merged.hex``
to flash the board.
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``
used for initialization is available in the PATH.
Debugging
=========