SDK not working on MC7455

IoT Modules MC/EM Series
1

Ive tried to follow the QMI SDK to a T and unable to connect to the unit but not sure where im messing up

i built the SDK executable
loaded drivers

when i do the command it shows this in /var/log/user.log

Also do users use mmcli or qmicli

2

Hi,

I believe all pre-requisites prior to use all sierra sdk tools. Could you list down “/dev/q*” because all sierra sdk tools are referring to these devices.

3

The modem is configured for MBIM. It must be in QMI mode for the SDK. I believe this is covered by the SDK docs. Use AT!USBCOMP to change the configuration.

4

Actually i dont see anything showing ls /dev/q*

how do i submit the AT command to change it

do i do something like minicom into ttyUSB2 ?

5

Ohh just got in … learning ova here lOL never been in AT LOL

BUT when i do this

AT!USBCOMP
ERROR

RE-edit found out theres some sort aof ENTERCND LOL

6

Hello,

Did you install and configure “GobiNet” and “GobiSerial” drivers as required by that SDK ? Based on you input that module is working fine on linux/ubuntu because I’ve the same on DELL E7240 running Ubuntu 17.04 and could get internet access. Without “GobiNet” and “GobiSerial” drivers, system would generate “/dev/cdc-wdm1” and “/dev/cdc-wdm2”.

7

pi@raspberrypi:~/sdk $ lsmod | grep -i gob
GobiSerial 10665 2
usbserial 29964 5 GobiSerial
GobiNet 104246 0

8

Hello,

From that related documentation, please refer below statements.

3.3.1.
Host Setup
The Linux distribution may have in built drivers and applications that can interfere with SDK process’s
execution. The below Qualcomm drivers, if present, need to be black listed.


qcserial
qmi_wwan
Please black list them as below (example is for Ubuntu). Add the 2 entries to the
“/etc/modprobe.d/blacklist-modem.conf” file and restart the host
blacklist qcserial
blacklist qmi_wwan
is another application that can interfere with the SDK’s operation. Please remove it
and restart the host. Below example is for an Ubuntu PC:
“Modem Manager”
#sudo apt-get remove modemmanager
#sudo killall -9 modemmanager
#sudo reboot

9

I did do the blacklist in the way beggining

I did try out modemmanager but i i did a purge but i ll do a autoremove now .

i rebooted

but dmesg still showing it up at cdc_mbim

10

i still cant seem to get it its still showing cdc_mbim

[    7.566736] GobiNet: 2017-01-04/SWI_2.40
[    7.567593] usbcore: registered new interface driver GobiNet
[    7.585035] usbcore: registered new interface driver cdc_ncm
[    7.682117] usbcore: registered new interface driver cdc_wdm
[    7.755037] usbcore: registered new interface driver usbserial
[    7.755263] usbcore: registered new interface driver usbserial_generic
[    7.755441] usbserial: USB Serial support registered for generic
[    7.772723] usbcore: registered new interface driver GobiSerial
[    7.772925] usbserial: USB Serial support registered for GobiSerial
[    7.840900] cdc_mbim 1-1:1.12: cdc-wdm0: USB WDM device
[    7.842646] cdc_mbim 1-1:1.12 wwan0: register 'cdc_mbim' at usb-20980000.usb-1, CDC MBIM, f2:a0:3e:5d:60:84
[    7.906800] GobiSerial 1-1:1.0: GobiSerial converter detected
[    7.912789] usbcore: registered new interface driver cdc_mbim
[    7.913171] usb 1-1: GobiSerial converter now attached to ttyUSB0
[    8.058356] GobiSerial 1-1:1.3: GobiSerial converter detected
[    8.062743] usb 1-1: GobiSerial converter now attached to ttyUSB1
[    8.086968] GobiSerial: 2017-01-04/SWI_2.27:GobiSerial
11

Hello,

Have a good day. I’ve MC7455 module installed on DELL E7240 running Ubuntu 17.04 where result as below:

Manufacturer: Sierra Wireless, Incorporated
Model: MC7455
Revision: SWI9X30C_02.24.03.00 r6978 CARMD-EV-FRMWR2 2017/03/02 13:36:45
MEID: 35907206065989
IMEI: 359072060659899
IMEI SV: 9
FSN: LQ708248800410
+GCAP: +CGSM

at!entercnd=“A710”
OK
at!usbcomp?
Config Index: 1
Config Type: 1 (Generic)
Interface bitmask: 0000050D (diag,nmea,modem,rmnet0,rmnet1)

You could change “USBCOMP” of your module to “1,1,50D” and reset that module “at!reset” or just reboot your machine and should be shown as below:

zabo5515@zabo5515-E7240:~$ dmesg | grep -i qmi_wwan
[ 3.024236] qmi_wwan 2-7:1.8: cdc-wdm1: USB WDM device
[ 3.024669] qmi_wwan 2-7:1.8 wwan0: register ‘qmi_wwan’ at usb-0000:00:14.0-7, WWAN/QMI device, 8e:c0:45:2f:c2:73
[ 3.025049] qmi_wwan 2-7:1.10: cdc-wdm2: USB WDM device
[ 3.025922] qmi_wwan 2-7:1.10 wwan1: register ‘qmi_wwan’ at usb-0000:00:14.0-7, WWAN/QMI device, 8e:c0:45:2f:c2:73
[ 3.025969] usbcore: registered new interface driver qmi_wwan
[ 3.297890] qmi_wwan 2-7:1.8 wwp0s20u7i8: renamed from wwan0
[ 3.315593] qmi_wwan 2-7:1.10 wwp0s20u7i10: renamed from wwan1

12

should i remove the qmi_wwan in the modprobe.d/blacklist-modem-conf then

ill try it hehe

13

Hello,

Once again and I would like to update mine when I’ve configured for GobiSerial and GobiNet drivers and others as requested by that Sierra SDK where result as below:

zabo5515@zabo5515-E7240:~$ ls -al /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 Jun 26 09:07 /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 1 Jun 26 09:07 /dev/ttyUSB1
crw-rw---- 1 root dialout 188, 2 Jun 26 09:07 /dev/ttyUSB2
zabo5515@zabo5515-E7240:~$ ls -al /dev/qc*
crw------- 1 root root 241, 0 Jun 26 09:06 /dev/qcqmi0
crw------- 1 root root 240, 0 Jun 26 09:06 /dev/qcqmi1

Above “qcqmi0 & qcqmi1” are used by that Sierra SDK tools.

14

OH cool SWEEEEEEET thanks i think im getting some success with qmi now.

this is rasberry Pi zero Wireless too hehe

pi@raspberrypi:~/sdk $ sudo ./SampleApps/Connection_Manager/bin/connectionmgrhostarmv6l ./build/bin/hostarmv6l/slqssdk 0
Instance ID :0
Session StateV4:1
Session StateV6:1
Instance ID :1
Session StateV4:1
Session StateV6:1

Please select one of the following options or press to exit:

  1. Start UMTS Data Session
  2. Start LTE Data Session
  3. Start CDMA Data Session
  4. Start RUIM data session