Author Message

<  Device Information  ~  New device TP-Link MA260

PostPosted: Sun Jun 23, 2013 2:35 pm
Posts: 142Location: Oslo, NorwayJoined: Thu Mar 15, 2012 10:47 pm
Hello,

this modem just showed up in the discussions down under.

Unswitched ID is 2357:f000
Switched ID is 2357:9000

Switching command is the same as for the TP-Link MA180:
5553424312345678000000000000061b000000020000000000000000000000

usb-devices before switching
http://forums.whirlpool.net.au/forum-re ... p=61#r1204

usb-devices after switching:
http://forums.whirlpool.net.au/forum-re ... p=63#r1257

I expect we'll add it to option + qmi_wwan, but still need confirmation on the QMI interface


Offline Profile
PostPosted: Mon Jun 24, 2013 6:59 pm
Site AdminPosts: 4834Joined: Sat Nov 03, 2007 12:30 am
Thanks, it's marked for addition!


Offline Profile
PostPosted: Sat Aug 24, 2013 1:26 pm
Posts: 64Joined: Sun Jul 17, 2011 12:08 pm
bmork wrote:
Hello,



I expect we'll add it to option + qmi_wwan, but still need confirmation on the QMI interface



qmi works!


Code:
Bus 001 Device 004: ID 2357:9000 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x2357
  idProduct          0x9000
  bcdDevice            0.00
  iManufacturer           3 TP-LINK, Incorporated
  iProduct                2 TP-LINK HSPA+ Modem
  iSerial                 4 863745010146666
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength          138
    bNumInterfaces          5
    bConfigurationValue     1
    iConfiguration          1 TP-LINK Configuration
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    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              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         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              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
      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
    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        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     0x86  EP 6 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     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            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)


[ 100.479184] usb 1-1: new high-speed USB device number 3 using ehci-pci
[ 100.596578] usb 1-1: New USB device found, idVendor=2357, idProduct=f000
[ 100.596594] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[ 100.596605] usb 1-1: Product: TP-LINK HSPA+ Modem
[ 100.596614] usb 1-1: Manufacturer: TP-LINK, Incorporated
[ 100.596623] usb 1-1: SerialNumber: 863745010146666
[ 100.672186] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 100.672440] scsi4 : usb-storage 1-1:1.0
[ 100.672763] usbcore: registered new interface driver usb-storage
[ 101.676679] scsi 4:0:0:0: CD-ROM TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2
[ 101.677519] scsi 4:0:0:0: Attached scsi generic sg1 type 5
[ 101.679576] scsi 4:0:0:1: Direct-Access TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2
[ 101.680730] sd 4:0:0:1: Attached scsi generic sg2 type 0
[ 101.683354] sd 4:0:0:1: [sdb] Attached SCSI removable disk
[ 101.701142] sr0: scsi-1 drive
[ 101.701154] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 101.702969] sr 4:0:0:0: Attached scsi CD-ROM sr0
[ 138.383941] usb 1-1: USB disconnect, device number 3
[ 138.705152] usb 1-1: new high-speed USB device number 4 using ehci-pci
[ 138.822946] usb 1-1: New USB device found, idVendor=2357, idProduct=9000
[ 138.822962] usb 1-1: New USB device strings: Mfr=3, Product=2, SerialNumber=4
[ 138.822973] usb 1-1: Product: TP-LINK HSPA+ Modem
[ 138.822982] usb 1-1: Manufacturer: TP-LINK, Incorporated
[ 138.822991] usb 1-1: SerialNumber: 863745010146666
[ 138.874378] usb-storage 1-1:1.2: USB Mass Storage device detected
[ 138.875639] scsi5 : usb-storage 1-1:1.2
[ 138.905999] usbcore: registered new interface driver usbserial
[ 138.907342] usbcore: registered new interface driver usbserial_generic
[ 138.911395] usbserial: USB Serial support registered for generic
[ 138.920599] usbcore: registered new interface driver option
[ 138.920661] usbserial: USB Serial support registered for GSM modem (1-port)
[ 138.920945] option 1-1:1.0: GSM modem (1-port) converter detected
[ 138.923224] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[ 138.923390] option 1-1:1.1: GSM modem (1-port) converter detected
[ 138.923711] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[ 138.923877] option 1-1:1.3: GSM modem (1-port) converter detected
[ 138.925636] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
[ 139.880790] scsi 5:0:0:0: CD-ROM TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2
[ 139.887903] sr0: scsi-1 drive
[ 139.888732] sr 5:0:0:0: Attached scsi CD-ROM sr0
[ 139.889361] sr 5:0:0:0: Attached scsi generic sg1 type 5
[ 139.891561] scsi 5:0:0:1: Direct-Access TP-LINK MMC Storage 2.31 PQ: 0 ANSI: 2
[ 139.892751] sd 5:0:0:1: Attached scsi generic sg2 type 0
[ 139.894885] sd 5:0:0:1: [sdb] Attached SCSI removable disk
[ 675.710836] usbcore: registered new interface driver cdc_wdm
[ 675.723929] usbcore: registered new interface driver qmi_wwan
[ 856.575106] qmi_wwan 1-1:1.4: cdc-wdm0: USB WDM device
[ 856.576011] qmi_wwan 1-1:1.4 wwan0: register 'qmi_wwan' at usb-0000:00:1d.7-1, WWAN/QMI device, 0a:10:1f:2a:76:52
[ 1094.880148] NET: Registered protocol family 17
[ 1095.992428] sit: IPv6 over IPv4 tunneling driver



