Author Message

<  Device Information  ~  New Device: Alcatel-sbell ASB TL131 TD-LTE USB Dongle

PostPosted: Sun Sep 08, 2013 9:31 am Reply with quote
Posts: 8Joined: Sun Sep 08, 2013 9:16 am
Alcatel-sbell ASB TL131 TD-LTE USB Dongle

un-switched
05c6:9024 Qualcomm, Inc.

switched
05c6:9025 Qualcomm HSUSB Device

switch code
Code:
usb_modeswitch -v 05c6 -p 9024 -M "5553424360F6FA8700000000000106EE000100000000000000000000000000"


So far, it did work well. Then you can use "adb shell" to log into the"Application Processor"of this Gobi device.


Application Processor
Machine: QCT MSM9615 CDP

Code:
/sbin # cat /proc/cpuinfo
Processor       : ARMv7 Processor rev 1 (v7l)
BogoMIPS        : 274.02
Features        : swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4
CPU implementer : 0x41
CPU architecture: 7
CPU variant     : 0x0
CPU part        : 0xc05
CPU revision    : 1

Hardware        : QCT MSM9615 CDP
Revision        : 0000
Serial          : 0000000000000000





but I haven't dial up successfully for now.

usbserial
I tried usbserial driver, it can be recognized as
ttyUSB0,ttyUSB1,ttyUSB2,ttyUSB3

But none of them response to "AT" command, which in windows driver, the modem serial port did response to "AT" command.

"ATI" command response as following ( in windows driver):
Code:
Manufacturer: QUALCOMM INCORPORATED
Model: 4070
Revision: M9615A-CETWTAZM-4.0.12043  1  [Mar 08 2013 03:00:00]
IMEI: 86*************
+GCAP: +CGSM

OK


qmi_wwan driver
I tried qmi_wwan driver (on openwrt), also failed.
I added a line in drivers/net/usb/qmi_wwan.c:
Code:
{QMI_GOBI_DEVICE(0x05c6, 0x9025)},  /* scateu test LTE alcatel-sbell */


then dmesg said:
Quote:
[ 64.150000] qmi_wwan: probe of 1-1:1.0 failed with error -22


lsusb -v -d 05c6:9025
Code:
Bus 001 Device 009: ID 05c6:9025 Qualcomm, Inc. Qualcomm HSUSB Device
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x05c6 Qualcomm, Inc.
  idProduct          0x9025 Qualcomm HSUSB Device
  bcdDevice            2.32
  iManufacturer           1 Android
  iProduct                2 Android
  iSerial                 3 0123456789ABCDEF
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          206
    bNumInterfaces          6
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    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               0
      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               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass     66
      bInterfaceProtocol      1
      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               0
      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               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      ** UNRECOGNIZED:  05 24 00 10 01
      ** UNRECOGNIZED:  05 24 01 00 00
      ** UNRECOGNIZED:  04 24 02 02
      ** UNRECOGNIZED:  05 24 06 00 00
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x84  EP 4 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x000a  1x 10 bytes
        bInterval               9
      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               0
      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               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      ** UNRECOGNIZED:  05 24 00 10 01
      ** UNRECOGNIZED:  05 24 01 00 00
      ** UNRECOGNIZED:  04 24 02 02
      ** UNRECOGNIZED:  05 24 06 00 00
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x000a  1x 10 bytes
        bInterval               9
      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               0
      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               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        4
      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     0x88  EP 8 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0008  1x 8 bytes
        bInterval               9
      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               0
      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               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        5
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              4 Mass Storage
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x89  EP 9 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)


usb_modeswitch output
Code:
# usb_modeswitch -v 05c6 -p 9024 -M "5553424360F6FA8700000000000106EE000100000000000000000000000000"
Looking for default devices ...
   found matching product ID
   adding device
 Found device in default mode, class or configuration (1)
Accessing device 008 on bus 001 ...
Getting the current device configuration ...
 OK, got current device configuration (1)
Using interface number 0
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
 OK, driver found ("usb-storage")
 OK, driver "usb-storage" detached

