Objective Development Forums

Then again we have a similar issue. I'm stuck withv-usb and can not figure out how to fully emulate an xbox controller. Guessing its do to the 1.0 limitations but I have not gave up yet.

viewtopic.php?f=8&t=2152

If I here back from Ralf I will let you know.

I tried to contact Ralf but his email address is bouncing. I can't see anything he does differently in his code anyway.

I was not suggesting he did it, but that he may know why it's not possible with v-usb. I think I have another email address for him I'll check. I'm 99% sure its a v-usb thing.

Its been a known issue for far too long. Most people just except it and look no deeper ;( I have never heard a good reason for it not working in linux. Have you talked to Ralf? I know he is aware of it and also a big linux buff. He may have researched it with the v-usb team a ways back. I'm fairly c...

Not sure how I go about doing this but here is what I see. On some, unfortunately I dont know what the difference is but on some computers I can not use more then an 8 packet descriptor. If I do no packets get sent. The computers that had the issues were formatted and had a new version of xp on them...

really? I wonder if its related to my problem

viewtopic.php?f=8&t=4149

Please see if you can dig that up, maybe I need to update my v-usb firmware.

I have a number of systems that work, enumerate, and function. And I have another number that does not even attempt to pass data to the host. Using a protocol analyzer it immediately tells me "device problem". I'm using 1/2 watt diodes and 68 ohms for my - + leads. I also have a 1.5k pull ...

Thank you for this info. So you made no changes from the 168 code to work with 328 chips?

Why do most v-usb examples show 1.01? From what I know the usb spec is 1.1 now? I seem to be having troubles when setting my version to 1.1 is there something I need to know.

Why do I see this so much?


Should it not be 0x10,0x01

ok I think I get the problem but cant make it work. This is what I do normally. my_usbDescriptorConfiguration[25] = rt_usbHidReportDescriptorSize; and now I do this.. my_usbDescriptorConfiguration[25] = rt_usbHidReportDescriptorSize - 0xff; my_usbDescriptorConfiguration[26] = 0x01; I also set #defin...

Well I know my post was lengthy but if you look back you will see I was able to send multiple packets with another project I had. So in theory , this should work. I'm not sure what the bottle neck is. I personally think its my knowledge of v-usb. But getting anyone with the correct knowledge or expe...

Grobi, I was sort of interested in trying this again. After failing to talk to the non-existent descriptor I gave up. But maybe helping you will get me thinking right and finally get this done. First what is the issue, you can not enumerate it? To me this is the easiest part. I looked back at the co...

There are countless topics on this actually. Here is where I learned how to do it.

http://www.obdev.at/products/vusb/prjdetail.php?pid=69

It uses two hid devices and talks to 0 or 1 using the first report bit.

I'm trying to resolve a problem dealing with desc lengths. I need to get the answer to this "What about the code that sequences the descriptor out of your firmware to the host? Does that have a byte-sized counter for keeping track of "remaining bytes"? " Can anyone understand, re...

See this post
http://forums.obdev.at/viewtopic.php?f=8&t=4022

It's the same beast, the P version gives issues. Waiting on an official word on the updates illustrated in that post.

I got a reply on usb-if, can anyone answer this, or point me to where I might find the answers.

What about the code that sequences the descriptor out of your firmware to the host? Does that have a byte-sized counter for keeping track of "remaining bytes"?