andrius
/
arm-trusted-firmware
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
Upstream fork of ATF with a couple of rk3399 patches to remove HDCP blob and increase BAUD_RATE.
1,715 Commits 2 Branches 52 Tags 32 MiB
C 86.4%
Assembly 8.1%
Makefile 3.7%
C++ 1.5%
Python 0.2%
Go to file
Masahiro Yamada bee71c7a80 Makefile: use git describe for BUILD_STRING 
Currently, the BUILD_STRING is just 7-digits git hash.  It is true
we can identify which version is running, but we can not get a quick
idea about how new or old it is.

The command "git describe" provides us a bit more useful information
in the format of:
  (tag-name)-(number of commits on top the tag)-g(7 digits hash)

I added some options:
  --always
    Make "git describe" work without any tag in case the upstream
    ATF is cloned, but all the tags are locally dropped.

  --tags
    Use any tag instead of only annotated tags.  In ATF, only some
    tags are annotated, actually the last annotated tag is "v0.2",
    whereas we are on "v1.3" tag now.  This option is needed to get
    something like v1.3-233-gbcc2bf0 instead of v0.2-1713-gbcc2bf0.

  --dirty
    The mark "-dirty" is appended if the source tree is locally
    modified.

With this commit, the welcome string

  NOTICE:  BL1: v1.3(debug):bcc2bf0

will become like follows:

  NOTICE:  BL1: v1.3(debug):v1.3-233-gbcc2bf0-dirty

While we are here, let's add "2> /dev/null" as well to silently
ignore any error message from git.  We should not assume that users
always work in a git repository; the ATF might be released in a
tarball form instead of a git repository.  In such a case, the git
command will fail, then the ugly message "fatal: Not a git ..." will
be displayed during the build:

$ make CROSS_COMPILE=aarch64-linux-gnu-
fatal: Not a git repository (or any of the parent directories): .git
Building fvp
  CC      drivers/io/io_semihosting.c
  CC      lib/semihosting/semihosting.c
     ...

Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
 		2017-02-03 12:54:49 +09:00
bl1 Report errata workaround status to console 2017-01-30 14:53:19 +00:00
bl2 Define and use no_ret macro where no return is expected 2016-12-05 14:55:35 +00:00
bl2u Define and use no_ret macro where no return is expected 2016-12-05 14:55:35 +00:00
bl31 Define and use no_ret macro where no return is expected 2016-12-05 14:55:35 +00:00
bl32 Abort preempted TSP STD SMC after PSCI CPU suspend 2016-12-23 10:46:32 +00:00
common Merge pull request #791 from jeenu-arm/asm-assert-32 2016-12-20 17:00:32 +00:00
docs Merge pull request #821 from jeenu-arm/errata-printing 2017-01-31 15:40:20 +00:00
drivers tbbr: Use constant-time bcmp() to compare hashes 2017-01-24 14:42:13 +00:00
fdts Fix incorrect copyright notices 2016-12-14 14:31:32 +00:00
include Merge pull request #821 from jeenu-arm/errata-printing 2017-01-31 15:40:20 +00:00
lib Report errata workaround status to console 2017-01-30 14:53:19 +00:00
make_helpers fiptool: support --align option to add desired alignment to image offset 2017-01-28 14:47:44 +09:00
plat Merge pull request #825 from dp-arm/dp/simplify-cond 2017-01-31 15:38:19 +00:00
services Resolve build errors flagged by GCC 6.2 2017-01-26 13:47:37 +00:00
tools fiptool: support --align option to add desired alignment to image offset 2017-01-28 14:47:44 +09:00
.checkpatch.conf Mandate 'Signed-off-by' line in commit messages 2016-10-24 13:44:59 +01:00
.gitignore .gitignore: ignore editor backup files 2016-10-25 01:21:01 +09:00
Makefile Makefile: use git describe for BUILD_STRING 2017-02-03 12:54:49 +09:00
acknowledgements.md Add Xilinx to acknowledgements file 2016-04-06 10:44:27 -07:00
contributing.md Drop requirement for CLA in contribution.md 2016-09-27 21:52:03 +01:00
dco.txt Drop requirement for CLA in contribution.md 2016-09-27 21:52:03 +01:00
license.md Update year in copyright text to 2014 2014-01-17 10:27:53 +00:00
readme.md readme.md: Add tested Linaro release information for FVPs 2016-11-09 13:18:36 +00:00

readme.md

ARM Trusted Firmware - version 1.3

ARM Trusted Firmware provides a reference implementation of secure world software for ARMv8-A, including a [Secure Monitor] TEE-SMC executing at Exception Level 3 (EL3). It implements various ARM interface standards, such as the Power State Coordination Interface (PSCI), Trusted Board Boot Requirements (TBBR, ARM DEN0006C-1) and SMC Calling Convention. As far as possible the code is designed for reuse or porting to other ARMv8-A model and hardware platforms.

ARM will continue development in collaboration with interested parties to provide a full reference implementation of PSCI, TBBR and Secure Monitor code to the benefit of all developers working with ARMv8-A TrustZone technology.

License

The software is provided under a BSD-3-Clause license. Contributions to this project are accepted under the same license with developer sign-off as described in the Contributing Guidelines.

