Sorry for top posting. If the instructions for the Pi4 are any guide you need to get the EFI bootloader for the Pi3 (if such a thing exists). The Generic ARM64 image expects that the boot code will execute /EFI/boot/<something>.EFI. That file finds the NetBSD partition and loads the kernel from there.
The standard RPi bootcode looks for kernel.img (or kernel7.img) which is the operating system kernel (there are a few files in between, but I'm not sure which is which). NetBSD can take a kernel and convert it to .img format. That should be your backup plan, although you'd need a NetBSD machine to do this. It doesn't have to be an aarch64 machine, though. The color mesh is usually a sign that the Pi couldn't boot. There should also be a green led that blinks 4 times to let you know that a boot failed (might only be for Pi4). But the easiest way to run NetBSD on an RPi is to download a pre-built image. Check the port-arm list archives for posts by Jun Ebihara. I'm not sure if his Pi3 image in 32 or 64 bit, though. HTH, Jason M. Get BlueMail for Android On Sep 16, 2021, 7:06 PM, at 7:06 PM, Greg Troxel <g...@lexort.com> wrote: > >James Cloos <cl...@jhcloos.com> writes: > >> https://wiki.netbsd.org/ports/evbarm/raspberry_pi/ >> >> i tried using: >> >> >https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/latest/evbarm-aarch64/binary/gzimg/arm64.img.gz >> >> but all i get is a red-yellow-blue-cyan colour mesh >> on the monitor. >> >> Does that colour mesh imply a failed boot? > >I hope somebody who knows more will help you, but yes, I believe that >implies it didn't work. > >Presumably you did gunzip and then dd. Also presumably a RPI2.1, 3, >or >4, as earlier ones do not have aarch64. > >You might try with no card, to see if you get the same syndrome. > >> (w/out net and secsh it is impossible for me to see what is wrong...) > >I would try hooking up a serial console if you have the cable. > >> (I guessed that HEAD holds current. Is that accurate?) > >Yes. Current is the logical name, and HEAD is the CVS branch >pseudoname. > >> I should note that i do not have any other bsd running, and thus no >> access to the ufs fs. > >You should be able to look at the uSD contents and see a partition >table >and I would expect a dos fs with boot stuff.
