MC7421 Module does not see GobiSerial Driver

IoT Modules MC/EM Series
1

Hello,
We are currently using MC7304 module on our embedded board which is based on ARM. We use MC7304 with GobiSerial and GobiNet driver. Our linux kernel version is 4.1.15. There is no problem so far.

However, we changed to MC7421 Module and now we have some connection problems.
When we check usb drivers with “lsusb” command, Sierra Wireless Inc is appeared. You can see the output below.

ekb:~$ lsusb
Bus 001 Device 010: ID 0403:6010 Future Technology Devices International, Ltd FT2232C Dual USB-UART/FIFO IC
Bus 001 Device 009: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 001 Device 008: ID 08bb:2912 Texas Instruments 
Bus 001 Device 006: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 001 Device 005: ID 04d8:0c02 Microchip Technology, Inc. 
**Bus 001 Device 017: ID 1199:9090 Sierra Wireless, Inc.** 
Bus 001 Device 004: ID 08bb:2912 Texas Instruments 
Bus 001 Device 003: ID 0424:2517 Standard Microsystems Corp. Hub
Bus 001 Device 007: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2517 Standard Microsystems Corp. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ekb:~$ lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M
        |__ Port 1: Dev 7, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 480M
            |__ Port 2: Dev 6, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M
            |__ Port 3: Dev 8, If 0, Class=Audio, Driver=snd-usb-audio, 12M
            |__ Port 3: Dev 8, If 1, Class=Audio, Driver=snd-usb-audio, 12M
            |__ Port 3: Dev 8, If 2, Class=Audio, Driver=snd-usb-audio, 12M
            |__ Port 4: Dev 9, If 0, Class=Vendor Specific Class, Driver=cp210x, 12M
            |__ Port 7: Dev 10, If 0, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
            |__ Port 7: Dev 10, If 1, Class=Vendor Specific Class, Driver=ftdi_sio, 480M
        |__ Port 3: Dev 4, If 0, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 3: Dev 4, If 1, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 3: Dev 4, If 2, Class=Audio, Driver=snd-usb-audio, 12M
        **|__ Port 6: Dev 17, If 0, Class=Vendor Specific Class, Driver=, 480M**
        |__ Port 7: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M

Here you can see Gobi modules.

ekb:~$ **dmesg | grep Gobi**
[    1.561911] GobiNet: 2014-10-09/SWI_2.27
[    1.561991] usbcore: registered new interface driver GobiNet
[    1.562052] usbcore: registered new interface driver GobiSerial
[    1.562104] usbserial: USB Serial support registered for GobiSerial
[    1.562120] GobiSerial: 2014-07-21/SWI_2.20:GobiSerial

When we check dmesg, no ttyUSB device created for Sierra MC7421. You can see usb 1-1.6 path below

