From owner-freebsd-arm@freebsd.org Tue Mar 16 16:44:08 2021 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1974F5B48D6 for ; Tue, 16 Mar 2021 16:44:08 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 4F0Jyv0hh4z4n0S for ; Tue, 16 Mar 2021 16:44:06 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id C36681A22 for ; Tue, 16 Mar 2021 12:44:04 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 16 Mar 2021 12:44:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= date:from:to:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=SJBTtweOy1RBAufh4LbggRq5hjl HllfXdLyh7wVdTxo=; b=qPYKi/fG3oOBcbjPjKo1YfLgoHM8xSSxvLYzyuHLpPB TqQ0ZsfL6sbPYJ39+D7ip9pl4hLQor/ojnWCriGXK4ILLHOxHr0nU0aTgA37hwG1 sSZaq8AR2y0FcnwYJPNncs2n8NdgTBtLrdrHQlsf6YO43Xm7kbfxXPOw/YEAw/ev sW77/L0B03GQbjuL+R9MyLJYC647sDyZ7pEIkVbsuOoR0aCN56gPiweHfU+KuAia f97BbWzTOAnE3ggD+izRhsGBkJk+A/PcY+FvULzKpPeqNtdtAaFSoK/xlF4RP0Lk 8FCob4gcCTEN88Lt3tU8mWw9CZ/8rsedVBW7x7dBW1A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=SJBTtw eOy1RBAufh4LbggRq5hjlHllfXdLyh7wVdTxo=; b=NWFHnB4upPUoL2Y/hFz4SE 12zYl+104Dmb7GAUSwgomcDN85n+FaSbR8Z6fO3m13SRWPzT4vpasx0uEEYzQjtr nW8Tu5E8RxhujVOsy7VyNhoAY5K51L4cyCl+BPsxc50qZx0H5QsnUzPo6n5Wkyrf TeyelL7Ml9KTmqnEWnUOL2o7eMrVdlkl1pRRSnfB5+z6ADneeIPO4LPLeFJ3z+fc 2VmgV5zPRGaRopKPxhR8VUKLK/gT8g3P0qJ9JenLCUiQY464E2G84/YfBTu4z8n1 a/tRV0aEoM29/9TnMvil2g+3yhuFuGk/xU3rWpDDYF+420y3Iec0TXihyjl5sJxA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudefvddgledvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesghdtre ertddtvdenucfhrhhomhepthgvtghhqdhlihhsthhsuceothgvtghhqdhlihhsthhsseii hiigshhtrdhnvghtqeenucggtffrrghtthgvrhhnpedthfdtheegueduffehieegudeuie fhhfetkeejtddugffghfdvieduheevfeevleenucffohhmrghinhepshhouhhrtggvfhho rhhgvgdrnhgvthdpghhithhhuhgsrdgtohhmnecukfhppeekvddrjedtrdeluddruddttd enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehtvggt hhdqlhhishhtshesiiihgihsthdrnhgvth X-ME-Proxy: Received: from ceres.zyxst.net (ceres.zyxst.net [82.70.91.100]) by mail.messagingengine.com (Postfix) with ESMTPA id D7FB1240054 for ; Tue, 16 Mar 2021 12:44:03 -0400 (EDT) Date: Tue, 16 Mar 2021 16:44:00 +0000 From: tech-lists To: freebsd-arm@freebsd.org Subject: Re: rpi4b main-n245392-8423f5d4c12 won't boot due to microsd timeout [FIXED] Message-ID: Mail-Followup-To: freebsd-arm@freebsd.org References: <79EB88DA-0144-4A12-B716-3CF5011F16C4@yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="79TQ+r8q2KPDo5o0" Content-Disposition: inline In-Reply-To: <79EB88DA-0144-4A12-B716-3CF5011F16C4@yahoo.com> X-Rspamd-Queue-Id: 4F0Jyv0hh4z4n0S X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=zyxst.net header.s=fm2 header.b=qPYKi/fG; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=NWFHnB4u; dmarc=none; spf=pass (mx1.freebsd.org: domain of tech-lists@zyxst.net designates 64.147.123.19 as permitted sender) smtp.mailfrom=tech-lists@zyxst.net X-Spamd-Result: default: False [-5.69 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[64.147.123.19:from]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.19]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; DKIM_TRACE(0.00)[zyxst.net:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-0.99)[-0.985]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[64.147.123.19:from]; ASN(0.00)[asn:11403, ipnet:64.147.123.0/24, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.19:from]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[zyxst.net:s=fm2,messagingengine.com:s=fm2]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; DMARC_NA(0.00)[zyxst.net]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[64.147.123.19:from:127.0.2.255]; MAILMAN_DEST(0.00)[freebsd-arm] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting FreeBSD to ARM processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2021 16:44:08 -0000 --79TQ+r8q2KPDo5o0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 15, 2021 at 06:50:02PM -0700, Mark Millard wrote: >So there would seem to be no urgent aspect of >existing RPi[34] u-boot ports vs. Klaus K.'s >build(s) to lead Klaus to put up reviews on >Phabricator for updates to: > >sysutils/u-boot-rpi-arm64 >sysutils/u-boot-rpi3 >sysutils/u-boot-rpi4 I don't know what (version) those ports make, as I've never=20 tested/used them. My way of working (directly updating firmware files)=20 is a hangover from the time when there was little support for the rpi4/8GB= =20 and I've just never changed my method. Maybe that needs changing. >> [1] how would I "test" the installed[2] u-boot.bin to make sure it was >> working correctly? > >I was thinking of whatever criteria you used when you >wrote: > >QUOTE >. . . >> https://sourceforge.net/projects/fbsd-rpi4-u-boot2021-04-klaus/files/u-b= oot.bin/download > >Pleased to report this new u-boot works perfectly! thank you >END QUOTE what I was looking for when I asked the question was whether you might know a method of testing it programmatically. I mean, I'm not a programmer,= =20 so I don't know where to look. I don't even know what the three firmware files do, apart from leveraging the booting process.=20 By "works perfectly", what I mean is it seems to do everything asked of it. The stable/13 machine, as well as self-hosting, runs poudriere for about 500 packages, runs mail clients, is a web server, uses usb3+zfs for additional (2Tb) storage, boots off sdcard, is clocked at 2GHz. I don't know what else to test apart from transferring files from sdmmc to usb3 storage and back and checking for crc errors, I mention because=20 there was an issue with large file transfers a while ago. >I had not quizzed you about what it takes to have the >status "works perfectly". Hopefully, the above answers that. If not, please suggest some tests to run? > (I would expect that "works perfectly" has to involve how the combination= =20 > of u-boot and RPi* firmware operate together in making the > judgment.) All I can say for certain is that this combination wget https://sourceforge.net/projects/fbsd-rpi4-u-boot2021-04-klaus/files/u-boot= =2Ebin/download -O u-boot.bin fetch https://github.com/raspberrypi/firmware/raw/0591568b29a724de406aa737fc8e13f= 68c423f3f/boot/start4.elf fetch https://github.com/raspberrypi/firmware/raw/0591568b29a724de406aa737fc8e13f= 68c423f3f/boot/fixup4.dat "work perfectly" (but see [3]), with both a stable/13 (13-n244890) GENERIC = rpi4 and current/14=20 (main-n245454) rpi4 with a GENERIC-NODEBUG kernel. >[2] has both a different u-boot and a different >group of RPi* firmware files. > >There would seem to be no urgent aspect of the >existing sysutils/rpi-firmware port vs. the >Mar 10 2021 RPI* materials to lead anyone to >put up a review on Phabricator for updating: I'm not sure either way because I don't know if or how any of the three files work when it comes to initialising usb, or sdmmc which is where I started. Additionally, main-n245454 (generic, so debug kernel) unmodified will=20 boot if there's nothing usb attached. If my usb3 disk is plugged in=20 after it boots, the pi will panic. If I reboot replacing just the u-boot=20 with Klaus's u-boot, I get the same result.=20 If I replace all 3 files with the latest versions as described in the URLs, (again generic kernel so with debug on main/14), it will still=20 panic when usb is plugged in. Presumably these "latest" files are ahead=20 of those made by ports. So, the things that are fixed for me are sdmmc initialisation (presumably u-boot fixed this) on stable/13 and usb initialisation (which making a generic kernel on main/14 fixes). [3] only thing tested on current/14 is booting and buildworld --=20 J. --79TQ+r8q2KPDo5o0 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEE8n3tWhxW11Ccvv9/s8o7QhFzNAUFAmBQ4EYACgkQs8o7QhFz NAV2nA//Ry+1aIoO1FLRHX9dZt4O/pEfaY8ql0E6wqalXIDBhYi4n9P0VqGHRZUu SSRiRZit8m1Omkk61+mP1zl+j53fK7k2KfC+SN2pAL2LPY093tn3jez+Op8o4UMj RiBV8mPrkn8qs3s7TaJ8KDLKSlTWREhoRpXVa+UXTwoZ2Umwjtinhb89NCR1cR4E MFpTIxYBGU8geXXOmzKBqCu8dQW12A15iCVez2TyOnORzPxJpeXutwReyn4RJ2G5 sTjPj8hBTaZZWbXNMHkNO+Hmp1JqGG9oQp+AN9+fbr784CutGKLuSUz34HkmAc1W jQCdh9JYdLfAHwr5lMElFwalCvCc7TohiDftLWlX+joNXOMf1jnqDFtylwj/rnb5 WURMNv0z+iZXCNaqbB/wPeHuony+p+WTkV/7LmenDe6HJ1GQhG65kCmeXWg3oyWZ pJLf1Dvguxer2zK4NsLIv/BbsObO7XouFiCJMJcqysan85Ul5OehO5j8JMA4vTig cLEm2HJTp/bL56R95vu6BdFmq++iNwCFgvK2xLi1GZz2pXrOijl2bBQfn1l5I9DM X3Vh+oE4D8cSu4vuBnX2vp8nA4g/oyBAmoAEb0rQxY5YFHmhf+/A1PSl8/YVBxeC Fgj2oVjWpsQAYyJ6RpRfylKtdz+qrIHfulLuSVIk2vwxt67rIpY= =dJi7 -----END PGP SIGNATURE----- --79TQ+r8q2KPDo5o0--