Mirrors/u-boot
2
0
Fork 0
mirror of https://github.com/AsahiLinux/u-boot synced 2024-11-05 20:54:31 +00:00
Code Issues Projects Releases Packages Wiki Activity
u-boot/include/fsl_secboot_err.h

132 lines
4.8 KiB
C
Raw Normal View History

SECURE BOOT: Add command for validation of images 1. esbc_validate command is meant for validating header and signature of images (Boot Script and ESBC uboot client). SHA-256 and RSA operations are performed using SEC block in HW. This command works on both PBL based and Non PBL based Freescale platforms. Command usage: esbc_validate img_hdr_addr [pub_key_hash] 2. ESBC uboot client can be linux. Additionally, rootfs and device tree blob can also be signed. 3. In the event of header or signature failure in validation, ITS and ITF bits determine further course of action. 4. In case of soft failure, appropriate error is dumped on console. 5. In case of hard failure, SoC is issued RESET REQUEST after dumping error on the console. 6. KEY REVOCATION Feature: QorIQ platforms like B4/T4 have support of srk key table and key revocation in ISBC code in Silicon. The srk key table allows the user to have a key table with multiple keys and revoke any key in case of particular key gets compromised. In case the ISBC code uses the key revocation and srk key table to verify the u-boot code, the subsequent chain of trust should also use the same. 6. ISBC KEY EXTENSION Feature: This feature allows large number of keys to be used for esbc validation of images. A set of public keys is being signed and validated by ISBC which can be further used for esbc validation of images. Signed-off-by: Ruchika Gupta <ruchika.gupta@freescale.com> Signed-off-by: Gaurav Rana <gaurav.rana@freescale.com> Reviewed-by: York Sun <yorksun@freescale.com>
2015-02-27 04:15:35 +00:00
/*
* Copyright 2015 Freescale Semiconductor, Inc.
*
* SPDX-License-Identifier: GPL-2.0+
*/
#ifndef _FSL_SECBOOT_ERR_H
#define _FSL_SECBOOT_ERR_H
#define ERROR_ESBC_PAMU_INIT 0x100000
#define ERROR_ESBC_SEC_RESET 0x200000
#define ERROR_ESBC_SEC_INIT 0x400000
#define ERROR_ESBC_SEC_DEQ 0x800000
#define ERROR_ESBC_SEC_DEQ_TO 0x1000000
#define ERROR_ESBC_SEC_ENQ 0x2000000
#define ERROR_ESBC_SEC_JOBQ_STATUS 0x4000000
#define ERROR_ESBC_CLIENT_CPUID_NO_MATCH 0x1
#define ERROR_ESBC_CLIENT_HDR_LOC 0x2
#define ERROR_ESBC_CLIENT_HEADER_BARKER 0x4
#define ERROR_ESBC_CLIENT_HEADER_KEY_LEN 0x8
#define ERROR_ESBC_CLIENT_HEADER_SIG_LEN 0x10
#define ERROR_ESBC_CLIENT_HEADER_KEY_REVOKED 0x11
#define ERROR_ESBC_CLIENT_HEADER_INVALID_SRK_NUM_ENTRY 0x12
#define ERROR_ESBC_CLIENT_HEADER_INVALID_KEY_NUM 0x13
#define ERROR_ESBC_CLIENT_HEADER_INV_SRK_ENTRY_KEYLEN 0x14
#define ERROR_ESBC_CLIENT_HEADER_IE_KEY_REVOKED 0x15
#define ERROR_ESBC_CLIENT_HEADER_INVALID_IE_NUM_ENTRY 0x16
#define ERROR_ESBC_CLIENT_HEADER_INVALID_IE_KEY_NUM 0x17
#define ERROR_ESBC_CLIENT_HEADER_INV_IE_ENTRY_KEYLEN 0x18
#define ERROR_IE_TABLE_NOT_FOUND 0x19
#define ERROR_ESBC_CLIENT_HEADER_KEY_LEN_NOT_TWICE_SIG_LEN 0x20
armv8: fsl-lsch3: Add new header for secure boot For secure boot, a header is used to identify key table, signature and image address. A new header structure is added for lsch3. Currently key extension (IE) feature is not supported. Single key feature is not supported. Keys must be in table format. Hence, SRK (key table) must be present. Max key number has increase from 4 to 8. The 8th key is irrevocable. A new barker Code is used. Signed-off-by: Aneesh Bansal <aneesh.bansal@nxp.com> Signed-off-by: Saksham Jain <saksham.jain@nxp.com> Reviewed-by: York Sun <york.sun@nxp.com>
2016-03-23 10:54:34 +00:00
#define ERROR_KEY_TABLE_NOT_FOUND 0x21
SECURE BOOT: Add command for validation of images 1. esbc_validate command is meant for validating header and signature of images (Boot Script and ESBC uboot client). SHA-256 and RSA operations are performed using SEC block in HW. This command works on both PBL based and Non PBL based Freescale platforms. Command usage: esbc_validate img_hdr_addr [pub_key_hash] 2. ESBC uboot client can be linux. Additionally, rootfs and device tree blob can also be signed. 3. In the event of header or signature failure in validation, ITS and ITF bits determine further course of action. 4. In case of soft failure, appropriate error is dumped on console. 5. In case of hard failure, SoC is issued RESET REQUEST after dumping error on the console. 6. KEY REVOCATION Feature: QorIQ platforms like B4/T4 have support of srk key table and key revocation in ISBC code in Silicon. The srk key table allows the user to have a key table with multiple keys and revoke any key in case of particular key gets compromised. In case the ISBC code uses the key revocation and srk key table to verify the u-boot code, the subsequent chain of trust should also use the same. 6. ISBC KEY EXTENSION Feature: This feature allows large number of keys to be used for esbc validation of images. A set of public keys is being signed and validated by ISBC which can be further used for esbc validation of images. Signed-off-by: Ruchika Gupta <ruchika.gupta@freescale.com> Signed-off-by: Gaurav Rana <gaurav.rana@freescale.com> Reviewed-by: York Sun <yorksun@freescale.com>
2015-02-27 04:15:35 +00:00
#define ERROR_ESBC_CLIENT_HEADER_KEY_MOD_1 0x40
#define ERROR_ESBC_CLIENT_HEADER_KEY_MOD_2 0x80
#define ERROR_ESBC_CLIENT_HEADER_SIG_KEY_MOD 0x100
#define ERROR_ESBC_CLIENT_HEADER_SG_ESBC_EP 0x200
#define ERROR_ESBC_CLIENT_HASH_COMPARE_KEY 0x400
#define ERROR_ESBC_CLIENT_HASH_COMPARE_EM 0x800
#define ERROR_ESBC_CLIENT_SSM_TRUSTSTS 0x1000
#define ERROR_ESBC_CLIENT_BAD_ADDRESS 0x2000
#define ERROR_ESBC_CLIENT_MISC 0x4000
#define ERROR_ESBC_CLIENT_HEADER_SG_ENTIRES_BAD 0x8000
#define ERROR_ESBC_CLIENT_HEADER_SG 0x10000
#define ERROR_ESBC_CLIENT_HEADER_IMG_SIZE 0x20000
#define ERROR_ESBC_WRONG_CMD 0x40000
#define ERROR_ESBC_MISSING_BOOTM 0x80000
#define ERROR_ESBC_CLIENT_MAX 0x0
struct fsl_secboot_errcode {
int errcode;
const char *name;
};
static const struct fsl_secboot_errcode fsl_secboot_errcodes[] = {
{ ERROR_ESBC_PAMU_INIT,
"Error in initializing PAMU"},
{ ERROR_ESBC_SEC_RESET,
"Error in resetting Job ring of SEC"},
{ ERROR_ESBC_SEC_INIT,
"Error in initializing SEC"},
{ ERROR_ESBC_SEC_ENQ,
"Error in enqueue operation by SEC"},
{ ERROR_ESBC_SEC_DEQ_TO,
"Dequeue operation by SEC is timed out"},
{ ERROR_ESBC_SEC_DEQ,
"Error in dequeue operation by SEC"},
{ ERROR_ESBC_SEC_JOBQ_STATUS,
"Error in status of the job submitted to SEC"},
{ ERROR_ESBC_CLIENT_CPUID_NO_MATCH,
"Current core is not boot core i.e core0" },
{ ERROR_ESBC_CLIENT_HDR_LOC,
"Header address not in allowed memory range" },
{ ERROR_ESBC_CLIENT_HEADER_BARKER,
"Wrong barker code in header" },
{ ERROR_ESBC_CLIENT_HEADER_KEY_LEN,
"Wrong public key length in header" },
{ ERROR_ESBC_CLIENT_HEADER_SIG_LEN,
"Wrong signature length in header" },
{ ERROR_ESBC_CLIENT_HEADER_KEY_LEN_NOT_TWICE_SIG_LEN,
"Public key length not twice of signature length" },
{ ERROR_ESBC_CLIENT_HEADER_KEY_MOD_1,
"Public key Modulus most significant bit not set" },
{ ERROR_ESBC_CLIENT_HEADER_KEY_MOD_2,
"Public key Modulus in header not odd" },
{ ERROR_ESBC_CLIENT_HEADER_SIG_KEY_MOD,
"Signature not less than modulus" },
{ ERROR_ESBC_CLIENT_HEADER_SG_ESBC_EP,
"Entry point not in allowed space or one of the SG entries" },
{ ERROR_ESBC_CLIENT_HASH_COMPARE_KEY,
"Public key hash comparison failed" },
{ ERROR_ESBC_CLIENT_HASH_COMPARE_EM,
"RSA verification failed" },
{ ERROR_ESBC_CLIENT_SSM_TRUSTSTS,
"SNVS not in TRUSTED state" },
{ ERROR_ESBC_CLIENT_BAD_ADDRESS,
"Bad address error" },
{ ERROR_ESBC_CLIENT_MISC,
"Miscallaneous error" },
{ ERROR_ESBC_CLIENT_HEADER_SG,
"No SG support" },
{ ERROR_ESBC_CLIENT_HEADER_IMG_SIZE,
"Invalid Image size" },
{ ERROR_ESBC_WRONG_CMD,
"Unknown cmd/Wrong arguments. Core in infinite loop"},
{ ERROR_ESBC_MISSING_BOOTM,
"Bootm command missing from bootscript" },
{ ERROR_ESBC_CLIENT_HEADER_KEY_REVOKED,
"Selected key is revoked" },
{ ERROR_ESBC_CLIENT_HEADER_INVALID_SRK_NUM_ENTRY,
"Wrong key entry" },
{ ERROR_ESBC_CLIENT_HEADER_INVALID_KEY_NUM,
"Wrong key is selected" },
{ ERROR_ESBC_CLIENT_HEADER_INV_SRK_ENTRY_KEYLEN,
"Wrong srk public key len in header" },
{ ERROR_ESBC_CLIENT_HEADER_IE_KEY_REVOKED,
"Selected IE key is revoked" },
{ ERROR_ESBC_CLIENT_HEADER_INVALID_IE_NUM_ENTRY,
"Wrong key entry in IE Table" },
{ ERROR_ESBC_CLIENT_HEADER_INVALID_IE_KEY_NUM,
"Wrong IE key is selected" },
{ ERROR_ESBC_CLIENT_HEADER_INV_IE_ENTRY_KEYLEN,
"Wrong IE public key len in header" },
{ ERROR_IE_TABLE_NOT_FOUND,
"Information about IE Table missing" },
armv8: fsl-lsch3: Add new header for secure boot For secure boot, a header is used to identify key table, signature and image address. A new header structure is added for lsch3. Currently key extension (IE) feature is not supported. Single key feature is not supported. Keys must be in table format. Hence, SRK (key table) must be present. Max key number has increase from 4 to 8. The 8th key is irrevocable. A new barker Code is used. Signed-off-by: Aneesh Bansal <aneesh.bansal@nxp.com> Signed-off-by: Saksham Jain <saksham.jain@nxp.com> Reviewed-by: York Sun <york.sun@nxp.com>
2016-03-23 10:54:34 +00:00
{ ERROR_KEY_TABLE_NOT_FOUND,
"No Key/ Key Table Found in header"},
SECURE BOOT: Add command for validation of images 1. esbc_validate command is meant for validating header and signature of images (Boot Script and ESBC uboot client). SHA-256 and RSA operations are performed using SEC block in HW. This command works on both PBL based and Non PBL based Freescale platforms. Command usage: esbc_validate img_hdr_addr [pub_key_hash] 2. ESBC uboot client can be linux. Additionally, rootfs and device tree blob can also be signed. 3. In the event of header or signature failure in validation, ITS and ITF bits determine further course of action. 4. In case of soft failure, appropriate error is dumped on console. 5. In case of hard failure, SoC is issued RESET REQUEST after dumping error on the console. 6. KEY REVOCATION Feature: QorIQ platforms like B4/T4 have support of srk key table and key revocation in ISBC code in Silicon. The srk key table allows the user to have a key table with multiple keys and revoke any key in case of particular key gets compromised. In case the ISBC code uses the key revocation and srk key table to verify the u-boot code, the subsequent chain of trust should also use the same. 6. ISBC KEY EXTENSION Feature: This feature allows large number of keys to be used for esbc validation of images. A set of public keys is being signed and validated by ISBC which can be further used for esbc validation of images. Signed-off-by: Ruchika Gupta <ruchika.gupta@freescale.com> Signed-off-by: Gaurav Rana <gaurav.rana@freescale.com> Reviewed-by: York Sun <yorksun@freescale.com>
2015-02-27 04:15:35 +00:00
{ ERROR_ESBC_CLIENT_MAX, "NULL" }
};
void fsl_secboot_handle_error(int error);
#endif
Reference in a new issue Copy permalink