Thanks again for your kind help, Miguel. My problem seems to be that the u-boot image is nt found or not loaded. So booting always ends up with the u-boot logo. I can't see the reason for that, because the image off course is present.
May it be important how the raspis boot order is configured? Regards Berni On Sun, 21 Sep 2025 20:30:31 +0000 Miguel Landaeta <[email protected]> wrote: > On Sun, Sep 21, 2025 at 08:43:25AM +0000, Bernhard Ernst wrote: > > > > I know that it should work in this way, but I have no chance to > > enter any character. The only output to HDMI is the nice little > > u-boot logo. That's all. No OpenBSD boot prompt, absolutely nothing. > > > > Did you change or add anything in the config.txt? > > I changed a few lines, trying to enable serial output on GPIOs 14/15 > with no luck (although I suspect a code change could be needed in > OpenBSD to get the secondary serial device to attach, since there are > at least 2 more serial devices not configured in the dmesg I sent > before). > > In any case, to get OpenBSD installed in the Pi 5, I didn't modify > the config.txt provided by the install images. > > This is what I have in that file for now: > > arm_64bit=1 > enable_uart=1 > dtoverlay=uart0-pi5 > dtparam=uart0=on > dtoverlay=disable-bt > kernel=u-boot.bin > dtparam=uart0_console > > What I gather from the docs is: the primary console will always be > available in the debug port (so, you need the debug probe cable or > something compatible with that). > > Once you get the serial output working, let the Pi firmware boot and > find u-boot, then in OpenBSD bootloader you can switch the console to > fb0 or continue with serial. > > Once you install OpenBSD, you can also configure /etc/boot.conf to > automate that and avoid using the debug probe. >
