Objective Development Forums

Interesting. Does this affect devices with interrupt endpoints only, or also custom class devices?

And can you track it down to a particular request, e.g. CLEAR_FEATURE or SET_FEATURE for an endpoint?

have a look at the libs-device directory. It contains example code for calibration at connect time and for continuous tuning.

Just posted the reply in the other thread, hope that does not cause too much confusion... Here's a copy: I have never tried one of the AVRs with P suffix. Maybe they need additional initialization? Or have other fuse values? If you take the HID Mouse project and change F_CPU to 12.8 MHz, it won't wo...

I have never tried one of the AVRs with P suffix. Maybe they need additional initialization? Or have other fuse values? If you take the HID Mouse project and change F_CPU to 12.8 MHz, it won't work. You must also add some kind of oscillator calibration and change the fuse values so that the internal...

This will be the next step. I don't know what options wikidot.com offers, but we'll check that next.

We have renamed AVR-USB to V-USB to avoid conflicts with a trademark of Atmel Corporation.

Let's start at the basics: Did you make sure that the fuse values are correct? In particular, there are settings to divide the clock by 8 and whether to use the internal RC oscillator. Since you can blink an LED, the processor seems to be running. Check that the clock rate is OK. Also, the mouse exa...

A VID/PID pair identifies a device type. No two device types may share the same VID and PID. E.g. you can't have a keyboard and a mouse with the same VID and PID, not even two different types of keyboard. To ensure that nobody else uses a given pair of VID and PID values, usb.org maintains a registr...

Since these examples are intended to run on almost any hardware, there hardware initialization is kept at a minimum. In most cases it's only the code in usbInit().

Ah, I overlooked that this is a keyboard. Good to know how keyboards and mice can be opened!

BTW: Please don't use the shared USB PID for HID devices with a keyboard. Windows permanently attaches the keyboard driver to this PID which causes all kinds of troubles.

Sorry, don't know the answers.

But where the hell is this line of code located in powerSwitch.c?

The following link should work until the big renaming is done:

http://www.obdev.at/downloads/avrusb/av ... 090323.zip

There are examples which ship with the driver itself, most of them have no particular hardware requirements. For debugging, compile with -DDEBUG_LEVEL=1 or -DDEBUG_LEVEL=2. The debug output is a hex dump sent to the processor's TxD with 19200 bps. For debugging from the host side, use a USB sniffer....

The limit of the resistor value does not depend on the type of AVR you use, it depends primarily on the characteristics of the zener diode and the voltage limit on the host side.

PowerSwitch is not registering as a HID. If you have modified it to be HID, you may need the filter versin of the libusb-win32 driver.