1Running on the Foundation FVP
2^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3
4The following ``Foundation_Platform`` parameters should be used to boot Linux with
54 CPUs using the AArch64 build of TF-A.
6
7.. code:: shell
8
9    <path-to>/Foundation_Platform                   \
10    --cores=4                                       \
11    --arm-v8.0                                      \
12    --secure-memory                                 \
13    --visualization                                 \
14    --gicv3                                         \
15    --data="<path-to>/<bl1-binary>"@0x0             \
16    --data="<path-to>/<FIP-binary>"@0x08000000      \
17    --data="<path-to>/<kernel-binary>"@0x80080000   \
18    --data="<path-to>/<ramdisk-binary>"@0x84000000
19
20Notes:
21
22-  BL1 is loaded at the start of the Trusted ROM.
23-  The Firmware Image Package is loaded at the start of NOR FLASH0.
24-  The firmware loads the FDT packaged in FIP to the DRAM. The FDT load address
25   is specified via the ``load-address`` property in the ``hw-config`` node of
26   `FW_CONFIG for FVP`_.
27-  The default use-case for the Foundation FVP is to use the ``--gicv3`` option
28   and enable the GICv3 device in the model. Note that without this option,
29   the Foundation FVP defaults to legacy (Versatile Express) memory map which
30   is not supported by TF-A.
31-  In order for TF-A to run correctly on the Foundation FVP, the architecture
32   versions must match. The Foundation FVP defaults to the highest v8.x
33   version it supports but the default build for TF-A is for v8.0. To avoid
34   issues either start the Foundation FVP to use v8.0 architecture using the
35   ``--arm-v8.0`` option, or build TF-A with an appropriate value for
36   ``ARM_ARCH_MINOR``.
37
38--------------
39
40*Copyright (c) 2019-2024, Arm Limited. All rights reserved.*
41
42.. _FW_CONFIG for FVP: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/tree/plat/arm/board/fvp/fdts/fvp_fw_config.dts
43