Success!
I have no idea why but all of a sudden it "just works"? I just dd'ed a new SD card, plugged er in.
This is the actual log prior to booting /bsd:I'll pardon the oddly naval bootloader and this is exactly the depth I wanted. And it even looks for USB mass storage before settling with the SD card. Very promising!
I have no idea why but all of a sudden it "just works"? I just dd'ed a new SD card, plugged er in.
This is the actual log prior to booting /bsd:
Code:
U-Boot 2021.10 (Mar 03 2024 - 10:35:09 -0700)DRAM: 7.9 GiBRPI 4 Model B (0xd03114)MMC: mmcnr@7e300000: 1, emmc2@7e340000: 0Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In: serialOut: serialErr: serialNet: eth0: ethernet@7d580000PCIe BRCM: link up, 5.0 Gbps x1 (SSC)starting USB...Bus xhci_pci: Register 5000420 NbrPorts 5Starting the controllerUSB XHCI 1.00scanning bus xhci_pci for devices... 2 USB Device(s) foundscanning usb for storage devices... 0 Storage Device(s) foundHit any key to stop autoboot: 0switch to partitions #0, OKmmc0 is current deviceScanning mmc 0:1...libfdt fdt_check_header(): FDT_ERR_BADMAGICCard did not respond to voltage select! : -110Scanning disk mmcnr@7e300000.blk...Disk mmcnr@7e300000.blk not readyScanning disk emmc2@7e340000.blk...Found 3 disksNo EFI system partitionBootOrder not definedEFI boot manager: Cannot load any imageFound EFI removable media binary efi/boot/bootaa64.efi229182 bytes read in 39 ms (5.6 MiB/s)libfdt fdt_check_header(): FDT_ERR_BADMAGICBooting /efi\boot\bootaa64.efidisks: sd0*>> OpenBSD/arm64 BOOTAA64 1.20boot>Such is the folly of being a software nerd. I can't code myself a way out of not realising there might be a voltage difference lurking in the fine manual.NP. But that is well documented. Pi GPIO are 3.3v only and always have been.
Statistics: Posted by *** — Sat Jan 11, 2025 8:17 pm