Date: Fri, 9 Apr 2021 20:33:36 +0200 From: Peter Cornelius <pcc@gmx.net> To: freebsd-arm@freebsd.org Subject: Re: JMicron jms561 umass on arm64? Message-ID: <trinity-17aa86d8-be8c-434e-9815-443ce0ce0d54-1617993216878@3c-app-gmx-bs30> In-Reply-To: <5099D78C-6656-4E4A-9F20-23F31A4397FE@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> <trinity-93090f7c-f2f9-4cec-8b27-1af7de718f7a-1617905889857@3c-app-gmx-bs32> <5099D78C-6656-4E4A-9F20-23F31A4397FE@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you, Mark,
> The RPi* situation was confusing enough, with multiple
> problems in multiple sets of firmware/kernels and
> combinations. I'm trying to not leave a fuzzy
> identification of what releases were at issue
> and what modern combinations are known to generally
> work. Folks have already spent enough time on bad
> combinations of materials in recent months.
I apologize for not having been precise in my elaborations. I now understa=
nd that
Power-on of the RPI
loads EEPROM
loads Firmware rpi-firmware-1.20210303.g20210303
loads U-Boot u-boot-rpi4-2020.10 (config.txt says kernel=3D=
u-boot.bin)
loads "FreeBSD" [3]
And each of them may or may not be able to properly provide access to USB.=
In any case, FreeBSD [3] does start, and does detect USB devices, so I'm =
happy this far.
Returning to my initial issue, what puzzles me is that I do not seem to be=
able to see the hat [2] at all while
(a) Raspbian did see it (and the disks, so I understand that the hat is in=
order),
(b) There are reports that the JMS561 [1] should be detected also by FreeB=
SD, and
(c) FreeBSD does detect any other USB device I I can find and hook up to e=
ither one of the USB3 ports (indicating that the RPI is fine).
In short, my expectation (hope?) was that I hook up the board and proceed =
with the disks, or at least be able to re-set the bus so that it finds at =
least a ugen device to build upon, but as-is, no trace of any device... I'=
m a bit lost and would appreciate any pointers.
Thanks again, and
All the best,
Peter.
=2D--
[1] I believe, https://www.jmicron.com/file/download/1026/JMS561_Product+B=
rief.pdf
[2] https://wiki.radxa.com/Dual_Quad_SATA_HAT
[3] Note: Later builds so far have not booted despite of current Firmware/=
Das U-Boot (March 2021)
FreeBSD rpi4 14.0-CURRENT FreeBSD 14.0-CURRENT #1: Tue Feb 23 02:30:31=
UTC 2021
root@rpi4:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64
[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-17aa86d8-be8c-434e-9815-443ce0ce0d54-1617993216878>