| /trusted-firmware-m-3.7.0/docs/platform/arm/corstone1000/ |
| D | readme.rst | 28 target. The platform has the build option to enable secure debug protocol to
46 Build section in Corstone-1000
52 The platform binaries are build using Yocto. Below is the user guide:
77 …cmake -B build/ -S . -DCMAKE_BUILD_TYPE=Debug -DTFM_TOOLCHAIN_FILE=<tf-m-root>/toolchain_GNUARM.cm…
78 cmake --build build -- install
79 dd conv=notrunc bs=1 if=build/install/outputs/bl1_1.bin of=build/install/outputs/bl1.bin seek=0
80 …dd conv=notrunc bs=1 if=build/install/outputs/bl1_provisioning_bundle.bin of=build/install/outputs…
81 ./platform/ext/target/arm/corstone1000/create-flash-image.sh build/install/outputs cs1000.bin
83 …build/install/outputs/bl1.bin" -C board.xnvm_size=64 -C se.trustedSRAM_config=6 -C se.BootROM_conf…
95 …cmake -B build/ -S . -DCMAKE_BUILD_TYPE=Debug -DTFM_TOOLCHAIN_FILE=<tf-m-root>/toolchain_GNUARM.cm…
[all …]
|
| /trusted-firmware-m-3.7.0/docs/building/ |
| D | tfm_build_instruction.rst | 2 Build instructions
6 The build process was changed a lot in Q3 2023 and included into the release v2.0.
20 Refer to :doc:`Building Tests </building/tests_build_instruction>` on how to build TF-M
37 Build Tests <tests_build_instruction>
47 This build generates the SPE binary and artifacts, necessary for :ref:`Building NSPE`.
77 only mandatory argument to TF-M build is a platform name, provided via
81 - An absolute path of target platform, mainly used for out-of-tree platform build.
89 - Build directory ``<Build Dir>`` - the location of all intermediate files required to produce
90 a build target.
91 - Install directory ``<Artifact Dir>`` - the location of the build output files.
[all …]
|
| D | tests_build_instruction.rst | 2 Build Tests
8 ``CONFIG_TFM_TEST_DIR`` option is used. When SPE build system sees this option
11 Also, test configurations should be passed to SPE build to include building Secure Tests.
14 repository [1]_ to build the SPE for testing rather than building it from the TF-M repository.
31 It is recommended to build both SPE and NSPE from that folder.
42 cmake --build build_spe -- install
45 cmake --build build_test
53 All the test suite config options should be passed to the SPE build command, including NS ones.
54 The SPE building command also accepts all the other config options used to build a single TF-M.
55 All options passing to SPE build does not have to be duplicated in NSPE build, including NS test
[all …]
|
| D | documentation_generation.rst | 10 The documentation build is independent from building the binary artifacts.
31 1. As a custom target of TF-M CMake build system
83 Build TF-M Reference Manual
96 cmake --build build_docs -- tfm_docs_refman_html tfm_docs_refman_pdf
104 cmake --build build_docs -- tfm_docs_refman_html tfm_docs_refman_pdf
107 Build TF-M User Guide
120 cmake --build build_docs -- tfm_docs_userguide_html tfm_docs_userguide_pdf
128 cmake --build build_docs -- tfm_docs_userguide_html tfm_docs_userguide_pdf
132 Direct build using a command line tools
135 The direct build will build both user_guide and reference_manual.
[all …]
|
| /trusted-firmware-m-3.7.0/platform/ext/cmsis/CMSIS/CoreValidation/ |
| D | README.md | 11 ┣ �� Project Solution and project files to build tests for various configurations.
17 Currently, the following build configurations are provided:
63 The following tools are required to build and run the CoreValidation tests:
67 - [Ninja 1.10.2](https://github.com/ninja-build/ninja/releases)*
81 Install the Python packages required by `build.py`:
87 ## Build and run
89 To build and run the CoreValidation tests for one or more configurations use the following command …
90 Select the `<compiler>`, `<device>`, and `<optimize>` level to `build` and `run` for.
93 ./CMSIS/CoreValidation/Project $ ./build.py -c <compiler> -d <device> -o <optimize> [build] [run]
96 For example, build and run the tests using GCC for Cortex-M3 with low optimization, execute:
[all …]
|
| /trusted-firmware-m-3.7.0/docs/platform/cypress/psoc64/ |
| D | cypress_psoc64_spec.rst | 44 Configuring the build
47 The build configuration for TF-M is provided to the build system using command
64 Build Instructions
67 The following instructions build multi-core TF-M without regression test suites
77 mkdir <build folder>
78 pushd <build folder>
83 cmake --build <build folder> -- -j VERBOSE=1
85 The following instructions build multi-core TF-M with regression test suites
95 mkdir <build folder>
96 pushd <build folder>
[all …]
|
| /trusted-firmware-m-3.7.0/platform/ext/cmsis/ |
| D | gen_pack.sh | 22 # Temporary pack build directory,
23 # Default: ./build
25 # PACK_BUILD=./build
45 # Specify file names to be deleted from pack build directory
80 # usage: preprocess <build>
81 # <build> The build folder
85 # before populating the pack build folder
93 # usage: postprocess <build>
94 # <build> The build folder
98 # after populating the pack build folder
|
| /trusted-firmware-m-3.7.0/docs/cmake/ |
| D | FindSphinx.cmake | 14 #(sphinx-build) and it's dependences (Python).
17 #method this module expects sphix-build to be either available on the PATH,
21 # SPHINX_PATH = variable specifying where sphinx-build can be found.
28 # SPHINX_VERSION = The version reported by "sphinx-build --version"
29 # SPHINX_FOUND = True is sphinx-build was found and executed fine
52 NAMES sphinx-build
63 message(STATUS "Failed to find sphinx-build at ${SPHINX_PATH}.")
70 NAMES sphinx-build
75 message(STATUS "Failed to find sphinx-build at OS specific default locations.")
85 if(_SPHINX_VERSION MATCHES ".*sphinx-build[^0-9.]*([0-9.]+).*")
[all …]
|
| /trusted-firmware-m-3.7.0/docs/platform/arm/rse/rom_releases/2024-04/ |
| D | readme.rst | 30 - The build instructions for this release initially contained an incorrect
31 address for the DMA ICS concatenation with the ROM code. The build
105 Build command
108 The RSE ROM image should be generated with the following build commands:
117 cmake -S . -B build -DTFM_PLATFORM=arm/rse/tc \
126 cmake --build build -- install
128 srec_cat build/bin/bl1_1.bin -Binary -offset 0x0 \
129 build/bin/rom_dma_ics.bin -Binary -offset 0x1F000 \
|
| /trusted-firmware-m-3.7.0/docs/getting_started/ |
| D | tfm_getting_started.rst | 19 Build and run instructions
24 To build & run TF-M:
28 :doc:`Build instructions </building/tfm_build_instruction>`
29 to compile and build the TF-M source.
40 Set up build environments
43 TF-M officially supports a limited set of build environments and setups. In
65 sudo apt-get install -y git curl wget build-essential libssl-dev python3 \
151 be available in the build environment. The currently supported compiler
224 …- Download IAR build tools from `here <https://www.iar.com/products/architectures/arm/iar-embedded…
233 …- Download IAR build tools from `here <https://www.iar.com/products/architectures/arm/iar-embedded…
[all …]
|
| /trusted-firmware-m-3.7.0/docs/platform/nxp/lpcxpresso55s69/ |
| D | README.rst | 16 There are two options for the TF-M build - with or without secondary bootloader (BL2).
20 To build S and NS application image without a BL2, run the following commands:
26 cmake --build build_spe -- install
28 cmake --build build_test
33 To build S and NS application along with a BL2, run the following commands:
39 cmake --build build_spe -- install
41 cmake --build build_test
52 cmake --build build_spe -- install
54 cmake --build build_test
|
| /trusted-firmware-m-3.7.0/platform/ext/cmsis/CMSIS/Core/Test/ |
| D | README.md | 14 ┣ �� build.py Build wrapper
16 ┣ �� requirements.txt Python dependencies required for build.py script
22 Currently, the following build configurations are provided:
74 The following tools are required to build and run the CoreValidation tests:
78 - [Ninja 1.10.2](https://github.com/ninja-build/ninja/releases)*
95 Install the Python packages required by `build.py`:
103 To build and run the CoreValidation tests for one or more configurations use the following command …
107 ./CMSIS/Core/Test $ ./build.py -c <compiler> -d <device> -o <optimize> [lit]
113 ./CMSIS/Core/Test $ ./build.py -c GCC -d CM3 -o none lit
|
| /trusted-firmware-m-3.7.0/platform/ext/cmsis/CMSIS/CoreValidation/Project/ |
| D | build.py | 161 return f"build/{config.device[1]}/{config.compiler.toolchain}/{config.optimize}"
166 """Build the selected configurations using CMSIS-Build."""
171 def build(config, results): function
172 """Build the selected configurations using CMSIS-Build."""
181 file = f"build/CoreValidation-{config_suffix(config)}.zip"
182 logging.info("Archiving build output to %s...", file)
191 """Extract the latest build archive."""
192 …archives = sorted(glob(f"build/CoreValidation-{config_suffix(config, timestamp=False)}-*.zip"), re…
203 results[0].test_report.write(f"build/CoreValidation-{config_suffix(config)}.junit")
|
| D | Validation.csolution.yml | 85 build-types:
113 cprjdir: ./build/$TargetType$/$Compiler$/$BuildType$/$Project$
114 intdir: ./build/$TargetType$/$Compiler$/$BuildType$/$Project$/intdir
115 outdir: ./build/$TargetType$/$Compiler$/$BuildType$/$Project$/outdir
|
| /trusted-firmware-m-3.7.0/docs/configuration/ |
| D | index.rst | 21 Build configuration
22 Specifies which file or component to include into compilation and build.
23 These are options, usually used by a build system to enable/disable
26 to other build systems.
27 In the :ref:`Base_configuration` table these options have *Build* type.
40 better support build systems other than a CMake, TF-M introduced a
48 TF-M Project provides a base build, defined in ``/config/config_base.cmake``
73 In contrast, before TF-M v1.7.0, the default build includes all possible
74 features. With growing functionality, such rich default build became
95 on step 1 will generate warnings which are expected to break a build.
[all …]
|
| D | test_configuration.rst | 18 | TEST_NS_ATTESTATION | Build non-secure regression Attestation tests. |
20 | TEST_NS_T_COSE | Build non-secure regression t_cose tests. |
22 | TEST_NS_QCBOR | Build non-secure regression QCBOR tests. |
24 | TEST_NS_CRYPTO | Build non-secure regression Crypto tests. |
26 | TEST_NS_ITS | Build non-secure regression ITS tests. |
28 | TEST_NS_PS | Build non-secure regression PS tests. |
30 | TEST_NS_PLATFORM | Build non-secure regression Platform tests. |
32 | TEST_NS_FWU | Build non-secure regression FWU tests. |
34 | TEST_NS_IPC | Build non-secure regression IPC tests. |
36 | TEST_NS_SLIH_IRQ | Build non-secure regression Second-Level Interrupt Handling tests. |
[all …]
|
| /trusted-firmware-m-3.7.0/docs/platform/stm/b_u585i_iot02a/ |
| D | readme.rst | 7 Configuration and Build
11 and build the selected configuration as follow.
13 The build configuration for TF-M is provided to the build system using command
16 The following instructions build multi-core TF-M with regression test suites
45 The following instructions build multi-core TF-M with PSA API test suite for
|
| /trusted-firmware-m-3.7.0/docs/platform/stm/nucleo_l552ze_q/ |
| D | readme.rst | 7 Configuration and Build
11 and build the selected configuration as follow.
13 The build configuration for TF-M is provided to the build system using command
16 The following instructions build multi-core TF-M with regression test suites
45 The following instructions build multi-core TF-M with PSA API test suite for
|
| /trusted-firmware-m-3.7.0/docs/platform/stm/stm32h573i_dk/ |
| D | readme.rst | 7 Configuration and Build
11 and build the selected configuration as follow.
13 The build configuration for TF-M is provided to the build system using command
16 The following instructions build multi-core TF-M with regression test suites
45 The following instructions build multi-core TF-M with PSA API test suite for
|
| /trusted-firmware-m-3.7.0/docs/platform/stm/stm32l562e_dk/ |
| D | readme.rst | 7 Configuration and Build
11 and build the selected configuration as follow.
13 The build configuration for TF-M is provided to the build system using command
16 The following instructions build multi-core TF-M with regression test suites
45 The following instructions build multi-core TF-M with PSA API test suite for
|
| /trusted-firmware-m-3.7.0/docs/platform/arm/mps3/corstone310/ |
| D | README.rst | 30 Build instructions with platform name: arm/mps3/corstone310/an555
40 Build instructions with platform name: arm/mps3/corstone310/fvp
68 … passing the new values to the build command, or by setting the ``-DPROVISIONING_KEYS_CONFIG`` flag
81 The new generated keypair can be found in the ``<build dir>/bin`` folder or in the
84 ``<build directory>/platform/target/provisioning/provisioning_data.c``
110 $ cd <build dir>/bin
115 build dir to ``<MPS3 device name>/SOFTWARE/``
171 build dir to ``<FVP installation path>/models/Linux64_GCC-9.3/``
206 …-a cpu0*="<path-to-build-directory>/bl2.axf" --data "<path-to-build-directory>/tfm_s_ns_signed.bin…
|
| /trusted-firmware-m-3.7.0/docs/configuration/profiles/ |
| D | tfm_profile_medium_arot-less.rst | 105 values, to explicitly configured the features required in this profile, during TF-M build.
109 The behavior of the build flow (particularly the order of configuration loading and overriding) can
158 automatically. A warning will be thrown out during build.
178 To build Profile Medium-ARoT-less, argument ``TFM_PROFILE`` in build command line should be
182 The following commands build Profile Medium-ARoT-less without test cases on **Musca-B1** with
183 build type **MinSizeRel**, built by **Armclang**.
188 mkdir build && cd build
194 cmake --build ./ -- install
196 The following commands build Profile Medium-ARoT-less with regression test cases on
197 **Musca-B1** with build type **MinSizeRel**, built by **Armclang**.
[all …]
|
| /trusted-firmware-m-3.7.0/docs/design_docs/booting/ |
| D | tfm_secure_boot.rst | 74 together. In order to have the same artefacts at the end of the build regardless
79 ``bl2/ext/mcuboot/scripts/``. At the end of a successful build the signed TF-M
164 switch (see `Build time configuration`_). With swapping image upgrade strategy
191 switch (see `Build time configuration`_). When enabling direct-xip operation
207 two build directories when building images using this mode, as intermediate
282 configuration variable in the build configuration file, or include this
286 ``MCUBOOT_UPGRADE_STRATEGY`` configuration variable in the build
290 ``MCUBOOT_UPGRADE_STRATEGY`` configuration variable in the build
347 Build time configuration
394 public key(s) must be known at MCUBoot build time.
[all …]
|
| /trusted-firmware-m-3.7.0/docs/platform/arm/mps3/corstone300/ |
| D | README.rst | 29 Build instructions with platform name: arm/mps3/corstone300/an547
38 Build instructions with platform name: arm/mps3/corstone300/an552
47 Build instructions with platform name: arm/mps3/corstone300/fvp
75 … passing the new values to the build command, or by setting the ``-DPROVISIONING_KEYS_CONFIG`` flag
87 The new generated keypair can be found in the ``<build dir>/bin`` folder or in the
90 ``<build directory>/platform/target/provisioning/provisioning_data.c``
111 build dir to ``<MPS3 device name>/SOFTWARE/``
177 build dir to ``<MPS3 device name>/SOFTWARE/``
236 build dir to ``<FVP installation path>/models/Linux64_GCC-9.3/``
271 …-a cpu0*="<path-to-build-directory>/bl2.axf" --data "<path-to-build-directory>/tfm_s_ns_signed.bin…
|
| /trusted-firmware-m-3.7.0/docs/platform/nuvoton/m2351/ |
| D | README.rst | 7 Build TF-M regression test with M2351 by following commands:
18 $ cmake --build build --parallel -- install
24 $ cmake --build build_test --parallel -- install
|
