On Fri, Apr 1, 2011 at 9:06 AM, Xiaofan Chen <[email protected]> wrote: > 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. >
Last time there is a report that libftdi-1.0 fixed similar issues. That is why I suggested to try libftdi-1.0. Reference: https://lists.berlios.de/pipermail/openocd-development/2010-June/015740.html Jtag debugger: Signalyzer H2 JTAG-adapter, should be FT2232H based Target: STM32 Arm Cotex M3 Issues: > Error: couldn't read enough bytes from FT2232 device (0 < 81) > Error: couldn't read from FT2232 > Error: couldn't read enough bytes from FT2232 device (79 < 81) > Error: couldn't read from FT2232 Fix: to use libftdi-1.0 under Linux https://lists.berlios.de/pipermail/openocd-development/2010-June/015814.html -- Xiaofan _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
