From nobody Wed Dec 14 06:45:14 2022 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 4NX5Tl4S6Vz4l24H for ; Wed, 14 Dec 2022 06:45:31 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic317-22.consmr.mail.gq1.yahoo.com (sonic317-22.consmr.mail.gq1.yahoo.com [98.137.66.148]) (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 4NX5Tk5QHDz3l6G for ; Wed, 14 Dec 2022 06:45:30 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=W9k7vulW; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.66.148 as permitted sender) smtp.mailfrom=marklmi@yahoo.com; dmarc=pass (policy=reject) header.from=yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1671000328; bh=0+M0uj6RT+op36ymfCjGON/IoSTA3+ln3wwL+p3Z7ns=; h=From:Subject:Date:To:References:From:Subject:Reply-To; b=W9k7vulWTGoHAebRh8XvT57NVsdX4vBtBhqrJw/aLxMvCGWniVNt5CM7SbcpPlWZv3bASI14bCAkGrk+8meV+A048mPWkmyBIlXygBQyDr1Oa9mr28wsuqCWbijXVSKirZWcbjKf7Qb2pe/BqqYGq1FpccWzD8v+IX71Eoc9mn6iDyfQqkTPMVG6NsesQWEUcjJF4CzpdtYh6hH6qGg7zFgwyzFSRZIGN4GVj69zz9FahtOlnLBg8VUHSJyRUlW5vvA0Crx/YdNAfFdrHSiC2//O3UZ60jkJ5qFXc6TJnz7xcO/VZ9lDAhoYzjOOnwKViqsZl7aOG4bbASY2qKu3bQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1671000328; bh=VbfWuo4TmssOjEJA3LXdhaHLFuXEuVsZsdtm4KJCNyJ=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=RBMeeoc4oQi5NuxaYnrmy+SCxx+Yg7JRvv7Txcz2/1UBI/6yW2ix54CCRDGnAEheHK3X8G/XxZWV/PMqMwYpkyZpS7vEUZNXA0XoalS5ceCNkPQe+nIIeHDzgVHGJlkR0BHwlZb3iyhJIEI8mTMH/r06Aqc6ukLvJZPgo74O/GepQ9QjPfks6/utDJIy10mbdEEO48J49uqkwBakRXNXAfPFvK7e4X0ef1oF1P/qXOGNgPu3HNu5pcrzUt7DavLTO1ZPAlskqgwgGbD9aorP6Y9/OPMrFLAi+smUs2rx6qQ9LWyr4c4cv54CXN5MRFFirSssFikCjg+qYiXSWoWsdw== X-YMail-OSG: CL1U7LUVM1kKWcTDqvjnccurlqMhfVwvTdmAqivP5fEm82nCVE3AtqJYVGHa364 VAj6.JC3cNMimeNTNUKGJChBmu_pX0rCYL.IzBl_pnqyv4dE0HRXLDhZpDL6FDvKZws5PJL93U1O QfWXJigN78SwljNu4uSDNZnjhx3Ickn0ytNrJa8DEViZCN4BsbwsYFu5ujQ7cPgSwQozwt6ms6gv W4chOvmR4iPF3QspSBVAMreLp4jRhrSwoLH.qDk1qZzXowGhvN6S7xu3umbMxNfOkh5Je9jJtEWX _SaUQ8JzngLenlBrJnifJlfWcpQ_7ebTJ1BL9B.mky04Zm6c._ZCZV1I1bkHrGbqevqB3oPbvJWl wQ5DRh4V5DOPKGGOE6jvJrq7pkD82BaKdSgE6oc4JtLMWWU77yBHvCsjaQGGMtub9D561fMUzu71 lknhb47CTgxaR8PHHSqZNfhxDr_B6IZutSmd_B6HrlPY4pVlBLFfjyyoLsZ2gvbJB0hx9O98Up1h rIl6cFvJjzkrfRfe2u0ppYa5ZgOQQS6uU6et147c6EmVRUPPKzs.h2ZB7zRVqp53d4nILNctyHBQ epwuIiEgqU4CFI7Ba.El1usynlMBG1gnao4WUa3MNig0yXvUt8Ou6AdOg5RGnhDkPAHg2KI.zCpJ ig8iwwJ.ByJHN55.EevCXy6dQfq5yIeDv.5P0QQhtffrjSmu4tLqQMsYnmLprdwIqndxhidUrUil bHAzWni0zlDrlQfBzNz6eBdzxVwBOg76NzL._k.WgFyctQSyasRkqJa12jNenI7_QHcqnUUoKmpa tDEnGhMRlt9MxOIWsxBd8jYxZRlCnslGIJ9GeWQS566Ay0wedKLhsAbeQiP26iGSrB3oPYWwsG_r g1aTW2yCtvKo9LOLETaehH4c2nve9K1pkjGy5EsezwU.BdUd4PKSbTpPi.k5EexZXrKM8Pe0jLNP vFrONR1r2ngTy51XJRCF75dfTitq5XnASzLZDY9HcrHBvO7A8M1j98XG.GQiZC_hS_BzAhANldhC pOBszxsGkDlykHd7QnYOfleIJLmwwNgF3_ooFrLTME76rYDoOHWHAmTKHChCoBpwDaLnjz2mDaV0 PgvdAMrA5z5GWs7vMlrMnZEkUkGFlb6XZm46uHXqxh.ySe.p3RZtQab2elBxAV7a8Nj7FG4onwDH ZHbPZkCA_gccTOurES_iT2yS9888KvvPnbu8JuXrWTZBUcCRo8MevDYEEELNu6alqL.30_Omrsg4 OW7yHjzyTtg0gTZUIVs0eYs.M7fA7ttf2pcHMWTeIDYI3JOTFvGIb_eVnQSI1g2HD15VgkqGz.RS q2ZYj7qRr32_vfKiwJ.ED5OppnoIlnpjFao0QUiH6TpQGh5PHViwQE48th6s9vWXk_J8CxHOu4b8 fKRs04fEskCevciKQG0CDRlljgxmzh2klpWCKEBFVEXMnzdjz0uv6f5g65iby3XQRAFM0TlXIF3O 1LAtxb40GZPEyuhjlyRzj63kFZngX5BpZpfXHYIvaqwLL_vYPFR33YGe8RGGWvEcjY5lj1KlsMkE aQbpVg_VsH4M9x7n588gP8WtmpSOPzoR0Ri4Oi7I1bWockDEcqGJQfDKGL0WD3GliqQp9k0Z12zk .cM51u1vkd73x.biKsdb1QhESTQBKkwX7Mxg_mPupSGXVRP3Y1Ansb0cFi7hpwfgu945KgBL2Y6d _uXtYxcM8gfHcAQ1bEa1MCkZRVf3YvvIkAVr8Lm.4KRJ0_Nt9R2jLv55Y2JQ7a6XdfO9cdbUWR1A YOkrbq844szL2jiNsnVXrz2.5uVy98aX8zvmtemvDRytdcGwNT.BGapKCPUz5EFYkDr.MMxOJhql X0bgPeBlz.00KmsDkEG9V_U2UB8ITCFLxZsXudSrNuYI8kQfkLvC6FZZP7dKeh0bQphkEon0RFu2 SxemOBfv9zXXBRob.WWJaOdYOAjORs82XqpE4Zg2RBKP4mILPM849grvpC5Djb0273ogX_5roQ8P 2dZMrjyZJsrjpmTRItutU5y6_zgiiXksVgilYHzwS9qrAAmH.XJqHEnMWTrd4PBSXN40BJ9K1rUc OFUKQmzfq1a68lrRajsiPBx_IdV6oYSpx.02m1ALADPkyfrVBwjKrVYIIcCnqyOIfsc3e9CGFbfV Mutw7jhs3no6x9TyznkHeU5hY8OBIVHj9AcS7AJK5qR5IfM_W9zN4GZfShYNR2S5m048PSQoFKWk nrjn_zZGJcGk888bdzkXMQXKfHXpdsGYUYjovlxUZhTfTfCpVdYtjwU34jvtp4MTMmjSUDNOQ X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Wed, 14 Dec 2022 06:45:28 +0000 Received: by hermes--production-gq1-d898c4779-kmgvg (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 3c7fe901b0250bd508d3f87207f029e5; Wed, 14 Dec 2022 06:45:25 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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.200.110.1.12\)) Subject: armv6/armv7/aarch64 vs. FreeBSD images (retitled from an arch reply, moving to freebsd-arm list) Message-Id: Date: Tue, 13 Dec 2022 22:45:14 -0800 To: jhs@berklix.com, freebsd-arm X-Mailer: Apple Mail (2.3731.200.110.1.12) References: X-Spamd-Result: default: False [-3.38 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.88)[-0.885]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; RCVD_IN_DNSWL_NONE(0.00)[98.137.66.148:from]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[yahoo.com]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[yahoo.com:+]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; MIME_TRACE(0.00)[0:+]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.66.148:from] X-Rspamd-Queue-Id: 4NX5Tk5QHDz3l6G X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Julian H. Stacey wrote on Date: Wed, 14 Dec 2022 02:22:10 UTC : > Hi, Reference: >> From: Mark Millard >> Date: Tue, 13 Dec 2022 15:52:16 -0800 > > . . . > > Extending wordings associated with each Pi dd image, would be very > welcome, to specificaly list all hardware version of a Pi each image > of v6, v7, aarch64, the image should boot. For FreeBSD support, a U-Boot build that is compatible is needed. U-Boot is via ports, with only a few preassembled combinations of U-Boot variant and FreeBSD produced officially. (Statements not limited to RPi*'s.) U-Boot materials are not part of FreeBSD but are used (even: needed) by FreeBSD. The RPi* firmware has a similar status: it is a port: rpi-firmware . It is not part of FreeBSD itself. A combination of RPi* firmware, U-Boot varient, and FreeBSD are needed overall. (The RPi* firmware can adjust some of the Device Tree before handing things over to U-Boot. U-Boot can adjust/add more before handing that off to the FreeBSD loader. FreeBSD does not handle all valid Device Trees from what I can tell --and this limits what range of RPi* firmware that FreeBSD avoids crashing with.) What armv6/armv7/aarch64 RPi's there are/have-been, no matter if a RPi*-firmware/U-Boot/FreeBSD combination has been shown to work or not: (I freely use my own abbreviations of official naming.) armv6 (BCM2835/BCM2708): RPiA, RPiB, RPiA+, RPiB+, CM, RPiZero v1.2, RPiZero v1.3, RPiZeroW (Note: https://www.raspberrypi.com/products/ does not list any of these as EOL yet. CM3 and CM1 are listed as "in production but not recommended for new designs".) FreeBSD image name pattern: *-arm-armv6-RPI-B* (and no others) No one may have evidence of the support status for each armv6 above. I've no evidence for any of them from anything like modern times. The port rpi-firmware has the files below (and more) in a vintage that matches with FreeBSD's implementation of the FDT (Device Tree) handling: bcm2708-rpi-b-plus.dtb bcm2708-rpi-b-rev1.dtb bcm2708-rpi-b.dtb bcm2708-rpi-cm.dtb bcm2708-rpi-zero-w.dtb bcm2708-rpi-zero.dtb Note: I do not know how to classify the RP2040 Dual-core Cortex-M0+ processor parts: they are armv6-M (M is for: microcontroller). So I did not list: RPiPico, RPiPicoW, or RP2040. No *.dtb name suggests which would support any of them. armv7 (BCM2836/BCM2709): RPi2B <= v1.1, CM2 (Note: https://www.raspberrypi.com/products/ list it as "in production but not recommended for new designs".) FreeBSD image name pattern: *-arm-armv6-RPI-B* 12.* FreeBSD image name pattern: *-arm-armv7-RPI2* 13.*+ FreeBSD image name pattern: *-arm-armv7-GENERICSD* (All should work for RPi2B <= v1.1 .) (No others) Note: *-arm-armv7-GENERICSD* is basically a rename of *-arm-armv7-RPI2* (relative to RPi* issues). I've no clue if anyone has CM2 evidence. The port rpi-firmware has the file below (and more) in a vintage that matches with FreeBSD's implementation of the FDT (Device Tree) handling: bcm2709-rpi-2-b.dtb The port rpi-firmware does not supply the file: bcm2709-rpi-cm2.dtb So the CM2 is missing something likely essential. (But the *.dtb need not be sufficient by itself.) (The file goes back to 2018-Mar-22 for its first commit on github.) aarch64 (BCM2837/BCM2710 family): RPi2B v1.2, RPi3A+, RPi3B, RPi3B+, CM3, CM3Lite, CM3+, CM3+Lite, RPiZero2, (BCM2710A1): RPiZero2W, (BCM2711 family): RPi4B, CM4, CM4Lite, CM4S, RPi400 (Note: https://www.raspberrypi.com/products/ does not list any of these as EOL yet. Nor any as not recommended for new designs.) Note: aarch64 RPi*'s can boot via RapsiOS 32-bit or RaspiOS64. (I've no clue if FreeBSD can do similarly for the BCM2711 family but it has handled BCM2837/BCM2710 contexts used as armv7 historically.) ("RaspiOS" is my abbreviation.) In part this is a U-Boot issue. RaspiOS and RaspiOS64 do not use U-Boot. U-Boot could potentially block FreeBSD from operating for a 32-bit addressing OS variant. FreeBSD image name pattern: *-arm-armv6-RPI-B* 12.* FreeBSD image name pattern: *-arm-armv7-RPI2* 13.*+ FreeBSD image name pattern: *-arm-armv7-GENERICSD* 12.* FreeBSD image name pattern: *-arm64-aarch64-RPI3* 13.*+ FreeBSD image name pattern: *-arm64-aarch64-RPI* Note: *-arm-armv7-GENERICSD* is basically a rename of *-arm-armv7-RPI2* (relative to RPi* issues). Note: *-arm64-aarch64-RPI* is basically a rename of *-arm64-aarch64-RPI3* (relative tp RPi* issues). No one may have evidence of the support status for each aarch64 above. I have some evidence only for RPi2B v1.2, RPi3B, some RPi4B. (All work for *-arm64-aarch64-RPI* last I checked.) The port rpi-firmware has the files below (and more) in a vintage that matches with FreeBSD's implementation of the FDT (Device Tree) handling: bcm2710-rpi-2-b.dtb bcm2710-rpi-3-b-plus.dtb bcm2710-rpi-3-b.dtb bcm2710-rpi-cm3.dtb bcm2711-rpi-4-b.dtb bcm2711-rpi-400.dtb bcm2711-rpi-cm4.dtb The port rpi-firmware does not supply the files: bcm2710-rpi-zero-2-w.dtb bcm2710-rpi-zero-2.dtb bcm2711-rpi-cm4s.dtb So the RPiZero2, RPiZero2W, and CM4S are missing something likely essential. (But the *.dtb need not be sufficient by itself.) > As a newbie to Raspberry Pi (but not FreeBSD) I have long been confused > which image is for which version of Pi hardware. The RPi3B+ should be able to use any of: FreeBSD image name pattern: *-arm-armv6-RPI-B* 12.* FreeBSD image name pattern: *-arm-armv7-RPI2* 13.* FreeBSD image name pattern: *-arm-armv7-GENERICSD* 12.* FreeBSD image name pattern: *-arm64-aarch64-RPI3* 13.* FreeBSD image name pattern: *-arm64-aarch64-RPI* But I've no evidence of my own of the actual results. (No access to such a part.) The *-arm64-aarch64-* ones are a more complete match to the hardware: for example supporting 64-bit addressing instead of 32-bit. > I previously had some kind of a 3B, & now have a "Pi 3 Model B+", > but have not got beyond booting images, starting to customise /etc/ > & then it crashes yet again, needing yet another dd, & repeat, > Being certain one is using the right image would be nice. This does not sound normal at all. I expect something more specific to your context is involved. > My notes: http://www.berklix.org/~jhs/pi/#images I'll look at the notes separately, possibly not tonight. === Mark Millard marklmi at yahoo.com