Could it be that you are missing the boot.cmd file from the first partition? See <http://linux-sunxi.org/Mainline_U-Boot#Booting_with_boot.cmd>.
Joonas Matt Zagrabelny: > I think my issue is related to generating the u-boot image. > > Here is the console output when I try to boot my new image: > > --- > > Net: Net Initialization Skipped > No ethernet found. > starting USB... > USB0: Core Release: 2.80a > scanning bus 0 for devices... 5 USB Device(s) found > scanning usb for storage devices... 0 Storage Device(s) found > scanning usb for ethernet devices... 1 Ethernet Device(s) found > Hit any key to stop autoboot: 0 > swithc to partitions #0, OK > mmc0 is current device > Scanning mmc 0:1... > Found U-Boot script /boot.scr > reading /boot.scr > 810 bytes read in 12 ms (65.4 KiB/s) > ## Executing script at 02000000 > Saving Environment to FAT... > writing uboot.env > FAT: Misaligned buffer address (000000003ab2aff0) > done > reading linux.uImage > 5974654 bytes read in 392 ms (14.5 MiB/s) > reading bcm2837-rpi-3-b.dtb > 12333 bytes read in 20 ms (601.6 KiB/s) > ** No boot file defined ** > ## Booting kernel from Legacy Image at 01000000 ... > Image Name: > Image Type: AArch64 Linux Kernel Image (gzip compressed) > Data Size: 5974590 Bytes = 5.7 MiB > Load Address: 00080000 > Entry POint: 00080000 > Verifying CHecksum ... OK > ## Flattened Device Tree blob at 00000100 > Booting using the fdt blob at 0x000100 > Uncompressing Kernel Image ... OK > reserving fdt memory region: addr=0 size=1000 > Loading Device Tree to 000000003ab27000, end 000000003ab2d02c ... OK > > Starting kernel ... > > --- > > and then it hangs forever. > > I am hoping to find some instructions for generating the u-boot image for > an RPi3 and check my workflow against that. > > Thanks! > > -m >
