On Sat, 2013-08-03 at 08:12 +0400, Paul Fertser wrote: > Hi, > > On Fri, Aug 02, 2013 at 04:55:24PM -0700, Tim Wescott wrote: > > Without libusb-0.1-4 installed I do: > > > > ./configure --enable-ft2232_libftdi --enable-stlink > > Please do not use ft2232_libftdi at all, --enable-ftdi is the current > driver for those devices. And you can remove libusb-0.1 altogether, > just install libusb-1.0 as that's needed by both ftdi and ti_icdi (and > hence stlink since ti_icdi is unconditionally enabled when stlink is). > > The new reworked README and configure script are in the works, they > provide much better diagnostic. > > HTH
Configuring it with --enable-ftdi and --enable-stlink fixed the problem. Oddly enough, it would build OK with --enable-ft2232_libftdi, but not with that and --enable-stlink. I suppose one is just supposed to know, but it'd be nice if bells went off and some big "depreciated usage" messages were thrown around in cases like this. Perhaps even a "--enable-ft2232_libftdi is depreciated, do you want to continue? [N | y]" message, if it's not too hard. -- Tim Wescott www.wescottdesign.com Control & Communications systems, circuit & software design. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