[24 Aug 2013, 12:50:05] [Debug] [/dev/cdc-wdm0] QMI Device supports 5 services:
[24 Aug 2013, 12:50:05] [Debug] [/dev/cdc-wdm0] ctl (1.3)
[24 Aug 2013, 12:50:05] [Debug] [/dev/cdc-wdm0] wds (1.5)
[24 Aug 2013, 12:50:05] [Debug] [/dev/cdc-wdm0] dms (1.2)
[24 Aug 2013, 12:50:05] [Debug] [/dev/cdc-wdm0] nas (1.0)
[24 Aug 2013, 12:50:05] [Debug] [/dev/cdc-wdm0] auth (1.0)
[24 Aug 2013, 12:50:05] [Debug] QMI Device at '/dev/cdc-wdm0' ready

ati
Manufacturer: QUALCOMM INCORPORATED
Model: 8
Revision: 8200C-FACPASZQ-30350 1 [Dec 15 2011 15:00:00]
IMEI: 863745010146666
+GCAP: +CGSM,+DS,+ES


OK
at&v
&C: 2; &D: 2; &E: 0; &F: 0; &S: 0; &W: 0; E: 1; L: 0; M: 0; Q: 0; V: 1;
X: 1; Z: 0; \Q: 3; \S: 0; \V: 0; O: 0; S0: 0; S2: 43; S3: 13; S4: 10;
S5: 8; S6: 2; S7: 50; S8: 2; S9: 6; S10: 14; S11: 95; S30: 0; S103: 1;
S104: 1; +FCLASS: 0; +ICF: 3,3; +IFC: 2,2; +IPR: 115200; +DR: 0;
+DS: 0,0,2048,6; +CMEE: 2; +WS46: 12; +CBST: 0,0,1;
+CRLP: (61,61,48,6,0),(61,61,48,6,1),(240,240,52,6,2);
+CV120: 1,1,1,0,0,0; +CHSN: 0,0,0,0; +CSSN: 0,0; +CREG: 0; +CGREG: 0;
+CFUN:; +CSCS: "IRA"; +CSTA: 129; +CR: 0; +CRC: 0; +CGDCONT: (1,"IP","","0.0.0.0",0,0)
; +CGDSCONT: ; +CGTFT: ; +CGEQREQ: ; +CGEQMIN: ; +CGQREQ: ; +CGQMIN: ;
+CGEREP: 0,0; +CGDATA: "PPP"; +CGCLASS: "A"; +CGSMS: 1; +CSMS: 0;
+CMGF: 0; +CSAS: 0; +CRES: 0; +CSCA: "+491710760000",145; +CSMP: ,,0,0;
+CSDH: 0; +CSCB: 0,"",""; +FDD: 0; +FAR: 0; +FCL: 0; +FIT: 0,0; +ES: ,,;
+ESA: 0,,,,0,0,255,; +CMOD: 0; +CVHU: 1; +CPIN: ��������,��������;
+CMEC: 0,0,0,0; +CIND: 0,3,1,0,0,0,1,0; +CMER: 0,0,0,0,0; +CGATT: 1;
+CGACT: 0; +CPBS: "SM"; +CPMS: "ME","ME","SM"; +CNMI: 0,0,0,0,0;
+CMMS: 0; +FTS: 0; +FRS: 0; +FTH: 3; +FRH: 3; +FTM: 96; +FRM: 96;
+CCUG: 0,0,0; +COPS: 0,0,""; +CUSD: 0; +CAOC: 1; +CCWA: 0; +CCLK: "";
+CPOL: 0,2,"",0,0,0; +CPLS: 0; +CTZR: 0; +CTZU: 0; +CLIP: 0; +COLP: 0;
+CDIP: 0; +CLIR: 0; +VTS: 0

