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.

Ethernet on Tiva EK-TM4C1294XL

Other Parts Discussed in Thread: EK-TM4C1294XL

Hello,

I am having trouble having 2  Tiva C Series EK-TM4C1294XL launchpads communicate with each other.  The 2 are connected by an ethernet hub.  Can anyone help?

  • Hello Gerardo,

    Do you have a DHCP server on the network to assign an IP address to the application layer?

    Regards
    Amit
  • Yes, in fact, I am using the Tiva EK-TM4C1294 to attempt to communicate to a LinkSys router. I am only using the ethernet port(s) to communicate to the router. I just want to make clear that I don't need the internet for this project only the communication to the router with an ethernet cable using the Tiva.

    Thanks
  • Hello Gerardo,

    You do not need Internet but you need a Server so that it can assign an IP address to each of the device which would be required by the LwIP or uIP Stack running on top of Ethernet. On the other hand if you want to get away from all TCP/IP, then it would be a bare metal Ethernet (no example exist as of now in TivaWare)

    Regards
    Amit
  • How can I go about setting up the server to make the connection with LwIP or uIP through ethernet?

    Thanks

  • Hello Gerardo,

    Were you able to get the qs_iot example working on the n/w?

    Regards
    Amit
  • No, I still need to go through the example and run it on the Tiva.

    Thanks

  • Hello Gerardo

    I would suggest evaluating the examples.

    Regards
    Amit
  • I am having trouble setting the tiva online through the exosite portal. It says that my device is offline.

    Thanks

  • Hello Gerardo,

    Does your network have a proxy server? You may want to check the n/w admin. If yes, then please set the proxy address and port using setproxy command line option in the console window.

    Regards
    Amit
  • I was able to connect to it online just now. How can I access the virtual COM port so that I can see the program output?

    Thanks
  • Alright, so I successfully finished the qs_iot example. Should I attempt to follow the qs_iot example to establish a server, therefore leading to the connection between the Tiva and the personal router I am using?
  • Hello Gerardo,

    The qs_iot is a client example with exosite as the server. What you now need is a client to client communication. I am not sure if the TivaWare examples do the same. However a bit of searching landed me to a page that may interest you

    stackoverflow.com/.../how-can-i-send-a-simple-http-request-with-a-lwip-stack

    Regards
    Amit
  • Hi Gerardo,
    Perhaps try setting ICMP enable (1) in (lwipopts.h) re-compile, re-flash both launch pads. Then try ping from a PC or router GUI each launch pad and know for sure of bidirectional Ethernet COMS to personal router. Make sure TCP (echo) port 7 is not disabled on router or ICMP ping may not respond.

    {Should I attempt to follow the qs_iot example to establish a server?}

    There is a http basic server example but suspect might require a basic understanding of LWIP.
    TivaWare_C_Series-2.1.0.12573\examples\boards\ek-tm4c1294xl\enet_io (readme file)

    TivaWare_C_Series-2.1.0.12573\third_party\lwip-1.4.1\apps\httpserver_raw
  • Enable DHCP on your Linksys router and set up a network DHCP address pool 10.1.10.10 - 10.1.10.20 (10 IP's) and make 10.1.10.1 the gateway address.
  • Hello,

    I need to make the Tiva EK-TM4C1294 into a server application to communicate through ethernet. I have worked on the qs_iot example but it uses the internet (Exosite as server). That is what I need but I need the Tiva to be a sever to communicate to a client computer and other clients. Are there any suggestions as to what can help me make the Tiva a server?
  • You would first need to define the word "server" just a little bit further! I don't mean to be rude, but if you don't know what I mean by that, you are out of your league - though that can be fixed with "homework"! In any case, the forum can't help you much with such a vague request.

  • The server Tiva simply needs to receive information from clients as well as send information to clients. I will be using other Tivas and a computer as clients. I'm having problems connecting to them. For your information, I don't need to connect to the internet. I am using a switch or router to make the communication.
  • A-ha! I see a keyword: "simply"! Yes - network communication is simple - if you know how to do it. And I don't mean how to do it with Tivas specifically - I'm speaking generally. You provided zero detail on what your "server" means in terms of protocols, data formats etc etc...
  • I'm using TCP protocols. I'm not on the data formats aspect yet. I am currently searching for a way that will let me connect to the clients.
  • Well, it's a start. But I must say I'm surprised that you have already locked down your choice of protocol when you don't even know what you will be transferring.

    You will want to get to the data format aspect quite soon - when you do so, you might even realize that TCP is not necessarily what you want. If it is data logging, acting on specific events etc, then perhaps. For real-time control or continuously relaying status information, TCP is overkill - you'll fare much better - and easier - with UDP. But that depends on the data, of course.
    My advice is to think it through - perhaps even simulate the Tiva with a "proper" computer - the client devices won't know the difference.

    These are things that are IMO outside the scope of this forum, but it is a good discussion to have here (every now and then). Not everyone realizes that what is being marketed almost as plug-and-play is really far, far from it. The most unpleasant surprise is that wandering outside the realm of vendor-provided examples actually requires thought & hard work!

    TL;DR: Map out your data transfer requirements first. Then decide what's the best way to transfer them (protocols). Then look at the available implementations.

    One more thing: You mention you'll be using "a switch or router" - you do know that using one over the other is fundamentally different from a network protocol point of view? (using a router limits your choice of protocols).