| /docs/ |
| A D | conf.py | 33 version = check_output("git describe --tags --always", variable
36 _v = vrex.match(version)
39 version = release + "+" + _v.group('GIT_SHA')[:7] variable
42 version = release = 'Unknown'
|
| /docs/design_docs/booting/ |
| A D | secure_boot_rollback_protection.rst | 12 an older version of its software, which has been deprecated due to security
20 - Manifest data: Metadata of the software image: size, version, hash,
63 was fixed in the current version. Later when this image is installed on the
65 to handle this counter independently from image main version number:
73 However, as an alternative solution the image version number also could serve
74 as the security counter of the image. Even the version number itself could be
96 or version counters as a counter with the following properties:
98 - It must only be possible to increment a version counter through a Trusted
100 - It must only be possible to increment a version counter. It must not be
102 - When a version counter reaches its maximum value, it must not roll over,
[all …]
|
| A D | tfm_secure_boot.rst | 142 layout. The third option is the direct execute-in-place version, which
306 - **Minimum version:** The minimum version of other image must be present on
314 minimum required version of the secure image.
316 minimum required version of the non-secure image.
318 Example of how to provide the secure image minimum version::
738 notice that image with higher version number (``version=1.2.3.5``) is executed:
743 [INF] Image 0: version=1.2.3.4, magic= good, image_ok=0x3
744 [INF] Image 1: version=1.2.3.5, magic= good, image_ok=0x3
800 (``version=0.0.0.2``) is executed:
805 [INF] Image 0: version=0.0.0.1, magic= good, image_ok=0x3
[all …]
|
| /docs/getting_started/ |
| A D | tfm_getting_started.rst | 58 1. version supported:
69 3. verify cmake version:
73 cmake --version
77 Please download CMake version 3.21 or later from https://cmake.org/download/.
87 1. version supported:
93 - Git client latest version (https://git-scm.com/download/win)
94 - CMake version 3.21 or later (`native Windows version <https://cmake.org/download/>`__)
96 - Python3 `(native Windows version) <https://www.python.org/downloads/>`__ and
175 - Arm Compiler minimum version v6.21
203 - GNU Arm compiler version minimum 10.3.2021.10
[all …]
|
| /docs/platform/rpi/rp2350/ |
| A D | readme.rst | 34 SDK version used for testing: ``SDK 2.1.1 release``.
36 To use a different version of the SDK than the one your version of TF-M uses
40 ``platform/ext/target/rpi/rp2350/pico-sdk.patch`` file from a TF-M version
41 that uses the SDK version you want to use, and it can be applied with
44 For example, to use SDK version 2.1.1, you can take the ``pico-sdk.patch``
45 file from TF-M version 2.1.2 and apply it to the SDK version 2.1.1.
|
| /docs/cmake/ |
| A D | FindSphinx.cmake | 28 # SPHINX_VERSION = The version reported by "sphinx-build --version"
81 #Get Sphinx version
82 execute_process(COMMAND "${SPHINX_EXECUTABLE}" "--version" OUTPUT_VARIABLE _SPHINX_VERSION OUTPUT_S…
|
| /docs/design_docs/services/ |
| A D | stateless_rot_service.rst | 31 The index, stateless indicator, and service version information are encoded into
47 - service version requested by client - for client version check
68 ``sid.h`` contains service ID and version. The tooling is extended to generate
72 with firmware framework version 1.1.
116 2. This API validates stateless handle, decodes index and service version
120 authorization check, service and client version check, and handle space
|
| A D | tfm_fwu_service.rst | 64 This service follows the PSA Firmware Update API spec of version 1.0 [1]_. Please refer to
264 An additional TLV area "image version" is added into the shared memory between
265 BL2 and TF-M. So that the firmware update partition can get the image version.
266 Even though the image version information is also included in the ``BOOT RECORD``
267 TLV area which is encoded by CBOR, adding a dedicated ``image version`` TLV area
|
| A D | tfm_psa_inter_process_communication.rst | 144 - These 2 functions are finally handled in SPM and return the framework version
145 or version to the caller.
149 psa_handle_t psa_connect(uint32_t sid, uint32_t version);
|
| A D | tfm_its_service.rst | 26 version 1.0-beta2. There is not yet an implementation of PSA Internal Trusted
40 The TF-M ITS service will implement PSA ITS version 1.0. It will be provided by
140 update the implementation to be aligned with the latest version of the PSA
183 - Keep a simplified version of the SST object table that just maps from
|
| /docs/releases/ |
| A D | 1.3.0.rst | 15 - Update MCUboot version to v1.7.2.
149 * - | Regression tests fail with GNU Arm Embedded toolchain version
151 | The support for CMSE feature is broken in version 10-2020-q4-major. The
152 | fix will be available in future release version.
|
| A D | release_process.rst | 77 Trusted Firmware-M uses a semantic versioning scheme. A version number is
82 - <MAJOR>: Major release version for significant feature and API changes.
83 - <MINOR>: Minor release version for incremental features and API changes.
110 version can hold PSA certification obtained once without a need for
125 unchanged with valid PSA certificate for that version.
|
| A D | index.rst | 71 interpreting version numbers.
|
| /docs/platform/arm/rse/rom_releases/2024-04/ |
| A D | readme.rst | 51 TF-M version
63 - arm-none-eabi-gcc --version | head -n 1
69 - python3 --version
|
| /docs/integration_guide/ |
| A D | tfm_fpu_support.rst | 15 2021.10`` and later version shall be used to mitigate VLLDM instruction
21 and later version shall be used to mitigate VLLDM instruction security
43 This issue has been fixed in the later version.
|
| /docs/design_docs/dual-cpu/ |
| A D | communication_prototype_between_nspe_and_spe_in_dual_core_systems.rst | 118 - Requested version of secure service
500 | ``version`` | The version of the PSA Framework implementation that is |
530 | ``> 0`` | The minor version of the implemented RoT Service. |
547 uint32_t version,
556 | ``version`` | The version of the RoT Service. |
570 | ``Does not return`` | The RoT Service ID and version are not supported, |
|
| /docs/design_docs/software/ |
| A D | code_sharing.rst | 304 version of the shared code. Then new code cannot rely on the shared version.
306 be ignored and the updated version of the functions must be compiled in the
307 SPE binary. The Mbed TLS library is API compatible with its current version
342 - `shared_code.axf`: GNUARM specific. The stripped version of the firmware
349 able to link them to any future SPE version.
|
| /docs/platform/stm/stm32l562e_dk/ |
| A D | readme.rst | 69 …git checkout <recommended tf-m-tests commit> (..\trusted-firmware-m\lib\ext\tf-m-tests\version.txt)
98 …git checkout <recommended tf-m-tests commit> (..\trusted-firmware-m\lib\ext\tf-m-tests\version.txt)
|
| /docs/platform/stm/b_u585i_iot02a/ |
| A D | readme.rst | 64 …git checkout <recommended tf-m-tests commit> (..\trusted-firmware-m\lib\ext\tf-m-tests\version.txt)
93 …git checkout <recommended tf-m-tests commit> (..\trusted-firmware-m\lib\ext\tf-m-tests\version.txt)
|
| /docs/platform/stm/stm32h573i_dk/ |
| A D | readme.rst | 72 …git checkout <recommended tf-m-tests commit> (..\trusted-firmware-m\lib\ext\tf-m-tests\version.txt)
101 …git checkout <recommended tf-m-tests commit> (..\trusted-firmware-m\lib\ext\tf-m-tests\version.txt)
|
| /docs/platform/stm/nucleo_l552ze_q/ |
| A D | readme.rst | 68 …git checkout <recommended tf-m-tests commit> (..\trusted-firmware-m\lib\ext\tf-m-tests\version.txt)
97 …git checkout <recommended tf-m-tests commit> (..\trusted-firmware-m\lib\ext\tf-m-tests\version.txt)
|
| /docs/building/ |
| A D | documentation_generation.rst | 57 …# NOTE: If your system python install version is <3.10 you can use `uv <https://docs.astral.sh/uv/…
99 …# NOTE: If your system python install version is <3.10 you can use `uv <https://docs.astral.sh/uv/…
|
| A D | tfm_build_instruction_iar.rst | 17 cmake needs to be version 3.21 or newer.
|
| /docs/platform/arm/rse/ |
| A D | rse_fwu_metadata.rst | 9 Current code implements version 2 of the metadata as per the spec section A3.2.2.
|
| /docs/security/security_advisories/ |
| A D | fwu_tlv_payload_out_of_bounds_vulnerability.rst | 12 | Versions | All version from TF-M `v1.3.0`_ up to TF-M `v2.2.0`_ |
|