SPMA080 April   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

 

  1.   Trademarks
  2. 1 Introduction
    1. 1.1 TI-RTOS Download
    2. 1.2 License
    3. 1.3 XDCtools
    4. 1.4 Versions
    5. 1.5 Configuring NDK Modules
    6. 1.6 Socket-Based API
      1. 1.6.1 BSD Style Socket APIs
  3. 2 Application Examples
  4. 3 Application Setup
    1. 3.1 Hardware Setup
    2. 3.2 Software Tools
  5. 4 Download and Import the Ethernet Examples
  6. 5 How to Create an Ethernet Application for TI-RTOS NDK
  7. 6 Enet_tcpecho_server_tirtos Example Overview
    1. 6.1 Build and Flash the Program
    2. 6.2 Check and Program the MAC Address
      1. 6.2.1 Using The LM Flash Programmer
      2. 6.2.2 Using CCS
      3. 6.2.3 Using UniFlash
    3. 6.3 Run the enet_tcpecho_server_tirtos Example
  8. 7 Enet_udpecho_server_tirtos Example Overview
    1. 7.1 Run the enet_udpecho_server_tirtos Example
  9. 8 Enet_httpServer_tirtos Example Overview
    1. 8.1 Configure NDK for HTTP Application
    2. 8.2 Embedded File System (EFS) Operation
    3. 8.3 Adding HTTP Server Content
    4. 8.4 Declaring HTML Files to EFS
    5. 8.5 Writing CGI Functions
    6. 8.6 Run the enet_httpServer_tirtos Example
  10. 9 Enet_dns_tirtos Example Overview
    1. 9.1 How to Configure NDK for DNS
    2. 9.2 How to View the DNS Traffic on Wireshark
    3. 9.3 Run the enet_dns_tirtos Example
  11. 10Enet_sntp_tirtos Example Overview
    1. 10.1 Run the enet_dns_tirtos Example
  12. 11Enet_tcpecho_client_tirtos Example Overview
    1. 11.1 Configure the Server IP Address
    2. 11.2 Configure the SocketTest Server
    3. 11.3 Run the enet_tcpecho_client_tirtos Example
  13. 12Enet_udpecho_client_tirtos Example Overview
    1. 12.1 Run the enet_udpecho_client_tirtos Example
  14. 13Enet_httpget_tirtos Example Overview
    1. 13.1 How to Configure NDK for HTTP GET Example
    2. 13.2 Run the enet_httpget_tirtos Example
  15. 14References

7.1 Run the enet_udpecho_server_tirtos Example

The SocketTest tool will act as the client running on the PC. Make sure the PC is connected to the same network as the EK-TM4C1294XL with the same subnet mask.

Follow the steps shown in Figure 7-1 to setup the SocketTest:

  1. Go to the “Udp” tab.
  2. Enter the PC’s IP address and the port number 23 and press the “Start Listening” button. The server IP address should be the address of the PC running SocketTest. To find out the PC’s IP address in your network, you can use the Windows’ ipconfig command. Bring up a Windows command window and at the prompt type “ipconfig” and you will see the IP address assigned to your PC. Note in SocketTest, the Server address field will be the address of the PC regardless if the PC is the actual server or client. SocketTest just listens for any incoming data at the specified address.
  3. Enter the MCU’s IP address in the “IP Address for Client”. The IP address assigned to the MCU is shown in the CCS console window.
  4. Go to the “Message” field and type in some messages and then hit the “Send” button.
  5. Observe the conversation field in SocketTest.
GUID-20210329-CA0I-MJ8Q-CF16-M0BSCDZRF1M5-low.jpgFigure 7-1 Enet_udpecho_server_tirtos Output

Examine the Wireshark capture for the UDP traffic in Figure 7-2.

  1. The frame number 15351 is the first echoed message from the server (IP Address 192.168.254.92) to the client (IP Address 192.168.254.69).
  2. The length is 49 bytes which is not surprising if we were to count the message “This is a UDP Echo Server example for TI-RTOS NDK\n\r” manually. Also, look at the port numbers. The port number on the PC (the client) is 60766 while the port number on the MCU (the server) is 23. The 60766 is different from what was entered in Figure 7-2. The reason is that the client never explicitly chooses a UDP port to bind to. The stack on the client side simply picks a current-available UDP port to implicitly bind the sending UDP socket to and this port may be different each time. However, the NDK stack running on the MCU is configured to bind to port 23.
GUID-20210329-CA0I-TPHG-J2CW-4B7S18WP2LZF-low.jpgFigure 7-2 Server to Client Wireshark Capture for Enet_udpecho_server_tirtos