> > I can't speak for the "H" part, but the "FT2232D" part works just fine
> > under Win32 with MSVC. I also built the same libftdi source for Linux
> > with gcc. I use direct/UART mode ("direct" meaning *not* VCP), as well as
> > MPSSE/SPI mode. My team will likely move to the "H" part in a few
> > months, so I'll know more then.
Ok, nice to know that it works.
> > One caveat is that Device Manager likes
> > to give the device to d2xx, and it takes some coaxing to make it take
> > libusb-win32 (I sometimes have to "update driver" a second time after the
> > first unplug/replug...but not always).
Do you use the default vendor-/product-id? Maybe it would help if you use a
different product id that the d2xx-driver doesn't know about.
You can ask FTDIchip, they will usually provide you with a unique product id
out of their range for free.
> libusb-win32 actually supports async mode, so does libusb-1.0.
> Right now the async mode of libftdi seems to directly manipulate
> sysfs and it is only for Linux.
The async-mode of libftdi is an evil hack which I wrote when libusb-1.0 wasn't
available yet. It would be nice to replace it with something based upon
libusb-1.0. I currently don't have the time to do that, but if someone wants
to work on it we could certainly provide some help and feedback.
Actually Jie Zhang wrote that he is working on it some days ago, you can
search for his post the mailinglist-archive.
Kind regards,
Gerd
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
