On Tue, Mar 29, 2011 at 7:07 PM, Drasko DRASKOVIC <[email protected]> wrote: > Hi Mathias, > I tried with 2 completely different hosts, installing stuff from > scratch. Both running Debian. I frequently used dmesg, no problems > observed. USB cables and HW works fine in various set-ups, as I use > them on day-to day basis. > > Both hosts showed identical problems on build and deployment. I tried > both shared and static version - result is the same > FT_GetLatencyTimer() sucks and should not be used. I can only try > Amontec dongles, as I have no other. > > While 0.4.16 works correctly (except build problems I mentioned > before, observed by many people and documented on the web), it is > showing same Error: couldn't read enough bytes from FT2232 device (0 < > 5) as currrent libftdi. New D2XX corrects these problems, but > FT_GetLatencyTimer() has to be workarounded. > > Do you have by any chance some Amontec dongle to try with Linux > (Windows plays no important role in the life of developer) ? >
Just wondering why you prefer to use d2xx under Linux. I remember the tests done in the past shows that it does not have real advantages over libftdi or libftdi-1.0. Under Windows, yes. But under Linux, seems no. -- Xiaofan _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
