Objective Development Forums

I know it's like a desert around here anymore but avr-freeks are not helping much. I hope someone knows enough about this to help. Going to keep it simple and to the point for now. I'll be happy to add anything I can so just ask. I have a atmega328 chip I have the bootloader that most everyone uses ...

yes you can do that but only in windows. Seems most linux based OS's will not enumerate. To do this you just use multiple ID's. 0x05, 0x01, // USAGE_PAGE (Generic Desktop) 0x09, 0x05, // USAGE (Game Pad) 0xa1, 0x01, // COLLECTION (Application) 0x85,0x01, // Report ID 1 <------------------- 0x09, 0x0...

The problem should be due to timing or math. You didn't post the a2dRead function, or I failed to find it. If you see a pattern like this

**
****
**

instead of a circle, the pots x,y may be sharing ground or like. When one pot reaches full right it may be pulling the other back.

I need to use the 2008 build for a project I'm working on. The project works ok with the latest v-usb code or as far back as 2012. When I compile it against the 2008 the usb just resets, disconnects and reconnects. Anyone have a clue as to why?

Not sure I follow this here but I'm getting this in linux. Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 41 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x00 (Missing must-be-set bit!) (Bus Powered) MaxPower 224mA This looks bad to me, why are we clearing...

Linux oes not seem to be replying to my usb function writes? Windows seems to be ok. I do see this with usbmon > e.g. status code "-115" Assuming x86 32, -115 = -EINPROGRESS, that means URB still pending, no results yet ffff8800089495c0 3713432687 S Ci:2:007:0 s a1 01 0302 0000 0005 8 < ff...

Your basic usb set up will not allow data to the client. You send to host normally. If you want to do stuff like that you will need to use the usbFunctionWrite. This can be done with HID based drivers or by making your own vendor specific. There are lots of usbFunctionWrite examples around the forms...

0x05, 0x01, // USAGE_PAGE (Generic Desktop) 0x15, 0x00, // LOGICAL_MINIMUM (0) this is none sense. 0x09, 0x04, // USAGE (Joystick) 0xa1, 0x01, // COLLECTION (Application) 0x05, 0x02, // USAGE_PAGE (Simulation Controls) 0x09, 0xbb, // USAGE (Throttle) 0x15, 0x81, // LOGICAL_MINIMUM (-127) 0x25, 0x7f,...

Can this be changed? #define USB_BUFSIZE 11 /* PID, 8 bytes data, 2 bytes CRC */ Because I want to support this in usbFunctionWrite? 0x09,0x68, // Usage Custom Force Data Rep... 0xA1,0x02, // Collection Datalink 0x85,0x07, // Report ID 7 0x09,0x22, // Usage Effect Block Index 0x15,0x01, // Logical M...

Will this even work on v-usb? Does v-usb have enough endpoints? 9, //bLength (length of interface descriptor 9 bytes) 4, //bDescriptorType (4 is interface) 0, //bInterfaceNumber (This is interface 0) 0, //bAlternateSetting (used to select alternate setting. notused) 2, //bNumEndpoints (this interfac...

Wonderful, nice job M$!!! I hope they didn't mess up the pole rates.

Key word is "worried". If the USB is "interrupted" in any way it will not work, thus if it's working stop worrying BTW: that comment was for an older v-usb build, I believe currently there is no restriction, however if you set the poll rate to 8ms then you need to finish all work...

Right that is where you change it but window will force 8ms. You need to hack the sys file to allow fast pole times.

huh I was able to make it work by changing USB_CFG_DESCR_PROPS_STRING_SERIAL_NUMBER != 0 ? 3 : 0, /* serial number string index */ to USB_CFG_DESCR_PROPS_STRING_SERIAL_NUMBER != 0 ? 3 : 1, /* serial number string index */ So I guess the define for USB_CFG_DESCR_PROPS_STRING_SERIAL_NUMBER is the issu...

I tried to change #define USB_CFG_SERIAL_NUMBER 'N', 'o', 'n', 'e' #define USB_CFG_SERIAL_NUMBER_LEN 4 to #define USB_CFG_SERIAL_NUMBER '1', '0', '0', '1' #define USB_CFG_SERIAL_NUMBER_LEN 4 The macros are being used in the code, but the serial is always 0. How can I change the serial? I also tried ...