[PATCH 02/10] arm: Update linker scripts to ensure appended device tree is aligned
Tom Rini
trini at konsulko.com
Fri Jan 23 00:24:07 CET 2026
On Thu, Jan 22, 2026 at 07:56:26PM -0300, Fabio Estevam wrote:
> On Thu, Jan 22, 2026 at 4:42 PM Tom Rini <trini at konsulko.com> wrote:
>
> > OK. FWIW, I can't reproduce those linker messages about ".sdram" and
> > ".sram", even when I point ROCKCHIP_TPL at the right binary file (per
> > the docs).
>
> I only see these messages if I force SPL_SEPARATE_BSS.
>
> The board boots despite these messages.
So with SEPARATE_BSS the dtb is found where it's expected to be? But
that then brings us back to what I'm saying..
> > I think you need to figure out where the mismatch is between where the
> > device tree is appended in the binary, and where it's expected to be, in
> > the binary, and then why something is writing it to the incorrect spot.
> > At run time, in xPL (and this is lib/fdtdec.c) we look at either
> > _image_binary_end if SEPARATE_BSS is enabled, or __bss_end if not.
> > Looking at the config, I see we are not SEPARATE_BSS here, so it needs
> > to be at __bss_end. And in both works and fails branches (my own quick
> > rebase -q origin/master), for me, __bss_end is the same location.
>
> The dtb is placed at shifted-by-4 offset after the commit in Subject line:
What's appending the dtb there? With SPL_SEPARATE_BSS off it needs to be
at __bss_end, and that's the same location for me, in both cases.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20260122/37958b41/attachment.sig>
More information about the U-Boot
mailing list