problem with MC7710 On Debian jessie kernel 3.14

IoT Modules MC/EM Series
1

Hi all,
I’m drying on a problem since 1 month so i need the community help.
I get a MC7710 in the system GNU/Debian Jessie in an embedded insdustrial PC without GUI,
recognized in dmesg by :

[    1.919667] usb 4-5: New USB device found, idVendor=1199, idProduct=68a3
[    1.919679] usb 4-5: New USB device strings: Mfr=4, Product=3, SerialNumber=5
[    1.919688] usb 4-5: Product: MC7710
[    1.919696] usb 4-5: Manufacturer: Sierra Wireless, Incorporated
[    1.919704] usb 4-5: SerialNumber: 358178041667322
[    2.786487] usbcore: registered new interface driver usbserial
[    2.786563] usbcore: registered new interface driver usbserial_generic
[    2.786641] usbserial: USB Serial support registered for generic
[    2.790339] usbcore: registered new interface driver sierra
[    2.790425] usbserial: USB Serial support registered for Sierra USB modem
[    2.800287] usb 4-5: Sierra USB modem converter now attached to ttyUSB0
[    2.811297] usb 4-5: Sierra USB modem converter now attached to ttyUSB1
[    2.814764] usb 4-5: Sierra USB modem converter now attached to ttyUSB2
[    2.817981] usb 4-5: Sierra USB modem converter now attached to ttyUSB3
[    2.820234] usb 4-5: Sierra USB modem converter now attached to ttyUSB4
[    2.824176] usb 4-5: Sierra USB modem converter now attached to ttyUSB5
[    2.824343] usbcore: registered new interface driver cdc_ether

lsusb -v | grep -E ‘<(Bus|iProduct|bDeviceClass|bDeviceProtocol)’ 2>/dev/null

Bus 004 Device 002: ID 1199:68a3 Sierra Wireless, Inc. MC8700 Modem
  bDeviceClass            2 Communications
  bDeviceProtocol         0 
  iProduct                3 MC7710
  bDeviceClass            2 Communications
  bDeviceProtocol         0 
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  bDeviceClass            9 Hub
  bDeviceProtocol         0 Full speed (or root) hub
  iProduct                2 EHCI Host Controller

rfkill list don’t return anything

which is the best way to use it to connect to the internet with this modem?
how can I pass it to DIP mode under linux?

regards,
Damien

2

Cridams,

From the PID of the unit (68A3) the unit seems to be in DIP mode already but it does not seems to be enumerating enough ttyUSB’s from what I can see (it is enumerating the same number as you would expect for a unit in QMI mode), you should get ttyUSB0 through 4. Of these ttyUSB3 would be the one to connect to send the AT commands to start the DIP connection up. Once connected can you send ls /dev so see can see all of the system devices?

Regards

Matt

3

hello matt,
thanks for your help, so 68a3 is for DIP mode but in this mode the sierra_net driver should mount a wwan0 device no?

here the result of ls /dev

~# ls /dev/
agpgart          hidraw2             pts       tty11  tty3   tty48  tty9     vcsa1
autofs           hpet                random    tty12  tty30  tty49  ttyS0    vcsa2
block            hugepages           rfkill    tty13  tty31  tty5   ttyS1    vcsa3
bsg              initctl             rtc       tty14  tty32  tty50  ttyS2    vcsa4
btrfs-control    input               rtc0      tty15  tty33  tty51  ttyS3    vcsa5
bus              kmsg                sda       tty16  tty34  tty52  ttyUSB0  vcsa6
char             log                 sda1      tty17  tty35  tty53  ttyUSB1  vga_arbiter
console          loop-control        sda2      tty18  tty36  tty54  ttyUSB2  vhci
core             mapper              serial    tty19  tty37  tty55  ttyUSB3  vhost-net
cpu              mcelog              sg0       tty2   tty38  tty56  uhid     watchdog
cpu_dma_latency  mem                 shm       tty20  tty39  tty57  uinput   watchdog0
cuse             mqueue              snapshot  tty21  tty4   tty58  urandom  xconsole
disk             net                 snd       tty22  tty40  tty59  vcs      zero
dri              network_latency     stderr    tty23  tty41  tty6   vcs1
fb0              network_throughput  stdin     tty24  tty42  tty60  vcs2
fd               null                stdout    tty25  tty43  tty61  vcs3
full             port                tty       tty26  tty44  tty62  vcs4
fuse             ppp                 tty0      tty27  tty45  tty63  vcs5
hidraw0          psaux               tty1      tty28  tty46  tty7   vcs6
hidraw1          ptmx                tty10     tty29  tty47  tty8   vcsa