SCSI inquiry data (for identification)
-------------------------
  Vendor String: Linux   
   Model String: File-CD Gadget 
Revision String: 0328
-------------------------

USB description data (for identification)
-------------------------
Manufacturer: Android
     Product: Android
  Serial No.: 0123456789ABCDEF
-------------------------
Setting up communication with interface 0
Using endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
 OK, message successfully sent
Resetting response endpoint 0x81
Resetting message endpoint 0x01
-> Run lsusb to note any changes. Bye.



Last edited by scateu on Sun Sep 08, 2013 9:43 am, edited 2 times in total.

Offline Profile
PostPosted: Sun Sep 08, 2013 9:35 am Reply with quote
Posts: 1148Location: Koh Samui, THJoined: Wed Jul 11, 2012 3:14 pm
Show output of lsusb -v -d 05c6:9025


Offline Profile
PostPosted: Sun Sep 08, 2013 9:46 am Reply with quote
Posts: 8Joined: Sun Sep 08, 2013 9:16 am
LOM wrote:
Show output of lsusb -v -d 05c6:9025


added on the end of the post above.


Offline Profile
PostPosted: Sun Sep 08, 2013 2:45 pm Reply with quote
Posts: 1148Location: Koh Samui, THJoined: Wed Jul 11, 2012 3:14 pm
You would probably had been more successful with the qmi driver if you had added the id as a QMI_GOBI1K_DEVICE which has interface 3 defined as qmi interface, QMI_GOBI_DEVICE has interface 0. ([ 64.150000] qmi_wwan: probe of 1-1:1.0 failed with error -22)

Interface 2 and 3 looks like net interfaces (dual qmi interfaces for improved speed ?) and interface 4 looks like a serial modem.


Offline Profile
PostPosted: Sun Sep 08, 2013 5:51 pm Reply with quote
Posts: 8Joined: Sun Sep 08, 2013 9:16 am
LOM wrote:
You would probably had been more successful with the qmi driver if you had added the id as a QMI_GOBI1K_DEVICE which has interface 3 defined as qmi interface, QMI_GOBI_DEVICE has interface 0. ([ 64.150000] qmi_wwan: probe of 1-1:1.0 failed with error -22)

Interface 2 and 3 looks like net interfaces (dual qmi interfaces for improved speed ?) and interface 4 looks like a serial modem.


hi , I tried QMI_GOBI1K_DEVICE, failed again , but it seems to have one more log output, which says "bogus CDC Union"
Besides, the qmi_wwan probe error code turns to -1 (from -22).
Code:
[  226.010000] usb 1-1: new high-speed USB device number 2 using ehci-platform
[  226.440000] usb 1-1: USB disconnect, device number 2
[  226.740000] usb 1-1: new high-speed USB device number 3 using ehci-platform
[  227.070000] usb 1-1: USB disconnect, device number 3
[  227.400000] usb 1-1: new high-speed USB device number 4 using ehci-platform
[  227.560000] qmi_wwan 1-1:1.3: bogus CDC Union: master=0, slave=0
[  227.570000] qmi_wwan: probe of 1-1:1.3 failed with error -1


Offline Profile
PostPosted: Mon Sep 09, 2013 4:09 am Reply with quote
Posts: 1148Location: Koh Samui, THJoined: Wed Jul 11, 2012 3:14 pm
Seems you are not the only one one having problem getting response to AT cmds on the modem interface:

https://www.codeaurora.org/forum/projec ... ully-linux

and also not responding to a qmi probe:

https://developer.qualcomm.com/forum/qd ... gobi/23647

Let's see if we can get a qmi expert to show up and shed some light on this, are you awake Björn? :)

While waiting, it would be good if you could try and find the windows .inf files and upload them here, those files are often found in a driver directory in the path where windows installs the communication manager and drivers from the cd-rom of the dongle.


Offline Profile
PostPosted: Mon Sep 09, 2013 10:13 am Reply with quote
Posts: 8Joined: Sun Sep 08, 2013 9:16 am
LOM wrote:
Seems you are not the only one one having problem getting response to AT cmds on the modem interface:

