summaryrefslogtreecommitdiffstats
path: root/board/ti/ks2_evm/Makefile
diff options
context:
space:
mode:
authorDaniel Allred <d-allred@ti.com>2016-05-19 19:10:51 -0500
committerTom Rini <trini@konsulko.com>2016-05-27 15:41:36 -0400
commit410f52579498ebe7863c0b88f417eb2d9fb25551 (patch)
tree352650af461aac836ac4c01fb16542a6175b3b69 /board/ti/ks2_evm/Makefile
parentb9b8403f4934c3236a6c8f515c6672e4714236f9 (diff)
downloadtalos-obmc-uboot-410f52579498ebe7863c0b88f417eb2d9fb25551.tar.gz
talos-obmc-uboot-410f52579498ebe7863c0b88f417eb2d9fb25551.zip
spl: build: ti: add support for secure boot images
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> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com> Tested-by: Andreas Dannenberg <dannenberg@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'board/ti/ks2_evm/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud