Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

Re: [lpc2000] Re: Looking for TCP/IP stack

2004-03-16 by Bogdan Marinescu

I agree. Look at uIP, it took me less than a sunday afternoon to port it to an eZ80 board with a CS8900 controller. And I didn't have the driver for CS8900. My experience was very good with uIP 0.6; meanwhile 0.9 was released and it fixed some bugs that I have to fix myself in the 0.6 version (yes, this also happened in the same afternoon). So give it a try, I don't think you'll regret it. 

embeddedjanitor <charles.manning@...> wrote:
--- In lpc2000@yahoogroups.com, "r_stickley" <r_stickley@y...> wrote:
> Wondering if anyone has any recommendations for a good TCP/IP stack.
> I just assumed that if we switched to an ARM processor, there would 
be 
> lots of stacks available, but I'm not finding many.
> 
> Several I've looked at are in the $10K range (very nicely done I'm 
> sure, but too expensive for a small project).  Several embedded 
stack 
> companies are now out of business also...
> 
> Main requirements are to support as many TCP levels as possible, in 
a 
> minimal amount of RAM...for something under $1K.
> 
> Thanks in advance!

Generally I'd say that TCP/IP stacks would be written mainly in C and 
thus CPU neutral. Have a grub around various LGPL and similar 
offerings. With LPC21xx, your biggest worry is probably going 
to be keeping the RAM footprint small. Look at http://dunkels.
com/adam/uip/size.html which has been crafted for small size.

-- Charles





Yahoo! Groups SponsorADVERTISEMENT


---------------------------------
Yahoo! Groups Links

   To visit your group on the web, go to:
http://groups.yahoo.com/group/lpc2000/
  
   To unsubscribe from this group, send an email to:
lpc2000-unsubscribe@yahoogroups.com
  
   Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 


Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.