Raspberry Pi 3 B+ ethernet

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Raspberry Pi 3 B+ ethernet

James Hastings
Hello all

I acquired a Raspberry Pi 3 Model B Plus recently
and have been working on enabling the onboard ethernet.

mue0 at uhub2 port 1 configuration 1 interface 0 "Standard
Microsystems LAN7800" rev 2.10/3.00 addr 4
mue0: LAN7800, address b8:27:eb:xx:xx:xx
ukphy0 at mue0 phy 1: Generic IEEE 802.3u media interface, rev. 2: OUI
0x0001f0, model 0x0013

The device is ignored in uhub_explore() because it is not
seen as connected unless device is reset first.

I have two ways to enable the chip and both are ugly hacks to uhub(4)
that apply to all ports on all hubs. I chose option 2.
1) Force CONNECTED status and change bits after checking status, or
2) Reset and delay all ports once before checking status.

What should a proper fix for this be?

dmesg and usbdevs before and after respectively

OpenBSD 6.4-current (UHUB_DEBUG) #20: Mon Nov 26 09:53:59 EST 2018
    xxx@xxx:/usr/src/sys/arch/arm64/compile/UHUB_DEBUG
real mem  = 961417216 (916MB)
avail mem = 902909952 (861MB)
mainbus0 at root: Raspberry Pi 3 Model B Plus Rev 1.3
cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4
cpu0: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu0: 512KB 64b/line 16-way L2 cache
efi0 at mainbus0: UEFI 2.7
efi0: Das U-Boot rev 0x20180900
simplefb0 at mainbus0: 656x416, 32bpp
wsdisplay0 at simplefb0 mux 1
wsdisplay0: screen 0-5 added (std, vt100 emulation)
simplebus0 at mainbus0: "soc"
bcmintc0 at simplebus0
bcmdog0 at simplebus0
bcmrng0 at simplebus0
pluart0 at simplebus0
bcmtemp0 at simplebus0
bcmaux0 at simplebus0
com0 at simplebus0: ns16550, no working fifo
com0: console
dwctwo0 at simplebus0
simplebus1 at mainbus0: "clocks"
agtimer0 at mainbus0: tick rate 19200 KHz
cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4
cpu1: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu1: 512KB 64b/line 16-way L2 cache
cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4
cpu2: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu2: 512KB 64b/line 16-way L2 cache
cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4
cpu3: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu3: 512KB 64b/line 16-way L2 cache
usb0 at dwctwo0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Broadcom DWC2 root hub" rev
2.00/1.00 addr 1
uhub0: 1 port with 1 removable, self powered
uhub0: port 1 status=0x0101 change=0x0001
uhub0: intr status=0
uhub0: port 1 status=0x0503 change=0x0000
uhub1 at uhub0 port 1 configuration 1 interface 0 "Standard
Microsystems product 0x2514" rev 2.00/b.b3 addr 2
uhub1: 4 ports with 3 removable, self powered, multiple transaction translators
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: port 1 status=0x0101 change=0x0001
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: port 1 status=0x0503 change=0x0000
uhub1: intr status=0
uhub2 at uhub1 port 1 configuration 1 interface 0 "Standard
Microsystems product 0x2514" rev 2.00/b.b3 addr 3
uhub2: 3 ports with 2 removable, self powered, multiple transaction translators
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub2: port 1 status=0x0100 change=0x0000
uhub2: port 2 status=0x0100 change=0x0000
uhub2: port 3 status=0x0100 change=0x0000
uhub1: port 2 status=0x0101 change=0x0001
uhub1: intr status=0
uhub1: intr status=0
uhub1: port 2 status=0x0503 change=0x0000
umass0 at uhub1 port 2 configuration 1 interface 0 "FUJIFILM Mass
Storage Device" rev 2.00/11.00 addr 4
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <FUJIFILM, 16GB, 1100> SCSI2 0/direct
removable serial.
sd0: 15468MB, 512 bytes/sector, 31678464 sectors
uhub1: port 3 status=0x0100 change=0x0000
uhub1: port 4 status=0x0100 change=0x0000
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
bootfile: sd0a:/bsd
boot device: sd0
root on sd0a (.a) swap on sd0b dump on sd0b
Controller /dev/usb0:
addr 01: 0000:0000 Broadcom, DWC2 root hub
         high speed, self powered, config 1, rev 1.00
         driver: uhub0
         port 01: 0000.0503 connect enabled power
addr 02: 0424:2514 Standard Microsystems, product 0x2514
         high speed, self powered, config 1, rev b.b3
         driver: uhub1
         port 01: 0000.0503 connect enabled power
         port 02: 0000.0503 connect enabled power
         port 03: 0000.0100 power
         port 04: 0000.0100 power
