leandrof/u-boot
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix mxc_hab documenation

Browse Source 
It is necessary to modify the configuration file for the target
board. It wasn't well documented that to enable any of the secure
boot modes, it is required to add CONFIG_SECURE_BOOT to the board
configuration file.

Also, fixed a typo in the encrypted boot section.

Signed-off-by: Ulises Cardenas <Ulises.Cardenas@freescale.com>
This commit is contained in:
Ulises Cardenas 2015-04-20 13:47:58 -05:00 committed by Stefano Babic
parent 8a2bd215a2
commit 8148b82449
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/README.mxc_hab
View File

@ -1,7 +1,13 @@
High Assurance Boot (HAB) for i.MX6 CPUs High Assurance Boot (HAB) for i.MX6 CPUs
To authenticate U-Boot only by the CPU there is no code required in To enable the authenticated or encrypted boot mode of U-Boot, it is
U-Boot itself. However, the U-Boot image to be programmed into the required to set the proper configuration for the target board. This
is done by adding the following configuration in in the proper config
file (e.g. include/configs/mx6qarm2.h)
#define CONFIG_SECURE_BOOT
In addition, the U-Boot image to be programmed into the
boot media needs to be properly constructed, i.e. it must contain a boot media needs to be properly constructed, i.e. it must contain a
proper Command Sequence File (CSF). proper Command Sequence File (CSF).
@ -69,7 +75,7 @@ CONFIG_SECURE_BOOT
CONFIG_SYS_FSL_SEC_COMPAT 4 /* HAB version */ CONFIG_SYS_FSL_SEC_COMPAT 4 /* HAB version */
CONFIG_FSL_CAAM CONFIG_FSL_CAAM
CONFIG_CMD_DEKBLOB CONFIG_CMD_DEKBLOB
CONFIG_SYS_FSL_LE CONFIG_SYS_FSL_SEC_LE
Note: The encrypted boot feature is only supported by HABv4 or Note: The encrypted boot feature is only supported by HABv4 or
greater. greater.