If by TCP_* API you mean the RAW API in lwIP terms, yes, it's the only API I use. I do so strictly for performance reasons and because we don't use an OS (in the lwIP sense of the term). If you have an OS I'd use the netconn or socket API? The latter will give you pretty good compatibility at the application level. If you don't have an OS (the NO_SYS=1 lwIP setting) start with the httpserver_raw demo and use that as a base for sending and receiving data. Just do your echo server in those callbacks.
Bill From: [email protected] [mailto:[email protected]] On Behalf Of Chen Sent: Thursday, February 05, 2009 10:19 AM To: [email protected] Subject: Re: RE: Re: [lwip-users] Struggling to build a TCP echo server Bill, thanks again for your time! Is there any one in this group uses TCP_* APIs to write his/her codes? ATMEL's samples do not use them, and I couldn't google out any code that actually uses them, either Regards, Chen Date: Thu, 5 Feb 2009 09:36:24 -0500 From: "bill" <[email protected]> Subject: RE: Re: [lwip-users] Struggleing to build a TCP echo server To: "'Mailing list for lwIP users'" <[email protected]> Message-ID: <003401c9879f$1ed75c70$5c8615...@com> Content-Type: text/plain; charset="us-ascii" The problem is you can't just call tcp_tmr repeatedly in a loop as you're doing. The docs for the function (in the code) say it should be called every 250mS. Bill
_______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
