0

I'm trying to boot my BeagleBone Black into Angstrom using pre-built images found here. My SD card has two partitions BOOT & ROOTFS, and was formatted according to the procedures found here.

enter image description here

Below are the contents of both partitions:

contents of BOOT & ROOTFS

The lost+found folder was the result of formatting the SD card and I haven't been able to delete it. I don't think this would cause u-boot to hang.

However when booting, u-boot repeatedly tells me that it can't find /boot/uImage & /boot/am335x-boneblack.dtb:

boot-up sequence

The first of the following 2 images is my uEnv.txt, it uses load mmc 0:2 to both load these files. The second image is the result after attempting to use ext4load mmc 0:2 since the ROOTFS partition is formatted as ext4:

uEnv.txt entering uboot and using ext4load

The ROOTFS (mmc 0:2) partition contains the rootfile system, but when I attempt to list the contents of the /boot directory u-boot returns nothing. When I had the SD card plugged into my comp and mounted. I attempted to ls the /boot directory and denied permission despite using sudo.

listing the contents of my ROOTFS partition (mmc 0:2)

Why can't uboot locate the uImage and dtb files?

Niko_Jako
  • 47
  • 1
  • 1
  • 9

1 Answers1

0

These are the classic symptoms of an old U-Boot trying to use a modern ext4 fs that has incompatible features. You need to run mkfs.ext4 with -O ^64bit,^metadata_csum for a U-Boot of that era to work with the filesystem.

Tom Rini
  • 495
  • 3
  • 10
  • Thanks @Tom Rini, that made it work, I reformatted my ROOTFS partition using your suggestion and that allowed for the kernel to boot. I have a lot to learn still. – Niko_Jako May 30 '20 at 00:12
  • FYI - "lost+found" that I mentioned in my second image, is most likely a partially recovered file that fsck found while fixing my uSD card. See the second paragraph in the [Use](https://en.wikipedia.org/wiki/Fsck) section of the fsck wiki-page. – Niko_Jako Jul 01 '20 at 21:07