On Mon, Oct 4, 2010 at 7:27 AM, Xiaofan Chen <xiaofanc@xxxxxxxxx> wrote:
> Could you post the output of testlibusb-win.exe?
>
> The recommend way of using the filter is to use the Filter Wizard and install
> the device filter to each of your device.
>
Crap. Sorry for the confusion. libftdi-0.18 is using libusb-win32.
But libftdi-1.0 is using libusb-1.0 Windows backend. Now you have
to use WinUSB driver and not FTDI driver.
I wrote before.
> To be able to run this, you have to switch the stock FTDI driver to
> WinUSB driver. You can easily do that with Zadig form libwdi.
> http://www.libusb.org/wiki/windows_backend
> I just tried and it works for me. I install the device filter to interface
> A of the FT2232D based Jtag debugger.
No this is not useful. I actually installed the WinUSB driver
using Zadig to the interface A.
Once the libusb0.sys backend is integrated into libusb-1.0 Windows
backend, then you can use the filter driver.
--
Xiaofan
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
