Lpc2000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

tsvetanusunov wrote:
> --- In lpc2000@yahoogroups.com, Steve Franks <stevefranks@i...> wrote:
>>
>> >Again, I have kids to feed and a company to run.  Sorry.
>>
>> I notice this keeps coming up.  Name your price, then.  Sounds like it
>> may become a preffered option for those with no budget for hardware
>> analysers.  Guess philips missed the proverbial boat somewhere in
>> their usb implementation.  The rest of us'll stick to the ftdi &
>> cp2101 chips, I guess.  Ethernet keeps looking better and better...
> 
> Philips didn't miss anything and LPC2148 USB is working as it says in
> the Philips documentation.
> We made at Olimex ->  USB mouse, USB mass storage, USB audio HID
> devices codes which works without problem whatsoever (don't ask for
> sources these are commercial projects :)
> 
> The only problem I can think of with LPC2148 USB is that everybody
> these days rely to use somebody's else code and not to read the
> datasheets and write one by himself.
> 
> This is why *everybody* start writting LPC2148 USB code based on KEIL
> Mass-storage demo code which is useless piece of crap as it doesn't
> handle the interrupt flags properly and the code may suddently freeze
> up (actually it's perfect for "demo" it shows something and is useless
> for anything else, so well done Keil!).
> 
> C'mon guys use your heads :) I know Internet made it too easy now and
> when you get new project first thing is to search for ready made code
> examples which to re-use but this is definitely not the best approach!
> 
> just my 2 cents..

I won't mind working on an open-source USB stack. In fact, I already
started a bit. I'd like to see a USB-stack released under a license
that allows hobby and commercial use in source and binary form, but
with the requirement that any improvements and additions to the
stack are also made open-source to be integrated back.
It looks like the LGPL is a good match for that.

Basic design ideas (mostly fairly obvious):
* layered approach:
  * USB HW layer that talks to the actual hardware
  * USB core layer that knows how to handle basic USB structures and
    can handle endpoint 0 (ep 0 is special)
  * USB application layer
* Interrupt driven. Basically there are just two interrupt types:
  * device status interrupt (frame, connection state changes, etc.)
  * endpoint interrupts (EP buffer received/transmitted)
* USB core layer is independent of USB application layer
  * USB application layer installs callbacks for the interrupts
    (device status and endpoint) and for USB descriptors.
* No support for DMA yet to keep things simple.

The stack should be completely free from anything that prohibits
open-source use (e.g. ambiguous copyrights). So for now I started
to work just from the datasheet, hopefully re-inventing the wheel
for the last time.

It seems that the USB controller in the LPC214x is at least partially
identical to the Philips PDIUSBD11/12 and ISP118x USB device
controllers. Does anyone know of any suitable free source code
to re-use?

Kind regards,
Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFD3MVuETD6mlrWxPURAo/hAJ9t9WXcDz2x4rP8RDlXnWjdhueNGwCfWBET
4dFAKPteN5BMmu7SO6KPswM=
=Pp+N
-----END PGP SIGNATURE-----