Searched full:build (Results 1 – 25 of 238) sorted by relevance
12345678910
| /trusted-firmware-a-3.4.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 | 14 The TF-A build system provides the make target ``fip`` to create a FIP file
16 project. Examples below show how to build a FIP file for FVP, packaging TF-A
35 build/fvp/<build-type>/fip.bin
37 For advanced operations on FIP files, it is also possible to independently build
47 Build the tool:
67 --tb-fw build/<platform>/<build-type>/bl2.bin \
68 --soc-fw build/<platform>/<build-type>/bl31.bin \
83 --tb-fw build/<platform>/release/bl2.bin \
84 build/<platform>/debug/fip.bin
98 --tb-fw build/<platform>/debug/fip.bin
[all …]
|
| D | index.rst | 10 docs-build
11 tools-build
12 initial-build
13 build-options
|
| D | build-options.rst | 1 Build Options
4 The TF-A build system supports the following build options. Unless mentioned
5 otherwise, these options are expected to be specified at the build command
7 build system doesn't track dependency for build options. Therefore, if any of
8 the build options are changed from a previous build, a clean build must be
13 Common build options
29 - ``ARCH`` : Choose the target build architecture for TF-A. It can take either
33 - ``ARM_ARCH_FEATURE``: Optional Arm Architecture build option which specifies
48 - ``BL2``: This is an optional build option which specifies the path to BL2
52 - ``BL2U``: This is an optional build option which specifies the path to
[all …]
|
| /trusted-firmware-a-3.4.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 | 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
|
| D | brcm-stingray.rst | 23 How to build
26 Build Procedure
31 - Build u-boot first, and get the binary image: u-boot.bin,
33 - Build TF-A
35 Build fip:
|
| /trusted-firmware-a-3.4.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.4.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
76 # Debug build
82 # Build platform
96 # Build option to enable MPAM for lower ELs
187 # Build flag to treat usage of deprecated platform and framework APIs as error.
235 # Option to build TF with Measured Boot support
[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.4.0/docs/components/spd/ |
| D | optee-dispatcher.rst | 6 To build and execute OP-TEE follow the instructions at
7 `OP-TEE build.git`_
13 .. _OP-TEE OS: https://github.com/OP-TEE/build
14 .. _OP-TEE build.git: https://github.com/OP-TEE/build
|
| /trusted-firmware-a-3.4.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.4.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.
39 specified at build time. The following locations are currently supported (see
40 ``ARM_ROTPK_LOCATION`` build option):
69 The result of this build will be the bl1.bin and the fip.bin binaries. This
71 Trust. These certificates can also be found in the output build directory.
74 Non-Volatile storage during the :ref:`Firmware Update (FWU)` process. To build the
[all …]
|
| /trusted-firmware-a-3.4.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.4.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/8K/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.4.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.4.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.4.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.4.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.4.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.4.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
|
| /trusted-firmware-a-3.4.0/plat/nxp/soc-ls1046a/ls1046ardb/ |
| D | platform.mk | 7 # board-specific build parameters
26 # Adding Platform files build files
34 # Adding platform board build info
37 # Adding SoC build info
|
| /trusted-firmware-a-3.4.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 …]
|
12345678910