OK
OK
at+cgdcont=?
+CGDCONT: (1-16),"IP",,,(0-2),(0-4)
+CGDCONT: (1-16),"PPP",,,(0-2),(0-4)
+CGDCONT: (1-16),"IPV6",,,(0-2),(0-4)

OK


Windows has modem at mi03 (linux /dev/ttyUSB2) and network at mi04 (qmi)


Regards,
Thomas


Offline Profile
PostPosted: Sat Aug 24, 2013 7:30 pm
Posts: 64Joined: Sun Jul 17, 2011 12:08 pm
thomasschaefer wrote:
bmork wrote:
Hello,



I expect we'll add it to option + qmi_wwan, but still need confirmation on the QMI interface



qmi works!





With the "dirty" skript and via modemmanager.

The only thing that makes me sad, the device supports only IPv4.

Via IPv6 it does not connect.

Thomas


Offline Profile
PostPosted: Sun Aug 25, 2013 2:07 pm
Posts: 142Location: Oslo, NorwayJoined: Thu Mar 15, 2012 10:47 pm
thomasschaefer wrote:
qmi works!


Thanks for confirming.

It's funny to see the number of devices now supported by the qmi_wwan driver, thinking of how I started out with the intention of supporting a single Huawei modem, possibly supporting a few more Huawei devices.

Your early testing of a number of devices has helped a lot. It would have been impossible writing a driver supporting more than a hundred different modems I have never even seen mylself without this kind of help.


Quote:
With the "dirty" skript and via modemmanager.

The only thing that makes me sad, the device supports only IPv4.

Via IPv6 it does not connect.


Could be just old firmware (the number of supported QMI services is low), or a "feature" disabled by the vendor. Too bad.


Offline Profile
PostPosted: Sat Dec 07, 2013 2:20 pm
Posts: 3Joined: Sat Dec 07, 2013 1:48 pm
Hi,
I have just bought this modem and tried to get it working with usb_modeswitch 2.0.1 on Opensuse 13.1. It works under WINXP
Autoswitch does not work.
This is the result of:
---------------------------------------------------
# usb_modeswitch -W -c /usr/share/usb_modeswitch/2357:f000

Read config file: /usr/share/usb_modeswitch/2357:f000

* usb_modeswitch: handle USB devices with multiple modes
* Version 2.0.1 (C) Josua Dietze 2013
* Based on libusb1/libusbx

