SPNA248 March 2021 TM4C1292NCPDT , TM4C1292NCPDT , TM4C1292NCZAD , TM4C1292NCZAD , TM4C1294KCPDT , TM4C1294KCPDT , TM4C1294NCPDT , TM4C1294NCPDT , TM4C1294NCZAD , TM4C1294NCZAD , TM4C1299KCZAD , TM4C1299KCZAD , TM4C1299NCZAD , TM4C1299NCZAD , TM4C129DNCPDT , TM4C129DNCPDT , TM4C129DNCZAD , TM4C129DNCZAD , TM4C129EKCPDT , TM4C129EKCPDT , TM4C129ENCPDT , TM4C129ENCPDT , TM4C129ENCZAD , TM4C129ENCZAD , TM4C129LNCZAD , TM4C129LNCZAD , TM4C129XKCZAD , TM4C129XKCZAD , TM4C129XNCZAD , TM4C129XNCZAD
The enet_tcpecho_server_lwip example demonstrates an echo-server application running on the TM4C129x MCU using TCP Transmission Control Protocol (TCP) as the underlying transport layer protocol. TCP is a connection-oriented protocol with built in error recovery and retransmission. The connection protocol is likened to a telephone connection. Both the sender and the receiver need to handshake for the connection (for example, the caller calls the number and the callee picks up the call) before communicating. The connection is there until one party hangs up the connection. TCP is used by applications when guaranteed error-free message delivery is required.
In this example, the TM4C129x MCU is acting as a server. The lwIP stack is configured for DHCP to automatically acquire an IP address. Once acquired, the IP address is displayed on the terminal window. The echo-server is ready by this time. The server will listen for the connection from the client. Once the client makes a connection the communication between the server and the client can start. The server implemented in this example will process the received characters by first inverting the case before echoing the inverted characters back to the client.