| /trusted-firmware-a/ |
| 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 …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | realm-management-extension.rst.txt | 10 RME support in TF-A
84 Building and running TF-A with RME
94 for two scenarios: TF-A with TF-A Tests, and four-world execution with
96 TF-A. You can use the following command to clone TF-A.
109 Building TF-A with TF-A Tests
111 Use the following instructions to build TF-A with `TF-A Tests`_ as the
114 **1. Obtain and build TF-A Tests**
124 **2. Build TF-A**
162 **2. Build TF-A**
164 Build TF-A with RME as well as SPM enabled.
[all …]
|
| /trusted-firmware-a/docs/components/ |
| A D | realm-management-extension.rst | 10 RME support in TF-A
84 Building and running TF-A with RME
94 for two scenarios: TF-A with TF-A Tests, and four-world execution with
96 TF-A. You can use the following command to clone TF-A.
109 Building TF-A with TF-A Tests
111 Use the following instructions to build TF-A with `TF-A Tests`_ as the
114 **1. Obtain and build TF-A Tests**
124 **2. Build TF-A**
162 **2. Build TF-A**
164 Build TF-A with RME as well as SPM enabled.
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/ |
| A D | brcm-stingray.rst.txt | 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
|
| A D | xilinx-zynqmp.rst.txt | 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:
44 FSBL->TF-A Parameter Passing
47 The FSBL populates a data structure with image information for TF-A. TF-A uses
50 register is free to be used by other software once TF-A has brought up
56 The following power domain tree represents the power domain model used by TF-A
|
| A D | xilinx-versal.rst.txt | 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 Straight-Line Speculation(SLS)
47 # PLM->TF-A Parameter Passing
49 The PLM populates a data structure with image information for the TF-A. The TF-A
52 The register is free to be used by other software once the TF-A is bringing up
|
| A D | ls1043a.rst.txt | 32 USB 3.0: two super speed USB 3.0 type A ports
42 Bootrom --> TF-A BL1 --> TF-A BL2 --> TF-A BL1 --> TF-A BL31
43 --> BL32(Tee OS) --> TF-A BL31 --> BL33(u-boot) --> Linux kernel
56 - Build TF-A for Nor boot
71 Deploy TF-A Images
74 - Deploy TF-A images on Nor flash Alt Bank.
84 Then change to Alt bank and boot up TF-A:
|
| A D | ti-k3.rst.txt | 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:
|
| A D | qti.rst.txt | 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.
|
| /trusted-firmware-a/docs/plat/ |
| 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
|
| 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:
44 FSBL->TF-A Parameter Passing
47 The FSBL populates a data structure with image information for TF-A. TF-A uses
50 register is free to be used by other software once TF-A has brought up
56 The following power domain tree represents the power domain model used by TF-A
|
| 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 Straight-Line Speculation(SLS)
47 # PLM->TF-A Parameter Passing
49 The PLM populates a data structure with image information for the TF-A. The TF-A
52 The register is free to be used by other software once the TF-A is bringing up
|
| A D | ls1043a.rst | 32 USB 3.0: two super speed USB 3.0 type A ports
42 Bootrom --> TF-A BL1 --> TF-A BL2 --> TF-A BL1 --> TF-A BL31
43 --> BL32(Tee OS) --> TF-A BL31 --> BL33(u-boot) --> Linux kernel
56 - Build TF-A for Nor boot
71 Deploy TF-A Images
74 - Deploy TF-A images on Nor flash Alt Bank.
84 Then change to Alt bank and boot up TF-A:
|
| 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:
|
| A D | qti.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.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/ |
| A D | index.rst.txt | 1 Trusted Firmware-A Documentation
23 Trusted Firmware-A (TF-A) provides a reference implementation of secure world
24 software for `Armv7-A and Armv8-A`_, including a `Secure Monitor`_ executing
35 Where possible, the code is designed for reuse or porting to other Armv7-A and
36 Armv8-A model and hardware platforms.
43 testing, on any secure world code derived from TF-A.
45 In collaboration with interested parties, we will continue to enhance |TF-A|
47 with Armv7-A and Armv8-A TrustZone technology.
52 The |TF-A| documentation contains guidance for obtaining and building the
60 the prerequisites and requirements for building |TF-A|.
[all …]
|
| A D | change-log.md.txt | 311 - **FF-A**
1551 - Armv8.6-A
1830 - Renamed SPCI to FF-A
3747 Armv8.1-A.
4407 TF-A.
4532 TF-A.
4537 - TF-A still uses too much on-chip Trusted SRAM. A number of RAM usage
4653 releases of TF-A.
4660 TF-A.
4704 releases of TF-A.
[all …]
|
| /trusted-firmware-a/docs/ |
| A D | index.rst | 1 Trusted Firmware-A Documentation
23 Trusted Firmware-A (TF-A) provides a reference implementation of secure world
24 software for `Armv7-A and Armv8-A`_, including a `Secure Monitor`_ executing
35 Where possible, the code is designed for reuse or porting to other Armv7-A and
36 Armv8-A model and hardware platforms.
43 testing, on any secure world code derived from TF-A.
45 In collaboration with interested parties, we will continue to enhance |TF-A|
47 with Armv7-A and Armv8-A TrustZone technology.
52 The |TF-A| documentation contains guidance for obtaining and building the
60 the prerequisites and requirements for building |TF-A|.
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/threat_model/ |
| A D | threat_model_spm.rst.txt | 7 This document provides a threat model for the TF-A `Secure Partition Manager`_
11 Arm A-profile`_ specification.
13 In brief, the broad FF-A specification and S-EL2 firmware implementation
16 - Isolation of mutually mistrusting SW components, or endpoints in the FF-A
20 - A standard protocol for communication and memory sharing between FF-A
31 The monitor and SPMD at EL3 are covered by the `Generic TF-A threat model`_.
35 - The TF-A implementation for the S-EL2 SPMC based on the Hafnium hypervisor
39 - The implementation complies with the FF-A v1.0 specification.
108 - Bootloaders (in particular BL1/BL2 if using TF-A) and run-time BL31 are
616 .. _Generic TF-A threat model: ./threat_model.html#threat-analysis
[all …]
|
| A D | threat_model.rst.txt | 7 This document provides a generic threat model for TF-A firmware.
18 Firmware for A-class Processors (TF-A). This includes the boot ROM (BL1),
39 Figure 1 shows a high-level data flow diagram for TF-A. The diagram
41 their interactions with TF-A. A description of each diagram element
44 are considered untrusted by TF-A.
47 :caption: Figure 1: TF-A Data Flow Diagram
49 .. table:: Table 1: TF-A Data Flow Diagram Description
95 We have identified the following assets for TF-A:
97 .. table:: Table 2: TF-A Assets
601 | | `TF-A error handling policy`_. TF-A provides an |
[all …]
|
| /trusted-firmware-a/docs/threat_model/ |
| A D | threat_model_spm.rst | 7 This document provides a threat model for the TF-A `Secure Partition Manager`_
11 Arm A-profile`_ specification.
13 In brief, the broad FF-A specification and S-EL2 firmware implementation
16 - Isolation of mutually mistrusting SW components, or endpoints in the FF-A
20 - A standard protocol for communication and memory sharing between FF-A
31 The monitor and SPMD at EL3 are covered by the `Generic TF-A threat model`_.
35 - The TF-A implementation for the S-EL2 SPMC based on the Hafnium hypervisor
39 - The implementation complies with the FF-A v1.0 specification.
108 - Bootloaders (in particular BL1/BL2 if using TF-A) and run-time BL31 are
616 .. _Generic TF-A threat model: ./threat_model.html#threat-analysis
[all …]
|
| A D | threat_model.rst | 7 This document provides a generic threat model for TF-A firmware.
18 Firmware for A-class Processors (TF-A). This includes the boot ROM (BL1),
39 Figure 1 shows a high-level data flow diagram for TF-A. The diagram
41 their interactions with TF-A. A description of each diagram element
44 are considered untrusted by TF-A.
47 :caption: Figure 1: TF-A Data Flow Diagram
49 .. table:: Table 1: TF-A Data Flow Diagram Description
95 We have identified the following assets for TF-A:
97 .. table:: Table 2: TF-A Assets
601 | | `TF-A error handling policy`_. TF-A provides an |
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/about/ |
| A D | contact.rst.txt | 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.
41 TF-A.
50 .. _`TF-A development`: https://lists.trustedfirmware.org/pipermail/tf-a/
51 .. _`TF-A-Tests development`: https://lists.trustedfirmware.org/pipermail/tf-a-tests/
|
| /trusted-firmware-a/docs/about/ |
| 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.
41 TF-A.
50 .. _`TF-A development`: https://lists.trustedfirmware.org/pipermail/tf-a/
51 .. _`TF-A-Tests development`: https://lists.trustedfirmware.org/pipermail/tf-a-tests/
|
| /trusted-firmware-a/docs/build/TF-A_2.5/ |
| A D | objects.inv | 2 # Project: Trusted Firmware-A
11 �r'B�g&w4��O����77�)�,Q)�,o����*��� ��^�H�3&*�F b�~! |j%t�0c�${f�A�TE�.�ױiJ��HOQ���:�2 g���O…
16 &WX<��$x�I�ؔĘ���pӅP!]P��Iۓ.M�A���5���"A�$��C�F%̘���� ���}�2H��u�Y�(FV�$#9a�#(����������[…
25 …�h!wdˈd�kËnߜ"=�㆗�n��fp��Ɣa��n9�Ǻx V� mӓQ�bϔ��ٝ���[-��3�1���n���\-a#��h��:;�6e���A�v�֓��
31 …��0]E�-T�(HRA�|B�$s��d��A=�Y��=&�Z�Y�ċ��L��"ħC���~����2� 8X%m..�?�Y��ظpV&��{�D�^�*�A�w�…
36 …������K��a�G�|<p,�2�D��$��M;�4�h�a cZ����+vb.�a�*Z��)�� ��O]��Ps���A#V��5$���Ժ(���"�mж…
41 ��*����"�� �!A�������K� ��!S1�s[�`("�6�2������J����t��U{/f��pr)���u��K �Z#v
49 &r��:�F����"�~ht�`�Ԗ���&}A����&�h �9���jQ�"+B���H�=ʻ�l* q!2�GS��A��a<��V�V3��s���4�3
56 �3V� �ݐi35A'm�S�t~j�d�:�)�����NOX P�k�Q�j�(�&61�� �oY����$Iy�����fDM��X�d@�_������aو�*…
63 …���h�|+[����w�N�3��^��x�-�-G��gn�;�to��)�����$�.�l�*c��I�D��q�z]��k Y����A����ӡ+s��%�l6�mT��z…
|