! PLEASE REPORT NEW CONFIGURATIONS !

TargetVendor= 0x2357
TargetProduct= 0x9000
MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
NeedResponse=0

InquireDevice enabled (default)

No default vendor/product ID given. Abort
--------------------------------------------------------

Why is that?

I also tried:
--------------------------------------------------------------------------------------------------------------------------------------------------
# usb_modeswitch -v 2357 -p f000 -V 2357 -P 9000 -W -M '5553424312345678000000000000061b000000020000000000000000000000'
Take all parameters from the command line


* usb_modeswitch: handle USB devices with multiple modes
* Version 2.0.1 (C) Josua Dietze 2013
* Based on libusb1/libusbx

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x2357
DefaultProduct= 0xf000
TargetVendor= 0x2357
TargetProduct= 0x9000
MessageContent="5553424312345678000000000000061b000000020000000000000000000000"
NeedResponse=0

InquireDevice enabled (default)

Look for target devices ...
found USB ID 05e3:0608
found USB ID 2357:f000
vendor ID matched
found USB ID 046d:c50e
found USB ID 1d6b:0002
found USB ID 1d6b:0002
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 046d:c52b
found USB ID 05e3:0608
found USB ID 1b1f:c006
found USB ID 040b:2000
No devices in target mode or class found
Look for default devices ...
found USB ID 05e3:0608
found USB ID 2357:f000
vendor ID matched
product ID matched
found USB ID 046d:c50e
found USB ID 1d6b:0002
found USB ID 1d6b:0002
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 046d:c52b
found USB ID 05e3:0608
found USB ID 1b1f:c006
found USB ID 040b:2000
Found devices in default mode (1)
Access device 009 on bus 002
Get the current device configuration ...
OK, got current device configuration (1)
Use interface number 0
Use endpoints 0x01 (out) and 0x81 (in)
Inquire device details; driver will be detached ...
Looking for active driver ...
OK, driver detached

SCSI inquiry data (for identification)
-------------------------
Vendor String: TP-LINK
Model String: MMC Storage
Revision String: 2.31
-------------------------

USB description data (for identification)
-------------------------
Manufacturer: TP-LINK, Incorporated
Product: TP-LINK HSPA+ Modem
Serial No.: 863745010294144
-------------------------
Set up interface 0
Use endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Reset response endpoint 0x81
Reset message endpoint 0x01
Device is gone, skip any further commands
-> Run lsusb to note any changes. Bye!


------------------------------------------------------------------------------

I also tried with the -I switch, but the result is always the same:

# lsusb -v | grep 2357
Bus 002 Device 009: ID 2357:f000
idVendor 0x2357

Any idea?

Thanks


Carlo


Offline Profile
PostPosted: Sat Dec 07, 2013 2:47 pm
Posts: 621Location: Koh Samui, THJoined: Wed Jul 11, 2012 3:14 pm
Try:

usb_modeswitch -v 2357 -p f000 -V 2357 -P 9000 -W -I -n -M '5553424312345678000000000000061e000000000000000000000000000000' -2 '5553424312345678000000000000061b000000020000000000000000000000'

The first message is "allow media removal" and the second is "eject media"
You could also try the linux cd-rom eject cmd, eject /dev/sr0 (or maybe sr1 if you have another cd/dvd player in the system).

It looks like your modeswitch was succesful ("Device is gone, skip any further commands") but it has for some unknown reason reappeared..


Offline Profile
PostPosted: Sat Dec 07, 2013 3:32 pm
Posts: 3Joined: Sat Dec 07, 2013 1:48 pm
Hi,
this indeed did the trick!

--------------------------------------------------------------------
# usb_modeswitch -v 2357 -p f000 -V 2357 -P 9000 -W -I -n -M '5553424312345678000000000000061e000000000000000000000000000000' -2 '5553424312345678000000000000061b000000020000000000000000000000'
Take all parameters from the command line


