Date: Wed, 16 Feb 2022 20:19:15 +0800 From: Archimedes Gaviola <archimedes.gaviola@gmail.com> To: "Daniel O'Connor" <darius@dons.net.au> Cc: mike@karels.net, freebsd-arm@freebsd.org Subject: Re: Raspberry Pi 4B does not detect devices in USB 3.0 Message-ID: <CAJFbk7GJw8RATGdZW8kXiVQnSyo_pj4EOfSXVNyVGX3oeWHfRQ@mail.gmail.com> In-Reply-To: <CAJFbk7FmYC4=SAnwss4XCR6RAE__bBdiisiQPjt2Xm63_7uffA@mail.gmail.com> References: <CAJFbk7E=t4ezXVgTTGQdsxNbAEgUJfRU5Phk=gy4m2ovBMzhww@mail.gmail.com> <202112231500.1BNF0FgX014693@mail.karels.net> <CAJFbk7EAoit=e-14sg7YGHMtf7qWA5VjDgnnn4xt9tMERjt17Q@mail.gmail.com> <E3005D55-FE54-4911-89C7-1E017975A1CA@dons.net.au> <CAJFbk7FFtq9xQW9rWZM5Vx-wQ09B47zkwPWrjzLnbNfAFeCvhw@mail.gmail.com> <CAJFbk7ERFyf1DGP4E4=F295o7YLOUCcZxi0JpWZPoz52JhK_AA@mail.gmail.com> <D9CA3262-2827-465F-9A3B-C200150EB77A@dons.net.au> <CAJFbk7FmYC4=SAnwss4XCR6RAE__bBdiisiQPjt2Xm63_7uffA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000002784ec05d821a9dc Content-Type: text/plain; charset="UTF-8" On Tue, Feb 15, 2022 at 6:47 PM Archimedes Gaviola < archimedes.gaviola@gmail.com> wrote: > > On Tue, Feb 15, 2022 at 6:22 AM Daniel O'Connor <darius@dons.net.au> > wrote: > >> >> >> > On 14 Feb 2022, at 23:10, Archimedes Gaviola < >> archimedes.gaviola@gmail.com> wrote: >> > I just tried my new RPI4 board and it seems to work fine the same as my >> old board. I just observed that the problem is when my VFD (vacuum >> fluorescent display) device is connected to either of the two USB 3.0 >> ports, this device having uplcom(4) driver is not detected. >> >> I wonder if the VFD is causing interference - it likely has a high >> voltage supply and those are notorious for generating electrical noise. >> >> > It's a Prolific USB-serial device having PL2303 chipset. However, when >> plugged-in to USB 2.0 ports, this device is detected and functioning. I can >> send characters with the echo command and redirect it to /dev/cuaU0 for >> display without any problem. Other observations when this VFD device is >> connected to either 3.0 ports, the 2.0 ports will not function i.e. >> plugging-in any USB devices like my keyboard or my EMV reader. When this >> device is also connected to either of the 2.0 ports, the other 2.0 port is >> functioning for other USB devices while 3.0 ports are not. I attached two >> dmesg outputs when the device is detected with 2.0 ports and undetected >> with 3.0. I also include kldstat and usbdump. >> >> I would be curious if putting the VFD on a longer cable, or wrapping the >> cable through a ferrite, or using an external hub fixes it. >> >> Any of those would give a bit more isolation between the VFD and USB3 >> hardware. >> > > Thanks Daniel for your recommendations, I've tried extending it to a long > cable and using an external USB hub however the outcomes were still the > same, it cannot be detected. As per checking, this device has a default > ferrite bead clamped over its USB cable. > > Using the same RPI 4B hardware, this VFD device has been tested as well > with OpenBSD 6.9 and CentOS 8. They both work with USB 3.0 except OpenBSD > system will panic the first time you plug-in the device but will work fine > after a forced reboot or when you unplug and plug back the power. > > Thanks, > Archimedes > Based on Fred's recommendation here https://lists.freebsd.org/archives/freebsd-arm/2022-February/001010.html with FreeBSD 14.0-CURRENT, my VFD device is now detected and functioning in 3.0 while the rests of the ports are now functioning as well with my other USB devices. So, I will now close this raised concern. Hoping this working state will still be available until release. Thanks for your inputs and support! Best regards, Archimedes --0000000000002784ec05d821a9dc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"></div><br><div class=3D"gmail_quote"><div= dir=3D"ltr" class=3D"gmail_attr">On Tue, Feb 15, 2022 at 6:47 PM Archimede= s Gaviola <<a href=3D"mailto:archimedes.gaviola@gmail.com">archimedes.ga= viola@gmail.com</a>> wrote:<br></div><blockquote class=3D"gmail_quote" s= tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad= ding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"></div><br><div class=3D"gm= ail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Feb 15, 2022 at 6:= 22 AM Daniel O'Connor <<a href=3D"mailto:darius@dons.net.au" target= =3D"_blank">darius@dons.net.au</a>> wrote:<br></div><blockquote class=3D= "gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2= 04,204,204);padding-left:1ex"><br> <br> > On 14 Feb 2022, at 23:10, Archimedes Gaviola <<a href=3D"mailto:arc= himedes.gaviola@gmail.com" target=3D"_blank">archimedes.gaviola@gmail.com</= a>> wrote:<br> > I just tried my new RPI4 board and it seems to work fine the same as m= y old board. I just observed that the problem is when my VFD (vacuum fluore= scent display) device is connected to either of the two USB 3.0 ports, this= device having uplcom(4) driver is not detected.<br> <br> I wonder if the VFD is causing interference - it likely has a high voltage = supply and those are notorious for generating electrical noise.<br> <br> > It's a Prolific USB-serial device having PL2303 chipset. However, = when plugged-in to USB 2.0 ports, this device is detected and functioning. = I can send characters with the echo command and redirect it to /dev/cuaU0 f= or display without any problem. Other observations when this VFD device is = connected to either 3.0 ports, the 2.0 ports will not function i.e. pluggin= g-in any USB devices like my keyboard or my EMV reader. When this device is= also connected to either of the 2.0 ports, the other 2.0 port is functioni= ng for other USB devices while 3.0 ports are not. I attached two dmesg outp= uts when the device is detected with 2.0 ports and undetected with 3.0. I a= lso include kldstat and usbdump.<br> <br> I would be curious if putting the VFD on a longer cable, or wrapping the ca= ble through a ferrite, or using an external hub fixes it.<br> <br> Any of those would give a bit more isolation between the VFD and USB3 hardw= are.<br></blockquote><div><br></div><div>Thanks Daniel for your recommendat= ions, I've tried extending it to a long cable and using an external USB= hub however the outcomes were still the same, it cannot be detected. As pe= r checking, this device has a default ferrite bead clamped over its USB cab= le.<br></div><div><br></div><div>Using the same RPI 4B hardware, this VFD d= evice has been tested as well with OpenBSD 6.9 and CentOS 8. They both work= with USB 3.0 except OpenBSD system will panic the first time you plug-in t= he device but will work fine after a forced reboot or when you unplug and p= lug back the power.<br></div><div>=C2=A0</div><div>Thanks,</div><div>Archim= edes<br></div></div></div></blockquote><div><br></div><div>Based on Fred= 9;s recommendation here <a href=3D"https://lists.freebsd.org/archives/freeb= sd-arm/2022-February/001010.html">https://lists.freebsd.org/archives/freebs= d-arm/2022-February/001010.html</a> with FreeBSD 14.0-CURRENT, my VFD devic= e is now detected and functioning in 3.0 while the rests of the ports are n= ow functioning as well with my other USB devices. So, I will now close this= raised concern. Hoping this working state will still be available until re= lease.</div><div><br></div><div>Thanks for your inputs and support!</div><d= iv><br></div><div>Best regards,<br></div><div>Archimedes <br></div><div>=C2= =A0<br></div></div></div> --0000000000002784ec05d821a9dc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJFbk7GJw8RATGdZW8kXiVQnSyo_pj4EOfSXVNyVGX3oeWHfRQ>