Objective Development Forums

Maybe it's the problem of USB initializing...

I was working on it for a long time.

Try to change them according to your own schematic.

sprhawk: Can you examine your descriptor somehow as its received on your host? I could resolve some of my problems with the great tool evtest under linux. It shows first the supported events of a device in a summary and then just all actual events as they come in.. very helpfull. for example with t...

Thank you!

the previous version was Release 2007-03-29

the new one is :Release 2007-08-07

I tested again. I am sure that the previous can't work correctly.

the previous version was Release 2007-03-29

the new one is :Release 2007-08-07

I tested again:
i used "make clean --> make all"

and flashed the program to m16, the descriptor worked!!!

I don't know why? I used the method before, but failed.

Maybe, because the usbdrv I used today is a new one.

It worked! Thank you, AVR-USB, all the same.

I have posted several posts in this forum, to ask why a correct(or even used to be correct) HID Report Descriptor didn't work correctly. today, I deleted the usbdrv directory and copy a new one there, recompiled again, the Descriptors worked again! However, when I changed the previous worked Descrip...

the working one: char usbHidReportDescriptor[25] = {//OK//ok 0x05, 0x01, // USAGE_PAGE (Generic Desktop) 0x15, 0x00, //Logical_Minimum (0) 0x09, 0x04, // USAGE (Joystick) 0xa1, 0x01, // COLLECTION (Application) 0x05, 0x02, // USAGE_PAGE (Simulation Controls&#...

what do you want to make?

I'm being making an HID joystick too:D

MSN:sprhawk "at" sohu.com

what's this descriptor wrong? char usbHidReportDescriptor[41] = { 0x05, 0x01, // USAGE_PAGE (Generic Desktop) 0x09, 0x04, // USAGE (Joystick) 0xa1, 0x01, // COLLECTION (Application) 0x09, 0x01, // USAGE (Pointer) 0xa1, 0x00, // COLLECTION (Physical) 0x09,...

The bug has been fixed, I used a Mega16 board that is connected as MJoy16, the descriptior works. I don't know why.