Date: Thu, 6 Feb 2025 06:03:56 -0800 From: Mark Millard <marklmi@yahoo.com> To: Tomek CEDRO <tomek@cedro.info> Cc: Mario Marietto <marietto2008@gmail.com>, Marco Devesas Campos <devesas.campos@gmail.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: Raimbow screen installing / booting FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img on the raspberry pi zero 2w Message-ID: <1EC055A5-EA4C-4857-BFC6-9C0C29573ED2@yahoo.com> In-Reply-To: <CAFYkXjkdaD8n6rYUrv0kdMwXkqA%2BENu0FAP-n8d7fydRKzwaYw@mail.gmail.com> References: <CA%2B1FSig9coHK-k1dNaong=rOSGGNW170gf%2B-13S7J3syORU_DA@mail.gmail.com> <5E12B96C-20A2-4FFB-A31E-00B259450707@gmail.com> <CA%2B1FSih6jzcy7po3Ux_nSfN6UF%2BzwBfp-iM1vzVgpPObnN3ukA@mail.gmail.com> <CA%2B1FSih9TauSj4YteGij2BFO7C4irxDE=RFoBtnKK6-EMzwV5Q@mail.gmail.com> <FEDBC538-E7B2-49CA-AD27-3641A1BF6E56@gmail.com> <D1B3EA48-16B7-4E9A-940E-A88B0E75F1DA@yahoo.com> <CA%2B1FSijy9OSoaMi%2BLfeiD4zqj=_0OkYcM3OrMEwGZqxrV7X4pg@mail.gmail.com> <E9F79146-A973-4AC0-BFFB-28EF15FF9AE7@yahoo.com> <CAFYkXjkdaD8n6rYUrv0kdMwXkqA%2BENu0FAP-n8d7fydRKzwaYw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Feb 5, 2025, at 23:51, Tomek CEDRO <tomek@cedro.info> wrote:
> On Wed, Feb 5, 2025 at 2:59=E2=80=AFAM Mark Millard =
<marklmi@yahoo.com> wrote:
>> On Feb 4, 2025, at 17:39, Mario Marietto <marietto2008@gmail.com> =
wrote:
>>> ----> A better alternative experiment would likely be to:
>>> I did :
>>> marietto# cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2-w.dtb
>>> and the board booted wonderfully without one only problem.
>>> I think that it's a good idea to add a note on the bug report that =
the patches created don't work and that the fix,for the moment is :
>>> marietto# cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2-w.dtb
>>=20
>> Why not try sysutils/rpi-firmware and copying over the
>> /usr/local/share/rpi-firmware/bcm2710-rpi-zero-2-w.dtb
>> that is actually for the RPi* that you have? It is the
>> same vintage of materials as is on the official media.
>>=20
>> If it does not work, that would be good to have in the
>> notes as well. Similarly, if it does work it would be
>> good to have that noted.
>=20
> Yup, I can confirm rpi-firmware/bcm2710-rpi-zero-2-w.dtb works with
> FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img :-)
FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img contains the
u-boot from:
/usr/ports/sysutils/u-boot-rpi-arm64
and, so, also contains and should be used with a copy of:
/usr/local/share/rpi-firmware/config_arm64.txt
as config.txt :
# grep -rA1 config_arm64 /usr/src/release/
/usr/src/release/arm64/RPI.conf: chroot ${CHROOTDIR} cp -p =
${DTB_DIR}/config_arm64.txt \
/usr/src/release/arm64/RPI.conf- ${FATMOUNT}/config.txt
/usr/local/share/rpi-firmware/config_rpi3.txt is for when:
/usr/ports/sysutils/u-boot-rpi3
is is use instead. No modern snapshot or release uses that:
# grep -r config_config_rpi3 /usr/src/release/
#
/usr/local/share/rpi-firmware/config_rpi_0_w.txt is for when:
/usr/ports/sysutils/u-boot-rpi-0-w
is is use instead. An rpi-0-w is not a arm64 / aarch64 system.
# grep -r config_rpi_0_w /usr/src/release/
#
> One thing to mention too is config_rpi3.txt -> config.txt (not
> config_rpi_0_w.txt) :-)
config_rpi3.txt is likely not fully appropriate and
config_arm64.txt is likely what should be used. But
it was already in place as config.txt in:
FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img
FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img is for
all the aarch64 / arm64 RPi*'s that FreeBSD happens
to support. (RPi5's not being supported as stands.)
> Thanks!! :-)
>=20
> ps/2: pkg does not update because of certificate errors, but
> freebsd-update fetch install went fine to 14.2-RELEASE-p1 o_O
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1EC055A5-EA4C-4857-BFC6-9C0C29573ED2>