Commit 4fce6554dcc9dc9077fa89b61c675e08f9090bfe
Committed by
Tom Rini
1 parent
2ff5183fba
Exists in
smarc_8mq_lf_v2020.04
and in
17 other branches
doc: Updates info on using Keystone2 secure devices
Add a section describing the secure boot image used on Keystone2 secure devices. Signed-off-by: Madan Srinivas <madans@ti.com> Signed-off-by: Andrew F. Davis <afd@ti.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: Lokesh Vutla <lokeshvutla@ti.com>
Showing 1 changed file with 20 additions and 0 deletions Side-by-side Diff
doc/README.ti-secure
... | ... | @@ -133,6 +133,26 @@ |
133 | 133 | u-boot-spl_HS_X-LOADER - boot image for all other flash memories |
134 | 134 | including QSPI and NOR flash |
135 | 135 | |
136 | + Invoking the script for Keystone2 Secure Devices | |
137 | + ============================================= | |
138 | + | |
139 | + create-boot-image.sh \ | |
140 | + <UNUSED> <INPUT_FILE> <OUTPUT_FILE> <UNUSED> | |
141 | + | |
142 | + <UNUSED> is currently ignored and reserved for future use. | |
143 | + | |
144 | + <INPUT_FILE> is the full path and filename of the public world boot | |
145 | + loader binary file (only u-boot.bin is currently supported on | |
146 | + Keystone2 devices, u-boot-spl.bin is not currently supported). | |
147 | + | |
148 | + <OUTPUT_FILE> is the full path and filename of the final secure image. | |
149 | + The output binary images should be used in place of the standard | |
150 | + non-secure binary images (see the platform-specific user's guides | |
151 | + and releases notes for how the non-secure images are typically used) | |
152 | + u-boot_HS_MLO - signed and encrypted boot image that can be used to | |
153 | + boot from all media. Secure boot from SPI NOR flash is not | |
154 | + currently supported. | |
155 | + | |
136 | 156 | Booting of Primary U-Boot (u-boot.img) |
137 | 157 | ====================================== |
138 | 158 |