https://www.codeaurora.org/forum/projec ... ully-linux

and also not responding to a qmi probe:

https://developer.qualcomm.com/forum/qd ... gobi/23647

Let's see if we can get a qmi expert to show up and shed some light on this, are you awake Björn? :)

While waiting, it would be good if you could try and find the windows .inf files and upload them here, those files are often found in a driver directory in the path where windows installs the communication manager and drivers from the cd-rom of the dongle.


Here comes the windows driver.

In windows ,the driver generate 5 devices:
#1.Qualcomm HS-USB Diagnostics 9025(COM61)
#2.Qualcomm HS-USB Android Modem 9025 (COM59)
#3.Qualcomm HS-USB NMEA 9025(COM60)
#4.Qualcomm Wireless HS-USB Ethernet Adapter 9025
#5.Android Composite ADB Interface

I found out that even #1 #2 #3 device are disabled (in Windows Device Management), 4G LTE-TDD original factory dial program works well. That is to say, in 4G mode doesn't use usbserial to control the USB dongle. But when #4 or #5 device is disabled, the original factory dial program won't work.

And in this USB dongle's 3G mode, #2 device is needed.


Offline Profile
PostPosted: Mon Sep 09, 2013 10:44 am Reply with quote
Posts: 1148Location: Koh Samui, THJoined: Wed Jul 11, 2012 3:14 pm
ok, it looks like the definition fom the qualcom developers forum is correct
(# DESCRIPTION: DIAG + ADB + MODEM + NMEA + QMI_RMNET + Mass Storage (Android) ) and matches the .inf files you provided.

%QcomDevice90250% = QportInstall00, USB\VID_05C6&PID_9025&MI_00

%QUALCOMM90252% = Modem2, USB\VID_05C6&PID_9025&MI_02
%QcomDevice90253% = QportInstall00, USB\VID_05C6&PID_9025&MI_03
%qcwwan.DeviceDesc90254% = qcwwan.ndi, USB\VID_05C6&PID_9025&MI_04

(interface 1 is an Android debug interface)

Most highspeed dongles operates over a net type interface since one can not reach much higher speed than 25-30Mbps over the serial ppp modem interface, thats why it works in windows without serial interfaces enabled.

Include the id and the interface number (4) in section 3 (QMI_FIXED_INTF devices) of qmi_wwan and test again.
You may even get the serial interfaces (0,2,3) working if you include them in the qcserial driver instead of using usb-serial.


Offline Profile
PostPosted: Mon Sep 09, 2013 11:31 am Reply with quote
Posts: 8Joined: Sun Sep 08, 2013 9:16 am
Good news!
I add this to qmi_wwan.c
Code:
{QMI_FIXED_INTF(0x05c6, 0x9025, 4)},    /* scateu test LTE alcatel-luncent */


and bingo!
Code:
[  126.850000] usb 1-1: new high-speed USB device number 2 using ehci-platform
[  127.370000] usb 1-1: USB disconnect, device number 2
[  127.700000] usb 1-1: new high-speed USB device number 3 using ehci-platform
[  127.870000] qmi_wwan 1-1:1.4: cdc-wdm0: USB WDM device
[  127.870000] qmi_wwan 1-1:1.4 wwan0: register 'qmi_wwan' at usb-ehci-platform-1, WWAN/QMI device, 72:f3:1c:af:54:20



Code:
root@OpenWrt:~# ifconfig -a
br-lan    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet addr:192.168.21.1  Bcast:192.168.21.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0      Link encap:Ethernet  HWaddr 12:34:DE:AD:BE:EF
          inet addr:192.168.1.254  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::1034:deff:fead:beef/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:505 errors:0 dropped:3 overruns:0 frame:0
          TX packets:446 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:49276 (48.1 KiB)  TX bytes:154770 (151.1 KiB)
          Interrupt:4

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:26 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2132 (2.0 KiB)  TX bytes:2132 (2.0 KiB)

wlan0     Link encap:Ethernet  HWaddr 12:34:DE:AD:BE:EF
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wwan0     Link encap:Ethernet  HWaddr 72:f3:1c:af:54:20
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)



