Laurent Gauch wrote: > actually I will recommend to still use D2XX drivers and build your > openocd for d2xx driver. Why : > > D2XX driver is actually still faster than libusb driver on Windows ...
Do you know why this is? Have you compared also using libusb-1.0, which uses WinUSB.sys? > D2XX driver is backward compatible with older D2XX ;-), not libusb > driver ... Hm, this would be a problem of libftdi I guess. Do you know if current products use older chips? > D2XX driver allows to have one only driver for JTAG channel and UART > channel ... (VCP D2XX), not the libusb This is maybe the most significant benefit. But if driver installation can be automated then I don't know if it matters anymore. > D2XX driver has a true compatibility trough OS (windows / linux / mac ) > ... This is of course also the case for libusb. That, and a straightforward API are IMO the most significant benefits of libusb. :) > D2XX driver is signed and Micrsoft WHQL certified for 32bits and > 64bits, not the libusb The libusb-win32 driver is signed as well, and I think at least a previous version has been WHQL certified. And for many systems libusb-1.0 can use WinUSB.sys from Microsoft themselves. > For the Amontec USB JTAG key dongle series please use the > > http://www.amontec.com/download/amontec-jtagkey-driver-d2xx-20091124.zip I understand that it is a little too early still, but hopefully libusb becomes a viable alternative for you soon. :) Kind regards //Peter _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
