On Fri, Nov 30, 2018 at 12:30 AM Ken Shirriff <ken.sh...@gmail.com
> Thanks, Robert. The make worked, but I can't seem to get an overlay to load at all using u-boot. I had moved to a modern u-boot kernel and the overlay I put into dtb_overlay in /boot/uEnv.txt doesn't get loaded, but I don't see any errors in the log either. How do I debug this in the post-capemgr world? I've tried a bunch of different overlays and settings but nothing seems to work. Is there some trick to loading an overlay with u-boot?
> Next, I reinstalled the kernel in case I'd messed up something along the way. Now when I try to install a simple overlay with "uboot_overlay_addr4=/lib/firmware/TEST-00A0.dtbo", it completely hangs during boot, so I'm making negative progress here. Now I get a bunch of overlay errors during boot:
> loading /boot/dtbs/4.14.71-ti-r80/am335x-boneblack-uboot-univ.dtb ...
> 161723 bytes read in 80 ms (1.9 MiB/s)
> uboot_overlays: [fdt_buffer=0x60000] ...
> uboot_overlays: loading /lib/firmware/TEST-00A0.dtbo ...
> 824 bytes read in 449 ms (1000 Bytes/s)
> failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
This usually means you are referencing a node that doesn't exist in the
current live device tree blob...
Let's see your overlay..