and /dev/cdc-wdm0 comes up!

but what should i do next?

should I manage to capture something about apn,username,password like
Code:
config interface 'broadband'
    option ifname 'wwan0'
    option proto 'qmi'
    option pincode '1234'
    option apn 'web.vodafone.de'
    option username 'user'
    option password 'password'
    # if you want a sepearate LTE APN to be used, set
    option lte_apn_use '1'
    option lte_apn 'web.vodafone.de'
    option lte_username 'user'
    option lte_password 'password'

And how can I get the information from windows driver?

I tried to capture the windows tcpip stream in Qualcomm Wireless HS-USB Ethernet Adapter.

The first stream is DHCP Discover-Offer-Request-ACK procedure.
So, I think information about apn,username,password,pincode can be captured on Android Composite ADB Interface.


Offline Profile
PostPosted: Mon Sep 09, 2013 12:27 pm Reply with quote
Posts: 8Joined: Sun Sep 08, 2013 9:16 am
after I install libqmi
Code:
# qmicli -d /dev/cdc-wdm0 --nas-get-signal-strength
[/dev/cdc-wdm0] Successfully got signal strength
Current:
        Network 'lte': '-76 dBm'
Other:
        Network 'cdma-1xevdo': '-125 dBm'
RSSI:
        Network 'lte': '-76 dBm'
        Network 'cdma-1xevdo': '-125 dBm'
ECIO:
        Network 'lte': '-31.5 dBm'
        Network 'cdma-1xevdo': '-2.5 dBm'
IO: '-106 dBm'
SINR: (8) '9.0 dB'
RSRQ:
        Network 'lte': '-7 dB'
SNR:
        Network 'lte': '12.0 dB'
RSRP:
        Network 'lte': '-103 dBm'



and
Code:
qmicli -d /dev/cdc-wdm0 --wds-start-network=
[/dev/cdc-wdm0] Network started
        Packet data handle: 1145193736



seems to have dialed successfully

but when I run
ifconfig wwan0 up
udhcpc wwan0

then the whole system crashed....


Offline Profile
PostPosted: Mon Sep 09, 2013 6:19 pm Reply with quote
Posts: 1148Location: Koh Samui, THJoined: Wed Jul 11, 2012 3:14 pm
scateu wrote:
but when I run
ifconfig wwan0 up
udhcpc wwan0

then the whole system crashed....


Is that a typo or the cmd you issued?
You need the -i switch for udhcpc when you specify the interface (udhcpc -i wwan0).


Offline Profile
PostPosted: Mon Sep 09, 2013 8:04 pm Reply with quote
Posts: 8Joined: Sun Sep 08, 2013 9:16 am
It Works!

I mistake it with dhclient, my fault..

Hallelujah from TDD-LTE!

Thank you LOM!


