On Wed, Jun 2, 2010 at 8:12 PM, Xiaofan Chen <xiaof...@gmail.com> wrote: > On Wed, Jun 2, 2010 at 5:26 PM, Martin Zenzes > <mzen...@informatik.uni-bremen.de> wrote: >> This seems to be a similar error to this one mentioned earlier: >> http://www.mail-archive.com/openocd-development@lists.berlios.de/msg12531.html >> but we got the same codebase, same OS (ubuntu 10.04) and tried >> even the same binaries build from the same git -- still the same strange >> error. >> >> So, if I understand this problem correctly this has something to do with >> our hardware-USB-subsystems, libftdi itself (both are using 0.17) or >> libusb itself (both are using 0.1)? >> > > You can probably ask in the libftdi mailinglist.
Oops, I see that you already asked but got no reply in the libftdi mailing list. Sorry I did not notice that. > > Just one data point: libusb-0.1 is considered as unmaintained and the > bug is considered as "won't fix". Debian/Ubuntu are still shipping > libusb-0.1 though. Many other distros change to use libusb-1.0+ > libusb-0.1-compat. > http://www.libusb.org/ > http://www.libusb.org/report/1 > > Unfortunately libftdi does not seem to be compatible with > libusb-0.1-compat. > > You can try libftdi-1.0 which is based on libusb-1.0. > -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
