Date: Tue, 16 Mar 2021 16:44:00 +0000 From: tech-lists <tech-lists@zyxst.net> To: freebsd-arm@freebsd.org Subject: Re: rpi4b main-n245392-8423f5d4c12 won't boot due to microsd timeout [FIXED] Message-ID: <YFDgUMrSv1uHkx6A@ceres.zyxst.net> In-Reply-To: <79EB88DA-0144-4A12-B716-3CF5011F16C4@yahoo.com> References: <A2A5B0EA-3BEA-4721-9E65-83D4FBF56724.ref@yahoo.com> <A2A5B0EA-3BEA-4721-9E65-83D4FBF56724@yahoo.com> <YE%2BY4HsI5KxfTLxG@ceres.zyxst.net> <79EB88DA-0144-4A12-B716-3CF5011F16C4@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YFDgUMrSv1uHkx6A>