V-USB Library broken in Windows 10? / Are there patches? / Alternative approaches for making a USB-HID device?

Go To Last Post
4 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

This is kind of annoying, but here's my situation:

 

I've been away from hardware hacking for a few years, and I've come back and it looks like V-USB is no longer updated -- the last version that I could find was "vusb-20121206".

 

And it still works, kind of. -- As long as you're using Windows 7. -- I never tried it in Windows 8, but it's definitely broken in Windows 10.

 

I prototyped a new device up, with the standard connections, and flashed it with the example code from "examples\hid-mouse\firmware" using the "make program" command, etc.

 

And when I plug the device into Windows 7 (x64) it does the correct behavior -- it shows up as a new mouse, and it slowly spins itself in a circle -- it works great.

 

But when I plug it into Windows 10 (x64) it fails to detect the device with the following error code "A request for the USB device descriptor failed.", and it failed hard -- it doesn't even know the VID/PID it says the Hardware ID is "USB\DEVICE_DESCRIPTOR_FAILURE".

 

I've read that Windows 10 changed the timing for how long a USB device can take to turn on before it will work (I've read that the timing has been lowered down to 20ms? -- I don't know what the old value was).

 

Here's my questions:

 

1.) Is there a more updated version of V-USB, or a Windows 10 patch/fix for it in the works?

 

2.) Is there a new library I should be using instead?

 

3.) Is there an alternative approach I should be considering? -- My goal is to produce a HID compliant gamepad device that does not require any special drivers in Windows or Linux (I've done this before, and not had trouble, but that was back in the Windows 7 days) -- I'm using ATMEGAs and ATTINY MCUs.

Last Edited: Sun. Mar 20, 2016 - 02:42 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

BrainSlug,

 

I was going to suggest that you ask over at

 

https://forums.obdev.at/viewtopi...

 

... but see that you already have. So how about waiting for Christian to comment... afterall he is the author.

 

Cheers,

 

Ross

(also a V-USB user but not with W10)

Ross McKenzie ValuSoft Melbourne Australia

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I know this thread is a bit old, but i found a solution for this Problem in my case.

 

multiple!!! USB-Hubs. In my case i needed three of this setups and some of them were working and some were not (all same devices).

 

My Setups: (Tablet = "Trekstor Tablet Wintron 7.0 with Windows 10 32bit")

first Tablet => OTG Cable => USB 3.0 Hub => HID-Device => WORKING

second Tablet => OTG Cable => USB 3.0 Hub => HID-Device => WORKING

third Tablet => OTG Cable => USB 3.0 Hub => HID-Device => NOT WORKING

 

Solution:

third Tablet => OTG Cable => USB 3.0 Hub => USB 2.0 Hub => USB 2.0 Hub => WORKING

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

This is usually because your clock is a little off, screwing up the timing. Some supported clock settings are closer to the spec than others, and some USB ports (particularly USB 3.0) are fussier than others.