Lpc2000

The LPC part of the USB code does not concern me that much. Writing and 
testing drivers for all  versions of windows (and maybe other operating 
systems) is something I am not looking forward to. I know that libusb 
and libusb-win32 (on sourceforge) may be of some help here, but they are 
still beta. I did not try this yet.  I also did not find a affordable 
way of registring my own vendor id.

This is the reason I am using FTDI chips for USB now. They provide a 
single FIFO channel that can be used like a very fast serial port and 
drivers all available for many operating systems. Maybe others have some 
experience with USB, and know something that can get the rest of us 
started with USB?

/RD


donwillwonthe wrote:

> Im thinking of swapping for the LPC2148 from my almost out the door
> PCB design containing an LPC2138 .... does anyone know what code
> overhead is involved with USB - a humble implementation would be all I
> need. Horrified by losing 24KBytes of RAM. Why so many endpoints? This
> is not a comms hub chippy.
> Looks sooooo complicated compared to a good old RS232 two wire
> connected to hyperterm implementation!
> Your wise words would be appreciated.
>
>
>
> ------------------------------------------------------------------------
> YAHOO! GROUPS LINKS
>
>     *  Visit your group "lpc2000
>       <http://groups.yahoo.com/group/lpc2000>" on the web.
>        
>     *  To unsubscribe from this group, send an email to:
>        lpc2000-unsubscribe@yahoogroups.com
>       <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe>
>        
>     *  Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
>
>
> ------------------------------------------------------------------------
>