Re: [lwip-users] TM4C1294 LWIP Usage

[Noam weissman]

Hi Lee,

In one of my previous mails I wrote that you can use the tcp_sent call-bak.

If you are able to send one packet simply take you code that creates the reply
and put it in your own function.

Call this function either from the recv call back or from the tcp_sent call-back
For every packet sent out the TCP stack will call your tcp_sent function. That 
is 
if you defined one and registered it in the accept call-back.

BR,
Noam.


-----Original Message-----
From: address@hidden on behalf of Lee
Sent: Sat 12/20/2014 2:24 AM
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

 
 
************************************************************************************
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.
************************************************************************************

<<winmail.dat>>