On 8 August 2018 at 11:10, Robert <info...@die-optimisten.net> wrote: > On Wed, 8 Aug 2018 10:29:30 -0700 > jungle Boogie <jungleboog...@gmail.com> wrote: >> So for your nanopi, it was something like this? >> $ doas dd if=miniroot63.fs of=/dev/rsd0c bs=1m >> $ doas dd if=/usr/local/share/u-boot/nanopi_a64/u-boot-sunxi-with-spl.bin \ >> > of=/dev/sd0c bs=1024 seek=8 > > I just tested with the snapshot (8.8.) miniroot and > u-boot-aarch64-2018.09rc1p0. > Works; full log below. > > One thing I noticed: > When booting for the first time, u-boot complains about a FAT issue - > which prevents further booting. > This is easily solved by stopping the u-boot at the "Hit any key to > stop autoboot" prompt and running "saveenv", and then rebooting the > device. > This also fixes the environment errors that sometimes appear > with new u-boot setups. > But in this case it also solved the OpenBSD boot issue. >
So I now have openBSD installed and can boot to it, but when I reboot the nane device, it continues to ignore the saved config. => saveenv Saving Environment to FAT... writing uboot.env OK => reset resetting ... U-Boot SPL 2018.09-rc1 (Aug 05 2018 - 07:22:07 -0600) DRAM: 1024 MiB Trying to boot from MMC1 it any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device ** Can't read partition table on 0:0 ** Scanning mmc 0:1... Found EFI removable media binary efi/boot/bootaa64.efi libfdt fdt_check_header(): FDT_ERR_BADMAGIC Scanning disks on usb... Disk usb0 not ready Disk usb1 not ready Disk usb2 not ready Disk usb3 not ready Scanning disks on mmc... MMC Device 1 not found MMC Device 2 not found MMC Device 3 not found Found 3 disks 108780 bytes read in 9 ms (11.5 MiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC ## Starting EFI application at 40080000 ... >> OpenBSD/arm64 BOOTAA64 0.13 boot> booting sd0a:/bsd: 4718588read text: Unknown error: code -1 failed(-1). will try /bsd Have you encountered anything like this with uboot?
