From nobody Wed Feb 05 01:39:19 2025 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YnjbM0FjWz5mqmJ for ; Wed, 05 Feb 2025 01:39:59 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-pj1-x1032.google.com (mail-pj1-x1032.google.com [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YnjbL0v0Fz3rbJ for ; Wed, 05 Feb 2025 01:39:58 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1032.google.com with SMTP id 98e67ed59e1d1-2f42992f608so8707742a91.0 for ; Tue, 04 Feb 2025 17:39:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738719596; x=1739324396; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xAWVdbgOU91W/qsx+GLNzrZv4LQ4hgVwXlfX+mCxSOg=; b=LeVVyEa8YQNVhnftnULlxcVLWy/8L2E1nkE/PdipQ7kKLHggFau9OHCjSGyZNdvXlG vXVdBU6XAZcwuf1ysmGE6wEWdkggEDtnuz1dHhf0S9J2tG99zxrHFft7rFAc35cLk//F VGWbGHP/+B3HDzpJkhsBvyha7FYemZ4yv5A+/zVzsxbjRZCfKDph3EoEbelLICxNrHY4 0nhj5RTMgJUQmDJIHEheVGm+LbOOw0var3tQjfe7GTEkzKf1qkpc/rSnYr+P3dN7GXF3 HskZ//MIrbp0IsRpm8PuLRi1/fAGMkk0nBOzAlYV80uJDQHSFLjzG4+Brn3DNB8PRcvQ 73uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738719596; x=1739324396; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xAWVdbgOU91W/qsx+GLNzrZv4LQ4hgVwXlfX+mCxSOg=; b=lzEtyhfwnO11m66jQWFcfHIEpmqyqKFft0H0tkD09BiUhurnnth3Ff6n45X+Es3y5l ddMNW8IY1gUqwY/o/qXyVRjk7JibaPyAN8AboDBcuJf2gAwxjC8fUadTe2g9PTW7cd4u e+TkaO8okuvrb4ZCOWVlYi63VQcrh8fe9y+Lz9PrP8m73ME8BS0UsIuPf0TE/NMNuiE/ HsKvgObPRVPXjVmwBEydMq6fXuZTIXDjOaUgNEo53tbUaXNdWZkCpq7lSt2F7VZk/+wo shrQo7CMvGTNDuTj6+nfq6CIGPkbVJOOcj9hwXsfpBxZoAgUjk3GyO3tdrP1k2PmQWhE /9JA== X-Forwarded-Encrypted: i=1; AJvYcCUOD+SVb/qOoEVqJBw7z2fQMEwpkJg0wUMMFm4tZPlSRYs6BFLXDqacjWIf7mj3BygTCpPQAltv4Jdh6g==@freebsd.org X-Gm-Message-State: AOJu0YyXIOghOJaMwwFuwRCfkON2i8q4ovWkFmdQrJx985X+nK3YaYX8 7Eq6nLaVJamllSqmcTM1TxfUNAiPWyc1AakfSc8jyJk8ybbiT+nUZ0lhY7Vsq1t/HmnEIfjqA+z kp0e0Yi1RPb39BAw6j8FmhcY7svMZoMaHfuo= X-Gm-Gg: ASbGnct7Dg9SHxrjGn+eW3+NQSSFUnh0HOzbv2+ZN+y10d5rIinzs/qDT2pWlhfb7uW al7B8h6mIMvWa5fcdpeQk+W5I23Bfya6qz87+9gNQoAZbgP31LfKHS728PbRSbzbxNk+oNbrYyQ == X-Google-Smtp-Source: AGHT+IHLtz5sUiWUj6jOXXIKdFomHconF+RQur4QQDMf8PE6VAFXDoKnlEAazZusRK8IniBfveKMwaVwrJS5m+fojjE= X-Received: by 2002:a17:90b:3a88:b0:2ee:c91a:ad05 with SMTP id 98e67ed59e1d1-2f9e074d153mr1376790a91.3.1738719595481; Tue, 04 Feb 2025 17:39:55 -0800 (PST) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 References: <5E12B96C-20A2-4FFB-A31E-00B259450707@gmail.com> In-Reply-To: From: Mario Marietto Date: Wed, 5 Feb 2025 02:39:19 +0100 X-Gm-Features: AWEUYZm--jbdpTANFoTaownmClbUpbkedm2oKWmGLSBYZsx9n8R6wOr_HvzIi8M Message-ID: Subject: Re: Raimbow screen installing / booting FreeBSD-14.2-RELEASE-arm64-aarch64-RPI.img on the raspberry pi zero 2w To: Mark Millard Cc: Marco Devesas Campos , freebsd-arm Content-Type: multipart/alternative; boundary="000000000000da5202062d5b3383" X-Rspamd-Queue-Id: 4YnjbL0v0Fz3rbJ X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; TAGGED_RCPT(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] --000000000000da5202062d5b3383 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable ----> 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 Thanks. On Wed, Feb 5, 2025 at 2:35=E2=80=AFAM Mark Millard wro= te: > On Feb 4, 2025, at 16:37, Marco Devesas Campos > wrote: > > > The problem isn=E2=80=99t the fix =E2=80=94 it=E2=80=99s that there is = simply no appropriate > device tree for the zero-2 that is bundled with the image so the board ha= s > no idea how to boot. > > > > So, while not perfect, until someone from the projects adds a zero 2 > dtb, I=E2=80=99m guessing copying one of the pi-3 images is your best bet= (I just > tried it and it works =E2=80=94 well, boots, at least). > > A better alternative experiment would likely be to: > > ) Note the PORTVERSION used for sysutils/rpi-firmware : > PORTVERSION=3D 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 . > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > > --=20 Mario. --000000000000da5202062d5b3383 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
----> A better alt= ernative 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 t= o 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

Thanks.

On Wed, Feb 5, 2025 at 2:35=E2=80= =AFAM Mark Millard <marklmi@yahoo.c= om> wrote:
devesas.campos@gmail.com> wr= ote:

> The problem isn=E2=80=99t the fix =E2=80=94 it=E2=80=99s 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 d= tb, I=E2=80=99m guessing copying one of the pi-3 images is your best bet (I= just tried it and it works =E2=80=94 well, boots, at least).

A better alternative experiment would likely be to:

) Note the PORTVERSION used for sysutils/rpi-firmware :
=C2=A0 PORTVERSION=3D=C2=A0 =C2=A0 1.20230405.g20230405
=C2=A0 (That encodes the date 2023-Apr-05, by the way.)

) Look for the history of bcm2710-rpi-zero-2-w.dtb to
=C2=A0 find one released (or at lest tagged) that is as
=C2=A0 similar of a vintage as is available. In this case
=C2=A0 there is a match for the specific version:

https://github.= com/raspberrypi/firmware/blob/1.20230405/boot/bcm2710-rpi-zero-2-w.dtb<= br>
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 .

=3D=3D=3D
Mark Millard
marklmi at yahoo.com




--
Ma= rio.
--000000000000da5202062d5b3383--