From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew F. Davis Date: Fri, 24 Feb 2017 06:59:43 -0600 Subject: [U-Boot] [RESEND PATCH 6/9] doc: Updates info on using Keystone2 secure devices In-Reply-To: <20170224125946.7500-1-afd@ti.com> References: <20170224125946.7500-1-afd@ti.com> Message-ID: <20170224125946.7500-7-afd@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 From: Madan Srinivas Add a section describing the secure boot image used on Keystone2 secure devices. Signed-off-by: Madan Srinivas Signed-off-by: Andrew F. Davis --- doc/README.ti-secure | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/doc/README.ti-secure b/doc/README.ti-secure index 9b0fbf9732..4b5380c0f3 100644 --- a/doc/README.ti-secure +++ b/doc/README.ti-secure @@ -133,6 +133,26 @@ Booting of U-Boot SPL u-boot-spl_HS_X-LOADER - boot image for all other flash memories including QSPI and NOR flash + Invoking the script for Keystone2 Secure Devices + ============================================= + + create-boot-image.sh \ + + + is currently ignored and reserved for future use. + + is the full path and filename of the public world boot + loader binary file (only u-boot.bin is currently supported on + Keystone2 devices, u-boot-spl.bin is not currently supported). + + is the full path and filename of the final secure image. + The output binary images should be used in place of the standard + non-secure binary images (see the platform-specific user's guides + and releases notes for how the non-secure images are typically used) + u-boot_HS_MLO - signed and encrypted boot image that can be used to + boot from all media. Secure boot from SPI NOR flash is not + currently supported. + Booting of Primary U-Boot (u-boot.img) ====================================== -- 2.11.0