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.

UDP same code work on ek-TM1294 but seldom on DK-TM129x

 Beta test result of TIVAWare and TIRTOS examples build up on Linux CCS ver 6.0.000190, target EK-TM4c1294 and DK-TM4C129x.

 Importing TIVAWARE example .project miss all code link, after import can be temporary fixed with a handy cut and paste from original .project , from after natures to variable list entire linked Resources marked in yellow.

    </natures>
    <linkedResources> missing from here to end
..................................

    </linkedResources> 
    <variableList>

 I checked a lot of examples and network where too much complex to be usable.

 All example after patch work on both board:

 QS-Weather, QS-RGB, FreeRTOS demo, Enet-LWIP, no usable simple TCP nor ready UDP where in place.

 I checked TIRTOS, here the scenario is better and call are simple and unix like, again I imported UDP demo, an issue exist on import and task is not set so it never run on imported example project.

 Adding Task var and initialization it started fine on EK-TM1294 and it worked like a charm.

 Windows client work quite good ignoring deallocation fault on exit, Linux client need to be compiled again, after a lot of coredump I noticed on exit it try deallocate from HEAP a buffer never allocated, just assign a null to pointer and test if not null cured this annoying bug.

 Client is now running fine on both Linux and windows box, EK-TM1294 code work ever if paused from debugger or on board just after power on or reset.

 On DK-TM129x it work very seldom, on debug few time get DHCP value and network is hiccup running no difference from reset power cycle  or restart or reloading code....

 Other network example work but not this so simple UDP echo, code is the same and swapping board just work or not ..

 LCD on DK-TM129x I was pretty sure it was a controllerless, I see it is connected to LCD interface and just port driven. Why not include a bare LCD without controller just to demonstrate internal Hardware LCD?

 Network cable used to test both board is the same, same router same code. USB cable are of good quality and short, the one connecting the DK is bigger and shortest, no change whatever on DK or <EK

 Prefetch bug is applied to both example but I suspect another silicon errata.