Objective Development Forums

Changing/adding the serial no. string should do it. Changing the device version no. may do it too.

Check usbdrv.h: Interrupt latency: The application must ensure that the USB interrupt is not disabled for more than 25 cycles (this is for 12 MHz, faster clocks allow longer latency). This implies that all interrupt routines must either be declared as "INTERRUPT" instead of "SIGNAL&qu...

You are overloading the systems input queue. Not only is the methology wrong, the report descriptor is malformed too. Here is a working example for a valid KB RD, 1st byte modifier keys plus two bytes for keys down: 0x05, 0x01, // USAGE_PAGE (Generic Desktop) 0x09, 0x06, // USAGE (Keyboard) 0xA1, 0x...

Oops, skimmed right over that, sorry. Very odd. I used the same BL w/ a mega8 w/o problems but later switched to bootloadHID since it doesn't need special kernel drivers. Anyway, what are your fuse values ? You need to set the BOOTSZ bits to 1024 words (2kbytes), BOOTRST needs to be enabled. The loa...

Wait a second -- 328p ? Did you see this ?

After defining the ID resistor you need to explicitly connect it via usbDeviceConnect() .

Bad Zeners would be my guess. For P type AVRs you really need 3.6V Z-diodes that are <= 500mW.

Try replacing the 47uF w/ a 4.7uF cap, remove the 2nd elca, and change the lfuses to 0x1f. I also would also suggest to put the diodes/resistors on the data lines as close to the MCU as possible and get rid of the long wires after the USB connector -- your flourescent lamps will wreck havoc w/ the s...

3.6V Z-diodes & 62Ohm. Make sure the diodes are rated 500mW or less.

I've used V-USB w/ a mega8 16MHz just fine. Fuse bytes I use: high: 0xD9, low: 0x1F (w/o bootloader)

The descriptors are only read during enumeration. The only way to get the host to enumerate is via a connect event. That can be done by un- and then re-plugging the USB cable or by dis- and re-connecting the USB ID resistor (UsbConnect() & UsbDisconnect()). Even if you could change the layout of...

On the 88 the GICR bits have moved to EIMSK (INT1, INT0) and MCUCR (IVSEL, IVCE).

..if I send decimal 128 (Keyboard Volume Up) the volume should increment... No effect in Windows, nor Ubuntu. Ok, I found another way, microsoft documents say: Consumer Page Audio Controls Supported in Windows Operating Systems 0xE2 Mute 0xE9 Volume Increment 0xEA Volume Decrement Which one are you...

I tried to send keycodes and modifiers and... it works! Going deeper, i've changed a line of HID descriptor to 0x25, 0x85, // LOGICAL_MAXIMUM (133) to use external keycodes (referencing usb.org hid document), and decided if I send decimal 128 (Keyboard Volume Up) the volume should increment... No e...

The D+ bit can be sampled from the INT0 input. Currently V-USB requires D- and D+ to be on the same port tho, you'll have to move D- to port D or sacrifice another I/O bit on port B for a copy of D+.