|
From: Tim R. <ti...@pr...> - 2024-09-20 17:55:49
|
Aaron Gomez | Rother Industries & Technology wrote: > > I am currently using the FTDI device but only for testing. Finally I > will use a software library created by me where I will use libusb and > I will use it with other devices that are multi-class (standard). For > this reason I wish obtain this via libusb. > > I know I could use the FTDI drivers but I want to get a general one > for multi-class devices. > I don't know what you mean by "multi-class (standard)". The FTDI232R has its device class and subclass embedded in its device descriptor. It has exactly one class. > How to know the ttyUSBx/ttyACMx/... name with libusb? I could see that > when I connect the device in the path dev/serial/by-id/ a file is > created where its name is the components of string descriptor and it > is linked with the ttyUSBx/ttyACMx/... (path: /dev/tty...) file which > I need to open this file descriptor and start the communication. > Well, hang on. If you have a ttyXXX device, then that means you already have a driver that is converting the USB device into a serial device. You cannot use libusb to talk to a /dev/ttyXXX device. /dev/ttyXXX speaks serial protocol, not USB protocol. -- Tim Roberts,ti...@pr... Providenza & Boekelheide, Inc. |