So i can see My ttyUSB interface.

but when i try to send ati5 on ttyUSB3 via minicom… nothing happens and minicom see the serial as disconnected…

regards,

Damien

4

Damien,

A few questions.

  • Do you see any responses from the unit at all?
  • So you re initially able to connect to ttyUSB3?

You could have one less ttyUSB port if the GPS is disabled and hence the NMEA port is not enumerating. In which case can you try to connect to each ttyUSB in turn with minicom and see i you get any responses out of it?

Regards

Matt

5

hello Matt,
there no response at all on all my ttyUSB ports,
I installed putty andxfce to try. putty don’t say that it can’t open the port but there s no response to ATZ commande or ati5 command
i don’t understand what happens, the modem is working when i put it in a laptop with debian testing/XFCE/kernel3.14 but not in the embedded PC with debian testing/XFCE/kernel3.14 …
i don’t understand what’s the difference.

thanks for your time Matt.

Regards,
Damien

6

Damien,

About to go on holiday but just had a last play with this and trying to wrap my head around what I have just done as I was seeing the same on both an MC771 and an MC8705. Essentially they would both enumerate with /dev/ttyUSB0 - 4, 3 is always the AT port but mine was coming back as APP1 when I sent it ati, this means it is a modem port and will respond to a limited number of AT commands.

On my 7710 I got around it by changing the USB composition from 3 to 4, you would need to do this on you machine which currently supports all of the at commands

at!entercnd=“A710”
at!udusbcomp=4
at!reset

Magically dev/ttyUSB3 is suddenly a full AT command port and not an APP1. This is not how it should work and so I think there must be some sort of driver issue on the system somewhere (I am using Ubuntu 12.04, kernel 3.5).

Can you send the following to the kernel to see what drivers you have

modinfo sierra

Regards

Matt

7

thank you Matt,
i’ll try this on monday cause i don’t have an access to the machine before…

regards,
Damien

8

hi All,
sorry for my latency i was very busy on other subjects… Sorry Matt but I can’t send any command to the modem can’t establish any connections on any serial port to pass commands…

modinfo sierra give me this:

# modinfo sierra
filename:       /lib/modules/3.14-2-686-pae/kernel/drivers/usb/serial/sierra.ko
license:        GPL
description:    USB Driver for Sierra Wireless USB modems
author:         Kevin Lloyd, Elina Pasheva, Matthew Safar, Rory Filer
alias:          usb:v0F3Dp68A3d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0F3Dp68AAd*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v1199p68A3d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6893d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6892d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v1199p6891d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v1199p6890d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v1199p6880d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v1199p685Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6859d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6856d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6855d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6853d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6852d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6851d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6850d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p683Ed*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p683Dd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p683Cd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p683Bd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p683Ad*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6839d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6838d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6835d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6834d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6833d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6832d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6822d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6821d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6820d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6816d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6815d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6813d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6812d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6809d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6808d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6805d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6804d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6803d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p6802d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0029d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0028d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0027d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0026d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0025d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v1199p0023d*dc*dsc*dp*icFFiscFFipFFin*
alias:          usb:v1199p0301d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0120d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0112d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0021d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0019d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0224d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0024d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0022d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0220d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0020d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0218d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0018d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v1199p0017d*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v03F0p1E1Dd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v03F0p211Dd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v03F0p1B1Dd*dc*dsc*dp*ic*isc*ip*in*
alias:          usb:v0F3Dp0112d*dc*dsc*dp*ic*isc*ip*in*
depends:        usbserial,usbcore
intree:         Y
vermagic:       3.14-2-686-pae SMP mod_unload modversions 686 
parm:           nmea:NMEA streaming (bool)

