| /rk3399_ARM-atf/docs/ |
| H A D | change-log.md | 6 ## [2.14.0](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/refs/tags/…
18 …55b519](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/c55b519ed8799…
26 …b9fc8c](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/bb9fc8c0bbf5f…
35 …ff7523](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/3ff7523883adb…
41 …5d0740](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/b5d0740e14f42…
51 …67e984](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/b67e984664a86…
61 …daebef](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/8daebefe59e51…
69 …515b43](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/8515b4395e62c…
70 …274b52](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/4274b5265576c…
71 …396aec](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/f396aec85ac52…
[all …]
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | threat_model_fw_update_and_recovery.rst | 7 This document provides a threat model of TF-A firmware for platforms with
8 the feature PSA firmware update or TBBR firmware update or both enabled.
9 To understand the design of the firmware update refer
21 is enabled. This includes the boot ROM (BL1), the trusted boot firmware (BL2).
45 | | | vulnerable/older firmware. |
64 1. The FWU metadata includes the firmware bank for booting; the attacker
65 tries to modify it to prevent the execution of the updated firmware.
66 2. The FWU metadata features a field indicating the firmware's status, either
68 ensuring the updated firmware consistently runs in trial mode, with the
94 | | | vulnerable/older firmware. |
|
| H A D | threat_model_rse_interface.rst | 16 the AP core. The threat model for the RSE firmware will be provided by the RSE
17 firmware project in the future.
48 allowed only for firmware running at EL3. Accidentally exposing this
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | image-terminology.rst | 33 Clearly, many of these images are not BootLoaders, they are simply firmware
46 This is a packaging format used by TF-A to package firmware images in a single
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
63 This is the 2nd stage AP firmware. It is currently also known as the "Trusted
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
[all …]
|
| /rk3399_ARM-atf/docs/plat/ |
| H 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
|
| H 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
|
| H 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/>`__
|
| H A D | rpi5.rst | 24 The firmware will be generated at ``build/rpi5/debug/bl31.bin``.
29 kernel from the firmware.
46 Copy the firmware binary to the first FAT32 partition of a supported boot media
50 No other config options or files are required by the firmware alone, this will
|
| H 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
|
| H A D | xilinx-versal-net.rst | 4 Trusted Firmware-A implements the EL3 firmware layer for Xilinx Versal NET.
51 firmware. Options:
99 | | Management APIs to firmware …
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | trusted-board-boot.rst | 4 The `Trusted Board Boot` (TBB) feature prevents malicious firmware from running
5 on the platform by authenticating all firmware images up to and including the
23 - The set of firmware images in use on this platform.
24 Typically, most platforms share a common set of firmware images (BL1, BL2,
79 In the TBBR CoT, all firmware binaries and certificates are (directly or
88 The private part of this key is used to sign the trusted boot firmware
120 - **Trusted boot firmware certificate**
123 the BL2 image and hashes of various firmware configuration files
132 - **SCP firmware key certificate**
137 - **SCP firmware content certificate**
[all …]
|
| H A D | index.rst | 11 firmware-design
|
| /rk3399_ARM-atf/docs/about/ |
| H A D | features.rst | 62 Firmware encryption and packaging of the various firmware images into a
65 - Measured boot support with PoC to showcase its interaction with firmware TPM
70 - Following firmware update mechanisms available:
85 interrupts to their registered handlers, to facilitate firmware-first
88 - A dynamic configuration framework that enables each of the firmware images
91 as part of the FIP, to be passed through the firmware stages.
92 This feature is now incorporated inside the firmware configuration framework
96 the EL3 Runtime Software is loaded using other firmware or a separate
100 - Support for Errata management firmware interface.
|
| /rk3399_ARM-atf/plat/arm/board/morello/fdts/ |
| H A D | morello_nt_fw_config.dts | 28 * Placeholder for firmware-version node with default values.
32 firmware-version {
|
| /rk3399_ARM-atf/docs/plat/arm/morello/ |
| H A D | index.rst | 5 The platform port present at `site <https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git>`_
18 firmware image (the FIP image) from the AP QSPI NOR Flash Memory into the
24 firmware. Execution is finally handed off to AP_BL33, which is the non-secure
|
| /rk3399_ARM-atf/docs/plat/qti/ |
| H A D | msm8916.rst | 22 It provides a minimal, community-maintained EL3 firmware and PSCI implementation,
34 The TF-A port is much more minimal compared to the original firmware and
54 BL31 (AArch64) or BL32/SP_MIN (AArch32) replaces the original ``tz`` firmware
61 the normal world bootloader was already loaded into RAM by a previous firmware
97 reports. This must be the same UART as used by earlier boot firmware since
105 The memory region used for the different firmware components is not fixed and
107 used by the original firmware (see ``platform.mk``):
111 * ``BL31_BASE``: Base address for the BL31 firmware component. Must point to
114 * ``BL32_BASE``: Base address for the BL32 firmware component.
126 but it provides the firmware with required metadata.
[all …]
|
| /rk3399_ARM-atf/ |
| H A D | .gitreview | 4 project=TF-A/trusted-firmware-a
|
| /rk3399_ARM-atf/docs/security_advisories/ |
| H 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
|
| H 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…
|
| H A D | security-advisory-tfv-7.rst | 38 new firmware interfaces, for example the `Software Delegated Exception Interface
90 the default mitigation state for firmware-managed execution contexts is enabled.
107 …n vulnerabilities: https://developer.arm.com/cache-speculation-vulnerability-firmware-specification
108 .. _Pull Request #1392: https://github.com/ARM-software/arm-trusted-firmware/pull/1392
109 .. _Pull Request #1397: https://github.com/ARM-software/arm-trusted-firmware/pull/1397
|
| /rk3399_ARM-atf/plat/arm/board/fvp/fdts/ |
| H A D | fvp_fw_config.dts | 34 * Load SoC and TOS firmware configs at the base of
36 * overlap BL2, BL31 or BL32. The NT firmware config
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | mpmm.rst | 11 |MPMM| is enabled on a per-core basis by the EL3 runtime firmware.
20 runtime firmware - please see :ref:`Activity Monitor Auxiliary Counters` for
|
| H 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
|
| /rk3399_ARM-atf/docs/plat/arm/automotive_rd/ |
| H A D | rdaspen.rst | 20 Once loaded, the RSE signals the System Control Processor firmware (SCP-firmware)
23 The SCP-firmware then sets the reset vector base address (RVBAR) for the AP, ensuring
24 it starts executing BL2 from the designated address. Following this, the SCP-firmware
52 * (If present) Reads and loads the SPMC manifest (for S-EL2 firmware configuration)
|
| /rk3399_ARM-atf/docs/plat/arm/corstone1000/ |
| H 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
|