diff options
author | Juan Castillo <juan.castillo@arm.com> | 2015-04-14 12:49:03 +0100 |
---|---|---|
committer | Juan Castillo <juan.castillo@arm.com> | 2015-06-25 08:53:26 +0100 |
commit | 95cfd4ad84633502938a8bccc2b0290dfbcac2f7 (patch) | |
tree | 88abb69a6b305be5bc3bcbf6010357e2edff0fa1 /bl1/bl1.ld.S | |
parent | 16948ae1d9e14190229f0fd8602f8cc0f25d57d2 (diff) |
TBB: add platform API to read the ROTPK information
This patch extends the platform port by adding an API that returns
either the Root of Trust public key (ROTPK) or its hash. This is
usually stored in ROM or eFUSE memory. The ROTPK returned must be
encoded in DER format according to the following ASN.1 structure:
SubjectPublicKeyInfo ::= SEQUENCE {
algorithm AlgorithmIdentifier,
subjectPublicKey BIT STRING
}
In case the platform returns a hash of the key:
DigestInfo ::= SEQUENCE {
digestAlgorithm AlgorithmIdentifier,
keyDigest OCTET STRING
}
An implementation for ARM development platforms is provided in this
patch. When TBB is enabled, the ROTPK hash location must be specified
using the build option 'ARM_ROTPK_LOCATION'. Available options are:
- 'regs' : return the ROTPK hash stored in the Trusted
root-key storage registers.
- 'devel_rsa' : return a ROTPK hash embedded in the BL1 and
BL2 binaries. This hash has been obtained from the development
RSA public key located in 'plat/arm/board/common/rotpk'.
On FVP, the number of MMU tables has been increased to map and
access the ROTPK registers.
A new file 'board_common.mk' has been added to improve code sharing
in the ARM develelopment platforms.
Change-Id: Ib25862e5507d1438da10773e62bd338da8f360bf
Diffstat (limited to 'bl1/bl1.ld.S')
0 files changed, 0 insertions, 0 deletions