Re: [Openocd-development] ftd2xx -> libftdi

[Ronald Vanschoren]

-------- Original Message  -------- Subject: [Openocd-development] ftd2xx -> libftdi From: Xiaofan Chen <xiaof...@gmail.com> To: open...@duaneellis.com Cc: openocd-development <openocd-development@lists.berlios.de> Date: Fri Jun 26 2009 17:27:36 GMT+0200 (Romance Standard Time) On Fri, Jun 26, 2009 at 11:15 PM, Duane Ellis<open...@duaneellis.com> wrote: Zach Welch wrote: Only libusb+libftdi serves our long-term interests. Wrong. "libusb" is a *blocking* issue that we cannot control, fix, nor whatever. LIBUSB is not supported by *newer* windows platforms. Unless and until it is supported it becomes a dead end solution, period, end of story. I believe the "WinUSB" solution is a solution, that for some reason keeps being left off your list. http://msdn.microsoft.com/en-us/library/aa476426.aspx I agree with you that WinUSB is a solution for OpenOCD. It is actually a solution for libusb-win32 as well. ;-) On the other hand, libusb-win32+libftdi may still need to be the solution for Windows 2000 users (and maybe 98SE and Win ME). I have only taken a quick look at WinUSB, but if I understand the concept correctly there might be an issue. I'm not sure of what I'm saying here so shout if it's complete nonsense. To work with WinUSB, your USB device has to indicate that WinUsb.sys is its driver. In the case of e.g. a Luminary eval board this can probably be done by making the correct .inf file or whatever (again, I'm not an expert in this). The problem I see is that all other tools using FTD2xx (like the Luminary Flash tool (I suppose)) will no longer be able to connect to the board as it is not "linked" to the FTD2xx driver. Does this make sense? And does this apply to libusb+libftdi as well? My apologies if you wasted 2 minutes of your life and want them back ;-) gr. Ronald

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development