This project contains code from other projects as listed below. The original license text is included in those source files.

  • The stdlib source code is derived from FreeBSD code.

  • The libfdt source code is dual licensed. It is used by this project under the terms of the BSD-2-Clause license.

This Release

This release provides a suitable starting point for productization of secure world boot and runtime firmware, executing in either the AArch32 or AArch64 execution state.

Users are encouraged to do their own security validation, including penetration testing, on any secure world code derived from ARM Trusted Firmware.

Functionality

  • Initialization of the secure world (for example, exception vectors, control registers, interrupt controller and interrupts for the platform), before transitioning into the normal world at the Exception Level and Register Width specified by the platform.

  • Library support for CPU specific reset and power down sequences. This includes support for errata workarounds.

  • Drivers for both versions 2.0 and 3.0 of the ARM Generic Interrupt Controller specifications (GICv2 and GICv3). The latter also enables GICv3 hardware systems that do not contain legacy GICv2 support.

  • Drivers to enable standard initialization of ARM System IP, for example Cache Coherent Interconnect (CCI), Cache Coherent Network (CCN), Network Interconnect (NIC) and TrustZone Controller (TZC).

  • SMC (Secure Monitor Call) handling, conforming to the SMC Calling Convention using an EL3 runtime services framework.

  • PSCI library support for the Secondary CPU Boot, CPU Hotplug, CPU Idle and System Shutdown/Reset/Suspend use-cases. This library is pre-integrated with the provided AArch64 EL3 Runtime Software, and is also suitable for integration into other EL3 Runtime Software.

  • A minimal AArch32 Secure Payload to demonstrate PSCI library integration on platforms with AArch32 EL3 Runtime Software.

  • Secure Monitor library code such as world switching, EL1 context management and interrupt routing. When using the provided AArch64 EL3 Runtime Software, this must be integrated with a Secure-EL1 Payload Dispatcher (SPD) component to customize the interaction with a Secure-EL1 Payload (SP), for example a Secure OS.

  • A Test Secure-EL1 Payload and Dispatcher to demonstrate AArch64 Secure Monitor functionality and Secure-EL1 interaction with PSCI.

  • AArch64 SPDs for the OP-TEE Secure OS and [NVidia Trusted Little Kernel] NVidia TLK.

  • A Trusted Board Boot implementation, conforming to all mandatory TBBR requirements. This includes image authentication using certificates, a Firmware Update (or recovery mode) boot flow, and packaging of the various firmware images into a Firmware Image Package (FIP) to be loaded from non-volatile storage. The TBBR implementation is currently only supported in the AArch64 build.

  • Support for alternative boot flows. Some platforms have their own boot firmware and only require the AArch64 EL3 Runtime Software provided by this project. Other platforms require minimal initialization before booting into an arbitrary EL3 payload.

For a full description of functionality and implementation details, please see the Firmware Design and supporting documentation. The Change Log provides details of changes made since the last release.

Platforms

The AArch64 build of this release has been tested on variants r0, r1 and r2 of the [Juno ARM Development Platform] Juno with Linaro Release 16.06.

The AArch64 build of this release has been tested on the following ARM FVPs (64-bit host machine only, with Linaro Release 16.06):

  • Foundation_Platform (Version 10.1, Build 10.1.32)
  • FVP_Base_AEMv8A-AEMv8A (Version 7.7, Build 0.8.7701)
  • FVP_Base_Cortex-A57x4-A53x4 (Version 7.7, Build 0.8.7701)
  • FVP_Base_Cortex-A57x1-A53x1 (Version 7.7, Build 0.8.7701)
  • FVP_Base_Cortex-A57x2-A53x4 (Version 7.7, Build 0.8.7701)

The AArch32 build of this release has been tested on the following ARM FVPs (64-bit host machine only, with Linaro Release 16.06):

  • FVP_Base_AEMv8A-AEMv8A (Version 7.7, Build 0.8.7701)
  • FVP_Base_Cortex-A32x4 (Version 10.1, Build 10.1.32)

The Foundation FVP can be downloaded free of charge. The Base FVPs can be licensed from ARM: see [www.arm.com/fvp] FVP.

This release also contains the following platform support:

  • MediaTek MT6795 and MT8173 SoCs
  • NVidia T210 and T132 SoCs
  • QEMU emulator
  • RockChip RK3368 and RK3399 SoCs
  • Xilinx Zynq UltraScale + MPSoC

Still to Come

  • AArch32 TBBR support and ongoing TBBR alignment.

  • More platform support.

  • Ongoing support for new architectural features, CPUs and System IP.

  • Ongoing PSCI alignment and feature support.

  • Ongoing security hardening, optimization and quality improvements.

For a full list of detailed issues in the current code, please see the Change Log and the GitHub issue tracker.

Getting Started

Get the Trusted Firmware source code from GitHub.

See the User Guide for instructions on how to install, build and use the Trusted Firmware with the ARM FVPs.

See the Firmware Design for information on how the ARM Trusted Firmware works.

See the Porting Guide as well for information about how to use this software on another ARMv8-A platform.

See the Contributing Guidelines for information on how to contribute to this project and the Acknowledgments file for a list of contributors to the project.

Feedback and support

ARM welcomes any feedback on the Trusted Firmware. Please send feedback using the GitHub issue tracker.

ARM licensees may contact ARM directly via their partner managers.

Copyright (c) 2013-2016, ARM Limited and Contributors. All rights reserved.