Re: [Libusb-devel] Can't Send Control Messages to usb device in Windows

[Jason K. <jas...@gm...>]

I can't seem to cross compile xusb, here is what I'm getting:

  CC     xusb.o
  CCLD   xusb.exe
libtool: link: Could not determine host path corresponding to
libtool: link:   '/Users/snookie/Projects/winusb/libusb/.libs'
libtool: link: Continuing, but uninstalled executables may not work.
libtool: link: Could not determine host path corresponding to
libtool: link:   '/usr/local/i386-mingw32-4.3.0/i386-mingw32/lib'
libtool: link: Continuing, but uninstalled executables may not work.
libtool: link: Could not determine host path corresponding to
libtool: link:   '/Users/snookie/Projects/winusb/libusb/.libs'
libtool: link: Continuing, but uninstalled executables may not work.
libtool: link: Could not determine host path corresponding to
libtool: link:   '/usr/local/i386-mingw32-4.3.0/i386-mingw32/lib'
libtool: link: Continuing, but uninstalled executables may not work.
libtool: link: Could not determine host path corresponding to
libtool: link:   '/usr/local/i386-mingw32-4.3.0/i386-mingw32/bin'
libtool: link: Continuing, but uninstalled executables may not work.
  CC     lsusb.o
  CCLD   lsusb.exe

Couldn't figure this one out.

Best,
Jason

On Apr 21, 2010, at 4:52 PM, Xiaofan Chen wrote:

> On Thu, Apr 22, 2010 at 6:47 AM, Jason Kotzin <jas...@gm...> wrote:
> 
>> As a quick test, I wanted to still make sure I'm not doing something
>> obviously wrong.  I changed my device not to be a composite device,
>> but I took out the Keyboard and left it a standard HID class device.
> 
>> In theory, I should now be able to run the same complied program
>> and it should work, windows is no longer is locking the keyboard as
>> this is just a standard HID device.
> 
> Yes it should work.
> 
>> Here is what I did:
>> 
>> I ensured that my device is using the windows default dll driver for my usb device
>> Copied the precompiled libusb-1.0.dll into C:/Windows/System/
> 
> Should be C:/Windows/System32
> 
>> Enabled Debugging
>> Opened the correct interface
>> 
>> But the results were exactly the same.
>> 
>> On my Mac, here is the results of calling ./test peek 0
>> (returns the contents of my ucontroller eeprom at memory location 0)
>> 
> 
> If your device is a real HID device, you will need to use the codeless
> kext to prevent the kernel HID driver from using it so that your libusb
> program can work. Is that the case here?
> 
> I second Pete's suggestion to run xusb to test your device.
> (under Windows and Mac OS X).
> 
> -- 
> Xiaofan http://mcuee.blogspot.com