Objective Development Forums

Oh cool, yes I too considered that but I wanted to add ADB to my legacy code (328). BTW, I didn't make any special arrangements to the v-usb to get it to work but I also don't have to read a sh*t ton of keys and only needed 3 commands each update;) FYI: I'm told linux will pull at 2ms with v-usb but...

So to get what you needed, you had to make changes to the asmcommon, interesting. Thx for sharing, I would guess that was not you, unless the initials SG mean anything to you.

Why are you talking about the ADB protocol? What is really strange about this, is that I just wrote a firmware driver for ADB last week but I never mentioned that in this post? It's like you can read minds LOL... That is crazy coincidental, I was just talking to a guy that did the ADP keyboard thing...

Can you elaborate on this "If you synchronize to USB packets", this sounds interesting to me, unless you mean interrupt packets as a posed to bulk?

I'm using a project that says one of its limits is The transmit routine disables all interrupts while a byte is being transmitted. For a typical 9600bps link that is approximately 1 millisecond. In some cases this might cause problems with interrupts which need urgent attention. Will v-usb handle th...

a) Everyone's USB 3.0 works fine?
b) Nobody cares?
c) "3.0" doesn't search correctly?

a) Get one person here to say V-USB works on a 3.0 port.
b) not many
c) its not an easy search no.

From what I here is buggy and will not work right. Also my project does not work on my 3.0 port. I can not find anything official on this, and I too would like to here from Christian on this.

I don't quite follow you here but most of the communication is handled in;

usbFunctionDescriptor
usbFunctionSetup
and
usbFunctionWrite

If I knew more of what you were after I may be able to help.

Yes it work fine, nothing is needed for changes. Check out USBLyzer (free trial) to see what the issue is. If you are using mega168/328/88 make sure you use 1/4 z-diodes.

Try. PROGMEM const char usbHidReportDescriptor[43]= { 0x05, 0x01, // USAGE_PAGE (Generic Desktop) 0x09, 0x04, // USAGE (Joystick) 0xa1, 0x01, // COLLECTION (Application)] 0x09, 0x01, // usage pointer 0xa1, 0x00, // COLLECTION (Physical) 0x05, 0x01, // USAGE_PAGE (Generic desktop) 0x09, 0x32, // USAG...

Sending data to the device has nothing to do with the schematic? To send data you need to use the usb write functions. There are a few examples on the forums here and even a data example (hid-data) is included in the samples from v-usb's downloads.

Sorry not clear why you need to change the device but consider.
0x09, 0x05, // USAGE (Game Pad = 05)
0x09, 0x04, // USAGE (Joy Stick= 04)

So did it all work out then?

I think this makes descriptors and comments as well. http://hidedit.org/

Right changing VID and PID have 0 effect on how the device preforms. As mentioned run the code untouched, if that gives you the same errors, it's not what you did If it seems to work without your changes then you are not changing the right values. Show us what you changed.

I'm really confused by your report here and what you are expecting? Your descriptor shows it needs 10 bytes( 2 analogs and 8 buttons), BTW buttons are normally done with one report ( 8 bits: a bit mask), I'm guessing you know that. EDIT!!! 0x95, 0x04, // REPORT_COUNT (2) <--- ahhh... see never do th...