public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 03/10] doc: Update info on using AM33xx secure devices from TI
Date: Tue, 30 Aug 2016 14:06:22 -0500	[thread overview]
Message-ID: <20160830190629.13956-4-afd@ti.com> (raw)
In-Reply-To: <20160830190629.13956-1-afd@ti.com>

Add a section describing the additional boot types used on AM33xx
secure devices.

Signed-off-by: Andrew F. Davis <afd@ti.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
---
 doc/README.ti-secure | 32 ++++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)

diff --git a/doc/README.ti-secure b/doc/README.ti-secure
index 54c996d..9b0fbf9 100644
--- a/doc/README.ti-secure
+++ b/doc/README.ti-secure
@@ -43,6 +43,38 @@ Booting of U-Boot SPL
 	The script is basically the only required interface to the TI SECDEV
 	package for creating a bootable SPL image for secure TI devices.
 
+	Invoking the script for AM33xx Secure Devices
+	=============================================
+
+	create-boot-image.sh \
+		<IMAGE_FLAG> <INPUT_FILE> <OUTPUT_FILE> <SPL_LOAD_ADDR>
+
+	<IMAGE_FLAG> is a value that specifies the type of the image to
+	generate OR the action the image generation tool will take. Valid
+	values are:
+		SPI_X-LOADER - Generates an image for SPI flash (byte swapped)
+		X-LOADER - Generates an image for non-XIP flash
+		MLO - Generates an image for SD/MMC/eMMC media
+		2ND - Generates an image for USB, UART and Ethernet
+		XIP_X-LOADER - Generates a single stage u-boot for NOR/QSPI XiP
+
+	<INPUT_FILE> is the full path and filename of the public world boot
+	loaderbinary file (depending on the boot media, this is usually
+	either u-boot-spl.bin or u-boot.bin).
+
+	<OUTPUT_FILE> 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-spl_HS_SPI_X-LOADER - byte swapped boot image for SPI flash
+	u-boot-spl_HS_X-LOADER - boot image for NAND or SD/MMC/eMMC rawmode
+	u-boot-spl_HS_MLO - boot image for SD/MMC/eMMC media
+	u-boot-spl_HS_2ND - boot image for USB, UART and Ethernet
+	u-boot_HS_XIP_X-LOADER - boot image for NOR or QSPI Xip flash
+
+	<SPL_LOAD_ADDR> is the address at which SOC ROM should load the
+	<INPUT_FILE>
+
 	Invoking the script for AM43xx Secure Devices
 	=============================================
 
-- 
2.9.3

  parent reply	other threads:[~2016-08-30 19:06 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 19:06 [U-Boot] [PATCH v4 00/10] Allow secure boot on AM33xx devices Andrew F. Davis
2016-08-30 19:06 ` [U-Boot] [PATCH v4 01/10] Kconfig: Separate AM33XX SOC config from target board config Andrew F. Davis
2016-08-31  3:26   ` Lokesh Vutla
2016-08-31 16:06   ` Hannes Schmelzer
2016-08-31 16:16     ` Andrew F. Davis
2016-08-31 17:45       ` Hannes Schmelzer
2016-09-02 14:53   ` Tom Rini
2016-10-03 13:38   ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 02/10] am33xx: config.mk: Add support for additional secure boot image types Andrew F. Davis
2016-08-31  3:26   ` Lokesh Vutla
2016-09-02 14:53   ` Tom Rini
2016-10-03 13:38   ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` Andrew F. Davis [this message]
2016-08-31  3:26   ` [U-Boot] [PATCH v4 03/10] doc: Update info on using AM33xx secure devices from TI Lokesh Vutla
2016-09-02 14:53   ` Tom Rini
2016-10-03 13:38   ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 04/10] am33xx: config.mk: Fix option used to enable SPI SPL image type Andrew F. Davis
2016-08-31  3:27   ` Lokesh Vutla
2016-09-02 14:53   ` Tom Rini
2016-10-03 13:38   ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 05/10] board: am33xx-hs: Allow post-processing of FIT image on AM33xx Andrew F. Davis
2016-08-31  3:28   ` Lokesh Vutla
2016-09-02 14:53   ` Tom Rini
2016-10-03 13:38   ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 06/10] ti: omap-common: Allow AM33xx devices to be built securely Andrew F. Davis
2016-08-31  3:28   ` Lokesh Vutla
2016-09-02 14:53   ` Tom Rini
2016-10-03 13:38   ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 07/10] am335x: configs: Use ISW_ENTRY_ADDR to set SPL_TEXT_BASE Andrew F. Davis
2016-08-31  3:28   ` Lokesh Vutla
2016-09-02 14:53   ` Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 08/10] config: Remove usage of CONFIG_STORAGE_EMMC Andrew F. Davis
2016-08-31  3:28   ` Lokesh Vutla
2016-09-02 14:54   ` Tom Rini
2016-10-03 13:38   ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 09/10] ti_armv7_common: Disable Falcon Mode on HS devices Andrew F. Davis
2016-08-31  3:29   ` Lokesh Vutla
2016-09-02 14:54   ` Tom Rini
2016-10-03 13:38   ` [U-Boot] [U-Boot, v4, " Tom Rini
2016-08-30 19:06 ` [U-Boot] [PATCH v4 10/10] defconfig: Add a config for AM335x High Security EVM with SD Boot support Andrew F. Davis
2016-08-31  3:30   ` Lokesh Vutla
2016-09-02 14:54   ` Tom Rini
2016-09-02 14:57     ` Andrew F. Davis
2016-09-02 14:58       ` Tom Rini
2016-09-07 18:04         ` Andrew F. Davis
2016-10-03 13:39   ` [U-Boot] [U-Boot, v4, " Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160830190629.13956-4-afd@ti.com \
    --to=afd@ti.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox