From nobody Fri Oct 21 19:53:47 2022 X-Original-To: freebsd-uboot@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 4MvFXR1lNkz4gdT7 for ; Fri, 21 Oct 2022 19:53:59 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic317-20.consmr.mail.gq1.yahoo.com (sonic317-20.consmr.mail.gq1.yahoo.com [98.137.66.146]) (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 4MvFXP4cSnz3R3m for ; Fri, 21 Oct 2022 19:53:57 +0000 (UTC) (envelope-from marklmi@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1666382035; bh=oVTrxdeoAkTJU13bw7CNxpmQmUXFyWYL+TiRGdQP3bk=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=TBsNSqLDvV9bTyy2b2KrH9apWMWqz1mn3v+2IzPsgi7du0TuRalJInIvxZIDd9fsuzIeO+IcRy2Cjde+48uT7Y9UPcwZwYOmZ7JBhy+dV5qDN3zm2r3pqVbqNBHMWHDOZPpkCNm+517TnQs27GWgDXW2l3bmEtJlFXE2XJYokTgly2uqudwUkKbFY63TgZGQDEjV+ljPXdjMMidZmxKWZR7AM25f9bp8QHm2dCO2WgKA8s0dhfO+kGRiBso/a2apnkAuk3jayEcnLzDkIex2ka9vQhRQ2Y1vzYGfjqHHlskHjKJIUnSi8FrKvvyk7sCIonFauB6qcp9N9eI/WUIFvQ== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1666382035; bh=Wck8MkZqsrVAyKe8GvjocSWY6KhhL5KCWQO7r0qxZ+2=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=OTnpcsCVEpMCcnCfgSVrKy/mxKezzEmgmsXB3Ae+etxWNvZbYS7VPEC3Y8xIy1cIf9SAve7KUfTVIpDVtEYcy8Y8xHbLhwkI3IyonuttcwhhZjEdRqR3RojaHk6v3jFB901/HskUkJCTaTf1MWVxbaXlRbKfY8vfZu8dV9BoRTbE/BRSOUrVqNfssAacDiaqSVWjW07GF/UJQiH2nH+3zssSFYuNRw2f6i8MXjpopN/pkznkxIKZzWx7kGE+pKtLL7xfe2+kgFrELL2CtQnOgAruaPQlVYEz5WwRIYMIzgNYJ5O+Yn6j3GUx2yqPNIy8GFIQIZGYmQgMxOg6RiCR4A== X-YMail-OSG: Vsfsj_sVM1mDyziuoMv.zx2qQNjB4ZUnSlwpGlfXv5.REpcN1QoJQnAg3IVH9Yu DloBr4_rwUQycBMy7Vj3p2jrZMBDlc440udcN_lTm65kxzJXroUGQIWP2I4OzFnENFHIz7adesUb lt4uAN9Sfqsu5_mjsa4LTLzOlYWKdr4pDki1_63hRSW5MLpsER4L122hc9tAmYDjjQ1QTyJdTwO5 LLutZt2GLypRc9V0GKgZPUYnJq_UKEehBvMvptcjleeRw4nsWV8oIkthpbBRnfo5Sw3rWNjAaq6T 9MMQvXQW5chzZdIT37GeGc.peq478AqQet2IsVmuO4ZvL2JxVQ0Fy.7HPLje2SLm2Yb8yNsvxcaH 5Q6TK.1.Lg1dKyOEhhSOINq2B6Xrfl6uxDuj9tS_sh3Y9b3ssUQ7WZIqxY3XuLrjOdBEXb8rTs1v FInNT4.xgGdmZ0x0jxg2gauHNh5BIs42nXfO6P_tHuFRRTzPKtTB0_PAg7BOz2EyCk99SQ_tTDQY aIIQ0VU16_QpdEHmzpMq4nRuh.HPWxC71u1heozIG.L0KxMeV2q6iVHN7Ffa0RXFHHCLvTLtiaOI mkKA0tBdSI6uXomNWtBvb.WihtudhK5r37Y8qsiXdt1wjSubKiVWA8NYLULC9Xsx7OE2aOHZHeAf vi9PGsge.OWMa3XjTz2T0xlWW_6wcXGTQjX61jO97Khi5EDrNA.uElsGJuR21f8T4Gp1cqYS3ps7 P4FFlEJLYEjXpjfpNUw3mnpJZoD5R4oqNEdVlOdRvF.lWyN62hBGy7DHEWZ8DA2Jhow_uLqgpV.N zXbqRetsV8f7vqwN32Dbg8IN.GN8bh8ZkzcNFKFoblEa1Lb6tjxSYycK_SQbNgZiDaw2ckWLW5.3 3VjoEXr3NYWK6T_02dnf_K.kYdp0ZvB5gRbCj17_pudjQZtBEtI3D_elg8U1fVsIqQ3FfW2XKFs9 ph8KMzdM17ZuyCtf6jq5XHegJor2CS6u0nsjJ2srdSb7Oz8hS2FXVdNaU_HG8t4F8F6MIWsHivmN qktkEYOVIjVCvnLdUiFb1mGGkO1dahSfgZ50ySdPTRNW13HfiFWcghr59mEKX3vDHFvekYetPhVc _LBAc3Q3jIIgsWBf4SGdE5dVxrp20HYV_9y5Fm5FDyNNsRhnrsHafoBJGLXfrqrJiT9lfb93SOkm 3n.8uRrzZfr_oXKkBIM0mOMndX2W3YpU0oP3LdXW9YM_WrERBWsB73OY.7BPWsoeeQ7yydusbfVQ 0SOSDDshuepXHACNty2uvs2UuM4x1l5wvQzaXClBiYZrK5_aBtoUUZJt9u0DOtFS9KkWPYsdxT9w jow0_LUFXuKJZ_k3UiCfM8IOMnbCphEsfseornjNSZfBSBQRno9D065dxpjnh5eJmmiNzK0QRBZ0 IemMrGiZ4MZ.Bld7PNyhit.Ox_t.eyCMcPIFxBjg9AmhOXwlP5Kl7rNlD2qia_RL47z5RdxWUnhV b6JigpJE5YIZ5.aLz4P16H9VLUdX2JBOeP0mr_jHG9BBCmjWod6v..ZMxCpTT2Mu2CH1MyD9w849 W0NHK2hWVVNCag3CXDWoVdmfBgYtzEegfNhwoX4FOdtaLgwkfsGhEKoieuW0EXnYW_vhbSXzNG.r XKK.gPooDi0qlEQOLVVRBAXsHb7BEuK1i9sVkaHlMzu7h5jLYMu.FrXKNfRdatQ6Y1vhK3sjE4Jn P1sy8Gy380XnDxXJw3HNZNIVuU9TUZEq34qhNpY8CAH6lLnYm_bIKpuQRO_nmcHPgpLnUinY9xtu uvLMGgx0Z57.z9DkrMvJrI3OukXloycH8tL_If668Hg9xlroFZ8k2JlpssaeH8iigpb.WoTEmZpA ueQn8f1H_Pc0tUCcZtzXDxWc9uItueKqeFYpfCppWQbrLnJn49phavsRdfJZ8iWlWsb4rp_66.zn 5uXWiR2rAKa4ADoDqeLEPf8Z014tU_eY0mIkCwI8WwH_Pi_FNPPuYGemoszzkD6bbmhTdGhjqd00 vFxUuX6TprRh9uB7Wn7L9SSphXjM8dnWF3Fv62YSpiqHBGdF_n76KqTNfWNqDszOMbmiMbUjusFw eTXOuc7c36_UP2SAudGRWXdn6DdJWUNLsLg5w0mXJRU8E4domdjeYPtA9ExR2EBes34vs7v0Zpo9 bmKYF8k6iF4siLtBKvuwLYbdy18lRtfko93b8DXiuFBa2P538bVVzDt9pjGKkASaYP9H_5cxLlmp uFeCrHW3jH89MZpMBpvqcZRwadGkOHJVQi_uW4vpF85PAZhh9uGanrEZeGc1YgxKXMuaxnW4pMPe 0 X-Sonic-MF: Received: from sonic.gate.mail.ne1.yahoo.com by sonic317.consmr.mail.gq1.yahoo.com with HTTP; Fri, 21 Oct 2022 19:53:55 +0000 Received: by hermes--production-bf1-64dccd5d47-s4dvw (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID 9ad4b8bb44faafddb9772161dd1180ad; Fri, 21 Oct 2022 19:53:50 +0000 (UTC) Content-Type: text/plain; charset=us-ascii List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-uboot List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-uboot@freebsd.org X-BeenThere: freebsd-uboot@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\)) Subject: Re: EDK2 on RPi3 was: Re: u-boot debug, was: Re: U-boot on RPI3, sees disk but won't boot it From: Mark Millard In-Reply-To: <20221021175142.GA62386@www.zefox.net> Date: Fri, 21 Oct 2022 12:53:47 -0700 Cc: freebsd-arm , freebsd-uboot@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: References: <20221004001857.GA7109@www.zefox.net> <62F8D709-BBC3-41C4-B1A9-939B2001BA52@yahoo.com> <1DE565E3-3906-4C53-83C8-EBC20A4E3C95@yahoo.com> <20221005034608.GA12761@www.zefox.net> <1560695E-4D99-40A1-8D62-29EAB24C7997@yahoo.com> <20221005160737.GA15227@www.zefox.net> <136B9190-4C73-45FB-8B41-FEEF7C38A253@yahoo.com> <3A76826B-B4E6-4837-915E-C9E1172BEA20@yahoo.com> <20221021175142.GA62386@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3696.120.41.1.1) X-Rspamd-Queue-Id: 4MvFXP4cSnz3R3m X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=TBsNSqLD; dmarc=pass (policy=reject) header.from=yahoo.com; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.66.146 as permitted sender) smtp.mailfrom=marklmi@yahoo.com X-Spamd-Result: default: False [-3.49 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.991]; 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)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RCVD_IN_DNSWL_NONE(0.00)[98.137.66.146:from]; 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:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; MLMMJ_DEST(0.00)[freebsd-uboot@freebsd.org] X-ThisMailContainsUnwantedMimeParts: N On 2022-Oct-21, at 10:51, bob prohaska wrote: > Mixed success has been obtained using EDK2 on a pair of Pi3 > systems, one running 13-stable and one running -current. > > The 13-stable machine is at stable/13-ef2aa7753 > The -current machine is at main-n258665-e03b7883e97c > > The 13-stable machine boots reliably with an EDK2 microSD card > and will boot almost as reliably with no microSD card at all. > This seems true with both JMS561 and JMS578 usb-serial bridges. > > The -current machine uses an ASMT bridge and is unresponsive > with either the EDK2 microSD or no microSD at all. It does boot > reliably using the "special bootcode.bin" file from the Pi foundation. > It appears to be the newer of the two Pi3's, having a non-latching > microSD receptacle. Which context does the "need bootcode.bin" problem follow? A) Where the ASMT bridge is used vs. not? B) Which RPi3B is used vs. not? C) Which OS version is used vs. not? D) It gets messier to specify if combinations of 2 or more those need to be specified. I'll not list all the possibilities. Does the newer RPi3B indicate that its USB booting has been enabled? (You may need to use the likes of a RaspiOS variant to check this.) I'm confused about the "special bootcode.bin": bootcoce.bin is a normal part of the RPi* firmware, just ignored by RPi4B related RPi*'s that have an alternate means of doing things. Is this the bootcode.bin in the standard RPi* firmware releases? Some other version? bootcode.bin always has more recent, bugfixed USB boot code than a RPi3B has built in, as far as I know. The RPi3B's do not have a supported means of updating what is built-in for such functionality. bootcode.bin is used instead. > On balance EDK2 appears to be useful, or at least having some > promise. I'm glad it seems to have helped. But there are things to know. Point #0: EDK2 versions and testedness The only tested RPi3B EDK2 versions are the ones that the developers release. They do not test EDK2 updates after they make an EDK2 release, at least until they again work on making a new RPi3B EDK2 release. Similarly, they do not test using newer RPi* firmware than they bundle. Only a small subset of the overall RPi* firmware is in their RPI3B release. For example, a lack of most of the overlays. They do have references to at least using one overlay that they do not include, as I remember. But use of any other overlays is untested/not-supported as far as I can tell. The same goes for the RPi4B related EDK2 releases vs. later EDK2 updates vs. overlays and such. The RPi3B vs. RPi4B EDK2 releases are not based on the same vintage of EDK2 materials --or on the same vintage of RPi* materials. This means that using the FreeBSD port will not pick out the release-matching EDK2 materials as are in the RPi3B or RPI4B EDK2 releases. Also, the RPi* firmware has to be separately supplied. Overall: an untested combination results, a combination that is unsupported by the RPi3B EDK2 developers and the RPi4B EDK2 developers. I've no clue if or how well the the port's builds might work. Another issue is that some software that is upstream of EDK2 tends to have problems staying inside the C language definition and when this happens, EDK2 builds fail, despite it not being EDK2's own code that needs the fix. Point #1: RPi3B microsd slot use is messed up In my RPi3B EDK2 related testing, trying to use a microsd card in the RPi3B slot for such can corrupt the contents. It does not even reliably lead to even correct file name displays in ls output. By contrast, using a USB reader/writer continued to work just fine. So just leave a RPi3B EDK2 microsd card in the slot after booting. I've no clue of the status for things like sound and such. Point #2: RPi4B does not even start to use the microsd card In my RPi4B EDK2 use, microsd card in the slot are not supported --by being ignored as I remember. By contrast, using a USB reader/writer continued to work just fine. So just leave a RPi4B EDK2 microsd card in the slot after booting. I've no clue of the status for things like sound and such. > Bugzilla traffic suggests work is stalled, can it be > unstuck? > I expect that at some point that some variation on my patches to allow the builds to at least complete will be committed so the likes of aarch64 FreeBSD builds become possible. (So long as EDK2+its-upstream stays inside the language definition.) But I do not know how useful builds are now when built on amd64 or the like --that will also be true for the aarch64 built ones. See the above "Point #0: EDK2 versions and testedness" notes. It may end up being more effective to stick to downloading and using releases made by the RPi3B EDK2 and RPi4B EDK2 folks if EDK2 is to be used for these RPi* families. === Mark Millard marklmi at yahoo.com