@J-B-Song Hello J.B Song, Did you connect HDMI via USB-C on VOXL2? Did you use this image

Hope your reply soon, thanks so much.

@tom Oh, I see Vinny's comment: "on Voxl2, we set that USB-C port as peripheral mode only, so it cannot be a host to any devices such as mass storage (thumb drives), ethernet dongles, and the like."

I would like to know if this limitation is from hardware or firmware (changed something in the Device Tree). Thanks for your reply.

@tom log from kernel, I think something is wrong with 88e8000.ssphy in Device Tree. If you know the reason, please let me know. Thanks so much.

[    1.857505] msm-usb-ssphy-qmp 88e8000.ssphy: Linked as a consumer to regulator.32
[    1.857519] msm-usb-ssphy-qmp 88e8000.ssphy: Linked as a consumer to regulator.18
[    1.857525] msm-usb-ssphy-qmp 88e8000.ssphy: failed to get phandle for msm_ssphy_qmp
[    1.857551] msm-usb-ssphy-qmp 88e8000.ssphy: Dropping the link to regulator.18
[    1.857563] msm-usb-ssphy-qmp 88e8000.ssphy: Dropping the link to regulator.32
[    1.857651] msm-usb-ssphy-qmp 88eb000.ssphy: Linked as a consumer to regulator.32
[    1.857661] msm-usb-ssphy-qmp 88eb000.ssphy: Linked as a consumer to regulator.18
[    1.860277] msm-dwc3 a600000.ssusb: unable to get ssphy device
[    1.956294] msm-usb-ssphy-qmp 88e8000.ssphy: Linked as a consumer to regulator.32
[    1.956311] msm-usb-ssphy-qmp 88e8000.ssphy: Linked as a consumer to regulator.18
[    1.956316] msm-usb-ssphy-qmp 88e8000.ssphy: failed to get phandle for msm_ssphy_qmp
[    1.956338] msm-usb-ssphy-qmp 88e8000.ssphy: Dropping the link to regulator.18
[    1.956346] msm-usb-ssphy-qmp 88e8000.ssphy: Dropping the link to regulator.32
[    1.958436] msm-dwc3 a600000.ssusb: unable to get ssphy device
[    2.149607] msm-usb-ssphy-qmp 88e8000.ssphy: Linked as a consumer to regulator.32
[    2.149618] msm-usb-ssphy-qmp 88e8000.ssphy: Linked as a consumer to regulator.18
[    2.149623] msm-usb-ssphy-qmp 88e8000.ssphy: failed to get phandle for msm_ssphy_qmp
[    2.149638] msm-usb-ssphy-qmp 88e8000.ssphy: Dropping the link to regulator.18
[    2.149648] msm-usb-ssphy-qmp 88e8000.ssphy: Dropping the link to regulator.32
[    2.150729] msm-dwc3 a600000.ssusb: unable to get ssphy device
[    2.158708] msm-usb-ssphy-qmp 88e8000.ssphy: Linked as a consumer to regulator.32
[    2.158716] msm-usb-ssphy-qmp 88e8000.ssphy: Linked as a consumer to regulator.18
[    2.158721] msm-usb-ssphy-qmp 88e8000.ssphy: No separate ID extcon device
[    2.162528] msm-usb-ssphy-qmp 88e8000.ssphy: USB DP QMP PHY: Update TYPEC CTRL(2)

Re: USBC Port as Ethernet interface

@Eric-Katzfey @mrawding Ya, I would like to use USB-C to connect ethernet via this hub but no have anything log in kernel and no connect to ethernet.

I think my hub works well, because I tried it on another board.

I would like to ask you to do it for me. And it is normal?

Thanks for your reply.

@tom

yes, please help me check. This is ifconfig when I dont connect ethernet. Because we only an USB-C on board, can not get ifconfig when plug in ethernet (via type C hub)

bond0: flags=5123<UP,BROADCAST,MASTER,MULTICAST>  mtu 1500
        ether ee:4f:a8:9e:b0:bc  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

dummy0: flags=195<UP,BROADCAST,RUNNING,NOARP>  mtu 1500
        inet6 fe80::fe46:ab6d:b90f:6fc7  prefixlen 64  scopeid 0x20<link>
        ether 72:cb:96:39:af:38  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 24  bytes 7120 (7.1 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 329822  bytes 32221264 (32.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 329822  bytes 32221264 (32.2 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

HI @Vinny @tom as you said, we can use ethernet via type C (J9), right? I followed this document to build and flash but my voxl2 can connect ethernet. I writed a post to ask about this, please help me check this my post Thanks a lot for your reply.

My issue: I can not connect to Ethernet via type C (J9) by adapter (i tried other hub). I followed these steps to flash the boot image from Modal AI here: flashing-guide.

My question: have any one can connect to Ethernet via type by adapter? I would like to know if we can connect to Ethernet without any extension board.

My check:
No log from kernel/journal when plugged in/out. I checked some drivers related to Ethernet from dmesg as

• r8152
• ax88179_178a
• lan78xx
• smsc75xx
• smsc95xx
• driver generic USB: cdc_ether, rndis_host, cdc_ncm, cdc_mbim, qmi_wwan

Hope to receive your answers, thanks a lot.