• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 100 subscribers
  • Views 2859 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

can't locate file 'ti/targets/rts6000/link.xdt'

Joseph Chang
Expert 1170 points
Other Parts Discussed in Thread: SYSBIOS, CONTROLSUITE

I get the following error when I try to build my project in CCS:

Description Resource Path Location Type
can't locate file 'ti/targets/rts6000/link.xdt' along the path: C:\ti\tirtos_c2000_2_12_01_33\products\bios_6_41_04_54\packages\ti\platforms\tms320x28;C:/ti/tirtos_c2000_2_12_01_33/packages;C:/ti/tirtos_c2000_2_12_01_33/products/bios_6_41_04_54/packages;C:/ti/tirtos_c2000_2_12_01_33/products/ipc_3_30_01_12/packages;C:/ti/tirtos_c2000_2_12_01_33/products/ndk_2_24_02_31/packages;C:/ti/tirtos_c2000_2_12_01_33/products/uia_2_00_02_39/packages;C:/ti/ccsv6/ccs_base;C:/ti/xdctools_3_31_00_24_core/packages;..; .xdchelp /exam_controller line 94 C/C++ Problem

Previously, it would build fine and it builds on other computers.  I'm not sure why it is trying to look for link.xdt, as I searched for this file in C:\ti on a computer that does not have this problem, and no such file exists.  I've tried cleaning the project, deleting the Debug directory, and deleting the workspace to clear out any possible corruption, but to no avail.

Any ideas on how to fix this?  Thanks in advance.

  • 0
    TI__Guru**** 171044 points
    Hi,

    Did you import this project from somewhere? The reason is because the error mentions rts6000 path (for C6000 devices), but the TI-RTOS you have installed seems to be designed for C2000 devices.

    You could try to install a C6000 TI-RTOS from the page below:
    http://www.ti.com/tool/ti-rtos

    Some additional instructions to add this product to your CCS are shown in the page below:
    processors.wiki.ti.com/.../Installing_TI-RTOS

    I will move this thread to the TI-RTOS forum so they may have additional insights about this issue.

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Expert 1170 points

    desouza said:
    Hi,
    Did you import this project from somewhere? The reason is because the error mentions rts6000 path (for C6000 devices), but the TI-RTOS you have installed seems to be designed for C2000 devices.

    No, the project was created as a New Project for the C2000, which is the actual target family.  There should be no references to C6000, so the problem appears to be an incorrect reference to C6000 for some reason.  

    desouza said:

    You could try to install a C6000 TI-RTOS from the page below:
    http://www.ti.com/tool/ti-rtos

    Some additional instructions to add this product to your CCS are shown in the page below:

    processors.wiki.ti.com/.../Installing_TI-RTOS

    I will move this thread to the TI-RTOS forum so they may have additional insights about this issue. 

    Since the target family is C2000, I don't think the issue is a missing C6000 TI-RTOS installation.  I'm not sure which forum an incorrect dependency goes in, but I would think it's more of a CCS issue.

  • 0 in reply to Joseph Chang
    Intellectual 310 points
    I'm getting the same message under the same (more or less) circumstances.
    Rafael, have you found a solution?
    -- Carl
  • 0
    TI__Mastermind 32475 points

    You said it previously built fine....any idea what change?

    Does the problem exhibit itself when you build one of the SYSBIOS examples from scratch?

    Unless I can reproduce this...it will be hard to know what's going on.l

    Judah

  • 0 in reply to judahvang
    Expert 1170 points

    judahvang said:

    You said it previously built fine....any idea what change?

    No, that's why I'm posting here.  I tried uninstalling TI-RTOS, CCS, and ControlSuite, deleting c:\ti, then reinstalling (though I didn't restart after uninstalling/deleting), but the problem still persists.

    judahvang said:

    Does the problem exhibit itself when you build one of the SYSBIOS examples from scratch?

    No, though I had to change Project Properties > General > RTSC > Target from "devkits.target.Generic" to "ti.targets.C28_float" to fix a target error when building the imported exampled project.

    judahvang said:

    Unless I can reproduce this...it will be hard to know what's going on.l

    Can you tell me what files you need to reproduce this and provide a private method of sending the files (I can't upload my project to a public forum)?  I tried a bit to look at the makefiles and other files generated as part of the build to figure out why the build is trying to look for 'ti/targets/rts6000/link.xdt', but I didn't get very far.  I imagine someone at TI understands the build process intimately enough to know how to reproduce and debug this.

  • 0 in reply to Joseph Chang
    Expert 1170 points

    I also tried starting CCS with -clean, but the problem still persists.

  • 0 in reply to Joseph Chang
    Expert 1170 points

    A colleague helped me track this one down.  He managed to follow the problem back to a bad app_p28FP.cfg (actually it was named app_p28FP_p28FP.cfg for some reason) which was referencing a app.cfg that no longer existed.  The path for the non-existent app.cfg included the name of a old build configuration that was deleted.  I figured the Debug directory for the old, deleted build configuration was somehow affecting the build process, so I tried deleting it and that fixed the problem.

    I'm not sure, but I think I deleted the old build configuration on another machine and checked in the changes to .project/.cproject files to source control.  This got rid of the build configuration when I got those changes on my machine, but it did not get delete the old build configuration Debug directory.

    I think this should probably be one of the first things to check if the build process errors out inexplicably like this.  Maybe cleaning the project should also include an option of deleting Debug directories for build configurations that no longer exist.