Objective Development Forums

The USB IRQ needs to be able to interrupt the USART ISRs -- either put a sli after saving the sr (assembler) or define your ISRs as

ISR( UARTn_.._vect, ISR_NOBLOCK )
{
..
}

when using GCC w/ avr_libc.

I bet the electrical specs are different, there may be diffences in the registers/behavior too. Do you have a schematic to take a look at ? AVR GCC (and avr_libc) expects atmega88p as parameter for -mmcu..

AVR-USB requires IAR or AVR GCC for a compiler, WinAVR 20071221 works out-of-the-box. As for an IDE, Atmel's AVR Studio comes w/ native support for WinAVR. Correct, most OS's come w/ native HID drivers. USB itself is pretty complex, take a look at USB in a Nutshell to get an idea. Check out the comm...

But before I simply kick out this idleRate-stuff as other people seem to do I'd like to know what it is exactly for. The Set_Idle request silences a particular report on the Interrupt In pipe until a new event occurs or the specified amount of time passes. [..] This request is used to limit the rep...

I didn't use a dynamic serial no. in my project but various other dynamic descriptors -- try something like this: uchar usbFunctionDescriptor(usbRequest_t *rq) { uchar *p = 0, len = 0; if(rq->wValue.bytes[1] == USBDESCR_STRING && rq->wValue.bytes[0] == [your serial no. str i...

I would expect any 5227 to work. The only difference should be the packaging. Just make sure the parameters are as close as possible.

Like these ? Digikey has a neat component selection tool, just type "zener" into the search bar and go from there..

Take a look at the Tiny461.

I don't see the defines for KEY_A..KEY_Q. Assuming they ae correct, I bet the index you pass into buildReport() isn't in the range 0..17. I dont use letters, as you see in recieving routine i only accept numbers and CR. And i think there is nowhere to change them during programm flow, so i dont hav...

I don't see the defines for KEY_A..KEY_Q. Assuming they ae correct, I bet the index you pass into buildReport() isn't in the range 0..17.

The BOOTRST fuse isn't programmed -- try 0xC8 for the high fuse byte. Program space is organized by words (2 bytes), hence address 0x3800. 32kb = 16kw.

I was hoping someone could show me how to modify it to include 6 more buttons. //HID Report Descriptor PROGMEM char usbHidReportDescriptor[USB_CFG_HID_REPORT_DESCRIPTOR_LENGTH] = { //ZX-Joystick-1 0x05, 0x01, // USAGE_PAGE (Generic Desktop) 0x09, 0x04, // USAGE (Joystick) 0xa1,...

Take a look at this.

No. It's a Windows issue, unfortunately.

The MS virtual com driver is not PnP aware. Lots of problems w/ it (just do a google search). There are even companies offereing replacement drivers (for $$$ tho, eg. Jungo). SP3 contains a newer driver, may help w/ your specific problem.