This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TM4C129ENCPDT: tcpEcho - TI RTOS

Part Number: TM4C129ENCPDT

Hello,

I am struggling to get the tcpEcho_EK_TM4C129EXL_TI example to work out of the box. I am using Tftpd64 to create a DHCP server on my Windows 11 PC. This works and the development kit is assigned the IP address of 192.68.56.2.

Now, here is where things stop working. I use the Windows command prompt to run the tcpSendReceive executable. The command I give is: tcpSendReceive 192.168.56.2 1000 1 -s100. And, this times out every time.

(As a side note, I do have a distribution of Ubuntu on a Virtual Box, and have tried to run this through Linux, but this also does not work).

Can someone please recommend a setup that can test out this example? I would love to use this example as the starting point for my development project, but have to validate its functionality first.

Thank you!

  • Hi,

      The example should work out of box. I just tried it. Please see below. My LaunchPad is assigned 192.168.254.201 as the IP address.

    I use .\tcpSendReceive.exe 192.168.254.201 1000 1 -s100 and below is the result. 

    I also use a utility program called Hercules to 1. ping the device, 2. connect to the server and 3. send a message 'This is a TEST for tcpEcho demo' to the server and get echo back. 

    - I will suggest you first try pinging the device.

    - Next check if there is some network issue on your end (e.g. firewall or hosts not on the same subnet).

    - Perhaps try on a different network.

    - Use the Wireshark to trace the traffic between the two hosts.

  • Charles,

    Thank you for the troubleshooting steps you provided. So, I am using a Dell PC with a docking station. The PC does not have any Ethernet connections natively, but the docking station does, and there's a USB C connection between the two. In summary, the PC's ethernet controller and the dock's ethernet controller were on different subnets.

    I forced the PC's IP address to a static value and made the sub-mask 255.255.0.0 (in case the dock's IP address went beyond the last byte). Then I used Tftpd64 to create a DHCP server and set the IP address pool to occur within the sub-net range of my PC's static IP address. Once the DHCP address was assigned, I was able to ping and use the tcpSendReceive from the command prompt!

    Then, I used Hercules to send text. What a great little tool. Thank you for recommending this!