| /rk3399_ARM-atf/docs/ |
| H A D | change-log.md | 4 issues in each release of Trusted Firmware-A.
6 ## [2.14.0](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/refs/tags/…
18 …ent offset ([c55b519](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+…
21 depending on the FF-A version of the source and destination.
26 …or FFA 1.2 ([bb9fc8c](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+…
35 …ementation ([3ff7523](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+…
37 - LibTL is now included in TF-A as a submodule.
39 issues after migrating to the latest version of TF-A.
41 … submodule ([b5d0740](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+…
47 - LibEventLog is now included in TF-A as a submodule.
[all …]
|
| H A D | index.rst | 1 Trusted Firmware-A Documentation
26 Trusted Firmware-A (TF-A) provides a reference implementation of secure world
27 software for `Armv7-A and Armv8-A`_, including a `Secure Monitor`_ executing
38 Where possible, the code is designed for reuse or porting to other Armv7-A and
39 Armv8-A model and hardware platforms.
46 testing, on any secure world code derived from TF-A.
48 In collaboration with interested parties, we will continue to enhance |TF-A|
50 with Armv7-A and Armv8-A TrustZone technology.
55 The |TF-A| documentation contains guidance for obtaining and building the
59 The **About** chapter gives a high-level overview of |TF-A| features as well as
[all …]
|
| H A D | glossary.rst | 4 This glossary provides definitions for terms and abbreviations used in the TF-A
43 Common Vulnerabilities and Exposures. A CVE document is commonly used to
91 FF-A
92 Firmware Framework for Arm A-profile
119 A collaborative engineering organization consolidating
123 A logical secure partition managed by SPM
133 supported by some Arm Armv9-A cores.
176 Reliability, Availability, and Serviceability extensions. A mandatory
252 TF-A
253 Trusted Firmware-A
[all …]
|
| /rk3399_ARM-atf/ |
| H A D | readme.rst | 1 Trusted Firmware-A
4 Trusted Firmware-A (TF-A) is a reference implementation of secure world software
5 for `Arm A-Profile architectures`_ (Armv8-A and Armv7-A), including an Exception
10 TF-A implements Arm interface standards, including:
19 software models that are based on the Armv8-A and Armv7-A architectures.
21 In collaboration with interested parties, we will continue to enhance TF-A
23 with Armv7-A and Armv8-A TrustZone technology.
26 testing, on any secure world code derived from TF-A.
31 To find out more about Trusted Firmware-A, please `view the full documentation`_
38 .. _Armv7-A and Armv8-A: https://developer.arm.com/products/architecture/a-profile
[all …]
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | brcm-stingray.rst | 7 Trusted Firmware-A (TF-A) is used to implement secure world firmware, supporting
16 Bootrom --> TF-A BL2 --> TF-A BL31 --> BL33(u-boot)
20 - Trusted Firmware-A:
21 `link <https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/>`__
33 - Build TF-A
41 Deploy TF-A Images
|
| H A D | xilinx-versal.rst | 4 Trusted Firmware-A implements the EL3 firmware layer for Xilinx Versal.
5 The platform only uses the runtime part of TF-A as Xilinx Versal already has a
8 BL31 is TF-A.
22 To build TF-A for JTAG DCC console
27 To build TF-A with Errata management interface
32 To build TF-A with Straight-Line Speculation(SLS)
65 The stack size in TF-A for the Versal platform is configurable.
87 TF-A build, its definition of ``custom_smc_handler`` is enabled.
89 Custom Package Makefile Fragment Inclusion in TF-A Build
92 - Custom package is not directly part of the TF-A source.
[all …]
|
| H A D | xilinx-zynqmp.rst | 4 Trusted Firmware-A (TF-A) implements the EL3 firmware layer for Xilinx Zynq
6 The platform only uses the runtime part of TF-A as ZynqMP already has a
9 BL31 is TF-A.
25 To build TF-A for JTAG DCC console:
48 With DEBUG=1, TF-A for ZynqMP uses DDR memory range instead of OCM memory range
70 range OR let TF-A modify the device tree on the run.
72 To let TF-A access and modify the device tree, the DTB address must be provided
82 When FSBL runs on RPU and TF-A is to be placed in DDR address range,
86 For this use case, with the minimum base address in DDR for TF-A,
95 The stack size in TF-A for ZynqMP platform is configurable.
[all …]
|
| H A D | ti-k3.rst | 4 Trusted Firmware-A (TF-A) implements the EL3 firmware layer for Texas Instruments K3 SoCs.
11 R5(U-Boot) --> TF-A BL31 --> BL32(OP-TEE) --> TF-A BL31 --> BL33(U-Boot) --> Linux
19 BL2 TF-A stages.
26 TF-A:
|
| H A D | amd-versal2.rst | 4 Trusted Firmware-A implements the EL3 firmware layer for AMD Versal Gen 2.
5 The platform only uses the runtime part of TF-A as AMD Versal Gen 2 already
8 BL31 is TF-A.
17 To build TF-A for JTAG DCC console:
22 To build TF-A with Errata management interface
27 To build TF-A with IPI CRC check:
48 The stack size in TF-A for the Versal platform is configurable.
70 TF-A build, its definition of ``custom_smc_handler`` is enabled.
72 Custom Package Makefile Fragment Inclusion in TF-A Build
75 - Custom package is not directly part of the TF-A source.
[all …]
|
| H A D | qemu-sbsa.rst | 4 Trusted Firmware-A (TF-A) implements the EL3 firmware layer for QEMU SBSA
5 Armv8-A. While running Qemu from command line, we need to supply two Flash
23 To build TF-A:
27 git clone https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git tfa
32 To build TF-A with BL32 and SPM enabled(StandaloneMM as a Secure Payload):
36 git clone https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git tfa
|
| /rk3399_ARM-atf/docs/about/ |
| H A D | contact.rst | 4 We welcome any feedback on |TF-A| and there are several methods for providing
14 Public mailing lists for TF-A and the wider Trusted Firmware project are
20 The relevant lists for the TF-A project are:
22 - `TF-A development`_
23 - `TF-A-Tests development`_
30 Every other week, we organize a call with all interested TF-A contributors.
40 gives everyone visibility of the known issues in TF-A.
48 .. _`issue tracker`: https://github.com/TrustedFirmware-A/trusted-firmware-a/issues
49 .. _`TF-A development`: https://lists.trustedfirmware.org/mailman3/lists/tf-a.lists.trustedfirmware…
50 .. _`TF-A-Tests development`: https://lists.trustedfirmware.org/mailman3/lists/tf-a-tests.lists.tru…
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | threat_model_el3_spm.rst | 7 This document provides a threat model for the TF-A :ref:`EL3 Secure Partition Manager`
9 `Arm Firmware Framework for Arm A-profile`_ specification.
16 The monitor and SPMD at EL3 are covered by the :ref:`Generic TF-A threat model
21 - The TF-A implementation for the EL3 SPMC
22 - The implementation complies with the FF-A v1.1 specification.
35 A description of each diagram element is given in Table 1. In the diagram, the
48 | DF1 | SP to SPMC communication. FF-A function invocation or |
74 This threat model follows a similar methodology to the :ref:`Generic TF-A threat model
88 - Bootloaders (in particular BL1/BL2 if using TF-A) and run-time BL31 are
119 The following threat categories as exposed in the :ref:`Generic TF-A threat model
[all …]
|
| H A D | threat_model.rst | 8 This document provides a generic threat model for TF-A firmware.
17 Firmware for A-class Processors (TF-A). This includes the boot ROM (BL1),
22 TF-A can be configured in various ways. In this threat model we consider
26 - All TF-A images are run from either ROM or on-chip trusted SRAM. This means
27 TF-A is not vulnerable to an attacker that can probe or tamper with off-chip
39 The :ref:`Threat Model for TF-A with Arm CCA support` covers these types of
51 Figure 1 shows a high-level data flow diagram for TF-A. The diagram
52 shows a model of the different components of a TF-A-based system and
53 their interactions with TF-A. A description of each diagram element
56 are considered untrusted by TF-A.
[all …]
|
| H A D | threat_model_rse_interface.rst | 7 This document is an extension for the general TF-A threat-model. It considers
15 AP. Otherwise, the TF-A :ref:`Generic Threat Model` document is applicable for
22 This diagram is different only from the general TF-A data flow diagram in that
25 is the same as in the general TF-A threat-model document.
28 :caption: Figure 1: TF-A Data Flow Diagram including RSE
30 .. table:: Table 1: TF-A - RSE data flow diagram
43 For this section, please reference the Threat Assessment under the general TF-A
|
| H A D | threat_model_firmware_handoff.rst | 7 This document provides a threat model of TF-A firmware for platforms that make
16 by A class firmware components. It is used to transfer state/metadata (e.g.,
17 Device Trees, entrypoint information) between boot stages in TF-A. This includes
24 The following assumptions are made about the TF-A Firmware Handoff framework
25 implementation in TF-A:
38 From a system perspective, we re-use the :ref:`Generic TF-A threat model
39 <tfa_dfd>` Data Flow Diagram (DFD). A generalized DFD showing information flow
41 diagram is representative of dataflows in TF-A where Firmware Handoff might be
47 .. table:: Table 1: TF-A Data Flow Diagram Description
61 This analysis follows the same methodology as the :ref:`Generic TF-A threat
[all …]
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | realm-management-extension.rst | 5 FEAT_RME (or RME for short) is an Armv9-A extension and is one component of the
6 `Arm Confidential Compute Architecture (Arm CCA)`_. TF-A supports RME starting
7 from version 2.6. This chapter discusses the changes to TF-A to support RME and
8 provides instructions on how to build and run TF-A with RME.
10 RME support in TF-A
13 The following diagram shows an Arm CCA software architecture with TF-A as the
15 states and address spaces: ``Root`` and ``Realm``. TF-A firmware runs in the
22 changes have been introduced to TF-A. We discuss those changes below.
38 A new CPU context for the Realm world has been added. The existing can be used
43 In a typical TF-A boot flow, BL2 runs at Secure-EL1. However when RME is
[all …]
|
| H A D | secure-partition-manager.rst | 15 | FF-A | Firmware Framework for Arm A-profile |
35 Three implementations of a Secure Partition Manager co-exist in the TF-A
38 #. S-EL2 SPMC based on the FF-A specification `[1]`_, enabling virtualization in
40 #. EL3 SPMC based on the FF-A specification, managing a single S-EL1 partition
52 SPMC) residing at different exception levels. To permit the FF-A specification
56 - The SPMD is located at EL3 and mainly relays the FF-A protocol from NWd
61 TF-A supports both cases:
64 extension. The SPMD relays the FF-A protocol from EL3 to S-EL1.
66 extension. The SPMD relays the FF-A protocol from EL3 to S-EL2.
68 TF-A build options
[all …]
|
| H A D | activity-monitors.rst | 4 FEAT_AMUv1 of the Armv8-A architecture introduces the Activity Monitors
9 When the ``ENABLE_FEAT_AMU=1`` build option is provided, Trusted Firmware-A
22 As a security precaution, Trusted Firmware-A does not enable these by default.
25 ``plat_my_core_pos()``. A core's value will be written verbatim into
|
| H A D | el3-spmc.rst | 9 This document describes the design of the EL3 SPMC based on the FF-A specification.
10 EL3 SPMC provides reference FF-A compliant implementation without S-EL2 virtualization support,
11 to help adopt and migrate to FF-A early.
12 EL3 SPMC implementation in TF-A:
15 - Provides a standard protocol for communication and memory sharing between FF-A endpoints.
28 TF-A build options
31 This section explains the TF-A build options involved in building
32 an FF-A based SPM where the SPMD and SPMC are located at EL3:
34 - **SPD=spmd**: this option selects the SPMD component to relay the FF-A
47 BL32 option can be omitted if using TF-A Test Secure Payload as SP.
[all …]
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | maintenance.rst | 4 Trusted Firmware-A (TF-A) project follows the generic `trustedfirmware.org
6 TF-A project-specific decisions.
14 To be elligible to become a maintainer for TF-A project, all criteria outlined
32 TF-A tech forums calls.
41 #. Send an email to all existing TF-A maintainers, asking whether they have any
42 objections to this individual becoming a TF-A maintainer.
50 #. If there are no (more) objections, announce the news on the TF-A mailing list
|
| H A D | security.rst | 8 relevant to Trusted Firmware-A. We encourage responsible disclosure of
11 We disclose TF-A vulnerabilities as Security Advisories, all of which are listed
13 TF-A project's `mailing list`_.
18 Although we try to keep TF-A secure, we can only do so with the help of the
27 TF-A have a chance to consider the implications of the vulnerability and its
31 Afterwards, we encourage you to write-up your findings about the TF-A source
61 | |TFV-6| | Trusted Firmware-A exposure to speculative processor |
64 | |TFV-7| | Trusted Firmware-A exposure to cache speculation vulnerability |
70 | |TFV-9| | Trusted Firmware-A exposure to speculative processor |
76 | |TFV-11| | A Malformed SDEI SMC can cause out of bound memory read |
[all …]
|
| /rk3399_ARM-atf/docs/plat/qti/ |
| H A D | chrome.rst | 4 Trusted Firmware-A (TF-A) implements the EL3 firmware layer for QTI SC7180,
20 - Trusted Firmware-A:
21 `link <https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git>`__
26 QTI SoC expects TF-A's BL31 to get integrated with other boot software
27 Coreboot, so only bl31.elf need to get build from the TF-A repository.
|
| /rk3399_ARM-atf/docs/components/spd/ |
| H A D | pnc-dispatcher.rst | 5 to work with Trusted Firmware-A (TF-A).
7 ProvenCore is a secure OS developed by ProvenRun S.A.S. using deductive formal methods.
|
| /rk3399_ARM-atf/docs/plat/arm/tc/ |
| H A D | index.rst | 4 Some of the features of TC platform referenced in TF-A include:
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
16 The TF-A build is specified by the option `TARGET_PLATFORM` which represents
29 RAM and starts executing it. The AP then continues executing the rest of TF-A
33 Build Procedure (TF-A only)
39 - Build TF-A:
|
| /rk3399_ARM-atf/docs/threat_model/ |
| H A D | supply_chain_threat_model.rst | 1 TF-A Supply Chain Threat Model
26 TF-A project.
28 TF-A Overview
31 Figure 1 shows the different software components surrounding the TF-A project.
32 A brief description of each component is provided below.
34 TF-A Repository
37 The TF-A repository contains generic and platform code contributed by TF-A
52 The TF-A repository also includes source code for host tools that supplement
53 the TF-A build process. These tools include:
57 loaded by TF-A from non-volatile platform storage.
[all …]
|