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.
Greetings,
I am trying to compile the demos and examples from the MCSDK under Linux, but the build fails because of dependency problems. It appears that the RTSC packages installed by MCSDK are not being discovered automatically by CCS, therefore the compiles fail. I am running Ubuntu 10.04 LTS. Attached are some screen shots illustrating my problem.
The compile errors are attributed to missing RTSC products, but reintalling MCSDK does not resolve them. Under the RTSC Properties tab, I can see that the NDK, MCSDK, IMGLIB and PDK repositories are unresolved despite being intalled in the same root directory as CCSv5 (/usr/local/CCSv5).
Occasionally, CCSv5 does automatically detect the tools and the applications do compile (I've tried a several installations on different machines running Ubuntu 10.04). However, it is unclear what conditions must be present for this auto-detection to occur. Furthermore, I had everything working on a machine one day and the following week it appears to have lost the tools it had previously found.
From this post (http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/134571.aspx), I am aware that CCSv5.1 has problems with automatic package detection, but the work-around (i.e., temporarily relocate the eclipse subdirectory within the package) has only worked for me once and it may have been a fluke. I have also tried to explicitly add the search path for each individual package to the search path, but they are still not found.
I would like to know if there are any alternative solutions that would allow me to consistently load RTSC packages into CCSv5 so that our team can continue with their C6678 development.
Thank you.
Nick.
I thought this issue was introduced in CCS 5.1M8. So M7 should've worked ok but the other discussions refer to the Windows version so I'm not sure about the Linux version. Please see these related threads:
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/137767.aspx
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/136923/496306.aspx#496306
It should be fixed in the final 5.1 release which is now available for download:
http://processors.wiki.ti.com/index.php/Download_CCS#Code_Composer_Studio_Version_5_Downloads