|
From: | Noam Weissman |
Subject: | Re: [lwip-users] RAW LWIP TCP Client |
Date: | Sat, 18 Mar 2017 18:42:45 +0000 |
Hi Matthew,
Please explain what you want to do as I am still in the dark.
You probably have a client as well? Who is sending what ?
There is an echo server that is probably what you need. It excepts a connection, on receive it reads some data, send it back and closes the connection.
Examples are in the contribution, also see here:
http://lwip.wikia.com/wiki/Sample_lwIP_applications https://github.com/goertzenator/lwip/tree/master/contrib-1.4.0/apps
From: lwip-users <lwip-users-bounces+address@hidden> on behalf of emseahays <address@hidden>
Sent: Saturday, March 18, 2017 8:17 PM To: address@hidden Subject: Re: [lwip-users] RAW LWIP TCP Client I basically scrapped the http server code, but rewrote similar functions. My goal is just to be a able to create a TCP connection and send one packet per connection and I want that to happen repeatedly, everytime I hit a btn on the board or perhaps in a timer interrupt.
Where are the examples?
What I’m doing now works to a degree. I’m wondering if there is a problem with the way I close a connection. I’ve been told I don’t need to wait for the server to close, but I run into the same situation when I close before the server does.
When I run the LWIP_DEBUG it never says it goes into CLOSED state, I only see it say it goes into SYN-ACK state, ESTABLISHED, and CLOSED-WAIT states.
I don’t use tcp_poll, which I’m wondering if that’s a way I could fix the problem. Did u look at the log I included in my last post?
Best,
-Matthew
From: [hidden email]
Hi Student,
1. Maybe if you will first describe what you want to do we may help you more. I did not understand? 2. I am a bit on the dark how you want to change the HTTP server without knowing the basics?
From the little you wrote I am not sure that the HTTP server is the code you need to start with. The HTTP server is designed to accept a request, parse it, send some data back and CLOSE the connection. This is the basics but it does much more. Therefore it may not be the base code to start with you own project.
If you need a server that gets a connection, stays open and be able to send back some data every time you click a button, you need to check other examples.
BR, Noam.
From: lwip-users <lwip-users-bounces+noam=[hidden email]> on behalf of emseahays <[hidden
email]>
I'm an EE Student working on a project involving modification of example code
If you reply to this email, your message will be added to the discussion below: http://lwip.100.n7.nabble.com/RAW-LWIP-TCP-Client-tp29090p29096.html To unsubscribe from RAW LWIP TCP Client,
click here.
View this message in context: RE: RAW LWIP TCP Client Sent from the lwip-users mailing list archive at Nabble.com. |
[Prev in Thread] | Current Thread | [Next in Thread] |