From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lokesh Vutla Date: Fri, 15 Apr 2016 15:29:04 +0530 Subject: [U-Boot] [PATCH 11/16] spl: build: ti: add support for secure boot images In-Reply-To: <1460417838-22343-12-git-send-email-d-allred@ti.com> References: <1460417838-22343-1-git-send-email-d-allred@ti.com> <1460417838-22343-12-git-send-email-d-allred@ti.com> Message-ID: <5710BB68.7070009@ti.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tuesday 12 April 2016 05:07 AM, Daniel Allred wrote: > Updates the SPL build so that when CONFIG_TI_SECURE_DEVICE > is in use (which it should be when building for secure parts), > the TI secure development package is used to create a valid > secure boot image. The u-boot SPL build processes is NOT aware > of the details of creating the boot image - all of that information > is encapsulated in the TI secure development package, which is > available from TI. More info can be found in README.ti-secure > > Right now, two image types are generated, MLO and X-LOADER. The types > are important, as certain boot modes implemented by the device's ROM > boot loader require one or the other (they are not equivalent). The > output filenames are u-boot-spl_HS_MLO and u-boot-spl_HS_X-LOADER. The > u-boot-spl_HS_MLO image is also copied to a file named MLO, which is > the name that the device ROM bootloader requires for loading from the > FAT partition of an SD card (same as on non-secure devices). Reviewed-by: Lokesh Vutla Thanks and regards, Lokesh