ekb:/sys/kernel/debug/usb$ dmesg | grep usb
[    0.276923] usbcore: registered new interface driver usbfs
[    0.276998] usbcore: registered new interface driver hub
[    0.277085] usbcore: registered new device driver usb
[    0.277276] 2000000.aips-bus:usbphy_nop1 supply vcc not found, using dummy regulator
[    0.277411] 2000000.aips-bus:usbphy_nop2 supply vcc not found, using dummy regulator
[    0.572538] usbcore: registered new interface driver smsc95xx
[    0.572850] usbcore: registered new interface driver usb-storage
[    0.573041] usbcore: registered new interface driver usbserial
[    0.573100] usbcore: registered new interface driver usbserial_generic
[    0.573145] usbserial: USB Serial support registered for generic
[    0.573200] usbcore: registered new interface driver cp210x
[    0.573245] usbserial: USB Serial support registered for cp210x
[    0.573296] usbcore: registered new interface driver ftdi_sio
[    0.573338] usbserial: USB Serial support registered for FTDI USB Serial Device
[    0.573396] usbcore: registered new interface driver usb_ehset_test
[    0.574803] 2184800.usbmisc supply vbus-wakeup not found, using dummy regulator
[    0.606861] usbcore: registered new interface driver usbtouchscreen
[    0.923660] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[    1.353621] usb 1-1.2: new high-speed USB device number 3 using ci_hdrc
[    1.543615] usb 1-1.3: new full-speed USB device number 4 using ci_hdrc
[    1.561402] usbcore: registered new interface driver usbhid
[    1.561408] usbhid: USB HID core driver
[    1.561991] usbcore: registered new interface driver GobiNet
[    1.562052] usbcore: registered new interface driver GobiSerial
[    1.562104] usbserial: USB Serial support registered for GobiSerial
[    1.698371] usb_otg_vbus: disabling
[    1.733624] usb 1-1.7: new full-speed USB device number 5 using ci_hdrc
[    1.857255] input: Microchip Technology Inc. AR1100 HID-MOUSE as /devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/1-1.7/1-1.7:1.0/0003:04D8:0C02.0001/input/input0
[    1.857936] hid-generic 0003:04D8:0C02.0001: input: USB HID v1.11 Mouse [Microchip Technology Inc. AR1100 HID-MOUSE] on usb-ci_hdrc.1-1.7/input0
[    1.923656] usb 1-1.2.2: new full-speed USB device number 6 using ci_hdrc
[    2.038939] usb 1-1.2.2: cp210x converter now attached to ttyUSB0
[    2.113700] usb 1-1.1: new high-speed USB device number 7 using ci_hdrc
[    2.303726] usb 1-1.2.3: new full-speed USB device number 8 using ci_hdrc
[    2.513657] usb 1-1.2.4: new full-speed USB device number 9 using ci_hdrc
[    2.628978] usb 1-1.2.4: cp210x converter now attached to ttyUSB1
[    2.723717] usb 1-1.2.7: new high-speed USB device number 10 using ci_hdrc
[    2.843407] usb 1-1.2.7: Detected FT2232H
[    2.844244] usb 1-1.2.7: FTDI USB Serial Device converter now attached to ttyUSB2
[    2.847421] usb 1-1.2.7: Detected FT2232H
[    2.848075] usb 1-1.2.7: FTDI USB Serial Device converter now attached to ttyUSB3
[    3.512347] usbcore: registered new interface driver snd-usb-audio
[   17.463700] usb 1-1.6: new high-speed USB device number 11 using ci_hdrc
[   17.574686] usb 1-1.6: config 1 has an invalid interface number: 8 but max is 3
[   17.574712] usb 1-1.6: config 1 has no interface number 1
[   28.491685] usb 1-1.6: USB disconnect, device number 11
[   37.683690] usb 1-1.6: new high-speed USB device number 12 using ci_hdrc
[   37.794669] usb 1-1.6: config 1 has an invalid interface number: 8 but max is 3
[   37.794714] usb 1-1.6: config 1 has no interface number 1
[   48.715537] usb 1-1.6: USB disconnect, device number 12
[   57.913683] usb 1-1.6: new high-speed USB device number 13 using ci_hdrc
[   58.024833] usb 1-1.6: config 1 has an invalid interface number: 8 but max is 3
[   58.024867] usb 1-1.6: config 1 has no interface number 1
[   68.683670] usb 1-1.6: USB disconnect, device number 13
[   77.873689] usb 1-1.6: new high-speed USB device number 14 using ci_hdrc
[   77.984508] usb 1-1.6: config 1 has an invalid interface number: 8 but max is 3
[   77.984523] usb 1-1.6: config 1 has no interface number 1
[   88.907681] usb 1-1.6: USB disconnect, device number 14
[   98.103662] usb 1-1.6: new high-speed USB device number 15 using ci_hdrc
[   98.214664] usb 1-1.6: config 1 has an invalid interface number: 8 but max is 3
[   98.214691] usb 1-1.6: config 1 has no interface number 1
[  108.875660] usb 1-1.6: USB disconnect, device number 15
[  118.073711] usb 1-1.6: new high-speed USB device number 16 using ci_hdrc
[  118.184544] usb 1-1.6: config 1 has an invalid interface number: 8 but max is 3
[  118.184571] usb 1-1.6: config 1 has no interface number 1
[  129.099511] usb 1-1.6: USB disconnect, device number 16
[  129.843657] usb 1-1.6: new high-speed USB device number 17 using ci_hdrc

We read documentation of Sierra MC7421 and we have confused. Our kernel version is older than 4.4 and is that possible to use Gobi drivers with MC7421? Do we have to use qcserial, qmi_wwan and usb_wwan drivers instead of Gobi Drivers?

Thanks for your support.

2

