Author Message

<  Device Information  ~  Huawei K3806

PostPosted: Wed Jan 23, 2013 6:02 am Reply with quote
Posts: 1106Location: Koh Samui, THJoined: Wed Jul 11, 2012 3:14 pm
This is a device which looks like a serial modem device but it is not.

Info from Huawei Linux Driver package:

SUBSYSTEMS=="usb", ATTRS{modalias}=="usb:v12D1p14AE*", KERNEL=="ttyUSB*", ATTRS{bInterfaceNumber}=="00", ATTRS{bInterfaceProtocol}=="ff", NAME="ttyUSB_utps_pcui"

SUBSYSTEMS=="usb", ATTRS{modalias}=="usb:v12D1p14AE*", KERNEL=="ttyUSB*", ATTRS{bInterfaceNumber}=="02", ATTRS{bInterfaceProtocol}=="ff", NAME="ttyUSB_utps_modem"

Info from Windows .inf file:


%VDFPcuiDesc% = DevInstall, USBCDCACM\VID_12D1&PID_14AE&MI_00
%VDFECMDesc% = ew_jucdcecm.ndi, USBCDCECM\VID_12D1&PID_14AE&MI_01
%VDFModemDesc% = DevInstall, USBCDCACM\VID_12D1&PID_14AE&MI_02

and finally a cat of the devices file which I found on the net:

T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 5 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=14ae Rev=01.02
S: Manufacturer=Vodafone Group (Huawei)
S: Product=Vodafone Mobile Broadband (Huawei)
S: SerialNumber=0
C: #Ifs= 4 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 1 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=ff Driver=option
I: If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage


bjorn?


Offline Profile
PostPosted: Wed Jan 23, 2013 10:17 pm Reply with quote
Posts: 165Location: Oslo, NorwayJoined: Thu Mar 15, 2012 10:47 pm
LOM wrote:
This is a device which looks like a serial modem device but it is not.

Info from Huawei Linux Driver package:

SUBSYSTEMS=="usb", ATTRS{modalias}=="usb:v12D1p14AE*", KERNEL=="ttyUSB*", ATTRS{bInterfaceNumber}=="00", ATTRS{bInterfaceProtocol}=="ff", NAME="ttyUSB_utps_pcui"

SUBSYSTEMS=="usb", ATTRS{modalias}=="usb:v12D1p14AE*", KERNEL=="ttyUSB*", ATTRS{bInterfaceNumber}=="02", ATTRS{bInterfaceProtocol}=="ff", NAME="ttyUSB_utps_modem"

Info from Windows .inf file:


%VDFPcuiDesc% = DevInstall, USBCDCACM\VID_12D1&PID_14AE&MI_00
%VDFECMDesc% = ew_jucdcecm.ndi, USBCDCECM\VID_12D1&PID_14AE&MI_01
%VDFModemDesc% = DevInstall, USBCDCACM\VID_12D1&PID_14AE&MI_02

and finally a cat of the devices file which I found on the net:

T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 5 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=12d1 ProdID=14ae Rev=01.02
S: Manufacturer=Vodafone Group (Huawei)
S: Product=Vodafone Mobile Broadband (Huawei)
S: SerialNumber=0
C: #Ifs= 4 Cfg#= 1 Atr=80 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 1 Alt= 0 #EPs= 1 Cls=02(commc) Sub=06 Prot=ff Driver=option
I: If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=option
I: If#= 3 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage


bjorn?


The devices listing seems consistent with the .inf. Both interface #0 and interface#2 should be serial ports, most likely supporting AT commands. But not necessarily PPP.

Interface #1 is supposed to be a CDC ECM interface and supported by the cdc_ether driver. It has this entry which should match:

Code:
 {
        /* Various Huawei modems with a network port like the UMG1831 */
        .match_flags    =   USB_DEVICE_ID_MATCH_VENDOR
                 | USB_DEVICE_ID_MATCH_INT_INFO,
        .idVendor               = HUAWEI_VENDOR_ID,
        .bInterfaceClass        = USB_CLASS_COMM,
        .bInterfaceSubClass     = USB_CDC_SUBCLASS_ETHERNET,
        .bInterfaceProtocol     = 255,
        .driver_info = (unsigned long)&wwan_info,
},


But a single endpoint is obviously not going to do. This driver needs 3 (interrupt + bulk in/out), preferably distributed over 2 interfaces (control + data). And I don't see any possible data interface here. The two data endpoints are probably hidden in an interface #1 altsetting we don't see. Which is one of the reasons I really dislike the usb-devices script.... It does not show the same information the old /proc/bus/usb/devices file used to show. Inactive configurations and altsettings are hidden. This makes it somewhat useless.

Could you get a lsusb -v listing for this device? That would also show the CDC functional descriptors, which we need to know to be able to support it.

I do not think the cdc_ether driver can support this right now. It currently requires a separate data interface. But I assume we can fix that in much the same way we recently fixed cdc_ncm to work with another Huawei Jungo firmware variant.


Bjørn


Offline Profile
PostPosted: Thu Jan 24, 2013 1:37 pm Reply with quote
Posts: 1106Location: Koh Samui, THJoined: Wed Jul 11, 2012 3:14 pm
bmork wrote:
Could you get a lsusb -v listing for this device? That would also show the CDC functional descriptors, which we need to know to be able to support it.

I do not think the cdc_ether driver can support this right now. It currently requires a separate data interface. But I assume we can fix that in much the same way we recently fixed cdc_ncm to work with another Huawei Jungo firmware variant.

Bjørn


I've been looking all over the net but that usb-devices output is all I can find.
The problem with K3806 is mentioned in a couple of forums but no user has provided much of useful info in order to
solve his problem :(
Someone googling for K3806 problem may find this thread and supply the needed info.


Offline Profile

Display posts from previous:  Sort by:

All times are UTC + 1 hour [ DST ]
Page 1 of 1
3 posts
Users browsing this forum: No registered users 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