diff --git a/docs/totalcompute/Makefile b/docs/totalcompute/Makefile new file mode 100644 index 0000000000000000000000000000000000000000..d4bb2cbb9eddb1bb1b4f366623044af8e4830919 --- /dev/null +++ b/docs/totalcompute/Makefile @@ -0,0 +1,20 @@ +# Minimal makefile for Sphinx documentation +# + +# You can set these variables from the command line, and also +# from the environment for the first two. +SPHINXOPTS ?= +SPHINXBUILD ?= sphinx-build +SOURCEDIR = . +BUILDDIR = _build + +# Put it first so that "make" without argument is like "make help". +help: + @$(SPHINXBUILD) -M help "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O) + +.PHONY: help Makefile + +# Catch-all target: route all unknown targets to Sphinx using the new +# "make mode" option. $(O) is meant as a shortcut for $(SPHINXOPTS). +%: Makefile + @$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O) diff --git a/docs/totalcompute/conf.py b/docs/totalcompute/conf.py new file mode 100644 index 0000000000000000000000000000000000000000..f0bbdbfc0aad266d7ff375b3661a06c416bfab2d --- /dev/null +++ b/docs/totalcompute/conf.py @@ -0,0 +1,52 @@ +# Configuration file for the Sphinx documentation builder. +# +# This file only contains a selection of the most common options. For a full +# list see the documentation: +# https://www.sphinx-doc.org/en/master/usage/configuration.html + +# -- Path setup -------------------------------------------------------------- + +# If extensions (or modules to document with autodoc) are in another directory, +# add these directories to sys.path here. If the directory is relative to the +# documentation root, use os.path.abspath to make it absolute, like shown here. +# +# import os +# import sys +# sys.path.insert(0, os.path.abspath('.')) + + +# -- Project information ----------------------------------------------------- + +project = 'Arm reference solutions' +copyright = '2020-2022, Arm' +author = 'Arunachalam Ganapathy' + + +# -- General configuration --------------------------------------------------- + +# Add any Sphinx extension module names here, as strings. They can be +# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom +# ones. +extensions = [ +] + +# Add any paths that contain templates here, relative to this directory. +templates_path = ['_templates'] + +# List of patterns, relative to source directory, that match files and +# directories to ignore when looking for source files. +# This pattern also affects html_static_path and html_extra_path. +exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store', 'docs/infra'] + + +# -- Options for HTML output ------------------------------------------------- + +# The theme to use for HTML and HTML Help pages. See the documentation for +# a list of builtin themes. +# +html_theme = 'sphinx_rtd_theme' + +# Add any paths that contain custom static files (such as style sheets) here, +# relative to this directory. They are copied after the builtin static files, +# so a file named "default.css" will overwrite the builtin "default.css". +html_static_path = ['_static'] diff --git a/docs/totalcompute/index.rst b/docs/totalcompute/index.rst new file mode 100644 index 0000000000000000000000000000000000000000..a949657bc3e57e991cc5f5edea43f6b93c2a4ee3 --- /dev/null +++ b/docs/totalcompute/index.rst @@ -0,0 +1,9 @@ +Welcome to Arm reference solutions documentation! +=================================================== + +.. toctree:: + :maxdepth: 2 + :caption: Total Compute: + + readme + diff --git a/docs/totalcompute/readme.rst b/docs/totalcompute/readme.rst index 65c31d6975879b2fb49da0fe4e828bf890c06d2c..3666e717d429ec08f3d4730af8ebd535996eda08 100644 --- a/docs/totalcompute/readme.rst +++ b/docs/totalcompute/readme.rst @@ -9,6 +9,9 @@ Total Compute focuses on optimizing Performance, Security, and Developer Access TC1 release tags ================ + +`TC1-2022.05.12 `_ + `TC1-2021.08.17 `_ TC0 release tags diff --git a/docs/totalcompute/tc1/change-log.rst b/docs/totalcompute/tc1/change-log.rst index 93d1a00a3a7cd8d27a0a9d07bc4f9ae51cf5425c..068e89480afb50fd123e2db178ecdb7bd7ed7ba0 100644 --- a/docs/totalcompute/tc1/change-log.rst +++ b/docs/totalcompute/tc1/change-log.rst @@ -8,6 +8,25 @@ Change Log This document contains a summary of the new features, changes and fixes in each release of TC1 software stack. +Version 2022.05.12 +------------------ + +Features added +~~~~~~~~~~~~~~ +- Trusty support in Android +- CI700-PMU enabled for profiling +- Added support for ETE and TRBE + +Changes +~~~~~~~ +- Updated Android to S +- Updated Trusted Firmware-A & Hafnium to v2.6 +- Updated SCP firmware to v2.10 +- Updated U-Boot to v2022.01 +- Updated Trusted Services +- Updated Yocto repositories +- Deprecated android-nano profile + Version 2021.08.17 ------------------ @@ -24,4 +43,4 @@ Features added - U-boot to v2021.07 - Yocto to master -*Copyright (c) 2021, Arm Limited. All rights reserved.* +*Copyright (c) 2021-2022, Arm Limited. All rights reserved.* diff --git a/docs/totalcompute/tc1/readme.rst b/docs/totalcompute/tc1/readme.rst index 0c4ad5ae0cb217a416c7ba2180d6c0195171dc2e..ca9409aafecb0de4a2abfb706d0ddce2ecfc467f 100644 --- a/docs/totalcompute/tc1/readme.rst +++ b/docs/totalcompute/tc1/readme.rst @@ -20,13 +20,16 @@ Following are the Software components: #. Secure Partition Manager #. Secure Partitions - * OP-TEE Trusted OS - * Trusted Services with Shim layer + * OP-TEE Trusted OS in Poky + * Trusted Services with Shim layer in Poky + * Trusty Trusted OS in Android + #. U-Boot – loads and verifies the fitImage for poky boot, containing kernel and filesystem or boot Image for Android Verified Boot, containing kernel and ramdisk. #. Kernel – supports the following hardware features * Mailbox hardware unit * PAC/MTE/BTI features + #. Android * Supports PAC/MTE/BTI features diff --git a/docs/totalcompute/tc1/release_notes.rst b/docs/totalcompute/tc1/release_notes.rst index 460dbd0d55bd20adb46e7c28d26fdc9943ae6bbd..1969b82ceb1d8b95afbdad162a647036392ddd3b 100755 --- a/docs/totalcompute/tc1/release_notes.rst +++ b/docs/totalcompute/tc1/release_notes.rst @@ -1,13 +1,13 @@ .. _docs/totalcompute/tc1/release_notes: -Release notes - 2021.08.17 +Release notes - 2022.05.12 ========================== .. contents:: Release tag ----------- -The manifest tag for this release is TC1-2021.08.17 +The manifest tag for this release is TC1-2022.05.12 Components ---------- @@ -17,8 +17,9 @@ The following is a summary of the key software features of the release: - System control processor(SCP) firmware for programming the interconnect, doing power control etc. - U-Boot bootloader. - Hafnium for S-EL2 Secure Partition Manager core. - - OP-TEE for Trusted Execution Environment (TEE). - - Crypto and Storage Trusted Services running at S-EL0. + - OP-TEE for Trusted Execution Environment (TEE) in Poky. + - Trusted Services (Crypto and Internal Trusted Storage) in Poky. + - Trusty for Trusted Execution Environment (TEE) with FF-A messaging in Android. Hardware Features ----------------- @@ -33,14 +34,17 @@ Hardware Features Software Features ----------------- - Poky Distribution support. - - Android AOSP Support (May21). + - Android S Support. - Android Common Kernel 5.10 with PAC/BTI/MTE - - Trusted Firmware-A & Hafnium v2.5 + - With Android S support, the KVM default mode of operation is set to ``protected``. This is a nVHE based mode with kernel running at EL1. + - Trusted Firmware-A & Hafnium v2.6 - OP-TEE 3.14.0 + - Trusty with FF-A messaging + - CI700-PMU enabled for profiling - Support secure boot based on TBBR specification https://developer.arm.com/documentation/den0006/latest - - System Control Processor (SCP) firmware v2.8 + - System Control Processor (SCP) firmware v2.10 - Build system based on Yocto master - - U-Boot bootloader v2021.07 + - U-Boot bootloader v2022.01 - Power management features: cpufreq and cpuidle. - SCMI (System Control and Management Interface) support. - Verified u-boot for authenticating fit image (containing kernel + ramdisk) during poky boot. @@ -50,21 +54,21 @@ Software Features - OP-TEE as Secure Partition at S-EL1, managed by S-EL2 SPMC (Hafnium) - Arm FF-A driver and FF-A Transport support for OP-TEE driver in Android Common Kernel. - OP-TEE Support in Poky distribution. This includes OP-TEE client and OP-TEE test suite. - - Crypto and Storage Trusted Services running at S-EL0. + - Trusted Services (Crypto and Internal Trusted Storage) running at S-EL0. - Trusted Services test suite added to poky distribution. - Shim Layer at S-EL1 running on top of S-EL2 SPMC (Hafnium) used by Trusted Services running in S-EL0. + - Tracing - Added support for ETE and TRBE v1.0 in TF-A, kernel and simpleperf. Traces can be captured with simpleperf. However, to enable tracing, the libete plugin has to be loaded while executing the FVP with ``--plugin /libete-plugin.so`` Platform Support ---------------- - This Software release is tested on TC1 Fast Model platform (FVP). - - Supported Fast model version for this release is 11.15.20 + - Supported Fast model version for this release is 11.17.33 Known issues or Limitations --------------------------- -1. At the U-Boot prompt press enter and type "boot" to continue booting else wait - for ~15 secs for boot to continue automatically. This is because of the time - difference in CPU frequency and FVP operating frequency. -2. OP-TEE test suite xtest, fails for Storage concurrency test case. This issue is under investigation. + #. At the U-Boot prompt press enter and type "boot" to continue booting else wait + for ~15 secs for boot to continue automatically. This is because of the time + difference in CPU frequency and FVP operating frequency. Support @@ -73,4 +77,4 @@ For support email: support-arch@arm.com -------------- -*Copyright (c) 2021, Arm Limited. All rights reserved.* +*Copyright (c) 2021-2022, Arm Limited. All rights reserved.* diff --git a/docs/totalcompute/tc1/tc1_sw_stack.png b/docs/totalcompute/tc1/tc1_sw_stack.png index 12da312a23436955bacd51719fa946e7ee09ac6f..3afae922ec0540e7133931a0083b288bc29f7e36 100644 Binary files a/docs/totalcompute/tc1/tc1_sw_stack.png and b/docs/totalcompute/tc1/tc1_sw_stack.png differ diff --git a/docs/totalcompute/tc1/tc1_sw_stack.rst b/docs/totalcompute/tc1/tc1_sw_stack.rst index 9ed06baf39c1da5ce97f29a8b809c020ec7e27ce..7f8c90f0749e82aa0fd9074ad1eaf3ec445b3092 100644 --- a/docs/totalcompute/tc1/tc1_sw_stack.rst +++ b/docs/totalcompute/tc1/tc1_sw_stack.rst @@ -74,7 +74,7 @@ Total Compute enables FEAT S-EL2 architectural extension, and it uses Hafnium as Secure Partitions ................. -Software image isolated using SPM is Secure Partition. Total Compute enables OP-TEE and Trusted Services (crypto, secure storage) as Secure Partitions. +Software image isolated using SPM is Secure Partition. Total Compute enables OP-TEE and Trusted Services (Crypto, Internal Trusted Storage) as Secure Partitions. OP-TEE ++++++ @@ -82,7 +82,7 @@ OP-TEE Trusted OS is virtualized using Hafnium at S-EL2. OP-TEE OS for Total Com Trusted Services ++++++++++++++++ -Trusted Services like Crypto Service and Secure Storage runs as S-EL0 Secure Partitions using a Shim layer at S-EL1. Crypto Service along with S-EL1 Shim layer is built as a single image. The Shim layer forwards FF-A calls from S-EL0 to S-EL2. +Trusted Services like Crypto Service and Internal Trusted Storage runs as S-EL0 Secure Partitions using a Shim layer at S-EL1. These services along with S-EL1 Shim layer are built as a single image. The Shim layer forwards FF-A calls from S-EL0 to S-EL2. U-Boot ------ @@ -99,12 +99,12 @@ Linux Kernel in Total Compute contains the subsystem-specific features that demo #. Arm FF-A driver #. OP-TEE driver with FF-A Transport Support #. Arm FF-A user space interface driver + #. Trusty driver with FF-A Transport Support Android ------- Total Compute has support for Android Open-Source Project (AOSP), which contains the Android framework, Native Libraries, Android Runtime and the Hardware Abstraction Layers (HALs) for Android Operating system. -The Total Compute device profile defines the required variables for Android such as partition size and product packages and has support for 2 different configurations of Android: +The Total Compute device profile defines the required variables for Android such as partition size and product packages and has support for the below configuration of Android: - #. Nano: This is a stripped-down version to provide the bare minimum for Android Runtime and boot Android to console. It does not have Android UI support. #. Software rendering: This profile has support for Android UI and boots Android to home screen. It uses SwiftShader to achieve this. Swiftshader is a CPU base implementation of the Vulkan graphics API by Google. diff --git a/docs/totalcompute/tc1/user-guide.rst b/docs/totalcompute/tc1/user-guide.rst index 095324e46f665e9171a20752569d141617137902..577e87ec0edb421610a67523846062bbdfad9d86 100755 --- a/docs/totalcompute/tc1/user-guide.rst +++ b/docs/totalcompute/tc1/user-guide.rst @@ -11,7 +11,7 @@ Notice The Total Compute 2021 (TC1) software stack uses the `Yocto project `__ to build a Board Support Package (BSP) and a choice of Poky Linux distribution or Android userspace. -The Yocto project uses `Bitbake `__ +The Yocto project uses `Bitbake `__ to build the software stack. @@ -22,25 +22,15 @@ These instructions assume that: * Your host PC is running Ubuntu Linux 18.04 LTS. * You are running the provided scripts in a ``bash`` shell environment. -The following utilities must be available on your host PC: - * chrpath - * compression library - * diffstat - * gawk - * makeinfo - * openssl headers - * pip - * repo - -To resolve these dependencies, run: +To resolve the dependencies, run: :: - + sudo add-apt-repository ppa:ubuntu-toolchain-r/test sudo apt-get update sudo apt-get install chrpath gawk texinfo libssl-dev diffstat wget git-core unzip gcc-multilib \ build-essential socat cpio python python3 python3-pip python3-pexpect xz-utils debianutils \ iputils-ping python3-git python3-jinja2 libegl1-mesa libsdl1.2-dev pylint3 xterm git-lfs openssl \ - curl lib32ncurses5-dev libz-dev python-pip u-boot-tools m4 zip + curl lib32ncurses5-dev libz-dev python-pip u-boot-tools m4 zip gcc-9 libstdc++6 liblz4-tool zstd To get the latest repo tool from google, run the following commands: @@ -75,7 +65,7 @@ in these instructions. mkdir cd - export TC1_RELEASE=refs/tags/TC1-2021.08.17 + export TC1_RELEASE=refs/tags/TC1-2022.05.12 To sync BSP only without Android, run the repo command. @@ -115,10 +105,7 @@ Note that the BSP includes the Poky Linux distribution, which offers BusyBox-lik Android OS build ################# -Two profiles are supported: - -#. tc1_swr : This supports Android display with swiftshader (software rendering). -#. tc1_nano : This supports headless Android and provides a good runtime environment for testing shell-based applications. +* tc1_swr : This supports Android display with swiftshader (software rendering). The android images can be built with or without authentication enabled using Android Verified Boot(AVB). AVB build is done in userdebug mode and takes a longer time to boot as the images are verified. @@ -132,22 +119,22 @@ The ``build-scripts/tc1/build_android.sh`` script in ``/android`` Incorrect script use, call script as: [OPTIONS] OPTIONS: - -d, --distro distro version, values supported [android-nano, android-swr] + -d, --distro distro version, values supported [android-swr] -a, --avb [OPTIONAL] avb boot, values supported [true, false], DEFAULT: false The ``--avb`` option does not influence the way the system boots rather it adds an optional sanity check on the prerequisite images. -As an example, to build android with software rendering and AVB enabled, run the command: +As an example, to build Android with software rendering and AVB disabled, run the command: :: - ./build-scripts/tc1/build_android.sh -d android-swr -a true + ./build-scripts/tc1/build_android.sh -d android-swr -To build headless android without AVB, run the command: +To build Android with software rendering and AVB enabled, run the command: :: - ./build-scripts/tc1/build_android.sh -d android-nano + ./build-scripts/tc1/build_android.sh -d android-swr -a true Android based stack takes considerable time to build, so start the build and go grab a cup of coffee! @@ -155,7 +142,7 @@ Provided components ------------------- Within the Yocto project, each component included in the TC1 software stack is specified as -a `Bitbake recipe `__. +a `Bitbake recipe `__. The TC1 recipes are located at ``/bsp/layers/meta-arm/``. Yocto allows modifying the fetched source code of each recipe component in the @@ -193,10 +180,10 @@ Trusted Firmware-A Based on `Trusted Firmware-A `__ +--------+------------------------------------------------------------------------------------------------------------+ -| Recipe | /bsp/layers/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-tc1.inc | +| Recipe | /bsp/layers/meta-arm/meta-arm-bsp/recipes-bsp/trusted-firmware-a/trusted-firmware-a-tc.inc | +--------+------------------------------------------------------------------------------------------------------------+ -| Files | * /bsp/build-poky/tmp-poky/deploy/images/tc1/bl1-tc1.bin | -| | * /bsp/build-poky/tmp-poky/deploy/images/tc1/fip-tc1.bin | +| Files | * /bsp/build-poky/tmp-poky/deploy/images/tc1/bl1-tc.bin | +| | * /bsp/build-poky/tmp-poky/deploy/images/tc1/fip_gpt.bin | +--------+------------------------------------------------------------------------------------------------------------+ @@ -206,7 +193,7 @@ System Control Processor (SCP) Based on `SCP Firmware `__ +--------+------------------------------------------------------------------------------------------------+ -| Recipe | /bsp/layers/meta-arm/meta-arm-bsp/recipes-bsp/scp-firmware/scp-firmware-tc1.inc | +| Recipe | /bsp/layers/meta-arm/meta-arm-bsp/recipes-bsp/scp-firmware/scp-firmware-tc.inc | +--------+------------------------------------------------------------------------------------------------+ | Files | * /bsp/build-poky/tmp-poky/deploy/images/tc1/scp_ramfw.bin | | | * /bsp/build-poky/tmp-poky/deploy/images/tc1/scp_romfw.bin | @@ -218,11 +205,11 @@ U-Boot Based on `U-Boot gitlab `__ -+--------+------------------------------------------------------------------------------------+ -| Recipe | /bsp/layers/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot-tc1.inc | -+--------+------------------------------------------------------------------------------------+ -| Files | * /bsp/build-poky/tmp-poky/deploy/images/tc1/u-boot.bin | -+--------+------------------------------------------------------------------------------------+ ++--------+---------------------------------------------------------------------------------------+ +| Recipe | /bsp/layers/meta-arm/meta-arm-bsp/recipes-bsp/u-boot/u-boot_%.bbappend | ++--------+---------------------------------------------------------------------------------------+ +| Files | * /bsp/build-poky/tmp-poky/deploy/images/tc1/u-boot.bin | ++--------+---------------------------------------------------------------------------------------+ Hafnium @@ -231,7 +218,7 @@ Hafnium Based on `Hafnium `__ +--------+--------------------------------------------------------------------------------------+ -| Recipe | /bsp/layers/meta-arm/meta-arm-bsp/recipes-bsp/hafnium/hafnium-tc1.inc | +| Recipe | /bsp/layers/meta-arm/meta-arm-bsp/recipes-bsp/hafnium/hafnium-tc.inc | +--------+--------------------------------------------------------------------------------------+ | Files | * /bsp/build-poky/tmp-poky/deploy/images/tc1/hafnium.bin | +--------+--------------------------------------------------------------------------------------+ @@ -243,7 +230,7 @@ OP-TEE Based on `OP-TEE `__ +--------+------------------------------------------------------------------------------------------+ -| Recipe | /bsp/layers/meta-arm/meta-arm-bsp/recipes-security/optee/optee-os-tc1.inc | +| Recipe | /bsp/layers/meta-arm/meta-arm-bsp/recipes-security/optee/optee-os-tc.inc | +--------+------------------------------------------------------------------------------------------+ | Files | * /bsp/build-poky/tmp-poky/deploy/images/tc1/optee/tee-pager_v2.bin | +--------+------------------------------------------------------------------------------------------+ @@ -257,8 +244,8 @@ Based on `Trusted Services /bsp/layers/meta-tc/recipes-security/trusted-services/secure-partitions_git.bb | +--------+-----------------------------------------------------------------------------------------------+ -| Files | * /bsp/build-poky/tmp-poky/deploy/images/tc1/firmware/crypto-sp.bin | -| | * /bsp/build-poky/tmp-poky/deploy/images/tc1/firmware/secure-storage.bin | +| Files | * /bsp/build-poky/tmp-poky/deploy/images/tc1/crypto-sp.bin | +| | * /bsp/build-poky/tmp-poky/deploy/images/tc1/internal-trusted-storage.bin | +--------+-----------------------------------------------------------------------------------------------+ Linux @@ -272,6 +259,16 @@ The recipe responsible for building a 5.10 version of the Android Common kernel | Files | * /bsp/build-poky/tmp-poky/deploy/images/tc1/Image | +--------+-----------------------------------------------------------------------------------------------+ +Trusty +****** + +Based on `Trusty `__ + ++--------+---------------------------------------------------------------------------+ +| Recipe | /bsp/layers/meta-tc/recipes-security/trusty/trusty_git.bb | ++--------+---------------------------------------------------------------------------+ +| Files | * /bsp/build-poky/tmp-poky/deploy/images/tc1/lk.bin | ++--------+---------------------------------------------------------------------------+ Distributions ############# @@ -292,7 +289,7 @@ The provided distribution is based on BusyBox and built using glibc. Android ******* -Android Master (as on May21) is supported in this release with device profiles suitable for TC1 machine configuration. +Android S is supported in this release with device profiles suitable for TC1 machine configuration. Android is built as a separate project and then booted with the BSP built by Yocto. @@ -337,7 +334,7 @@ the previously built images as arguments. Run the ``run_model.sh`` script: [OPTIONS] OPTIONS: -m, --model path to model - -d, --distro distro version, values supported [poky, android-nano, android-swr] + -d, --distro distro version, values supported [poky, android-swr] -a, --avb [OPTIONAL] avb boot, values supported [true, false], DEFAULT: false -t, --tap-interface [OPTIONAL] enable TAP interface -e, --extra-model-params [OPTIONAL] extra model parameters @@ -359,32 +356,30 @@ Running Android For running android with AVB disabled: ./run-scripts/tc1/run_model.sh -m -d android-swr - OR - ./run-scripts/tc1/run_model.sh -m -d android-nano For running android with AVB enabled: ./run-scripts/tc1/run_model.sh -m -d android-swr -a true - OR - ./run-scripts/tc1/run_model.sh -m -d android-nano -a true When the script is run, two terminal instances will be launched. terminal_s0 used for the SCP, TF-A, OP-TEE core logs and terminal_s1 used by TF-A early boot, Hafnium, U-boot and Linux. Once the FVP is running, the SCP will be the first to boot, bringing the AP out of reset. -The AP will start booting from its ROM and then proceed to boot Trusted Firmware-A, Hafnium, OP-TEE -then U-Boot, and then Linux and Poky/Android. +The AP will start booting from its ROM and then proceed to boot Trusted Firmware-A, Hafnium, +Secure Partitions (OP-TEE, Trusted Services in Poky and Trusty in Android) then U-Boot, and then Linux and Poky/Android. When booting Poky the model will boot Linux and present a login prompt. Login using the username ``root``. You may need to hit Enter for the prompt to appear. -The OP-TEE and Trusted Services are initialized on both the Android and Poky -distribution. But the functionality of OP-TEE and core set of trusted services -such as cryptography and secure storage can be invoked only on Poky -distribution. For OP-TEE, the TEE sanity test suite can be run using command -``xtest``. For Trusted Services, run command ``ts-service-test`` for Service -API level tests and run command ``ts-demo`` for the demonstration client -application. +The OP-TEE and Trusted Services are initialized in Poky distribution. The functionality of OP-TEE and +core set of trusted services such as Crypto and Internal Trusted Storage can be invoked only on Poky distribution. +For OP-TEE, the TEE sanity test suite can be run using command ``xtest``. +For Trusted Services, run command ``ts-service-test -sg ItsServiceTests -sg PsaCryptoApiTests -sg +CryptoServicePackedcTests -sg CryptoServiceProtobufTests -sg CryptoServiceLimitTests -v`` for Service API level tests +and run command ``ts-demo`` for the demonstration client application. + +On Android distribution, Trusty provides a Trusted Execution Environment (TEE). +The functionality of Trusty IPC can be tested using command ``tipc-test -t ta2ta-ipc`` with root privilege. -------------- -*Copyright (c) 2021, Arm Limited. All rights reserved.* +*Copyright (c) 2021-2022, Arm Limited. All rights reserved.*