On Sun, Mar 2, 2014 at 11:13 PM, Andreas Fritiofson <andreas.fritiof...@gmail.com> wrote: > > On Sun, Mar 2, 2014 at 1:12 PM, Paul Fertser <fercer...@gmail.com> wrote: >> >> >> Regarding your patches, do I understand it right that you want to use >> proprietary library because you do not want to install WinUSB driver >> for your device because some proprietary "crossworks" can't use that >> adapter with WinUSB drivers? And so you either have to use the >> libftdi version of OpenOCD's ft2322 adapter driver or that d2xx >> version of the same old deprecated ft2232 driver, and you can't switch >> to "ftdi" driver at all? >> >> If this is really the case, wouldn't it be better and cleaner in the >> long run to employ libwdi and write a custom app that would >> temporarily switch WinUSB to the proprietary driver before starting >> crossworks and switch it back to WinUSB after it's finished?
I think that is probably the better way to go. Zadig is good to switch the driver to WinUSB but it does not address the step to go back to the FTDI driver. libwdi has simple example which should work for the custom app, just plug the vendor driver package. Please look at the wdi-simple example here. Pete even includes the driver install script for Inno Setup and NSIS. https://github.com/pbatard/libwdi/tree/master/examples > > I haven't tried this myself or even heard someone suggest it before, but I > think you could actually make use of another misfeature of Windows. I don't > know why or how but sometimes I have to reinstall the drivers for a device > when it's plugged into another port. I guess this depends on the driver inf > file because it only happens for some devices (typically my own virtual > com-port devices, which is highly annoying). Usually that means your device does not have a unique serial number. If the device has a unique serial number, Windows will not need to re-install the driver for your device. > So with the right setup, it should be possible to have WinUSB installed for > the driver when it's plugged into one port, and the proprietary FTDI drivers > installed for the same device on another port. Switching application thus > only requires switching USB-ports for the dongle. Most of the FTDI based dongles will have a unique serial number and this will not work. > Considering the cost of FTDI adapters, I even think it's fair to require > people wanting to use proprietary tools to simply buy another one for that > purpose. I really don't think we should maintain the ft2232 driver any > longer. It *wants* to die. I support your view as well. On the other hand, apparently there are people who still want to use the FTDI driver for other utility. The other possibility is to help libusb project to improve the support of libusb-win32 filter driver in the libusb Windows backend. Right now it does not work for USB Composite device like FT2232x. -- Xiaofan ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
