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.

SetupInCCSnRegistry.exe Fatal Error when manually executed

Hello,

There are some question on compiler version between CCS 5.5 and 6.1.

First, latest compilers are not shown in software updates for V5.5. For example, V5.5 upgrades to ARM 5.1.11 but not aware of the 5.2.4 which is shown in update for V6. Similarly, V5.5 sees C6000 V7.4.4 in update but not 7.4.14 as in V6.1.

Q: Why latest compilers are not detected by older CCS? As will be described in next question, “SetupInCCSnRegistry.exe” can actually be called to manually add new compiler to CCS5.5. So is this [update policy] choice made mainly because the CCS team sees CCS6 as more stable and runs more test of compilers mainly on V6?

 

The SetupInCCSnRegistry.exe executes with

C:\ti\ccsv5\tools\compiler\msp430_4.3.3>SetupInCCSnRegistry.exe

Please specify the tool version number as the first argument to this script.

And if executed with a number string like “4.3.3”:

C:\ti\ccsv5\tools\compiler\msp430_4.3.3>SetupInCCSnRegistry.exe 4.3.3

Preparing to install in C:/ti/ccsv5/tools/compiler/msp430_4.3.3

FATAL ERROR: failed to open C:/ti/ccsv5/tools/compiler/msp430_4.3.3\compiler.reg: No such file or directory

 

Although there is such error, this does make the compile available to CCS. But out of cautiousness I certainly need to address the “FATAL ERROR” message:

Q: what is the correct syntax for calling this command to avoid the error message? Is using the command in such a way to add newer compilers to older version actually approved or might cause unexpected problems?

 

Matt

  • Hi Matt,

    Matt Mitchell46 said:
    First, latest compilers are not shown in software updates for V5.5. For example, V5.5 upgrades to ARM 5.1.11 but not aware of the 5.2.4 which is shown in update for V6.

    For compiler version x.y.z, the updater will only detect versions of a higher 'z'. If you what to update to a higher 'x' or 'y', you need to use the I"install new Software" option. For more details, see:

    Matt Mitchell46 said:
    Similarly, V5.5 sees C6000 V7.4.4 in update but not 7.4.14 as in V6.1.

    Now that should work. In fact, I see C6000 v7.4.14 as an available update with my CCSv5.5.

    Matt Mitchell46 said:
    As will be described in next question, “SetupInCCSnRegistry.exe” can actually be called to manually add new compiler to CCS5.5.

    That file, along with the other registry related files are not needed for newer CCS versions (like CCSv5 and 6). It was used by older CCS versions that used the Windows registry. Those files are still there for legacy support.

    The instructions of manually installing standalone compiler version is listed below:

    Thanks

    ki