libftdi Archives

Subject: Re: How to open the second channel on a FT2232H device?

From: Xiaofan Chen <xiaofanc@xxxxxxxxx>
To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
Date: Mon, 30 Apr 2012 20:30:25 +0800
On Mon, Apr 30, 2012 at 7:48 PM, Thomas Heller <theller@xxxxxxxxxx> wrote:
> I'm having problems opening the second channel on a FT2232H device
> (Windows7 64 bit, using Xiafan Chen's 0.20 binary snapshot build).
>
> I used the serial_test.exe program:
>
> A) serial_text.exe -v 0x0403 -p 0x6010 -i 1 > null
> B) serial_text.exe -v 0x0403 -p 0x6010 -i 2 > null
>
> and tried different scenarios.
>
> 1. Using the FTDI driver, and installed libusb-win32 filter driver for
> the USB-Compound device "vid:0403 pid6010 rev:0700" - both A) and B) work.

This is good.
BTW, it is not a USB Compound device, but rather a USB composite
device.

> 2. Using the FTDI driver, installed libusb-win32 filter drivers for
> "vid:0403 pid:6010 rev:0700 mi:00" and "vid:0403 pid:6010 rev:0700 mi:01"
> USB Serial Converters.  A) works, B) prints:
>    unable to open ftdi device: -5 (unable to claim usb device. Make sure the
> default FTDI driver is not in use)

A bit strange.

> 3. Using libusb-win32 drivers only, for both "USB Serial Converter
> (Interface 0)" and "USB Serial Converter (Interface 1)".
> A) works, B) doesn't work.

Again a bit strange.

> Am I doing something wrong?  Must I install a libusb-win32 driver for
> the compound device (if so - how)?

At least one works, so that is one option. You can indeed use
libusb-win32 device driver for the whole USB composite device,
replacing the default Microsoft USB Composite Parent Driver
and the FTDI driver. You just need to modify the inf file
generated for 3 and remove the reference to the interface
in the inf file (&MI_00 or &MI_01).

-- 
Xiaofan

--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx

Current Thread