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.

TM4C1292NCPDT: TM4C1292NCPDT: Unable to validate enet_tcpecho_server example code on Launchpad

Part Number: TM4C1292NCPDT

Hi,

I am working on validation of PHY interface with microcontroller using enet_tcpecho_server example code with launchpad.

I am able to get IP address through tera term but flailed in socket test, also not able to connect target using ROV.

Also not getting IP address on Wireshark as mentioned in output of tera term.

Below image for your reference.

Please share your feedback to validate this code on launchpad.

Thanks,

Kiran

  • Hi,

      Today is US public holiday. Please expect delayed response. As I have told you in the other thread, you have problem with the DHCP server. You are not getting DHCP address. You need to check your network. 

  • Hi Charles,

    Thanks for your response!!

    As per your suggestion, i created a sperate thread. I will recheck the network.

    Thanks,

    Kiranjit 

  • Your screenshot is a bit different from last time where you showed 16.254.35.17.  With 192.168.2.119, should be fine. Check if your PC and MCU are on the same subnet. Are they connected to a switch?

  • Hi Charles,

    Check if your PC and MCU are on the same subnet. 

    >> Both are in same subnet.

    Are they connected to a switch?

    >> Yes 

    We are getting traffic from PC rather than EV Board. 

    We also checked on Advanced port scanner for open port status. It was showing that there is no open port.

    Please share your feedbacks.

    Thanks,

    Kiranjit 

  • Setup as below:Used crossed cable for EV board 

  • Hi, 

    Are they connected to a switch?

    >> Yes 

    Setup as below:Used crossed cable for EV board

      Your above two statements are confusing. Earlier, you said both PC and the LaunchPad are connected to a switch. Now you said you use crossed cable for LaunchPad. Which one is the setup? I will suggest you start with a switch so the example can get its IP address from the DHCP server. If both PC and LaunchPad board are connected to the switch then why do you use a crossover Ethernet cable? You should use a regular straight-through cable if you are connecting the LaunchPad board to the switch. You only use crossover cable when you are connecting LaunchPad to PC directly. 

    Another thing I see is that you change the MAC address. LaunchPad is preprogrammed with a MAC OUI address that indicates for TI. The new MAC address you program should be fine if it is a valid MAC address. It is just an observation from my side.  

      As I mentioned, I have run this example many times. It should work unless it is a problem on your network. Can you try a different TivaWare example such as enet_lwip? This is a simple web server. Can you get it to work? All of these examples should work out of the box. If enet_lwip does not work either, then it is a problem on your network side. I will suggest you try a different network. See if you can get the example to bring up on a network like your home network. This way you you can compare the results.  

  • Hi Charles,

    Can you try a different TivaWare example such as enet_lwip? This is a simple web server. Can you get it to work? All of these examples should work out of the box

    I tried with straight cable as well,the socket test connection is not built.PC and MCU are on same subnet. I changed the MAC address too.

    I tried to create new 'Inbound Rule' and 'Outbound Rule' in Windows Defender Firewall for port 23 as well.

    Can you try a different TivaWare example such as enet_lwip? This is a simple web server. Can you get it to work? All of these examples should work out of the box

    I'm unable to connect to the ip address on the browser in enet_lwip example as well.

    Any port enable settings needed on the switch side? 

    I need to get it working on my office network only. 

    Can you suggest of anything else to be taken care of?

    Best Regards,

    Kiranjit

  • I'm unable to connect to the ip address on the browser in enet_lwip example as well.

    The enet_lwip example has been around for so many years. It should work out of the box. If you are unable to get an IP address then you need to check iwith your IT department if there is a DHCP server on your network. 

    I have not seen any wireshark capture from you. The wireshark capture should show that the client first send out a 'Discover' packet. The DHCP server is supposed to return a 'Offer' packet. The client will then send 'Request' and finally the server will return 'Acknowledge'. You need to do port mirroring on your switch in order to see all four packets exchange. Without port mirroring, you might only see 'Discover' and 'Request' if it works. Most likely in your case, you only see 'Discover' and the server is not responding. If this is the case, you need to check with your IT department. I don't know how to help you. Why don't you first show your wireshark capture and also the terminal window on the client side. It is supposed to show the DHCP address acquired if it works. 

    Any port enable settings needed on the switch side? 

    Not I'm aware of. Normally you just plug in the cables to the switch. I normally just connect both PC and MCU to the switch and the switch is connected to the local network. 

    I need to get it working on my office network only. 

    I understand it needs to work in your office network. But I strongly suggest you try other network first. If it works on your home network then you know it is something in your office network that prevents from working. You can then troubleshoot by comparing the wireshark captures and take it to your IT department on how to configure the switch and network. Perhaps there is some firewall or something that is blocking the traffic. 

  • Hi Charles,

    Please check the wireshark traffic for the TI launchpad before and after request from socket test utility.

    Best Regards,

    Kiranjit

  • Hi,

      Your wireshark seems to show that you have the DHCP address acquired. Can you provide the terminal window output? See below. I just run the same example and I don't see an issue. After DHCP address is acquired, it is displayed on the terminal window. I then type that IP address on SocketTest. It immediately connects to the server. The client sends a test message 'This is just a test'. The server echoes back the same but invert the letter case. 

    This is my wireshark capture. If you look at frame 147, the message 'This is just a test' is sent by the client 192.168.254.79 (my PC) to 192.168.254.200 (my LaunchPad).

      Can you run enet_lwip and capture the wireshark and the terminal window output? enet_lwip does not rely on SocketTest. This is to make sure it is not some issue related to your SocketTest. As I mentioned, if you fail to run enet_lwip successfully, it is your network problem and I don't know how to solve it. I already suggested you try out other network to determine if it is a office network problem. It is up to you.

  • Hi Charles,

    Thanks for your response!!

    I will try your suggested steps once I reach office.

    Below are some screenshots of Wireshark and terminal window which I tried on my Home WIFI network. 

    As it is running perfectly on your side so please share your comments and feedbacks to resolve this network related issue.

    Thanks,

    Kiranjit 

  • Hi Charles,

    It's up and running now. Maybe there was some network issue in the office.

    Wireshark capture for enet_lwip example

    Wireshark capture for enet_tcpecho_server example

    Best Regards,

    Kiranjit

  • Thanks a lot for your help

  • Glad your problem is resolved. Can you share what you change on your network to make it work now? It may help other people who runs into the same issue.