Bitbashed Low Speed USB
ckf13 <[email protected]> Mon, 25 Aug 2003 15:15:21 +1200
| Newsgroups | gmane.comp.hardware.avr.general |
|---|---|
| Message-ID | <3F479D7C@webmail> |
Hi, I stumbled across Ing. Igor Cesko's bitbashed implementation of Low Speed USB some time last year and thought it was interesting but didn't have any time to investigate it further, or even build it to verify it worked. Doing some googling last night I came across this mailing list where a couple of months ago there was interest in further developing this project and some evidence that yes it does in fact function as specified. Is it as easy to get working as specified? How far have people got in their efforts to further this project? There was a call for interest for someone to develop a Linux and/or a Windows device driver in order to be able to utilise such a "beast". I would be interested in such a development project (both Linux and Windows), depending on interest as I was heading down that direction myself anyway. I might not be the most experienced device driver developer, but that's why I've been looking for interesting projects to further enhance my skills upon. This project seems to be a really interesting way of further honing my skills. Up till present I've only implemented "useless" drivers, such as one to invert the coordinates of my USB mouse. The biggest project so far was to produce the starts of a "virtual serial port" (Win2K platform) style device driver, much like those drivers utilised for the FTDI232 and FTDI245 style USB solutions.. I got as far as being able to enumerate it via apps such as HyperTerminal. >From memory (i'm presently at work) there was a Windows device driver provided with the original solution but it was a binary only solution and hence isn't a good starting point for a "generic driver" for similiar projects which implement different end uses for the stream of data. Is there still interest in further developing both the AVR firmware and the deveice driver for this project? I would love to help out by attempting to provide a device driver which might possibly work :-). I suppose in my case the first step is to actually build one as described with the supplied hex image and see how well i can get it going in my setup (Linux based). Thanks, Christopher Fairbairn.