From: Tom Rini <trini@konsulko.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH V5 08/12] iot2050: Add script for signing artifacts
Date: Sat, 4 Feb 2023 11:21:37 -0500 [thread overview]
Message-ID: <Y96GERFesLaQq2F5@bill-the-cat> (raw)
In-Reply-To: <48d7b446-ffce-63ad-8c65-d392eae0a8d8@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
On Sat, Feb 04, 2023 at 07:34:46AM +0100, Jan Kiszka wrote:
> On 03.02.23 19:51, Tom Rini wrote:
> > On Fri, Feb 03, 2023 at 01:26:37PM +0100, Jan Kiszka wrote:
> >
> >> From: Jan Kiszka <jan.kiszka@siemens.com>
> >>
> >> There are many ways to get a signed firmware for the IOT2050 devices,
> >> namely for the parts under user-control. This script documents one way
> >> of doing it, given a signing key. Augment the board documentation with
> >> the required procedure around it.
> >>
> >> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> > [snip]
> >> +# currently broken in upstream
> >> +#source/tools/binman/binman replace -i flash.bin -f fit@0x380000.fit fit@0x380000
> >> +dd if=fit@0x380000.fit of=flash.bin bs=$((0x1000)) seek=$((0x380000/0x1000)) conv=notrunc
> >
> > Is that still a true comment?
> >
>
> binman: Node '/fit@0x380000/images/u-boot': Offset 0x0 (0) size 0xb8870
> (755824) is outside the section '/fit@0x380000' starting at 0x0 (0) of
> size 0x400 (1024)
>
> And for the second call:
>
> binman: Node '/fit@0x380000': Replacing sections is not implemented yet
>
> We tried fixing but eventually had to give up. binman is not easy to
> understand in these corners.
OK, thanks.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-02-04 16:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 12:26 [PATCH V5 00/12] IOT2050-related enhancements Jan Kiszka
2023-02-03 12:26 ` [PATCH V5 01/12] board: siemens: iot2050: Split the build for PG1 and PG2 Jan Kiszka
2023-02-03 12:26 ` [PATCH V5 02/12] arm: dts: iot2050: Use the auto generator nodes for fdt Jan Kiszka
2023-02-03 12:26 ` [PATCH V5 03/12] iot2050: Update firmware layout Jan Kiszka
2023-02-03 12:26 ` [PATCH V5 04/12] iot2050: Add watchdog start to bootcmd Jan Kiszka
2023-02-03 18:51 ` Tom Rini
2023-02-04 6:35 ` Jan Kiszka
2023-02-03 12:26 ` [PATCH V5 05/12] iot2050: Add CONFIG_ENV_FLAGS_LIST_STATIC Jan Kiszka
2023-02-03 18:52 ` Tom Rini
2023-02-04 6:34 ` Jan Kiszka
2023-02-03 12:26 ` [PATCH V5 06/12] arm: dts: iot2050: Allow verifying U-Boot proper by SPL Jan Kiszka
2023-02-03 12:26 ` [PATCH V5 07/12] tools: Add script for converting public key into device tree include Jan Kiszka
2023-02-04 0:20 ` Simon Glass
2023-02-04 6:35 ` Jan Kiszka
2023-02-04 22:23 ` Simon Glass
2023-02-06 10:42 ` Jan Kiszka
2023-02-06 10:44 ` Jan Kiszka
2023-02-07 4:02 ` Simon Glass
2023-02-07 5:47 ` Jan Kiszka
2023-02-07 13:38 ` Simon Glass
2023-02-03 12:26 ` [PATCH V5 08/12] iot2050: Add script for signing artifacts Jan Kiszka
2023-02-03 18:51 ` Tom Rini
2023-02-04 6:34 ` Jan Kiszka
2023-02-04 16:21 ` Tom Rini [this message]
2023-02-04 22:26 ` Simon Glass
2023-02-06 10:47 ` Jan Kiszka
2023-02-06 11:57 ` Jan Kiszka
2023-02-07 15:28 ` Simon Glass
2023-02-07 16:45 ` Jan Kiszka
2023-02-07 18:39 ` Simon Glass
2023-02-13 4:26 ` Simon Glass
2023-02-13 6:33 ` Jan Kiszka
2023-03-11 1:38 ` Simon Glass
2023-02-03 12:26 ` [PATCH V5 09/12] arm: dts: iot2050: Optionally embed OTP programming data into image Jan Kiszka
2023-02-03 12:37 ` Lothar Waßmann
2023-02-03 12:40 ` Jan Kiszka
2023-02-03 12:26 ` [PATCH V5 10/12] doc: iot2050: Add a note about the watchdog firmware Jan Kiszka
2023-02-03 12:26 ` [PATCH V5 11/12] board: siemens: iot2050: use the named gpio to control the user-button Jan Kiszka
2023-02-03 12:26 ` [PATCH V5 12/12] iot2050: Refresh defconfigs and activate CONFIG_EFI_SCROLL_ON_CLEAR_SCREEN Jan Kiszka
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=Y96GERFesLaQq2F5@bill-the-cat \
--to=trini@konsulko.com \
--cc=jan.kiszka@siemens.com \
--cc=sjg@chromium.org \
--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