| /rk3399_ARM-atf/docs/getting_started/ |
| H A 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 …]
|
| 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,
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 …]
|
| H A D | index.rst | 9 docs-build
10 initial-build
11 tools-build
12 build-options
13 build-internals
|
| 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 | 1 Internal Build Options
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/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 | 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 …]
|
| 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 | s32g274a.rst | 42 How to build
62 BUILD="debug"
64 BUILD="release"
67 BOOT_IMAGE="build/s32g274ardb2/${BUILD}/BOOT_IMAGE.bin"
68 BL2_BIN="build/s32g274ardb2/${BUILD}/bl2.bin"
69 FIP_BIN="build/s32g274ardb2/${BUILD}/fip.bin"
89 # Build a bootable image by appending the IVT
|
| /rk3399_ARM-atf/make_helpers/ |
| H A 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
22 # The Target build architecture. Supported values are: aarch64, aarch32.
62 # Build flag to include AArch32 registers in cpu context save and restore during
72 # Debug build
78 # Build platform
125 # Build flag to treat usage of deprecated platform and framework APIs as error.
198 # Option to build TF with Measured Boot support
201 # Option to build TF with Discrete TPM support
[all …]
|
| 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/plat/rockchip/rk3399/drivers/m0/ |
| H A D | Makefile | 11 # Build architecture
14 # Build platform
33 LDFLAGS := -Wl,--gc-sections -Wl,--build-id=none -Wl,--fatal-warnings -z noexecstack
47 OBJS_COMMON := $(addprefix $(BUILD)/,$(call SOURCES_TO_OBJS,$(SOURCES_COMMON)))
48 OBJS := $(addprefix $(BUILD)/,$(call SOURCES_TO_OBJS,$(SOURCES)))
49 OBJS_PMU := $(addprefix $(BUILD)/,$(call SOURCES_TO_OBJS,$(SOURCES_PMU)))
50 LINKERFILE := $(BUILD)/$(PLAT_M0).ld
51 MAPFILE := $(BUILD)/$(PLAT_M0).map
52 MAPFILE_PMU := $(BUILD)/$(PLAT_M0_PMU).map
53 ELF := $(BUILD)/$(PLAT_M0).elf
[all …]
|
| /rk3399_ARM-atf/docs/plat/st/ |
| H A 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.
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 \
[all …]
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | fvp-build-options.rst | 3 Arm FVP Platform Specific Build Options
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/docs/design/ |
| 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
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):
97 The result of this build will be the bl1.bin and the fip.bin binaries. This
[all …]
|
| /rk3399_ARM-atf/services/spd/tspd/ |
| H A 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
|
| /rk3399_ARM-atf/docs/plat/marvell/armada/ |
| H A 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 …]
|
| /rk3399_ARM-atf/docs/plat/arm/juno/ |
| H A 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 …]
|
| /rk3399_ARM-atf/docs/plat/qti/ |
| H A D | chrome.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
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/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/services/std_svc/spm/el3_spmc/ |
| H A 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.
|
| /rk3399_ARM-atf/plat/nxp/soc-ls1088a/ls1088ardb/ |
| H A 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
|
| /rk3399_ARM-atf/plat/nxp/soc-ls1028a/ls1028ardb/ |
| H A D | platform.mk | 7 # Board-specific build parameters
13 # DDR build parameters
29 # Add platform board build info
32 # Add SoC build info
|
| /rk3399_ARM-atf/docs/plat/arm/ |
| H A D | arm-build-options.rst | 1 Arm Development Platform Build Options
4 Arm Platform Build Options
10 sets the TSP location to DRAM and ignores the ``ARM_TSP_RAM_LOCATION`` build
30 Trusted Watchdog may be disabled at build time for testing or development
119 Arm CSS Platform-Specific Build Options
137 - ``CSS_SYSTEM_GRACEFUL_RESET``: Build option to enable graceful powerdown of
138 CPU core on reset. This build option can be used on CSS platforms that
142 Arm FVP Build Options
147 build option ENABLE_RME=0 and 384 for ENABLE_RME=1.
149 Arm Juno Build Option
[all...] |
| /rk3399_ARM-atf/plat/nxp/soc-ls1046a/ls1046ardb/ |
| H A 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
|