| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | index.rst | 9 docs-build
10 initial-build
11 tools-build
12 build-options
13 build-internals
|
| H A D | initial-build.rst | 19 It is possible to build TF-A using Clang or Arm Compiler 6. To do so
23 'armclang'. GNU binutils are required since the TF-A build system doesn't
50 - Change to the root directory of the TF-A source tree and build.
67 :ref:`Build Options` document for more information on available build
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
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)
[all …]
|
| H A D | tools-build.rst | 6 OpenSSL 3.0 is needed in order to build the tools. A custom installation
9 indicate the location of the custom OpenSSL build. Then, to run the tools,
17 The following snippets build a :ref:`FIP<Image Terminology>` for the FVP
23 The TF-A build system provides the make target ``fip`` to create a FIP file
25 project. Examples below show how to build a FIP file for FVP, packaging TF-A
44 build/fvp/<build-type>/fip.bin
46 For advanced operations on FIP files, it is also possible to independently build
76 --tb-fw build/<platform>/<build-type>/bl2.bin \
77 --soc-fw build/<platform>/<build-type>/bl31.bin \
92 --tb-fw build/<platform>/release/bl2.bin \
[all …]
|
| H A D | docs-build.rst | 5 `Sphinx`_ tool to build and package the plain-text documents into HTML-formatted
15 copy without doing a local build.
47 Output from the build process will be placed in: ``docs/build/html``.
60 To build the documentation in PDF format, additionally ensure that the following
77 docs latexpdf`` to build the documentation. Output from the build process
78 (``trustedfirmware-a.pdf``) can be found in ``docs/build/latex``.
83 If Poetry is installed, the ``doc`` target wraps its build steps with ``poetry
90 build the documentation directly with ``make``.
121 build process will be placed in: ``docs/build/html``.
|
| H A D | build-internals.rst | 5 :ref:`build-options <build options>` but enabled or disabled indirectly and
23 - ``OPTEE_SP_FW_CONFIG``: DTC build flag to include OP-TEE as SP in
27 - ``TRUSTY_SP_FW_CONFIG``: DTC build flag to include Trusty as SP in
|
| /rk3399_ARM-atf/make_helpers/ |
| H A D | build-rules.mk | 7 ifndef build-rules-mk
8 build-rules-mk := $(lastword $(MAKEFILE_LIST))
10 include $(dir $(build-rules-mk))common.mk
11 include $(dir $(build-rules-mk))utilities.mk
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | qemu-sbsa.rst | 7 is made by EDK2 build system by composing BL1 and FIP. Second parameter for Qemu
9 contains of UEFI and EFI variables (also made by EDK2 build system). Semihosting
23 To build TF-A:
32 To build TF-A with BL32 and SPM enabled(StandaloneMM as a Secure Payload):
41 Images will be placed at build/qemu_sbsa/release (bl1.bin and fip.bin).
46 cp build/qemu_sbsa/release/bl1.bin ../
47 cp build/qemu_sbsa/release/fip.bin ../
50 EDK2 build system, refer to edk2-platform repo for full build instructions.
|
| H A D | rockchip.rst | 32 How to build
37 these images need to get build from the TF-A repository.
39 For AARCH64 architectures the build command looks like
48 want to build for and the CROSS_COMPILE argument with you cross-
56 to put the built images during their respective build process.
57 So after successfully building TF-A just follow their build instructions
|
| H A D | synquacer.rst | 11 How to build
37 - Firstly, in addition to the “normal” build tools you will also need a
50 export WORKSPACE=$HOME/build/developerbox-firmware
70 --tb-fw ./build/synquacer/release/bl31.bin \
71 --soc-fw ./build/synquacer/release/bl31.bin \
72 --scp-fw ./build/synquacer/release/bl31.bin \
88 build -p $ACTIVE_PLATFORM -b RELEASE -a AARCH64 -t GCC5 -n `nproc` -D DO_X86EMU=TRUE
96 any version of gcc >= 5 will support this feature and may be used to build EDK2.
98 Note #2: Replace -b RELEASE with -b DEBUG to build a debug.
|
| H A D | amd-versal2.rst | 12 To build:
17 To build TF-A for JTAG DCC console:
22 To build TF-A with Errata management interface
27 To build TF-A with IPI CRC check:
32 AMD Versal Gen 2 platform specific build options
70 TF-A build, its definition of ``custom_smc_handler`` is enabled.
81 ``custom_pkg.mk`` so it can be included in the TF-A build.
85 required to be part of the TF-A build.
87 - When ``<CUSTOM_PKG_PATH>`` is specified in the TF-A build command,
90 - Example TF-A build command:
|
| H A D | xilinx-zynqmp.rst | 13 To build:
19 To build bl32 TSP you have to rebuild bl31 too:
25 To build TF-A for JTAG DCC console:
31 ZynqMP platform specific build options
55 must be provided during build as,
62 provide it through the build command as above.
65 the DDR address location using the build time parameters ZYNQMP_ATF_MEM_BASE and
73 to the build command as follows,
87 the build command example is;
145 included in TF-A build, their definition of custom_smc_handler is
[all …]
|
| H A D | xilinx-versal.rst | 12 To build:
17 To build bl32 TSP you have to rebuild bl31 too
22 To build TF-A for JTAG DCC console
27 To build TF-A with Errata management interface
32 To build TF-A with Straight-Line Speculation(SLS)
37 Xilinx Versal platform specific build options
87 TF-A build, its definition of ``custom_smc_handler`` is enabled.
98 ``custom_pkg.mk`` so it can be included in the TF-A build.
102 required to be part of the TF-A build.
104 - When ``<CUSTOM_PKG_PATH>`` is specified in the TF-A build command,
[all …]
|
| H A D | allwinner.rst | 11 There is one build target per supported SoC:
14 | SoC | TF-A build target |
31 To build with the default settings for a particular SoC:
35 make CROSS_COMPILE=aarch64-linux-gnu- PLAT=<build target> DEBUG=1
37 So for instance to build for a board with the Allwinner A64 SoC::
41 Platform-specific build options
44 The default build options should generate a working firmware image. There are
45 some build options that allow to fine-tune the firmware, or to disable support
72 can bet set to ``0`` on the build command line, to skip the PMIC setup
82 After building bl31.bin, the binary must be fed to the U-Boot build system
|
| H A D | xilinx-versal-net.rst | 12 To build:
17 To build bl32 TSP you have to rebuild bl31 too
22 To build TF-A for JTAG DCC console:
27 To build TF-A with SDEI_SUPPORT:
32 Xilinx Versal NET platform specific build options
|
| /rk3399_ARM-atf/docs/perf/ |
| H A D | tsp.rst | 12 First clean the TF-A build directory to get rid of any previous BL31 binary.
13 Then to build the TSP image use:
19 An additional boot loader binary file is created in the ``build`` directory:
23 build/<platform>/<build-type>/bl32.bin
|
| /rk3399_ARM-atf/docs/plat/st/ |
| H A D | stm32mp1.rst | 107 You need to build BL2, BL32 (SP_min or OP-TEE) and BL33 (U-Boot) before building FIP binary.
133 To build TF-A BL32, and its device tree file:
142 To build TF-A BL2 with its STM32 header for SD-card boot:
187 tools/cert_create/cert_create -n --rot-key build/stm32mp1/release/rot_key.pem \
191 --trusted-key-cert build/stm32mp1/release/trusted_key.crt \
195 --tos-fw-cert build/stm32mp1/release/tos_fw_content.crt \
196 --tos-fw-key-cert build/stm32mp1/release/tos_fw_key.crt \
198 --nt-fw-cert build/stm32mp1/release/nt_fw_content.crt \
199 --nt-fw-key-cert build/stm32mp1/release/nt_fw_key.crt \
201 --fw-config build/stm32mp1/release/fdts/fw-config.dtb \
[all …]
|
| /rk3399_ARM-atf/docs/plat/qti/ |
| H A D | chrome.rst | 14 How to build
27 Coreboot, so only bl31.elf need to get build from the TF-A repository.
29 The build command looks like
36 Additional QTISECLIB_PATH=<path to qtiseclib> can be added in build command.
37 if QTISECLIB_PATH is not added in build command stub implementation of qtiseclib
|
| /rk3399_ARM-atf/docs/components/spd/ |
| H A D | optee-dispatcher.rst | 6 To build and execute OP-TEE follow the instructions at
7 `OP-TEE build.git`_
30 .. _OP-TEE OS: https://github.com/OP-TEE/build
31 .. _OP-TEE build.git: https://github.com/OP-TEE/build
|
| /rk3399_ARM-atf/docs/ |
| H A D | Makefile | 13 SPHINXBUILD = sphinx-build
16 BUILDDIR = build
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | index.rst | 10 cpu-specific-build-macros
17 trusted-board-boot-build
|
| H A D | trusted-board-boot-build.rst | 9 The following steps should be followed to build FIP and (optionally) FWU_FIP
22 options required to build the mbed TLS sources.
28 #. To build the FIP image, ensure the following command line variables are set
29 while invoking ``make`` to build TF-A:
36 document. To select a different one, use the ``COT`` build option.
38 If using a custom build of OpenSSL, set the ``OPENSSL_DIR`` variable
46 specified at build time. The following locations are currently supported (see
47 ``ARM_ROTPK_LOCATION`` build option):
97 The result of this build will be the bl1.bin and the fip.bin binaries. This
99 Trust. These certificates can also be found in the output build directory.
[all …]
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | fvp-build-options.rst | 7 build the topology tree within TF-A. By default TF-A is configured for dual
23 in the system. This option defaults to 1. Note that the build option
35 file in ``fdts/`` folder depending on other build options. But some cases,
36 like shifted affinity format for MPIDR, cannot be detected at build time
43 the default HW_CONFIG selected by the build system.
51 tree blob at build time. Takes an initrd size value in hex format
54 blob at build time. Takes a path to an initrd file. Can be used as an
|
| /rk3399_ARM-atf/ |
| H A D | .gitignore | 9 # Ignore build directory
10 build/
12 # Ignore build products from tools
|
| /rk3399_ARM-atf/tools/memory/ |
| H A D | pyproject.toml | 27 [build-system]
29 build-backend = "poetry.core.masonry.api"
|
| /rk3399_ARM-atf/docs/plat/marvell/armada/ |
| H A D | build.rst | 35 (3) Armada-37x0 build requires WTP tools installation.
44 (4) Clean previous build residuals (if any)
52 There are several build options:
112 For A7K/A8K/CN913x it is used for BLE build and for Armada37x0 it used
113 for ddr_tool build.
117 mv-ddr build process calls git commands.
119 Do not remove any parts of git checkout becuase build process and other
123 CN913x specific build options:
128 the build uses the default number of CPs, which is a number of embedded CPs inside the
134 A7K/A8K/CN913x specific build options:
[all …]
|