From: Simon Glass <sjg@chromium.org>
To: Frank Wunderlich <frank-w@public-files.de>
Cc: Philipp Tomsich <philipp.tomsich@vrull.eu>,
Kever Yang <kever.yang@rock-chips.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: uboot FIT signature difference
Date: Sun, 24 Oct 2021 13:53:32 -0600 [thread overview]
Message-ID: <CAPnjgZ2yuR_pUTDO6Ngw0EkkGLGDRXPPRkTA6HxJjvN4E+i-iA@mail.gmail.com> (raw)
In-Reply-To: <trinity-28848953-5228-4dc7-ae23-7a8db7d8257e-1633888288772@3c-app-gmx-bs02>
Hi Frank,
On Sun, 10 Oct 2021 at 11:51, Frank Wunderlich <frank-w@public-files.de> wrote:
>
> Hi,
>
> i try to create a upstream uboot binary for use with rockchip rk3568 (bananapi r2 pro). Currently i'm on preparation phase as i don't have the hardware yet (so i cannot test it).
>
> First thanks to everybody upstreamed support for this SOC in uboot and linux.
>
> i found a compiled uboot.img with this signature:
>
> FIT Image with ATF/OP-TEE/U-Boot
>
> my created itb (make u-boot.itb) has this signature:
>
> FIT image for U-Boot with bl31 (TF-A)
>
> can anybody give me a hint how to create same signature as above? or where i have to look...
As far as I know this is just the description, which you can change by
updating the 'description' of your .its file, or binman node if you
are using that.
>
> i guess the uboot.img is created using this source:
> https://github.com/rockchip-linux/u-boot
>
> as far as i see the itb gets generated from the dtb
>
> OBJCOPY u-boot-nodtb.bin
> ./"arch/arm/mach-rockchip/make_fit_atf.py" \
> arch/arm/dts/rk3568-evb.dtb > u-boot.its
> RELOC u-boot-nodtb.bin
> MKIMAGE u-boot.itb
>
> op-tee seems to be a lib only in rockchip repo, not upstream
>
> https://github.com/rockchip-linux/u-boot/tree/next-dev/lib/optee_clientApi
>
> seems to be some kind of secure boot, idk if this is needed to boot the device
>
> i wonder why uboot differentiate between ATF and BL31...imho BL31 is part of ATF, do i need all parts of ATF (at least BL2) to get same signature? i have some rk3568_ddr_xxxxMHz_v1.08.bin which can be BL2 (did not found any signature and Rockchip ATF source is afaik not yet released, at least not for rk35xx which is new).
>
> "my" source is this:
>
> https://github.com/frank-w/u-boot/tree/2021-10-bpi-r2-pro
I'm not sure about all these flows. It is all quite complicated these days...
Regards,
Simon
next prev parent reply other threads:[~2021-10-24 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-10 17:51 uboot FIT signature difference Frank Wunderlich
2021-10-24 19:53 ` Simon Glass [this message]
2021-10-25 17:59 ` Aw: " Frank Wunderlich
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=CAPnjgZ2yuR_pUTDO6Ngw0EkkGLGDRXPPRkTA6HxJjvN4E+i-iA@mail.gmail.com \
--to=sjg@chromium.org \
--cc=frank-w@public-files.de \
--cc=kever.yang@rock-chips.com \
--cc=philipp.tomsich@vrull.eu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.