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.

Target Configuration File Problem

CCS is showing me the following "problem" in one of my target configuration files.

Description    Resource    Path    Location    Type
PARENT-6-PROJECT_LOC\tools\target_config\C6A8143EVM.ccxml (The system cannot find the path specified) in file PARENT-6-PROJECT_LOC/tools/target_config/C6A8143EVM.ccxml    C6A8143EVM.ccxml    /enet_echo_evmc6a8143    line 0    Problem

I can't make out what it's trying to tell me.  The target config launches fine and works fine as far as I can tell. 

I am linking the file in my project as follows:

- Location: PROJECT_LOC\..\..\..\..\..\..\tools\target_config\C6A8143EVM.ccxml

- Resolved Location: C:\myDspProjects\C6Ware_C6A814x\tools\target_config\C6A8143EVM.ccxml

I tried removing the single GEL file I am using, but that didn't clear the problem.

CCS Version: 5.1.0.08012

C6A8143EVM.zip
  • Gus,

    I see a similar issue here; when I link a .ccxml file to a project using Project --> Add Files and try to reference to one of the Project Build variables, it throws an error message to the Problems view.

    I am not sure yet how to work around this error message, but similarly as your case everything works fine for me as well.

    I agree the error message is somewhat strange, although PARENT-6-PROJECT_LOC means it is six directories up (parent directories) from the PROJECT_LOC location.

    How are you exactly linking this file to your project?

    Just a quick note, though: looking at your ccxml file I see an apparently incorrect GEL file specification: ..\gel\PG2.1_Centaurus_20Mhz_Si.gel.gel

    I will get back when I find additional details about how to solve this (or a bug report).

    Regards,

    Rafael

  • Rafael,

    Thanks for looking into this and for catching that typo.  I'm also adding the files as you: Project -> Add Files.

    Gus

  • Gus,

    It seems to be a bug indeed. I filed today under the number SDSCM00042621 (check its status in the SDOWP link in my signature below).

    Other groups have been solving this by creating a copy of the file per example project - which has its benefits in case modifications are made to accomodate specific project requirements. However, sharing a common target configuration also has its advantages. It is more of a design choice.

    Cheers,

    Rafael