Re: Raimbow screen installing / booting FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img on the raspberry pi zero 2w
- Reply: Mario Marietto : "Re: Raimbow screen installing / booting FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img on the raspberry pi zero 2w"
- In reply to: Marco Devesas Campos : "Re: Raimbow screen installing / booting FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img on the raspberry pi zero 2w"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 05 Feb 2025 01:35:22 UTC
On Feb 4, 2025, at 16:37, Marco Devesas Campos <devesas.campos@gmail.com> wrote: > The problem isn’t the fix — it’s that there is simply no appropriate device tree for the zero-2 that is bundled with the image so the board has no idea how to boot. > > So, while not perfect, until someone from the projects adds a zero 2 dtb, I’m guessing copying one of the pi-3 images is your best bet (I just tried it and it works — well, boots, at least). A better alternative experiment would likely be to: ) Note the PORTVERSION used for sysutils/rpi-firmware : PORTVERSION= 1.20230405.g20230405 (That encodes the date 2023-Apr-05, by the way.) ) Look for the history of bcm2710-rpi-zero-2-w.dtb to find one released (or at lest tagged) that is as similar of a vintage as is available. In this case there is a match for the specific version: https://github.com/raspberrypi/firmware/blob/1.20230405/boot/bcm2710-rpi-zero-2-w.dtb However, because it is a match, installing sysutils/rpi-firmware and looking at what it installs it turns out happens to have: /usr/local/share/rpi-firmware/bcm2710-rpi-zero-2-w.dtb So that is the file one would likely want to copy over to the relevant msdosfs and test rpi-zero-2-w operation with. But, I'll note that that the .dtb (or the live adjustments that the RPi* firmware makes after loading the *.dtb) may have things that the FreeBSD kernel does not support or does not handle/avoid. A lack of any explicit development or testing for the rpi-zero-2-w is likely why bcm2710-rpi-zero-2-w.dtb is not on the release or stable snapshot media. So it still may simply not work. I'll note that the bcm271[012]-rpi-*.dtb files are for aarch64 (a.k.a. arm64): Tier 1 (at least for non-embedded) Also, bcm2709-rpi-*.dtb files are for armv7 (32-bit) instead: Tier 2. Finally, bcm2708-rpi-*.dtb files are for armv6 (also 32-bit): Tier 2/3/Unsupported for 13/14/15 . === Mark Millard marklmi at yahoo.com