Hi again @RobertCNelson and @SuicidalLabRat ,
Due to numerous issues I am facing with meta-ti-bsp layer in kirkstone, I started to test the meta-yocto-bsp instead. These errors do not occur there, but the problem is my device tree overlay cannot be loaded anymore via extlinux.conf file… At boot I get:
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
I tried adding the fdtoverlay_addr_r variable to the extlinux.conf, but then:
Ignoring unknown command: fdtoverlay_addr_r
Do you have any idea how to overcome this…?