CCS: [E1000] Cannot open command file '\\2116014': No such file or directory

Hello,
Did you just update your Windows 10 machine to the latest patches or did you move from an older Windows major version (Windows 7 to 10 update)?

What are value of both your TEMP and TMP environment variables?

Thanks
ki

Hi,
We moved form Windows 7 to windows 10 and since then we are getting compilation errors.

My TEMP and TMP are in this format :
C:\Users\username\AppData\Local\Temp

what is "username" for your account? Is it actually "username"?

My username is "hragrawa".
So under user variables for hragrawa, the TEMP and TMP are :
C:\Users\hragrawa\AppData\Local\Temp

And under system variables, TEMP and TMP are :
C:\WINDOWS\TEMP

Thanks. Both the path and your username should not be causing issues.

I'm not sure what else could be causing the issue. One thing I would like to suggest is to install a later version of CCS in a clean new directory. You can have multiple versions of CCS installed on the same PC so I would leave your 6.1.0 installation alone and do a new full install of a later CCS version in another directory. Please note that CCSv6.1.3 is the oldest version to start supporting Windows 10 so please choose at least that version (but preferably newer than that).

I see that the latest version is 9.0.1. Which one would you recommend to download? Would 9.0.1 be a good fir or should I stick to the 6 series?

Thanks!
Heena

We would love for you to move to the latest CCS version. What is best for you would depend on if there is some specific reason why you need to stick to some older version (some companies have it in the SW process to not change tool versions in the middle of SW development). Also note that the old XDS510 USB debug probes are no longer supported with CCSv9.x (CCSv8.3.1 is the last version to support it). Note that it is possible to use the same version of the build tools (compiler, linker, etc) with CCSv.9.x that you were using with CCSv6

Hi Heena,

Were you able to try out CCSv9.0.1?

Thanks

ki

Hi Ki,

Our project requires us to use CCSv6.1.0 with "c6000_7.4.14" and "ti-cgt-arm_5.2.4" compilers on MS Windows 10.

I am receiving this above error when I am trying to integrate code composer 6 with our Bamboo Atlassian environment. Everything seemed to be working fine when we were on Windows 7 but the Windows 10 update seems to have caused some issues.

Having said that, if we try to use this combination (CCSv6.1.0 with "c6000_7.4.14" and "ti-cgt-arm_5.2.4" compilers on MS Windows 10) directly through code composer interface, we are able to build successfully.

From the compilation failure logs, it seems that code composer is creating a bunch of temp files and then is not able to find them (see snapshot). At this point, I am completely stuck and not sure why this is happening. We have tried uninstalling and reinstalling CCSV6 but that dint seem to help. I am kind of looking for an understanding on these temp files and how/where they are getting created during compilation. NO luck yet. Any help is appreciated.

Heena Agrawal said:

Our project requires us to use CCSv6.1.0 with "c6000_7.4.14" and "ti-cgt-arm_5.2.4" compilers on MS Windows 10.

Would it be possible to at least move to CCSv6.1.3? It is a minor revision change - mostly just bug fixes. It should have minimal impact and you can use the same versions of the compilers.

CCSv6.1.0 is not officially supported on Windows 10. At the very least, I would like to have you using a CCS version that supports your OS.