Re: [Libusb-win32-devel] Problems using libusb after installing AVR32 Studio 2.2

[Xiaofan C. <xia...@gm...>]

On Fri, Oct 16, 2009 at 11:21 AM, Frank Tkalcevic
<fr...@fr...> wrote:
>> Are you using the libusb-win32 filter driver or the device driver? If
>> you are using the filter driver, uninstall it and then use device driver.
>> Then give it a try.
>
> What is the difference?  I installed libusb-win32-filter-bin-0.1.12.2.exe.  My
> device is a plain HID device.  My application works with any HID device.  Is
> the device driver install suitable?  I just need the libusb interface in my
> application to access the USB devices.

The filter driver is known to cause problems. Do you have other
application which access your device using the native HID API?
If yes, you can not use the libusb-win32 driver. If no, you can
use the libusb-win32 driver.

But it is far better to use native HID API and not libusb-win32
0.1 for HID device under Windows.

>>
>> By the way, even if libusb-win32 listed two DFU device, your
>> application should not be confused. Why does that happen?
>
> It's confused because it doesn't know which device to program.  It started
> with 1 HID device, 0 DFU devices.  Then the HID device was told to become a
> DFU device, and suddenly there is 0 HID devices and 2 DFU devices.  It claims
> to the user there is more than 1 device.

What if you just use the 1st device or just use the 2nd device?

>> What testlibusb-win.exe says before and after you have this
>> problem? If you can, get another PC to see whether you
>> still have this problem (without install avr32 studio).
>
> testlibusb-win.exe shows 2 devices.  The application works fine on a clean PC.
>
This is kind of strange.
What does "lsusb -vvv" say about your device under Linux?
Does it show two DFU device?

All in all, I suspect this has something to do with the filter
driver. Uninstall it and see if that helps.



-- 
Xiaofan http://mcuee.blogspot.com