Praise be, The beast boots with a home-cooked U-Boot on mmc and the system on SATA. I used the latest u-boot sources, so I will have to patch still for the ethernet to work and fix some silliness, but that is minor.
Watch this space. j. On Thu, Nov 3, 2022 at 11:39 AM Mark Kettenis <mark.kette...@xs4all.nl> wrote: > > From: Jan de Kruyf <jan.de.kr...@gmail.com> > > Date: Tue, 1 Nov 2022 20:48:07 +0100 > > > > > Hope that helps, > > > > No, let me show you what happens after the u-boot on mmc0 (just blank > > otherwise) > > ------- > > Hit any key to stop autoboot: 0 > > switch to partitions #0, OK > > mmc0 is current device > > Scanning mmc 0:1... > > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > > Scanning disk m...@1c0f000.blk... > > Found 2 disks > > No EFI system partition > > BootOrder not defined > > EFI boot manager: Cannot load any image > > MMC Device 1 not found > > no mmc device at slot 1 > > scanning bus for devices... > > Target spinup took 0 ms. > > AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode > > flags: ncq stag pm led clo only pmp pio slum part ccc apst > > Device 0: (0:0) Vendor: ATA Prod.: WDC WDS500G1R0A Rev: 4110 > > Type: Hard Disk > > Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) > > > > Device 0: (0:0) Vendor: ATA Prod.: WDC WDS500G1R0A Rev: 4110 > > Type: Hard Disk > > Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) > > ... is now current device > > Scanning scsi 0:1... > > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > > BootOrder not defined > > EFI boot manager: Cannot load any image > > Found EFI removable media binary efi/boot/bootarm.efi > > 117796 bytes read in 9 ms (12.5 MiB/s) > > libfdt fdt_check_header(): FDT_ERR_BADMAGIC > > Booting /efi\boot\bootarm.efi > > disks: sd0 > > >> OpenBSD/armv7 BOOTARM 1.19 > > open(tftp0a:/etc/boot.conf): Operation not permitted > > boot> > > booting tftp0a:/bsd: open tftp0a:/bsd: Operation not permitted > > failed(1). will try /bsd > > boot> > > Ah, that is a clear sign of a broken U-Boot. You may have better > > > The open-BSD supplied u-boot has a problem with the ethernet: it does not > > work. And presumably the ram clockspeed might be too high. It was lowered > > considerably at one stage by olimex. > > Did you try using the OpenBSD U-Boot together with the Olimex DTB file? > > > Hopefully you have some more light. > > Where is the source for the openBSD supied u-boot? > > It is U-Boot 2021.10 with a limited set of patches applied. You can > find the patches in the ports tree: > > https://github.com/openbsd/ports/tree/master/sysutils/u-boot/patches > > But it doesn't look like any of them will affect this board. >
