• Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 2423 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.

XDC tools is not recognized by CCS

SRINIVASALU BS
Intellectual 300 points

Hi Support,

I was able to build a project many times, then left that machine for few weeks, came back, and CCS is no longer able to find XDC tools.  The XDC path

 c:\ti\xdctools_3_23_04_60

was untouched.  I have tried deleting the path and re-installing, deleting the project workspace, and other combinations.  CCS still cannot find the XDC tools.

What is the way to force CCS to proceed?  The correct folder is obviously there.  These kind of problems with CCS eat so much time.  There has to be a manual override for something so basic as XDC tools, like a file I can edit manually?  Which file can I edit?.

When i right click project->properties, i am getting error messages attached with this post

Srinivasalu

-Signalogic

  • TI__Guru**** 477471 points

    Hello,

    SRINIVASALU BS said:
    I was able to build a project many times, then left that machine for few weeks, came back, and CCS is no longer able to find XDC tools.

    Did to take any updates to CCS? Any changes to your environment

    SRINIVASALU BS said:
    I have tried deleting the path and re-installing, deleting the project workspace, and other combinations.  CCS still cannot find the XDC tools.

    What is the way to force CCS to proceed?  The correct folder is obviously there.  These kind of problems with CCS eat so much time.  There has to be a manual override for something so basic as XDC tools, like a file I can edit manually?  Which file can I edit?.

    Check the RTSC preferences under Window -> Preferences -> Code Composer Studio -> RTSC. Here you can see the XDC versions detected and the search paths.

    I'd also try using a clean new workspace. It sounds like some corruption occurred.

    Thanks

    ki