Re: Merely discovering FTDI devices using libftdi/libusb detaches them from ftdi_sio

[Joe Zbiciak <intvnut@xxxxxxxxx>]

I echo Eric's suggestion.

On my devices, I personally set the manufacturer string, description string, and serial number in EEPROM to something I can use to directly identify my device.  I don't generally change VID/PID, so I can use whatever stock FTDI driver is installed in the computer I plug into.

I don't remember offhand, but do you also need to set the CHANNEL_x_DRIVER fields in EEPROM to indicate you want bitbang rather than VCP, or does that only affect non-Linux platforms?

On Mon, Jun 4, 2018 at 12:48 PM, Eric Schott <eric@xxxxxxxxxxxxxx> wrote:

On Mon, 4 Jun 2018 18:22:38 +0000, Paul Ourada wrote:

I have a situation where I am using two FT4232H devices for serial communication via ftdi_sio, and a third device which I wish to use in bit bang mode to set up some control lines in the UARTS which are downstream from the first two FT4232Hs. These UARTS can be configured as RS232/422/485, etc. Of course, I do not wish to disturb the first two FT4232H devices wrt to their connection to ftdi_sio. However, I must discover all these devices to decide which one I should use with libftdi. But first, I check how things come up before attempting anything:

Have you considered changing the Vendor/Product ID, description, and/or
serial number fields stored in the EEPROM for the FT4232H which you
will be using for BitBang mode?  I use those capabilities with the
ftdi_usb_open_desc_index() method to always and easily select the
desired device irrespective of any other FTDI devices on the USB
bus.  Easy, foolproof.

--

libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@developer.intra2net.com   

--

We sell spatulas, and that's all!
http://spatula-city.org/~im14u2c/
http://spacepatrol.info/

---

libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx