Roughly how long would it take to implement V-USB on an ATmega8/32/64? I have a lot of AVR experience but none with V-USB. I have done USB on non-AVR MCUs and also on the AT90USB1287 (LUFA).
I know this is highly dependant upon the developer's capabilities, but I am just looking for a rough number for an estimate.
10 hours? 25 hours? 50 hours? 100 hours? more?
(Sorry if this post pops up twice. I posted over an hour ago and it didn't show up so I am trying again.)
Development Time
Re: Development Time
- I had 0 experience with avr and usb-v . With the examples they have it only took me 1/2 a day. And most of that was due to fuse settings and learning the nature of avr. If by that you mean just creating a simple usb project and you do in fact have avr experience it should be as simple as a compile. Create an avr project, put in the example code and compile. Learning how to interface(send data ) with the usb for me was very simple. Create a HID to do what I want was a bit difficult I spent a few weeks on that. I still have not implemented data from host to client ( ForceFeedBack ) and I'm still trying.Roughly how long would it take to implement V-USB on an ATmega8/32/64? I have a lot of AVR experience but none with V-USB. I have done USB on non-AVR MCUs and also on the AT90USB1287 (LUFA).
Re: Development Time
2 hours. Including the one hour i wasted because the USB cable i bought from a local store did not follow the color coding as described in wikipedia. I havent attempted HID but custom class devices are very easy to make with V-USB. The author has done everything for you. Someone with even very little experience in AVR can also pick up on V-USB. The documentation is simply superb. Even a noob like me couldn't go wrong.
Re: Development Time
Thank you for the responses.
If you are doing a standard device (keyboard, mouse, joystick, etc) Windows may already have a usable HID driver for the PC side. Are you saying that you needed a special HID and that the Device-to-Host portion was easy but the Host-to-Device was your difficult part?
Create a HID to do what I want was a bit difficult I spent a few weeks on that. I still have not implemented data from host to client ( ForceFeedBack ) and I'm still trying.
If you are doing a standard device (keyboard, mouse, joystick, etc) Windows may already have a usable HID driver for the PC side. Are you saying that you needed a special HID and that the Device-to-Host portion was easy but the Host-to-Device was your difficult part?
Re: Development Time
Yes, I personally find it extremely frustration, confusing, and lonely. Not only can I not find working examples, people point blank dont answer questions on the matter, hence I dont think its just me.
Re: Development Time
I have done several medical products that required USB connectivity. I wrote a GUI on the PC side using C#. There were several examples available to get me started but the device was unique and required special HID considerations.