• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 1508 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.

RTSC Platform and XDC tool version

tamo2
Expert 1670 points

Hi, 

We have been using a custom Platform file create by RTSC Platform tool for our C66x based product.

Recently, I modified the file a bit using the tool and suddenly the system started behaving strangely.  It turned out that the generated platform file now uses different XDC tool version (originally it was 3_25_00_48 and now it is changed to 3_30_01_25.  In my environment, both are installed).

The DSP .out project uses 3.25.0.48.

So, my question is, how do you force the XDC version in Platform file?

I use CCS v5.4.0.00091, and I have both 3_25_00_48 and 3_30_01_25 XDC installed.

Thanks,
tamo2

  • 0
    TI__Guru* 96960 points

    Hello,

    In the Project Properties->General->RTSC->XDCtools version drop-down, you can select which XDCtools to use.

    Todd

  • 0
    TI__Mastermind 37985 points
    tamo2,
    Todd's answer works for the version of XDCtools used in the project, but the Platform Wizard always uses the highest available version. I can see why you would have problems with 3.30.01.25 because that version of XDCtools should be used only with CCS 6.0 and later, which is mentioned in the release notes.
    You can try uninstalling 3.30.01.25 in Window->Preferences->Code Composer Studio->RTSC->Products. I can't recall know if that worked in CCS 5.4. If not, you may have to reinstall CCS 5.4 or upgrade to CCS 6.0 or 6.1.
  • 0 in reply to Sasha Slijepcevic
    Expert 1670 points

    Hi Sasha, 

    Actually, I rebooted my PC and then the Platform Wizard started working (it somehow correctly uses 3_25_00_48, which had been always the case before I suddenly encountered the problem).  So I guess somehow the Platform Wizard knows 3_25_00_48 is the "latest compatible" tool?

    I was going to uninstall 3_30_01_25 if the problem persist as you suggested, but since the problem is now gone, I am OK with what I have now.  If the problem happens again, then I will try what you suggested.

    Thank you,
    tamo2