Hi Johan,
2015-11-12 10:12 GMT+01:00 Johan Hovold <[email protected]>:
> On Wed, Nov 11, 2015 at 07:24:23PM +0100, Daniele Palmas wrote:
>> Hi Johan,
>>
>> 2015-11-06 12:24 GMT+01:00 Johan Hovold <[email protected]>:
>> > On Thu, Nov 05, 2015 at 01:57:43PM +0100, Jonas Jonsson wrote:
>> >> Some modems, such as the Telit UE910, are using an Infineon Flash Loader
>> >> utility. It has two interfaces, 2/2/0 (Abstract Modem) and 10/0/0 (CDC
>> >> Data). The latter can be used as a serial interface to upgrade the
>> >> firmware of the modem. However, that isn't possible when the cdc-acm
>> >> driver takes control of the device.
>> >
>> > Why can't you just use the tty device that the cdc-acm driver provides?
>>
>> I have the same problem reported by Jonas.
>>
>> Telit flashing procedure does not work with the cdc-acm driver.
>
> What exactly do you mean by "not work"? Does the driver fail to probe?
> Or is it just that your user-space tool expects the tty devices to be
> named ttyUSBn rather than ttyACMn (in which case the tool needs to be
> fixed)?
>
The driver cdc-acm is correctly loaded, since the device presents as
an acm device.
The user space tool has an argument for the device name: so it is not
a problem to use /dev/ttyACM or /dev/ttyUSB.
Having tested it several times with the ACM driver, I think it is not
an application issue.
>> Moreover, the device 0x058b/0x0041 is in itself a flashing device, so
>> /* Infineon Flashloader driver */ section of usb-serial-simple seems a
>> good place for it.
>>
>> Since the procedure is working properly with only bulk endpoints I suspect
>> that on the firmware side the definition of the device is not correct.
>
> What is the lsusb -v output for this device? Could you also provide the
> logs from when plugging it in?
>
It is an ACM device:
Bus 002 Device 007: ID 058b:0041 Infineon Technologies
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x058b Infineon Technologies
idProduct 0x0041
bcdDevice 0.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 67
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 0 None
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 255
CDC Header:
bcdCDC 1.10
CDC Call Management:
bmCapabilities 0x00
bDataInterface 1
CDC ACM:
bmCapabilities 0x02
line coding and serial state
CDC Union:
bMasterInterface 0
bSlaveInterface 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 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
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
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 2 Communications
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
> Thanks,
> Johan
Thanks,
Daniele
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
