Skip to content
Snippets Groups Projects
user avatar
Lionel Debieve authored
Do not build firmware configuration file if no AARCH32_SP
is selected. It will avoid build issue when building only
bl2 target.

Signed-off-by: default avatarLionel Debieve <lionel.debieve@st.com>
Change-Id: Ic43e72aff475d0673d9456110f0d3d82fd5c9683
Reviewed-on: https://gerrit.st.com/c/mpu/oe/st/tf-a/+/186657


Reviewed-by: default avatarCITOOLS <smet-aci-reviews@lists.codex.cro.st.com>
Reviewed-by: default avatarCIBUILD <smet-aci-builds@lists.codex.cro.st.com>
Reviewed-by: default avatarNicolas TOROMANOFF <nicolas.toromanoff@st.com>
Reviewed-by: default avatarYann GAUTIER <yann.gautier@st.com>
ad695417
History

Trusted Firmware-A

Trusted Firmware-A (TF-A) is a reference implementation of secure world software for Arm A-Profile architectures (Armv8-A and Armv7-A), including an Exception Level 3 (EL3) Secure Monitor. It provides a suitable starting point for productization of secure world boot and runtime firmware, in either the AArch32 or AArch64 execution states.

TF-A implements Arm interface standards, including:

The code is designed to be portable and reusable across hardware platforms and software models that are based on the Armv8-A and Armv7-A architectures.

In collaboration with interested parties, we will continue to enhance TF-A with reference implementations of Arm standards to benefit developers working with Armv7-A and Armv8-A TrustZone technology.

Users are encouraged to do their own security validation, including penetration testing, on any secure world code derived from TF-A.

More Info and Documentation

To find out more about Trusted Firmware-A, please view the full documentation that is available through trustedfirmware.org.


Copyright (c) 2013-2019, Arm Limited and Contributors. All rights reserved.