xref: /rk3399_ARM-atf/readme.rst (revision 27989a8e34a44ff8e6a2e5b011123a09fd8a82c7)
1Trusted Firmware-A - version 1.5
2================================
3
4Trusted Firmware-A (TF-A) provides a reference implementation of secure world
5software for `Armv7-A and Armv8-A`_, including a `Secure Monitor`_ executing
6at Exception Level 3 (EL3). It implements various Arm interface standards,
7such as:
8
9-  The `Power State Coordination Interface (PSCI)`_
10-  Trusted Board Boot Requirements (TBBR, Arm DEN0006C-1)
11-  `SMC Calling Convention`_
12-  `System Control and Management Interface`_
13-  `Software Delegated Exception Interface (SDEI)`_
14
15Where possible, the code is designed for reuse or porting to other Armv7-A and
16Armv8-A model and hardware platforms.
17
18Arm will continue development in collaboration with interested parties to
19provide a full reference implementation of Secure Monitor code and Arm standards
20to the benefit of all developers working with Armv7-A and Armv8-A TrustZone
21technology.
22
23License
24-------
25
26The software is provided under a BSD-3-Clause `license`_. Contributions to this
27project are accepted under the same license with developer sign-off as
28described in the `Contributing Guidelines`_.
29
30This project contains code from other projects as listed below. The original
31license text is included in those source files.
32
33-  The libc source code is derived from `FreeBSD`_ and `SCC`_. FreeBSD uses
34   various BSD licenses, including BSD-3-Clause and BSD-2-Clause. The SCC code
35   is used under the BSD-3-Clause license with the author's permission.
36
37-  The libfdt source code is disjunctively dual licensed
38   (GPL-2.0+ OR BSD-2-Clause). It is used by this project under the terms of
39   the BSD-2-Clause license. Any contributions to this code must be made under
40   the terms of both licenses.
41
42-  The LLVM compiler-rt source code is disjunctively dual licensed
43   (NCSA OR MIT). It is used by this project under the terms of the NCSA
44   license (also known as the University of Illinois/NCSA Open Source License),
45   which is a permissive license compatible with BSD-3-Clause. Any
46   contributions to this code must be made under the terms of both licenses.
47
48-  The zlib source code is licensed under the Zlib license, which is a
49   permissive license compatible with BSD-3-Clause.
50
51-  Some STMicroelectronics platform source code is disjunctively dual licensed
52   (GPL-2.0+ OR BSD-3-Clause). It is used by this project under the terms of the
53   BSD-3-Clause license. Any contributions to this code must be made under the
54   terms of both licenses.
55
56This release
57------------
58
59This release provides a suitable starting point for productization of secure
60world boot and runtime firmware, in either the AArch32 or AArch64 execution
61state.
62
63Users are encouraged to do their own security validation, including penetration
64testing, on any secure world code derived from TF-A.
65
66Functionality
67~~~~~~~~~~~~~
68
69-  Initialization of the secure world, for example exception vectors, control
70   registers and interrupts for the platform.
71
72-  Library support for CPU specific reset and power down sequences. This
73   includes support for errata workarounds and the latest Arm DynamIQ CPUs.
74
75-  Drivers to enable standard initialization of Arm System IP, for example
76   Generic Interrupt Controller (GIC), Cache Coherent Interconnect (CCI),
77   Cache Coherent Network (CCN), Network Interconnect (NIC) and TrustZone
78   Controller (TZC).
79
80-  A generic `SCMI`_ driver to interface with conforming power controllers, for
81   example the Arm System Control Processor (SCP).
82
83-  SMC (Secure Monitor Call) handling, conforming to the `SMC Calling
84   Convention`_ using an EL3 runtime services framework.
85
86-  `PSCI`_ library support for CPU, cluster and system power management
87   use-cases.
88   This library is pre-integrated with the AArch64 EL3 Runtime Software, and
89   is also suitable for integration with other AArch32 EL3 Runtime Software,
90   for example an AArch32 Secure OS.
91
92-  A minimal AArch32 Secure Payload (SP\_MIN) to demonstrate `PSCI`_ library
93   integration with AArch32 EL3 Runtime Software.
94
95-  Secure Monitor library code such as world switching, EL1 context management
96   and interrupt routing.
97   When a Secure-EL1 Payload (SP) is present, for example a Secure OS, the
98   AArch64 EL3 Runtime Software must be integrated with a dispatcher component
99   (SPD) to customize the interaction with the SP.
100
101-  A Test SP/SPD to demonstrate AArch64 Secure Monitor functionality and SP
102   interaction with PSCI.
103
104-  SPDs for the `OP-TEE Secure OS`_, `NVidia Trusted Little Kernel`_
105   and `Trusty Secure OS`_.
106
107-  A Trusted Board Boot implementation, conforming to all mandatory TBBR
108   requirements. This includes image authentication, Firmware Update (or
109   recovery mode), and packaging of the various firmware images into a
110   Firmware Image Package (FIP).
111
112-  Pre-integration of TBB with the Arm CryptoCell product, to take advantage of
113   its hardware Root of Trust and crypto acceleration services.
114
115-  Reliability, Availability, and Serviceability (RAS) functionality, including
116
117   -  A Secure Partition Manager (SPM) to manage Secure Partitions in
118      Secure-EL0, which can be used to implement simple management and
119      security services.
120
121   -  An SDEI dispatcher to route interrupt-based SDEI events.
122
123   -  An Exception Handling Framework (EHF) that allows dispatching of EL3
124      interrupts to their registered handlers, to facilitate firmware-first
125      error handling.
126
127-  A dynamic configuration framework that enables each of the firmware images
128   to be configured at runtime if required by the platform. It also enables
129   loading of a hardware configuration (for example, a kernel device tree)
130   as part of the FIP, to be passed through the firmware stages.
131
132-  Support for alternative boot flows, for example to support platforms where
133   the EL3 Runtime Software is loaded using other firmware or a separate
134   secure system processor, or where a non-TF-A ROM expects BL2 to be loaded
135   at EL3.
136
137-  Support for the GCC, LLVM and Arm Compiler 6 toolchains.
138
139For a full description of functionality and implementation details, please
140see the `Firmware Design`_ and supporting documentation. The `Change Log`_
141provides details of changes made since the last release.
142
143Platforms
144~~~~~~~~~
145
146Various AArch32 and AArch64 builds of this release has been tested on variants
147r0, r1 and r2 of the `Juno Arm Development Platform`_.
148
149Various AArch64 builds of this release have been tested on the following Arm
150Fixed Virtual Platforms (`FVP`_) without shifted affinities, and that do not
151support threaded CPU cores (64-bit host machine only):
152
153NOTE: Unless otherwise stated, the FVP Version is 11.2 Build 11.2.33.
154
155-  ``Foundation_Platform``
156-  ``FVP_Base_AEMv8A-AEMv8A`` (and also Version 9.0, Build 0.8.9005)
157-  ``FVP_Base_Cortex-A35x4``
158-  ``FVP_Base_Cortex-A53x4``
159-  ``FVP_Base_Cortex-A57x4-A53x4``
160-  ``FVP_Base_Cortex-A57x4``
161-  ``FVP_Base_Cortex-A72x4-A53x4``
162-  ``FVP_Base_Cortex-A72x4``
163-  ``FVP_Base_Cortex-A73x4-A53x4``
164-  ``FVP_Base_Cortex-A73x4``
165
166Additionally, various AArch64 builds were tested on the following Arm `FVP`_ s
167with shifted affinities, supporting threaded CPU cores (64-bit host machine
168only).
169
170-  ``FVP_Base_Cortex-A55x4-A75x4`` (Version 0.0, build 0.0.4395)
171-  ``FVP_Base_Cortex-A55x4`` (Version 0.0, build 0.0.4395)
172-  ``FVP_Base_Cortex-A75x4`` (Version 0.0, build 0.0.4395)
173-  ``FVP_Base_RevC-2xAEMv8A``
174
175Various AArch32 builds of this release has been tested on the following Arm
176`FVP`_\ s without shifted affinities, and that do not support threaded CPU cores
177(64-bit host machine only):
178
179-  ``FVP_Base_AEMv8A-AEMv8A``
180-  ``FVP_Base_Cortex-A32x4``
181
182The Foundation FVP can be downloaded free of charge. The Base FVPs can be
183licensed from Arm. See the `Arm FVP website`_.
184
185All the above platforms have been tested with `Linaro Release 17.10`_.
186
187This release also contains the following platform support:
188
189-  HiKey, HiKey960 and Poplar boards
190-  MediaTek MT6795 and MT8173 SoCs
191-  NVidia T132, T186 and T210 SoCs
192-  QEMU emulator
193-  Raspberry Pi 3 board
194-  RockChip RK3328, RK3368 and RK3399 SoCs
195-  Socionext UniPhier SoC family and SynQuacer SC2A11 SoCs
196-  Texas Instruments K3 SoCs
197-  Xilinx Zynq UltraScale + MPSoC
198
199Still to come
200~~~~~~~~~~~~~
201
202-  More platform support.
203
204-  Improved dynamic configuration support.
205
206-  Ongoing support for new architectural features, CPUs and System IP.
207
208-  Ongoing support for new Arm system architecture specifications.
209
210-  Ongoing security hardening, optimization and quality improvements.
211
212For a full list of detailed issues in the current code, please see the `Change
213Log`_ and the `GitHub issue tracker`_.
214
215Getting started
216---------------
217
218Get the TF-A source code from `GitHub`_.
219
220See the `User Guide`_ for instructions on how to install, build and use
221the TF-A with the Arm `FVP`_\ s.
222
223See the `Firmware Design`_ for information on how the TF-A works.
224
225See the `Porting Guide`_ as well for information about how to use this
226software on another Armv7-A or Armv8-A platform.
227
228See the `Contributing Guidelines`_ for information on how to contribute to this
229project and the `Acknowledgments`_ file for a list of contributors to the
230project.
231
232IRC channel
233~~~~~~~~~~~
234
235Development discussion takes place on the #trusted-firmware-a channel
236on the Freenode IRC network. This is not an official support channel.
237If you have an issue to raise, please use the `GitHub issue tracker`_.
238
239Feedback and support
240~~~~~~~~~~~~~~~~~~~~
241
242Arm welcomes any feedback on TF-A. If you think you have found a security
243vulnerability, please report this using the process defined in the TF-A
244`Security Centre`_. For all other feedback, please use the
245`GitHub issue tracker`_.
246
247Arm licensees may contact Arm directly via their partner managers.
248
249--------------
250
251*Copyright (c) 2013-2018, Arm Limited and Contributors. All rights reserved.*
252
253.. _Armv7-A and Armv8-A: https://developer.arm.com/products/architecture/a-profile
254.. _Secure Monitor: http://www.arm.com/products/processors/technologies/trustzone/tee-smc.php
255.. _Power State Coordination Interface (PSCI): PSCI_
256.. _PSCI: http://infocenter.arm.com/help/topic/com.arm.doc.den0022d/Power_State_Coordination_Interface_PDD_v1_1_DEN0022D.pdf
257.. _SMC Calling Convention: http://infocenter.arm.com/help/topic/com.arm.doc.den0028b/ARM_DEN0028B_SMC_Calling_Convention.pdf
258.. _System Control and Management Interface: SCMI_
259.. _SCMI: http://infocenter.arm.com/help/topic/com.arm.doc.den0056a/DEN0056A_System_Control_and_Management_Interface.pdf
260.. _Software Delegated Exception Interface (SDEI): SDEI_
261.. _SDEI: http://infocenter.arm.com/help/topic/com.arm.doc.den0054a/ARM_DEN0054A_Software_Delegated_Exception_Interface.pdf
262.. _Juno Arm Development Platform: http://www.arm.com/products/tools/development-boards/versatile-express/juno-arm-development-platform.php
263.. _Arm FVP website: FVP_
264.. _FVP: https://developer.arm.com/products/system-design/fixed-virtual-platforms
265.. _Linaro Release 17.10: https://community.arm.com/dev-platforms/b/documents/posts/linaro-release-notes-deprecated#LinaroRelease17.10
266.. _OP-TEE Secure OS: https://github.com/OP-TEE/optee_os
267.. _NVidia Trusted Little Kernel: http://nv-tegra.nvidia.com/gitweb/?p=3rdparty/ote_partner/tlk.git;a=summary
268.. _Trusty Secure OS: https://source.android.com/security/trusty
269.. _GitHub: https://www.github.com/ARM-software/arm-trusted-firmware
270.. _GitHub issue tracker: https://github.com/ARM-software/tf-issues/issues
271.. _Security Centre: https://github.com/ARM-software/arm-trusted-firmware/wiki/ARM-Trusted-Firmware-Security-Centre
272.. _license: ./license.rst
273.. _Contributing Guidelines: ./contributing.rst
274.. _Acknowledgments: ./acknowledgements.rst
275.. _Firmware Design: ./docs/firmware-design.rst
276.. _Change Log: ./docs/change-log.rst
277.. _User Guide: ./docs/user-guide.rst
278.. _Porting Guide: ./docs/porting-guide.rst
279.. _FreeBSD: http://www.freebsd.org
280.. _SCC: http://www.simple-cc.org/
281