ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Ethernet Dongle

    VOXL 2
    4
    20
    1502
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      Huynh Gremsy
      last edited by Huynh Gremsy

      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.

      tomT 1 Reply Last reply Reply Quote 0
      • tomT
        tom admin @Huynh Gremsy
        last edited by

        @Huynh-Gremsy Can you share your output of ifconfig on your voxl?

        H 1 Reply Last reply Reply Quote 0
        • H
          Huynh Gremsy @tom
          last edited by

          @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
          
          H 1 Reply Last reply Reply Quote 0
          • H
            Huynh Gremsy @Huynh Gremsy
            last edited by

            @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)
            
            tomT 1 Reply Last reply Reply Quote 0
            • tomT
              tom admin @Huynh Gremsy
              last edited by

              @Huynh-Gremsy Apologies, didn't realize you were trying to use the usb-c port, see Vinny's comment here:

              https://forum.modalai.com/post/8501

              H 2 Replies Last reply Reply Quote 0
              • H
                Huynh Gremsy @tom
                last edited by

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

                1 Reply Last reply Reply Quote 0
                • H
                  Huynh Gremsy @tom
                  last edited by

                  @tom Oh I have a important question, please help me reply soon.
                  I see comment in this post: “ MCCA-M0125 USB3.0 / UART Expansion Adapter” can use to connect to Ethernet. So if it can use MCCA-M0125 USB3.0 / UART Expansion Adapter to connect HDMI. Thanks so much for your reply.

                  tomT 1 Reply Last reply Reply Quote 0
                  • tomT
                    tom admin @Huynh Gremsy
                    last edited by

                    @Huynh-Gremsy There is no way to get HDMI output, are you trying to use HDMI input? If so you can use an HDMI to USB-A capture card and the HDMI device will enumerate as a UVC camera

                    H 1 Reply Last reply Reply Quote 0
                    • H
                      Huynh Gremsy @tom
                      last edited by

                      @tom i am asking about HDMI output. I would like to push the frame to the Screen to watch. You mean no way to do that?

                      tomT 1 Reply Last reply Reply Quote 0
                      • tomT
                        tom admin @Huynh Gremsy
                        last edited by

                        @Huynh-Gremsy No, there is no way to do that. There is no display output

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Powered by NodeBB | Contributors