From nobody Wed Feb 16 12:19:15 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id F1FA519B98B5 for ; Wed, 16 Feb 2022 12:19:28 +0000 (UTC) (envelope-from archimedes.gaviola@gmail.com) Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JzH7z6XVxz3HQ5 for ; Wed, 16 Feb 2022 12:19:27 +0000 (UTC) (envelope-from archimedes.gaviola@gmail.com) Received: by mail-ed1-x52a.google.com with SMTP id q17so3612506edd.4 for ; Wed, 16 Feb 2022 04:19:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CRbZ9YUmhgebkxRO1nIjaNEru76NbYO4hV+QlZS+cXg=; b=T6oQhnAX17JcjV8QX2aUNRtcJOK243LvadIVgjxxg/iZt4Di+imYz8sb4QNkNcHrau rQ8gxsOGlq3H8Ks4Gdz8VplAR2alffhsqqPN7bICbRgDacMg00bPu3sCCb/0fueQUfFd QaB8TP7UzoY/2R9xzBBImmRgVbterkEqee/SXvYAxnc3HRFOXwzrwa+gnTbQei+3HsWt 6eIlf7p+owGdjcBtMR3vFvjHoYY9+DqpPuMA2jbmOyRBm8rDTK5lOD95mFPphkinsojw WmdQHj++ETkCcUPucXYH6u9hrhrhCM9gU6dlPm7UA3NSKKFqg/sUJ3SRWck5e8yaZqpR WxVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CRbZ9YUmhgebkxRO1nIjaNEru76NbYO4hV+QlZS+cXg=; b=ZZFKjXcmQQ4SDjplsw/GOs816zNbF8Q+vpL3KUN5xwcAq9lYvttWVGBgOPcYHZ3brf /sJlRKbWi6IuP/Jh+fVtQg+FGh7PYfPsnCE4R+zuSXfzz0jmuPtBH0d0YW6qaVrBusDQ 0AUsWpUJLnuWlOq9LFlHsu1sZxF1VaGFIviA8QYaMcnBK8t/14NpO7tr0pqCubJx/QFk LwjdQt9jbxxS3rrpTFeZrahEzpPligqbEiKzvGSBi9CtrRZ8ag4Yxr339cXQWjg3wiaX SadSBWKJMODeL2nGLEt1KV/KDTzUqu1co5GHGvPAybkbGWpJ8f3xZftooDMw+liT2LwP TtaQ== X-Gm-Message-State: AOAM532yOrmZRbnlOADxjEAka9/jfl52Ov84niDsKI/DzveqEDKLQFzV VwKN5GBFUrseaJvszTRSvNfO7OYA18hAXwkytkIyF20TnEADUQ== X-Google-Smtp-Source: ABdhPJwKLx9YbzaDyHw35yAqArW5TKXy4w05bPmM1OnTccTnv8A6KIjmBo/1Jed/+RN6AHtM2vU4mjOhmVsbyd6aUdo= X-Received: by 2002:aa7:d80f:0:b0:410:d5c3:f770 with SMTP id v15-20020aa7d80f000000b00410d5c3f770mr2662139edq.279.1645013967012; Wed, 16 Feb 2022 04:19:27 -0800 (PST) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: <202112231500.1BNF0FgX014693@mail.karels.net> In-Reply-To: From: Archimedes Gaviola Date: Wed, 16 Feb 2022 20:19:15 +0800 Message-ID: Subject: Re: Raspberry Pi 4B does not detect devices in USB 3.0 To: "Daniel O'Connor" Cc: mike@karels.net, freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="0000000000002784ec05d821a9dc" X-Rspamd-Queue-Id: 4JzH7z6XVxz3HQ5 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=T6oQhnAX; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of archimedesgaviola@gmail.com designates 2a00:1450:4864:20::52a as permitted sender) smtp.mailfrom=archimedesgaviola@gmail.com X-Spamd-Result: default: False [-4.00 / 15.00]; TO_DN_SOME(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::52a:from]; MLMMJ_DEST(0.00)[freebsd-arm]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --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 > 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

On Tue, Feb 15, 2022 at 6:47 PM Archimede= s Gaviola <archimedes.ga= viola@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 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.

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 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.

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.

Any of those would give a bit more isolation between the VFD and USB3 hardw= are.



Based on Fred= 9;s recommendation here https://lists.freebsd.org/archives/freebs= d-arm/2022-February/001010.html 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.

Thanks for your inputs and support!

Best regards,
Archimedes
=C2= =A0
--0000000000002784ec05d821a9dc--