Lpc2000

Joel, 

> > Recently I was in the same dilemma. Is the OpenTCP project 
> still active
> > ? I am about to integrate a TCP stack in my RTOS and I am 
> choosing with
> > which one to go.
> 
> Last release of OpenTCP: 2003-08-03
> The last post may sum it up on OpenTCP:
> http://sourceforge.net/forum/forum.php?thread_id=1031838&forum
> _id=224425
> 
> 
> Paul what where the big differences between lwIP and uIP?

lwIP has a sockets-like API, uIP doesn't.  lwIP has many more
TCP/IP-related features than uIP does (windowing, for example) and will
potentially have a better throughput for applications that are streaming
data.  uIP has a single segment in flight at any time hence falls foul
of delayed ACK implementations of TCP/IP (cf Windows at least).  uIP
applications are harder to write than lwIP apps as uIP does not use
threads (but there is something called protothreads that you *can* use
to make life easier).  lwIP is bigger in RAM and code size, uIP is small
in both.  uIP runs a full web server on MSP430s in 8K of code with a
fully-compliant stack and less than 1K of memory (and that's with a big
packet buffer).

If you have space issues, uIP is the way to go.  If you don't, then lwIP
is more the thing.

--
Paul Curtis, Rowley Associates Ltd  http://www.rowley.co.uk
CrossWorks for MSP430, ARM, AVR and now MAXQ processors