and a bonus :

# modinfo sierra_net 
filename:       /lib/modules/3.14-2-686-pae/kernel/drivers/net/usb/sierra_net.ko
license:        GPL
version:        v.2.0
description:    USB-to-WWAN Driver for Sierra Wireless modems
author:         Paxton Smith, Matthew Safar, Rory Filer
srcversion:     896313DAA9C61C842F37412
alias:          usb:v0F3Dp68AAd*dc*dsc*dp*ic*isc*ip*in0B*
alias:          usb:v0F3Dp68AAd*dc*dsc*dp*ic*isc*ip*in0A*
alias:          usb:v0F3Dp68AAd*dc*dsc*dp*ic*isc*ip*in07*
alias:          usb:v1199p68AAd*dc*dsc*dp*ic*isc*ip*in0B*
alias:          usb:v1199p68AAd*dc*dsc*dp*ic*isc*ip*in0A*
alias:          usb:v1199p68AAd*dc*dsc*dp*ic*isc*ip*in07*
alias:          usb:v0F3Dp68A3d*dc*dsc*dp*ic*isc*ip*in0B*
alias:          usb:v0F3Dp68A3d*dc*dsc*dp*ic*isc*ip*in0A*
alias:          usb:v0F3Dp68A3d*dc*dsc*dp*ic*isc*ip*in07*
alias:          usb:v1199p68A3d*dc*dsc*dp*ic*isc*ip*in0B*
alias:          usb:v1199p68A3d*dc*dsc*dp*ic*isc*ip*in0A*
alias:          usb:v1199p68A3d*dc*dsc*dp*ic*isc*ip*in07*
depends:        usbnet,usbcore
intree:         Y
vermagic:       3.14-2-686-pae SMP mod_unload modversions 686

regards,
Damien

9

I am a bit confused here, but let’s try if a few questions can clear stuff up…

