From: Andrew F. Davis <afd@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] armv7R: K3: am654: Fix order of debug elements in x509 template
Date: Fri, 1 Feb 2019 15:04:58 -0600 [thread overview]
Message-ID: <20190201210458.17449-3-afd@ti.com> (raw)
In-Reply-To: <20190201210458.17449-1-afd@ti.com>
The first element in the debug section is expected to be debugUID.
ROM will not parse this correctly when out of order, fix this here.
Signed-off-by: Andrew F. Davis <afd@ti.com>
---
tools/k3_x509template.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/k3_x509template.txt b/tools/k3_x509template.txt
index bd3a9ab056..f176ff3ad2 100644
--- a/tools/k3_x509template.txt
+++ b/tools/k3_x509template.txt
@@ -42,7 +42,7 @@
# salt = FORMAT:HEX,OCT:TEST_IMAGE_KEY_DERIVE_SALT
[ debug ]
+ debugUID = FORMAT:HEX,OCT:0000000000000000000000000000000000000000000000000000000000000000
debugType = INTEGER:4
coreDbgEn = INTEGER:0
coreDbgSecEn = INTEGER:0
- debugUID = FORMAT:HEX,OCT:0000000000000000000000000000000000000000000000000000000000000000
--
2.19.1
next prev parent reply other threads:[~2019-02-01 21:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 21:04 [U-Boot] [PATCH 1/3] configs: am65x_evm_r5: Enable GPT support Andrew F. Davis
2019-02-01 21:04 ` [U-Boot] [PATCH 2/3] am65x_evm: Allow bootm to load larger kernels Andrew F. Davis
2019-02-03 1:10 ` Tom Rini
2019-02-04 4:18 ` Lokesh Vutla
2019-02-10 13:10 ` [U-Boot] [U-Boot, " Tom Rini
2019-02-01 21:04 ` Andrew F. Davis [this message]
2019-02-03 1:10 ` [U-Boot] [PATCH 3/3] armv7R: K3: am654: Fix order of debug elements in x509 template Tom Rini
2019-02-04 4:18 ` Lokesh Vutla
2019-02-10 13:10 ` [U-Boot] [U-Boot, " Tom Rini
2019-02-03 1:09 ` [U-Boot] [PATCH 1/3] configs: am65x_evm_r5: Enable GPT support Tom Rini
2019-02-04 4:18 ` Lokesh Vutla
2019-02-10 13:10 ` [U-Boot] [U-Boot, " 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=20190201210458.17449-3-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