addr 03: 0424:2514 Standard Microsystems, product 0x2514
         high speed, self powered, config 1, rev b.b3
         driver: uhub2
         port 01: 0000.0100 power
         port 02: 0000.0100 power
         port 03: 0000.0100 power
addr 04: 8564:1000 FUJIFILM, Mass Storage Device
         high speed, power 500 mA, config 1, rev 11.00, iSerialNumber
         driver: umass0

------------------------------------------------------------------------------
OpenBSD 6.4-current (UHUB_DEBUG) #17: Mon Nov 26 08:02:22 EST 2018
    xxx@xxx:/usr/src/sys/arch/arm64/compile/UHUB_DEBUG
real mem  = 961417216 (916MB)
avail mem = 902914048 (861MB)
mainbus0 at root: Raspberry Pi 3 Model B Plus Rev 1.3
cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4
cpu0: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu0: 512KB 64b/line 16-way L2 cache
efi0 at mainbus0: UEFI 2.7
efi0: Das U-Boot rev 0x20180900
simplefb0 at mainbus0: 656x416, 32bpp
wsdisplay0 at simplefb0 mux 1
wsdisplay0: screen 0-5 added (std, vt100 emulation)
simplebus0 at mainbus0: "soc"
bcmintc0 at simplebus0
bcmdog0 at simplebus0
bcmrng0 at simplebus0
pluart0 at simplebus0
bcmtemp0 at simplebus0
bcmaux0 at simplebus0
com0 at simplebus0: ns16550, no working fifo
com0: console
dwctwo0 at simplebus0
simplebus1 at mainbus0: "clocks"
agtimer0 at mainbus0: tick rate 19200 KHz
cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4
cpu1: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu1: 512KB 64b/line 16-way L2 cache
cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4
cpu2: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu2: 512KB 64b/line 16-way L2 cache
cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4
cpu3: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
cpu3: 512KB 64b/line 16-way L2 cache
usb0 at dwctwo0: USB revision 2.0
uhub0 at usb0 configuration 1 interface 0 "Broadcom DWC2 root hub" rev
2.00/1.00 addr 1
uhub0: 1 port with 1 removable, self powered
uhub0: intr status=0
uhub0: port 1 status=0x0503 change=0x0001
uhub0: intr status=0
uhub0: intr status=0
uhub0: port 1 status=0x0503 change=0x0002
uhub1 at uhub0 port 1 configuration 1 interface 0 "Standard
Microsystems product 0x2514" rev 2.00/b.b3 addr 2
uhub1: 4 ports with 3 removable, self powered, multiple transaction translators
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: port 1 status=0x0503 change=0x0001
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: port 1 status=0x0503 change=0x0000
uhub1: intr status=0
uhub1: intr status=0
uhub2 at uhub1 port 1 configuration 1 interface 0 "Standard
Microsystems product 0x2514" rev 2.00/b.b3 addr 3
uhub2: 3 ports with 2 removable, self powered, multiple transaction translators
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub2: port 1 status=0x0101 change=0x0001
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub2: port 1 status=0x0503 change=0x0000
uhub1: intr status=0
mue0 at uhub2 port 1 configuration 1 interface 0 "Standard
Microsystems LAN7800" rev 2.10/3.00 addr 4
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
mue0: LAN7800, address b8:27:eb:xx:xx:xx
uhub1: intr status=0
ukphy0 at mue0 phy 1: Generic IEEE 802.3u media interface, rev. 2: OUI
0x0001f0, model 0x0013
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub2: port 2 status=0x0100 change=0x0000
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub2: port 3 status=0x0100 change=0x0000
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: intr status=0
uhub1: port 2 status=0x0503 change=0x0001
uhub1: intr status=0
uhub1: port 2 status=0x0503 change=0x0000
umass0 at uhub1 port 2 configuration 1 interface 0 "FUJIFILM Mass
Storage Device" rev 2.00/11.00 addr 5
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0: <FUJIFILM, 16GB, 1100> SCSI2 0/direct
removable serial.
sd0: 15468MB, 512 bytes/sector, 31678464 sectors
uhub1: port 3 status=0x0100 change=0x0000
uhub1: port 4 status=0x0100 change=0x0000
vscsi0 at root
scsibus1 at vscsi0: 256 targets
softraid0 at root
scsibus2 at softraid0: 256 targets
bootfile: sd0a:/bsd
boot device: sd0
root on sd0a (.a) swap on sd0b dump on sd0b
WARNING: CHECK AND RESET THE DATE!
Controller /dev/usb0:
addr 01: 0000:0000 Broadcom, DWC2 root hub
         high speed, self powered, config 1, rev 1.00
         driver: uhub0
         port 01: 0002.0503 connect enabled power
