Objective Development Forums

1.) A driver is something I would rather like to avoid, ... would be better if it would work out of the box completely agree Well maybe you can help me with the out put from host functions.. But if you want the HID FFB to work you better get typing because you have a long way to go. I'd first off g...

Yes, I have just about got it working, but there are a few unanswered questions. Two ways to do it.. 1) a driver: If your up for that let me know how it goes... 2) the Hid defined physical layer: Been working on this for a year on and off and finally got the descriptor finished. There are a few issu...

Nope, thing.. Its like I'm missing something? Hopping for someone to school me on this.

Well yes you do need the control added in the descriptor. I dont know what it should look like in your case, is depends on how you want to interface the device. For example if your device is going to receive data like the data example set it up like that. Also yes, the usbFunctionSetup does need to ...

I think your after the same thing I am
viewtopic.php?f=8&t=4231

The function you want is usbFunctionWrite. Let me know if you have any luck, see the hid-data example provided with the driver it shows how its done.

If usbSetInterrupt is to send data to the host, how to you capture data? I added USBRQ_HID_SET_REPOR to my function set up. unsigned usbFunctionSetup(uchar data[8]) { usbRequest_t *rq = (void *)data; if((rq->bmRequestType & USBRQ_TYPE_MASK) == USBRQ_TYPE_CLASS){ /* class request type */ if(rq->b...

The latest version of v-usb supports 16mhz, all you should have to do is set the freq in your make.

Well I know its not on the 168 chip but this should work on it.

http://forums.obdev.at/viewtopic.php?f=8&t=3931

Guessing both projects are using the same pid? You need to clear the registry entry for that pid. For example in xp you woudl go here [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet007\Control\MediaProperties\PrivateProperties\Joystick\OEM\ [[ find your pid ]] I dont know about w7, but you can make it any nam...

Oh, and I looked on Ralph's site but couldn't see where he did it that way.

Yeah, Grendel fixed his post to clear up the confusion. I'd like to see how you make out.

I noticed one thing which may be of interest. V-USB reports USB version 0x10, 0x01. Most USB 1.1 devices seem to go with 0x01, 0x01. I will send a test firmware to my Linux tester to see if it makes any difference. If you look a few posts down you will see that was already answered. http://forums.o...

Ok I did a lot of tracing and found the break down in here static inline void usbProcessRx(uchar *data, uchar len) when it calls for usbDriverSetup it returns a 8 bit car value. notice the end.. return len; } and the beginning static inline usbMsgLen_t usbDriverSetup(usbRequest_t *rq) { uchar len = ...

I had a similar problem.

viewtopic.php?f=8&t=4149

Turns out my zeners ( surface mounts ) where the problem. I put my through hole zeners in place and it now works direct to the PC. My readings were 4.0 volt though.

I'd like to also make that comment, v-usb is simple an amazing development. If I ever had gripe it would be lack of definitive answers. I'd like to see some sticky posts, or attempts to answer some of the question that dead end. I do understand its free ware and certainly appreciate that. However so...

I do realize moving a full avr usb based device woudl achieve my goal. But where is the fun in that? Really though, ditching the 88 style chip woudl through out my entire design. I'd rather ditch the xbox idea yet I seem to have this knack to make things work that should not. Definitely let us know ...