Re: Raspberry Pi 4B does not detect devices in USB 3.0
Date: Fri, 24 Dec 2021 04:32:41 UTC
On Fri, Dec 24, 2021 at 10:49 AM Daniel O'Connor <darius@dons.net.au> wrote: > > > > On 24 Dec 2021, at 02:25, Archimedes Gaviola < > archimedes.gaviola@gmail.com> wrote: > > Are you using the boot files that came with 13.0 (dtb, etc)? > > > > Yes, I am. I have not changed anything that came from 13.0 files, it's > all intact since I wrote the image to the microSD card. > > > > To be specific with my USB devices, this is an input and an output > device. I have an RFID card reader and an Epson TM-U22B USB printer > (self-powered) which are detected and work well with USB 2.0. Below dmesg > log shows the drivers of my printer and RFID card reader. As soon as these > devices are transferred to the blue-colored USB 3.0 ports these drivers > will no longer show up in the dmesg. > > > > ugen0.3: <EPSON EPSON UB-U03II> at usbus0 > > ugen0.4: <Sycreader RFID Technology Co., Ltd SYC IDIC USB Reader> at > usbus0 > > ukbd0 on uhub1 > > ukbd0: <USB Standard Keyboard> on usbus0 > > kbd1 at ukbd0 > > uhid0 on uhub1 > > uhid0: <USB Vender Hid> on usbus0 > > For what it's worth I have successfully used USB devices on the USB3 ports > with FreeBSD 13 on an RPi4: > ugen0.1: <0x1106 XHCI root HUB> at usbus0 > ... > uhub0 on usbus0 > uhub0: <0x1106 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 > ... > uhub1 on uhub0 > uhub1: <vendor 0x2109 USB2.0 Hub, class 9/0, rev 2.10/4.21, addr 1> on > usbus0 > uhub1: 4 ports with 4 removable, self powered > ugen0.3: <PixArt Microsoft USB Optical Mouse> at usbus0 > ugen0.4: <BTC USB Multimedia Keyboard> at usbus0 > ukbd0 on uhub1 > ukbd0: <BTC USB Multimedia Keyboard, class 0/0, rev 1.10/1.00, addr 3> on > usbus0 > kbd1 at ukbd0 > > I have also used a custom Cypress FX2 based board on it with no problems. > > -- > Daniel O'Connor > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > Thanks Daniel for sharing your experience with your RPi4! My next step will be to secure another board (with the same specs) and check if it behaves the same. I'll burn another 13.0 image to further verify just in case it still fail.