• Home
  • Raw
  • Download

Lines Matching +full:test +full:- +full:shell +full:- +full:loader

4 -  Before building TF-A, the environment variable ``CROSS_COMPILE`` must point
9 .. code:: shell
11 export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf-
15 .. code:: shell
17 export CROSS_COMPILE=<path-to-aarch32-gcc>/bin/arm-none-eabi-
19 It is possible to build TF-A using Clang or Arm Compiler 6. To do so
25 known to work with TF-A.
34 .. code:: shell
36 export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf-
37 make CC=<path-to-armclang>/bin/armclang PLAT=<platform> all
40 contains the string 'clang'. This is to allow both clang and clang-X.Y
45 .. code:: shell
47 export CROSS_COMPILE=<path-to-aarch64-gcc>/bin/aarch64-none-elf-
48 make CC=<path-to-clang>/bin/clang PLAT=<platform> all
50 - Change to the root directory of the TF-A source tree and build.
54 .. code:: shell
60 .. code:: shell
66 - If ``PLAT`` is not specified, ``fvp`` is assumed by default. See the
70 - (AArch32 only) Currently only ``PLAT=fvp`` is supported.
72 - (AArch32 only) ``AARCH32_SP`` is the AArch32 EL3 Runtime Software and it
74 provided by TF-A to demonstrate how PSCI Library can be integrated with
78 at :ref:`PSCI Library Integration guide for Armv8-A AArch32 systems`.
80 - (AArch64 only) The TSP (Test Secure Payload), corresponding to the BL32
82 :ref:`Test Secure Payload (TSP) and Dispatcher (TSPD)` document for
85 - By default this produces a release version of the build. To produce a
88 - The build process creates products in a ``build`` directory tree, building
89 the objects and binaries for each boot loader stage in separate
90 sub-directories. The following boot loader binary files are created
93 - ``build/<platform>/<build-type>/bl1.bin``
94 - ``build/<platform>/<build-type>/bl2.bin``
95 - ``build/<platform>/<build-type>/bl31.bin`` (AArch64 only)
96 - ``build/<platform>/<build-type>/bl32.bin`` (mandatory for AArch32)
98 where ``<platform>`` is the name of the chosen platform and ``<build-type>``
102 - Build products for a specific build variant can be removed using:
104 .. code:: shell
112 .. code:: shell
116 --------------