Re: Help needed debugging Motorola Solutions TETRA PEI interface

[Max Schulze <max.schulze@xxxxxxxxx>]

Thanks Johan for taking a look.


Am 08.01.2018 um 17:30 schrieb Johan Hovold:
> Adding the device ids and a quirk to cdc_acm.c
>>> .driver_info = NO_UNION_NORMAL,
>> does only suppress the "Zero length" message.
> Do you then get a ttyACMn device? Or some other error?
Nothing more. No ttyACM device . Only the

[ 1745.845561] cdc_acm: probe of 1-1.4:1.1 failed with error -22
>
> Thus doesn't look like a CDC device. Can you post the full output of
> "lsusb -v"?
( As mentioned, I interfered the cdc-nature from the windows driver)
Bus 001 Device 007: ID 0cad:9011 Motorola CGISS
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0cad Motorola CGISS
  idProduct          0x9011
  bcdDevice           24.16
  iManufacturer           1 Motorola Solutions Inc.
  iProduct                2 Motorola Solutions TETRA PEI interface
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           55
    bNumInterfaces          2
    bConfigurationValue     1
    iConfiguration          3 Generic Serial config
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      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     0x0040  1x 64 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     0x0040  1x 64 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      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     0x0040  1x 64 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     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)
>
> Yeah, this is expected since you will not be able to do modem control
> when using the generic driver.
>
>
Strange enough - after said "sudo modprobe usbserial vendor=0x0cad
product=0x9011"
I can connect to the ttyUSB0 and ttyUSB1 with minicom instead of
miniterm.py (which indeed sems broken) - and it works! I get the AT
command set I expect.

So I guess for the time being leave it here - unsupported but somehow
working with the usbserial generic driver?

Max
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html