Your first dmesg log showed ttyUSB[0-5] being created, but then you showed a “ls /dev/” listing with only /dev/ttyUSB[0-3]. Is that correct? Then I wonder what happend to the two last devices. I do not understand why they weren’t created like the others. In any case, ttyUSB3 should normally be an AT command port, so if it doesn’t respond to AT commands then there is something odd going on. Could you please verify that ttyUSB3 is mapped to the USB interface we expect (#3)?. Something like

ls -l /sys/bus/usb-serial/devices

will do.

It is correct that the device is in DIP mode when the PID is 68a3, but there are several possible USB compositions available in that mode too. Not all of them have a “NIC” function. So if you can get an AT command session going, then it would be useful to see the output of the protected AT!UDUSBCOMP command:

AT!ENTERCND="password"
AT!UDUSBCOMP?
AT!UDUSBCOMP=?

You’ll have to ask your Sierra FAE for the password if Google doesn’t help…

I am hoping that will tell us why you get 6 serial ports and no NIC port. If it doesn’t, or you cannot get AT commands working, then a full (or at least one showing the interface numbers) “lsusb -vd 1199:68a3” will probably do as well.

If it doesn’t, then I am curious if someone might have done something to mess up probing here. Maybe dynamically adding the 1199:68a3 device id? I believe 3.14 is new enough that you can do

cat  /sys/bus/usb-serial/drivers/sierra/new_id

to detect this. If you get nothing, then you are fine. If you get something including “1199 68a3”, then you need to figure out which script is adding that and fix it.

10

hello,
thanks to for your help. i’m confused to not be clear but i’m a little lost equally with this device… i will try to clarify

dmesg | grep usb give me this

dmesg | grep "usb"
[    1.429425] usbcore: registered new interface driver usbfs
[    1.429507] usbcore: registered new interface driver hub
[    1.429665] usbcore: registered new device driver usb
[    1.433166] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[    1.433178] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.433187] usb usb1: Product: UHCI Host Controller
[    1.433194] usb usb1: Manufacturer: Linux 3.14-2-686-pae uhci_hcd
[    1.433201] usb usb1: SerialNumber: 0000:00:1d.0
[    1.435400] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[    1.435410] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.435418] usb usb2: Product: UHCI Host Controller
[    1.435426] usb usb2: Manufacturer: Linux 3.14-2-686-pae uhci_hcd
[    1.435434] usb usb2: SerialNumber: 0000:00:1d.1
[    1.452286] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    1.452296] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.452304] usb usb3: Product: EHCI Host Controller
[    1.452312] usb usb3: Manufacturer: Linux 3.14-2-686-pae ehci_hcd
[    1.452319] usb usb3: SerialNumber: 0000:00:1d.7
[    1.505939] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[    1.505950] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.505957] usb usb4: Product: UHCI Host Controller
[    1.505967] usb usb4: Manufacturer: Linux 3.14-2-686-pae uhci_hcd
[    1.505975] usb usb4: SerialNumber: 0000:00:1d.2
[    1.820170] usb 3-5: new high-speed USB device number 3 using ehci-pci
[    1.953725] usb 3-5: config 1 has an invalid interface number: 12 but max is 5
[    1.953738] usb 3-5: config 1 has an invalid interface number: 13 but max is 5
[    1.953748] usb 3-5: config 1 has an invalid interface number: 13 but max is 5
[    1.953757] usb 3-5: config 1 has no interface number 4
[    1.953765] usb 3-5: config 1 has no interface number 5
[    1.955814] usb 3-5: New USB device found, idVendor=1199, idProduct=68a3
[    1.955823] usb 3-5: New USB device strings: Mfr=4, Product=3, SerialNumber=5
[    1.955829] usb 3-5: Product: MC7710
[    1.955835] usb 3-5: Manufacturer: Sierra Wireless, Incorporated
[    1.955840] usb 3-5: SerialNumber: 358178041667322
[    2.324274] usb 1-2: new low-speed USB device number 2 using uhci_hcd
[    2.535135] usb 1-2: New USB device found, idVendor=413c, idProduct=2106
[    2.535150] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.535158] usb 1-2: Product: Dell QuietKey Keyboard
[    2.535165] usb 1-2: Manufacturer: Dell
[    3.370119] usbcore: registered new interface driver usbserial
[    3.370192] usbcore: registered new interface driver usbserial_generic
[    3.370263] usbserial: USB Serial support registered for generic
[    3.373327] usbcore: registered new interface driver sierra
[    3.373409] usbserial: USB Serial support registered for Sierra USB modem
[    3.377201] usb 3-5: Sierra USB modem converter now attached to ttyUSB0
[    3.378153] usb 3-5: Sierra USB modem converter now attached to ttyUSB1
[    3.378953] usb 3-5: Sierra USB modem converter now attached to ttyUSB2
[    3.381035] usb 3-5: Sierra USB modem converter now attached to ttyUSB3
[    3.381873] usb 3-5: Sierra USB modem converter now attached to ttyUSB4
[    3.384938] usb 3-5: Sierra USB modem converter now attached to ttyUSB5
[    3.388492] usbcore: registered new interface driver cdc_ether
[    3.643896] usbcore: registered new interface driver usbhid
[    3.643906] usbhid: USB HID core driver
[    3.652850] input: Dell Dell QuietKey Keyboard as /devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/0003:413C:2106.0001/input/input6
[    3.666842] hid-generic 0003:413C:2106.0001: input,hidraw0: USB HID v1.10 Keyboard [Dell Dell QuietKey Keyboard] on usb-0000:00:1d.0-2/input0

