CTCaer/switch-l4t-atf
1
0
Fork 0
mirror of https://github.com/CTCaer/switch-l4t-atf.git synced 2024-12-12 04:35:59 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
379 Commits 9 Branches 0 Tags 36 MiB
C 88.3%
Assembly 7.9%
Makefile 3.6%
Python 0.1%
6ad2e461f0
Go to file
Dan Handley 6ad2e461f0 Rationalize console log output 
Fix the following issues with the console log output:

* Make sure the welcome string is the first thing in the log output
(during normal boot).
* Prefix each message with the BL image name so it's clear which
BL the output is coming from.
* Ensure all output is wrapped in one of the log output macros so it can
be easily compiled out if necessary. Change some of the INFO() messages
to VERBOSE(), especially in the TSP.
* Create some extra NOTICE() and INFO() messages during cold boot.
* Remove all usage of \r in log output.

Fixes ARM-software/tf-issues#231

Change-Id: Ib24f7acb36ce64bbba549f204b9cde2dbb46c8a3
2014-08-12 16:51:18 +01:00
bl1 Rationalize console log output 2014-08-12 16:51:18 +01:00
bl2 Rationalize console log output 2014-08-12 16:51:18 +01:00
bl31 Rationalize console log output 2014-08-12 16:51:18 +01:00
bl32/tsp Rationalize console log output 2014-08-12 16:51:18 +01:00
common Rationalize console log output 2014-08-12 16:51:18 +01:00
docs Add concept of console output log levels 2014-08-12 16:51:05 +01:00
drivers Rationalize console log output 2014-08-12 16:51:18 +01:00
fdts Reserve some DDR DRAM for secure use on FVP platforms 2014-05-22 17:27:28 +01:00
include Add concept of console output log levels 2014-08-12 16:51:05 +01:00
lib Rationalize console log output 2014-08-12 16:51:18 +01:00
plat Rationalize console log output 2014-08-12 16:51:18 +01:00
services Merge pull request #178 from soby-mathew/sm/optmize_el3_context 2014-08-04 10:31:54 +01:00
tools/fip_create Improve BL3-0 documentation 2014-05-19 14:28:53 +01:00
.gitignore Update .gitignore 2014-02-20 19:06:34 +00: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
Makefile Add concept of console output log levels 2014-08-12 16:51:05 +01:00
readme.md Trusted Firmware v0.4 release documentation 2014-06-03 14:52:12 +01:00

readme.md

ARM Trusted Firmware - version 0.4

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 previous source code releases, supporting the Base and Foundation 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 technology.

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 a limited functionality implementation of the Trusted Firmware. It provides a suitable starting point for productization. Future versions will contain new features, optimizations and quality improvements.

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, EL1 context management and interrupt routing. 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.

  • Support for alternative Trusted Boot Firmware. Some platforms have their own Trusted Boot implementation and only require the Secure Monitor functionality provided by ARM Trusted Firmware.

  • Isolation of memory accessible by the secure world from the normal world through programming of a TrustZone controller.

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

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.6, Build 0.8.5602)
  • FVP_Base_Cortex-A57x4-A53x4 (Version 5.6, Build 0.8.5602)
  • FVP_Base_Cortex-A57x1-A53x1 (Version 5.6, Build 0.8.5602)
  • FVP_Base_Cortex-A57x2-A53x4 (Version 5.6, Build 0.8.5602)

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

  • Support for ARMv8-A development board as a reference platform.

  • Complete Trusted Boot implementation.

  • Complete implementation of the PSCI specification.

  • Support for alternative types of Secure-EL1 Payloads.

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