* usb_modeswitch: handle USB devices with multiple modes
* Version 2.0.1 (C) Josua Dietze 2013
* Based on libusb1/libusbx

! PLEASE REPORT NEW CONFIGURATIONS !

DefaultVendor= 0x2357
DefaultProduct= 0xf000
TargetVendor= 0x2357
TargetProduct= 0x9000
MessageContent="5553424312345678000000000000061e000000000000000000000000000000"
MessageContent2="5553424312345678000000000000061b000000020000000000000000000000"
NeedResponse=1

InquireDevice disabled

Look for target devices ...
found USB ID 05e3:0608
found USB ID 2357:f000
vendor ID matched
found USB ID 046d:c50e
found USB ID 1d6b:0002
found USB ID 1d6b:0002
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 046d:c52b
found USB ID 05e3:0608
found USB ID 1b1f:c006
found USB ID 040b:2000
No devices in target mode or class found
Look for default devices ...
found USB ID 05e3:0608
found USB ID 2357:f000
vendor ID matched
product ID matched
found USB ID 046d:c50e
found USB ID 1d6b:0002
found USB ID 1d6b:0002
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 1d6b:0001
found USB ID 046d:c52b
found USB ID 05e3:0608
found USB ID 1b1f:c006
found USB ID 040b:2000
Found devices in default mode (1)
Access device 011 on bus 002
Get the current device configuration ...
OK, got current device configuration (1)
Use interface number 0
Use endpoints 0x01 (out) and 0x81 (in)

USB description data (for identification)
-------------------------
Manufacturer: TP-LINK, Incorporated
Product: TP-LINK HSPA+ Modem
Serial No.: 863745010294144
-------------------------
Looking for active driver ...
OK, driver detached
Set up interface 0
Use endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
OK, message successfully sent
Read the response to message 1 (CSW) ...
Response successfully read (13 bytes).
Trying to send message 2 to endpoint 0x01 ...
OK, message successfully sent
Read the response to message 2 (CSW) ...
Response successfully read (13 bytes).
Reset response endpoint 0x81
Could not reset endpoint (probably harmless): -4
Reset message endpoint 0x01
Could not reset endpoint (probably harmless): -4
Device is gone, skip any further commands
-> Run lsusb to note any changes. Bye!


and

# lsusb -v | grep 2357
Bus 002 Device 012: ID 2357:9000
idVendor 0x2357

-----------------------------------------------------------------------

Good!

In result three ttyUSB devices were created:

------------------------------------------------------
/dev/serial/by-id # l
totale 0
drwxr-xr-x 2 root root 120 7 dic 14.24 ./
drwxr-xr-x 4 root root 80 7 dic 12.12 ../
lrwxrwxrwx 1 root root 13 7 dic 12.12 usb-ELV_AG_eQ3_WS_300_PC_II-if00-port0 -> ../../ttyUSB0
lrwxrwxrwx 1 root root 13 7 dic 14.24 usb-TP-LINK__Incorporated_TP-LINK_HSPA+_Modem_863745010294144-if00-port0 -> ../../ttyUSB1
lrwxrwxrwx 1 root root 13 7 dic 14.24 usb-TP-LINK__Incorporated_TP-LINK_HSPA+_Modem_863745010294144-if01-port0 -> ../../ttyUSB2
lrwxrwxrwx 1 root root 13 7 dic 14.24 usb-TP-LINK__Incorporated_TP-LINK_HSPA+_Modem_863745010294144-if03-port0 -> ../../ttyUSB3

------------------------------------------------------

Let's see which one is working.
Do I need to stud' the qbi stuff?

Thanks

Carlo


Offline Profile
PostPosted: Sat Dec 07, 2013 4:04 pm
Posts: 621Location: Koh Samui, THJoined: Wed Jul 11, 2012 3:14 pm
The last one (ttyUSB3) is the serial ppp modem interface over which you can get a 25Mbps transfer rate.
QMI gives you much more but you will need a fairly recent kernel or a kernel to which updates of the qmi_wwan driver gets backported. The dongle was added to qmi_wwan around end of August this year, see discussion a few posts up.


