Ethernet Dongle
-
Can you ssh into the VOXL2 by plugging an ethernet adapter into the USB C port as opposed to using the USB breakout board? I'd like to be able to see the portal while I do testing but I'm using the UART breakout board for my project so I cannot simultaneously use the USB breakoutboard
-
Hi @bendraper
Unfortunately, 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.
Hope that helps. -
@Vinny Thanks for the quick reply! Can the 10 pin connector in the MCCA-M0125 USB3.0 / UART Expansion Adapter be used to host the wifi/ethernet adapter while using the other connector for external flight controllers?
-
Per the product description it seems that port is also peripheral. Is there any Voxl2 configuration where I can use the UART for external flight controllers and also have a wifi dongle plugged in?
-
@bendraper Yes, J3 is a USB3.0 port. You can use that port paired with an MCBL-00022-2 (https://www.modalai.com/collections/accessories/products/mcbl-00022) to give you an USB-A port.
-
@tom Will the USB-A port support a wifi dongle/ethernet adapter though? Or is it purely peripheral like the USB-C port on the Voxl 2
-
@bendraper Yes, the VOXL2 will act as the host for whatever USB device you plug in there. So you can use a WiFi dongle, ethernet adapter, UVC camera, etc. on that port. It's the same idea as this kit: https://www.modalai.com/products/voxl-2-wifi-add-on-kit?_pos=1&_sid=bb17898ae&_ss=r
Except yours would be USB3
-
@bendraper said in Ethernet Dongle:
Per the product description it seems that port is also peripheral. Is there any Voxl2 configuration where I can use the UART for external flight controllers and also have a wifi dongle plugged in?
Hi,
Where do you see this as "peripheral"? We need to fix that typo if so. It is certainly a HOST port.
Thanks! -
@Vinny At this link https://www.modalai.com/products/m0125?variant=40740708876339
Our USB3.0 / UART Expansion Adapter installs directly onto a VOXL 2 via the legacy board to board connector (J3). Use this board to integrate USB 3 peripheral devices as well as an additional UART for communicating with an external flight controller. This product cannot be used in combination with other daughter boards or modems which are installed onto the legacy or high speed board to board connectors.
-
Hi @bendraper ,
Sorry for the confusion, we can make that clearer.
It's trying to say that you can connect peripheral devices to Voxl2.
So, maybe Instead of
"Use this board to integrate USB 3 peripheral devices..."
we can change it to say
"Use this board to connect USB 3 peripheral devices..."
Would that help in your opinion?
Thanks and apologies if that created confusion. -
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.
-
@Huynh-Gremsy Can you share your output of
ifconfig
on your voxl? -
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
-
@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)
-
@Huynh-Gremsy Apologies, didn't realize you were trying to use the usb-c port, see Vinny's comment here:
-
@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.