Hi Xiaofan, I tried also building libftdi-1.0 with libusb-1.0. Unfortunately, probelem : couldn't read enough bytes from FT2232 device (0 < 5) couldn't read from FT2232
persist, it is not corrected. The only lib that corrects this problem is libftd2xx-1.0.4, but in this case OpenOCD has to be patched not to call FT_GetLatencyTimer() like we discussed before. I had hard times, because the build system with CMake sucks. It is very difficult to build it if you want some other installation dir apart the default /usr/lib, which for me is RO. Here is discussion list : http://developer.intra2net.com/mailarchive/html/libftdi/2011/msg00114.html Luckily I found out that guys from Milkymist already did some effort : http://www.milkymist.org/wiki/index.php?title=Build_the_libftdi-1.0_and_new_ftdi_eeprom. Just that making softlinks did not work for me, because of some different config for lib tool. In that case it makes more sense to use one autogen.sh like this : #!/bin/sh # use glibtoolize if it is available (darwin) (glibtoolize --version) < /dev/null > /dev/null 2>&1 && LIBTOOLIZE=glibtoolize || LIBTOOLIZE=libtoolize $LIBTOOLIZE --copy --force || exit 1 aclocal || exit 1 autoheader || exit 1 autoconf || exit 1 automake -a -c || exit 1 ./configure --enable-maintainer-mode --enable-debug-log \ --enable-examples-build $* This will create ./configure program, and after you can use switches to configure like --prefix=<your_install_dir> Also, be sure to build libusb-1.0 before (builds in a similar way, with autogen.sh already present in the git repo). After installing libusb-1.0 set-up your env var like this : export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:<install_dir>/libusb-1.0/lib/pkgconfig in order for libftdi-1.0 to find libusb-1.0, because it's search path seems to be hard-coded in configure, and I did not find a way to pass it separately except via PKG_CONFIG_PATH variable. After that OpenOCD can be pointed to new libs and built without problems. Unfortunately, this do not scratch my itch. BR, Drasko On Wed, Mar 30, 2011 at 4:41 PM, Xiaofan Chen <[email protected]> wrote: > Here is the test binary for OpenOCD git. It is built with libusb-1.0 and > libftdi-1.0 support. I have configured the support for jlink and > ft2232_libftdi. > http://code.google.com/p/picusb/downloads/list > > openocd_30March2011_mingw32_libftdi1.zip > OpenOCD libftdi-1.0 test binary with only J-Link and ft2232-libftdi > support, 30March2011 > > libusb1win_K_snapshot_30March2011.zip > libusb-1.0 Windows backend K branch MinGW and mingw-w64 snapshots on > 30March2011 > > libftdi1_30March2011_mingw32_mingw64.zip > libftdi-1.0 mingw32 and mingw64 binary snapshots on 30March2011, > header/library/example only > > To use the binary, you have to switch the FTDI driver to WinUSB. You > can do that with Zadig (now the version is Zadig w131). > http://sourceforge.net/projects/libwdi/ > > -- > Xiaofan > _______________________________________________ > Openocd-development mailing list > [email protected] > https://lists.berlios.de/mailman/listinfo/openocd-development > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
