>I've checked that now, and normal libusb0.sys seems to work fine, but
>you can never be sure, maybe after reset I will stop working or sth...

I could not install my ftd2xx device here the normal way. I must
use a composite version of the inf file.

Regards,

Michael

-----Ursprungliche Nachricht-----
Von: openocd-development-boun...@lists.berlios.de
[mailto:openocd-development-boun...@lists.berlios.de]im Auftrag von
Freddie Chopin
Gesendet: Sonntag, 21. Juni 2009 12:01
An: openocd-development
Betreff: Re: [Openocd-development] Will the next release 0.2.0 build on
FTD2XX support?


Xiaofan Chen pisze:
> Using MinGW/Msys may be complicated. But it is not that difficult to use
> Cygwin. Installaing Cygwin it can be an issue for average Windows users
> though.

So it's complicated anyway [;

> libusb-win32 device driver has the binary distribution. It is also very
easy
> to build the svn version under Cygwin or MinGW/Msys.

You need to know what to do with the created libraries - that's not a
Windows kind of knowledge.

> I believe you do not need the hacked libusb0.sys file. I think you just
> need to create the INF file for the whole device in stead of individual
> device. But  I need to get an FT2232x based JTAG tools to prove that.
> Or Gene Smith can test that.

I've checked that now, and normal libusb0.sys seems to work fine, but
you can never be sure, maybe after reset I will stop working or sth...

> 2) libftdi can be build under Cygwin pretty easily. Michael's SparkFun
> post mentioned that there would be errors. But with the latest
> libftdi 0.16 version, there are no errors any more.

The most recent libftdi cannot be build under MSYS - the build fails,
but the library is created.

4\/3!!


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

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

Reply via email to