Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BBAI64 - Failed loading overlay /boot/firmware/overlays/BBORG_LOAD-00A2.dtbo #235

Open
scroston opened this issue Jan 22, 2025 · 6 comments

Comments

@scroston
Copy link

Good Morning,

I have a BBAI64 with a Load Cape attached running Linux BeagleBone-AI64 6.6.58-ti-rt-arm64-r17 #1 SMP PREEMPT_RT.

** Booting bootflow 'mmc@4f80000.bootdev.part_1' with extlinux
BeagleBone AI-64 eMMC (extlinux.conf)
1: copy eMMC to microSD
2: eMMC (debug)
3: eMMC (default)
Enter choice: 3
3: eMMC (default)
Retrieving file: /Image
Retrieving file: /initrd.img
append: root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait net.ifnames=0 quiet
Retrieving file: /ti/k3-j721e-beagleboneai64.dtb
Retrieving file: /boot/firmware/overlays/BBORG_LOAD-00A2.dtbo
Failed loading overlay /boot/firmware/overlays/BBORG_LOAD-00A2.dtbo

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Working FDT set to 88000000
Loading Ramdisk to 8f608000, end 8ffffadc ... OK
Loading Device Tree to 000000008f5e8000, end 000000008f607165 ... OK
Working FDT set to 8f5e8000

Starting kernel ...

extLinux Updated to:

label eMMC (default)
kernel /Image
append root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait net.ifnames=0 quiet
fdtdir /
fdtoverlays /boot/firmware/overlays/BBORG_LOAD-00A2.dtbo
initrd /initrd.img

It indicates it found the file, but failed on loading it. I retrieved the Device Tree files from github branch-> dtb-6.6.

Is there a newer version of BBORG_LOAD-00A2.dtbo for the AI-64? What am I missing here?

v/r
Scott Croston

@RobertCNelson
Copy link
Member

RobertCNelson commented Jan 22, 2025

label eMMC (default)
kernel /Image
append root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait net.ifnames=0 quiet
fdtdir /
fdtoverlays /boot/firmware/overlays/BBORG_LOAD-00A2.dtbo
initrd /initrd.img

"/boot/firmware" is the fat32 mounted path in linux.

If you mount just the partition, you'll see it's:

/overlays/BBORG_LOAD-00A2.dtbo

So the fix is to use:

label eMMC (default)
kernel /Image
append root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait net.ifnames=0 quiet
fdtdir /
fdtoverlays /overlays/BBORG_LOAD-00A2.dtbo
initrd /initrd.img

Which will give you:

1:	Linux eMMC (default)
Retrieving file: /Image
Retrieving file: /initrd.img
append: console=root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait net.ifnames=0 quiet
Retrieving file: /ti/k3-j721e-beagleboneai64.dtb
Retrieving file: /overlays/BBORG_LOAD-00A2.dtbo
failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND
Failed to apply overlay /overlays/BBORG_LOAD-00A2.dtbo, skipping
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree

We need to update BBORG_LOAD-00A2.dts...

Regards,

Edit, BBORG_LOAD hasn't been ported to the BBAI64, give me a few days, it's just pins..

@scroston
Copy link
Author

Got it. Thank you very much. I'll await the update.

Regards

@jadonk
Copy link
Member

jadonk commented Jan 29, 2025

cc @lorforlinux

This should be in our cape compatibility backlog.

@lorforlinux
Copy link

@jadonk Thanks for pointing it out, I have added it to my to-do list.

@RobertCNelson
Copy link
Member

This cape arrived this week, it's just toggling 8 gpio pins, we can do it with gpioset/gpioclear

@jadonk
Copy link
Member

jadonk commented Jan 30, 2025

If we can use names to make it compatible between boards, it would be great to reuse the instructions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants