From: Lukasz Majewski <lukma@denx.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
Marek Vasut <marex@denx.de>
Subject: Re: [Binman] Question regarding SPL symbol offsets generation
Date: Thu, 15 Aug 2024 22:14:21 +0200 [thread overview]
Message-ID: <20240815221421.61f64a17@wsk> (raw)
In-Reply-To: <CAOMZO5A74MigLO0qkeXi04=7M70jaiEgk9zdFBjUV74vuZDP0g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1998 bytes --]
Hi Fabio,
> Hi Lukasz,
>
> On Thu, Aug 8, 2024 at 6:07 AM Lukasz Majewski <lukma@denx.de> wrote:
> >
> > Dear Community
> >
> > I'd like to ask about one issue with generation of symbol offsets in
> > binman [1].
> >
> > In my case the CONFIG_FSPI_CONF_HEADER is defined.
> >
> > Problem is with generated symbols [2] to point into
> > ddr-1d-imem-fw/ddr-1d-dmem-fw/ddr-2d-imem-fw/ddr-2d-dmem-fw.
> >
> > It looks like only symbols have extra offset of 0x1000 (the same as
> > the first section introduces) - binaries for training memory are
> > placed without this extra offset.
> >
> > On the other hand - before this change:
> > SHA1: 37e50627efacd8dae18b564e9d8886a033e181bc
> >
> > The u-boot-spl-ddr.bin was a separate binman "entry" (i.e. not
> > section)
> > - so e.g. ddr-1d-dmem-fw {} had proper offsets (as this binary was
> > also mangled into spl.bin with mkimage invocation).
> >
> >
> > Now the question - how to properly fix this issue?
>
> I assume you fixed the problem with this change:
> https://patchwork.ozlabs.org/project/uboot/patch/20240815080948.457524-1-lukma@denx.de/
Unfortunately not - this change is only for properly setting start
address of the u-boot.
The _real_ problem here is the symbol placement generated by binman
when we try to define the image as a single one.
Moreover, this change follows other boards with imx8mm processor -
./configs/imx8mm_beacon_fspi_defconfig to be specific.
The "fix" (for which I'd been now probably opt) for this issue would be
to generate two images with binman - one for u-boot-spl-ddr.bin and the
final flash.bin with the former one included (as it was before SHA1:
37e50627efacd8dae18b564e9d8886a033e181bc)
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-08-15 20:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 9:06 [Binman] Question regarding SPL symbol offsets generation Lukasz Majewski
2024-08-08 14:28 ` Simon Glass
2024-08-09 9:51 ` Lukasz Majewski
2024-08-15 12:20 ` Fabio Estevam
2024-08-15 20:14 ` Lukasz Majewski [this message]
2024-08-27 18:46 ` Fabio Estevam
2024-08-27 19:26 ` Simon Glass
2024-08-28 8:04 ` Lukasz Majewski
2024-09-02 22:06 ` Adam Ford
2024-09-05 13:54 ` Lukasz Majewski
2024-09-06 0:30 ` Simon Glass
2024-09-06 7:54 ` Lukasz Majewski
2024-09-12 1:11 ` Simon Glass
2024-09-12 7:06 ` Lukasz Majewski
2024-11-04 1:41 ` Adam Ford
2024-11-04 2:00 ` Adam Ford
2024-11-04 3:35 ` Adam Ford
2024-11-04 8:14 ` Lukasz Majewski
2024-11-09 1:04 ` Adam Ford
2024-11-09 2:12 ` Adam Ford
2024-11-09 2:15 ` Fabio Estevam
2024-11-09 20:07 ` Adam Ford
2024-08-28 8:03 ` Lukasz Majewski
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=20240815221421.61f64a17@wsk \
--to=lukma@denx.de \
--cc=festevam@gmail.com \
--cc=marex@denx.de \
--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