From nobody Fri Dec 16 00:26:30 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 4NY8zs2d77z4jclf for ; Fri, 16 Dec 2022 00:26:49 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic315-55.consmr.mail.gq1.yahoo.com (sonic315-55.consmr.mail.gq1.yahoo.com [98.137.65.31]) (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 4NY8zq6nHsz4YFZ for ; Fri, 16 Dec 2022 00:26:47 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=CmimbpYC; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.65.31 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=1671150406; bh=BjEVVyk2auN+8O6hn2cTvLGDv5+o3IKOwYqLaQMendQ=; h=From:Subject:Date:References:To:In-Reply-To:From:Subject:Reply-To; b=CmimbpYCzcHkyo59as6hIbfxTAG8rC3gtwXC+W0hqG/K6WHpO2pW8cZxE+37lOApPHkdakeQvoPTXqClJsebBzkWo9FEwKKTNObgDAUVtWlYql2Acdc5VnMEoDOR01oFnZUVBi2o7OdiRq6X+1wYlHj/cBS46ZtAuzdHhMGhhmmW+PS/lYqF4khGivNk5zbBjTH84oJwbKkaF5pV+WpAFcyMnzkzZZhIt0cpDbhSaY5itzK/kA1Exh93Zo1BnWR67K5184YZ1PGVHRqtSgk2vm7CydSR2U/o6+z7uoBxv08sp1IIdPJh/QEWDks1o4O+ksKAhiMTpoh9U6TvuwIG8Q== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1671150406; bh=gjobIiE99kQPNv/JR1JNGEpee7eWdetZRZHtSrZeYE6=; h=X-Sonic-MF:From:Subject:Date:To:From:Subject; b=QSl9d3oczvYiRCqNiuP6TjnXEDLsFdLE+sBEI0faBDQXWPa5FFvcxC++hRfkVcN0QQlpcB3QdsYNN7u78x6rtEX2XopRGiBG64C8aMguGia6M5EbznJPP/XJvQbgRSvbCOHEIrtR3ysbKurqg59E70XuL+rZe4s3DQfY2wVciuDOmn2RNFNxdmFCa3r2ZwNIUxjEDcBBedvd/8sBul6cBWfpcXLhgW1S1vPaHxeq7m769lzmg4aa7/15G8A/h3Ufo7qOooAUQiM3Dy2wkR4on/ToMwXWGXsksfO5hKJFIw0H56D1gG8NrSjiQsZy8G1AcrqpzeDru23QRu6w1bkAEg== X-YMail-OSG: WbZWB6kVM1mL.xX0ZTXWAng17qC_xd1jLuFzGzfXcJmyo677xYASUdlRW7lWnyK 503cOtf6SAU5u657PcP984EAT5wqxVHMLWUoV2e5XaHt__vyETWp6Lkl6U03.EB69SXYtxLLTQvx nDzkFfJn1R791nyGaGjvbSVFHcYz4.N2z_BEqg6BukXiNC55_gjAFK5ZSLF7iDOyerC5mA_0LV2h SuNB7iSNcX0zjvay.xcpQayHvBDtR6X9wFHvAYqUh1KxUwsA9cap8OvlyMM0SHqRbAlQapoF8IiM 1we1ehblgMda.Bd7ctd5bbhzTA3mjUceKv0cqhb73nRnITIo0lvRddXdU0MHAHX6W6m_2jIKuvLJ MqEngWpDjyrQ0E7zzcWlb4lZ8YocIBWpVnzxsBm9Rm9EMWJfPuDLQGDYfcGGnLlrh6FPYA4eX6hD Fj0HhXLtPIFxf7AcgwD4hQWHNIuizNanMVLAlPzqlwbxCFfQML7vl9diKll1lVX.NlOdNDyrgiPg l6f_BfkufucZWfW89N7pVQpDNnkn885ZNtmw6lf5qnhH6fWI0MIqDVFFESiFLrikrvFAdL8bzgnw BcrHjHwe0BKfAvGqYN9cWkRCt2jxIgmQ44x2YXEz13xZQ1DVXzLTGhsgn2EvTfJVx3EBl.ejLnjS TRAL8f8eCUnLyBBBj7d0QReFCaYOIiQ9A6ZrDYQIAJDOsSPipjF6GtjOfy4DAHcuz5.V41zYE1M9 Zne.V3eONJItXVYDl.wKSQCm1x.Tx7ygrOIFxBWEtkzIArwfFhk0aUwQAkBr7IT0OjYBMfoRSphu d6VRBgFewjgWIZogjcdhXkCqM36lmncgVwfId5CzW0ZIQ2szlu4G0BWKo.eBaSd_zRc0ji1jqOK2 89z_WNshtHquEao6NzV5HMB.6IT6lZYTDR_5txwiWfkpxs466FvShNWWA5.kGskUsPJKDXht4I1P rF488TnzbhzJQ.3XXH.7mHu05ngZaLOtR3QgcXIg.D9ZZpPXRX2ct60Q1.2uqasvfv5kOAqkaJJd tbRCPXG5ctZ2r94_e0zNkNEZ_vjMe5NBBzcDjV9plU2cxT5GMbxYbXxuYudHX17DXzMbDSYcImNf jiJmkmUh.thPJBD.2MbFHrgwdsa2DsrtPWspWeY7osrf.QkqOKUZwZWeCGIcjg_fLrJl5zF7A.JP dx4nJ_yWusUkDtYnR.5gdyJrFWXdI5CauTCUXExQr1Qs_tf46VMDtJWEZrjjceaa3d3wqUskAE_H zIllt_OE4.e3ryknhIqXxmUisD5S7Nec9qrDlbx14QpY7AGNagL2RjGZnw1vUPO_Jlyvfo3bjtCu gnaNUzlodpoblj6JodnQivVXy2tHOqKAVCmexab9AJHvXT9d0ikTcCLnUW094mHjbr.z1AYk2Ovp YetvvgNb0GdjlHYDrkY9V4JBqGHLwtzlKoNfThDn0TOABktLJOtaJ7GJ03iTt9K52.P6nSG2kGKl fJ6qy512aKg38Hb87wGJu0jcPmgG.f3l7PTeCLvFWuq6wzwNnZ.U85_QmEOqzUB8uqyYDrHme4eF lsOWAQ1wEQAM5XflP.8nj3ah6bXRGoTO_JtPO5ywbrf4hXLFwtOt8LXUiep18EOKiGHNPXNf1C2. wZEIKWXO4VPlmADurO52404JcCUYv_eLQCmta._B2QsJgur3jPgdfcBcZOSCAG5Z8RqCcpYBB9VY w6e1fQBVV.KcmYrRtFB9TbBE9XEsnTZFbPYS2l7byZw5EjkrHfueKd0Ev84lMI4gTML8qNhN9kaL 0jv7AJ7C_mMqihxZcBeB_peP8rhQ_yL_nY0bWhqAZgN0eyXgRsN6pUQv4UxicJ.PzBpQU1dB2hOC 0w7qPSpnDlCnFcklTrCcrDj7z5EyDfa0QjthC9FEoiYO2b51o4yOJQZ8fEn4A1m4dmReUahJ_cSa LoWru_PtR0z_Lq_OZ3llgA_dnYOcMgh7ENi8LMudyJg10cVsdk2YIM_3WnYJPDb4Y61QZDEuv2NU OPzLevPaiFvl8dbHR4R2zGHYKt_tCbvxlEkU_Lme7GmFqwmlJXdoI9tqfsfTLMgkWu0xGGSGqgK0 zKDipRfDqrUVGhZBtmGJAmBDa1oMKsslxz8BVGmk1VKe9Bm9QwYiOaF7tobU4Gz6Cv1MeObhPWH6 pnm84VeI3lmWEC2O3ieRfNhJZLSQjUh0miC2l9nmv.eSWN4yMF.271P7a1kAHzJHZOnOiAOqIfq5 JD6u2x3BOtRygoM_8cHE3UT0qvAL3bo8j2wm1GjLF3qAWCeQnzPUNlcjpDO2UA0OQLDoKMGWQu0x r.Q-- X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Fri, 16 Dec 2022 00:26:46 +0000 Received: by hermes--production-gq1-d898c4779-4ndbh (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID faccd2cbf2de17518198ab35d1ed9a53; Fri, 16 Dec 2022 00:26:41 +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: Re: armv6/armv7/aarch64 vs. FreeBSD images (retitled from an arch reply, moving to freebsd-arm list) Date: Thu, 15 Dec 2022 16:26:30 -0800 References: To: jhs@berklix.com, freebsd-arm In-Reply-To: Message-Id: <995C856D-B030-48C6-B369-26A8E7233379@yahoo.com> X-Mailer: Apple Mail (2.3731.200.110.1.12) X-Spamd-Result: default: False [-3.41 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.91)[-0.905]; MV_CASE(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; MIME_GOOD(-0.10)[text/plain]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.31:from]; RCVD_COUNT_THREE(0.00)[3]; FREEMAIL_FROM(0.00)[yahoo.com]; TO_DN_SOME(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; DKIM_TRACE(0.00)[yahoo.com:+]; FROM_EQ_ENVFROM(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org] X-Rspamd-Queue-Id: 4NY8zq6nHsz4YFZ X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On Dec 13, 2022, at 22:45, Mark Millard wrote: > 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. I tried using the USB3 FreeBSD media I have for booting both a RPi2B v1.1 (native armv7) and a OrangePi+2ed by plugging it into a RPi4B: U-Boot 2022.10 (Oct 21 2022 - 01:23:47 +0000) DRAM: 947 MiB RPI 4 Model B (0xd03115) Core: 200 devices, 12 uclasses, devicetree: board . . . Net: No ethernet found. starting USB... No working controllers found Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 MMC Device 1 not found no mmc device at slot 1 MMC Device 2 not found no mmc device at slot 2 starting USB... No working controllers found USB is stopped. Please issue 'usb start' first. starting USB... No working controllers found . . . starting USB... No working controllers found No ethernet found. No ethernet found. U-Boot> So U-Boot is not set up to deal with the RPi4B's differing USB hardware. It did not make it to the FreeBSD loader. Thus, effectively, the BCM2711 family is limited to aarch64 FreeBSD. > FreeBSD image name pattern: *-arm-armv6-RPI-B* > 12.* FreeBSD image name pattern: *-arm-armv7-RPI2* > 13.*+ FreeBSD image name pattern: *-arm-armv7-GENERICSD* The above 3 are not appropriate for the BCM2711 based family. > 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