lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] TM4C1294 LWIP Usage


From: Noam weissman
Subject: Re: [lwip-users] TM4C1294 LWIP Usage
Date: Sun, 21 Dec 2014 11:39:56 +0200

Hi Paul, Lee,

Calling tcp_output after tcp_write will notify the TCP stack to send the
data immediately but if
You do not exit the call-back function it will not be sent.

Noam.

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of Paul
Webber
Sent: Saturday, December 20, 2014 9:20 PM
To: address@hidden
Subject: Re: [lwip-users] TM4C1294 LWIP Usage

Lee,

tcp_write puts the data in to the tcp buffer. After tcp_write try
tcp_output.

Paul

________________________________________
From: address@hidden
<address@hidden> on behalf of Lee
<address@hidden>
Sent: Friday, December 19, 2014 7:24 PM
To: address@hidden
Subject: Re: [lwip-users] TM4C1294 LWIP Usage

Hi Noam,

I am still trying to get a simple send function working which is
frustrating. Perhaps it is more of a C issue than a LWIP (client or
server) issue. Once I have a connection I can do 1 send with tcp_write
called in either the recv callback or the accept. Once connected however
I am stuck as to where to call another write. I think I would have to
make the functions extern and the pcb more global to call another write
from main or any included application code. Is this how you did it?

Lee.



--
View this message in context:
http://lwip.100.n7.nabble.com/TM4C1294-LWIP-Usage-tp23623p23636.html
Sent from the lwip-users mailing list archive at Nabble.com.

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users

_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users

 
 
************************************************************************
************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals &
computer viruses.
************************************************************************
************






************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer 
viruses.
************************************************************************************






reply via email to

[Prev in Thread] Current Thread [Next in Thread]