Pine64 and USB bug

Mark Millard marklmi at yahoo.com
Mon Jul 8 08:23:59 UTC 2019



On 2019-Jul-7, at 13:08, Milan Obuch <freebsd-arm at dino.sk> wrote:

> Hi,
> 
> on both Pine64 and Pine64-LTS I observed a problem with USB ports. Both
> board have two ports, lower one (nearer to PCB) works, but upper one
> does not. Running 'usbconfig' gives me
> 
> ugen0.1: <Allwinner EHCI root HUB> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
> ugen1.1: <Generic OHCI root HUB> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
> ugen2.1: <Allwinner EHCI root HUB> at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
> ugen3.1: <Generic OHCI root HUB> at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
> 
> so both are detected, but only one works - with USB flash put in, line
> 
> ugen2.2: <Kingston DataTraveler 2.0> at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (300mA)
> 
> gets added. Upper port (probably ugen0 and ugen1 in listing above) is
> enabled, at least partially - using USB meter shows there is 5 V
> sourced, but looks like no data communication is taking place.
> 
> Any hint, anybody? This was FreeBSD 13.0-CURRENT r349025 GENERIC,
> snapshot downloaded from ftp.freebsd.org.

The following older build also only has the lower USB port working
on the Pine64+ 2GB that I have access to:

# uname -apKU
FreeBSD Pine64OrRPI3 13.0-CURRENT FreeBSD 13.0-CURRENT #4 r343670M: Fri Feb  1 17:04:23 PST 2019     markmi at FBSDFSSD:/usr/obj/cortexA53_clang/arm64.aarch64/usr/src/arm64.aarch64/sys/GENERIC-NODBG  arm64 aarch64 1300010 1300010

But, ss I remember, the 1-USB-port-usable status has been true
much longer than that . . . Looking . . .

Head -r324563 is where ECHI was (re-)enabled on the lower port.
The note from -r323641 still applied back then:

QUOTE:
This (plus 323640) re-enable OHCI on Pine64 on the bottom USB port.
The top USB port is routed to the OHCI0/EHCI0 which is by default in OTG mode.
While the phy code can handle the re-route to standard OHCI/EHCI we still need
a driver for musb to probe and configure it in host mode.
:END QUOTE

It may be that the status for the top port is still unchanged.

(This is based on an old 2017-Oct-23 list message that I sent
out at the time. I'd forgotten the details until I found that
message.)


===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)



More information about the freebsd-arm mailing list