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.

Error updating compilers on CCS for Mac



Hi,

While trying to update the MSP and ARM compilers using "Install New Software" on the latest CCS for Mac, I receive these errors:

An error occurred while configuring the installed items

session context was:(profile=epp.package.cpp, phase=org.eclipse.equinox.internal.p2.engine.phases.Configure, operand=null --> [R]com.ti.cgt.msp430.16.mac.feature.group 16.3.0, action=org.eclipse.equinox.internal.p2.touchpoint.natives.actions.CopyAction).

I/O Error while copying /Applications/ti/ccsv6/eclipse/downloads/com.ti.cgt.msp430.16.mac.properties - see details.

Target: Path /Applications/ti/ccsv6/eclipse/../../../../install_info could not be created

While file permissions seem OK to me, the target path looks fishy. It seems to be trying to put "install_info" in the root directory of the hard drive! Certainly not advisable.

  • Anup,

    The reason you are seeing this error is the version of Eclipse used in CCSv6.1.2 has a different folder tree structure than the version of Eclipse used and CCSv6.1.3. This update has been created to be compatible with CCSV6.1.3 only.

    If you do not require the changes in the update immediately, my recommendation would be to wait for the CCSv6.1.3 release and install it. The new version should out in approximately 1 week and would be the best approach as we would prefer developers to migrate off the OS X beta version. If you do require the changes in this update sooner, we can look at other options.
  • Andy,

    Thanks for the clarification. We should be able to wait a week.

    But, what we have also observed is that importing a project based on a MSP430 compiler with the new numbering scheme into CCS for Mac fails. Normally, we would get a warning that the particular version isn't installed, and it would instead use the latest one that is installed. Perhaps CCS for Mac isn't configured to calculate this kind of fallback because the "major" version number is significantly higher?
  • Anup Rajput said:
    But, what we have also observed is that importing a project based on a MSP430 compiler with the new numbering scheme into CCS for Mac fails. Normally, we would get a warning that the particular version isn't installed, and it would instead use the latest one that is installed. Perhaps CCS for Mac isn't configured to calculate this kind of fallback because the "major" version number is significantly higher?

    Anup,

    Yes in this case the project import fails because the CCS version you are using does not have the "built-in model" for compiler version 15.x.x. This will also be fixed in CCS 6.1.3, so when the final release is out in the next week or so, you should be able to create and import projects with the new compiler versions.