Hi Giacinto,
> can you send the result of "lsusb" and "lsusb -t"?
The usbutils version of lsusb is somewhat better.
# lsusb
Bus 002 Device 001: ID 1d6b:0003
Bus 001 Device 002: ID 1546:1107
Bus 001 Device 001: ID 1d6b:0002
# lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=, Driver=cdc_acm, 480M
|__ Port 1: Dev 2, If 1, Class=, Driver=cdc_acm, 480M
|__ Port 1: Dev 2, If 2, Class=, Driver=cdc_acm, 480M
|__ Port 1: Dev 2, If 3, Class=, Driver=cdc_acm, 480M
|__ Port 1: Dev 2, If 4, Class=, Driver=cdc_acm, 480M
|__ Port 1: Dev 2, If 5, Class=, Driver=cdc_acm, 480M
|__ Port 1: Dev 2, If 6, Class=, Driver=cdc_acm, 480M
|__ Port 1: Dev 2, If 7, Class=, Driver=cdc_acm, 480M
|__ Port 1: Dev 2, If 8, Class=, Driver=cdc_acm, 480M
|__ Port 1: Dev 2, If 9, Class=, Driver=cdc_acm, 480M
|__ Port 1: Dev 2, If 10, Class=, Driver=cdc_acm, 480M
|__ Port 1: Dev 2, If 11, Class=, Driver=cdc_acm, 480M
And here is a relevant excerpt from lsusb -v.
Bus 001 Device 002: ID 1546:1107
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 239
bDeviceSubClass 2
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x1546
idProduct 0x1107
bcdDevice 17.29
iManufacturer 1 u-blox
iProduct 2 u-blox Cellular Module
iSerial 3 352848080392646
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 405
bNumInterfaces 12
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 0
bInterfaceCount 2
bFunctionClass 2
bFunctionSubClass 2
bFunctionProtocol 1
iFunction 4 CDC ACM
...
Cheers,
Frank
On Thu, Sep 13, 2018 at 10:21 AM Frank Vasquez <[email protected]> wrote:
> Hi Giacinto,
>
> > can you send the result of "lsusb" and "lsusb -t"?
>
> # lsusb -t
> Bus 001 Device 001: ID 1d6b:0002
> Bus 001 Device 002: ID 1546:1107
> Bus 002 Device 001: ID 1d6b:0003
>
> I am running BusyBox's stripped down version of lsusb that's why
> information is so lacking.
> I'll install usbutils on my device's Buildroot image and rerun the
> commands.
>
> Cheers,
> Frank
>
> On Thu, Sep 13, 2018 at 3:49 AM Giacinto Cifelli <[email protected]>
> wrote:
>
>> hi Frank,
>>
>> can you send the result of "lsusb" and "lsusb -t"?
>>
>> Giacinto
>>
>> On Thu, 13 Sep 2018, 00:41 Frank Vasquez, <[email protected]> wrote:
>>
>>> Greetings,
>>>
>>> I have an embedded device with a ublox TOBY-R200 on it. I want to use
>>> connman to manage any cellular connection on that modem since connman is
>>> already managing ethernet and wifi connectivity. oFono seems like the best
>>> option. I see that there is already a ublox plugin for oFono but I don't
>>> think the TOBY-R200 is supported. The cell module is soldered onto the
>>> board and appears as a USB device.
>>>
>>> [ 6.519190] usb 1-1: New USB device strings: Mfr=1, Product=2,
>>> SerialNumber=3
>>> [ 6.519197] usb 1-1: Product: u-blox Cellular Module
>>> [ 6.519204] usb 1-1: Manufacturer: u-blox
>>> [ 6.519211] usb 1-1: SerialNumber: 352848080392646
>>>
>>> I can send AT commands to the modem over /dev/ttyACM0.
>>>
>>> Cheers,
>>> Frank
>>> _______________________________________________
>>> ofono mailing list
>>> [email protected]
>>> https://lists.ofono.org/mailman/listinfo/ofono
>>>
>>
_______________________________________________
ofono mailing list
[email protected]
https://lists.ofono.org/mailman/listinfo/ofono
