Lines Matching refs:trusted

1 The trusted boot framework on Marvell Armada 38x
6 1. Overview of the trusted boot
15 1. Overview of the trusted boot
18 The Armada's trusted boot framework enables the SoC to cryptographically verify
48 image, which employs this trusted boot framework, the following tasks need to
61 The documentation of the trusted boot mode is contained in part 1, chapter
88 			 trusted boot (also known as "security header")
92     Trusted debug mode - A special mode for the trusted boot that allows
93 			 debugging of devices employing the trusted boot
124 For the trusted boot framework, a additional header is added to the boot image.
140 trusted boot process to enable and configure secure debugging, but they were
141 not tested in the current implementation of the trusted boot in U-Boot.
146 The steps in the boot flow that are relevant for the trusted boot framework
149 1) Check if trusted boot is enabled, and perform regular boot if it is not.
165 NOTE: The Box ID and Flash ID are checked after step 6, and the trusted debug
174 To employ the trusted boot framework, cryptographic key material needs to be
204 trusted boot framework, several new options were added to faciliate
215 	     BOX_ID - The BoxID to be used for trusted debugging (a integer
217 	   FLASH_ID - The FlashID to be used for trusted debugging (a integer
219 	 JTAG_DELAY - The JTAG delay to be used for trusted debugging (a
223 		      in the image (that is, whether to use the trusted debug
225        SEC_BOOT_DEV - The boot device from which the trusted boot is allowed to
242 To enable the generation of trusted boot images, the corresponding support
251  -> [*] Build image for trusted boot
300 * Enable trusted boot by burning the corresponding fuse (WARNING: this must be
307 For the trusted boot, the fuse prog command has a special syntax, since the