Hello,
I am trying to load a custom device tree overlay file in the
extlinux/extlinux.conf file (using Yocto [Kirkstone branch] and
beaglebone yocto machine). At boot time u-boot complains:
Invalid fdtoverlay_addr_r for loading overlays
Full uboot output till that point:
U-Boot 2022.01 (Jan 10 2022 - 18:46:34 +0000)
CPU : AM335X-GP rev 2.1
Model: TI AM335x BeagleBone Black
DRAM: 512 MiB
WDT: Started wdt@44e35000 with servicing (60s timeout)
NAND: 0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1...
<ethaddr> not set. Validating first E-fuse MAC
Net: eth2: ethernet@4a100000, eth3: usb_ether
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
1: Yocto
Retrieving file: /zImage
append: root=PARTUUID=18e99beb-02 rootwait console=ttyS0,115200
Retrieving file: /am335x-bonegreen.dtb
Invalid fdtoverlay_addr_r for loading overlays
Kernel image @ 0x82000000 [ 0x000000 - 0x77b738 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Device Tree to 8ffed000, end 8ffff9dc ... OK
Where, how and to what value can I set this variable, so it is possible
to load the dtbo file? I have found some references here:
https://docs.u-boot.org/en/latest/develop/bootstd.html , but still
cannot figure out how to configure this variable for the u-boot to see
it.
PS: I think that when I used U-Boot 2023.04 I have not experienced this
issue. If this would be the case, I can always update the built u-boot
version. I am however trying to understand what is going on exactly.
I would appreciate all help!
--
Łukasz Przeniosło
