Objective Development Forums

W/o going into detail (too late here..) -- you'll have to define multiple reports in the descriptor. Each report can carry 7 bytes data max (8th byte is the report ID). Details should be in the USB specs.

Nah, just making sure you changed -mmcu=atmega8 to -mmcu=atmega88 ..

Could you add your makefile to the sources ?

You also have to change F_CPU in hardware.h BTW. Just tried it w/ the doper version currently up for grabs -- after switching to 16MHz, latest WinAVR (avr-gcc 4.1.2, avr-libc 1.4.6) errors when linking: avr-gcc -Wall -Os -Iusbdrv -I. -mmcu=atmega8 -DDEBUG_LEVEL=0 -o main.bin usbdrv/usbdrv.o usbdrv/u...

Did you try setting the fuse bit EESAVE to 0 ?

Does it enumerate if you comment out your timer handling and just have the USB stack running ? 2kHz is quite an ISR load and may interfer w/ the USB ISR.

Well.. 5.6 Reports Using USB terminology, a device may send or receive a transaction every USB frame (1 millisecond). A transaction may be made up of multiple packets (token, data, handshake) but is limited in size to 8 bytes for low-speed devices and 64 bytes for high-speed devices . A transfer is ...

That's a short item w/ a 2 byte value -- it's just the way the encoding is defined: 6.2.2.2 Short Items The short item format packs the item size, type, and tag into the first byte. The first byte may be followed by 0, 1, 2, or 4 optional data bytes depending on the size of the data. [..] A short it...

Well.. While Logical Minimum and Logical Maximum (extents) bound the values returned by a device, Physical Minimum and Physical Maximum give meaning to those bounds by allowing the report value to be offset and scaled. For example, a thermometer might have logical extents of 0 and 999 but physical e...

I am playing around with some simple USB HID game devices. Hardware es essentially the same as my C64 USB keyboard . 1) Is there some tool that can show the HID report descriptor received when plugging in a device? I would like to use this to examine the report descriptor of some commercial HID dev...

Try changing "awk" in the checksize script to "gawk". Worked for me.

Odd that changing the M103C fuse doesn't change the behavior.. Could you post the values of the three fuse bytes ? I would suggest these values: Extended fuse byte -- 0xFF High fuse byte -- 0xD9 Low fuse byte -- 0x9F Also, what version of WinAVR are you using ? 20060421 or 20070122 ? (the latter is ...

Hm, is the M103C fuse programmed (it is by default) ? If so, kill it.

Wuerde mal auf nicht oder falsch programmierte fuse Bits tippen -- welche Werte hast Du programmiert ?

Edit: Der Tiny2313 hat nur 128 Bytes RAM, das koennte das Problem sein. Wieviel RAM ist von dem Programm belegt, wieviel Stack braucht es etwa ?

Thank you very much. I switched my project to the new stack, compiles fine in WinAVR 20060421 & 20070122 (latter creates bigger code tho.) I'll let you know if there are any problems.