You need to use mbpl driver

https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/

3

Thanks for fast reply,

We can follow Software Integration and Development Guide. But, in “1.3. Supported Kernel Versions” topic, it said that, MBPL supports open source kernel versions 4.4 and newer. Our kernel version is 4.1.15. Can it be a problem?

We have already cross-compiled mbpl drivers and get .ko files. When we try to load modules via modprobe, we get some errors like “modprobe Exec format error”

Do you have any idea?

4

then you need to use Gobi driver for old kernel version.

BTW, there is chance that no AT port enabled in AT!USBCOMP…
You can verify in Windows platform first.

5

As we mentioned before, we try to connect to MC7421 with Gobi driver which works with MC7304 perfectly. But no ttyUSBx appears in Linux for MC7421. So, we can’t access AT commands. You can see outputs in my first entry.
Could you explain what we will do step by step? What do we verify in Windows to?

Thanks your support

6

you can install this driver together with attached .ini file:

Configuration.ini (84 Bytes)
image

7

You need more recent Gobi-drivers. The 9090/9091 device IDs were added in S2.29N2.45

But there is a second problem here which you’ll have to solve after getting the correct drivers installed: The module is booted in “QDL” (boot loader) mode. Maybe waiting for a firmware? Or failing to boot for some reason? In any case, the easiest is to attempt a firmware upgrade once you have drivers in place.

8

Thanks for your answer. I will upgrade Gobi Driver to S2.35N2.54. I will download it from github, right?(GitHub - DiUS/sierra-gobi-drivers: Sierra Linux QMI "Gobi" drivers for CI use) Because, I could not find Gobi Drivers in Sierra Sources
BTW, how could you understand that module is in bootloader mode? I will share you last updates after upgrade Gobi
Thank you in advance

9

source is still the autoritative source (pun intended :-). I would download it from there. You can find the Gobi drivers under the older modules at least. Or here:
https://source.sierrawireless.com/resources/airprime/software/usb-drivers-linux-qmi-software-history/

There are two indications:

  1. the product id is 9090 (boot) instead of 9091 (app)
  2. there is only one USB interface

EDIT: let me moderate that. I was looking only at your two lsusb dumps, which showed the above end result. But the dmesg dumps actually shows what happened:, despite missing the device ID: The module connects and disconnects 6 times before it ends up in the stable state shown by lsusb (“device number 17”). Thanks to the way the kernel always complains about the descriptors of these modules, we know that the first 6 attempts were in application mode (because “has no interface number 1” implies that there is more than one, and “invalid interface number: 8” means that one of those interfaces is QMI/RMNET)

