Date: Thu, 8 Apr 2021 09:23:55 -0700 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: freebsd-arm@freebsd.org Subject: Re: JMicron jms561 umass on arm64? Message-ID: <694B7C84-E627-4E17-9148-4C4BB54FAD17@yahoo.com> In-Reply-To: <20210408150934.GA99223@www.zefox.net> References: <trinity-96292338-af50-4ea1-a4cf-0afcd97dfe35-1617806989816@3c-app-gmx-bs02> <20210407153732.GA50562@www.zefox.net> <trinity-2bcace35-09e8-4e81-87be-53287568c3c1-1617827433585@3c-app-gmx-bs02> <20210407211513.GA53438@www.zefox.net> <trinity-c3148d05-2413-4522-b67d-8be37f8c0dad-1617868014706@3c-app-gmx-bs02> <A2E9C605-ABB3-40E3-931C-7FB10CDD0990@yahoo.com> <20210408150934.GA99223@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Apr-8, at 08:09, bob prohaska <fbsd at www.zefox.net> wrote: > On Thu, Apr 08, 2021 at 02:00:29AM -0700, Mark Millard via freebsd-arm = wrote: >>=20 >>=20 >> I expect that until you have the above RPi firmware build >> in place on the firmware-boot-stage media, all other >> efforts are going to be messed up by the older firmware. >> (I've no clue if the RPi firmware is a sufficient fix by >> itself for your context even with a modern FreeBSD >> relateive to what was fixed, but the RPi firmware likely >> is a necessary part of the overall fix.) >>=20 >=20 > I forgot to mention that before initially booting FreeBSD on > my Pi4B I booted it with RasPiOS and ran sudo apt update/upgrade. > That likely fixed the firmware on the Pi without intelligent=20 > intervention. How would booting RasPiOS via RasPiOS media and running apt update/upgrade automatically update the firmware that is on the FreeBSD media, files like start4.elf on the msdos file system on FreeBSD boot media? I was not writing of things like the eepprom update that enables USB booting on older RPi*'s that did not support such initially. I explicitly mentioned start4.elf and "firmware-boot-stage media". Unless there were more steps than described, I doubt the activity updated what I was refering to. > At that point=20 > FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20210304-483c6da3a20-257149.img > booted without memorable problems. That image is too old to be generally well behaved for USB (quoted from a older list message): QUOTE FreeBSD-14.0-CURRENT-arm64-aarch64-RPI-20210304-483c6da3a20-257149.img contains: # strings /mnt/start4.elf | grep VC_BUILD_ID_ VC_BUILD_ID_USER: dom VC_BUILD_ID_TIME: 22:19:57 VC_BUILD_ID_VARIANT: start VC_BUILD_ID_TIME: Jan 27 2021 VC_BUILD_ID_BRANCH: bcm2711_2 VC_BUILD_ID_HOSTNAME: buildbot VC_BUILD_ID_PLATFORM: raspberrypi_linux VC_BUILD_ID_VERSION: 99d9a48302e4553cff3688692bb7e9ac760a03fa (clean) END QUOTE I'll remind that the USB problems had issues with USB keyboards and such, not just booting from USB drives. Unless you go back far enough into last year, the RPi* firmware needs to that vintage that has: # strings start4.elf | grep VC_BUILD_ID_ VC_BUILD_ID_USER: dom VC_BUILD_ID_TIME: 12:10:40 VC_BUILD_ID_VARIANT: start VC_BUILD_ID_TIME: Feb 25 2021 VC_BUILD_ID_BRANCH: bcm2711_2 VC_BUILD_ID_HOSTNAME: buildbot VC_BUILD_ID_PLATFORM: raspberrypi_linux VC_BUILD_ID_VERSION: 564e5f9b852b23a330b1764bcf0b2d022a20afd0 (clean) (or possibly later, status unknown). > HTH, >=20 > bob prohaska >=20 >=20 >> Note the lack of referencing u-boot in the above: so far >> as I know u-boot was working fine over the time that >> the RPi firmware was badly behaved, not that such was >> obvious at the time. It just did not need to be changed >> from what was officially built over the time frame. >=20 =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?694B7C84-E627-4E17-9148-4C4BB54FAD17>