From: Quentin Schulz <quentin.schulz@cherry.de>
To: Simon Glass <sjg@chromium.org>
Cc: FUKAUMI Naoki <naoki@radxa.com>,
u-boot@lists.denx.de, philipp.tomsich@vrull.eu,
kever.yang@rock-chips.com, trini@konsulko.com, jonas@kwiboo.se,
dsimic@manjaro.org, pbrobinson@gmail.com,
marek.vasut+renesas@mailbox.org, ian.roberts@timesys.com,
nathan.morrison@timesys.com, greg.malysa@timesys.com, bb@ti.com
Subject: Re: [PATCH 3/3] rockchip: Fix binman error
Date: Thu, 6 Feb 2025 17:54:32 +0100 [thread overview]
Message-ID: <7178d2ce-9c13-4ab7-9c56-aff84b65461a@cherry.de> (raw)
In-Reply-To: <CAFLszTi7EuM36eSrKehuH_fOkbkE0ZX79jkpZAAn7PonS1EgNQ@mail.gmail.com>
Hi Simon,
On 2/6/25 1:46 PM, Simon Glass wrote:
> Hi Quentin,
>
> On Wed, 5 Feb 2025 at 06:00, Quentin Schulz <quentin.schulz@cherry.de> wrote:
>>
>> Hi Naoki,
>>
>> On 1/29/25 2:25 PM, FUKAUMI Naoki wrote:
>>> After adding the below configs, binman produces an error.
>>>
>>> CONFIG_SPL_DFU
>>> CONFIG_SPL_ENV_SUPPORT
>>> CONFIG_SPL_USB_DWC3_GENERIC
>>> CONFIG_SPL_USB_GADGET
>>>
>>> binman: Section '/binman/simple-bin-spi': Symbol '_binman_u_boot_any_prop_size'
>>> in entry '/binman/simple-bin-spi/mkimage/u-boot-spl/u-boot-spl-nodtb': Entry 'u-boot-any' not found in list (u-boot-tpl-nodtb,u-boot-tpl-dtb,u-boot-tpl,u-boot-spl-nodtb,u-boot-spl-dtb,u-boot-spl,mkimage,fit,simple-bin-spi)
>>>
>>> Add "no-write-symbols;" to u-boot-tpl and u-boot-spl.
>>>
>>
>> I'll be frank with you, I have no clue what's happening :)
>
> I means that simple-bin-spi has a binary inside it, u-boot-spl, which
> uses binman_sym_declare(ulong, u_boot_any, size). Most likely it is
> the one at the top of common/spl.c
>
> This symbol is filled in (by binman, at build-time) with the size of
> the U-Boot binary. If there is no such U-Boot image then it cannot do
> this.
>
Why is it not failing right now? Why does it fail when you enable
CONFIG_SPL_DFU, CONFIG_SPL_ENV_SUPPORT, CONFIG_SPL_USB_DWC3_GENERIC,
CONFIG_SPL_USB_GADGET for Rock-Pi-4? This doesn't generate the
u-boot.itb file we need for simple-bin-spi as we anyway take the fit
blob generated by simple-bin instead.
It would make sense to always fail if this relies on u-boot.itb to be
built for simple-bin-spi as well?
I suggested to use only blobs from simple-bin in simple-bin-spi but
according to
https://docs.u-boot.org/en/latest/develop/package/binman.html#image-dependencies
this is undefined behavior. Maybe we should use a template
(https://docs.u-boot.org/en/latest/develop/package/binman.html#templates)
and rebuild everything for the SPI image as well. I saw such a patch in
your VBE part H series I believe, maybe it makes sense to have this
merged separately?
This feels somewhat wrong though, if I'm not mistaken every binary used
in simple-bin and simple-bin-spi is the same, to the exception of how
the idbloader.img is generated (-T rkspi/rksd), so it doesn't make a lot
of sense to me to go through a complete rebuild of all binaries, instead
of just running mkimage a second time with the same set of binaries. But
if that's the only way to have something with defined behavior AND
working, then so be it.
Cheers,
Quentin
next prev parent reply other threads:[~2025-02-06 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 13:25 [PATCH 1/3] rockchip: Fix TPL link error FUKAUMI Naoki
2025-01-29 13:25 ` [PATCH 2/3] rockchip: Fix SPL link error for Radxa ROCK Pi 4 FUKAUMI Naoki
2025-02-05 11:37 ` Quentin Schulz
2025-02-05 16:20 ` Jonas Karlman
2025-01-29 13:25 ` [PATCH 3/3] rockchip: Fix binman error FUKAUMI Naoki
2025-02-05 12:59 ` Quentin Schulz
2025-02-06 12:46 ` Simon Glass
2025-02-06 16:54 ` Quentin Schulz [this message]
2025-02-09 14:27 ` Simon Glass
2025-02-10 7:40 ` FUKAUMI Naoki
2025-02-11 5:41 ` FUKAUMI Naoki
2025-01-29 14:16 ` [PATCH 1/3] rockchip: Fix TPL link error Quentin Schulz
2025-01-29 15:29 ` 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=7178d2ce-9c13-4ab7-9c56-aff84b65461a@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=bb@ti.com \
--cc=dsimic@manjaro.org \
--cc=greg.malysa@timesys.com \
--cc=ian.roberts@timesys.com \
--cc=jonas@kwiboo.se \
--cc=kever.yang@rock-chips.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=naoki@radxa.com \
--cc=nathan.morrison@timesys.com \
--cc=pbrobinson@gmail.com \
--cc=philipp.tomsich@vrull.eu \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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