HI William, I am in over my head here :) I don't really know how it works.
All I know at this point is that I see the system seeing and registereing the device but I cannot get it to bring it live on the BBB. But on my desktop machine running ubuntu 3.16.0-70-generic #90~14.04.1-Ubuntu it simply registers and then brings and then bring it up. It just works. However on my BBB it doesn't ever list it in ifconfig. Matt Maher Peterson APANA w: 360.746.2276x401 c: 360.393.5549 On Wed, Apr 20, 2016 at 4:00 PM, William Hermans <yyrk...@gmail.com> wrote: > Do you know how a cdc_ether device works ? Because according to the text > you've got there, and the output from dmesg, you should be able to run sudo > ifconfig, and see it listed. > > On Wed, Apr 20, 2016 at 3:31 PM, Matt99eo <mattmaherpeter...@gmail.com> > wrote: > >> Still working on this and really not sure what my next step is. >> >> When I plug the module into both my old device running 3.8 and now a new >> device (just compiled 4.1.21-bone-rt-r20) I do am not getting a >> connection. Tailing the syslog it gets up the poingt of declaring it >> ttyACM0: USB ACM device but then nothing happens: >> >> >> [12990.725461] cdc_ether 1-1:1.0 usb0: unregister 'cdc_ether' >> usb-musb-hdrc.1.auto-1, CDC Ethernet Device >> Apr 20 21:28:05 arm kernel: [12990.719975] usb 1-1: USB disconnect, >> device number 4 >> Apr 20 21:28:05 arm kernel: [12990.725461] cdc_ether 1-1:1.0 usb0: >> unregister 'cdc_ether' usb-musb-hdrc.1.auto-1, CDC Ethernet Device >> [12993.532521] usb 1-1: new high-speed USB device number 6 using musb-hdrc >> Apr 20 21:28:08 arm kernel: [12993.532521] usb 1-1: new high-speed USB >> device number 6 using musb-hdrc >> [12993.823315] usb 1-1: New USB device found, idVendor=1e2d, >> idProduct=00a0 >> [12993.830122] usb 1-1: New USB device strings: Mfr=1, Product=2, >> SerialNumber=3 >> [12993.837381] usb 1-1: Product: SQN >> [12993.840731] usb 1-1: Manufacturer: Sequans Communications >> [12993.846221] usb 1-1: SerialNumber: 700400708002 >> Apr 20 21:28:08 arm kernel: [12993.823315] usb 1-1: New USB device found, >> idVendor=1e2d, idProduct=00a0 >> Apr 20 21:28:08 arm kernel: [12993.830122] usb 1-1: New USB device >> strings: Mfr=1, Product=2, SerialNumber=3 >> Apr 20 21:28:08 arm kernel: [12993.837381] usb 1-1: Product: SQN >> Apr 20 21:28:08 arm kernel: [12993.840731] usb 1-1: Manufacturer: Sequans >> Communications >> Apr 20 21:28:08 arm kernel: [12993.846221] usb 1-1: SerialNumber: >> 700400708002 >> [12993.922298] cdc_ether 1-1:1.0 usb0: register 'cdc_ether' at >> usb-musb-hdrc.1.auto-1, CDC Ethernet Device, 02:80:70:00:04:70 >> [12993.942669] cdc_acm 1-1:1.2: ttyACM0: USB ACM device >> >> >> I have also now taken this module and plugged it hot into my dev desktop >> computer running ubuntu ( 3.16.0-70-generic #90~14.04.1-Ubuntu ) and it >> just fires up all the way! Auto detects and I instantly have an >> established connection thru the module. >> >> I attached my syslog from when I did this and you see much more going on >> after ~ line 11 where we have the same ttyACM0: USB ACM device. >> >> >> On Monday, April 18, 2016 at 10:37:20 AM UTC-7, Matt99eo wrote: >>> >>> Ok I see it now with lsusb: >>> >>> lsusb >>> Bus 001 Device 004: ID 1e2d:00a0 >>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub >>> >>> And in my dmesg log I see it registering: >>> >>> dmesg |grep cdc_ether >>> [ 0.709427] usbcore: registered new interface driver cdc_ether >>> [ 1.859965] cdc_ether 1-1:1.0: usb_probe_interface >>> [ 1.859981] cdc_ether 1-1:1.0: usb_probe_interface - got id >>> [ 1.885585] cdc_ether 1-1:1.0 usb0: register 'cdc_ether' at >>> usb-musb-hdrc.1.auto-1, CDC Ethernet Device, 02:80:70:00:04:70 >>> >>> What am I missing to establish the Ethernet over USB connection? >>> >>> >>> On Monday, April 18, 2016 at 9:03:22 AM UTC-7, RobertCNelson wrote: >>>> >>>> >>>> >>>> On Mon, Apr 18, 2016 at 10:57 AM, Matt99eo <mattmahe...@gmail.com> >>>> wrote: >>>> >>>>> Hi RC, >>>>> >>>>> Sorry for the limited information. Just got word the document I am >>>>> working with is public (attached) >>>>> >>>>> The device I am working with is a Skywire LTE CAT1 Module (Gemalto >>>>> ELS35). >>>>> >>>>> Here is what the helpful support is telling me: >>>>> ____ >>>>> >>>>> CDC_ETH is a device support class that allows for the modem to act as >>>>> LAN connection over USB. There isn't a VIP/PID that needs to be added for >>>>> the kernel to support it, the Kernel needs to be built to support the >>>>> CDC_ETH class. >>>>> >>>>> When the device is loaded as a CDC_ETH device you will see it >>>>> enumerate in your system as something like this: >>>>> >>>>> [ 17.900000] cdc_ether 1-1:1.0 usb0: register 'cdc_ether' at >>>>> usb-ehci-platform-1, CDC Ethernet Device, 02:10:81:64:89:60 >>>>> _____ >>>>> >>>>> When I use lsusb I don't see the device listed (believe I should see Bus >>>>> 001 Device 001: ID 1d6b:0002) >>>>> >>>> >>>> That's the root hub: http://www.linux-usb.org/usb.ids >>>> >>>> 1d6b Linux Foundation >>>> >>>> 0001 1.1 root hub >>>> 0002 2.0 root hub >>>> 0003 3.0 root hub >>>> 0100 PTP Gadget >>>> 0101 Audio Gadget >>>> 0102 EEM Gadget >>>> 0103 NCM (Ethernet) Gadget >>>> 0104 Multifunction Composite Gadget >>>> 0105 FunctionFS Gadget >>>> 0200 Qemu Audio Device >>>> >>>> run "lsusb" again. ;) >>>> >>>> Regards, >>>> >>>> -- >>>> Robert Nelson >>>> https://rcn-ee.com/ >>>> >>> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to beagleboard+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/6240b56b-93c7-4739-8920-d40881508721%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/6240b56b-93c7-4739-8920-d40881508721%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/GYVMpkXrMWU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/CALHSORp%2B2W4ybrT5wgoq7ardQbOofkWf92WbtC_QN9K0QFfNyA%40mail.gmail.com > <https://groups.google.com/d/msgid/beagleboard/CALHSORp%2B2W4ybrT5wgoq7ardQbOofkWf92WbtC_QN9K0QFfNyA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAPt7HNLVFeXZ1S231gbTNzq0Mweaxz9CwCqKnqp5szgZRk_L2Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