addr 02: 0424:2514 Standard Microsystems, product 0x2514
         high speed, self powered, config 1, rev b.b3
         driver: uhub1
         port 01: 0000.0503 connect enabled power
         port 02: 0000.0503 connect enabled power
         port 03: 0000.0100 power
         port 04: 0000.0100 power
addr 03: 0424:2514 Standard Microsystems, product 0x2514
         high speed, self powered, config 1, rev b.b3
         driver: uhub2
         port 01: 0000.0503 connect enabled power
         port 02: 0000.0100 power
         port 03: 0000.0100 power
addr 04: 0424:7800 Standard Microsystems, LAN7800
         high speed, self powered, config 1, rev 3.00
         driver: mue0
addr 05: 8564:1000 FUJIFILM, Mass Storage Device
         high speed, power 500 mA, config 1, rev 11.00, iSerialNumber
         driver: umass0

Reply | Threaded
Open this post in threaded view
|

Re: Raspberry Pi 3 B+ ethernet

Jonathan Gray-11
On Tue, Nov 27, 2018 at 05:10:20AM -0500, James Hastings wrote:

> Hello all
>
> I acquired a Raspberry Pi 3 Model B Plus recently
> and have been working on enabling the onboard ethernet.
>
> mue0 at uhub2 port 1 configuration 1 interface 0 "Standard
> Microsystems LAN7800" rev 2.10/3.00 addr 4
> mue0: LAN7800, address b8:27:eb:xx:xx:xx
> ukphy0 at mue0 phy 1: Generic IEEE 802.3u media interface, rev. 2: OUI
> 0x0001f0, model 0x0013
>
> The device is ignored in uhub_explore() because it is not
> seen as connected unless device is reset first.
>
> I have two ways to enable the chip and both are ugly hacks to uhub(4)
> that apply to all ports on all hubs. I chose option 2.
> 1) Force CONNECTED status and change bits after checking status, or
> 2) Reset and delay all ports once before checking status.
>
> What should a proper fix for this be?

I suspect a proper fix would be somewhere in dwc2.
NetBSD supposedly works with mue(4) on dwc2 with the 3b+, might be worth
comparing dwc2 changes.