ls -l /sys/bus/usb-serial/devices

lrwxrwxrwx 1 root root 0 août  27 12:01 ttyUSB0 -> ../../../devices/pci0000:00/0000:00:1d.7/usb3/3-5/3-5:1.0/ttyUSB0
lrwxrwxrwx 1 root root 0 août  27 12:01 ttyUSB1 -> ../../../devices/pci0000:00/0000:00:1d.7/usb3/3-5/3-5:1.1/ttyUSB1
lrwxrwxrwx 1 root root 0 août  27 12:01 ttyUSB2 -> ../../../devices/pci0000:00/0000:00:1d.7/usb3/3-5/3-5:1.2/ttyUSB2
lrwxrwxrwx 1 root root 0 août  27 12:01 ttyUSB3 -> ../../../devices/pci0000:00/0000:00:1d.7/usb3/3-5/3-5:1.3/ttyUSB3
lrwxrwxrwx 1 root root 0 août  21 13:23 ttyUSB4 -> ../../../devices/pci0000:00/0000:00:1d.7/usb3/3-5/3-5:1.12/ttyUSB4
lrwxrwxrwx 1 root root 0 août  27 12:01 ttyUSB5 -> ../../../devices/pci0000:00/0000:00:1d.7/usb3/3-5/3-5:1.13/ttyUSB5
root@MonitorUndef:~# dmesg | grep 1199
[    1.955814] usb 3-5: New USB device found, idVendor=1199, idProduct=68a3

so if i understand all my serial ports are created sierra module seems to do error :

dmesg | grep sierra

[    3.373327] usbcore: registered new interface driver sierra
[    3.373478] sierra 3-5:1.0: Sierra USB modem converter detected
[    3.377284] sierra 3-5:1.1: Sierra USB modem converter detected
[    3.378236] sierra 3-5:1.2: Sierra USB modem converter detected
[    3.379030] sierra 3-5:1.3: Sierra USB modem converter detected
[    3.381122] sierra 3-5:1.12: Sierra USB modem converter detected
[    3.383113] sierra 3-5:1.13: Sierra USB modem converter detected
[    5.132084] sierra ttyUSB4: sierra_submit_rx_urbs: submit urb failed: -8
[    5.132292] sierra ttyUSB4: sierra_submit_rx_urbs: submit urb failed: -8
[    5.132488] sierra ttyUSB4: sierra_submit_rx_urbs: submit urb failed: -8
[    5.132684] sierra ttyUSB4: sierra_submit_rx_urbs: submit urb failed: -8
[    5.154430] sierra ttyUSB4: sierra_submit_rx_urbs: submit urb failed: -8
[    5.154638] sierra ttyUSB4: sierra_submit_rx_urbs: submit urb failed: -8

but when i launch a micom with : minicom -D /dev/ttyUSB3

  1. if i use shortcut ctrl^a immediatly the status is disconnected…
  2. if i try a command, i can’t pass any command and hangs up until i kill the process…

and cat /sys/bus/usb-serial/drivers/sierra/new_id returns nothing…

thanks for help,

regards,
Damien

11

Wow, that was a bit surprising to me. Sierra Wireless have so far been using 12 and 13 for MBIM control and data, but I’ve never seen that on a device configured for DIP before. If it really is an MBIM function… Any chance you could provide a full “lsusb -vd 1199:68a3” listing?

Yes, that looks fine and ttyUSB3 should be an AT port. The ttyUSB4 and ttyUSB5 devices are bogus if my MBIM guess is correct, but that problem is expected because we only blacklist the known non-serial interfaces in sierra.c. And 12 and 13 were so far unknown for a DIP device. We should probably fix it by doing a
USB_DEVICE_AND_INTERFACE_INFO match on ff/ff/ff instead of a catch-all USB_DEVICE match.

If my guess is correct then there aren’t any bulk endpoints available to ttyUSB4, so these errors are not at all surprising.

