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.

Cleaning/rebuilding RTSC registry



Hello,
Is it possible to rebuild the RTSC registry (probably the location where the information on all installed products is stored)?

The problem I'm currently facing with CCS v5.1 is the following:
I have pspdrivers_02_20_01_00 installed in the top level search directory (above the ccsv5 directory).
Now if I want to this package, I see in RTSC->Products view the message that the package can not be found (indicated by a small yellow sign)

If I rename the package (to let's say pspdrivers_02_20_02_00), and do a refresh, I can use the package out of the new directory.

I would assume that the RTSC registry is somehow weird, so I would like to rebuild it...

Thanks and best regards,
Rene

  • Rene,

    Rene Wittmann said:
    Is it possible to rebuild the RTSC registry (probably the location where the information on all installed products is stored)?

    I'm not sure about this, I'll have to check into it.

    Rene Wittmann said:
    I have pspdrivers_02_20_01_00 installed in the top level search directory (above the ccsv5 directory).



    Did you add this directory to the Tool Discovery path (under Window ->Preferences->Code Composer Studio->RTSC->Products) and then restart the computer for it to take effect?

     

  • Hi AartiG

    AartiG said:
    Did you add this directory to the Tool Discovery path (under Window ->Preferences->Code Composer Studio->RTSC->Products) and then restart the computer for it to take effect?
    Yes, I have done this. Although I would assume that the "Refresh" button should do the same (and then maybe tell you that it is required to restart).

    The strange thing is that says "Product 'PSP Drivers' v.2.20.1.00 defines no repository. Uninstall and reinstall the product, or contact the product provider".
    If I rename the directory, and add the renamed directory to "Tool discovery path" the message does not appear and I can actually use libs out of PSPDrivers!

    Regards,
    Rene
  • Rene,

    I discussed this with some experts and the recommendation is to give CCS 5.1.1 a try. This version is now available for download.

    CCS 5.1.1 is more robust in handling and detecting RTSC components, especially in cases where a user manually deletes a RTSC product through the filesystem. It also has a "Remove" button on the Preferences->RTSC->Products page, which will allow you to cleanly unregister a RTSC product.

  • AartiG said:

    Is it possible to rebuild the RTSC registry...?

    I'm not sure about this, I'll have to check into it.

    [/quote]

    Check it, for me also, please.

    My CCS 5.1 crashed during of updating of SYS/BIOS, IPC, XDC tools (40 min of updating and crashed then).

    Now all the new repositories 'defines no repositories' for CCS.

    The uninstalling and re-installing does not solve the problem.
  • I apologize for the inconvenience, but I was told that CCS 5.1.1 is more robust in this regard. Would you mind giving this version a try?

  • Is it possible to update CCS 5.1.0 to 5.1.1 out of CCS? Or is it required to download the full package and install it in parallel to the current installation?

    If an update is possible, I would be willing to give it a try. Otherwise I personally can state a clear: no!
    I absolutely would mind downloading another 1,x GB, install it, set up my environment and waste another day in developing. The end user should not be your testing departement!

    Rene
  • Rene Wittmann said:
    Is it possible to update CCS 5.1.0 to 5.1.1 out of CCS? Or is it required to download the full package and install it in parallel to the current installation?



    It is possible to update from 5.1.0 to 5.1.1 via Update Manager, however, unfortunately we have discovered some issues with it that we are currently investigating. I apologize for the inconvenience caused by this and we hope to resolve this issue as soon as possible.