Some RPi5B "D0" status . . .
Mark Millard <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.arm |
|---|---|
| Message-ID | <[email protected]> |
) The RPi* folks have released an updated "latest" (not factory default yet) EEPROM update that fixes the issue that lead to needing framebuffer_depth=24 to be set. The date involved is 2025-Jun-09, not prior updates. framebuffer_depth=32 worked in my basic testing. This should not be specific to the EDK2 effort. ) As stands, https://github.com/NumberOneGit/rpi5-uefi for the RPi5B "D0" vintage has been making updates via direct updates to the .zip for the EDK2 variant: https://github.com/NumberOneGit/rpi5-uefi/releases/download/v0.1/RPI5_D0.zip instead of using a more normal git-hub release process. The zip does not have a directory as the top level of the expansion as stands. You likely would want to expand into a directory that you had created for the purpose. ) As of last night (my time), I tested a change to get the RPi5 debug port based serial console working when EDK2 is set to Serial instead of to Graphical. It worked in my testing, including getting both kernel and non-kernel messages and allowing login. The .zip currently has ( what I put in RPI5_D0_new_b/ ): # find -s ~/RPI5_D0_new_b/ -print /root/RPI5_D0_new_b/ /root/RPI5_D0_new_b/RPI_EFI.fd /root/RPI5_D0_new_b/bcm2712-d-rpi-5-b.dtb /root/RPI5_D0_new_b/bcm2712-rpi-5-b.dtb /root/RPI5_D0_new_b/bcm2712-rpi-500.dtb /root/RPI5_D0_new_b/bcm2712-rpi-cm5-cm4io.dtb /root/RPI5_D0_new_b/bcm2712-rpi-cm5-cm5io.dtb /root/RPI5_D0_new_b/bcm2712-rpi-cm5l-cm4io.dtb /root/RPI5_D0_new_b/bcm2712-rpi-cm5l-cm5io.dtb /root/RPI5_D0_new_b/bcm2712d0-rpi-5-b.dtb /root/RPI5_D0_new_b/config.txt /root/RPI5_D0_new_b/overlays /root/RPI5_D0_new_b/overlays/bcm2712d0.dtbo Other notes . . . I only have access to a 16 GiByte RPi5B as far as the "D0" vintage/variation goes. I've no detailed clue about the status for cm5 variants or the 500 variant. I'll note that bcm2712d0-rpi-5-b.dtb is named by the upstream linux convention and is analogous to a normal RPi5 "D0" use of bcm2712-rpi-5-b.dtb and then the overlays/bcm2712d0.dtbo (so far?). (That is done by the RPi* firmware early on.) I do not know why the RPi5* folks distribute bcm2712-d-rpi-5-b.dtb . It seem to have fewer differences with bcm2712-rpi-5-b.dtb . I put the files in a msdosfs on a microsd card and boot either an NVMe on a M.2 HAT+ or a USB3 drive, each has the FreeBSD loader well placed in its msdosfs and the kernel and world in its UFS. /boot/loader.conf includes: boot_multicons="YES" boot_serial="YES" console="eficom,efi" but I tested changing things in FreeBSD's loader menu. (I've not tested anything like X11 or such.) I have some lines that I normally just carry around in my /boot/loader.conf files and may not be needed in any specific context: kern.cam.boot_delay=10000 vfs.mountroot.timeout=10 vfs.root_mount_always_wait=1 vfs.ffs.dotrimcons=1 screen.font=8x14 === Mark Millard marklmi at yahoo.com