On Thu, Mar 31, 2011 at 10:59 PM, Drasko DRASKOVIC <[email protected]> wrote: > 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.
Thanks for the report. Sorry to hear that it does not work. In this case, I think it is good to see what is the difference between the data sent/received and then probably OpenOCD with libftdi / libftdi-1.0 issues cab be sorted out. It can be an issue with OpenOCD, it may be an issue with libftdi and libftdi-1.0 as well. > 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 Yes it is not that easy to use Cmake. However I do not like auto-tools either. These build systems all suck in one way or another. We tried a lot to get libftdi-1.0 to be built with MinGW-w64 with libusb-1.0 Windows backend last time. Take note this is a long thread. http://libusb.6.n5.nabble.com/Win-libusb-1-0-snapshots-no-longer-work-with-cross-compiling-of-libftdi-1-0-tp2262878p2473199.html But in general, you can try "cmake -i" and then it is not that difficult. Then you can also manually edit the CMakefileCache.txt. > 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. You need to remember that libftdi-1.0 will use CMake and the auto-tools script may be removed in the future. So you may have to deal with CMake anyway. > After that OpenOCD can be pointed to new libs and built without > problems. Unfortunately, this do not scratch my itch. > -- Xiaofan _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
