Re: Debugging USB device

johann.d schrieb:

This is almost perfect, but my goal is to make a "standard" keypad to be
used as input device in any application, and not a vendor-specific device.
Now my problem is, as soon as I claim being to USB HID keypad (and of course
provide the appropriate descriptor, as found on the specification and in a
few samples), Windows stops my device and marks it as invalid (with error
code 10). Note that when I remove the "keyboard" part of the descriptor to
keep only the "LED" part (CAPS LOCK, NUM LOCK, SCROLL LOCK), the device is
marked OK, and any change in main keyboard status is correctly forwarded to
my board.

Delete the device in Device Manager while plugged before changing the descriptor. This makes Windows forget the driver binding. The next plug will be again a first plug.
Best post your HID descriptor to the USB IF forum
http://www.usb.org/phpbb/viewforum.php?f=1
Many decriptors have been dissected there already :-)
.

Relevant Pages

  • Re: LOR with filedesc structure and Giant
    ... We hold the file descriptor lock for the duration ... > because I need to grab a vnode lock to authorize polling the vnode using ... The easiest fix is to take a reference on the descriptors in the ...
    (freebsd-current)
  • Re: Fine grain select locking.
    ... Briefly, linux uses RCU to protect the list, which is ... other hand uses the actual file lock to protect the descriptor slot. ...
    (freebsd-arch)
  • Re: Fine grain select locking.
    ... other hand uses the actual file lock to protect the descriptor slot. ... If the ref count and flags were done with atomics the main consumer of FILE_LOCK would actually be the unix domain socket garbage collection code. ...
    (freebsd-arch)
  • Re: Multiple IMAP connections to same folder
    ... it has a shared lock open on the mailbox on the server. ... So it opens another descriptor append the message to the destination, keeping the first descriptor for the open mailbox. ...
    (comp.mail.imap)
  • Re: [TIP] BUG kmalloc-4096: Poison overwritten (ath5k_rx_skb_alloc)
    ... manipulate rxlink and descriptor address under rxbuf lock ... Grabbing an ath5k_buf then dropping the lock is racy because the ... referenced descriptor can be obtained in another thread and released ... hardware descriptors. ...
    (Linux-Kernel)