Searched refs:build (Results 1 – 25 of 129) sorted by relevance
123456
| /trusted-firmware-a-3.7.0/docs/getting_started/ |
| D | index.rst | 9 docs-build
10 initial-build
11 tools-build
12 build-options
13 build-internals
|
| 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 …]
|
| 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 …]
|
| 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.
64 Output from the build process will be placed in: ``docs/build/html``.
77 To build the documentation in PDF format, additionally ensure that the following
94 docs latexpdf`` to build the documentation. Output from the build process
95 (``trustedfirmware-a.pdf``) can be found in ``docs/build/latex``.
106 build the documentation directly with ``make``.
137 build process will be placed in: ``docs/build/html``.
|
| /trusted-firmware-a-3.7.0/docs/perf/ |
| 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
|
| D | psci-performance-n1sdp.rst | 26 #. Build TF-A with the following build options:
38 -sLS -o build/n1sdp/release/scp_rom.bin \
41 --retry 5 -sLS -o build/n1sdp/release/scp_ram.bin \
49 -sLS -o build/n1sdp/release/mcp_rom.bin \
52 -sLS -o build/n1sdp/release/mcp_ram.bin \
61 uuid=cfacc2c4-15e8-4668-82be-430a38fad705,file=build/n1sdp/release/bl1.bin \
62 --scp-fw build/n1sdp/release/scp_ram.bin build/n1sdp/release/scp_fw.bin
69 --blob uuid=54464222-a4cf-4bf8-b1b6-cee7dade539e,file=build/n1sdp/release/mcp_ram.bin \
70 build/n1sdp/release/mcp_fw.bin
|
| /trusted-firmware-a-3.7.0/docs/plat/ |
| 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.
|
| D | rockchip.rst | 29 How to build
34 these images need to get build from the TF-A repository.
36 For AARCH64 architectures the build command looks like
45 want to build for and the CROSS_COMPILE argument with you cross-
53 to put the built images during their respective build process.
54 So after successfully building TF-A just follow their build instructions
|
| D | qti.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
35 Additional QTISECLIB_PATH=<path to qtiseclib> can be added in build command.
36 if QTISECLIB_PATH is not added in build command stub implementation of qtiseclib
|
| 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 …]
|
| D | xilinx-versal.rst | 12 To build:
17 To build ATF for different platform (supported are "silicon"(default) and "versal_virt")
22 To build bl32 TSP you have to rebuild bl31 too
27 To build TF-A for JTAG DCC console
32 To build TF-A with Straight-Line Speculation(SLS)
37 Xilinx Versal platform specific build options
|
| 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.
|
| 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 Xilinx Versal NET platform specific build options
|
| 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
|
| /trusted-firmware-a-3.7.0/docs/plat/st/ |
| D | stm32mp1.rst | 107 You need to build BL2, BL32 (SP_min or OP-TEE) and BL33 (U-Boot) before building FIP binary.
131 To build TF-A BL32, and its device tree file:
140 To build TF-A BL2 with its STM32 header for SD-card boot:
185 tools/cert_create/cert_create -n --rot-key build/stm32mp1/release/rot_key.pem \
189 --trusted-key-cert build/stm32mp1/release/trusted_key.crt \
193 --tos-fw-cert build/stm32mp1/release/tos_fw_content.crt \
194 --tos-fw-key-cert build/stm32mp1/release/tos_fw_key.crt \
196 --nt-fw-cert build/stm32mp1/release/nt_fw_content.crt \
197 --nt-fw-key-cert build/stm32mp1/release/nt_fw_key.crt \
199 --fw-config build/stm32mp1/release/fdts/fw-config.dtb \
[all …]
|
| /trusted-firmware-a-3.7.0/docs/ |
| D | Makefile | 11 SPHINXBUILD = sphinx-build
14 BUILDDIR = build
|
| /trusted-firmware-a-3.7.0/docs/design/ |
| D | index.rst | 10 cpu-specific-build-macros
16 trusted-board-boot-build
|
| 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):
79 The result of this build will be the bl1.bin and the fip.bin binaries. This
81 Trust. These certificates can also be found in the output build directory.
[all …]
|
| /trusted-firmware-a-3.7.0/docs/components/spd/ |
| 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
|
| /trusted-firmware-a-3.7.0/ |
| D | .gitignore | 9 # Ignore build directory
10 build/
12 # Ignore build products from tools
|
| /trusted-firmware-a-3.7.0/docs/tools/ |
| D | memory-layout-tool.rst | 45 build-path: build/fvp/release
121 the build path to generate a table (per memory type), showing memory allocation
127 build-path: build/fvp/release
160 build-path: build/fvp/release
213 build-path: build/fvp/release
|
| /trusted-firmware-a-3.7.0/docs/components/ |
| D | realm-management-extension.rst | 8 provides instructions on how to build and run TF-A with RME.
95 This section describes how you can build and run TF-A with RME enabled.
96 We assume you have read the :ref:`Prerequisites` to build TF-A.
98 The following instructions show you how to build and run TF-A with RME
126 **1. Clone and build RMM Image**
129 Host Environment and build `RMM`_. The build commands assume that
134 To clone `RMM`_ and build using the default build options for FVP:
140 cmake -DRMM_CONFIG=fvp_defcfg -S . -B build
141 cmake --build build
143 This will generate **rmm.img** in **build/Release** folder.
[all …]
|
| D | activity-monitors.rst | 9 When the ``ENABLE_FEAT_AMU=1`` build option is provided, Trusted Firmware-A
20 build option.
26 - |FCONF|, controlled by the ``ENABLE_AMU_FCONF`` build option.
|
| /trusted-firmware-a-3.7.0/plat/mediatek/mt8192/drivers/spm/ |
| D | build.mk | 57 $(info SPM build flags: ${PLAT_SPM_DEBUG_CFLAGS})
58 $(info SPM build files: ${BL31_MT_LPM_PLAT_SPM_SOURCE_FILES})
|
| /trusted-firmware-a-3.7.0/plat/mediatek/mt8195/drivers/spm/ |
| D | build.mk | 57 $(info SPM build flags: ${PLAT_SPM_DEBUG_CFLAGS})
58 $(info SPM build files: ${BL31_MT_LPM_PLAT_SPM_SOURCE_FILES})
|
123456
