This document describes the software requirements for building TF-A for AArch32 and AArch64 target platforms.
It may possible to build TF-A with combinations of software packages that are different from those listed below, however only the software described in this document can be officially supported.
1.1. Build Host¶
TF-A can be built using either a Linux or a Windows machine as the build host.
A relatively recent Linux distribution is recommended for building TF-A. We have performed tests using Ubuntu 16.04 LTS (64-bit) but other distributions should also work fine as a base, provided that the necessary tools and libraries can be installed.
TF-A can be built with any of the following cross-compiler toolchains that target the Armv7-A or Armv8-A architectures:
GCC >= 9.2-2019.12 (from the Arm Developer website)
Clang >= 4.0
Arm Compiler >= 6.0
In addition, a native compiler is required to build the supporting tools.
The software has also been built on Windows 7 Enterprise SP1, using CMD.EXE, Cygwin, and Msys (MinGW) shells, using version 5.3.1 of the GNU toolchain.
For instructions on how to select the cross compiler refer to Performing an Initial Build.
1.3. Software and Libraries¶
The following tools are required to obtain and build TF-A:
An appropriate toolchain (see Toolchain)
The following libraries must be available to build one or more components or supporting tools:
OpenSSL >= 1.0.1
Required to build the cert_create tool.
The following libraries are required for Trusted Board Boot support:
mbed TLS == 2.26.0 (tag:
These tools are optional:
Device Tree Compiler (DTC) >= 1.4.6
Needed if you want to rebuild the provided Flattened Device Tree (FDT) source files (
.dtsfiles). DTC is available for Linux through the package repositories of most distributions.
The standard software package used for debugging software on Arm development platforms and FVP models.
Node.js >= 14
Highly recommended, and necessary in order to install and use the packaged Git hooks and helper tools. Without these tools you will need to rely on the CI for feedback on commit message conformance.
1.3.1. Package Installation (Linux)¶
If you are using the recommended Ubuntu distribution then you can install the required packages with the following command:
sudo apt install build-essential git libssl-dev
The optional packages can be installed using:
sudo apt install device-tree-compiler
Additionally, to install an up-to-date version of Node.js, you can use the Node Version Manager to install a version of your choosing (we recommend 14, but later LTS versions might offer a more stable experience):
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | "$SHELL" exec "$SHELL" -ic "nvm install 14; exec $SHELL"
1.4. Supporting Files¶
1.5. Getting the TF-A Source¶
Source code for TF-A is maintained in a Git repository hosted on TrustedFirmware.org. To clone this repository from the server, run the following in your shell:
git clone "https://review.trustedfirmware.org/TF-A/trusted-firmware-a"
1.5.1. Additional Steps for Contributors¶
If you are planning on contributing back to TF-A, there are some things you’ll want to know.
TF-A is hosted by a Gerrit Code Review server. Gerrit requires that all
commits include a
Change-Id footer, and this footer is typically
automatically generated by a Git hook installed by you, the developer.
If you have opted not to install Node.js, you can install the Gerrit hook manually by running:
curl -Lo $(git rev-parse --git-dir)/hooks/commit-msg https://review.trustedfirmware.org/tools/hooks/commit-msg chmod +x $(git rev-parse --git-dir)/hooks/commit-msg
You can read more about Git hooks in the githooks page of the Git documentation, available here.
Copyright (c) 2021, Arm Limited. All rights reserved.