• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 597 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS: CCS possible project copying bugs

Sean Oliver28
Intellectual 1060 points

Tool/software: Code Composer Studio

I believe I found a few CCS bugs. In CCS Version: 7.3.0.00019, I copied a project from another project in the same workspace. In order to get this copied project to build, I had to fix a few things. I've had to do this with a few projects now.

1. In "general settings" the target device had changed itself from ti.targets.arm.elf.M4F to ti.targets.arm.elf.M4. This results in a build error as the proper library file isn't found. Trivial to fix but figuring out what caused it took a few minutes. Ideally CCS would keep the same target device.

2. In the .cproject file, some of the xml fields kept the old project's paths so the auto generated makefiles couldn't find config.bld. The excerpts below show the offending sections. The highlighted parts are the folder names that I had to change.

<tool id="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.614135008" name="XDCtools" superClass="com.ti.rtsc.buildDefinitions.XDC_3.16.tool">
<option id="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.XDC_PATH.1203689341" name="Package repositories (--xdcpath)" superClass="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.XDC_PATH" valueType="stringList">
<listOptionValue builtIn="false" value="${XDC_CG_ROOT}/packages"/>
<listOptionValue builtIn="false" value="${TARGET_CONTENT_BASE}"/>
</option>
<option id="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.TARGET.606357614" name="Target (-t)" superClass="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.TARGET" value="ti.targets.arm.elf.M4F" valueType="string"/>
...
<option id="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.BUILD_CONFIGURATION_FILE.1929286763" name="Build configuration file (-b)" superClass="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.BUILD_CONFIGURATION_FILE" value="${PROJECT_ROOT}/OldProjectName/configPkg/config.bld" valueType="string"/>

<tool id="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.624706169" name="XDCtools" superClass="com.ti.rtsc.buildDefinitions.XDC_3.16.tool">
<option id="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.XDC_PATH.1491284185" name="Package repositories (--xdcpath)" superClass="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.XDC_PATH" valueType="stringList">
<listOptionValue builtIn="false" value="${XDC_CG_ROOT}/packages"/>
<listOptionValue builtIn="false" value="${TARGET_CONTENT_BASE}"/>
</option>
<option id="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.TARGET.954356362" name="Target (-t)" superClass="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.TARGET" value="ti.targets.arm.elf.M4F" valueType="string"/>
...
<option id="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.BUILD_CONFIGURATION_FILE.797499136" name="Build configuration file (-b)" superClass="com.ti.rtsc.buildDefinitions.XDC_3.16.tool.BUILD_CONFIGURATION_FILE" value="${PROJECT_ROOT}/OldProjectName/configPkg/config.bld" valueType="string"/>

Hope this is helpful and not just a problem on my end.

  • 0
    TI__Guru**** 173310 points

    Sean,

    Could you please attach a simple project that we can use to reproduce these issues? I haven't been able to reproduce them so far with the examples I've tried.

  • 0 in reply to AartiG
    TI__Intellectual 1060 points
    I'm not sure how useful this will be since the target is un-released hardware on an unreleased SDK, but I'll email you with a sample project I came up with. Perhaps that is the cause of the weird behavior but I don't know enough about how CCS works internally to really guess.
  • 0
    TI__Guru**** 173310 points

    This issue was worked offline.

    To summarize:

    Sean Oliver28 said:
    1. In "general settings" the target device had changed itself from ti.targets.arm.elf.M4F to ti.targets.arm.elf.M4.



    This was not reproducible on a cut-down version of the project. The original poster will report back if they hit this issue again.

    Sean Oliver28 said:
    2. In the .cproject file, some of the xml fields kept the old project's paths so the auto generated makefiles couldn't find config.bld.

    This was because the project's XDCtools option had a hard-coded path to config.bld. Modifying the path to use build variables (like PROJECT_BUILD_DIR/configPkg/config.bld) will help with portability.