libFTDI
A library to talk to FTDI chips:
FT232BM/245BM, FT2232C/D and FT232/245R using libusb, including the popular bitbang mode. The license is LGPL.
Updates
2008-04-16: Version 0.12 of libftdi released
- Fix build of documentation for "out of tree" builds
- Fix USB config descriptor in the eeprom by Juergen Beisert
- Ability to purge RX/TX buffers separately by Arnim Läuger
- Setting of event and error character by Arnim Läuger
- Poll modem status function by Arnim Läuger and Intra2net
- Updated documentation and created AUTHORS file
- Vala bindings helper functions by Even Nermerson
- Support for different EEPROM sizes by Andrew John Rogers
- Async write support. Linux only and no error handling
- Detection of R-type chips
- FTDIChip-ID read support by Peter Holik
Additional Software
ftdi_eeprom - A tool for creating and uploading the configuration eeprom for the FTDI chip. An example configuration file is included. EEPROM flashing for the 2232C/D and 232R/245R type chips is currently unsupported due the lack of proper documentation.
Dependencies
libconfuse - Library for parsing configuration files. Needed by ftdi_eeprom.
Download
We don't provide prebuild binary RPMs. You can easily build them yourself
via "rpmbuild --rebuild libftdi-*.src.rpm"
Dependencies
libusb - Library for talking to USB devices from user-space. Needed by libftdi.
Source TGZs Source RPMs Patches |
Older versions |
Documentation
Example code is included in the distribution file.
Here you can find the API documentation.
Note: When you get a -5 error "can't claim usb device" during ftdi_usb_open(), make sure the kernel ftdi_sio driver is unloaded.
You also find a patch for uisp here, an Atmel microcontroller flashing software, to program these via bitbang mode. The patch is not released yet and is only here as a bitbang mode example. Take a look at line 315+ of the patch for code using the bitbang mode.
.NET bindings for use with Mono can be found here: http://jelmer.vernstok.nl/oss/ftdi-cil/. Thanks to Jelmer Vernooij.
Contact
If you have any problems using the library, feel free to ask us via email at:

