From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Cc: Matthias Zoechmann <matthias.zoechmann@ife-doors.com>
Subject: [PATCH 1/3] scripts: imx: fix string in further auth block
Date: Mon, 01 Sep 2025 09:35:29 +0200 [thread overview]
Message-ID: <20250901-imx6-usb-uuu-v1-1-1194bb6135ae@pengutronix.de> (raw)
In-Reply-To: <20250901-imx6-usb-uuu-v1-0-1194bb6135ae@pengutronix.de>
From: Matthias Zoechmann <matthias.zoechmann@ife-doors.com>
If an additional block to be authenticated is added via
'hab_do_block off+size@addr' the CST tool will fail.
It seems that an own line is expected for each authentication
block. Add a '\' and linefeed after the comma to avoid a fail of CST.
Signed-off-by: Matthias Zoechmann <matthias.zoechmann@ife-doors.com>
---
scripts/imx/imx.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/imx/imx.c b/scripts/imx/imx.c
index 26027f0f3548ce5ce60c84bf1c94d3a699a331cc..6dabaf59c159b582dfe84eff81cec039c4863b77 100644
--- a/scripts/imx/imx.c
+++ b/scripts/imx/imx.c
@@ -488,7 +488,7 @@ static int do_hab_blocks(struct config_data *data, int argc, char *argv[])
return -EINVAL;
}
- ret = asprintf(&str, ", 0x%08x 0x%08x 0x%08x \"%s\"", addr, off, size, data->outfile);
+ ret = asprintf(&str, ", \\\n 0x%08x 0x%08x 0x%08x \"%s\"", addr, off, size, data->outfile);
if (ret < 0)
return -ENOMEM;
--
2.47.2
next prev parent reply other threads:[~2025-09-01 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-01 7:35 [PATCH 0/3] i.MX6 uuu support for signed images Sascha Hauer
2025-09-01 7:35 ` Sascha Hauer [this message]
2025-09-01 7:35 ` [PATCH 2/3] scripts: imx-image: support DCD_WRITE on closed dev Sascha Hauer
2025-09-01 7:35 ` [PATCH 3/3] mach-imx: Kconfig: add option for image with dcd auth block Sascha Hauer
2025-09-01 8:23 ` Ahmad Fatoum
2025-09-01 8:28 ` Sascha Hauer
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=20250901-imx6-usb-uuu-v1-1-1194bb6135ae@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=matthias.zoechmann@ife-doors.com \
/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