qmicli / Sierra EM7455
Sebastian Sjoholm
sebastian.sjoholm at gmail.com
Wed Mar 9 19:35:44 UTC 2016
Hi,
I seem to have issues with the Sierra Wireless EM7455 and qmicli, it seems that I get problems already in the start of the communication, and it does not really matter what I send to the modem, it will fail with the same error as below:
root at x046:~# qmicli -d /dev/cdc-wdm0 --dms-get-model -v
[09 Mar 2016, 20:09:05] [Debug] [/dev/cdc-wdm0] Opening device with flags 'none'...
[09 Mar 2016, 20:09:05] [Debug] QMI Device at '/dev/cdc-wdm0' ready
[09 Mar 2016, 20:09:05] [Debug] [/dev/cdc-wdm0] Assuming service 'dms' is supported...
[09 Mar 2016, 20:09:05] [Debug] [/dev/cdc-wdm0] Allocating new client ID...
[09 Mar 2016, 20:09:05] [Debug] [/dev/cdc-wdm0] Sent message...
<<<<<< RAW:
<<<<<< length = 16
<<<<<< data = 01:0F:00:00:00:00:00:01:22:00:04:00:01:01:00:02
[09 Mar 2016, 20:09:05] [Debug] [/dev/cdc-wdm0] Sent message (translated)...
<<<<<< QMUX:
<<<<<< length = 15
<<<<<< flags = 0x00
<<<<<< service = "ctl"
<<<<<< client = 0
<<<<<< QMI:
<<<<<< flags = "none"
<<<<<< transaction = 1
<<<<<< tlv_length = 4
<<<<<< message = "Allocate CID" (0x0022)
<<<<<< TLV:
<<<<<< type = "Service" (0x01)
<<<<<< length = 1
<<<<<< value = 02
<<<<<< translated = dms
error: couldn't create client for the 'dms' service: CID allocation failed in the CTL client: Transaction timed out
I am using the latest qmicli I could get via Debian Sid.
root at x046:~# qmicli —version
qmicli 1.12.6
Copyright (C) 2015 Aleksander Morgado
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
root at x046:~#
The EM7455 was updated to the latest firmware, that seems to be now the release version.
ati
Manufacturer: Sierra Wireless, Incorporated
Model: EM7455
Revision: SWI9X30C_02.08.02.00 r5428 CARMD-EV-FRMWR2 2016/01/06 20:38:53
MEID: 35432407003xxx
IMEI: 35432407003xxxx
IMEI SV: 4
FSN: LF533510920410
+GCAP: +CGSM,+DS,+ES
OK
I have configured the USB composition as following, as the default it comes with CDC_MBIM active.
at!usbcomp?
Config Index: 1
Config Type: 1 (Generic)
Interface bitmask: 0000010D (diag,nmea,modem,rmnet0)
OK
I have latest kernel from mainline;
root at x046:~# uname -a
Linux x046 4.5.0-rc7-NONAME-00337-g7f02bf6 #1 SMP Wed Mar 9 14:41:03 CET 2016 armv7l GNU/Linux
root at x046:~#
The USB events from dmesg;
root at x046:~# dmesg |grep usb
[ 0.686885] usbcore: registered new interface driver usbfs
[ 0.686953] usbcore: registered new interface driver hub
[ 0.687059] usbcore: registered new device driver usb
[ 1.078652] usbcore: registered new interface driver usb-storage
[ 1.406957] usb 2-1: new high-speed USB device number 2 using ci_hdrc
[ 1.427686] usbcore: registered new interface driver usbhid
[ 1.427690] usbhid: USB HID core driver
[ 1.427778] usbcore: registered new interface driver r8712u
[ 12.012460] usb 2-1.2: new high-speed USB device number 3 using ci_hdrc
[ 12.091715] usb 2-1.2: config 1 has an invalid interface number: 8 but max is 3
[ 12.091739] usb 2-1.2: config 1 has no interface number 1
[ 12.235717] usbcore: registered new interface driver usbserial
[ 12.235787] usbcore: registered new interface driver usbserial_generic
[ 12.235858] usbserial: USB Serial support registered for generic
[ 12.242258] usbcore: registered new interface driver qcserial
[ 12.242342] usbserial: USB Serial support registered for Qualcomm USB modem
[ 12.253858] usb 2-1.2: Qualcomm USB modem converter now attached to ttyUSB0
[ 12.274148] usb 2-1.2: Qualcomm USB modem converter now attached to ttyUSB1
[ 12.276974] usb 2-1.2: Qualcomm USB modem converter now attached to ttyUSB2
[ 12.281253] usbcore: registered new interface driver cdc_wdm
[ 12.303536] qmi_wwan 2-1.2:1.8 wwan0: register 'qmi_wwan' at usb-ci_hdrc.1-1.2, WWAN/QMI device, 32:5a:27:f4:ce:59
[ 12.307546] usbcore: registered new interface driver qmi_wwan
root at x046:~#
As sidenote I tried the CDC_MBIM as well, but I seem to get transaction time out on that as well.
Regards,
Sebastian
More information about the libqmi-devel
mailing list