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.

TIDA-00203: How to get Ethernet data from TIDA-00203

Part Number: TIDA-00203

Dear Sir,

I am using Can to Ethernet TIDA-00203 rev.E1 board. i have successfully compile source code and burn which  has download from

TI website into microcontroller. I have successfully  ping the TIDA-00203 broad by using default IP (169.254.254.255) as well as any other

Static IP(ex-172.24.248.78).but I am not getting  Ethernet data from board on Wires hark application whereas I have received can data successfully in TIDA-00203 .  

  • Hello Bhupendra,

    I am a little confused with the question.

    As I read your questions you can see that you get the Ethernet data successfully from PC to the PCB.

    If ping gives you a response the Ethernet data is transferred successfully in both directions.

    But you do not see a response in wireshark from the TIDA-00203 during normal operation or how do I understand the question?

    Below I have tried to answer per my understanding of your issue.

    Have you turned off your anti-virus software during the wireshark test?(here do not have the PC online during these tests).

    I have seen issues when using firewall and anti-virus software while running wireshark, this can have the effect that the protection software filters out the Ethernet packets before wireshark captures them

    The examples mentioned now are using LwIP stack server, and you'll find code for these in TivaWare under examples/boards/dk-tm4c129x. Look for enet_lwip, enet_uip and enet_io.

    If you are acting as a client rather than a server (all the examples I mention above are web servers), you can look at the qs-weather application which sends requests to a remote server to retrieve weather information using lwIP. One very important thing to remember (and which qs-weather currently doesn't do correctly! Bug raised) when making client requests and using lwIP is that lwIP APIs can only be called from the Ethernet interrupt context so you can't just put lwIP API calls into your main function and expect things to work. They will probably work for a while then you'll hit a race condition that corrupts a control block and things will fall over. Beware!

    This is mentioned in the post, link.

    Fixing this issue can be done as described in the post.

  • hello 

    i am not getting can to Ethernet converted data on wire shark  application whereas i have received correct can  data.

    i am acting as a server.