• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 797 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.

CCS 5 lost XDC tools

Alexander Baehr
Intellectual 616 points

Hello,

my CCS 5 lost its connection to the xdc tools. The XDCTools were working, and the XDC tools installation directory is existing and still in the search path, looking at Window/ Preferences.

When I open a project (OMAP L138/ ARM) usign DSP BIOS, I see that no  XDC tools are known. When I try to re-import the XDC tools, I get the message "No tools selected!".

Please see attached file for version information and screenshots.

Thanks for any help.

Alexander

 

 

 

xdctools_verloren (1).pdf
  • 0
    Intellectual 616 points

    I also tried copying the XDC Tools directory from a colleague where the CCS + XDC work. No effect.

  • 0 in reply to Alexander Baehr
    TI__Guru**** 463941 points

    Hello Alexander,

    Have you tried using a new workspace? It should clear out the cache and force CCS to rediscover any components again.

    I also suggest updating your CCS installation if you can.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 616 points

    Hallo Ki,

    I created a new workspace with a single ARM project. XDCTools is still unknown.

    Updating the toolchain is not an option for me, since I work together with several colleagues and we need to have exactly the same. Is there a single suggested update to the eclipse environment that should solve the problem?

    Strangest thing to me is that the manual import of the tools does not work. What exactly does CCS search for? Which system variables are needed?

    Thanks

    Alexander

  • 0 in reply to Alexander Baehr
    TI__Guru**** 463941 points

    Sorry for the late response.

    I got some feedback for one of the CCS developers. This can happen if for some reason some of the eclipse directories in CCSv5 become read-only or if files get modified/corrupted inside the .\ccsv5\eclipse/configuration directory. Later versions of CCSv5 guard against such issues better. We would normally recommend an upgrade but since you would like to stick to the existing version, you can try a reinstall of CCS

    ki