Objective Development Forums

This works on devices which have Read-While-Write capability (probably all devices with a boot loader section). It does NOT work on the ATTiny85.

When you switch your HID between mouse, keyboard and other types, ALWAYS switch the USB PID as well. Windows caches the association of PID with a driver forever. Regarding the host side software: Look at the hid-data example, it uses the functions from libs-host. The Windows version uses native Wind...

Whey you receive the data in (e.g.) usbFunctionWrite(), the last USB transfer is not complete. The host wants to read a zero byte block as a kind of ACK. The host polls for this reply while you are in usbFunctionWrite(). If you block the CPU during this time, the host won't receive a NAK to its poll...

You can also remove the association somewhere in the device manager. I'd recommend separate experimental PIDs, though, unless you really know where to remove the driver association.

Sorry, have not checked your code... I think it should work, but only a test can give you a definitive answer.

There's no problem from a legal point of view. We might even set a link to your shop, if the board is A Good Thing.

Does Windows refer to the device by name? If it knows the device name, there has been some basic USB communication going on. If not, it's very likely that something very basic is broken.

You MUST NOT use the same VID/PID pair for two devices with different low level drivers. Windows caches the association of VID/PID and driver FOREVER. Simply use a new pair (see USB-IDs-for-free.txt in the latest driver).

Since the Tiny85 does not have read-while-write capability, the CPU is halted during programming. This means that not even interrupts (such as the USB interrupt) can execute. The host won't receive any responses to USB requests during this time. You might get around the problem if you ensure that al...

If you want to use HID for data, not as an external keyboard, see the hid-data example which ships with the driver.

The report-ID must also be the first byte of the report data. The reports sizes all increase by one byte.

HIDKeys is not intended for real keyboards, it's an example only. The code is kept simple, no handling of key bounces etc.

See http://www.obdev.at/products/vusb/prjhid.html for keyboard implementations which have been made for real-life.

HIDKeys is only a simple example, it does not aim at BIOS compatibility. See the document cited by grendel to see what you need to change.

Where does it say that you need the DDK? MinGW comes with DDK compatible libs, only two headers are missing and we ship those with the examples. So all you need on Windows is MinGW. And even if you cross-compile for Windows on Linux, you use the MinGW libraries which include enogh of the DDK to make...

Regarding transfer speed: The poll rate is only relevant for interrupt endpoints. What you compute would be the maximum data rate for an interrupt endpoint when you send a maximum of 8 bytes on each poll. In practice, people use control endpoints for higher volume data transfer on low speed devices....