summaryrefslogtreecommitdiff
path: root/doc/README.armada-secureboot
diff options
context:
space:
mode:
authorPali Rohár <[email protected]>2022-11-02 18:51:28 +0100
committerStefan Roese <[email protected]>2022-11-07 07:17:55 +0100
commit87ac4b4b4ca5f00e2ddcdac41c9dc691ab2aecf1 (patch)
tree214b5ae758e50c7733b1b65d41f3819d67aaa17d /doc/README.armada-secureboot
parent497db3ad89d6bc257519961cb89aa7dcda30a045 (diff)
Makefile: Rename u-boot-spl.kwb to u-boot-with-spl.kwb
File name with pattern u-boot-spl* is used on all places except in kwb image for binary with SPL-only code. Combined binary with both SPL and proper U-Boot in other places has file name pattern u-boot-with-spl*. Make it consistent also for kwb image and rename u-boot-spl.kwb to u-boot-with-spl.kwb as this image contains both SPL and proper U-Boot code. Also update documentation about file name changes. Signed-off-by: Pali Rohár <[email protected]> Reviewed-by: Stefan Roese <[email protected]>
Diffstat (limited to 'doc/README.armada-secureboot')
-rw-r--r--doc/README.armada-secureboot4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/README.armada-secureboot b/doc/README.armada-secureboot
index 157cb5a231a..4ec89d5c061 100644
--- a/doc/README.armada-secureboot
+++ b/doc/README.armada-secureboot
@@ -257,13 +257,13 @@ ARM architecture
The creation of the boot image is done via the usual invocation of make (with a
suitably set CROSS_COMPILE environment variable, of course). The resulting boot
-image u-boot-spl.kwb can then be tested, if so desired. The hdrparser from [5]
+image u-boot-with-spl.kwb can then be tested, if so desired. The hdrparser from [5]
can be used for this purpose. To build the tool, invoke make in the
'tools/marvell/doimage_mv' directory of [5], which builds a stand-alone
hdrparser executable. A test can be conducted by calling hdrparser with the
produced boot image and the following (mandatory) parameters:
-./hdrparser -k 0 -t u-boot-spl.kwb
+./hdrparser -k 0 -t u-boot-with-spl.kwb
Here we assume that the CSK index is 0 and the boot image file resides in the
same directory (adapt accordingly if needed). The tool should report that all