> From: Rob Clark <robdcl...@gmail.com> > Date: Sat, 5 Aug 2017 10:28:34 -0400 > > On Sat, Aug 5, 2017 at 10:01 AM, Mark Kettenis <mark.kette...@xs4all.nl> > wrote: > > > > OpenBSD doesn't run on the db410c. However, our EFI bootloader should > > just run. You can download it from: > > > > http://ftp.openbsd.org/pub/OpenBSD/snapshots/arm64/BOOTAA64.EFI > > > > for the 64-bit (AArch64) and > > > > http://ftp.openbsd.org/pub/OpenBSD/snapshots/armv7/BOOTARM.EFI > > > > for the 32-bit version (AArch32). > > > > Yup, this appears to work, I think this is about what you'd expect > without having an openbsd fs: > > dragonboard410c => load mmc 0:1 ${kernel_addr_r} efi/openbsd/bootaa64.efi > reading efi/openbsd/bootaa64.efi > 75732 bytes read in 35 ms (2.1 MiB/s) > dragonboard410c => bootefi ${kernel_addr_r} ${fdt_addr_r} > ## Starting EFI application at 81000000 ... > Scanning disk sd...@07864000.blk... > Found 1 disks > WARNING: Invalid device tree, expect boot to fail > >> OpenBSD/arm64 BOOTAA64 0.6 > sd0: getdisklabel: no disk label > open(sd0a:/etc/boot.conf): bad partition > boot> > sd0: getdisklabel: no disk label > cannot open sd0a:/etc/random.seed: bad partition > booting sd0a:/bsd: sd0: getdisklabel: no disk label > open sd0a:/bsd: bad partition > failed(95). will try /bsd > boot> > sd0: getdisklabel: no disk label > cannot open sd0a:/etc/random.seed: bad partition > booting sd0a:/bsd: sd0: getdisklabel: no disk label > open sd0a:/bsd: bad partition > failed(95). will try /bsd > Turning timeout off. > boot>
Right. At that point it is trying to load the OpenBSD kernel from a UFS/FFS filesystem, which fails because you don't have a BSD disklabel on your SD/MMC device. And even if it could, it would be game over pretty quickly as the OpenBSD kernel doesn't support the UART on your board (yet). _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot