Sunday, February 23, 2014

libusb-1.0.18 release and the merge of libusb/libusbx project

Announcement on 26-Jan-2014:

This is the first libusb release after the merger of libusb and libusbx project.



Git repo:

Take note that Peter Stuge is opposed to the libusbx fork and the merger of libusb/libusbx. He is no longer the maintainer of libusb project. But he still wants to maintain the rival website.

libftdi1-1.1 released and Windows binaries

libftdi1-1.1 has been released on 06-Feb-2014

Main highlights
* Fix FT232H eeprom suspend pulldown setting (Davide Michelizza)
* Fix FT232H eeprom user area size (Davide Michelizza)
* Improved mingw build (Paul Fertser and Michel Zou)
* C++ wrapper: Get/set functions for USB timeouts (Jochen Sprickerhof)
* Partial support for FT230X (Nathael Pajani)
* New API function: ftdi_eeprom_set_strings() (Nathael Pajani)
* Prevent possible segfault in ftdi_eeprom_decode() (Nathael Pajani)
* Save device release number in eeprom (Jarkko Sonninen)
* Fix "self powered" eeprom flag (Jarkko Sonninen)
* Improved python wrapper (Michel Zou)
* Many buildsystem improvements (Michel Zou and Mike Frysinger)
* See the git history for more changes and fixes


GPG signature:

Full changelog:;a=blob;f=ChangeLog;hb=HEAD

I provided the Windows development kit download here. This time I have provided both the based 32bit development kit and MinGW-w64 based 32bit/64bit development kit. libusb-1.0.18 is used as the base for the libftdi1-1.1.

Monday, March 4, 2013

libftdi1-1.0 released and Windows binary download

libftdi1-1.0 has been released on 29-Jan-2013 after three years of active development.

Main highlights
* Ported to libusb 1.x
* Many EEProm handling improvements
* Library .so / pkgconfig files are called "libftdi1".
  So it can co-exist with libftdi 0.x
* ftdi_eeprom is part of the main distribution


I provided the MinGW32 download here.

Saturday, September 22, 2012

OpenOCD 0.6.0 release 32bit Windows binary using libusbx 1.0.13

OpenOCD 0.6.0
Release date: 7 September 2012
build date: 22 September 2012
build system: Windows XP SP3
compiler: GCC 4.7.0 (, 32bit only

Libraries used (32bit)

Build commands used:

LDFLAGS="-lusb-1.0" ../configure --enable-ftdi \
--enable-ft2232_libftdi --enable-presto_libftdi --enable-stlink \
--enable-arm-jtag-ew --enable-jlink --enable-rlink \
--enable-usbprog --enable-vsllink --enable-usb_blaster_libftdi \
--enable-remote-bitbang  --enable-vsllink --enable-ulink \
--enable-osbdm --enable-opendous \
--disable-shared --disable-werror

Drive installation.
1) ST-Link V2: use the driver from ST (winusb based)

2) libusb-1.0 drivers are required for:
- J-Link
- FTDI FTx232 adapters when using config files from
interface/ftdi/ subfolder (mpsse engine)

You can install libusb-1.0 drivers using Zadig software from
the libwdi project

You can choose to use winusb.sys, libusb0.sys, or libusbk.sys.
In general, they should perform the same but Winusb.sys
support in libusbx 1.0.13 may be more mature than libusb0.sys
and libusbk.sys.

For ST-Link V1 and J-Link, you may want to use the libusb-win32
filter driver since you can keep the existing vendor driver.

For FTx232 adapters (USB composite device), you can not use
the filter driver since libusbx 1.0.13 does not support
the filter driver for USB Composite device.

3) Other USB JTAG debuggers including FTDI FTx232 adapters when
not using config files from interface/ftdi/ subfolder (not using
the new mpsse engine)

Use Zadig to install libusb-win32 drivers (device driver or
filter driver)