Of all those ports, I’d only expect ttyUSB3 to work as an AT command port. But that one should work. I cannot explain the problems you have with it. ttyUSB0, ttyUSB1 and ttyUSB2 are most likely HIP, DM and NMEA ports.

Is minicom configured to send some initial reset sequence? Is there any other terminal application you can try? Maybe it’s time to try out usbmon? Ref kernel.org/doc/Documentation/usb/usbmon.txt

Yes, that makes sense after seeing the 12 and 13 interface numbers. They will be matched by default by the current sierra driver.

12

hello,
here is the first part of the question :

lsusb -vd 1199:68a3

Bus 003 Device 003: ID 1199:68a3 Sierra Wireless, Inc. MC8700 Modem
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            2 Communications
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x1199 Sierra Wireless, Inc.
  idProduct          0x68a3 MC8700 Modem
  bcdDevice            0.06
  iManufacturer           4 Sierra Wireless, Incorporated
  iProduct                3 MC7710
  iSerial                 5 358178041667322
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          179
    bNumInterfaces          6
    bConfigurationValue     1
    iConfiguration          2 Sierra Configuration
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower                0mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x03  EP 3 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               5
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber       12
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      6 Ethernet Networking
      bInterfaceProtocol      0 
      iInterface              0 
      CDC Header:
        bcdCDC               1.10
      CDC Ethernet:
        iMacAddress                      1 00A0C6000000
        bmEthernetStatistics    0x00000000
        wMaxSegmentSize               8192
        wNumberMCFilters            0x0001
        bNumberPowerFilters              0
      CDC Union:
        bMasterInterface        12
        bSlaveInterface         13 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               5
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber       13
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              0 
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber       13
      bAlternateSetting       1
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 Unused
      bInterfaceProtocol      0 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x05  EP 5 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval              32
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            2 Communications
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

i don’t have a specific configuration on minicom i use it out of the box just configured the port and speed. i installed it when problems started, so i just have the default package configuration.
i’ll read the usbmon documentation to try it before answers to the other part.

but for me the more surprising is that if i put this module in my laptop on debian testing/XFCE with the same package version it work. but i need to get this working cause i have 5 embedded pc to make working with these modules… but i m not sure that all of them have the same firmware.
Is it possible to upgrade firmware on all of them with the same firmware on linux cause I don’t have a windows PC under the hand with a mSata port…

best regards,
Damien

13

Ah, OK. So Sierra Wireless obviously use this pair of USB interface numbers for more than just MBIM. Maybe it’s used for “any CDC class function” or something like that? Only the Sierra firmware developers will know for sure. In any case, the end result is the same: The sierra driver should be prevented from binding to these interfaces, to allow the proper class driver (in this case: cdc_ether) to drive it instead.

I will prepare a patch for the sierra driver based ASAP. Hopefully ending up in the Debian kernels within a few weeks.

The AT port should definitely work in both cases, and the fact that it works in the laptop is just proof that there is nothing wrong with the modem module. I don’t have any suggestion what could possibly be different on your embedded platform. Being a PC platform with a PCI EHCI host controller should make it equivalent to the laptop in all possible ways. And the modem boots fine, so I believe we can rule out any problem with the mini-PCIe slot as well.

Sorry, I have run out of things to try out. Thanks for the lsusb output which I will use to fix the sierra driver. I hope someone else comes

It’s not likely that this is a modem firmware issue. But Sierra supports upgrading the firmware on Linux if you want to try that. I have not tested it myself on a modem in DIP mode though…

I would try a few other things first:

  • another terminal application. Maybe simply ‘echo -e “ATI\r” >/dev/ttyUSB3; cat /dev/ttyUSB3’?
  • usbmon
  • assuming the embedded PC have USB ports: does the problem affect other 3G/LTE modems?
14

ok,
thak you very much for your time, i ll try to search in bios about running modes. i tryed echo and usbmon but get the same result on ttyUSB3…

regards,
Damien