blob: 8eecb3ca60fe9da8bbe5493c33a0bae498129750 [file] [log] [blame]
Paul Beesleyea225122019-02-11 17:54:45 +00001Trusted Firmware-A Documentation
2================================
Paul Beesley22994f72019-01-23 15:39:39 +00003
4.. toctree::
5 :maxdepth: 1
Paul Beesleyea225122019-02-11 17:54:45 +00006 :caption: Contents
Paul Beesley22994f72019-01-23 15:39:39 +00007
Paul Beesleycb238022019-03-07 15:25:14 +00008 Home<self>
Paul Beesleyea225122019-02-11 17:54:45 +00009 getting_started/index
10 process/index
11 components/index
12 design/index
13 plat/index
14 perf/index
15 security_advisories/index
Paul Beesley22994f72019-01-23 15:39:39 +000016 change-log
Paul Beesleyea225122019-02-11 17:54:45 +000017 maintainers
18 acknowledgements
Paul Beesleycb238022019-03-07 15:25:14 +000019 license
Paul Beesley22994f72019-01-23 15:39:39 +000020
Paul Beesleycb238022019-03-07 15:25:14 +000021Trusted Firmware-A (TF-A) provides a reference implementation of secure world
22software for `Armv7-A and Armv8-A`_, including a `Secure Monitor`_ executing
23at Exception Level 3 (EL3). It implements various Arm interface standards,
24such as:
25
26- The `Power State Coordination Interface (PSCI)`_
27- `Trusted Board Boot Requirements CLIENT (TBBR-CLIENT)`_
28- `SMC Calling Convention`_
29- `System Control and Management Interface (SCMI)`_
30- `Software Delegated Exception Interface (SDEI)`_
31
32Where possible, the code is designed for reuse or porting to other Armv7-A and
33Armv8-A model and hardware platforms.
34
35This release provides a suitable starting point for productization of secure
36world boot and runtime firmware, in either the AArch32 or AArch64 execution
37states.
38
39Users are encouraged to do their own security validation, including penetration
40testing, on any secure world code derived from TF-A.
41
42Arm will continue development in collaboration with interested parties to
43provide a full reference implementation of Secure Monitor code and Arm standards
44to the benefit of all developers working with Armv7-A and Armv8-A TrustZone
45technology.
46
47Functionality
48-------------
49
50- Initialization of the secure world, for example exception vectors, control
51 registers and interrupts for the platform.
52
53- Library support for CPU specific reset and power down sequences. This
54 includes support for errata workarounds and the latest Arm DynamIQ CPUs.
55
56- Drivers to enable standard initialization of Arm System IP, for example
57 Generic Interrupt Controller (GIC), Cache Coherent Interconnect (CCI),
58 Cache Coherent Network (CCN), Network Interconnect (NIC) and TrustZone
59 Controller (TZC).
60
61- A generic `SCMI`_ driver to interface with conforming power controllers, for
62 example the Arm System Control Processor (SCP).
63
64- SMC (Secure Monitor Call) handling, conforming to the `SMC Calling
65 Convention`_ using an EL3 runtime services framework.
66
67- `PSCI`_ library support for CPU, cluster and system power management
68 use-cases.
69 This library is pre-integrated with the AArch64 EL3 Runtime Software, and
70 is also suitable for integration with other AArch32 EL3 Runtime Software,
71 for example an AArch32 Secure OS.
72
73- A minimal AArch32 Secure Payload (SP\_MIN) to demonstrate `PSCI`_ library
74 integration with AArch32 EL3 Runtime Software.
75
76- Secure Monitor library code such as world switching, EL1 context management
77 and interrupt routing.
78 When a Secure-EL1 Payload (SP) is present, for example a Secure OS, the
79 AArch64 EL3 Runtime Software must be integrated with a Secure Payload
80 Dispatcher (SPD) component to customize the interaction with the SP.
81
82- A Test SP and SPD to demonstrate AArch64 Secure Monitor functionality and SP
83 interaction with PSCI.
84
85- SPDs for the `OP-TEE Secure OS`_, `NVIDIA Trusted Little Kernel`_
86 and `Trusty Secure OS`_.
87
88- A Trusted Board Boot implementation, conforming to all mandatory TBBR
89 requirements. This includes image authentication, Firmware Update (or
90 recovery mode), and packaging of the various firmware images into a
91 Firmware Image Package (FIP).
92
93- Pre-integration of TBB with the Arm CryptoCell product, to take advantage of
94 its hardware Root of Trust and crypto acceleration services.
95
96- Reliability, Availability, and Serviceability (RAS) functionality, including
97
98 - A Secure Partition Manager (SPM) to manage Secure Partitions in
99 Secure-EL0, which can be used to implement simple management and
100 security services.
101
102 - An SDEI dispatcher to route interrupt-based SDEI events.
103
104 - An Exception Handling Framework (EHF) that allows dispatching of EL3
105 interrupts to their registered handlers, to facilitate firmware-first
106 error handling.
107
108- A dynamic configuration framework that enables each of the firmware images
109 to be configured at runtime if required by the platform. It also enables
110 loading of a hardware configuration (for example, a kernel device tree)
111 as part of the FIP, to be passed through the firmware stages.
112
113- Support for alternative boot flows, for example to support platforms where
114 the EL3 Runtime Software is loaded using other firmware or a separate
115 secure system processor, or where a non-TF-A ROM expects BL2 to be loaded
116 at EL3.
117
118- Support for the GCC, LLVM and Arm Compiler 6 toolchains.
119
120- Support for combining several libraries into a "romlib" image that may be
121 shared across images to reduce memory footprint. The romlib image is stored
122 in ROM but is accessed through a jump-table that may be stored
123 in read-write memory, allowing for the library code to be patched.
124
125- A prototype implementation of a Secure Partition Manager (SPM) that is based
126 on the SPCI Alpha 1 and SPRT draft specifications.
127
128- Support for ARMv8.3 pointer authentication in the normal and secure worlds.
129 The use of pointer authentication in the normal world is enabled whenever
130 architectural support is available, without the need for additional build
131 flags. Use of pointer authentication in the secure world remains an
132 experimental configuration at this time and requires the ``ENABLE_PAUTH``
133 build flag to be set.
134
135- Position-Independent Executable (PIE) support. Initially for BL31 only, with
136 further support to be added in a future release.
137
138For a full description of functionality and implementation details, please
139see the `Firmware Design`_ and supporting documentation. The `Change Log`_
140provides details of changes made since the last release.
141
142Platforms
143---------
144
145Various AArch32 and AArch64 builds of this release have been tested on r0, r1
146and r2 variants of the `Juno Arm Development Platform`_.
147
148The latest version of the AArch64 build of TF-A has been tested on the following
149Arm FVPs without shifted affinities, and that do not support threaded CPU cores
150(64-bit host machine only).
151
152The FVP models used are Version 11.5 Build 33, unless otherwise stated.
153
154- ``FVP_Base_AEMv8A-AEMv8A``
155- ``FVP_Base_AEMv8A-AEMv8A-AEMv8A-AEMv8A-CCN502``
156- ``FVP_Base_RevC-2xAEMv8A``
157- ``FVP_Base_Cortex-A32x4``
158- ``FVP_Base_Cortex-A35x4``
159- ``FVP_Base_Cortex-A53x4``
160- ``FVP_Base_Cortex-A55x4+Cortex-A75x4``
161- ``FVP_Base_Cortex-A55x4``
162- ``FVP_Base_Cortex-A57x1-A53x1``
163- ``FVP_Base_Cortex-A57x2-A53x4``
164- ``FVP_Base_Cortex-A57x4-A53x4``
165- ``FVP_Base_Cortex-A57x4``
166- ``FVP_Base_Cortex-A72x4-A53x4``
167- ``FVP_Base_Cortex-A72x4``
168- ``FVP_Base_Cortex-A73x4-A53x4``
169- ``FVP_Base_Cortex-A73x4``
170- ``FVP_Base_Cortex-A75x4``
171- ``FVP_Base_Cortex-A76x4``
172- ``FVP_Base_Cortex-A76AEx4`` (Tested with internal model)
173- ``FVP_Base_Cortex-A76AEx8`` (Tested with internal model)
174- ``FVP_Base_Neoverse-N1x4`` (Tested with internal model)
175- ``FVP_Base_Deimos``
176- ``FVP_CSS_SGI-575`` (Version 11.3 build 42)
177- ``FVP_CSS_SGM-775`` (Version 11.3 build 42)
178- ``FVP_RD_E1Edge`` (Version 11.3 build 42)
179- ``FVP_RD_N1Edge`` (Version 11.3 build 42)
180- ``Foundation_Platform``
181
182The latest version of the AArch32 build of TF-A has been tested on the following
183Arm FVPs without shifted affinities, and that do not support threaded CPU cores
184(64-bit host machine only).
185
186- ``FVP_Base_AEMv8A-AEMv8A``
187- ``FVP_Base_Cortex-A32x4``
188
189NOTE: The ``FVP_Base_RevC-2xAEMv8A`` FVP only supports shifted affinities.
190
191The Foundation FVP can be downloaded free of charge. The Base FVPs can be
192licensed from Arm. See the `Arm FVP website`_.
193
194All the above platforms have been tested with `Linaro Release 18.04`_.
195
196This release also contains the following platform support:
197
198- Allwinner sun50i_a64 and sun50i_h6
199- Amlogic Meson S905 (GXBB)
200- Arm Juno Software Development Platform
201- Arm Neoverse N1 System Development Platform (N1SDP)
202- Arm Neoverse Reference Design N1 Edge (RD-N1-Edge) FVP
203- Arm Neoverse Reference Design E1 Edge (RD-E1-Edge) FVP
204- Arm SGI-575 and SGM-775
205- Arm Versatile Express FVP
206- HiKey, HiKey960 and Poplar boards
207- Intel Stratix 10 SoC FPGA
208- Marvell Armada 3700 and 8K
209- MediaTek MT6795 and MT8173 SoCs
210- NVIDIA T132, T186 and T210 SoCs
211- NXP QorIQ LS1043A, i.MX8MM, i.MX8MQ, i.MX8QX, i.MX8QM and i.MX7Solo WaRP7
212- QEMU
213- Raspberry Pi 3
214- Renesas R-Car Generation 3
215- RockChip RK3328, RK3368 and RK3399 SoCs
216- Socionext UniPhier SoC family and SynQuacer SC2A11 SoCs
217- STMicroelectronics STM32MP1
218- Texas Instruments K3 SoCs
219- Xilinx Versal and Zynq UltraScale + MPSoC
220
221Still to come
222-------------
223
224- Support for additional platforms.
225
226- Refinements to Position Independent Executable (PIE) support.
227
228- Refinements to the SPCI-based SPM implementation as the draft SPCI and SPRT
229 specifications continue to evolve.
230
231- Documentation enhancements.
232
233- Ongoing support for new architectural features, CPUs and System IP.
234
235- Ongoing support for new Arm system architecture specifications.
236
237- Ongoing security hardening, optimization and quality improvements.
238
239For a full list of detailed issues in the current code, please see the `Change
240Log`_ and the `issue tracker`_.
241
242Getting started
243---------------
244
245See the `User Guide`_ for instructions on how to download, install, build and
246use TF-A with the Arm `FVP`_\ s.
247
248See the `Firmware Design`_ for information on how TF-A works.
249
250See the `Porting Guide`_ as well for information about how to use this
251software on another Armv7-A or Armv8-A platform.
252
253See the `Contributing Guidelines`_ for information on how to contribute to this
254project and the `Acknowledgments`_ file for a list of contributors to the
255project.
256
257IRC channel
258~~~~~~~~~~~
259
260Development discussion takes place on the #trusted-firmware-a channel
261on the Freenode IRC network. This is not an official support channel.
262If you have an issue to raise, please use the `issue tracker`_.
263
264Feedback and support
265~~~~~~~~~~~~~~~~~~~~
266
267Arm welcomes any feedback on TF-A. If you think you have found a security
268vulnerability, please report this using the process defined in the TF-A
269`Security Center`_. For all other feedback, please use the
270`issue tracker`_.
271
272Arm licensees may contact Arm directly via their partner managers.
273
274--------------
275
276*Copyright (c) 2013-2019, Arm Limited and Contributors. All rights reserved.*
Paul Beesley22994f72019-01-23 15:39:39 +0000277
Paul Beesleycb238022019-03-07 15:25:14 +0000278.. _Armv7-A and Armv8-A: https://developer.arm.com/products/architecture/a-profile
279.. _Secure Monitor: http://www.arm.com/products/processors/technologies/trustzone/tee-smc.php
280.. _Power State Coordination Interface (PSCI): PSCI_
281.. _PSCI: http://infocenter.arm.com/help/topic/com.arm.doc.den0022d/Power_State_Coordination_Interface_PDD_v1_1_DEN0022D.pdf
282.. _Trusted Board Boot Requirements CLIENT (TBBR-CLIENT): https://developer.arm.com/docs/den0006/latest/trusted-board-boot-requirements-client-tbbr-client-armv8-a
283.. _SMC Calling Convention: http://infocenter.arm.com/help/topic/com.arm.doc.den0028b/ARM_DEN0028B_SMC_Calling_Convention.pdf
284.. _System Control and Management Interface (SCMI): SCMI_
285.. _SCMI: http://infocenter.arm.com/help/topic/com.arm.doc.den0056a/DEN0056A_System_Control_and_Management_Interface.pdf
286.. _Software Delegated Exception Interface (SDEI): SDEI_
287.. _SDEI: http://infocenter.arm.com/help/topic/com.arm.doc.den0054a/ARM_DEN0054A_Software_Delegated_Exception_Interface.pdf
288.. _Juno Arm Development Platform: http://www.arm.com/products/tools/development-boards/versatile-express/juno-arm-development-platform.php
289.. _Arm FVP website: FVP_
290.. _FVP: https://developer.arm.com/products/system-design/fixed-virtual-platforms
291.. _Linaro Release 18.04: https://community.arm.com/dev-platforms/b/documents/posts/linaro-release-notes-deprecated#LinaroRelease18.04
292.. _OP-TEE Secure OS: https://github.com/OP-TEE/optee_os
293.. _NVIDIA Trusted Little Kernel: http://nv-tegra.nvidia.com/gitweb/?p=3rdparty/ote_partner/tlk.git;a=summary
294.. _Trusty Secure OS: https://source.android.com/security/trusty
295.. _trustedfirmware.org: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
296.. _issue tracker: https://issues.trustedfirmware.org
297.. _Security Center: ./docs/security-center.rst
298.. _license: ./license.rst
299.. _Contributing Guidelines: ./contributing.rst
300.. _Acknowledgments: ./acknowledgements.rst
301.. _Firmware Design: ./docs/firmware-design.rst
302.. _Change Log: ./docs/change-log.rst
303.. _User Guide: ./docs/user-guide.rst
304.. _Porting Guide: ./docs/porting-guide.rst
305.. _FreeBSD: http://www.freebsd.org
306.. _SCC: http://www.simple-cc.org/
307.. _Security Advisory TFV-1: ./docs/security_advisories/security-advisory-tfv-1.rst
308.. _Security Advisory TFV-2: ./docs/security_advisories/security-advisory-tfv-2.rst
309.. _Security Advisory TFV-3: ./docs/security_advisories/security-advisory-tfv-3.rst
310.. _Security Advisory TFV-4: ./docs/security_advisories/security-advisory-tfv-4.rst
311.. _Security Advisory TFV-5: ./docs/security_advisories/security-advisory-tfv-5.rst
312.. _Security Advisory TFV-6: ./docs/security_advisories/security-advisory-tfv-6.rst
313.. _Security Advisory TFV-7: ./docs/security_advisories/security-advisory-tfv-7.rst
314.. _Security Advisory TFV-8: ./docs/security_advisories/security-advisory-tfv-8.rst