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

    RNDIS Connection

    Ask your questions right here!
    2
    16
    515
    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.
    • tomT
      tom admin
      last edited by

      https://docs.modalai.com/usb-to-ethernet-with-voxl/

      Not all usb to ethernet adapters are supported. A lot of people around the office use the apple ones but they have since been discontinued and are hard to find online so the other one I linked works as well.

      wilkinsafW 1 Reply Last reply Reply Quote 0
      • wilkinsafW
        wilkinsaf ModalAI Team @tom
        last edited by

        @tom AAAHHHH

        hence 892a0218-8729-474f-ba53-69f2039d0ffa-image.png

        Because not all are the same. Yes, that is what we mean. USB to Ethernet tethered. However, it appears that these are not all of the same. Some work and some don't.

        We have a couple different here I can try. I wonder what makes the apple ones work in particular. Our goal is to try and get different modems working over USB. One provides RNDIS. Apparently another does usb to ethernet interface.

        My knowledge on these network connections over usb is (obviously) novice.

        Would you recommend looking through voxl-modem to see how a connection is made, or is there another informational page you recommend?

        wilkinsafW 1 Reply Last reply Reply Quote 0
        • wilkinsafW
          wilkinsaf ModalAI Team @wilkinsaf
          last edited by wilkinsaf

          @wilkinsaf We are just attempting to understand how VOXL can make these network connections (bring up eth0 and such)

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

            @wilkinsaf Any sort of process used to support usb to ethernet is located at the kernel level (I believe). voxl-modem for example isn't used at all for bringing up a usb to ethernet dongle connection.

            So if the usb to ethernet dongle is supported (we've only tried out a couple and stuck with ones that have worked for us), the network interface should "just come up" wihtout any intervention from voxl-modem

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

              I find using dmesg -wH super helpful when debugging usb devices as you can monitor which driver is picking up the hardware that is being plugged in and then you can inspect the driver itself if needed. Although, if the hardware is unrecognized by the kernel you may not see anything in dmesg

              wilkinsafW 1 Reply Last reply Reply Quote 0
              • wilkinsafW
                wilkinsaf ModalAI Team
                last edited by

                This is super helpful.

                Thank you @tom. I will continue posting here for updates

                1 Reply Last reply Reply Quote 0
                • wilkinsafW
                  wilkinsaf ModalAI Team @tom
                  last edited by

                  @tom said in RNDIS Connection:

                  dmesg -wH

                  Apologies for the delay Tom.

                  I got some extra hardware and I am trying again to form RNDIS connection. I see the usb device and captured log from dmesg -wH command

                  [  +0.234046] usb 1-1: new high-speed USB device number 3 using xhci-hcd
[  +0.153446] usb 1-1: New USB device found, idVendor=1d6b, idProduct=0104
[  +0.000049] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  +0.000027] usb 1-1: Product: RNDIS Gadget
[  +0.000022] usb 1-1: Manufacturer: DTC
[  +0.000023] usb 1-1: SerialNumber: 0123678945
[  +0.059949] rndis_host 1-1:1.0 usb0: register 'rndis_host' at usb-xhci-hcd.0.auto-1, RNDIS device, ffffffc0ec10b610
[  +0.001060] mdss_register_panel: mdss mdp resource not initialized yet
[  +0.000047] mdss_wb soc:qcom,mdss_wb_panel: unable to register writeback panel
[  +0.012804] cdc_acm 1-1:1.2: This device cannot do calls on its own. It is not a modem.
[  +0.013688] wcd9335-slim tasha-slim-pgd: Platform data from device tree
[  +0.000347] wcd9335-slim tasha-slim-pgd: cdc-vdd-buck: vol=[1800000 1800000]uV, curr=[650000]uA, ond 0
[  +0.000082] wcd9335-slim tasha-slim-pgd: cdc-buck-sido: vol=[1800000 1800000]uV, curr=[250000]uA, ond 0
[  +0.000062] wcd9335-slim tasha-slim-pgd: cdc-vdd-tx-h: vol=[1800000 1800000]uV, curr=[25000]uA, ond 0
[  +0.000059] wcd9335-slim tasha-slim-pgd: cdc-vdd-rx-h: vol=[1800000 1800000]uV, curr=[25000]uA, ond 0
[  +0.000068] wcd9335-slim tasha-slim-pgd: cdc-vddpx-1: vol=[1800000 1800000]uV, curr=[10000]uA, ond 0
[  +0.000025] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-ldoh-v property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000025] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-cfilt1-mv property in node /soc/slim@91c0000/tasha_codec failed
[  +0.002282] cdc_acm 1-1:1.2: ttyACM0: USB ACM device
[  +0.005805] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-cfilt2-mv property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000036] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-cfilt3-mv property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000030] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias1-cfilt-sel property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000034] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias2-cfilt-sel property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000020] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias3-cfilt-sel property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000021] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias4-cfilt-sel property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000180] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-mic-unmute-delay property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000040] wcd9335-slim tasha-slim-pgd: wcd9xxx_slim_probe: codec type is 2
[  +0.170558] wcd9xxx_slim_probe: failed to get slimbus tasha-slim-pgd logical address: -6
[  +0.003819] mdss_register_panel: mdss mdp resource not initialized yet
[  +0.000058] mdss_wb soc:qcom,mdss_wb_panel: unable to register writeback panel
[  +0.018967] wcd9335-slim tasha-slim-pgd: Platform data from device tree
[  +0.000134] wcd9335-slim tasha-slim-pgd: cdc-vdd-buck: vol=[1800000 1800000]uV, curr=[650000]uA, ond 0
[  +0.000034] wcd9335-slim tasha-slim-pgd: cdc-buck-sido: vol=[1800000 1800000]uV, curr=[250000]uA, ond 0
[  +0.000032] wcd9335-slim tasha-slim-pgd: cdc-vdd-tx-h: vol=[1800000 1800000]uV, curr=[25000]uA, ond 0
[  +0.000032] wcd9335-slim tasha-slim-pgd: cdc-vdd-rx-h: vol=[1800000 1800000]uV, curr=[25000]uA, ond 0
[  +0.000033] wcd9335-slim tasha-slim-pgd: cdc-vddpx-1: vol=[1800000 1800000]uV, curr=[10000]uA, ond 0
[  +0.000016] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-ldoh-v property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000011] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-cfilt1-mv property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000012] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-cfilt2-mv property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000013] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias-cfilt3-mv property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000014] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias1-cfilt-sel property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000011] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias2-cfilt-sel property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000010] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias3-cfilt-sel property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000011] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-micbias4-cfilt-sel property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000059] wcd9335-slim tasha-slim-pgd: Looking up qcom,cdc-mic-unmute-delay property in node /soc/slim@91c0000/tasha_codec failed
[  +0.000027] wcd9335-slim tasha-slim-pgd: wcd9xxx_slim_probe: codec type is 2
[  +0.156933] wcd9xxx_slim_probe: failed to get slimbus tasha-slim-pgd logical address: -6

                  not seeing the RNDIS interface, but I am going to look closer into this

                  1 Reply Last reply Reply Quote 0
                  • wilkinsafW
                    wilkinsaf ModalAI Team
                    last edited by

                    5e76d789-acb8-455c-a515-fe3a08c85deb-image.png

                    Cool, lets see if I can actually talk over it

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

                      @wilkinsaf Awesome! Looks like you've made some good progress

                      wilkinsafW 1 Reply Last reply Reply Quote 0
                      • wilkinsafW
                        wilkinsaf ModalAI Team @tom
                        last edited by

                        @tom Yes! we were able to make a connection! Thank you @tom

                        1 Reply Last reply Reply Quote 0
                        • S skl1g14 referenced this topic on
                        • First post
                          Last post
                        Powered by NodeBB | Contributors