This is the part where libusb is configured: cd libusb && ./autogen.sh --prefix=/tmp/test && make install && cd ..
Nor can I find any other line that seems to activate verbosity. How do I rebuild libusb without verbose debugging? On Tue, 2010-08-03 at 18:50 +0200, Peter Stuge wrote: > Olof Tångrot wrote: > > Okay, I build it, run it and here is the result. > > Hehe. I think it was too long for the list to like it. > > > > In the end it still seems like it fails. > > Yep. There are three occurences of: > > Error: couldn't read enough bytes from FT2232 device (0 < 81) > Error: couldn't read from FT2232 > > After the second there's: > > Command handler execution failed > in procedure 'transport' > Command handler execution failed > in procedure 'init' > > Hm. You could try rebuilding libusb without the verbose debugging, to > eliminate any timing issues that might be caused by the many printed > lines. > > > > I hope it is possible to conclude from the USB transactions if the > > commands to the JTAG engine on the FT2232H or whatever is correct. > > I don't think there's much of a JTAG engine on the FT2232 - I think > it's just bitbanged, which would also explain the massive debug > output. > > > //Peter > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
