1Build Options 2============= 3 4The TF-A build system supports the following build options. Unless mentioned 5otherwise, these options are expected to be specified at the build command 6line and are not to be modified in any component makefiles. Note that the 7build system doesn't track dependency for build options. Therefore, if any of 8the build options are changed from a previous build, a clean build must be 9performed. 10 11.. _build_options_common: 12 13Common build options 14-------------------- 15 16- ``AARCH32_INSTRUCTION_SET``: Choose the AArch32 instruction set that the 17 compiler should use. Valid values are T32 and A32. It defaults to T32 due to 18 code having a smaller resulting size. 19 20- ``AARCH32_SP`` : Choose the AArch32 Secure Payload component to be built as 21 as the BL32 image when ``ARCH=aarch32``. The value should be the path to the 22 directory containing the SP source, relative to the ``bl32/``; the directory 23 is expected to contain a makefile called ``<aarch32_sp-value>.mk``. 24 25- ``AMU_RESTRICT_COUNTERS``: Register reads to the group 1 counters will return 26 zero at all but the highest implemented exception level. External 27 memory-mapped debug accesses are unaffected by this control. 28 The default value is 1 for all platforms. 29 30- ``ARCH`` : Choose the target build architecture for TF-A. It can take either 31 ``aarch64`` or ``aarch32`` as values. By default, it is defined to 32 ``aarch64``. 33 34- ``ARM_ARCH_FEATURE``: Optional Arm Architecture build option which specifies 35 one or more feature modifiers. This option has the form ``[no]feature+...`` 36 and defaults to ``none``. It translates into compiler option 37 ``-march=armvX[.Y]-a+[no]feature+...``. See compiler's documentation for the 38 list of supported feature modifiers. 39 40- ``ARM_ARCH_MAJOR``: The major version of Arm Architecture to target when 41 compiling TF-A. Its value must be numeric, and defaults to 8 . See also, 42 *Armv8 Architecture Extensions* and *Armv7 Architecture Extensions* in 43 :ref:`Firmware Design`. 44 45- ``ARM_ARCH_MINOR``: The minor version of Arm Architecture to target when 46 compiling TF-A. Its value must be a numeric, and defaults to 0. See also, 47 *Armv8 Architecture Extensions* in :ref:`Firmware Design`. 48 49- ``ARM_BL2_SP_LIST_DTS``: Path to DTS file snippet to override the hardcoded 50 SP nodes in tb_fw_config. 51 52- ``ARM_SPMC_MANIFEST_DTS`` : path to an alternate manifest file used as the 53 SPMC Core manifest. Valid when ``SPD=spmd`` is selected. 54 55- ``BL2``: This is an optional build option which specifies the path to BL2 56 image for the ``fip`` target. In this case, the BL2 in the TF-A will not be 57 built. 58 59- ``BL2U``: This is an optional build option which specifies the path to 60 BL2U image. In this case, the BL2U in TF-A will not be built. 61 62- ``RESET_TO_BL2``: Boolean option to enable BL2 entrypoint as the CPU reset 63 vector instead of the BL1 entrypoint. It can take the value 0 (CPU reset to BL1 64 entrypoint) or 1 (CPU reset to BL2 entrypoint). 65 The default value is 0. 66 67- ``BL2_RUNS_AT_EL3``: This is an implicit flag to denote that BL2 runs at EL3. 68 While it is explicitly set to 1 when RESET_TO_BL2 is set to 1 it can also be 69 true in a 4-world system where RESET_TO_BL2 is 0. 70 71- ``BL2_ENABLE_SP_LOAD``: Boolean option to enable loading SP packages from the 72 FIP. Automatically enabled if ``SP_LAYOUT_FILE`` is provided. 73 74- ``BL2_IN_XIP_MEM``: In some use-cases BL2 will be stored in eXecute In Place 75 (XIP) memory, like BL1. In these use-cases, it is necessary to initialize 76 the RW sections in RAM, while leaving the RO sections in place. This option 77 enable this use-case. For now, this option is only supported 78 when RESET_TO_BL2 is set to '1'. 79 80- ``BL31``: This is an optional build option which specifies the path to 81 BL31 image for the ``fip`` target. In this case, the BL31 in TF-A will not 82 be built. 83 84- ``BL31_KEY``: This option is used when ``GENERATE_COT=1``. It specifies a 85 file that contains the BL31 private key in PEM format or a PKCS11 URI. If 86 ``SAVE_KEYS=1``, only a file is accepted and it will be used to save the key. 87 88- ``BL32``: This is an optional build option which specifies the path to 89 BL32 image for the ``fip`` target. In this case, the BL32 in TF-A will not 90 be built. 91 92- ``BL32_EXTRA1``: This is an optional build option which specifies the path to 93 Trusted OS Extra1 image for the ``fip`` target. 94 95- ``BL32_EXTRA2``: This is an optional build option which specifies the path to 96 Trusted OS Extra2 image for the ``fip`` target. 97 98- ``BL32_KEY``: This option is used when ``GENERATE_COT=1``. It specifies a 99 file that contains the BL32 private key in PEM format or a PKCS11 URI. If 100 ``SAVE_KEYS=1``, only a file is accepted and it will be used to save the key. 101 102- ``RMM``: This is an optional build option used when ``ENABLE_RME`` is set. 103 It specifies the path to RMM binary for the ``fip`` target. If the RMM option 104 is not specified, TF-A builds the TRP to load and run at R-EL2. 105 106- ``BL33``: Path to BL33 image in the host file system. This is mandatory for 107 ``fip`` target in case TF-A BL2 is used. 108 109- ``BL33_KEY``: This option is used when ``GENERATE_COT=1``. It specifies a 110 file that contains the BL33 private key in PEM format or a PKCS11 URI. If 111 ``SAVE_KEYS=1``, only a file is accepted and it will be used to save the key. 112 113- ``BRANCH_PROTECTION``: Numeric value to enable ARMv8.3 Pointer Authentication 114 and ARMv8.5 Branch Target Identification support for TF-A BL images themselves. 115 If enabled, it is needed to use a compiler that supports the option 116 ``-mbranch-protection``. The value of the ``-march`` (via ``ARM_ARCH_MINOR`` 117 and ``ARM_ARCH_MAJOR``) option will control which instructions will be 118 emitted (HINT space or not). Selects the branch protection features to use: 119- 0: Default value turns off all types of branch protection (FEAT_STATE_DISABLED) 120- 1: Enables all types of branch protection features 121- 2: Return address signing to its standard level 122- 3: Extend the signing to include leaf functions 123- 4: Turn on branch target identification mechanism 124- 5: Enables all types of branch protection features, only if present in 125 hardware (FEAT_STATE_CHECK). 126 127 The table below summarizes ``BRANCH_PROTECTION`` values, GCC compilation options 128 and resulting PAuth/BTI features. 129 130 +-------+--------------+-------+-----+ 131 | Value | GCC option | PAuth | BTI | 132 +=======+==============+=======+=====+ 133 | 0 | none | N | N | 134 +-------+--------------+-------+-----+ 135 | 1 | standard | Y | Y | 136 +-------+--------------+-------+-----+ 137 | 2 | pac-ret | Y | N | 138 +-------+--------------+-------+-----+ 139 | 3 | pac-ret+leaf | Y | N | 140 +-------+--------------+-------+-----+ 141 | 4 | bti | N | Y | 142 +-------+--------------+-------+-----+ 143 | 5 | dynamic | Y | Y | 144 +-------+--------------+-------+-----+ 145 146 This option defaults to 0. 147 Note that Pointer Authentication is enabled for Non-secure world 148 irrespective of the value of this option if the CPU supports it. 149 150- ``BUILD_MESSAGE_TIMESTAMP``: String used to identify the time and date of the 151 compilation of each build. It must be set to a C string (including quotes 152 where applicable). Defaults to a string that contains the time and date of 153 the compilation. 154 155- ``BUILD_STRING``: Input string for VERSION_STRING, which allows the TF-A 156 build to be uniquely identified. Defaults to the current git commit id. 157 158- ``BUILD_BASE``: Output directory for the build. Defaults to ``./build`` 159 160- ``CFLAGS``: Extra user options appended on the compiler's command line in 161 addition to the options set by the build system. 162 163- ``COLD_BOOT_SINGLE_CPU``: This option indicates whether the platform may 164 release several CPUs out of reset. It can take either 0 (several CPUs may be 165 brought up) or 1 (only one CPU will ever be brought up during cold reset). 166 Default is 0. If the platform always brings up a single CPU, there is no 167 need to distinguish between primary and secondary CPUs and the boot path can 168 be optimised. The ``plat_is_my_cpu_primary()`` and 169 ``plat_secondary_cold_boot_setup()`` platform porting interfaces do not need 170 to be implemented in this case. 171 172- ``COT``: When Trusted Boot is enabled, selects the desired chain of trust. 173 Defaults to ``tbbr``. 174 175- ``CRASH_REPORTING``: A non-zero value enables a console dump of processor 176 register state when an unexpected exception occurs during execution of 177 BL31. This option defaults to the value of ``DEBUG`` - i.e. by default 178 this is only enabled for a debug build of the firmware. 179 180- ``CREATE_KEYS``: This option is used when ``GENERATE_COT=1``. It tells the 181 certificate generation tool to create new keys in case no valid keys are 182 present or specified. Allowed options are '0' or '1'. Default is '1'. 183 184- ``CTX_INCLUDE_AARCH32_REGS`` : Boolean option that, when set to 1, will cause 185 the AArch32 system registers to be included when saving and restoring the 186 CPU context. The option must be set to 0 for AArch64-only platforms (that 187 is on hardware that does not implement AArch32, or at least not at EL1 and 188 higher ELs). Default value is 1. 189 190- ``CTX_INCLUDE_FPREGS``: Boolean option that, when set to 1, will cause the FP 191 registers to be included when saving and restoring the CPU context. Default 192 is 0. 193 194- ``CTX_INCLUDE_MPAM_REGS``: Boolean option that, when set to 1, will cause the 195 Memory System Resource Partitioning and Monitoring (MPAM) 196 registers to be included when saving and restoring the CPU context. 197 Default is '0'. 198 199- ``CTX_INCLUDE_NEVE_REGS``: Numeric value, when set will cause the Armv8.4-NV 200 registers to be saved/restored when entering/exiting an EL2 execution 201 context. This flag can take values 0 to 2, to align with the 202 ``ENABLE_FEAT`` mechanism. Default value is 0. 203 204- ``CTX_INCLUDE_PAUTH_REGS``: Numeric value to enable the Pointer 205 Authentication for Secure world. This will cause the ARMv8.3-PAuth registers 206 to be included when saving and restoring the CPU context as part of world 207 switch. Automatically enabled when ``BRANCH_PROTECTION`` is enabled. This flag 208 can take values 0 to 2, to align with ``ENABLE_FEAT`` mechanism. Default value 209 is 0. 210 211 Note that Pointer Authentication is enabled for Non-secure world irrespective 212 of the value of this flag if the CPU supports it. Alternatively, when 213 ``BRANCH_PROTECTION`` is enabled, this flag is superseded. 214 215- ``CTX_INCLUDE_SVE_REGS``: Boolean option that, when set to 1, will cause the 216 SVE registers to be included when saving and restoring the CPU context. Note 217 that this build option requires ``ENABLE_SVE_FOR_SWD`` to be enabled. In 218 general, it is recommended to perform SVE context management in lower ELs 219 and skip in EL3 due to the additional cost of maintaining large data 220 structures to track the SVE state. Hence, the default value is 0. 221 222- ``DEBUG``: Chooses between a debug and release build. It can take either 0 223 (release) or 1 (debug) as values. 0 is the default. 224 225- ``DECRYPTION_SUPPORT``: This build flag enables the user to select the 226 authenticated decryption algorithm to be used to decrypt firmware/s during 227 boot. It accepts 2 values: ``aes_gcm`` and ``none``. The default value of 228 this flag is ``none`` to disable firmware decryption which is an optional 229 feature as per TBBR. 230 231- ``DISABLE_BIN_GENERATION``: Boolean option to disable the generation 232 of the binary image. If set to 1, then only the ELF image is built. 233 0 is the default. 234 235- ``DISABLE_MTPMU``: Numeric option to disable ``FEAT_MTPMU`` (Multi Threaded 236 PMU). ``FEAT_MTPMU`` is an optional feature available on Armv8.6 onwards. 237 This flag can take values 0 to 2, to align with the ``ENABLE_FEAT`` 238 mechanism. Default is ``0``. 239 240- ``DYN_DISABLE_AUTH``: Provides the capability to dynamically disable Trusted 241 Board Boot authentication at runtime. This option is meant to be enabled only 242 for development platforms. ``TRUSTED_BOARD_BOOT`` flag must be set if this 243 flag has to be enabled. 0 is the default. 244 245- ``E``: Boolean option to make warnings into errors. Default is 1. 246 247 When specifying higher warnings levels (``W=1`` and higher), this option 248 defaults to 0. This is done to encourage contributors to use them, as they 249 are expected to produce warnings that would otherwise fail the build. New 250 contributions are still expected to build with ``W=0`` and ``E=1`` (the 251 default). 252 253- ``EARLY_CONSOLE``: This option is used to enable early traces before default 254 console is properly setup. It introduces EARLY_* traces macros, that will 255 use the non-EARLY traces macros if the flag is enabled, or do nothing 256 otherwise. To use this feature, platforms will have to create the function 257 plat_setup_early_console(). 258 Default is 0 (disabled) 259 260- ``EL3_PAYLOAD_BASE``: This option enables booting an EL3 payload instead of 261 the normal boot flow. It must specify the entry point address of the EL3 262 payload. Please refer to the "Booting an EL3 payload" section for more 263 details. 264 265- ``ENABLE_AMU_AUXILIARY_COUNTERS``: Enables support for AMU auxiliary counters 266 (also known as group 1 counters). These are implementation-defined counters, 267 and as such require additional platform configuration. Default is 0. 268 269- ``ENABLE_ASSERTIONS``: This option controls whether or not calls to ``assert()`` 270 are compiled out. For debug builds, this option defaults to 1, and calls to 271 ``assert()`` are left in place. For release builds, this option defaults to 0 272 and calls to ``assert()`` function are compiled out. This option can be set 273 independently of ``DEBUG``. It can also be used to hide any auxiliary code 274 that is only required for the assertion and does not fit in the assertion 275 itself. 276 277- ``ENABLE_BACKTRACE``: This option controls whether to enable backtrace 278 dumps or not. It is supported in both AArch64 and AArch32. However, in 279 AArch32 the format of the frame records are not defined in the AAPCS and they 280 are defined by the implementation. This implementation of backtrace only 281 supports the format used by GCC when T32 interworking is disabled. For this 282 reason enabling this option in AArch32 will force the compiler to only 283 generate A32 code. This option is enabled by default only in AArch64 debug 284 builds, but this behaviour can be overridden in each platform's Makefile or 285 in the build command line. 286 287- ``ENABLE_FEAT`` 288 The Arm architecture defines several architecture extension features, 289 named FEAT_xxx in the architecure manual. Some of those features require 290 setup code in higher exception levels, other features might be used by TF-A 291 code itself. 292 Most of the feature flags defined in the TF-A build system permit to take 293 the values 0, 1 or 2, with the following meaning: 294 295 :: 296 297 ENABLE_FEAT_* = 0: Feature is disabled statically at compile time. 298 ENABLE_FEAT_* = 1: Feature is enabled unconditionally at compile time. 299 ENABLE_FEAT_* = 2: Feature is enabled, but checked at runtime. 300 301 When setting the flag to 0, the feature is disabled during compilation, 302 and the compiler's optimisation stage and the linker will try to remove 303 as much of this code as possible. 304 If it is defined to 1, the code will use the feature unconditionally, so the 305 CPU is expected to support that feature. The FEATURE_DETECTION debug 306 feature, if enabled, will verify this. 307 If the feature flag is set to 2, support for the feature will be compiled 308 in, but its existence will be checked at runtime, so it works on CPUs with 309 or without the feature. This is mostly useful for platforms which either 310 support multiple different CPUs, or where the CPU is configured at runtime, 311 like in emulators. 312 313- ``ENABLE_FEAT_AMU``: Numeric value to enable Activity Monitor Unit 314 extensions. This flag can take the values 0 to 2, to align with the 315 ``ENABLE_FEAT`` mechanism. This is an optional architectural feature 316 available on v8.4 onwards. Some v8.2 implementations also implement an AMU 317 and this option can be used to enable this feature on those systems as well. 318 This flag can take the values 0 to 2, the default is 0. 319 320- ``ENABLE_FEAT_AMUv1p1``: Numeric value to enable the ``FEAT_AMUv1p1`` 321 extension. ``FEAT_AMUv1p1`` is an optional feature available on Arm v8.6 322 onwards. This flag can take the values 0 to 2, to align with the 323 ``ENABLE_FEAT`` mechanism. Default value is ``0``. 324 325- ``ENABLE_FEAT_CSV2_2``: Numeric value to enable the ``FEAT_CSV2_2`` 326 extension. It allows access to the SCXTNUM_EL2 (Software Context Number) 327 register during EL2 context save/restore operations. ``FEAT_CSV2_2`` is an 328 optional feature available on Arm v8.0 onwards. This flag can take values 329 0 to 2, to align with the ``ENABLE_FEAT`` mechanism. 330 Default value is ``0``. 331 332- ``ENABLE_FEAT_CSV2_3``: Numeric value to enable support for ``FEAT_CSV2_3`` 333 extension. This feature is supported in AArch64 state only and is an optional 334 feature available in Arm v8.0 implementations. 335 ``FEAT_CSV2_3`` implies the implementation of ``FEAT_CSV2_2``. 336 The flag can take values 0 to 2, to align with the ``ENABLE_FEAT`` 337 mechanism. Default value is ``0``. 338 339- ``ENABLE_FEAT_DEBUGV8P9``: Numeric value to enable ``FEAT_DEBUGV8P9`` 340 extension which allows the ability to implement more than 16 breakpoints 341 and/or watchpoints. This feature is mandatory from v8.9 and is optional 342 from v8.8. This flag can take the values of 0 to 2, to align with the 343 ``ENABLE_FEAT`` mechanism. Default value is ``0``. 344 345- ``ENABLE_FEAT_DIT``: Numeric value to enable ``FEAT_DIT`` (Data Independent 346 Timing) extension. It allows setting the ``DIT`` bit of PSTATE in EL3. 347 ``FEAT_DIT`` is a mandatory architectural feature and is enabled from v8.4 348 and upwards. This flag can take the values 0 to 2, to align with the 349 ``ENABLE_FEAT`` mechanism. Default value is ``0``. 350 351- ``ENABLE_FEAT_ECV``: Numeric value to enable support for the Enhanced Counter 352 Virtualization feature, allowing for access to the CNTPOFF_EL2 (Counter-timer 353 Physical Offset register) during EL2 to EL3 context save/restore operations. 354 Its a mandatory architectural feature and is enabled from v8.6 and upwards. 355 This flag can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 356 mechanism. Default value is ``0``. 357 358- ``ENABLE_FEAT_FPMR``: Numerical value to enable support for Floating Point 359 Mode Register feature, allowing access to the FPMR register. FPMR register 360 controls the behaviors of FP8 instructions. It is an optional architectural 361 feature from v9.2 and upwards. This flag can take value of 0 to 2, to align 362 with the ``FEATURE_DETECTION`` mechanism. Default value is ``0``. 363 364- ``ENABLE_FEAT_FGT``: Numeric value to enable support for FGT (Fine Grain Traps) 365 feature allowing for access to the HDFGRTR_EL2 (Hypervisor Debug Fine-Grained 366 Read Trap Register) during EL2 to EL3 context save/restore operations. 367 Its a mandatory architectural feature and is enabled from v8.6 and upwards. 368 This flag can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 369 mechanism. Default value is ``0``. 370 371- ``ENABLE_FEAT_FGT2``: Numeric value to enable support for FGT2 372 (Fine Grain Traps 2) feature allowing for access to Fine-grained trap 2 registers 373 during EL2 to EL3 context save/restore operations. 374 Its an optional architectural feature and is available from v8.8 and upwards. 375 This flag can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 376 mechanism. Default value is ``0``. 377 378- ``ENABLE_FEAT_FGWTE3``: Numeric value to enable support for 379 Fine Grained Write Trap EL3 (FEAT_FGWTE3), a feature that allows EL3 to 380 restrict overwriting certain EL3 registers after boot. 381 This lockdown is established by setting individual trap bits for 382 system registers that are not expected to be overwritten after boot. 383 This feature is an optional architectural feature and is available from 384 Armv9.4 onwards. This flag can take values from 0 to 2, aligning with 385 the ``ENABLE_FEAT`` mechanism. The default value is 0. 386 387 .. note:: 388 This feature currently traps access to all EL3 registers in 389 ``FGWTE3_EL3``, except for ``MDCR_EL3``, ``MPAM3_EL3``, 390 ``TPIDR_EL3``(when ``CRASH_REPORTING=1``), and 391 ``SCTLR_EL3``(when ``HW_ASSISTED_COHERENCY=0``). 392 If additional traps need to be disabled for specific platforms, 393 please contact the Arm team on `TF-A public mailing list`_. 394 395- ``ENABLE_FEAT_HCX``: Numeric value to set the bit SCR_EL3.HXEn in EL3 to 396 allow access to HCRX_EL2 (extended hypervisor control register) from EL2 as 397 well as adding HCRX_EL2 to the EL2 context save/restore operations. Its a 398 mandatory architectural feature and is enabled from v8.7 and upwards. This 399 flag can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 400 mechanism. Default value is ``0``. 401 402- ``ENABLE_FEAT_MOPS``: Numeric value to enable FEAT_MOPS (Standardization 403 of memory operations) when INIT_UNUSED_NS_EL2=1. 404 This feature is mandatory from v8.8 and enabling of FEAT_MOPS does not 405 require any settings from EL3 as the controls are present in EL2 registers 406 (HCRX_EL2.{MSCEn,MCE2} and SCTLR_EL2.MSCEn) and in most configurations 407 we expect EL2 to be present. But in case of INIT_UNUSED_NS_EL2=1 , 408 EL3 should configure the EL2 registers. This flag 409 can take values 0 to 2, to align with the ``ENABLE_FEAT`` mechanism. 410 Default value is ``0``. 411 412- ``ENABLE_FEAT_MTE2``: Numeric value to enable Memory Tagging Extension2 413 if the platform wants to use this feature and MTE2 is enabled at ELX. 414 This flag can take values 0 to 2, to align with the ``ENABLE_FEAT`` 415 mechanism. Default value is ``0``. 416 417- ``ENABLE_FEAT_PAN``: Numeric value to enable the ``FEAT_PAN`` (Privileged 418 Access Never) extension. ``FEAT_PAN`` adds a bit to PSTATE, generating a 419 permission fault for any privileged data access from EL1/EL2 to virtual 420 memory address, accessible at EL0, provided (HCR_EL2.E2H=1). It is a 421 mandatory architectural feature and is enabled from v8.1 and upwards. This 422 flag can take values 0 to 2, to align with the ``ENABLE_FEAT`` 423 mechanism. Default value is ``0``. 424 425- ``ENABLE_FEAT_PAUTH_LR``: Numeric value to enable the ``FEAT_PAUTH_LR`` 426 extension. ``FEAT_PAUTH_LR`` is an optional feature available from Arm v9.4 427 onwards. This feature requires PAUTH to be enabled via the 428 ``BRANCH_PROTECTION`` flag. This flag can take the values 0 to 2, to align 429 with the ``ENABLE_FEAT`` mechanism. Default value is ``0``. 430 431- ``ENABLE_FEAT_RNG``: Numeric value to enable the ``FEAT_RNG`` extension. 432 ``FEAT_RNG`` is an optional feature available on Arm v8.5 onwards. This 433 flag can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 434 mechanism. Default value is ``0``. 435 436- ``ENABLE_FEAT_RNG_TRAP``: Numeric value to enable the ``FEAT_RNG_TRAP`` 437 extension. This feature is only supported in AArch64 state. This flag can 438 take values 0 to 2, to align with the ``ENABLE_FEAT`` mechanism. 439 Default value is ``0``. ``FEAT_RNG_TRAP`` is an optional feature from 440 Armv8.5 onwards. 441 442- ``ENABLE_FEAT_SB``: Boolean option to let the TF-A code use the ``FEAT_SB`` 443 (Speculation Barrier) instruction ``FEAT_SB`` is an optional feature and 444 defaults to ``0`` for pre-Armv8.5 CPUs, but is mandatory for Armv8.5 or 445 later CPUs. It is enabled from v8.5 and upwards and if needed can be 446 overidden from platforms explicitly. 447 448- ``ENABLE_FEAT_SEL2``: Numeric value to enable the ``FEAT_SEL2`` (Secure EL2) 449 extension. ``FEAT_SEL2`` is a mandatory feature available on Arm v8.4. 450 This flag can take values 0 to 2, to align with the ``ENABLE_FEAT`` 451 mechanism. Default is ``0``. 452 453- ``ENABLE_FEAT_TWED``: Numeric value to enable the ``FEAT_TWED`` (Delayed 454 trapping of WFE Instruction) extension. ``FEAT_TWED`` is a optional feature 455 available on Arm v8.6. This flag can take values 0 to 2, to align with the 456 ``ENABLE_FEAT`` mechanism. Default is ``0``. 457 458 When ``ENABLE_FEAT_TWED`` is set to ``1``, WFE instruction trapping gets 459 delayed by the amount of value in ``TWED_DELAY``. 460 461- ``ENABLE_FEAT_VHE``: Numeric value to enable the ``FEAT_VHE`` (Virtualization 462 Host Extensions) extension. It allows access to CONTEXTIDR_EL2 register 463 during EL2 context save/restore operations.``FEAT_VHE`` is a mandatory 464 architectural feature and is enabled from v8.1 and upwards. It can take 465 values 0 to 2, to align with the ``ENABLE_FEAT`` mechanism. 466 Default value is ``0``. 467 468- ``ENABLE_FEAT_TCR2``: Numeric value to set the bit SCR_EL3.ENTCR2 in EL3 to 469 allow access to TCR2_EL2 (extended translation control) from EL2 as 470 well as adding TCR2_EL2 to the EL2 context save/restore operations. Its a 471 mandatory architectural feature and is enabled from v8.9 and upwards. This 472 flag can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 473 mechanism. Default value is ``0``. 474 475- ``ENABLE_FEAT_S2PIE``: Numeric value to enable support for FEAT_S2PIE 476 at EL2 and below, and context switch relevant registers. This flag 477 can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 478 mechanism. Default value is ``0``. 479 480- ``ENABLE_FEAT_S1PIE``: Numeric value to enable support for FEAT_S1PIE 481 at EL2 and below, and context switch relevant registers. This flag 482 can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 483 mechanism. Default value is ``0``. 484 485- ``ENABLE_FEAT_S2POE``: Numeric value to enable support for FEAT_S2POE 486 at EL2 and below, and context switch relevant registers. This flag 487 can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 488 mechanism. Default value is ``0``. 489 490- ``ENABLE_FEAT_S1POE``: Numeric value to enable support for FEAT_S1POE 491 at EL2 and below, and context switch relevant registers. This flag 492 can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 493 mechanism. Default value is ``0``. 494 495- ``ENABLE_FEAT_GCS``: Numeric value to set the bit SCR_EL3.GCSEn in EL3 to 496 allow use of Guarded Control Stack from EL2 as well as adding the GCS 497 registers to the EL2 context save/restore operations. This flag can take 498 the values 0 to 2, to align with the ``ENABLE_FEAT`` mechanism. 499 Default value is ``0``. 500 501 - ``ENABLE_FEAT_GCIE``: Boolean value to enable support for the GICv5 CPU 502 interface (see ``USE_GIC_DRIVER`` for the IRI). GICv5 and GICv3 are mutually 503 exclusive, so the ``ENABLE_FEAT`` mechanism is currently not supported. 504 Default value is ``0``. 505 506- ``ENABLE_FEAT_THE``: Numeric value to enable support for FEAT_THE 507 (Translation Hardening Extension) at EL2 and below, setting the bit 508 SCR_EL3.RCWMASKEn in EL3 to allow access to RCWMASK_EL1 and RCWSMASK_EL1 509 registers and context switch them. 510 Its an optional architectural feature and is available from v8.8 and upwards. 511 This flag can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 512 mechanism. Default value is ``0``. 513 514- ``ENABLE_FEAT_SCTLR2``: Numeric value to enable support for FEAT_SCTLR2 515 (Extension to SCTLR_ELx) at EL2 and below, setting the bit 516 SCR_EL3.SCTLR2En in EL3 to allow access to SCTLR2_ELx registers and 517 context switch them. This feature is OPTIONAL from Armv8.0 implementations 518 and mandatory in Armv8.9 implementations. 519 This flag can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 520 mechanism. Default value is ``0``. 521 522- ``ENABLE_FEAT_D128``: Numeric value to enable support for FEAT_D128 523 at EL2 and below, setting the bit SCT_EL3.D128En in EL3 to allow access to 524 128 bit version of system registers like PAR_EL1, TTBR0_EL1, TTBR1_EL1, 525 TTBR0_EL2, TTBR1_EL2, TTBR0_EL12, TTBR1_EL12 , VTTBR_EL2, RCWMASK_EL1, and 526 RCWSMASK_EL1. Its an optional architectural feature and is available from 527 9.3 and upwards. 528 This flag can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 529 mechanism. Default value is ``0``. 530 531- ``ENABLE_LTO``: Boolean option to enable Link Time Optimization (LTO) 532 support in GCC for TF-A. This option is currently only supported for 533 AArch64. Default is 0. 534 535- ``ENABLE_FEAT_MPAM``: Numeric value to enable lower ELs to use MPAM 536 feature. MPAM is an optional Armv8.4 extension that enables various memory 537 system components and resources to define partitions; software running at 538 various ELs can assign themselves to desired partition to control their 539 performance aspects. 540 541 This flag can take values 0 to 2, to align with the ``ENABLE_FEAT`` 542 mechanism. When this option is set to ``1`` or ``2``, EL3 allows lower ELs to 543 access their own MPAM registers without trapping into EL3. This option 544 doesn't make use of partitioning in EL3, however. Platform initialisation 545 code should configure and use partitions in EL3 as required. This option 546 defaults to ``2`` since MPAM is enabled by default for NS world only. 547 The flag is automatically disabled when the target 548 architecture is AArch32. 549 550- ``ENABLE_FEAT_LS64_ACCDATA``: Numeric value to enable access and save and 551 restore the ACCDATA_EL1 system register, at EL2 and below. This flag can 552 take the values 0 to 2, to align with the ``ENABLE_FEAT`` mechanism. 553 Default value is ``0``. 554 555- ``ENABLE_MPMM``: Boolean option to enable support for the Maximum Power 556 Mitigation Mechanism supported by certain Arm cores, which allows the SoC 557 firmware to detect and limit high activity events to assist in SoC processor 558 power domain dynamic power budgeting and limit the triggering of whole-rail 559 (i.e. clock chopping) responses to overcurrent conditions. Defaults to ``0``. 560 561- ``ENABLE_PIE``: Boolean option to enable Position Independent Executable(PIE) 562 support within generic code in TF-A. This option is currently only supported 563 in BL2, BL31, and BL32 (TSP) for AARCH64 binaries, and 564 in BL32 (SP_min) for AARCH32. Default is 0. 565 566- ``ENABLE_PMF``: Boolean option to enable support for optional Performance 567 Measurement Framework(PMF). Default is 0. 568 569- ``ENABLE_PSCI_STAT``: Boolean option to enable support for optional PSCI 570 functions ``PSCI_STAT_RESIDENCY`` and ``PSCI_STAT_COUNT``. Default is 0. 571 In the absence of an alternate stat collection backend, ``ENABLE_PMF`` must 572 be enabled. If ``ENABLE_PMF`` is set, the residency statistics are tracked in 573 software. 574 575- ``ENABLE_RUNTIME_INSTRUMENTATION``: Boolean option to enable runtime 576 instrumentation which injects timestamp collection points into TF-A to 577 allow runtime performance to be measured. Currently, only PSCI is 578 instrumented. Enabling this option enables the ``ENABLE_PMF`` build option 579 as well. Default is 0. 580 581- ``ENABLE_SPE_FOR_NS`` : Numeric value to enable Statistical Profiling 582 extensions. This is an optional architectural feature for AArch64. 583 This flag can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 584 mechanism. The default is 2 but is automatically disabled when the target 585 architecture is AArch32. 586 587- ``ENABLE_SVE_FOR_NS``: Numeric value to enable Scalable Vector Extension 588 (SVE) for the Non-secure world only. SVE is an optional architectural feature 589 for AArch64. This flag can take the values 0 to 2, to align with the 590 ``ENABLE_FEAT`` mechanism. At this time, this build option cannot be used on 591 systems that have SPM_MM enabled. The default value is 2. 592 593 Note that when SVE is enabled for the Non-secure world, access 594 to SVE, SIMD and floating-point functionality from the Secure world is 595 independently controlled by build option ``ENABLE_SVE_FOR_SWD``. When enabling 596 ``CTX_INCLUDE_FPREGS`` and ``ENABLE_SVE_FOR_NS`` together, it is mandatory to 597 enable ``CTX_INCLUDE_SVE_REGS``. This is to avoid corruption of the Non-secure 598 world data in the Z-registers which are aliased by the SIMD and FP registers. 599 600- ``ENABLE_SVE_FOR_SWD``: Boolean option to enable SVE and FPU/SIMD functionality 601 for the Secure world. SVE is an optional architectural feature for AArch64. 602 The default is 0 and it is automatically disabled when the target architecture 603 is AArch32. 604 605 .. note:: 606 This build flag requires ``ENABLE_SVE_FOR_NS`` to be enabled. When enabling 607 ``ENABLE_SVE_FOR_SWD``, a developer must carefully consider whether 608 ``CTX_INCLUDE_SVE_REGS`` is also needed. 609 610- ``ENABLE_STACK_PROTECTOR``: String option to enable the stack protection 611 checks in GCC. Allowed values are "all", "strong", "default" and "none". The 612 default value is set to "none". "strong" is the recommended stack protection 613 level if this feature is desired. "none" disables the stack protection. For 614 all values other than "none", the ``plat_get_stack_protector_canary()`` 615 platform hook needs to be implemented. The value is passed as the last 616 component of the option ``-fstack-protector-$ENABLE_STACK_PROTECTOR``. 617 618- ``ENABLE_ERRATA_ALL``: This option is used only for testing purposes, Boolean 619 option to enable the workarounds for all errata that TF-A implements. Normally 620 they should be explicitly enabled depending on each platform's needs. Not 621 recommended for release builds. This option is default set to 0. 622 623- ``ENCRYPT_BL31``: Binary flag to enable encryption of BL31 firmware. This 624 flag depends on ``DECRYPTION_SUPPORT`` build flag. 625 626- ``ENCRYPT_BL32``: Binary flag to enable encryption of Secure BL32 payload. 627 This flag depends on ``DECRYPTION_SUPPORT`` build flag. 628 629- ``ENC_KEY``: A 32-byte (256-bit) symmetric key in hex string format. It could 630 either be SSK or BSSK depending on ``FW_ENC_STATUS`` flag. This value depends 631 on ``DECRYPTION_SUPPORT`` build flag. 632 633- ``ENC_NONCE``: A 12-byte (96-bit) encryption nonce or Initialization Vector 634 (IV) in hex string format. This value depends on ``DECRYPTION_SUPPORT`` 635 build flag. 636 637- ``ERROR_DEPRECATED``: This option decides whether to treat the usage of 638 deprecated platform APIs, helper functions or drivers within Trusted 639 Firmware as error. It can take the value 1 (flag the use of deprecated 640 APIs as error) or 0. The default is 0. 641 642- ``ETHOSN_NPU_DRIVER``: boolean option to enable a SiP service that can 643 configure an Arm® Ethos™-N NPU. To use this service the target platform's 644 ``HW_CONFIG`` must include the device tree nodes for the NPU. Currently, only 645 the Arm Juno platform has this included in its ``HW_CONFIG`` and the platform 646 only loads the ``HW_CONFIG`` in AArch64 builds. Default is 0. 647 648- ``ETHOSN_NPU_TZMP1``: boolean option to enable TZMP1 support for the 649 Arm® Ethos™-N NPU. Requires ``ETHOSN_NPU_DRIVER`` and 650 ``TRUSTED_BOARD_BOOT`` to be enabled. 651 652- ``ETHOSN_NPU_FW``: location of the NPU firmware binary 653 (```ethosn.bin```). This firmware image will be included in the FIP and 654 loaded at runtime. 655 656- ``EL3_EXCEPTION_HANDLING``: When set to ``1``, enable handling of exceptions 657 targeted at EL3. When set ``0`` (default), no exceptions are expected or 658 handled at EL3, and a panic will result. The exception to this rule is when 659 ``SPMD_SPM_AT_SEL2`` is set to ``1``, in which case, only exceptions 660 occuring during normal world execution, are trapped to EL3. Any exception 661 trapped during secure world execution are trapped to the SPMC. This is 662 supported only for AArch64 builds. 663 664- ``EVENT_LOG_LEVEL``: Chooses the log level to use for Measured Boot when 665 ``MEASURED_BOOT`` is enabled. For a list of valid values, see ``LOG_LEVEL``. 666 Default value is 40 (LOG_LEVEL_INFO). 667 668- ``FAULT_INJECTION_SUPPORT``: ARMv8.4 extensions introduced support for fault 669 injection from lower ELs, and this build option enables lower ELs to use 670 Error Records accessed via System Registers to inject faults. This is 671 applicable only to AArch64 builds. 672 673 This feature is intended for testing purposes only, and is advisable to keep 674 disabled for production images. 675 676- ``FIP_NAME``: This is an optional build option which specifies the FIP 677 filename for the ``fip`` target. Default is ``fip.bin``. 678 679- ``FWU_FIP_NAME``: This is an optional build option which specifies the FWU 680 FIP filename for the ``fwu_fip`` target. Default is ``fwu_fip.bin``. 681 682- ``FW_ENC_STATUS``: Top level firmware's encryption numeric flag, values: 683 684 :: 685 686 0: Encryption is done with Secret Symmetric Key (SSK) which is common 687 for a class of devices. 688 1: Encryption is done with Binding Secret Symmetric Key (BSSK) which is 689 unique per device. 690 691 This flag depends on ``DECRYPTION_SUPPORT`` build flag. 692 693- ``GENERATE_COT``: Boolean flag used to build and execute the ``cert_create`` 694 tool to create certificates as per the Chain of Trust described in 695 :ref:`Trusted Board Boot`. The build system then calls ``fiptool`` to 696 include the certificates in the FIP and FWU_FIP. Default value is '0'. 697 698 Specify both ``TRUSTED_BOARD_BOOT=1`` and ``GENERATE_COT=1`` to include support 699 for the Trusted Board Boot feature in the BL1 and BL2 images, to generate 700 the corresponding certificates, and to include those certificates in the 701 FIP and FWU_FIP. 702 703 Note that if ``TRUSTED_BOARD_BOOT=0`` and ``GENERATE_COT=1``, the BL1 and BL2 704 images will not include support for Trusted Board Boot. The FIP will still 705 include the corresponding certificates. This FIP can be used to verify the 706 Chain of Trust on the host machine through other mechanisms. 707 708 Note that if ``TRUSTED_BOARD_BOOT=1`` and ``GENERATE_COT=0``, the BL1 and BL2 709 images will include support for Trusted Board Boot, but the FIP and FWU_FIP 710 will not include the corresponding certificates, causing a boot failure. 711 712- ``GICV2_G0_FOR_EL3``: Unlike GICv3, the GICv2 architecture doesn't have 713 inherent support for specific EL3 type interrupts. Setting this build option 714 to ``1`` assumes GICv2 *Group 0* interrupts are expected to target EL3, both 715 by :ref:`platform abstraction layer<platform Interrupt Controller API>` and 716 :ref:`Interrupt Management Framework<Interrupt Management Framework>`. 717 This allows GICv2 platforms to enable features requiring EL3 interrupt type. 718 This also means that all GICv2 Group 0 interrupts are delivered to EL3, and 719 the Secure Payload interrupts needs to be synchronously handed over to Secure 720 EL1 for handling. The default value of this option is ``0``, which means the 721 Group 0 interrupts are assumed to be handled by Secure EL1. 722 723- ``HANDLE_EA_EL3_FIRST_NS``: When set to ``1``, External Aborts and SError 724 Interrupts, resulting from errors in NS world, will be always trapped in 725 EL3 i.e. in BL31 at runtime. When set to ``0`` (default), these exceptions 726 will be trapped in the current exception level (or in EL1 if the current 727 exception level is EL0). 728 729- ``HW_ASSISTED_COHERENCY``: On most Arm systems to-date, platform-specific 730 software operations are required for CPUs to enter and exit coherency. 731 However, newer systems exist where CPUs' entry to and exit from coherency 732 is managed in hardware. Such systems require software to only initiate these 733 operations, and the rest is managed in hardware, minimizing active software 734 management. In such systems, this boolean option enables TF-A to carry out 735 build and run-time optimizations during boot and power management operations. 736 This option defaults to 0 and if it is enabled, then it implies 737 ``WARMBOOT_ENABLE_DCACHE_EARLY`` is also enabled. 738 739 If this flag is disabled while the platform which TF-A is compiled for 740 includes cores that manage coherency in hardware, then a compilation error is 741 generated. This is based on the fact that a system cannot have, at the same 742 time, cores that manage coherency in hardware and cores that don't. In other 743 words, a platform cannot have, at the same time, cores that require 744 ``HW_ASSISTED_COHERENCY=1`` and cores that require 745 ``HW_ASSISTED_COHERENCY=0``. 746 747 Note that, when ``HW_ASSISTED_COHERENCY`` is enabled, version 2 of 748 translation library (xlat tables v2) must be used; version 1 of translation 749 library is not supported. 750 751- ``IMPDEF_SYSREG_TRAP``: Numeric value to enable the handling traps for 752 implementation defined system register accesses from lower ELs. Default 753 value is ``0``. 754 755- ``INVERTED_MEMMAP``: memmap tool print by default lower addresses at the 756 bottom, higher addresses at the top. This build flag can be set to '1' to 757 invert this behavior. Lower addresses will be printed at the top and higher 758 addresses at the bottom. 759 760- ``INIT_UNUSED_NS_EL2``: This build flag guards code that disables EL2 761 safely in scenario where NS-EL2 is present but unused. This flag is set to 0 762 by default. Platforms without NS-EL2 in use must enable this flag. 763 764- ``KEY_ALG``: This build flag enables the user to select the algorithm to be 765 used for generating the PKCS keys and subsequent signing of the certificate. 766 It accepts 5 values: ``rsa``, ``rsa_1_5``, ``ecdsa``, ``ecdsa-brainpool-regular`` 767 and ``ecdsa-brainpool-twisted``. The option ``rsa_1_5`` is the legacy PKCS#1 768 RSA 1.5 algorithm which is not TBBR compliant and is retained only for 769 compatibility. The default value of this flag is ``rsa`` which is the TBBR 770 compliant PKCS#1 RSA 2.1 scheme. 771 772- ``KEY_SIZE``: This build flag enables the user to select the key size for 773 the algorithm specified by ``KEY_ALG``. The valid values for ``KEY_SIZE`` 774 depend on the chosen algorithm and the cryptographic module. 775 776 +---------------------------+------------------------------------+ 777 | KEY_ALG | Possible key sizes | 778 +===========================+====================================+ 779 | rsa | 1024 , 2048 (default), 3072, 4096 | 780 +---------------------------+------------------------------------+ 781 | ecdsa | 256 (default), 384 | 782 +---------------------------+------------------------------------+ 783 | ecdsa-brainpool-regular | 256 (default) | 784 +---------------------------+------------------------------------+ 785 | ecdsa-brainpool-twisted | 256 (default) | 786 +---------------------------+------------------------------------+ 787 788- ``HASH_ALG``: This build flag enables the user to select the secure hash 789 algorithm. It accepts 3 values: ``sha256``, ``sha384`` and ``sha512``. 790 The default value of this flag is ``sha256``. 791 792- ``LDFLAGS``: Extra user options appended to the linkers' command line in 793 addition to the one set by the build system. 794 795- ``LOG_LEVEL``: Chooses the log level, which controls the amount of console log 796 output compiled into the build. This should be one of the following: 797 798 :: 799 800 0 (LOG_LEVEL_NONE) 801 10 (LOG_LEVEL_ERROR) 802 20 (LOG_LEVEL_NOTICE) 803 30 (LOG_LEVEL_WARNING) 804 40 (LOG_LEVEL_INFO) 805 50 (LOG_LEVEL_VERBOSE) 806 807 All log output up to and including the selected log level is compiled into 808 the build. The default value is 40 in debug builds and 20 in release builds. 809 810- ``MEASURED_BOOT``: Boolean flag to include support for the Measured Boot 811 feature. This flag can be enabled with ``TRUSTED_BOARD_BOOT`` in order to 812 provide trust that the code taking the measurements and recording them has 813 not been tampered with. 814 815 This option defaults to 0. 816 817- ``DISCRETE_TPM``: Boolean flag to include support for a Discrete TPM. 818 819 This option defaults to 0. 820 821- ``TPM_INTERFACE``: When ``DISCRETE_TPM=1``, this is a required flag to 822 select the TPM interface. Currently only one interface is supported: 823 824 :: 825 826 FIFO_SPI 827 828- ``MBOOT_TPM_HASH_ALG``: Build flag to select the TPM hash algorithm used during 829 Measured Boot. Currently only accepts ``sha256`` as a valid algorithm. 830 831- ``MARCH_DIRECTIVE``: used to pass a -march option from the platform build 832 options to the compiler. An example usage: 833 834 .. code:: make 835 836 MARCH_DIRECTIVE := -march=armv8.5-a 837 838- ``HARDEN_SLS``: used to pass -mharden-sls=all from the TF-A build 839 options to the compiler currently supporting only of the options. 840 GCC documentation: 841 https://gcc.gnu.org/onlinedocs/gcc/AArch64-Options.html#index-mharden-sls 842 843 An example usage: 844 845 .. code:: make 846 847 HARDEN_SLS := 1 848 849 This option defaults to 0. 850 851- ``NON_TRUSTED_WORLD_KEY``: This option is used when ``GENERATE_COT=1``. It 852 specifies a file that contains the Non-Trusted World private key in PEM 853 format or a PKCS11 URI. If ``SAVE_KEYS=1``, only a file is accepted and it 854 will be used to save the key. 855 856- ``NS_BL2U``: Path to NS_BL2U image in the host file system. This image is 857 optional. It is only needed if the platform makefile specifies that it 858 is required in order to build the ``fwu_fip`` target. 859 860- ``NS_TIMER_SWITCH``: Enable save and restore for non-secure timer register 861 contents upon world switch. It can take either 0 (don't save and restore) or 862 1 (do save and restore). 0 is the default. An SPD may set this to 1 if it 863 wants the timer registers to be saved and restored. 864 865- ``OVERRIDE_LIBC``: This option allows platforms to override the default libc 866 for the BL image. It can be either 0 (include) or 1 (remove). The default 867 value is 0. 868 869- ``PL011_GENERIC_UART``: Boolean option to indicate the PL011 driver that 870 the underlying hardware is not a full PL011 UART but a minimally compliant 871 generic UART, which is a subset of the PL011. The driver will not access 872 any register that is not part of the SBSA generic UART specification. 873 Default value is 0 (a full PL011 compliant UART is present). 874 875- ``PLAT``: Choose a platform to build TF-A for. The chosen platform name 876 must be subdirectory of any depth under ``plat/``, and must contain a 877 platform makefile named ``platform.mk``. For example, to build TF-A for the 878 Arm Juno board, select PLAT=juno. 879 880- ``PLATFORM_REPORT_CTX_MEM_USE``: Reports the context memory allocated for 881 each core as well as the global context. The data includes the memory used 882 by each world and each privileged exception level. This build option is 883 applicable only for ``ARCH=aarch64`` builds. The default value is 0. 884 885- ``PRELOADED_BL33_BASE``: This option enables booting a preloaded BL33 image 886 instead of the normal boot flow. When defined, it must specify the entry 887 point address for the preloaded BL33 image. This option is incompatible with 888 ``EL3_PAYLOAD_BASE``. If both are defined, ``EL3_PAYLOAD_BASE`` has priority 889 over ``PRELOADED_BL33_BASE``. 890 891- ``PRESERVE_DSU_PMU_REGS``: This options when enabled allows the platform to 892 save/restore the DynamIQ Shared Unit's(DSU) Performance Monitoring Unit(PMU) 893 registers when the cluster goes through a power cycle. This is disabled by 894 default and platforms that require this feature have to enable them. 895 896- ``PROGRAMMABLE_RESET_ADDRESS``: This option indicates whether the reset 897 vector address can be programmed or is fixed on the platform. It can take 898 either 0 (fixed) or 1 (programmable). Default is 0. If the platform has a 899 programmable reset address, it is expected that a CPU will start executing 900 code directly at the right address, both on a cold and warm reset. In this 901 case, there is no need to identify the entrypoint on boot and the boot path 902 can be optimised. The ``plat_get_my_entrypoint()`` platform porting interface 903 does not need to be implemented in this case. 904 905- ``PSCI_EXTENDED_STATE_ID``: As per PSCI1.0 Specification, there are 2 formats 906 possible for the PSCI power-state parameter: original and extended State-ID 907 formats. This flag if set to 1, configures the generic PSCI layer to use the 908 extended format. The default value of this flag is 0, which means by default 909 the original power-state format is used by the PSCI implementation. This flag 910 should be specified by the platform makefile and it governs the return value 911 of PSCI_FEATURES API for CPU_SUSPEND smc function id. When this option is 912 enabled on Arm platforms, the option ``ARM_RECOM_STATE_ID_ENC`` needs to be 913 set to 1 as well. 914 915- ``PSCI_OS_INIT_MODE``: Boolean flag to enable support for optional PSCI 916 OS-initiated mode. This option defaults to 0. 917 918- ``ARCH_FEATURE_AVAILABILITY``: Boolean flag to enable support for the 919 optional SMCCC_ARCH_FEATURE_AVAILABILITY call. This option implicitly 920 interacts with IMPDEF_SYSREG_TRAP and software emulation. This option 921 defaults to 0. 922 923- ``ENABLE_FEAT_RAS``: Boolean flag to enable Armv8.2 RAS features. RAS features 924 are an optional extension for pre-Armv8.2 CPUs, but are mandatory for Armv8.2 925 or later CPUs. This flag can take the values 0 or 1. The default value is 0. 926 NOTE: This flag enables use of IESB capability to reduce entry latency into 927 EL3 even when RAS error handling is not performed on the platform. Hence this 928 flag is recommended to be turned on Armv8.2 and later CPUs. 929 930- ``RESET_TO_BL31``: Enable BL31 entrypoint as the CPU reset vector instead 931 of the BL1 entrypoint. It can take the value 0 (CPU reset to BL1 932 entrypoint) or 1 (CPU reset to BL31 entrypoint). 933 The default value is 0. 934 935- ``RESET_TO_SP_MIN``: SP_MIN is the minimal AArch32 Secure Payload provided 936 in TF-A. This flag configures SP_MIN entrypoint as the CPU reset vector 937 instead of the BL1 entrypoint. It can take the value 0 (CPU reset to BL1 938 entrypoint) or 1 (CPU reset to SP_MIN entrypoint). The default value is 0. 939 940- ``RME_GPT_BITLOCK_BLOCK``: This defines the block size (in number of 512MB 941- blocks) covered by a single bit of the bitlock structure during RME GPT 942- operations. The lower the block size, the better opportunity for 943- parallelising GPT operations but at the cost of more bits being needed 944- for the bitlock structure. This numeric parameter can take the values 945- from 0 to 512 and must be a power of 2. The value of 0 is special and 946- and it chooses a single spinlock for all GPT L1 table entries. Default 947- value is 1 which corresponds to block size of 512MB per bit of bitlock 948- structure. 949 950- ``RME_GPT_MAX_BLOCK``: Numeric value in MB to define the maximum size of 951 supported contiguous blocks in GPT Library. This parameter can take the 952 values 0, 2, 32 and 512. Setting this value to 0 disables use of Contigious 953 descriptors. Default value is 512. 954 955- ``ROT_KEY``: This option is used when ``GENERATE_COT=1``. It specifies a 956 file that contains the ROT private key in PEM format or a PKCS11 URI and 957 enforces public key hash generation. If ``SAVE_KEYS=1``, only a file is 958 accepted and it will be used to save the key. 959 960- ``SAVE_KEYS``: This option is used when ``GENERATE_COT=1``. It tells the 961 certificate generation tool to save the keys used to establish the Chain of 962 Trust. Allowed options are '0' or '1'. Default is '0' (do not save). 963 964- ``SCP_BL2``: Path to SCP_BL2 image in the host file system. This image is optional. 965 If a SCP_BL2 image is present then this option must be passed for the ``fip`` 966 target. 967 968- ``SCP_BL2_KEY``: This option is used when ``GENERATE_COT=1``. It specifies a 969 file that contains the SCP_BL2 private key in PEM format or a PKCS11 URI. 970 If ``SAVE_KEYS=1``, only a file is accepted and it will be used to save the key. 971 972- ``SCP_BL2U``: Path to SCP_BL2U image in the host file system. This image is 973 optional. It is only needed if the platform makefile specifies that it 974 is required in order to build the ``fwu_fip`` target. 975 976- ``SDEI_SUPPORT``: Setting this to ``1`` enables support for Software 977 Delegated Exception Interface to BL31 image. This defaults to ``0``. 978 979 When set to ``1``, the build option ``EL3_EXCEPTION_HANDLING`` must also be 980 set to ``1``. 981 982- ``SEPARATE_CODE_AND_RODATA``: Whether code and read-only data should be 983 isolated on separate memory pages. This is a trade-off between security and 984 memory usage. See "Isolating code and read-only data on separate memory 985 pages" section in :ref:`Firmware Design`. This flag is disabled by default 986 and affects all BL images. 987 988- ``SEPARATE_NOBITS_REGION``: Setting this option to ``1`` allows the NOBITS 989 sections of BL31 (.bss, stacks, page tables, and coherent memory) to be 990 allocated in RAM discontiguous from the loaded firmware image. When set, the 991 platform is expected to provide definitions for ``BL31_NOBITS_BASE`` and 992 ``BL31_NOBITS_LIMIT``. When the option is ``0`` (the default), NOBITS 993 sections are placed in RAM immediately following the loaded firmware image. 994 995- ``SEPARATE_BL2_NOLOAD_REGION``: Setting this option to ``1`` allows the 996 NOLOAD sections of BL2 (.bss, stacks, page tables) to be allocated in RAM 997 discontiguous from loaded firmware images. When set, the platform need to 998 provide definitions of ``BL2_NOLOAD_START`` and ``BL2_NOLOAD_LIMIT``. This 999 flag is disabled by default and NOLOAD sections are placed in RAM immediately 1000 following the loaded firmware image. 1001 1002- ``SEPARATE_SIMD_SECTION``: Setting this option to ``1`` allows the SIMD context 1003 data structures to be put in a dedicated memory region as decided by platform 1004 integrator. Default value is ``0`` which means the SIMD context is put in BSS 1005 section of EL3 firmware. 1006 1007- ``SMC_PCI_SUPPORT``: This option allows platforms to handle PCI configuration 1008 access requests via a standard SMCCC defined in `DEN0115`_. When combined with 1009 UEFI+ACPI this can provide a certain amount of OS forward compatibility 1010 with newer platforms that aren't ECAM compliant. 1011 1012- ``SPD``: Choose a Secure Payload Dispatcher component to be built into TF-A. 1013 This build option is only valid if ``ARCH=aarch64``. The value should be 1014 the path to the directory containing the SPD source, relative to 1015 ``services/spd/``; the directory is expected to contain a makefile called 1016 ``<spd-value>.mk``. The SPM Dispatcher standard service is located in 1017 services/std_svc/spmd and enabled by ``SPD=spmd``. The SPM Dispatcher 1018 cannot be enabled when the ``SPM_MM`` option is enabled. 1019 1020- ``SPIN_ON_BL1_EXIT``: This option introduces an infinite loop in BL1. It can 1021 take either 0 (no loop) or 1 (add a loop). 0 is the default. This loop stops 1022 execution in BL1 just before handing over to BL31. At this point, all 1023 firmware images have been loaded in memory, and the MMU and caches are 1024 turned off. Refer to the "Debugging options" section for more details. 1025 1026- ``SPMC_AT_EL3`` : This boolean option is used jointly with the SPM 1027 Dispatcher option (``SPD=spmd``). When enabled (1) it indicates the SPMC 1028 component runs at the EL3 exception level. The default value is ``0`` ( 1029 disabled). This configuration supports pre-Armv8.4 platforms (aka not 1030 implementing the ``FEAT_SEL2`` extension). 1031 1032- ``SPMC_AT_EL3_SEL0_SP`` : Boolean option to enable SEL0 SP load support when 1033 ``SPMC_AT_EL3`` is enabled. The default value if ``0`` (disabled). This 1034 option cannot be enabled (``1``) when (``SPMC_AT_EL3``) is disabled. 1035 1036- ``SPMC_OPTEE`` : This boolean option is used jointly with the SPM 1037 Dispatcher option (``SPD=spmd``) and with ``SPMD_SPM_AT_SEL2=0`` to 1038 indicate that the SPMC at S-EL1 is OP-TEE and an OP-TEE specific loading 1039 mechanism should be used. 1040 1041- ``SPMD_SPM_AT_SEL2`` : This boolean option is used jointly with the SPM 1042 Dispatcher option (``SPD=spmd``). When enabled (1) it indicates the SPMC 1043 component runs at the S-EL2 exception level provided by the ``FEAT_SEL2`` 1044 extension. This is the default when enabling the SPM Dispatcher. When 1045 disabled (0) it indicates the SPMC component runs at the S-EL1 execution 1046 state or at EL3 if ``SPMC_AT_EL3`` is enabled. The latter configurations 1047 support pre-Armv8.4 platforms (aka not implementing the ``FEAT_SEL2`` 1048 extension). 1049 1050- ``SPM_MM`` : Boolean option to enable the Management Mode (MM)-based Secure 1051 Partition Manager (SPM) implementation. The default value is ``0`` 1052 (disabled). This option cannot be enabled (``1``) when SPM Dispatcher is 1053 enabled (``SPD=spmd``). 1054 1055- ``SP_LAYOUT_FILE``: Platform provided path to JSON file containing the 1056 description of secure partitions. The build system will parse this file and 1057 package all secure partition blobs into the FIP. This file is not 1058 necessarily part of TF-A tree. Only available when ``SPD=spmd``. 1059 1060- ``SP_MIN_WITH_SECURE_FIQ``: Boolean flag to indicate the SP_MIN handles 1061 secure interrupts (caught through the FIQ line). Platforms can enable 1062 this directive if they need to handle such interruption. When enabled, 1063 the FIQ are handled in monitor mode and non secure world is not allowed 1064 to mask these events. Platforms that enable FIQ handling in SP_MIN shall 1065 implement the api ``sp_min_plat_fiq_handler()``. The default value is 0. 1066 1067- ``SVE_VECTOR_LEN``: SVE vector length to configure in ZCR_EL3. 1068 Platforms can configure this if they need to lower the hardware 1069 limit, for example due to asymmetric configuration or limitations of 1070 software run at lower ELs. The default is the architectural maximum 1071 of 2048 which should be suitable for most configurations, the 1072 hardware will limit the effective VL to the maximum physically supported 1073 VL. 1074 1075- ``TRNG_SUPPORT``: Setting this to ``1`` enables support for True 1076 Random Number Generator Interface to BL31 image. This defaults to ``0``. 1077 1078- ``TRUSTED_BOARD_BOOT``: Boolean flag to include support for the Trusted Board 1079 Boot feature. When set to '1', BL1 and BL2 images include support to load 1080 and verify the certificates and images in a FIP, and BL1 includes support 1081 for the Firmware Update. The default value is '0'. Generation and inclusion 1082 of certificates in the FIP and FWU_FIP depends upon the value of the 1083 ``GENERATE_COT`` option. 1084 1085 .. warning:: 1086 This option depends on ``CREATE_KEYS`` to be enabled. If the keys 1087 already exist in disk, they will be overwritten without further notice. 1088 1089- ``TRUSTED_WORLD_KEY``: This option is used when ``GENERATE_COT=1``. It 1090 specifies a file that contains the Trusted World private key in PEM 1091 format or a PKCS11 URI. If ``SAVE_KEYS=1``, only a file is accepted and 1092 it will be used to save the key. 1093 1094- ``TSP_INIT_ASYNC``: Choose BL32 initialization method as asynchronous or 1095 synchronous, (see "Initializing a BL32 Image" section in 1096 :ref:`Firmware Design`). It can take the value 0 (BL32 is initialized using 1097 synchronous method) or 1 (BL32 is initialized using asynchronous method). 1098 Default is 0. 1099 1100- ``TSP_NS_INTR_ASYNC_PREEMPT``: A non zero value enables the interrupt 1101 routing model which routes non-secure interrupts asynchronously from TSP 1102 to EL3 causing immediate preemption of TSP. The EL3 is responsible 1103 for saving and restoring the TSP context in this routing model. The 1104 default routing model (when the value is 0) is to route non-secure 1105 interrupts to TSP allowing it to save its context and hand over 1106 synchronously to EL3 via an SMC. 1107 1108 .. note:: 1109 When ``EL3_EXCEPTION_HANDLING`` is ``1``, ``TSP_NS_INTR_ASYNC_PREEMPT`` 1110 must also be set to ``1``. 1111 1112- ``TS_SP_FW_CONFIG``: DTC build flag to include Trusted Services (Crypto and 1113 internal-trusted-storage) as SP in tb_fw_config device tree. 1114 1115- ``TWED_DELAY``: Numeric value to be set in order to delay the trapping of 1116 WFE instruction. ``ENABLE_FEAT_TWED`` build option must be enabled to set 1117 this delay. It can take values in the range (0-15). Default value is ``0`` 1118 and based on this value, 2^(TWED_DELAY + 8) cycles will be delayed. 1119 Platforms need to explicitly update this value based on their requirements. 1120 1121- ``USE_ARM_LINK``: This flag determines whether to enable support for ARM 1122 linker. When the ``LINKER`` build variable points to the armlink linker, 1123 this flag is enabled automatically. To enable support for armlink, platforms 1124 will have to provide a scatter file for the BL image. Currently, Tegra 1125 platforms use the armlink support to compile BL3-1 images. 1126 1127- ``USE_COHERENT_MEM``: This flag determines whether to include the coherent 1128 memory region in the BL memory map or not (see "Use of Coherent memory in 1129 TF-A" section in :ref:`Firmware Design`). It can take the value 1 1130 (Coherent memory region is included) or 0 (Coherent memory region is 1131 excluded). Default is 1. 1132 1133- ``USE_DSU_DRIVER``: This flag enables DSU (DynamIQ Shared Unit) driver. 1134 The DSU driver allows save/restore of DSU PMU registers through 1135 ``PRESERVE_DSU_PMU_REGS`` build option and allows platforms to 1136 configure powerdown and power settings of DSU. 1137 1138- ``ARM_IO_IN_DTB``: This flag determines whether to use IO based on the 1139 firmware configuration framework. This will move the io_policies into a 1140 configuration device tree, instead of static structure in the code base. 1141 1142- ``COT_DESC_IN_DTB``: This flag determines whether to create COT descriptors 1143 at runtime using fconf. If this flag is enabled, COT descriptors are 1144 statically captured in tb_fw_config file in the form of device tree nodes 1145 and properties. Currently, COT descriptors used by BL2 are moved to the 1146 device tree and COT descriptors used by BL1 are retained in the code 1147 base statically. 1148 1149- ``SDEI_IN_FCONF``: This flag determines whether to configure SDEI setup in 1150 runtime using firmware configuration framework. The platform specific SDEI 1151 shared and private events configuration is retrieved from device tree rather 1152 than static C structures at compile time. This is only supported if 1153 SDEI_SUPPORT build flag is enabled. 1154 1155- ``SEC_INT_DESC_IN_FCONF``: This flag determines whether to configure Group 0 1156 and Group1 secure interrupts using the firmware configuration framework. The 1157 platform specific secure interrupt property descriptor is retrieved from 1158 device tree in runtime rather than depending on static C structure at compile 1159 time. 1160 1161- ``USE_ROMLIB``: This flag determines whether library at ROM will be used. 1162 This feature creates a library of functions to be placed in ROM and thus 1163 reduces SRAM usage. Refer to :ref:`Library at ROM` for further details. Default 1164 is 0. 1165 1166- ``V``: Verbose build. If assigned anything other than 0, the build commands 1167 are printed. Default is 0. 1168 1169- ``VERSION_STRING``: String used in the log output for each TF-A image. 1170 Defaults to a string formed by concatenating the version number, build type 1171 and build string. 1172 1173- ``W``: Warning level. Some compiler warning options of interest have been 1174 regrouped and put in the root Makefile. This flag can take the values 0 to 3, 1175 each level enabling more warning options. Default is 0. 1176 1177 This option is closely related to the ``E`` option, which enables 1178 ``-Werror``. 1179 1180 - ``W=0`` (default) 1181 1182 Enables a wide assortment of warnings, most notably ``-Wall`` and 1183 ``-Wextra``, as well as various bad practices and things that are likely to 1184 result in errors. Includes some compiler specific flags. No warnings are 1185 expected at this level for any build. 1186 1187 - ``W=1`` 1188 1189 Enables warnings we want the generic build to include but are too time 1190 consuming to fix at the moment. It re-enables warnings taken out for 1191 ``W=0`` builds (a few of the ``-Wextra`` additions). This level is expected 1192 to eventually be merged into ``W=0``. Some warnings are expected on some 1193 builds, but new contributions should not introduce new ones. 1194 1195 - ``W=2`` (recommended) 1196 1197 Enables warnings we want the generic build to include but cannot be enabled 1198 due to external libraries. This level is expected to eventually be merged 1199 into ``W=0``. Lots of warnings are expected, primarily from external 1200 libraries like zlib and compiler-rt, but new controbutions should not 1201 introduce new ones. 1202 1203 - ``W=3`` 1204 1205 Enables warnings that are informative but not necessary and generally too 1206 verbose and frequently ignored. A very large number of warnings are 1207 expected. 1208 1209 The exact set of warning flags depends on the compiler and TF-A warning 1210 level, however they are all succinctly set in the top-level Makefile. Please 1211 refer to the `GCC`_ or `Clang`_ documentation for more information on the 1212 individual flags. 1213 1214- ``WARMBOOT_ENABLE_DCACHE_EARLY`` : Boolean option to enable D-cache early on 1215 the CPU after warm boot. This is applicable for platforms which do not 1216 require interconnect programming to enable cache coherency (eg: single 1217 cluster platforms). If this option is enabled, then warm boot path 1218 enables D-caches immediately after enabling MMU. This option defaults to 0. 1219 1220- ``ERRATA_SPECULATIVE_AT``: This flag determines whether to enable ``AT`` 1221 speculative errata workaround or not. It accepts 2 values: ``1`` and ``0``. 1222 The default value of this flag is ``0``. 1223 1224 ``AT`` speculative errata workaround disables stage1 page table walk for 1225 lower ELs (EL1 and EL0) in EL3 so that ``AT`` speculative fetch at any point 1226 produces either the correct result or failure without TLB allocation. 1227 1228 This boolean option enables errata for all below CPUs. 1229 1230 +---------+--------------+-------------------------+ 1231 | Errata | CPU | Workaround Define | 1232 +=========+==============+=========================+ 1233 | 1165522 | Cortex-A76 | ``ERRATA_A76_1165522`` | 1234 +---------+--------------+-------------------------+ 1235 | 1319367 | Cortex-A72 | ``ERRATA_A72_1319367`` | 1236 +---------+--------------+-------------------------+ 1237 | 1319537 | Cortex-A57 | ``ERRATA_A57_1319537`` | 1238 +---------+--------------+-------------------------+ 1239 | 1530923 | Cortex-A55 | ``ERRATA_A55_1530923`` | 1240 +---------+--------------+-------------------------+ 1241 | 1530924 | Cortex-A53 | ``ERRATA_A53_1530924`` | 1242 +---------+--------------+-------------------------+ 1243 1244 .. note:: 1245 This option is enabled by build only if platform sets any of above defines 1246 mentioned in ’Workaround Define' column in the table. 1247 If this option is enabled for the EL3 software then EL2 software also must 1248 implement this workaround due to the behaviour of the errata mentioned 1249 in new SDEN document which will get published soon. 1250 1251- ``ERRATA_SME_POWER_DOWN``: Boolean option to disable SME (PSTATE.{ZA,SM}=0) 1252 before power down and downgrade a suspend to power down request to a normal 1253 suspend request. This is necessary when software running at lower ELs requests 1254 power down without first clearing these bits. On affected cores, the CME 1255 connected to it will reject its power down request. The default value is 0. 1256 1257- ``RAS_TRAP_NS_ERR_REC_ACCESS``: This flag enables/disables the SCR_EL3.TERR 1258 bit, to trap access to the RAS ERR and RAS ERX registers from lower ELs. 1259 This flag is disabled by default. 1260 1261- ``OPENSSL_DIR``: This option is used to provide the path to a directory on the 1262 host machine where a custom installation of OpenSSL is located, which is used 1263 to build the certificate generation, firmware encryption and FIP tools. If 1264 this option is not set, the default OS installation will be used. 1265 1266- ``USE_SP804_TIMER``: Use the SP804 timer instead of the Generic Timer for 1267 functions that wait for an arbitrary time length (udelay and mdelay). The 1268 default value is 0. 1269 1270- ``ENABLE_BRBE_FOR_NS``: Numeric value to enable access to the branch record 1271 buffer registers from NS ELs when FEAT_BRBE is implemented. BRBE is an 1272 optional architectural feature for AArch64. This flag can take the values 1273 0 to 2, to align with the ``ENABLE_FEAT`` mechanism. The default is 0 1274 and it is automatically disabled when the target architecture is AArch32. 1275 1276- ``ENABLE_TRBE_FOR_NS``: Numeric value to enable access of trace buffer 1277 control registers from NS ELs, NS-EL2 or NS-EL1(when NS-EL2 is implemented 1278 but unused) when FEAT_TRBE is implemented. TRBE is an optional architectural 1279 feature for AArch64. This flag can take the values 0 to 2, to align with the 1280 ``ENABLE_FEAT`` mechanism. The default is 0 and it is automatically 1281 disabled when the target architecture is AArch32. 1282 1283- ``ENABLE_SYS_REG_TRACE_FOR_NS``: Numeric value to enable trace system 1284 registers access from NS ELs, NS-EL2 or NS-EL1 (when NS-EL2 is implemented 1285 but unused). This feature is available if trace unit such as ETMv4.x, and 1286 ETE(extending ETM feature) is implemented. This flag can take the values 1287 0 to 2, to align with the ``ENABLE_FEAT`` mechanism. The default is 0. 1288 1289- ``ENABLE_TRF_FOR_NS``: Numeric value to enable trace filter control registers 1290 access from NS ELs, NS-EL2 or NS-EL1 (when NS-EL2 is implemented but unused), 1291 if FEAT_TRF is implemented. This flag can take the values 0 to 2, to align 1292 with the ``ENABLE_FEAT`` mechanism. This flag is disabled by default. 1293 1294- ``CONDITIONAL_CMO``: Boolean option to enable call to platform-defined routine 1295 ``plat_can_cmo`` which will return zero if cache management operations should 1296 be skipped and non-zero otherwise. By default, this option is disabled which 1297 means platform hook won't be checked and CMOs will always be performed when 1298 related functions are called. 1299 1300- ``ERRATA_ABI_SUPPORT``: Boolean option to enable support for Errata management 1301 firmware interface for the BL31 image. By default its disabled (``0``). 1302 1303- ``ERRATA_NON_ARM_INTERCONNECT``: Boolean option to enable support for the 1304 errata mitigation for platforms with a non-arm interconnect using the errata 1305 ABI. By default its disabled (``0``). 1306 1307- ``ENABLE_CONSOLE_GETC``: Boolean option to enable `getc()` feature in console 1308 driver(s). By default it is disabled (``0``) because it constitutes an attack 1309 vector into TF-A by potentially allowing an attacker to inject arbitrary data. 1310 This option should only be enabled on a need basis if there is a use case for 1311 reading characters from the console. 1312 1313GIC driver options 1314-------------------- 1315 1316The generic GIC driver can be included with the ``USE_GIC_DRIVER`` option. It is 1317a numeric option that can take the following values: 1318 1319 - ``0``: generic GIC driver not enabled. Any support is entirely in platform 1320 code. Strongly discouraged for GIC based interrupt controllers. 1321 1322 - ``1``: enable the use of the generic GIC driver but do not include any files 1323 or function definitions. It is then the platform's responsibility to provide 1324 these. This is useful if the platform either has a custom GIC implementation 1325 or an alternative interrupt controller design. Use of this option is strongly 1326 discouraged for standard GIC implementations. 1327 1328 - ``2``: use the GICv2 driver 1329 1330 - ``3``: use the GICv3 driver. See the next section on how to further configure 1331 it. Use this option for GICv4 implementations. 1332 - ``5``: use the EXPERIMENTAL GICv5 driver. Requires ``ENABLE_FEAT_GCIE=1``. 1333 1334 For GIC driver versions other than ``1``, deciding when to save and restore GIC 1335 context on a power domain state transition, as well as any GIC actions outside 1336 of the PSCI library's visibility are the platform's responsibility. The driver 1337 provides implementations of all necessary subroutines, they only need to be 1338 called as appropriate. 1339 1340GICv3 driver options 1341~~~~~~~~~~~~~~~~~~~~ 1342 1343``USE_GIC_DRIVER=3`` is the preferred way of including GICv3 driver files. The 1344old (deprecated) way of included them is using the directive: 1345``include drivers/arm/gic/v3/gicv3.mk`` 1346 1347The driver can be configured with the following options set in the platform 1348makefile: 1349 1350- ``GICV3_SUPPORT_GIC600``: Add support for the GIC-600 variants of GICv3. 1351 Enabling this option will add runtime detection support for the 1352 GIC-600, so is safe to select even for a GIC500 implementation. 1353 This option defaults to 0. 1354 1355- ``GICV3_SUPPORT_GIC600AE_FMU``: Add support for the Fault Management Unit 1356 for GIC-600 AE. Enabling this option will introduce support to initialize 1357 the FMU. Platforms should call the init function during boot to enable the 1358 FMU and its safety mechanisms. This option defaults to 0. 1359 1360- ``GICV3_IMPL_GIC600_MULTICHIP``: Selects GIC-600 variant with multichip 1361 functionality. This option defaults to 0 1362 1363- ``GICV3_OVERRIDE_DISTIF_PWR_OPS``: Allows override of default implementation 1364 of ``arm_gicv3_distif_pre_save`` and ``arm_gicv3_distif_post_restore`` 1365 functions. This is required for FVP platform which need to simulate GIC save 1366 and restore during SYSTEM_SUSPEND without powering down GIC. Default is 0. 1367 1368- ``GIC_ENABLE_V4_EXTN`` : Enables GICv4 related changes in GICv3 driver. 1369 This option defaults to 0. 1370 1371- ``GIC_EXT_INTID``: When set to ``1``, GICv3 driver will support extended 1372 PPI (1056-1119) and SPI (4096-5119) range. This option defaults to 0. 1373 1374Debugging options 1375----------------- 1376 1377To compile a debug version and make the build more verbose use 1378 1379.. code:: shell 1380 1381 make PLAT=<platform> DEBUG=1 V=1 all 1382 1383AArch64 GCC 11 uses DWARF version 5 debugging symbols by default. Some tools 1384(for example Arm-DS) might not support this and may need an older version of 1385DWARF symbols to be emitted by GCC. This can be achieved by using the 1386``-gdwarf-<version>`` flag, with the version being set to 2, 3, 4 or 5. Setting 1387the version to 4 is recommended for Arm-DS. 1388 1389When debugging logic problems it might also be useful to disable all compiler 1390optimizations by using ``-O0``. 1391 1392.. warning:: 1393 Using ``-O0`` could cause output images to be larger and base addresses 1394 might need to be recalculated (see the **Memory layout on Arm development 1395 platforms** section in the :ref:`Firmware Design`). 1396 1397Extra debug options can be passed to the build system by setting ``CFLAGS`` or 1398``LDFLAGS``: 1399 1400.. code:: shell 1401 1402 CFLAGS='-O0 -gdwarf-2' \ 1403 make PLAT=<platform> DEBUG=1 V=1 all 1404 1405Note that using ``-Wl,`` style compilation driver options in ``CFLAGS`` will be 1406ignored as the linker is called directly. 1407 1408It is also possible to introduce an infinite loop to help in debugging the 1409post-BL2 phase of TF-A. This can be done by rebuilding BL1 with the 1410``SPIN_ON_BL1_EXIT=1`` build flag. Refer to the :ref:`build_options_common` 1411section. In this case, the developer may take control of the target using a 1412debugger when indicated by the console output. When using Arm-DS, the following 1413commands can be used: 1414 1415:: 1416 1417 # Stop target execution 1418 interrupt 1419 1420 # 1421 # Prepare your debugging environment, e.g. set breakpoints 1422 # 1423 1424 # Jump over the debug loop 1425 set var $AARCH64::$Core::$PC = $AARCH64::$Core::$PC + 4 1426 1427 # Resume execution 1428 continue 1429 1430.. _build_options_experimental: 1431 1432Experimental build options 1433--------------------------- 1434 1435Common build options 1436~~~~~~~~~~~~~~~~~~~~ 1437 1438- ``DICE_PROTECTION_ENVIRONMENT``: Boolean flag to specify the measured boot 1439 backend when ``MEASURED_BOOT`` is enabled. The default value is ``0``. When 1440 set to ``1`` then measurements and additional metadata collected during the 1441 measured boot process are sent to the DICE Protection Environment for storage 1442 and processing. A certificate chain, which represents the boot state of the 1443 device, can be queried from the DPE. 1444 1445- ``DRTM_SUPPORT``: Boolean flag to enable support for Dynamic Root of Trust 1446 for Measurement (DRTM). This feature has trust dependency on BL31 for taking 1447 the measurements and recording them as per `PSA DRTM specification`_. For 1448 platforms which use BL2 to load/authenticate BL31 ``TRUSTED_BOARD_BOOT`` can 1449 be used and for the platforms which use ``RESET_TO_BL31`` platform owners 1450 should have mechanism to authenticate BL31. This option defaults to 0. 1451 1452- ``ENABLE_RME``: Numeric value to enable support for the ARMv9 Realm 1453 Management Extension. This flag can take the values 0 to 2, to align with 1454 the ``ENABLE_FEAT`` mechanism. Default value is 0. 1455 1456- ``ENABLE_FEAT_MEC``: Numeric value to enable support for the ARMv9.2 Memory 1457 Encryption Contexts (MEC). This flag can take the values 0 to 2, to align 1458 with the ``ENABLE_FEAT`` mechanism. MEC supports multiple encryption 1459 contexts for Realm security state and only one encryption context for the 1460 rest of the security states. Default value is 0. 1461 1462- ``RMMD_ENABLE_EL3_TOKEN_SIGN``: Numeric value to enable support for singing 1463 realm attestation token signing requests in EL3. This flag can take the 1464 values 0 and 1. The default value is ``0``. When set to ``1``, this option 1465 enables additional RMMD SMCs to push and pop requests for signing to 1466 EL3 along with platform hooks that must be implemented to service those 1467 requests and responses. 1468 1469- ``ENABLE_SME_FOR_NS``: Numeric value to enable Scalable Matrix Extension 1470 (SME), SVE, and FPU/SIMD for the non-secure world only. These features share 1471 registers so are enabled together. Using this option without 1472 ENABLE_SME_FOR_SWD=1 will cause SME, SVE, and FPU/SIMD instructions in secure 1473 world to trap to EL3. Requires ``ENABLE_SVE_FOR_NS`` to be set as SME is a 1474 superset of SVE. SME is an optional architectural feature for AArch64. 1475 At this time, this build option cannot be used on systems that have 1476 SPD=spmd/SPM_MM and atempting to build with this option will fail. 1477 This flag can take the values 0 to 2, to align with the ``ENABLE_FEAT`` 1478 mechanism. Default is 0. 1479 1480- ``ENABLE_SME2_FOR_NS``: Numeric value to enable Scalable Matrix Extension 1481 version 2 (SME2) for the non-secure world only. SME2 is an optional 1482 architectural feature for AArch64. 1483 This should be set along with ENABLE_SME_FOR_NS=1, if not, the default SME 1484 accesses will still be trapped. This flag can take the values 0 to 2, to 1485 align with the ``ENABLE_FEAT`` mechanism. Default is 0. 1486 1487- ``ENABLE_SME_FOR_SWD``: Boolean option to enable the Scalable Matrix 1488 Extension for secure world. Used along with SVE and FPU/SIMD. 1489 ENABLE_SME_FOR_NS and ENABLE_SVE_FOR_SWD must also be set to use this. 1490 Default is 0. 1491 1492- ``ENABLE_SPMD_LP`` : This boolean option is used jointly with the SPM 1493 Dispatcher option (``SPD=spmd``). When enabled (1) it indicates support 1494 for logical partitions in EL3, managed by the SPMD as defined in the 1495 FF-A v1.2 specification. This flag is disabled by default. This flag 1496 must not be used if ``SPMC_AT_EL3`` is enabled. 1497 1498- ``FEATURE_DETECTION``: Boolean option to enable the architectural features 1499 verification mechanism. This is a debug feature that compares the 1500 architectural features enabled through the feature specific build flags 1501 (ENABLE_FEAT_xxx) with the features actually available on the CPU running, 1502 and reports any discrepancies. 1503 This flag will also enable errata ordering checking for ``DEBUG`` builds. 1504 1505 It is expected that this feature is only used for flexible platforms like 1506 software emulators, or for hardware platforms at bringup time, to verify 1507 that the configured feature set matches the CPU. 1508 The ``FEATURE_DETECTION`` macro is disabled by default. 1509 1510- ``PSA_CRYPTO``: Boolean option for enabling MbedTLS PSA crypto APIs support. 1511 The platform will use PSA compliant Crypto APIs during authentication and 1512 image measurement process by enabling this option. It uses APIs defined as 1513 per the `PSA Crypto API specification`_. This feature is only supported if 1514 using MbedTLS 3.x version. It is disabled (``0``) by default. 1515 1516- ``LFA_SUPPORT``: Boolean flag to enable support for Live Firmware 1517 activation as per the specification. This option defaults to 0. 1518 1519- ``TRANSFER_LIST``: Setting this to ``1`` enables support for Firmware 1520 Handoff using Transfer List defined in `Firmware Handoff specification`_. 1521 This defaults to ``0``. Current implementation follows the Firmware Handoff 1522 specification v0.9. 1523 1524- ``USE_DEBUGFS``: When set to 1 this option exposes a virtual filesystem 1525 interface through BL31 as a SiP SMC function. 1526 Default is disabled (0). 1527 1528- ``HOB_LIST``: Setting this to ``1`` enables support for passing boot 1529 information using HOB defined in `Platform Initialization specification`_. 1530 This defaults to ``0``. 1531 1532- ``ENABLE_ACS_SMC``: When set to ``1``, this enables support for ACS SMC 1533 handler code to handle SMC calls from the Architecture Compliance Suite. The 1534 handler is intentionally empty to reserve the SMC section and allow 1535 project-specific implementations in future ACS use cases. 1536 1537Firmware update options 1538~~~~~~~~~~~~~~~~~~~~~~~ 1539 1540- ``PSA_FWU_SUPPORT``: Enable the firmware update mechanism as per the 1541 `PSA FW update specification`_. The default value is 0. 1542 PSA firmware update implementation has few limitations, such as: 1543 1544 - BL2 is not part of the protocol-updatable images. If BL2 needs to 1545 be updated, then it should be done through another platform-defined 1546 mechanism. 1547 1548 - It assumes the platform's hardware supports CRC32 instructions. 1549 1550- ``NR_OF_FW_BANKS``: Define the number of firmware banks. This flag is used 1551 in defining the firmware update metadata structure. This flag is by default 1552 set to '2'. 1553 1554- ``NR_OF_IMAGES_IN_FW_BANK``: Define the number of firmware images in each 1555 firmware bank. Each firmware bank must have the same number of images as per 1556 the `PSA FW update specification`_. 1557 This flag is used in defining the firmware update metadata structure. This 1558 flag is by default set to '1'. 1559 1560- ``PSA_FWU_METADATA_FW_STORE_DESC``: To be enabled when the FWU 1561 metadata contains image description. The default value is 1. 1562 1563 The version 2 of the FWU metadata allows for an opaque metadata 1564 structure where a platform can choose to not include the firmware 1565 store description in the metadata structure. This option indicates 1566 if the firmware store description, which provides information on 1567 the updatable images is part of the structure. 1568 1569-------------- 1570 1571*Copyright (c) 2019-2025, Arm Limited. All rights reserved.* 1572 1573.. _DEN0115: https://developer.arm.com/docs/den0115/latest 1574.. _PSA FW update specification: https://developer.arm.com/documentation/den0118/latest/ 1575.. _PSA DRTM specification: https://developer.arm.com/documentation/den0113/a 1576.. _GCC: https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html 1577.. _Clang: https://clang.llvm.org/docs/DiagnosticsReference.html 1578.. _Firmware Handoff specification: https://github.com/FirmwareHandoff/firmware_handoff/releases/tag/v0.9 1579.. _PSA Crypto API specification: https://armmbed.github.io/mbed-crypto/html/ 1580.. _Platform Initialization specification: https://uefi.org/specs/PI/1.8/index.html 1581.. _TF-A public mailing list: https://lists.trustedfirmware.org/mailman3/lists/tf-a.lists.trustedfirmware.org/ 1582