Djam/arm-trusted-firmware
1
0
Fork 0
mirror of https://github.com/ARM-software/arm-trusted-firmware.git synced 2025-04-17 10:04:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: GCC toolchain upgrade to version 9.2-2019.12

Browse source 
This toolchain provides multiple cross compilers and are publicly
available on developer.arm.com

We build TF-A in CI using:
AArch32 bare-metal target (arm-none-eabi)
AArch64 ELF bare-metal target (aarch64-none-elf)

Change-Id: I910200174d5bad985504d1af4a1ae5819b524003
Signed-off-by: Madhukar Pappireddy <madhukar.pappireddy@arm.com>
This commit is contained in:
Madhukar Pappireddy 2020-01-10 16:11:18 -06:00
parent 22d12c4148
commit f35e5ab39c
4 changed files with 7 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/getting_started/initial-build.rst
View file

@ -8,13 +8,13 @@ Performing an Initial Build
.. code:: shell .. code:: shell
export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-linux-gnu- export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf-
For AArch32: For AArch32:
.. code:: shell .. code:: shell
export CROSS_COMPILE=<path-to-aarch32-gcc>/bin/arm-eabi- export CROSS_COMPILE=<path-to-aarch32-gcc>/bin/arm-none-eabi-
It is possible to build TF-A using Clang or Arm Compiler 6. To do so It is possible to build TF-A using Clang or Arm Compiler 6. To do so
``CC`` needs to point to the clang or armclang binary, which will ``CC`` needs to point to the clang or armclang binary, which will
@ -32,7 +32,7 @@ Performing an Initial Build
.. code:: shell .. code:: shell
export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-linux-gnu- export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf-
make CC=<path-to-armclang>/bin/armclang PLAT=<platform> all make CC=<path-to-armclang>/bin/armclang PLAT=<platform> all
Clang will be selected when the base name of the path assigned to ``CC`` Clang will be selected when the base name of the path assigned to ``CC``
@ -43,7 +43,7 @@ Performing an Initial Build
.. code:: shell .. code:: shell
export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-linux-gnu- export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf-
make CC=<path-to-clang>/bin/clang PLAT=<platform> all make CC=<path-to-clang>/bin/clang PLAT=<platform> all
- Change to the root directory of the TF-A source tree and build. - Change to the root directory of the TF-A source tree and build.

2
docs/getting_started/prerequisites.rst
View file

@ -26,7 +26,7 @@ Toolchain
|TF-A| can be built with any of the following *cross-compiler* toolchains that |TF-A| can be built with any of the following *cross-compiler* toolchains that
target the Armv7-A or Armv8-A architectures: target the Armv7-A or Armv8-A architectures:
- GCC >= 8.3-2019.03 (from the `Arm Developer website`_) - GCC >= 9.2-2019.12 (from the `Arm Developer website`_)
- Clang >= 4.0 - Clang >= 4.0
- Arm Compiler >= 6.0 - Arm Compiler >= 6.0

2
docs/plat/arm/fvp/index.rst
View file

@ -223,7 +223,7 @@ address ``0x82000000``, the firmware can be built like this:
.. code:: shell .. code:: shell
CROSS_COMPILE=aarch64-linux-gnu- \ CROSS_COMPILE=aarch64-none-elf- \
make PLAT=fvp DEBUG=1 \ make PLAT=fvp DEBUG=1 \
RESET_TO_BL31=1 \ RESET_TO_BL31=1 \
ARM_LINUX_KERNEL_AS_BL33=1 \ ARM_LINUX_KERNEL_AS_BL33=1 \

2
docs/plat/arm/juno/index.rst
View file

@ -136,7 +136,7 @@ a single FIP binary. It assumes that a Linaro release has been installed.
.. code:: shell .. code:: shell
export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-linux-gnu- export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf-
- The following parameters should be used to build BL1 and BL2 in AArch64 - The following parameters should be used to build BL1 and BL2 in AArch64
and point to the BL32 file. and point to the BL32 file.