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.
Tool/software: Code Composer Studio
Based on the initial responses we are now using Code Composer 6.1.3 with following compilers c6000_7.4.14 and ti-cgt-arm_5.2.4 on windows 10., but still we are receiving all the errors mentioned earlier and in the snapshot. Any help is greatly appreciated.
I'm not sure about the cause of the problem.
It might be the same one as in this forum thread. One way to see is to upgrade the C6000 compiler from version 7.4.14 to version 7.4.22. If that fixes the problem, then you need to upgrade the ARM compiler too. However, there is no version 5.2.x of the ARM compiler with the fix. You would have to upgrade to something much later. That being the case, I recommend you upgrade all the way to the latest long term support release, which at this time is version 18.12.3.LTS.
If upgrading the compiler does not help ... Use the compiler option --temp_directory=directory_path to have the compiler use that directory for temporary files. If that helps, then consider changing the environment variable TMP or TEMP to that directory.
Thanks and regards,
-George
Hi George,
I also wanted to mention that when I run our builds directly through code composer 6.1.3 interface with c6000_7.4.14 and ti-cgt-arm_5.2.4 compilers on widnows 10, then everything works perfectly.
In this case, we are sending build commands to code composer through the ALM Bamboo interface (Continuous integration plan). This is mostly set up using python commands and Tortoise SVN directory. Here our builds are failing with the above error. Do you have any suggestions for that?
Thank you!
I don't really understand this part ...
Heena Agrawal said:sending build commands to code composer through the ALM Bamboo interface (Continuous integration plan). This is mostly set up using python commands and Tortoise SVN directory.
I just take this to mean several layers of software are involved in performing the build.
Did you try the option --temp_directory? Did that help?
Thanks and regards,
-George
Hi George,
As per your suggestion, I upgraded Code composer and compilers to the latest version.
Our user environment variables are set to :
TEMP = %USERPROFILE%\AppData\Local\Temp (which is C:\Users\<username>\AppData\Local\Temp )
TMP = %USERPROFILE%\AppData\Local\Temp
Our system environment vraiables are set to :
TEMP = %SystemRoot%\TEMP (which is C:\WINDOWS\TEMP)
TMP = %SystemRoot%\TEMP
After all this, we are still getting the attached error. Also, the link that you mentioned seems to have similar issue but I did not quite understand the resolution. Can you please explain that?
Can you please explain how to add "--temp_directory=directory_path" in the existing project through command line?
so far I have this -
%CCS_DIR%/eclipsec -noSplash -data %WORKSPACE_DIR% -application com.ti.ccstudio.apps.projectCreate -ccs.name NewProject -ccs.device com.ti.ccstudio.deviceModel.C6000.GenericC64xxDevice -ccs.setCompilerOptions "--temp_directory=directory_path" -ccs.overwrite (keep)
But this creates a new folder completely. How can i add this "--temp_directory=directory_path" to the existing .cproject file through command line? that file already has some other include options too.
Another issue is that even though we have upgraded our system to Code Composer Studio 9, we are still required to use compilers "c6000_7.4.14" and "ti-cgt-arm_5.2.4". Is this issue not resolvable without updating the compilers?
Thank you for upgrading CCS and the compiler. I'm sorry it didn't help.
The option --temp_directory is for the compiler, not the command line invocation of CCS. Given what I know now, I can tell it won't help. So, please ignore that suggestion.
I'll contact you privately to gather more information.
Thanks and regards,
-George
The root cause turned out to be a network issue in the customer's system.
Thanks and regards,
-George