Build Options Summary¶
As far as possible, TF-A Tests dynamically detects the platform hardware components and available features. There are a few build options to select specific features where the dynamic detection falls short.
Unless mentioned otherwise, these options are expected to be specified at the build command line and are not to be modified in any component makefiles.
The build system doesn’t track dependencies for build options. Therefore, if any of the build options are changed from a previous build, a clean build must be performed.
Arm FVP Platform Specific Build Options¶
FVP_CLUSTER_COUNT: Configures the cluster count to be used to build the topology tree within TFTF. By default TFTF is configured for dual cluster for CPUs with single thread (ST) and single cluster for SMT CPUs. For ST CPUs this option can be used to override the default number of clusters with a value in the range 1-4.
FVP_MAX_CPUS_PER_CLUSTER: Sets the maximum number of CPUs implemented in a single cluster. This option defaults to the maximum value of 4 for ST CPUs and maximum value of 8 for SMT CPUs.
FVP_MAX_PE_PER_CPU: Sets the maximum number of PEs implemented on any CPU in the system. This option defaults to 1 to select ST CPUs. For platforms with SMT CPUs this value must be set to 2.
TFTF-specific Build Options¶
NEW_TEST_SESSION: Choose whether a new test session should be started every time or whether the framework should determine whether a previous session was interrupted and resume it. It can take either 1 (always start new session) or 0 (resume session as appropriate). 1 is the default.
TESTS: Set of tests to run. Use the following command to list all possible sets of tests:
If no set of tests is specified, the standard tests will be selected (see
USE_NVM: Used to select the location of test results. It can take either 0 (RAM) or 1 (non-volatile memory like flash) as test results storage. Default value is 0, as writing to the flash significantly slows tests down.
Realm payload specific Build Options¶
TFTF_MAX_IMAGE_SIZE: The option needs to be either set by the user or by the platform makefile to specify the maximum size of TFTF binary. This is needed so that the Realm payload binary can be appended to TFTF binary via
make pack_realmbuild command.
FWU-specific Build Options¶
FIRMWARE_UPDATE: Whether the Firmware Update test images (i.e.
NS_BL2U) should be built. The default value is 0. The platform makefile is free to override this value if Firmware Update is supported on this platform.
Copyright (c) 2019-2020, Arm Limited. All rights reserved.