• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Subscribers 55 subscribers
  • Views 3263 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 cannot find product/package when moved after auto discovery

sgspecker
Intellectual 2765 points
Other Parts Discussed in Thread: MSP430WARE, SYSBIOS

We've run into this twice in the last week. (On 2 different computers and with 2 different product/packages.)

How can you get CCS v5.x to re-recognize a package (i.e. product) such as XDC or MSP430ware?

In each of these cases, the product was already discovered by CCS. Then, it was moved to another location in C:/TI. After it was moved, CCS lost all knowledge of the package and will not recognize it again. I suspect CCS must be storing this information somewhere, but I cannot find it.

It does not help, even if you go to Windows->Preferences->CCS->RTSC->Products and verify the path shows up in the list; even if you click refresh.

Thanks,
Scott

  • 0
    TI__Guru**** 463871 points

    Hi Scott,

    Sometimes I clear out the workspace metadata information to have CCS re-detect packages that it "loses". But that is probably an extreme step.

    When you move a package, where do you move it to? In the same root directory but just with a new name? And why are packages being moved around? What is the common use case for this?

    Thanks

    ki

  • 0 in reply to Ki
    TI__Intellectual 2765 points

    I've tried moving to a brand new workspace, that didn't help.

    I moved the MSP430 package from within the "C:\ti\ccsv5\tools\compiler\msp430_4.2.1\" folder (where it was placed on CCS install) to the "C:\TI" directory where a stand-alone MSP430ware default installation places it. While maybe unusual, I can see other folks trying this - and getting stuck, too.

    I cannot remember why he moved XDC 2 weeks ago and got a similar problem. I think it was just to re-organize the products inside the TI folder.

    Scott

  • 0 in reply to sgspecker
    TI__Genius 9345 points

    Hi Scott,

    What exact version of CCS are you using?

    Thanks,

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    TI__Intellectual 2765 points

    Two weeks ago I saw this with CCSv5.4. Currently, I'm using a pre-production v5.5.

  • 0 in reply to sgspecker
    TI__Genius 9345 points

    Scott,

    I've opened a CQ to track this problem: SDSCM00047983 Moving/removing target-content products in filesystem puts CCS in a bad state.  I will look into fixing this for CCS v6.

    You should be able to recover your CCS as follows:

    1. Open Help > About...
    2. Click Installation Details...
    3. On the Installed Software tab, select the two MSP430ware and the two RTSC/XDCtools components, and click Uninstall...
    4. Once CCS restarts, you should be able to re-discover these products by clicking the Refresh button on the Preferences > CCS > RTSC > Products page.

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    TI__Intellectual 2765 points

    Well, it didn't seem to auto-discover the products after uninstalling them and refreshing as per the steps. I just went ahead and reinstalled CCS.

    Thank you for submitting the ticket for fixing this in a future revision of CCS.

    - Scott

  • 0 in reply to sgspecker
    TI__Genius 17101 points

    Guys,

    this is definitely a show stopper. We experiencing this on all machines at the customer. Please provide steps to go through to discover packages again. We don't want to re-install CCS. There need to be another way to fix it.

    We had just renamed one SYSBIOS package. Before we removed it from preferences of packages to be auto disovered. Now we can't get SYSBIOS discovered.

    What can we do?

    Thorsten

  • 0 in reply to Thorsten Lorenzen
    TI__Genius 17101 points

     

    On way we fixed it was to copy the folder below on top of the CCS installation. As we made a backup copy prior to this problem we were able to take the complete folder "configuration" from backup and copied over the link below. Now we can see the packages again.

    C:\ti\ccsv5\eclipse\configuration

    Please comment on this and let us now what it is.

    Thorsten

  • 0 in reply to Thorsten Lorenzen
    TI__Genius 9345 points

    Hi Thorsten,

    Could you let me know which version of CCS you are using, and also provide the steps to reproduce the problem you're seeing?

    Thanks,

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    TI__Genius 17101 points

    Hi Baltasar,

    We are using CCS5.4. CCS5.5 seems to not show this behavior.

    So you build a project of your choice having two SYSBIOS packages discovered in CCS. After you re-name one SYBIOS package so that it is not in the list of products anymore after restarting CCS. You buld with the other version. Then you bring the origin name from one package back you have re-named. CCS is not showing this package any more. So you can't go back and build with this version.

    Thorsten

  • 0 in reply to Thorsten Lorenzen
    TI__Genius 9345 points

    Hi Thorsten,

    I'm still a bit unsure about the problem you're facing.  Are you trying to fix a corrupted installation of CCS v5.4?  Or are you looking for a way of switching the version of SYSBIOS for an existing project?

    To properly switch the version of SYSBIOS that is used to build a project, you should use the project's Properties > General > RTSC page. There, you can quickly select the versions of any target-content product for the project, without changing any of the products that are currently installed and registered with CCS.

    - Baltasar

  • 0 in reply to Baltasar Belyavsky
    TI__Genius 17101 points

    Hi Baltasar,

    currently, we are using CCS5.4. We moved to a later version of SYSBIOS for testing. That worked out fine. To be sure the system doesn't use the original version we renamed the package. After testing we wanted to move back to the version of SYSBIOS we used before. However, it disappeared from "Properties>General>RTSC page. So, we are not able to select it anymore. Even as we put the original name for that first version it is not detected anymore.

    Just for interest, I tested it on CCS5.5. Here it found the package at any time which is as expected.

  • 0 in reply to Thorsten Lorenzen
    TI__Genius 9345 points

    Hi Thorsten,

    I'm still not a 100% sure I understand the problem you're trying to solve.

    1. If you are just trying to resurrect your corrupted installation of 5.4, then you should either re-install it, or upgrade to CCS v5.5.  We cannot produce patches for CCS v5.4 at this point.
       
    2. And if you are trying to find the proper way of switching between different versions of SYSBIOS, then please use the project Properties > General > RTSC page, instead of physically renaming the installed software. Even in CCS v5.5 and up, this is the intended approach.
    Thanks,
    - Baltasar
  • 0 in reply to Baltasar Belyavsky
    TI__Genius 17101 points

    Hi Baltasar,

    I can imagine you remain confused. However, I can't tell customers always to totaly uninstall CCS and re-install just because of some unexpected behavior. Customers focus on completing thier own application rather than installing and debugging CCS. I was expecting to get some internal ideas of what to try if unexpected behavior is recognized.

    My customer need to work with CCS5.4 for now as automotive customers can't just move to later versions when unexpected behavior is observed. They need our help to keep going.

    So. if you are saying there is nothing TI can do we have to live with it. Unfortunately.

    Thanks for you help,

    Thorsten