Objective Development Forums

Show us your schematic, or at lease the usb side of it.

Do you mean PROGMEM ? const char analog_usbHidReportDescriptor[] PROGMEM = { ///// gampad 0x05,0x01, // Usage Page Generic Desktop 0x09,0x05, // Usage Joystick 0xA1,0x01, // Collection Application //axis 0x85,0x01, // Report ID 1 //0x05, 0x02, //USAGE_PAGE (Simulation Controls) //0x09, 0xBB, //USAGE...

why not just contact mojo? He is still around and still active. I'm sure he can help you. Mojo knows his stuff and should have an answer. I know the ps3 has a different packet style, so maybe its simple as putting the button on another byte. Also he uses Igor Cesko's USB implementation here not usb-...

Ah right you are, I forgot about that caveat. I can't offer much more help on that. Wait around and see if another can.

You define your D pins in the usbconfig.h file (Hardware Config). You can set them up on any pins that are int pins.

for an example of the descriptor see Post #: 35 at this link http://www.microchip.com/forums/tm.aspx ... 25&mpage=2

Yes its big, yes I tried to chop it down, no it does no budge. You will need the latest version of v-usb as a patch had to be made to allow > 254 descriptor lengths.

Its a bit to get used to but not too hard. This is using the ADC's on an atmega 168/328 //voltage reader. #define ADC_VREF_TYPE 0x40 static int read_adc(unsigned char adc_input) { ADMUX=adc_input|ADC_VREF_TYPE; _delay_us(150); ADCSRA|=0x40; // Start the AD conversion while ((ADCSRA & 0x10)==0);/...

I wonder if HID over I2C may do it?

Also I know VMware has a VMBus HID mini port virtual nic. Not sure about making a descriptor to communicate with it though. Did you look at the HID Descriptor Tool? Maybe there is a HID network virtual driver.

I think straight answer is better than wasting bandwidth told me to look for the "good example" which I didn't know which is "good" exactly because I'm new to this V-USB, and told me to try to use >255 then (which make me asking here in the first post), OK first off if you're go...

Like what? Any link to it? So I guess you never even downloaded the package? The examples come with the download. Possible if less than 255 bytes (as I knew so far) no, possible if > 255. See this descriptor at post #35 m that is the one I use. mouse or joystick examples only needs under 255 bytes,...

So my question is simple, how I can get more than 255 bytes in descriptor? There is no trick, just do it. Like I said find a better example. Or more simple is how can I cast the descriptor into "int" or is it possible to cast it into "int" as the usbHidReportDescriptor[] was &qu...

First you're going to have to learn a little patience. "Anybody home", really? Second please use the "code" button so its not painful to read this. Make things easy for people to help you. Third you code is a mess, things like if (rq->wValue.bytes[0] == 5) is really bad practices...

Yes it was fixed, I committed the bug. Can you show a bit more code? I think the issue is in the typing of the descriptor functions. Just add your main to the thread and I'll spot the error.

All it does is throttles the power for your device and reports the usage to the host. For example if you make a device that uses 50ma then why leave the max power at 100. In doing so you just told the host to waste 50ma. So you set 50 for USB_CFG_MAX_BUS_POWER. The second case would be like I mentio...

level it bee unless you need to borrow more power. There is no "correct entry" it just depends on what you need. For example if you get power exceeded, then up it.