The default tool chain is tms470, which produces a .out file that is not a Linux executable. Even when you add the executable attribute to the .out file, the program still doesn't run.
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.
The default tool chain is tms470, which produces a .out file that is not a Linux executable. Even when you add the executable attribute to the .out file, the program still doesn't run.
Neil,
The project must be created using GCC. Check the page below:
http://processors.wiki.ti.com/index.php/GCC_-_Create_a_project
Although the page talks about CCSv4, the concepts for CCSv5 are the same.
Hope this helps,
Rafael
Rafael:
The link you provided sort of answered my question. One comment and one question:
1) In CCS5.0.2 when you add a CCS project, you can’t add an Executable. Instead, you chose from a list of ARM, C2000, C6000. Only when I added a regular Eclipse-like project was I able to get the gnu tool chain.
2) I had to give the full path to the CodeSourcery gcc, even after I updated the PATH “Build Variable” and likewise, where to I had to hard code OUTPUT_PREFIX build variable in the linker command line so that I can direct the linker to output the executable into the appropriate directory. How do you update the PATH and OUTPUT_PREFIX build environment variables?
Neil
Neil,
Neil Walker said:1) In CCS5.0.2 when you add a CCS project, you can’t add an Executable. Instead, you chose from a list of ARM, C2000, C6000. Only when I added a regular Eclipse-like project was I able to get the gnu tool chain.
Yes, you are correct. CCS Projects use TI tools (compiler, assembler, linker). To use GCC you must open a standard Eclipse managed project.
2) I had to give the full path to the CodeSourcery gcc, even after I updated the PATH “Build Variable” and likewise, where to I had to hard code OUTPUT_PREFIX build variable in the linker command line so that I can direct the linker to output the executable into the appropriate directory. How do you update the PATH and OUTPUT_PREFIX build environment variables?
With regards to the PATH to the Codesourcery tools, whenever you update a system environment variable the changes do not take effect for the currently opened applications. You must restart each application where the changes are required. This is standard Windows operation.
The OUTPUT_PREFIX is usually set in the tab Build Artifact of the C/C++ Build --> Settings. Check if there is one there.
Hope this helps,
Rafael