Upstream fork of ATF with a couple of rk3399 patches to remove HDCP blob and increase BAUD_RATE.
Go to file
Vikram Kanigiri 29fb905d5f Rework handover interface between BL stages
This patch reworks the handover interface from: BL1 to BL2 and
BL2 to BL3-1. It removes the raise_el(), change_el(), drop_el()
and run_image() functions as they catered for code paths that were
never exercised.
BL1 calls bl1_run_bl2() to jump into BL2 instead of doing the same
by calling run_image(). Similarly, BL2 issues the SMC to transfer
execution to BL3-1 through BL1 directly. Only x0 and x1 are used
to pass arguments to BL31. These arguments and parameters for
running BL3-1 are passed through a reference to a
'el_change_info_t' structure. They were being passed value in
general purpose registers earlier.

Change-Id: Id4fd019a19a9595de063766d4a66295a2c9307e1
2014-05-22 15:43:23 +01:00
bl1 Rework handover interface between BL stages 2014-05-22 15:43:23 +01:00
bl2 Rework handover interface between BL stages 2014-05-22 15:43:23 +01:00
bl31 Rework handover interface between BL stages 2014-05-22 15:43:23 +01:00
bl32/tsp Merge pull request #71 from sandrine-bailleux:sb/fix-tsp-fvp-makefile 2014-05-16 12:27:33 +01:00
common Rework handover interface between BL stages 2014-05-22 15:43:23 +01:00
docs Merge pull request #78 from jeenuv:tf-issues-148 2014-05-19 12:54:05 +01:00
drivers Rework BL3-1 unhandled exception handling and reporting 2014-05-16 14:51:00 +01:00
fdts Enable secure memory support for FVPs 2014-04-24 14:08:01 +01:00
include Rework handover interface between BL stages 2014-05-22 15:43:23 +01:00
lib Rework BL3-1 unhandled exception handling and reporting 2014-05-16 14:51:00 +01:00
plat Rework handover interface between BL stages 2014-05-22 15:43:23 +01:00
services Introduce macros to manipulate the SPSR 2014-05-22 15:42:09 +01:00
tools/fip_create Always use named structs in header files 2014-05-06 13:57:48 +01:00
.gitignore Update .gitignore 2014-02-20 19:06:34 +00:00
Makefile Merge pull request #78 from jeenuv:tf-issues-148 2014-05-19 12:54:05 +01:00
acknowledgements.md Build system: Fixes #2: Add multi-platform support 2014-01-20 18:45:04 +00:00
contributing.md Update contributing.md with new integration process 2014-04-01 11:22:43 +01:00
license.md Update year in copyright text to 2014 2014-01-17 10:27:53 +00:00
readme.md Add v0.3 release documentation 2014-02-28 18:23:42 +00:00

readme.md

ARM Trusted Firmware - version 0.3

ARM Trusted Firmware provides a reference implementation of secure world software for ARMv8-A, including Exception Level 3 (EL3) software. This release focuses on support for ARM's [Fixed Virtual Platforms (FVPs)] FVP.

The intent is to provide a reference implementation of various ARM interface standards, such as the Power State Coordination Interface (PSCI), Trusted Board Boot Requirements (TBBR) and [Secure Monitor] TEE-SMC code. As far as possible the code is designed for reuse or porting to other ARMv8-A model and hardware platforms.

This release builds on the previous source code release, which has been available in source and binary form since the [Linaro AArch64 OpenEmbedded 13.11 Engineering Build] AArch64 LEB. These support the Base FVP platform models from ARM.

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 software.

License

The software is provided under a BSD 3-Clause license. Certain source files are derived from FreeBSD code: the original license is included in these source files.

This Release

This release is an incomplete implementation of the Trusted Firmware. Only limited functionality is provided at present and it has not been optimized or subjected to extended robustness or stress testing.

Functionality

  • Initial implementation of a subset of the Trusted Board Boot Requirements Platform Design Document (PDD). This includes packaging the various firmware images into a Firmware Image Package (FIP) to be loaded from non-volatile storage.

  • Initializes the secure world (for example, exception vectors, control registers, GIC and interrupts for the platform), before transitioning into the normal world.

  • Supports both GICv2 and GICv3 initialization for use by normal world software.

  • Starts the normal world at the highest available Exception Level: EL2 if available, otherwise EL1.

  • Handles SMCs (Secure Monitor Calls) conforming to the [SMC Calling Convention PDD] SMCCC using an EL3 runtime services framework.

  • Handles SMCs relating to the [Power State Coordination Interface PDD] PSCI for the Secondary CPU Boot, CPU hotplug and CPU idle use-cases.

  • A Test Secure-EL1 Payload and Dispatcher to demonstrate Secure Monitor functionality such as world switching and EL1 context management. This also demonstrates Secure-EL1 interaction with PSCI. Some of this functionality is provided in library form for re-use by other Secure-EL1 Payload Dispatchers.

For a full list of updated functionality and implementation details, please see the User Guide. The Change Log provides details of changes made since the last release.

Platforms

This release of the Trusted Firmware has been tested on the following ARM FVPs (64-bit versions only):

  • Foundation_v8 (Version 2.0, Build 0.8.5206)
  • FVP_Base_AEMv8A-AEMv8A (Version 5.4, Build 0.8.5405)
  • FVP_Base_Cortex-A57x4-A53x4 (Version 5.4, Build 0.8.5405)
  • FVP_Base_Cortex-A57x1-A53x1 (Version 5.4, Build 0.8.5405)

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

Still to Come

  • Complete implementation of the PSCI specification.

  • Secure memory, Secure interrupts and support for other types of Secure-EL1 Payloads.

  • Booting the firmware from a Virtio block device.

  • Completing the currently experimental GICv3 support.

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 Acknowledgements 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-2014, ARM Limited and Contributors. All rights reserved.