Date: Thu, 8 Apr 2021 20:18:09 +0200 From: Peter Cornelius <pcc@gmx.net> To: freebsd-arm@freebsd.org Subject: Aw: Re: JMicron jms561 umass on arm64? Message-ID: <trinity-93090f7c-f2f9-4cec-8b27-1af7de718f7a-1617905889857@3c-app-gmx-bs32> In-Reply-To: <694B7C84-E627-4E17-9148-4C4BB54FAD17@yahoo.com> 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> <694B7C84-E627-4E17-9148-4C4BB54FAD17@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you, Mark and Bob, > >> 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.) > >> > > > > 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 > > 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. I think we may have some confusion here. There was some sort of EEPROM fir= mware upgrade [4] which I also did last round Raspbian was up (either Jan = 11 or Feb 16). I also had to do that last year (August?) in order to make = the RPI4 boot FreeBSD at all. I think the EEPROM upgrade tool is too Linux= ish and does not run under FreeBSD (at least I failed). > 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) I am aware of bug 252971 [5] and can confirm that I do have this version. = Actually built on March 3 this year. Before that, I had to go back to some= September? October? U-Boot to get the box back up running with USB (such = as to use my USB keyboard & mouse, for instance). I just connected a USB3 hub with a USB2 memstick and a USB3 disk to the US= B3 hub of the RPI4, and both storage devices are detected immediately on e= ither USB3 port of the RPI4. Which gives me a sensation of looking in the wrong spot... Thanks again, and All the best, Peter. [4] https://jamesachambers.com/raspberry-pi-4-bootloader-firmware-updating= -recovery-guide/ [5] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252971
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?trinity-93090f7c-f2f9-4cec-8b27-1af7de718f7a-1617905889857>