Huawei E3276 problem

[Fred Lefévère-Laoide]

Will try usbsnoop on windows xp in a week's time.
I'll let you know

Thanks for the help
Fred

Le 15/02/2013 13:12, Bjørn Mork a écrit :
> Fred Lefévère-Laoide <fred at lefevere-laoide.net> writes:
>
>> Bus 001 Device 011: ID 12d1:1401 Huawei Technologies Co., Ltd.
>> Device Descriptor:
>>    bLength                18
>>    bDescriptorType         1
>>    bcdUSB               2.00
>>    bDeviceClass            0 (Defined at Interface level)
>>    bDeviceSubClass         0
>>    bDeviceProtocol         0
>>    bMaxPacketSize0        64
>>    idVendor           0x12d1 Huawei Technologies Co., Ltd.
>>    idProduct          0x1401
>>    bcdDevice            1.00
>>    iManufacturer           3
>>    iProduct                2
>>    iSerial                 1
>>    bNumConfigurations      1
>>    Configuration Descriptor:
>>      bLength                 9
>>      bDescriptorType         2
>>      wTotalLength           55
>>      bNumInterfaces          2
>>      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         8 Mass Storage
>>        bInterfaceSubClass      6 SCSI
>>        bInterfaceProtocol     80 Bulk-Only
>>        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
>
> Strange.  This looks like the exact same config, except for the product
> ID.  Seems meaningless to implement two identical configurations like
> this.
>
>> option is loaded
>> But I still get nothing out of ttyUSB0
>>
>> Anything else I could do ?
> I think we have to find out how the Windows drivers use this device.  I
> have no idea.
>
> Just looking at the devices appearing in Windows will tell a lot, but we
> will likely need a usbsnoop to replicate the actions unless they are
> obvious in some other way. Only one vendor specific function with only 2
> endpoints makes me think that this device either has crashed and is
> waiting for a reset command, or is waiting for firmware.
>
>
>
> Bjørn