libftdi Archives

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

From: Uwe Bonnes <bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Tue, 5 Jun 2018 12:28:15 +0200
>>>>> "Joe" == Joe Zbiciak <intvnut@xxxxxxxxx> writes:

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

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

Look at DS_FT2232H datasheet "4.13.1 Do I need an EEPROM?"

Bye

-- 
Uwe Bonnes                bon@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 1623569 ------- Fax. 06151 1623305 ---------

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

Current Thread