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/TMS320C6657: RTSC Platform Config Error: Can't find 'ti.catalog' pacakges...

Part Number: TMS320C6657
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

There are a couple posts on this issue with older versions of code composer, but I have not been able to resolve this issue yet.

I need to create a new platform with XDCTools Version 3.32.1.22_core, however the RTSC->New Platform fails with the error below.   If I attempt to create a new platform with the XDCTools version set to 3.50.1.12_core, it works properly.  How do I get the 3.32.1.22_core option to work?

UPDATE/NOTE:

1) I have tried on various installation with the same problem, CCS 6.1, 7.0.0.00043, 7.1.  all have the same issue.   It seems to be following the XDCTools 3.32.1.22 Version.

2) I cannot upgrade to the XDCTOOLS 3.50 because we can't change compilers on this program.  TI's site seems to indicate 3.50 is only good vor CCS7.1 and up, but we are stuck at 7.0.0.043 right now.  

I attached a .txt file with my installation information (Help->About Code Composer Studio, Configuration Tab).

/cfs-file/__key/communityserver-discussions-components-files/791/4278.8883.CCS7.0.0.00043_5F00_Installation_2D00_Details.txt

  • Hi,

    I've notified the sw team. their feedback will be posted here.

    Best Regards,
    Yordan
  • Mark,

    We are not recommending migration to XDC 3.50.xx.xx version that is part of the CCSv7. Please stick with the XDC3.32 version that is supported with the C6657 SDK as you have choosen.

    The issue you are reporting has less to do with XDCtools and more to do with the tool unable to locate the bios_6_46_01_38\packages\ti\catalog which is the default path where it installs the new platform. Here is the screenshot from my Processor SDK setup. In my setup, I have not set any RTSC settings but have discovered the Processor SDK RTOS components globally so all RTSC and BIOS related functions use those global settings. I am including a screenshot for reference:

    Preferences-> CCS-> Products


     

    One option for you to try is to click the Browse option and manually locate the bios_6_46_x_x/packages  in the tool or just create the custom platform in repository in your project instead of putting it along the platforms in the bios package.

    Hope this helps.

    Regards,

    Rahul

  • I'm working my way towards your suggestions.   My current problem is, if I try to un-check all of the products and repositories in

    (Help->Preferences->Code Composer Studio->Prodcuts->RTSC) , then hit the "apply" button, followed by the "OK" button", if I re-open that same window it get's repopulated and versions that are not even installed get checked.     See the screenshots below:

    1) Make Changes and apply

    2) Re-open window, and invalid options are checked...?

  • A few more things I noticed.

    1) I'm using the SysBios that was packaged with the 6657 SDK. That is 6.46.4.53...you mentioned 6.46.01.38. Do I need to download the older sysbios version?

    2) I am unable to create a new platform regardless of whether I select File->New->RTSC->RTSC Platform, or Project->RTSC Tools->Platform->New Platform (Same Error)

    3) If I try to change my project's RTSC XDCTools setting to 3.32.... I can't because there are no valid platforms created for that, and it doesn't allow me to save the project without a valid platform.

    4) Is this an issue because i'm use CCSv7.0.0.00043 instead of  one of the CCSv7.1 builds?   This was all working under 7.1, and porting it back to 7.0.0.00043 has been a nightmare. 

  • There is clearly some integration issues with ccs 7.0.0.00043 and the development tools i'm using.
    I have 7.1 and 7.0... installed on my machine.
    In order to make project changes they have to be done with ccs v7.1. These show up properly when I open my workspace in 7.0. I am unable to make any useful changes in 7.0. I guess I have to talk this through with our development team to see where we go from here.