Still don’t know why, but it does look like the module fails to boot into application mode. I believe the bootloader mode is a debugging and failsafe method to break out of an otherwise infinite boot loop. You might need help from support to fix the underlying issue… (don’t look at me - I’m just one of the other users here - being mentioned in the MBPL driver package doesn’t make me a Sierra Wireless employee :wink:

1 Like
10

First of all, thanks for your detailed explanation. I tough that you are one of the Sierra employees.

I upgraded Gobi Drivers to S2.42N2.64 version which you send me. Now, I can see GobiSerial and GobiNet drivers in dmesg. Also ttyUSB devices were created successfully. However; The module connects and disconnects 6 times again and ttyUSB devices were disconnected finally. Same behavior is seen in output of “lsusb -t” You can see my outputs below.

Dmesg output:

ekb:~$ dmesg | grep Gobi
[   17.101238] GobiNet: 2020-08-17/SWI_2.64
[   17.106926] GobiNet 1-1.6:1.8 eth1: register 'GobiNet' at usb-ci_hdrc.1-1.6, GobiNet Ethernet Device, 2e:26:c3:a6:36:08
[   17.107870] usbcore: registered new interface driver GobiNet
[   17.112348] usbcore: registered new interface driver GobiSerial
[   17.112473] usbserial: USB Serial support registered for GobiSerial
[   17.115880] GobiSerial 1-1.6:1.0: GobiSerial converter detected
[   17.116753] usb 1-1.6: GobiSerial converter now attached to ttyUSB0
[   17.117160] GobiSerial 1-1.6:1.2: GobiSerial converter detected
[   17.117675] usb 1-1.6: GobiSerial converter now attached to ttyUSB1
[   17.118458] GobiSerial 1-1.6:1.3: GobiSerial converter detected
[   17.118958] usb 1-1.6: GobiSerial converter now attached to ttyUSB2
[   17.119139] GobiSerial: 2020-08-17/SWI_2.42:GobiSerial
[   27.980480] GobiSerial driver ttyUSB0: GobiSerial converter now disconnected from ttyUSB0
[   27.980599] GobiSerial 1-1.6:1.0: device disconnected
[   27.982108] GobiSerial driver ttyUSB1: GobiSerial converter now disconnected from ttyUSB1
[   27.982232] GobiSerial 1-1.6:1.2: device disconnected
[   27.984253] GobiSerial driver ttyUSB2: GobiSerial converter now disconnected from ttyUSB2
[   27.984407] GobiSerial 1-1.6:1.3: device disconnected
[   27.987189] GobiNet 1-1.6:1.8 eth1: unregister 'GobiNet' usb-ci_hdrc.1-1.6, GobiNet Ethernet Device
[   37.287544] GobiSerial 1-1.6:1.0: GobiSerial converter detected
[   37.288029] usb 1-1.6: GobiSerial converter now attached to ttyUSB0
[   37.289098] GobiSerial 1-1.6:1.2: GobiSerial converter detected
[   37.289514] usb 1-1.6: GobiSerial converter now attached to ttyUSB1
[   37.290693] GobiSerial 1-1.6:1.3: GobiSerial converter detected
[   37.291104] usb 1-1.6: GobiSerial converter now attached to ttyUSB2
[   37.293524] GobiNet 1-1.6:1.8 eth1: register 'GobiNet' at usb-ci_hdrc.1-1.6, GobiNet Ethernet Device, 2e:26:c3:a6:36:08
[   48.203951] GobiSerial driver ttyUSB0: GobiSerial converter now disconnected from ttyUSB0
[   48.204016] GobiSerial 1-1.6:1.0: device disconnected
[   48.204631] GobiSerial driver ttyUSB1: GobiSerial converter now disconnected from ttyUSB1
[   48.204694] GobiSerial 1-1.6:1.2: device disconnected
[   48.206518] GobiSerial driver ttyUSB2: GobiSerial converter now disconnected from ttyUSB2
[   48.206587] GobiSerial 1-1.6:1.3: device disconnected
[   48.209999] GobiNet 1-1.6:1.8 eth1: unregister 'GobiNet' usb-ci_hdrc.1-1.6, GobiNet Ethernet Device
[   57.520609] GobiSerial 1-1.6:1.0: GobiSerial converter detected
[   57.521642] usb 1-1.6: GobiSerial converter now attached to ttyUSB0
[   57.524117] GobiSerial 1-1.6:1.2: GobiSerial converter detected
[   57.525287] usb 1-1.6: GobiSerial converter now attached to ttyUSB1
[   57.527499] GobiSerial 1-1.6:1.3: GobiSerial converter detected
[   57.528505] usb 1-1.6: GobiSerial converter now attached to ttyUSB2
[   57.533922] GobiNet 1-1.6:1.8 eth1: register 'GobiNet' at usb-ci_hdrc.1-1.6, GobiNet Ethernet Device, 2e:26:c3:a6:36:08
[   68.181707] GobiSerial driver ttyUSB2: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
[   68.193979] GobiSerial driver ttyUSB2: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
[   68.206084] GobiSerial driver ttyUSB2: usb_serial_generic_write_bulk_callback - nonzero urb status: -71
[   68.427713] GobiSerial driver ttyUSB0: GobiSerial converter now disconnected from ttyUSB0
[   68.427903] GobiSerial 1-1.6:1.0: device disconnected
[   68.428708] GobiSerial driver ttyUSB1: GobiSerial converter now disconnected from ttyUSB1
[   68.428899] GobiSerial 1-1.6:1.2: device disconnected
[   68.429982] GobiSerial driver ttyUSB2: GobiSerial converter now disconnected from ttyUSB2
[   68.430042] GobiSerial 1-1.6:1.3: device disconnected
[   68.432017] GobiNet 1-1.6:1.8 eth1: unregister 'GobiNet' usb-ci_hdrc.1-1.6, GobiNet Ethernet Device
[   77.740290] GobiSerial 1-1.6:1.0: GobiSerial converter detected
[   77.741144] usb 1-1.6: GobiSerial converter now attached to ttyUSB0
[   77.743247] GobiSerial 1-1.6:1.2: GobiSerial converter detected
[   77.744223] usb 1-1.6: GobiSerial converter now attached to ttyUSB1
[   77.746371] GobiSerial 1-1.6:1.3: GobiSerial converter detected
[   77.747243] usb 1-1.6: GobiSerial converter now attached to ttyUSB2
[   77.752110] GobiNet 1-1.6:1.8 eth1: register 'GobiNet' at usb-ci_hdrc.1-1.6, GobiNet Ethernet Device, 2e:26:c3:a6:36:08
[   88.396718] GobiSerial driver ttyUSB0: GobiSerial converter now disconnected from ttyUSB0
[   88.397012] GobiSerial 1-1.6:1.0: device disconnected
[   88.399602] GobiSerial driver ttyUSB1: GobiSerial converter now disconnected from ttyUSB1
[   88.399735] GobiSerial 1-1.6:1.2: device disconnected
[   88.402061] GobiSerial driver ttyUSB2: GobiSerial converter now disconnected from ttyUSB2
[   88.402325] GobiSerial 1-1.6:1.3: device disconnected
[   88.406053] GobiNet 1-1.6:1.8 eth1: unregister 'GobiNet' usb-ci_hdrc.1-1.6, GobiNet Ethernet Device
[   97.960378] GobiSerial 1-1.6:1.0: GobiSerial converter detected
[   97.961291] usb 1-1.6: GobiSerial converter now attached to ttyUSB0
[   97.963433] GobiSerial 1-1.6:1.2: GobiSerial converter detected
[   97.965440] usb 1-1.6: GobiSerial converter now attached to ttyUSB1
[   97.967902] GobiSerial 1-1.6:1.3: GobiSerial converter detected
[   97.968674] usb 1-1.6: GobiSerial converter now attached to ttyUSB2
[   97.976169] GobiNet 1-1.6:1.8 eth1: register 'GobiNet' at usb-ci_hdrc.1-1.6, GobiNet Ethernet Device, 2e:26:c3:a6:36:08
[  108.621458] GobiSerial driver ttyUSB0: GobiSerial converter now disconnected from ttyUSB0
[  108.621600] GobiSerial 1-1.6:1.0: device disconnected
[  108.623899] GobiSerial driver ttyUSB2: usb_serial_generic_submit_read_urb - usb_submit_urb failed: -19
[  108.632320] GobiSerial driver ttyUSB1: GobiSerial converter now disconnected from ttyUSB1
[  108.632471] GobiSerial 1-1.6:1.2: device disconnected
[  108.634364] GobiSerial driver ttyUSB2: GobiSerial converter now disconnected from ttyUSB2
[  108.634502] GobiSerial 1-1.6:1.3: device disconnected
[  108.636933] GobiNet 1-1.6:1.8 eth1: unregister 'GobiNet' usb-ci_hdrc.1-1.6, GobiNet Ethernet Device
[  118.187665] GobiSerial 1-1.6:1.0: GobiSerial converter detected
[  118.188123] usb 1-1.6: GobiSerial converter now attached to ttyUSB0
[  118.189034] GobiSerial 1-1.6:1.2: GobiSerial converter detected
[  118.189424] usb 1-1.6: GobiSerial converter now attached to ttyUSB1
[  118.190568] GobiSerial 1-1.6:1.3: GobiSerial converter detected
[  118.190991] usb 1-1.6: GobiSerial converter now attached to ttyUSB2
[  118.193286] GobiNet 1-1.6:1.8 eth1: register 'GobiNet' at usb-ci_hdrc.1-1.6, GobiNet Ethernet Device, 2e:26:c3:a6:36:08
[  128.843947] GobiSerial driver ttyUSB0: GobiSerial converter now disconnected from ttyUSB0
[  128.844011] GobiSerial 1-1.6:1.0: device disconnected
[  128.844636] GobiSerial driver ttyUSB1: GobiSerial converter now disconnected from ttyUSB1
[  128.844700] GobiSerial 1-1.6:1.2: device disconnected
[  128.845733] GobiSerial driver ttyUSB2: GobiSerial converter now disconnected from ttyUSB2
[  128.845921] GobiSerial 1-1.6:1.3: device disconnected
[  128.847942] GobiNet 1-1.6:1.8 eth1: unregister 'GobiNet' usb-ci_hdrc.1-1.6, GobiNet Ethernet Device
[  130.218930] GobiSerial 1-1.6:1.0: GobiSerial converter detected
[  130.219464] usb 1-1.6: GobiSerial converter now attached to ttyUSB0

lsusb output

ekb:~$ lsusb
Bus 001 Device 004: ID 04d8:0c02 Microchip Technology, Inc. 
Bus 001 Device 014: ID 1199:9091 Sierra Wireless, Inc. 
Bus 001 Device 003: ID 08bb:2912 Texas Instruments 
Bus 001 Device 008: ID 04d8:0c03 Microchip Technology, Inc. 
Bus 001 Device 007: ID 0403:601c Future Technology Devices International, Ltd 
Bus 001 Device 006: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2517 Standard Microsystems Corp. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsusb -t output

ekb:~$ lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M
        |__ Port 1: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 2: Dev 6, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 3: Dev 7, If 0, Class=Vendor Specific Class, Driver=usbfs, 480M
                |__ Port 4: Dev 8, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 3: Dev 3, If 0, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 3: Dev 3, If 1, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 3: Dev 3, If 2, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 6: Dev 14, If 0, Class=Vendor Specific Class, Driver=GobiSerial, 480M
        |__ Port 6: Dev 14, If 2, Class=Vendor Specific Class, Driver=GobiSerial, 480M
        |__ Port 6: Dev 14, If 3, Class=Vendor Specific Class, Driver=GobiSerial, 480M
        |__ Port 6: Dev 14, If 8, Class=Vendor Specific Class, Driver=GobiNet, 480M
        |__ Port 7: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M

After a while …

ekb:~$ lsusb
Bus 001 Device 004: ID 04d8:0c02 Microchip Technology, Inc. 
Bus 001 Device 015: ID 1199:9090 Sierra Wireless, Inc. 
Bus 001 Device 003: ID 08bb:2912 Texas Instruments 
Bus 001 Device 008: ID 04d8:0c03 Microchip Technology, Inc. 
Bus 001 Device 007: ID 0403:601c Future Technology Devices International, Ltd 
Bus 001 Device 006: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 0424:2517 Standard Microsystems Corp. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

ekb:~$ lsusb -t
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ci_hdrc/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M
        |__ Port 1: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
            |__ Port 2: Dev 6, If 0, Class=Hub, Driver=hub/4p, 480M
                |__ Port 3: Dev 7, If 0, Class=Vendor Specific Class, Driver=usbfs, 480M
                |__ Port 4: Dev 8, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 3: Dev 3, If 0, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 3: Dev 3, If 1, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 3: Dev 3, If 2, Class=Audio, Driver=snd-usb-audio, 12M
        |__ Port 6: Dev 15, If 0, Class=Vendor Specific Class, Driver=GobiSerial, 480M
        |__ Port 7: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
 here

I can see that device entered in bootloader mode. (I can understand PID:VID of it now. Thanks :slight_smile: )

We were able to take a step. But we still investigate how module enters bootloader mode. We were using MC7304 series before. We connected MC7421 to same connector on our board.(PCI Express Mini Card) I checked pinout and could not noticed any problem except USB3 interface. Could it be caused for USB3 interface?

I can try any suggestion from you :slight_smile:

PS: I can connect to /dev/ttyUSB0 via microcom on board. I get some meaningless characters. I have tried to change baudrate but it didn’t work.

11

The module isn’t supposed to do that. You should probably contact your FAE to get proper support. I assume they can help you with debug tools and checklists.

I don’t know if pin confusion can cause this, but I guess it’s possible. Should be easy to verify by testing the module with another host. For example a PC with a USB to mini-card adapter. If it works there, then the problem must be related to pinout or power supply.

If the module fails with other hosts, then you could try a firmware upgrade to see if that fixes the issue. I believe the upgrade tools are prepared to start from this state. Could be wrong - haven’t tried myself.

I’m afraid that’s all I got.

EDIT: As for the debug serial port in bootloader mode - I believe it speaks SAHARA. You won’t be able to do anything useful with a terminal application. But you can do a ram dump or upload files, with the proper tools.