diff mbox

[11/16] spl: build: ti: add support for secure boot images

Message ID 1460417838-22343-12-git-send-email-d-allred@ti.com
State Superseded
Headers show

Commit Message

Allred, Daniel April 11, 2016, 11:37 p.m. UTC 
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).

Signed-off-by: Daniel Allred <d-allred@ti.com>

Signed-off-by: Madan Srinivas <madans@ti.com>

---
 arch/arm/cpu/armv7/omap5/config.mk | 6 ++++++
 1 file changed, 6 insertions(+)

-- 
1.9.1

_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

Comments

Andreas Dannenberg April 21, 2016, 5:27 p.m. UTC | #1 
On Mon, Apr 11, 2016 at 06:37:13PM -0500, 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).

> 

> Signed-off-by: Daniel Allred <d-allred@ti.com>

> Signed-off-by: Madan Srinivas <madans@ti.com>


Successfully boot-tested the patch on actual DRA72x HS and DRA74x HS
hardware.

Tested-by: Andreas Dannenberg <dannenberg@ti.com>


--
Andreas Dannenberg
Texas Instruments Inc
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
diff mbox

Patch

diff --git a/arch/arm/cpu/armv7/omap5/config.mk b/arch/arm/cpu/armv7/omap5/config.mk
index ef2725a..a7e55a5 100644
--- a/arch/arm/cpu/armv7/omap5/config.mk
+++ b/arch/arm/cpu/armv7/omap5/config.mk
@@ -6,8 +6,14 @@ 
 # SPDX-License-Identifier:	GPL-2.0+
 #
 
+include  $(srctree)/$(CPUDIR)/omap-common/config_secure.mk
+
 ifdef CONFIG_SPL_BUILD
+ifeq ($(CONFIG_TI_SECURE_DEVICE),y)
+ALL-y	+= u-boot-spl_HS_MLO u-boot-spl_HS_X-LOADER
+else
 ALL-y	+= MLO
+endif
 else
 ALL-y	+= u-boot.img
 endif