Searched full:build (Results 1 – 25 of 283) sorted by relevance
12345678910>>...12
| /trusted-firmware-a-3.7.0/docs/getting_started/ |
| D | initial-build.rst | 1 Performing an Initial Build
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)
[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,
12 :ref:`Build Options`.
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
56 Build the tool:
76 --tb-fw build/<platform>/<build-type>/bl2.bin \
[all …]
|
| D | index.rst | 9 docs-build
10 initial-build
11 tools-build
12 build-options
13 build-internals
|
| /trusted-firmware-a-3.7.0/make_helpers/ |
| D | defaults.mk | 7 # Default, static values for build variables, listed in alphabetic order.
8 # Dependencies between build options, if any, are handled in the top-level
10 # poised to handle dependencies, as all build variables would have a default
19 # The Target build architecture. Supported values are: aarch64, aarch32.
59 # Build flag to include AArch32 registers in cpu context save and restore during
66 # Debug build
72 # Build platform
118 # Build flag to treat usage of deprecated platform and framework APIs as error.
176 # Option to build TF with Measured Boot support
185 # Build PL011 UART driver in minimal generic UART mode
[all …]
|
| D | build_env.mk | 8 # build environment specific make include files.
54 $(error "SHELL_COPY not defined for build environment.")
57 $(error "SHELL_COPY_TREE not defined for build environment.")
60 $(error "SHELL_DELETE_ALL not defined for build environment.")
63 $(error "SHELL_DELETE not defined for build environment.")
66 $(error "MAKE_PREREQ_DIR not defined for build environment.")
69 $(error "SHELL_REMOVE_DIR not defined for build environment.")
|
| /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 | synquacer.rst | 11 How to build
34 Build Procedure
37 - Firstly, in addition to the “normal” build tools you will also need a
50 export WORKSPACE=$HOME/build/developerbox-firmware
63 - Build ATF:
70 --tb-fw ./build/synquacer/release/bl31.bin \
71 --soc-fw ./build/synquacer/release/bl31.bin \
72 --scp-fw ./build/synquacer/release/bl31.bin \
75 - Build EDK2:
88 build -p $ACTIVE_PLATFORM -b RELEASE -a AARCH64 -t GCC5 -n `nproc` -D DO_X86EMU=TRUE
[all …]
|
| 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 | qti.rst | 14 How to build
23 Build Procedure
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 | 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
|
| /trusted-firmware-a-3.7.0/plat/rockchip/rk3399/drivers/m0/ |
| D | Makefile | 10 # Build architecture
13 # Build platform
39 LDFLAGS := -Wl,--gc-sections -Wl,--build-id=none
60 OBJS_COMMON := $(addprefix $(BUILD)/,$(call SOURCES_TO_OBJS,$(SOURCES_COMMON)))
61 OBJS := $(addprefix $(BUILD)/,$(call SOURCES_TO_OBJS,$(SOURCES)))
62 OBJS_PMU := $(addprefix $(BUILD)/,$(call SOURCES_TO_OBJS,$(SOURCES_PMU)))
63 LINKERFILE := $(BUILD)/$(PLAT_M0).ld
64 MAPFILE := $(BUILD)/$(PLAT_M0).map
65 MAPFILE_PMU := $(BUILD)/$(PLAT_M0_PMU).map
66 ELF := $(BUILD)/$(PLAT_M0).elf
[all …]
|
| /trusted-firmware-a-3.7.0/docs/design/ |
| 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
40 :ref:`Build Options`. In addition, set the ``LD_LIBRARY_PATH`` 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
[all …]
|
| /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 …]
|
| /trusted-firmware-a-3.7.0/docs/plat/st/ |
| D | stm32mp1.rst | 89 Build Instructions
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 \
[all …]
|
| /trusted-firmware-a-3.7.0/services/spd/tspd/ |
| D | tspd.mk | 19 # build the Test Secure Payload along with this dispatcher.
21 # In cases where an associated Secure Payload lies outside this build
23 # build command or assume it pre-built
27 # Include SP's Makefile. The assumption is that the TSP's build system is
29 # build targets and variables
32 # Let the top-level Makefile know that we intend to build the SP from source
|
| /trusted-firmware-a-3.7.0/docs/plat/marvell/armada/ |
| D | build.rst | 1 TF-A Build Instructions for Marvell Platforms
6 Build Instructions
35 (3) Armada-37x0 build requires WTP tools installation.
44 (4) Clean previous build residuals (if any)
50 (5) Build TF-A
52 There are several build options:
106 Build trusted(=1)/non trusted(=0) image, default is non trusted.
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.
[all …]
|
| /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
|
| /trusted-firmware-a-3.7.0/plat/nxp/soc-ls1088a/ls1088ardb/ |
| D | platform.mk | 7 # board-specific build parameters
19 # Adding Platform files build files
26 # Adding platform board build info
29 # Adding SoC build info
|
| /trusted-firmware-a-3.7.0/services/std_svc/spm/el3_spmc/ |
| D | spmc.mk | 32 # build the Test Secure Payload if no other image has been provided
35 # In cases where an associated Secure Payload lies outside this build
37 # build command or assume it is pre-built.
41 # Conditionally include SP's Makefile. The assumption is that the TSP's build
43 # necessary build targets and variables.
|
| /trusted-firmware-a-3.7.0/plat/nxp/soc-ls1028a/ls1028ardb/ |
| D | platform.mk | 7 # Board-specific build parameters
13 # DDR build parameters
29 # Add platform board build info
32 # Add SoC build info
|
| /trusted-firmware-a-3.7.0/docs/plat/arm/juno/ |
| D | index.rst | 4 Platform-specific build options
18 build the software stack yourself by following the
26 This section provides Juno and FVP specific instructions to build Trusted
48 For the FVP, the kernel FDT is packaged in FIP during build and loaded
61 from `TF-A downloads page`_. Alternatively, you can `build
71 # Build the fiptool
89 #. Build TF-A images and create a new FIP for FVP
99 #. Build TF-A images and create a new FIP for Juno
104 as a build parameter.
123 - Build BL32 in AArch32.
[all …]
|
| /trusted-firmware-a-3.7.0/docs/process/ |
| D | contributing.rst | 180 at regular intervals. We maintain a build script ``tf-cov-make`` which contains the
181 build configurations of various platforms in order to cover the entire source
186 respective build configurations in the ``tf-cov-make`` build script.
188 - In this section you find the details on how to append your new build
197 #. Edit `tf-cov-make`_ script by appending all the possible build configurations with
198 the specific ``build-flags`` relevant to your platform, so that newly added
212 under the Intel platform and the build configurations has been added suitably
223 - In this case for ``Hikey`` boards additional ``build-flags`` has been included
226 - Similar to this you can still find many other different build configurations
228 them and append your build configurations respectively.
[all …]
|
| /trusted-firmware-a-3.7.0/plat/nxp/soc-ls1043a/ls1043ardb/ |
| D | platform.mk | 7 # board-specific build parameters
28 # Adding Platform files build files
36 # Adding platform board build info
39 # Adding SoC build info
|
| /trusted-firmware-a-3.7.0/plat/nxp/soc-ls1046a/ls1046afrwy/ |
| D | platform.mk | 7 # board-specific build parameters
28 # Adding Platform files build files
35 # Adding platform board build info
38 # Adding SoC build info
|
| /trusted-firmware-a-3.7.0/plat/nxp/soc-ls1046a/ls1046aqds/ |
| D | platform.mk | 7 # board-specific build parameters
26 # Adding Platform files build files
35 # Adding platform board build info
38 # Adding SoC build info
|
12345678910>>...12
