Eric, thanks much for your replies -
The device shows up as /dev/ttyUSB0 and
occasionally as /dev/ttyUSB1, so there
doesn't seem to be a problem on that end.
What I *am* struggling with is how to
imitate the flow control the Windows
terminal emulator uses, and that's the
only type of flow control this device
understands.
In this so called manual flow control,
"RTS/DTR can be set or reset manually.
CTS/DSR lines are displayed but not used in
synchronization". All of the four flags
must be off, which to me looks just like
using a "No flow control" option. The
problem is that the device does NOT work
when flow control is off. So, I was wondering
which option(s) should be passed to the driver,
so it would behave as I just described?
Again, pls pardon the silly questions.
Cheers.
Quoting Eric Schott <eric@xxxxxxxxxxxxxx>:
On 09/20/2017 10:05 AM, Nickolai Dobrynin wrote:
Matwey,
lsusb -v shows
idVendor 0x0403 Future Technology Devices International, Ltd
whereas idProduct is
0x6001 FT232 Serial (UART) IC
Is this the information you were asking for?
Yes, this is the correct information. This device is supported by the
Linux ftdi_sio driver. Specifically, ftdi_sio.c contains
{ USB_DEVICE(FTDI_VID, FTDI_8U232AM_PID) },
Which are defined in ftdi_sio_ids.h as
#define FTDI_VID 0x0403 /* Vendor Id */
#define FTDI_8U232AM_PID 0x6001 /* Similar device to SIO above */
Try the following to debug:
* What are the system logs when plugging in the device?
* Also do a "ls -lt /dev | head" after plugging in the device
* Build a loop back cable and run a program like minicom
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
