On 02 Feb 2015, at 15:40, Paul Fertser <fercer...@gmail.com> wrote: > If he has a regular FTDI-based debug adapter (such as Olimex's or > Amontek's), then he doesn't need anything apart from libusb-1.0
Since I personally do not use these configuration, all I can do is check the documentation, and I'm quite confused about your statement. I checked the latest openocd.pdf manual (Feb 2), and at page 42 the olimex-jtag is listed below the ft2232_layout command. I also checked the Olimex documentation (https://www.olimex.com/Products/ARM/JTAG/_resources/ARM-USB-OCD_and_OCD_H_manual.pdf) and at page 13 it is clearly stated: "Please note that since OpenOCD 0.8.0 FTDI drivers are recommended! It was quite the opposite before 0.8.0 when LibUSB drivers were suggested as default. If you are going for FTDI driver support: ./bootstrap ./configure --enable-ftdi --enable-ft2232_ftd2xx make make install If you are going for the LibUSB driver support: ./bootstrap ./configure --enable-maintainer-mode --enable-ft2232_libftdi make sudo make install " On the other hand you say that adding any --enable-ftdi* is no longer necessary in the configure step for any devices except USB Blaster v1. Is there any document where I can find the actual configuration options required for various devices? Or, the other way around, what are the devices supported by the default configuration that you recommend? In my distribution I used exactly the configuration options used by Freddie Chopin, and it took some effort to properly build the FTDI and USB-W32 libraries. "${OPENOCD_GIT_FOLDER}/configure" \ --build="$(uname -m)-linux-gnu" \ --host="${CROSS_COMPILE_PREFIX}" \ --prefix="${OPENOCD_INSTALL_FOLDER}/openocd" \ --datarootdir="${OPENOCD_INSTALL_FOLDER}" \ --infodir="${OPENOCD_INSTALL_FOLDER}/openocd/info" \ --localedir="${OPENOCD_INSTALL_FOLDER}/openocd/locale" \ --mandir="${OPENOCD_INSTALL_FOLDER}/openocd/man" \ --docdir="${OPENOCD_INSTALL_FOLDER}/openocd/doc" \ --enable-aice \ --enable-amtjtagaccel \ --enable-armjtagew \ --enable-cmsis-dap \ --enable-ftdi \ --enable-gw16012 \ --enable-jlink \ --enable-jtag_vpi \ --enable-opendous \ --enable-openjtag_ftdi \ --enable-osbdm \ --enable-legacy-ft2232_libftdi \ --enable-parport \ --disable-parport-ppdev \ --enable-parport-giveio \ --enable-presto_libftdi \ --enable-remote-bitbang \ --enable-rlink \ --enable-stlink \ --enable-ti-icdi \ --enable-ulink \ --enable-usb-blaster-2 \ --enable-usb_blaster_libftdi \ --enable-usbprog \ --enable-vsllink Do you suggest that most of these should not have been included? Regards, Liviu ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
