Hello,
we found several discussions how to make the TCP protocol running on Keystone devices. A lot of different patches and workarounds are published and it's difficult to assemble the common sense of all posts.
http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/271367.aspx
http://e2e.ti.com/support/embedded/tirtos/f/355/p/253488/891759.aspx
http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/214649/762847.aspx
http://e2e.ti.com/support/embedded/tirtos/f/355/t/253237.aspx
http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/178524.aspx
http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/278508/971884.aspx#971884
http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/243353/999492.aspx
After reading this posts there is no doubt, that TCP is not working out-of-the-box for Keystone devices and TI source-code has to be patched as well as the TI sample-code the user bases his application on.
Is there an official procedure from TI describing, how to make TCP working on Keystone devices ? Like a list of files to be patched in the C:\ti folder and in the code-samples ? Maybe with a list of the settings to be tuned (task-priorities, buffer-sizes) and where to enter this settings ?
Regards,
Roelof