| /arm-trusted-firmware-2.8.0/docs/ |
| A D | change-log.md | 3282 - Added support for TRNG firmware interface service
3603 - Fixed MSS firmware loader for A8K family
3864 - The firmware update check is now executed only once
4150 use with SCPI, and reserve and map space for the SCP firmware
4248 - encrypt_fw: Add firmware authenticated encryption tool
4462 firmware updates.
5963 firmware image loading mechanism that adds flexibility.
6140 firmware to update firmware images from external interfaces to SoC
6402 - The Juno-specific firmware design documentation is incomplete.
6523 - The Juno-specific firmware design documentation is incomplete.
[all …]
|
| /arm-trusted-firmware-2.8.0/docs/getting_started/ |
| A D | image-terminology.rst | 48 platform-specific and may include TF-A images and other firmware images
57 and authenticate an updateable AP firmware image into an executable RAM
65 required to load and authenticate all 3rd level firmware images into their
71 Also known as "SoC AP firmware" or "EL3 monitor firmware". Its primary purpose
107 This is the Realm-EL2 firmware. It is required if
117 and authenticate an updateable SCP firmware image into an executable RAM
119 conjunction with other processor firmware (for example, ``AP_BL1`` and
131 runtime firmware" but it could potentially be an intermediate firmware if the
135 this has always been the 2nd stage firmware. The previous name is too
168 complete the firmware update operation. It is potentially a subset of
[all …]
|
| /arm-trusted-firmware-2.8.0/docs/plat/ |
| A D | synquacer.rst | 18 `link <https://github.com/ARM-software/arm-trusted-firmware>`__
32 SCP firmware --> TF-A BL31 --> UEFI(edk2)
50 export WORKSPACE=$HOME/build/developerbox-firmware
58 git clone https://github.com/ARM-software/arm-trusted-firmware -b master
67 cd $WORKSPACE/arm-trusted-firmware
90 - The firmware image, which comprises the option ROM, ARM trusted firmware and
104 installed then you can adopt your the newly compiled system firmware using
|
| A D | brcm-stingray.rst | 7 Trusted Firmware-A (TF-A) is used to implement secure world firmware, supporting
21 `link <https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/>`__
|
| A D | qemu-sbsa.rst | 4 Trusted Firmware-A (TF-A) implements the EL3 firmware layer for QEMU SBSA
27 git clone https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git tfa
36 git clone https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git tfa
|
| A D | ti-k3.rst | 4 Trusted Firmware-A (TF-A) implements the EL3 firmware layer for Texas Instruments K3 SoCs.
24 https://github.com/ARM-software/arm-trusted-firmware.git
|
| A D | qti.rst | 4 Trusted Firmware-A (TF-A) implements the EL3 firmware layer for QTI SC7180,
21 `link <https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git>`__
|
| A D | qti-msm8916.rst | 11 EL3 firmware. It is primarily based on information from the public
24 The BL31 port is much more minimal compared to the original firmware and
44 BL31 replaces the original ``tz`` firmware in the boot flow::
49 ``0x8f600000``. The original hypervisor firmware (``hyp``) is not used, you can
67 but it provides the firmware with required metadata.
79 Do not flash incorrectly signed firmware on devices that have secure
|
| A D | xilinx-versal.rst | 4 Trusted Firmware-A implements the EL3 firmware layer for Xilinx Versal.
55 further firmware images.
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | mpmm.rst | 11 |MPMM| is enabled on a per-core basis by the EL3 runtime firmware. The presence
12 of |MPMM| cannot be determined at runtime by the firmware, and therefore the
29 runtime firmware - please see :ref:`Activity Monitor Auxiliary Counters` for
|
| A D | index.rst | 14 firmware-update
|
| A D | debugfs-design.rst | 10 The *DebugFS* feature is primarily aimed at exposing firmware debug data to
20 The implementation permits exposing virtual files, firmware drivers, and file blobs.
71 measurements through a file, and internal firmware state counters through
73 - This permits direct access to a firmware driver, mainly for test purposes
105 - Notice, a physical device driver if exposed by the firmware may conflict with
|
| A D | firmware-update.rst | 11 IHI 0093), which defines a standard firmware interface for installing firmware
13 On the other hand, TBBR Firmware Update only covers firmware recovery. Arguably,
28 The new firmware images are provided by the ``Client`` to the ``Update Agent``
34 entity aka ``Client`` to transmit the firmware images to the ``Update Agent``.
49 An active bank stores running firmware, whereas an update bank contains
50 firmware updates.
89 choose firmware recovery mechanism :ref:`TBBR Firmware Update` to bring system
100 This technique enables authenticated firmware to update firmware images from
104 This feature functions even when the current firmware in the system is corrupt
106 complemented by other, higher level firmware update software.
[all …]
|
| /arm-trusted-firmware-2.8.0/ |
| A D | .gitreview | 4 project=TF-A/trusted-firmware-a
|
| /arm-trusted-firmware-2.8.0/plat/arm/board/fvp/fdts/ |
| A D | fvp_fw_config.dts | 29 * Load SoC and TOS firmware configs at the base of
31 * overlap BL2, BL31 or BL32. The NT firmware config
|
| /arm-trusted-firmware-2.8.0/docs/security_advisories/ |
| A D | security-advisory-tfv-2.rst | 58 .. _commit 495f3d3: https://github.com/ARM-software/arm-trusted-firmware/commit/495f3d3
59 .. _AArch64 macro: https://github.com/ARM-software/arm-trusted-firmware/blob/bcc2bf0/include/common…
60 .. _AArch32 equivalent: https://github.com/ARM-software/arm-trusted-firmware/blob/bcc2bf0/include/c…
61 .. _Pull Request #841: https://github.com/ARM-software/arm-trusted-firmware/pull/841
|
| A D | security-advisory-tfv-5.rst | 54 .. _Pull Request #1127: https://github.com/ARM-software/arm-trusted-firmware/pull/1127
55 .. _Commit e290a8fcbc: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=e290a…
56 .. _Commit c3e8b0be9b: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=c3e8b…
|
| A D | security-advisory-tfv-7.rst | 36 new firmware interfaces, for example the `Software Delegated Exception Interface
88 the default mitigation state for firmware-managed execution contexts is enabled.
105 …n vulnerabilities: https://developer.arm.com/cache-speculation-vulnerability-firmware-specification
106 .. _Pull Request #1392: https://github.com/ARM-software/arm-trusted-firmware/pull/1392
107 .. _Pull Request #1397: https://github.com/ARM-software/arm-trusted-firmware/pull/1397
|
| A D | security-advisory-tfv-6.rst | 59 (to execute firmware branch predictor invalidation), then there is a dependency
71 the normal world to discover the presence of this firmware service.
144 .. _Pull Request #1214: https://github.com/ARM-software/arm-trusted-firmware/pull/1214
145 .. _Pull Request #1228: https://github.com/ARM-software/arm-trusted-firmware/pull/1228
146 .. _Pull Request #1240: https://github.com/ARM-software/arm-trusted-firmware/pull/1240
147 .. _Pull Request #1405: https://github.com/ARM-software/arm-trusted-firmware/pull/1405
148 …ion specification: https://developer.arm.com/cache-speculation-vulnerability-firmware-specification
|
| A D | security-advisory-tfv-4.rst | 17 | Affected | firmware update code executing before BL31 |
121 .. _commit c396b73: https://github.com/ARM-software/arm-trusted-firmware/commit/c396b73
122 .. _Pull Request #678: https://github.com/ARM-software/arm-trusted-firmware/pull/678
123 .. _Pull Request #939: https://github.com/ARM-software/arm-trusted-firmware/pull/939
124 .. _Pull Request #979: https://github.com/ARM-software/arm-trusted-firmware/pull/979
|
| /arm-trusted-firmware-2.8.0/docs/design/ |
| A D | index.rst | 11 firmware-design
|
| /arm-trusted-firmware-2.8.0/docs/about/ |
| A D | features.rst | 54 recovery mode), and packaging of the various firmware images into a
69 interrupts to their registered handlers, to facilitate firmware-first
72 - A dynamic configuration framework that enables each of the firmware images
75 as part of the FIP, to be passed through the firmware stages.
76 This feature is now incorporated inside the firmware configuration framework
80 the EL3 Runtime Software is loaded using other firmware or a separate
|
| /arm-trusted-firmware-2.8.0/include/plat/arm/common/ |
| A D | fconf_ethosn_getter.h | 30 struct ethosn_allocator_t firmware; member
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/corstone1000/ |
| A D | index.rst | 14 The board boot relies on CoT (chain of trust). The trusted-firmware-a
23 BL2 performs the actions described in the trusted-firmware-a TBB design
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/tc/ |
| A D | index.rst | 6 - A `System Control Processor <https://github.com/ARM-software/SCP-firmware>`_
8 processors. The RAM firmware for SCP is included in the TF-A FIP and is
|