Hi Xiaofan, many thanks for this hint. The 1.0.0.0 was not working here with OpenOCD. The libusb build based on 0.1.12.1 is working now.
But this is the same version which the user can download from sourcefore. Perhaps someone should create a 0.1.12.2 for using with OpenOCD? Regards, Michael -----Ursprüngliche Nachricht----- Von: Xiaofan Chen [mailto:xiaof...@gmail.com] Gesendet: Sonntag, 21. Juni 2009 16:59 An: Michael Fischer Cc: Freddie Chopin; openocd-development Betreff: Re: [Openocd-development] Will the next release 0.2.0 build on FTD2XX support? On Sun, Jun 21, 2009 at 7:08 PM, Michael Fischer<fische...@t-online.de> wrote: > Hello List, > > an hacked version of libusb0.sys is not needed anymore. > With the hacked version it is still not allowed to distribute > it because how should the user create the hacked version? > > I could build a libusb driver based on SVN trunk version 161, > under MinGW. The drivers version is 1.0.0.0. > This driver will support the setting of composite devices > in the inf file. > > Unfortunately I could only build the x32 verison and no x64. > > Btw, this will not solve the need of the FTD2XX, but now we > can distribute a libusb composite version. > Oops, I forgot to mention that libusb-win32 1.0 SVN branch (named libusb1) is not working yet. So your version 1.0.0.0 is not ready yet. You should build the 0.1 branch (named libusb). There are two branches here: http://libusb-win32.svn.sourceforge.net/viewvc/libusb-win32/trunk/ The libusb branch is the stable branch and should work. DLL version: 0.1.12.1 Driver version: 0.1.12.1 The libusb1 branch is the development branch and has WinUSB and HID backend along with the libusb-win32 device driver backend. But it is not working as far as I know. DLL version: 1.0.0.0 Driver version: -1.-1.-1.-1 -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
