Lib.rs

› Hardware support › libftd3xx
#ftdi #usb #ffi

sys libftd3xx-ffi

Rust FFI bindings to the FTDI d3xx drivers

by drebbe-intrepid

2 releases

0.0.2 May 30, 2023
0.0.1 May 24, 2023

#1619 in Hardware support


Used in 2 crates

Custom license

36MB
10K SLoC

Rust 3.5K SLoC // 0.0% comments C 3K SLoC // 0.1% comments C++ 3K SLoC // 0.1% comments

Contains (static library, 3.5MB) vendor/linux/armv6-hf/libftd3xx-static.a, (static library, 3MB) vendor/linux/armv7-hf/libftd3xx-static.a, (static library, 3MB) vendor/linux/armv8-hf/libftd3xx-static.a, (static library, 2.5MB) vendor/linux/x64/libftd3xx-static.a, (static library, 2.5MB) vendor/linux/x86/libftd3xx-static.a, (ELF lib, 1MB) vendor/linux/armv6-hf/libftd3xx.so and 8 more.

crates.io docs.rs CI

libftd3xx-ffi

Rust FFI bindings to the FTDI D3XX drivers. THIS REPOSITORY IS STILL EXPERIMENTAL AND NON-FUNCTIONAL.

This crate is just the C bindings. There is a separate crate, libftd3xx, which provides safe wrappers around the unsafe C bindings.

Usage

Simply add this crate as a dependency in your Cargo.toml. The static library is distributed in this crate with permission from FTDI. The default feature set will use dynamic linking.

[dependencies]
libftd3xx-ffi = "~0.0.2"

Bindgen

The default feature set will use pre-generated bindings. This is only available for Windows x86_64 and Linux x86_64 platforms.

The bindings can also be generated during compilation using the bindgen feature flag.

[dependencies]
libftd3xx-ffi = { version = "~0.0.2", features = ["bindgen"] }

Bindgen has additional dependencies that must be installed in order to compile successfully, see the bindgen requirements page for more details.

Static Linking

Static linking the FTD3XX library into this crate can be done by using the static feature flag.

[dependencies]
libftd3xx-ffi = { version = "~0.0.2", features = ["static"] }

Static linking may be preferred, however there may be license incompatibilities (static linking with GPL code). If in doubt, check the FTDI driver license terms.

Supported Targets

Tested Targets

TODO: UPDATE THIS THIS REPOSITORY IS STILL EXPERIMENTAL AND NON-FUNCTIONAL.

Untested Targets

These targets are provided, but they are untested. Use at your own risk.

  • aarch64-unknown-linux-gnu (dynamic + static)

  • aarch64-unknown-linux-musl (static)

  • i686-pc-windows-msvc (dynamic + static)

  • i686-unknown-linux-gnu (dynamic + static)

  • i686-unknown-linux-musl (static)

  • x86_64-pc-windows-msvc (dynamic + static)

  • x86_64-unknown-linux-gnu (dynamic + static)

  • x86_64-unknown-linux-musl (static)

  • arm-unknown-linux-gnueabihf (dynamic + static)

  • arm-unknown-linux-musleabihf (static)

  • armv7-unknown-linux-gnueabihf (dynamic + static)

  • armv7-unknown-linux-musleabihf (static)

  • x86_64-apple-darwin (dynamic)

  • aarch64-apple-darwin (dynamic)

References

Troubleshooting

Unknown Device on Linux

TODO: UPDATE THIS

Remove the VCP FTDI driver.

sudo rmmod ftdi_sio
sudo rmmod usbserial

See FTDI Drivers Installation Guide for Linux for more details.

License

FTDI provides the D3XX driver as a compiled library and a header file. These files can be found within the vendor directory.

The code within the vendor directory is licensed by FTDI. Please see the driver license terms page for their license.

All code outside of the vendor directory is MIT licensed.

Note: This crate is not affiliated with FTDI. You will need to contact the vendor for any support requests with the underlying library because it is closed source.

TODO: UPDATE THIS

Dependencies