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.

Network game between PC and DK-TM4C129X Connected Development Kit

Hello,

I am a final year student doing a bachelor of electrical engineering, majoring in control systems. This is my first time posting on this forum, so hi.

Context:

I have a project for one of my subjects, we must build a game which can have up to 12 players simultaneously playing. The game is to be played simultaneously, over either a PC or a Tiva C series DK-TM4C129X Connected Development Kit. I am using python to develop the PC game, and CCSv6 to develop the game on the Tiva.

My understanding is that we must use a udp protocol for networking and TI-RTOS operating system for the implementation of the game on the embedded processor.

Question:

Can anyone suggest where I should start? I would like to build my project from the ground up using only the necessary resources.

  • Hello OMG,

    It is not necessary to have TI RTOS. The bare metal examples of enet_lwip or enet_uip can also support UDP packets without the requirement to have TI RTOS

    Regards
    Amit
  • Hi Amit, thank you for taking the time to answer me. TI RTOS implementation is a requirement of the project.
  • Hello OMG,

    Then you can use the TI RTOS UDP implementation to jump start the example. However do note that any query regarding to specifics of TI RTOS would be redirected to the TI RTOS Forum. There would be some forum material on TM4C for UDP implementation though that you can use via the Search on the top of the fourm

    Regards
    Amit
  • OMG Uleh said:
    TI RTOS implementation is a requirement of the project.

    So - may we ask if the individual(s) drafting project, "requirements" is/are as skilled, experienced & "TM4C savvy" as this vendor's Amit?   (we think not!)

    Rejecting Amit's considered opinon/recommendation rarely proves wise - especially when the, "objective of the requirement" is unstated - thus unknown.

    Have we not learned (already) that your project now has TWO masters?   (RTOS & TM4C)   KISS argues against such complexity - especially when (promised) benefits are not quickly evident - and challenges may "ride" (unclearly) between or within each master.   What then?

    Failed projects/products - due to overly-ambitious/inadequately considered "requirements" - can be expected to cause substantial, "pain/suffering."   When poorly planned/conceived such "requirements" most always lead to the misuse of time/effort/funds/resources.   They thus prove extremely critical.

    It would be of great interest to learn just how this "requirement" was determined - and the level of TM4C familiarity/experience/capability of the requirement's draft team.

    At the minimum - vendor Amit's comment should be presented to the project's "requirement creator(s)" as a high-value "feedback."   Requirements "cast in stone" and/or those not "welcoming & reacting" to such valued guidance - are unlikely to deliver maximum results in a timely fashion...