Re: u-boot places device-tree in bss

[Yuri Honegger <yuri.honegger%icloud.com@localhost>]

> Am 14.12.2025 um 21:20 schrieb Lloyd Parkes <lloyd%must-have-coffee.gen.nz@localhost>:
> 
> 
> On 15/12/2025 07:56, Yuri Honegger wrote:
>> Hello,
>> When the memory address for the device tree isn't provided to u-boot, u-boot
>> decides where to place the device tree by itself. For me, it chooses to place it
>> right after the code, overlapping the bss section.
> 
> What device are you using and what version of U-Boot? Some of our U-Boot versions are quite old and some boards have seen significant changes in U-Boot functionality over the years.

The imx23-olinuxino, but on my development branch where I’m converting it to device trees. u-boot is relatively up-to-date (2025.07).

> 
> I've also seen boards vary in how sophisticated their boot scripts in EEPROM/Flash memory are. I expect that many board manufacturers don't care how well their boot scripts work because the user can just reprogram the board to do what ever is required.
> 
> Maybe adding a suitably sophisticated boot.scr to the U-Boot package itself is a reliable way to solve this problem.

Yes, a boot.scr works to solve the issue. The reason I’ve brought it up is to see if this is an area where netbsd can improve (for example with a better error message or by dealing with the problem.)

> 
> Ngā mihi,
> Lloyd
>