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.

automatically generated configPkg/linker.cmd, causes linker errors

Hi,

I migrated weeks ago a project to the CCSv6.0.1 and then to CCSv6.1.1 it all worked fine until yesterday. Now I constantly get the following error:

Console Output:

"C:\\ti\\ccsv6.1.1\\ccsv6\\utils\\bin\\gmake" -k all
gmake: *** No rule to make target `D:/projects/THDA/Firmware/GIT_repo_complete/Firmware/trunk/Debug - Kopie/configPkg/config.bld', needed by `configPkg/linker.cmd'.
gmake: Target `all' not remade because of errors.

1. The folder >Debug - Kopie< does not even exist anymore! --> why is it mentioned and how can it be deleted?

2. setup a new Project didn't change anything

3. I tried to add the --clean option to the CCS exe file. --> no change

4. In CCS6.1.1 the Errors displayed in the Problems Tab are deleted when you change to this tab. So normally the Console output is simply >not remade because of errors< how should it be possible to work with such a tool?

5. trying to open the project again in CCS6.0.1 is not possible because the import is canceled with the error message that the compiler 6.4.x is not installed. So it can't import... (why is the import different if the compiler version in the project is higher than the current installation? --> why isn't it possible to select another compiler when the project is opened.

6. and most important, why is there now an automatic linker file generation? it always worked fine to have a linker cmd file in the project, now the automatic generated file generates problems with the cmd file in the project how can this be turned off?

  • Andreas Unterberger said:
    1. The folder >Debug - Kopie< does not even exist anymore! --> why is it mentioned and how can it be deleted?

    Have you tried importing the project into a new workspace? Is the issue reproducible in a new workspace? 

    Andreas Unterberger said:
    4. In CCS6.1.1 the Errors displayed in the Problems Tab are deleted when you change to this tab.

    This may be due to this bug? Normally if the Problems view is kept open, the contents should not be deleted.

    Andreas Unterberger said:
    5. trying to open the project again in CCS6.0.1 is not possible because the import is canceled with the error message that the compiler 6.4.x is not installed.

    If the project is created for a newer version of compiler than the version "found" in CCS, then it will not import until you install that equivalent version. So you would need to first install a 6.4.x version of the compiler into CCS 6.0.1 and then import the project. 

    Andreas Unterberger said:
    6. and most important, why is there now an automatic linker file generation? it always worked fine to have a linker cmd file in the project, now the automatic generated file generates problems with the cmd file in the project

    RTSC projects generally do generate a linker command file automatically. But is should still possible to add custom linker command files to the project, as long as the contents don't clash. http://processors.wiki.ti.com/index.php/Files_in_CCS_Projects#SYS.2FBIOS_Configuration_files