Offline Profile
PostPosted: Tue Sep 10, 2013 9:48 am Reply with quote
Posts: 165Location: Oslo, NorwayJoined: Thu Mar 15, 2012 10:47 pm
LOM wrote:
ok, it looks like the definition fom the qualcom developers forum is correct
(# DESCRIPTION: DIAG + ADB + MODEM + NMEA + QMI_RMNET + Mass Storage (Android) ) and matches the .inf files you provided.


Yup, that's nice and I see that the ADB and QMI functions are verified. I'll go add the QMI now.

Quote:
You may even get the serial interfaces (0,2,3) working if you include them in the qcserial driver instead of using usb-serial.


But I wonder about this. I did add a few Sierra devices with non-Gobi layout, but it doesn't scale well to keep adding 3 entries for every device with 3 serial functions. So I'm more tempted to add this device to the option driver with an appropriate blacklist instead. Unless this is one device among a large number of new Gobi Xk devices with similar layout? In which case it would make sense to add code for such devices to qcserial.

Anyone know? Otherwise I think I'll just add it to theoption driver for now. We can always change this later.


EDIT: I took a quick look at the Windows*.inf files. Extremely interesting. Thanks a lot for posting that.

Among the interesting stuff there, I note that there are several device IDs with stuff like this:

Code:
%qcwwan.DeviceDesc90333%    = qcwwan.ndi, USB\VID_05C6&PID_9033&MI_03
%qcwwan.DeviceDesc90334%    = qcwwan.ndi, USB\VID_05C6&PID_9033&MI_04
%qcwwan.DeviceDesc90335%    = qcwwan.ndi, USB\VID_05C6&PID_9033&MI_05
%qcwwan.DeviceDesc90336%    = qcwwan.ndi, USB\VID_05C6&PID_9033&MI_06

and even
Code:
%qcwwan.DeviceDesc90622%    = qcwwan.ndi, USB\VID_05C6&PID_9062&MI_02
%qcwwan.DeviceDesc90623%    = qcwwan.ndi, USB\VID_05C6&PID_9062&MI_03
%qcwwan.DeviceDesc90624%    = qcwwan.ndi, USB\VID_05C6&PID_9062&MI_04
%qcwwan.DeviceDesc90625%    = qcwwan.ndi, USB\VID_05C6&PID_9062&MI_05
%qcwwan.DeviceDesc90626%    = qcwwan.ndi, USB\VID_05C6&PID_9062&MI_06
%qcwwan.DeviceDesc90627%    = qcwwan.ndi, USB\VID_05C6&PID_9062&MI_07
%qcwwan.DeviceDesc90628%    = qcwwan.ndi, USB\VID_05C6&PID_9062&MI_08
%qcwwan.DeviceDesc90629%    = qcwwan.ndi, USB\VID_05C6&PID_9062&MI_09


That's 8(!) QMI wwan functions in one device. Nice. I was hoping we would see something like that.

There is also a very large number of Qualcomm device IDs we haven't seen yet in those files. I assume that many of those are used in different OEM designs which we may never hear about. But we should probably just add them all, given that any Windows system can run Linux.


Offline Profile
PostPosted: Tue Sep 10, 2013 10:45 am Reply with quote
Posts: 165Location: Oslo, NorwayJoined: Thu Mar 15, 2012 10:47 pm
scateu wrote:
Alcatel-sbell ASB TL131 TD-LTE USB Dongle

un-switched
05c6:9024 Qualcomm, Inc.

switched
05c6:9025 Qualcomm HSUSB Device

switch code
Code:
usb_modeswitch -v 05c6 -p 9024 -M "5553424360F6FA8700000000000106EE000100000000000000000000000000"




How did you figure out that command? Snooping on Windows?

I also wonder about Windows8 and this device. I suspect that it could also support MBIM. Is that correct? Could you post the output of "lsusb -v -d 05c6:9024" before switching as well?

Qualcomm devices have traditionally provided a QDL function in their boot loader, but I guess this could be moved to some other mode since these modern devices have application firmware in flash. But I would be surprised if a new device like this didn't also provide a Windows8 configuration with MBIM. If so, then I believe that should be used by default in Linux as well


Offline Profile
PostPosted: Tue Sep 10, 2013 10:50 am Reply with quote
Posts: 8Joined: Sun Sep 08, 2013 9:16 am
before switching:
Code:
$ lsusb -v -d 05c6:9024

Bus 002 Device 010: ID 05c6:9024 Qualcomm, Inc.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x05c6 Qualcomm, Inc.
  idProduct          0x9024
  bcdDevice            2.32
  iManufacturer           1 Android
  iProduct                2 Android
  iSerial                 3 0123456789ABCDEF
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           32
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              4 Mass Storage
      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               0
      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               1
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)



Yes, I did snooping windows driver to get the message, using USBlyzer


Offline Profile

Display posts from previous:  Sort by:

All times are UTC + 1 hour [ DST ]
Page 1 of 2
18 posts
Go to page 1, 2  Next
Users browsing this forum: Google [Bot] and 1 guest
Search for:
Post new topic  Reply to topic
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum
cron