>
> dmesg and usbdevs before and after respectively
>
> OpenBSD 6.4-current (UHUB_DEBUG) #20: Mon Nov 26 09:53:59 EST 2018
>     xxx@xxx:/usr/src/sys/arch/arm64/compile/UHUB_DEBUG
> real mem  = 961417216 (916MB)
> avail mem = 902909952 (861MB)
> mainbus0 at root: Raspberry Pi 3 Model B Plus Rev 1.3
> cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4
> cpu0: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
> cpu0: 512KB 64b/line 16-way L2 cache
> efi0 at mainbus0: UEFI 2.7
> efi0: Das U-Boot rev 0x20180900
> simplefb0 at mainbus0: 656x416, 32bpp
> wsdisplay0 at simplefb0 mux 1
> wsdisplay0: screen 0-5 added (std, vt100 emulation)
> simplebus0 at mainbus0: "soc"
> bcmintc0 at simplebus0
> bcmdog0 at simplebus0
> bcmrng0 at simplebus0
> pluart0 at simplebus0
> bcmtemp0 at simplebus0
> bcmaux0 at simplebus0
> com0 at simplebus0: ns16550, no working fifo
> com0: console
> dwctwo0 at simplebus0
> simplebus1 at mainbus0: "clocks"
> agtimer0 at mainbus0: tick rate 19200 KHz
> cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4
> cpu1: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
> cpu1: 512KB 64b/line 16-way L2 cache
> cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4
> cpu2: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
> cpu2: 512KB 64b/line 16-way L2 cache
> cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4
> cpu3: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
> cpu3: 512KB 64b/line 16-way L2 cache
> usb0 at dwctwo0: USB revision 2.0
> uhub0 at usb0 configuration 1 interface 0 "Broadcom DWC2 root hub" rev
> 2.00/1.00 addr 1
> uhub0: 1 port with 1 removable, self powered
> uhub0: port 1 status=0x0101 change=0x0001
> uhub0: intr status=0
> uhub0: port 1 status=0x0503 change=0x0000
> uhub1 at uhub0 port 1 configuration 1 interface 0 "Standard
> Microsystems product 0x2514" rev 2.00/b.b3 addr 2
> uhub1: 4 ports with 3 removable, self powered, multiple transaction translators
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: port 1 status=0x0101 change=0x0001
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: port 1 status=0x0503 change=0x0000
> uhub1: intr status=0
> uhub2 at uhub1 port 1 configuration 1 interface 0 "Standard
> Microsystems product 0x2514" rev 2.00/b.b3 addr 3
> uhub2: 3 ports with 2 removable, self powered, multiple transaction translators
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub2: port 1 status=0x0100 change=0x0000
> uhub2: port 2 status=0x0100 change=0x0000
> uhub2: port 3 status=0x0100 change=0x0000
> uhub1: port 2 status=0x0101 change=0x0001
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: port 2 status=0x0503 change=0x0000
> umass0 at uhub1 port 2 configuration 1 interface 0 "FUJIFILM Mass
> Storage Device" rev 2.00/11.00 addr 4
> umass0: using SCSI over Bulk-Only
> scsibus0 at umass0: 2 targets, initiator 0
> sd0 at scsibus0 targ 1 lun 0: <FUJIFILM, 16GB, 1100> SCSI2 0/direct
> removable serial.
> sd0: 15468MB, 512 bytes/sector, 31678464 sectors
> uhub1: port 3 status=0x0100 change=0x0000
> uhub1: port 4 status=0x0100 change=0x0000
> vscsi0 at root
> scsibus1 at vscsi0: 256 targets
> softraid0 at root
> scsibus2 at softraid0: 256 targets
> bootfile: sd0a:/bsd
> boot device: sd0
> root on sd0a (.a) swap on sd0b dump on sd0b
> Controller /dev/usb0:
> addr 01: 0000:0000 Broadcom, DWC2 root hub
> high speed, self powered, config 1, rev 1.00
> driver: uhub0
> port 01: 0000.0503 connect enabled power
> addr 02: 0424:2514 Standard Microsystems, product 0x2514
> high speed, self powered, config 1, rev b.b3
> driver: uhub1
> port 01: 0000.0503 connect enabled power
> port 02: 0000.0503 connect enabled power
> port 03: 0000.0100 power
> port 04: 0000.0100 power
> addr 03: 0424:2514 Standard Microsystems, product 0x2514
> high speed, self powered, config 1, rev b.b3
> driver: uhub2
> port 01: 0000.0100 power
> port 02: 0000.0100 power
> port 03: 0000.0100 power
> addr 04: 8564:1000 FUJIFILM, Mass Storage Device
> high speed, power 500 mA, config 1, rev 11.00, iSerialNumber
> driver: umass0
>
> ------------------------------------------------------------------------------
> OpenBSD 6.4-current (UHUB_DEBUG) #17: Mon Nov 26 08:02:22 EST 2018
>     xxx@xxx:/usr/src/sys/arch/arm64/compile/UHUB_DEBUG
> real mem  = 961417216 (916MB)
> avail mem = 902914048 (861MB)
> mainbus0 at root: Raspberry Pi 3 Model B Plus Rev 1.3
> cpu0 at mainbus0 mpidr 0: ARM Cortex-A53 r0p4
> cpu0: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
> cpu0: 512KB 64b/line 16-way L2 cache
> efi0 at mainbus0: UEFI 2.7
> efi0: Das U-Boot rev 0x20180900
> simplefb0 at mainbus0: 656x416, 32bpp
> wsdisplay0 at simplefb0 mux 1
> wsdisplay0: screen 0-5 added (std, vt100 emulation)
> simplebus0 at mainbus0: "soc"
> bcmintc0 at simplebus0
> bcmdog0 at simplebus0
> bcmrng0 at simplebus0
> pluart0 at simplebus0
> bcmtemp0 at simplebus0
> bcmaux0 at simplebus0
> com0 at simplebus0: ns16550, no working fifo
> com0: console
> dwctwo0 at simplebus0
> simplebus1 at mainbus0: "clocks"
> agtimer0 at mainbus0: tick rate 19200 KHz
> cpu1 at mainbus0 mpidr 1: ARM Cortex-A53 r0p4
> cpu1: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
> cpu1: 512KB 64b/line 16-way L2 cache
> cpu2 at mainbus0 mpidr 2: ARM Cortex-A53 r0p4
> cpu2: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
> cpu2: 512KB 64b/line 16-way L2 cache
> cpu3 at mainbus0 mpidr 3: ARM Cortex-A53 r0p4
> cpu3: 32KB 64b/line 2-way L1 VIPT I-cache, 32KB 64b/line 4-way L1 D-cache
> cpu3: 512KB 64b/line 16-way L2 cache
> usb0 at dwctwo0: USB revision 2.0
> uhub0 at usb0 configuration 1 interface 0 "Broadcom DWC2 root hub" rev
> 2.00/1.00 addr 1
> uhub0: 1 port with 1 removable, self powered
> uhub0: intr status=0
> uhub0: port 1 status=0x0503 change=0x0001
> uhub0: intr status=0
> uhub0: intr status=0
> uhub0: port 1 status=0x0503 change=0x0002
> uhub1 at uhub0 port 1 configuration 1 interface 0 "Standard
> Microsystems product 0x2514" rev 2.00/b.b3 addr 2
> uhub1: 4 ports with 3 removable, self powered, multiple transaction translators
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: port 1 status=0x0503 change=0x0001
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: port 1 status=0x0503 change=0x0000
> uhub1: intr status=0
> uhub1: intr status=0
> uhub2 at uhub1 port 1 configuration 1 interface 0 "Standard
> Microsystems product 0x2514" rev 2.00/b.b3 addr 3
> uhub2: 3 ports with 2 removable, self powered, multiple transaction translators
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub2: port 1 status=0x0101 change=0x0001
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub2: port 1 status=0x0503 change=0x0000
> uhub1: intr status=0
> mue0 at uhub2 port 1 configuration 1 interface 0 "Standard
> Microsystems LAN7800" rev 2.10/3.00 addr 4
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> mue0: LAN7800, address b8:27:eb:xx:xx:xx
> uhub1: intr status=0
> ukphy0 at mue0 phy 1: Generic IEEE 802.3u media interface, rev. 2: OUI
> 0x0001f0, model 0x0013
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub2: port 2 status=0x0100 change=0x0000
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub2: port 3 status=0x0100 change=0x0000
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: intr status=0
> uhub1: port 2 status=0x0503 change=0x0001
> uhub1: intr status=0
> uhub1: port 2 status=0x0503 change=0x0000
> umass0 at uhub1 port 2 configuration 1 interface 0 "FUJIFILM Mass
> Storage Device" rev 2.00/11.00 addr 5
> umass0: using SCSI over Bulk-Only
> scsibus0 at umass0: 2 targets, initiator 0
> sd0 at scsibus0 targ 1 lun 0: <FUJIFILM, 16GB, 1100> SCSI2 0/direct
> removable serial.
> sd0: 15468MB, 512 bytes/sector, 31678464 sectors
> uhub1: port 3 status=0x0100 change=0x0000
> uhub1: port 4 status=0x0100 change=0x0000
> vscsi0 at root
> scsibus1 at vscsi0: 256 targets
> softraid0 at root
> scsibus2 at softraid0: 256 targets
> bootfile: sd0a:/bsd
> boot device: sd0
> root on sd0a (.a) swap on sd0b dump on sd0b
> WARNING: CHECK AND RESET THE DATE!
> Controller /dev/usb0:
> addr 01: 0000:0000 Broadcom, DWC2 root hub
> high speed, self powered, config 1, rev 1.00
> driver: uhub0
> port 01: 0002.0503 connect enabled power
> addr 02: 0424:2514 Standard Microsystems, product 0x2514
> high speed, self powered, config 1, rev b.b3
> driver: uhub1
> port 01: 0000.0503 connect enabled power
> port 02: 0000.0503 connect enabled power
> port 03: 0000.0100 power
> port 04: 0000.0100 power
> addr 03: 0424:2514 Standard Microsystems, product 0x2514
> high speed, self powered, config 1, rev b.b3
> driver: uhub2
> port 01: 0000.0503 connect enabled power
> port 02: 0000.0100 power
> port 03: 0000.0100 power
> addr 04: 0424:7800 Standard Microsystems, LAN7800
> high speed, self powered, config 1, rev 3.00
> driver: mue0
> addr 05: 8564:1000 FUJIFILM, Mass Storage Device
> high speed, power 500 mA, config 1, rev 11.00, iSerialNumber
> driver: umass0
>

Reply | Threaded
Open this post in threaded view
|

Re: Raspberry Pi 3 B+ ethernet

James Hastings
More testing on all four USB ports has revealed the following.

The right two ports (wired to uhub1) attach new devices at all times.
The left two ports (wired to uhub2) will not attach new devices after
initial usb_explore.
Inserting a USB hub to the left ports has no response.
Inserting a USB hub to the right ports attaches a new uhub(4).
Inserting a device in to that hub has no response.

uhub(4) seems to not be receiving interrupts on the second daisy-chained hub.
The ethernet controller is wired to uhub2 port 1 so this is likely why
it is not detected.
Can any other Pi 3B+ users confirm this?

Thanks