Offline Profile
PostPosted: Sat Dec 07, 2013 4:26 pm
Posts: 3Joined: Sat Dec 07, 2013 1:48 pm
Thanks for the info.
I connected with sakis3g and I am writing this on the MA260 3g link. Amazing!

I will get into more depth with wvdial etc. before delving into this QMI stuff. Opensuse 13.1 kernel is 3.11.6 but I have no trouble configuring, compiling and installing the kernel from source.
Unfortunately I have access to this 3G stick on Sundays, the rest of the week it has to work at our office.
I hope the connection with this MA260/Wind will be more stable than the present Z360/Vodafone link that disconnects 1-3 times a day.

Thank you! You have been very very helpful!

Carlo


Offline Profile
PostPosted: Sat Jun 07, 2014 3:05 am
Posts: 1Joined: Sat Jun 07, 2014 2:58 am
For any Raspberry PI user out there on Raspbian, don't use the version 1.n.n of usb_modeswitch distributed with raspbian. Download the source (2.2.n as of writing this), apt-get install libusb-1.0-0-dev, make install (given you have tcl) and run the command as mentioned above:

usb_modeswitch -v 2357 -p f000 -V 2357 -P 9000 -W -I -n -M '5553424312345678000000000000061e000000000000000000000000000000' -2 '5553424312345678000000000000061b000000020000000000000000000000'


Offline Profile
PostPosted: Mon Jun 09, 2014 9:15 am
Site AdminPosts: 4834Joined: Sat Nov 03, 2007 12:30 am
Addendum:

If you have usb_modeswitch >= 2.1.0 you can just use the "StandardEject" parameter (-K on the command line). It includes exactly those two MessageContents that you posted.

Also, if you dont have (or don't want) "tcl" on your system, run "make static; make install" to create an 'embedded' usb_modeswitch wrapper with no further dependencies.


Offline Profile
PostPosted: Thu Sep 04, 2014 4:12 pm
Posts: 5Location: Puteaux, FRJoined: Thu Sep 04, 2014 3:49 pm
I'm using MA260 on a Debian jessie on a Raspberry Pi (up to date as of 20140903). I need the modem to be present before the PI starts up (no hot plug), and here are the issues I run into:
- usb_modeswitch does not seem to work (well, it does say "switching device..." but nothing happens)
- when called a couple minutes after boot, usb_modeswitch sometimes requires to be executed twice in order to work.
Any idea?


Offline Profile
PostPosted: Thu Sep 04, 2014 7:31 pm
Posts: 621Location: Koh Samui, THJoined: Wed Jul 11, 2012 3:14 pm
mig wrote:
I'm using MA260 on a Debian jessie on a Raspberry Pi (up to date as of 20140903). I need the modem to be present before the PI starts up (no hot plug), and here are the issues I run into:
- usb_modeswitch does not seem to work (well, it does say "switching device..." but nothing happens)
- when called a couple minutes after boot, usb_modeswitch sometimes requires to be executed twice in order to work.
Any idea?


Which driver do you use for the root hub, dwc2 or dwc_otg?
The old dwc_otg driver is rotten..


Offline Profile
PostPosted: Thu Sep 04, 2014 9:31 pm
Posts: 5Location: Puteaux, FRJoined: Thu Sep 04, 2014 3:49 pm
That's a jolly good question!

Unless dwc2 goes by the name "dwc_otg" in the logs, I'm using dwc_otg. How do I switch?


Offline Profile

Display posts from previous:  Sort by:

All times are UTC + 1 hour [ DST ]
Page 1 of 2
20 posts
Go to page 1, 2  Next
Users browsing this forum: Bing [Bot], Yahoo [Bot] and 3 guests
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