• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 762 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.3.0 (Linux) doesn't discover installed tools

OH
Intellectual 260 points


Having insalled the same CCS and tools/products on both Windows (7) and Linux, I'm having problem on the Linux installation.

The problem is that I can't get CCS to discover my installed tools/products/packages.

Looking in Window->Preferences, under Code Composer Studio->RTSC->Products my tool discovery path seems ok, but I miss for example NDk and MCSDK completely in the discovered tools section. Another thing, that I guess is related, is that in the discoverd tools section I have several versions of IPC and SYS/BIOS (which I guess is ok) but som of them displays a "warning sign icon" and a tooltip stating "Product XXX defines no repositories. Uninstal and reinstall the product, or contaxt the product provider"

Does anyone know how to solve this problem(s)?

/OH 

  • 0
    TI__Guru*** 130875 points

    Hi Olof,

    is it only in the Linux version you see this behaviour?  Can you try launching CCS and installing any updates/packages with the same privileges/settings?  Eg if you installed ccs as sudo could you launch as sudo and install these packages as sudo?  We have seen this behaviour (packages not recognised) when not using the same admin settings.

    Please keep us informed.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Intellectual 260 points

    Hi Lisa

    Yes, this happened just when using the Linux version.

    I was not the one doing the actual installation, but the one who did is sure he used the same user for both CCS and all additional packages.

    I guess it has something to do with the privileges though, because after just starting CCS as the "install user" and letting the packages be discovered as that user, they were discovered the next time I started as my regular user.

    Does the "discovery" involve writing stuff in the install directories?

    /Olof

  • 0 in reply to OH
    TI__Guru*** 130875 points

    Hi Olof,

    yes, there should be some initialization files that get updated with the search path.   I am glad to hear you seem up and running.  Thanks for the update and all the best with development.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    TI__Genius 13505 points

    I just ran across this issue myself.  There does seem to be an issue with CCS 5.3 and detecting some of the MCSDK tools.  I also tried going the route of Help->Install New Software.  The MCSDK tools never appear in the RTSC products view after installing the packages.

    I decided to delete the ccsv5 path, but leave all the MCSDK libraries intact (/opt/ti/...) and install CCS 5.2.  CCS 5.2 detected all the MCSDK libraries without any intervention on the first launch.

    I'm using Debian Squeeze (6.06), FYI.