From nobody Thu Aug 17 19:22:30 2023 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 4RRZdx6xkVz4q3Rc for ; Thu, 17 Aug 2023 19:22:45 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic304-25.consmr.mail.gq1.yahoo.com (sonic304-25.consmr.mail.gq1.yahoo.com [98.137.68.206]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RRZdx4Qpgz3YNK for ; Thu, 17 Aug 2023 19:22:45 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1692300163; bh=rKLQLQncxO2/LNJ+GDOwCkoMcQeEmU3LJzJRGa3UbrQ=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=NfAzOGPB4YBpJhMuN/cotF+8jCrkpdkgrmnDlX0e3LuI/KN2wnQC7gz46i8NT+iWJKP9jNbGLE7lXFCtzU8Sml1beMV7sULHFhqBHCdEXq7Cx3hL4C7+DXHpOjpifC5x3dasjznakTAfj/7PDlJBowP6NuEVYqBYlAevlAfQwXnQ7sTT1F5hgKDGGfoKik6pzoRObek+Pz8wQHUZ0eRCnNpfKs1tdFH9voY7J1P5wpP9HLR8bfmrFnCAhHvf1msgAD4YkjAgfEAkGOS7zZabqjHhOeECdgdIVG6e1iYLi7PGsvkFc9aqEcJ6dCAIeKO+MFLB47gwfP1AEfHjk9o+vA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1692300163; bh=/8AKLJfrPw+g0VXxc9JS9tp8h5JjBXu/n7xVThzqCeu=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=AdNKMKDoh4RYngYDBLSMA+3DjIMe20W9aZaHRXC/0sSfVE0Z2fQ0m+9N5YarnLD49rJVmJvqO3WaehWTOkHCBxtD05oeKdVmUdqNiTjQXbiaZxR6Inr1aCg6qsC5I6NL/octaM6poyxMACZTDZgVRhajGFEvtbbhts7ERi3rEmgIL83nEUa4JxdZoHWhar8V73zlRDidGWDKzuvR4deTeu95YMxik6D/T9o23C3KtLcYlPGH9ktkIJ8/KMIWYMjXE7LZmgQXCeloyBfovVIkmA0mpxmLdyi8rhSi4e1HJv00jKnQKfw1Kh6sav0lzfhH/XtneAYQqp+Va+wPx2QkUA== X-YMail-OSG: sj8xp9cVM1nsEbAbm9QZIyVf_dHMqou4ol7HVvsEQ5RL5K7lU10gggRxUQv8lnv 5aOuLBUe5MDFPL0erLOaS2AqEVIJlNBEsDdP.oV2bK7Gw8OBoJniCt0ixqg9eJJOIr1Zg_50MElI 94NgleeAiNnVI7ndCz4e7id9DS93H8wDKVv02KRIbV_6yibV1ITpBjqLsEx8PGky04arzhwFOVSo phN0wlYQutY2aNtc.tv18YM7mhJQ5rWB8anJNGItW9TGQnQAj8uy1mZFOtSqXp3kUWEidZ4ckV0e a.K36ss2CBH1xOAMTINh1And2GzQQezbSMktl8UiXAfryrZrFWFJU1TjRNgL68Vm_rlDBdFvf.oJ GRyuTYfpjktF4tWixyYeqFeaswV5SOuQsLwdPI1oiUlhebmdolq4cCJNj9b3yA.ZNMtvREa4tJcq Vo8wtxtHXdC1FquRuNL_EZpASoTCQ5saVp0_oBQTsddNwIhCnfJZfjZxJZxQIuFNLyiRqdu8ijPj L9ye8Pabq8N2ynherXiAoiOXcqICz.oxQeLVSuVhRwo2oEqi5wXfPA4NQP7QGzKo7IyjvQjULfVg 1qOvxySChGMu3QurXcRoxy8oZoIz_xH2rL1s.bUodEdWsUMuTmdSrmj17EGavm7kMTGotq3mEXIO LHY4lasQiomhicUYWH8L8jAoBFC2J0aN2IL_k.FK2lQn5B7M0qEkOPl0GtPnTQKocV6o2HY5hWqw MDFAwPkPQkfOWsrjUGUevGltEIhn2WqxdSPieQhaiBN4AwSSg1QjswNMSs5BS9xE1IT9MogK0H0h duztEmT.JCnX9WOzzm3altPqjz0GV5zoi8XZeAKaiPihM5QANS4Vcl_zSYwOWAKFrbixLPpVOMt6 XrPy05dNg5WJdYWOzYRtFhPxMZOcSYCLisLtdU9YlLu.I4Q88A9XoFHzAhdR3y9iWVfuI9lzQZpH uvZ8McTMlwSXPqvFpo.RXzKA0krgFK0ZVVGfV_Bh8l7tine04yy5U94oCjUjepVuQu9zPayOaJ88 A_sCD2oUTmqRDbrSKxtf2dgYYlmogAQ2..v1R7UbJt5_KeF4kRyOHrVg_z1Rw1NUiFKOc90xdYYZ HXdS.921VEvESxOae3Dh8yrShqxvm3EAYQQhlpK1N4VX7g3XkS0oCy2IGnQ6QTC5s4KUAycchp0Y aLcA2Qh__srdx5CJKaiWwrCHXtFtRdQzdgY7vYuXthRGQ1uakhaKckSKQ_oTT9UNCA2MsoLCFdYr GcUP79TFtDgbRs2xTV6wsx77A9catjobbm.lzYRvSiHfGdxiGI48RhHjCdM0QY_novIwp7bvJaZf hXjt6rBYrstPMOtInQg4CVhmLRnqbd6gyHODtSlAShmgQ8U9U0Mj_sI83a7pbz5vmGzk8XFqK8FV iKh8GVozmv3iSs0T6NVUWm2bAFRIwjHfvsaxiIeE256MVxB.sUtRr4eqvO6Z9w2wO_z.cLca1qY3 k3x6l44Ub7bNVfZWwietVettmt5leeLskYH_Y3b9ZTYDnyBTl_5.JxymW6cX7AJlaiKGnZtqUw1q 4P0nHStCKbsKNFJ4TZd8i7S.UEx_Zzrew9Hnp3DTnoqSDGHtIgfMIW8KiZKhisFR_WbN5vw4BYmo lggLoRKZB8AxJuxCYJa02NqI15zFuKftAWybhRZt1MTeuEMMNiAgjosyrHRWtbgCy1S84a.0Jl3g fcwhrRW6gD51UITU1R6IeVALMapUCfAdJLfoBbx8FYMSkaBHa9zhYKW.JxWaoV..v8oRhY.OWxY5 wmkimOBZW2Q8iTHdE5Z0hk.KyEPlU_cuJy43Z4WtoXtO9YSJunVF1Q5HjwCQYs9sD8itgsCGqQiX qsYgq.rg6eR4iRvUEHQuOcOszLqvivl_dP7zb.jmiHR0hkFkevuBwHTZS74XiXwvsaM958PRhhut 1X6CCkW2_.bWWyhe1gQTaFS9lgAtU0wa_FckY1BCfojGmWJXzf6z3yQ53td_.8n1pLDGe9q1DUew q1HvmG41vEoltITFZyHTbnZVsSXgEpNop3QVyo1vkXY2yJ7DqtDhQdwQSExP4VYB5H9uBN9YWOP0 K3UX.VVjxjJyEARKyyDQJDqow3bazr61i4.nz2OfxrfA3uBFm185hnNgIbxYPrtdenFJ2PU2enwm aXc7XezAacc8Hoz1_cxYbgvEFCiSWh5UsL5ERWjqSdaAtuGNNMc7jWHY85JCjAI59ZkjAGawccKO YJB2w66dnaJI_YA8S8.12G5Cu.6mW3cLltuhFrerRkNu52tNJ7cbZQY89Riql7aILFAlQHfQV5Gi Oag-- X-Sonic-MF: X-Sonic-ID: 8984ffae-7cc9-43a6-a078-3214fca5d3b9 Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.gq1.yahoo.com with HTTP; Thu, 17 Aug 2023 19:22:43 +0000 Received: by hermes--production-gq1-6b7c87dcf5-qfzfj (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 78a17d3eef107774b89aba8984949aa0; Thu, 17 Aug 2023 19:22:41 +0000 (UTC) Content-Type: text/plain; charset=us-ascii 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 (Mac OS X Mail 16.0 \(3731.700.6\)) Subject: Re: Unable to boot Pi 3b+ UPDATED From: Mark Millard In-Reply-To: Date: Thu, 17 Aug 2023 12:22:30 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8C766959-8B62-4823-A183-69CC9BA91DF5@yahoo.com> References: <6baa4f78-6648-45a2-a4c6-96bfcaeecdea@box559.com> <1DF8A97C-2CA3-4223-9194-F16C5AEB49D8@yahoo.com> To: Peter G X-Mailer: Apple Mail (2.3731.700.6) X-Rspamd-Queue-Id: 4RRZdx4Qpgz3YNK 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)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] On Aug 17, 2023, at 11:08, Peter G wrote: > Apologies for top posting, but now that I understand the problem = better, most of the stuff below is not relevant. Here's the whole issue: >=20 > Late last year there was a new hardware release of the Raspberry Pi = 3B+ board. The PMIC chip was changed; more information is here: > = https://pip.raspberrypi.com/categories/797-pcn/documents/RP-003337-PC/Pi3B= -Revision-9-PCN.pdf > The new board is Rev. 1.4, a.k.a. a020d4. >=20 > The FreeBSD image at > = http://ftp3.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/13.2/FreeBSD-13.2-= RELEASE-arm64-aarch64-RPI.img.xz > boots fine on the old Rev. 1.3 version of the board but it fails to = boot on the Rev 1.4 version. I have tried it on more than one example of = each version of the board. 1.3 boards boot fine, 1.4 boards fail to boot = and flash the green LED in 4 long - 7 short pattern. >=20 > Not sure what to do about this. Is it a known problem? Should I file a = bug report? =46rom the *.pdf document that you referenced: QUOTE Software/Firmware Changes Required This new product revision is supported in firmware versions from = September 2021 onwards. The firmware version . . . It can also be found for an image by running strings /boot/start.elf | grep VC_BUILD END QUOTE (The /boot/ path is not from FreeBSD, so replace with a FreeBSD path. Also, start4.elf is of more direct interest here.) Until the recent change in systuil/rpi-firmware , FreeBSD simply used too old of an RPI* firmware version (over 2 years old) to work for the RPi3B+ Rev 1.4 (or later) parts. I'm not aware of FreeBSD re-releasing the likes of a releng/X.Y with just updated RPi* firmware (or an updated U-Boot since such is also available now). Any solution must involve replacing the older firmware with newer firmware. But the port to package builder is not done yet --and once it is there is also distribution time after that before the update will be available. One way to do that replacement now is to get the material from the msdosfs for one of the snapshot builds that I referenced: = http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/14.0/FreeBSD-14.0= -ALPHA1-arm64-aarch64-RPI-20230811-136fc495615f-264678.img.xz or, possibly one that I've not validated that it has the new RPi* firmware and U-Boot: = http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.2/FreeBSD-13.2= -STABLE-arm64-aarch64-RPI-20230810-5abba9619cbb-256019.img.xz There is a newer stable/13 one today: = http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.2/FreeBSD-13.2= -STABLE-arm64-aarch64-RPI-20230817-31d385e78eba-256060.img.xz The main snapshot build had its own systuil/rpi-firmware build that was used. The stable/13 ones may have as well. > Mark Millard wrote on 2023-08-16 06:45: >> On Aug 16, 2023, at 01:49, Peter G = wrote: >>> Mark Millard wrote on 2023-08-15 20:25: >>>> On Aug 15, 2023, at 19:17, Peter G = wrote: >>>>> I am unable to get FreeBSD-13.2-RELEASE-arm64-aarch64 to boot on = either of two brand new Raspberry Pi 3B+ boards. (Just as a diagnostic, = I checked that both work perfectly well with Raspberry Pi OS.) I have = tried several different brands and sizes of SD card (which all boot fine = with Raspberry Pi OS). I have redone the image downloads multiple times = and verified the checksums. I burn images to the SD card on another = machine using dd with bs=3D1M. If I mount the prepared SD cards on that = other machine, I can confirm the files are readable. >>>>>=20 >>>>> I have tried both >>>>> = /ftp/releases/arm64/aarch64/ISO-IMAGES/13.2/FreeBSD-13.2-RELEASE-arm64-aar= ch64-RPI.img >>>> It may not be likely to be the issue, but you did not mention >>>> it explicitly, so . . . >>>> I instead see: >>>> = http://ftp3.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/13.2/FreeBSD-13.2-= RELEASE-arm64-aarch64-RPI.img.xz >>>=20 >>> Yes, this is what I used. Sorry to not have been more explicit; I = used unxz -k to extract the .img file before dd'ing it to the SD card. >>>=20 >>>> Note the *.xz naming. I do not see a: = FreeBSD-13.2-RELEASE-arm64-aarch64-RPI.img >>>> to download >>>> After downloading FreeBSD-13.2-RELEASE-arm64-aarch64-RPI.img.xz , >>>> using: >>>> # unxz FreeBSD-13.2-RELEASE-arm64-aarch64-RPI.img.xz >>>> would produce a: >>>> FreeBSD-13.2-RELEASE-arm64-aarch64-RPI.img >>>> That, in turn, would be dd'd to the microsd card. >>>>> and >>>>> = /ftp/releases/arm64/aarch64/ISO-IMAGES/13.2/FreeBSD-13.2-RELEASE-arm64-aar= ch64-disc1.iso. >>>> Definitely the wrong media: no RPi* firmware, no U-Boot for the >>>> aarch64 RPi* , and so on. >>>=20 >>> Lack of a boot loader would explain why I get no green LED at all = with the disc1.iso >>>=20 >>> The other image, the RPI.img one, at least tries to boot, as = evidenced by the 4 long and 7 short blinks of the green LED. As a = further diagnostic, I took that same SD card that blinks the LED and = fails to boot in the 3B+ and put it in a Pi 4, where it boots fine. >>>=20 >>> So the RPI.img, the one you suggested above, is booting and working = well in the Pi 4 but the exact same SD card fails to boot in the Pi 3B+. = Since my two Pi 3B+s both work fine with other (non-FreeBSD) images, it = seems that there must be a problem with that FreeBSD image on the PI = 3B+. Are there any known issues with the boot loader on the Pi 3B+? >>>=20 >>> Again, perhaps I'm missing something, but I don't know what else to = try. Suggestions most welcome. >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259438 comment #4 = indicates 13.2 booting >> an example (older) RPi3B+ for someone that has one. (I do not have = access to any vintage >> of RPi3B+ .) >> This, with your finding that your media does boot a RPi4B, suggests = that modern RPi*3B+'s >> have some sort of technical change that requires newer RPi* firmware = than releng/13.2 >> contains. (I do not expect that U-Boot would do the blinking = activity, for example.) >> You could try a microsd card made from a modern snapshot. If that = works, you >> could replace appropriate msdosfs material on the releng/13.2 media = with >> materials from the modern snapshot and then see if that boots. >> I've used: >> = http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/14.0/FreeBSD-14.0= -ALPHA1-arm64-aarch64-RPI-20230811-136fc495615f-264678.img.xz >> and know it has the modern RPi* firmware. Likely the following would = as well, >> but I've done nothing that would confirm or deny that: >> = http://ftp3.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/13.2/FreeBSD-13.2= -STABLE-arm64-aarch64-RPI-20230810-5abba9619cbb-256019.img.xz >> Do you have a serial console environment for the RPi3B+'s? It is hard = to get >> evidence from early problems without such. Capturing and reporting = the serial >> console output (if any) would be relevant evidence. For example, it = would >> likely be obvious if it reached the U-Boot stage or not. >>>>> Neither boots. >>>>> The first image gives green LED blinks: slow four and then fast = seven. The second never blinks. >>>>>=20 >>>>> Any advice on what I'm missing would be appreciated. >>>=20 >=20 =3D=3D=3D Mark Millard marklmi at yahoo.com