Port to CCS10.1 and C2000Ware3.03

[kentavv]

Release and Debug configurations tested for ELS code by cloning clean repository, switching to branch, loading up CCS, building, loading, and debugging. Testjigs unchanged; I didn't know how they were used. The local copy of C2000Ware was removed and the currently installed is referenced by links. Built against C2000Ware 3.03 installed into C:\Ti. If a different version is used or the installation location is different, update the two C2000Ware variables in the build settings for the release and debug configurations. Default binary format remains COFF; ELF binaries can be built however, a bug in C2000Ware 3.03 would requires a small change to f28004x_usdelay.asm, requiring a local copy of this file or the original to be modified.

[bobek]

@kentavv thank you very much for you effort, I am trying to compile ELS with a newer version of the C2kW and studio. Can you please describe how you have handled the "upgrade", is it all manual work? I wonder if so much manual work is going to be needed for every release or if the project structure should be different.

I am new to C2000 development and currently really struggle with getting ELS to even compile... I will probably try Windows VM just for sanity check (I am on Linux).

[kentavv]

@bobek The code imported pretty easily into the newer CCS. I then cleaned up compile errors, enabled all compiler warnings, and cleaned up warnings. Then replaced the C2kW files in the repository with links to the installed C2kW. Then the project references the TI installed C2kW files that their installer maintains and reduces potential for license conflicts. Before flashing, you'll need to update the linkage files, which have prefixes like *.cmd. I synced these with TI's latest which seemed to fix memory allocation problems. I don't remember if for the CCS update I needed to change compilation settings for the base code, but did for my Nextion version to enable library features. These are all the details I remember. To learn more, pull the main release, the release my changes are relative to, and my changes. Then using a three-way compare tool such as Beyond Compare. If you do this work, please consider creating a new pull request to save someone else the effort.