• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 1239 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.

Original question:

CCS: V9 update failure

CCS: CCS v9 coexistence policy with other versions

Victor Kazmirenko
Guru 13202 points
Other Parts Discussed in Thread: MATHLIB

Tool/software: Code Composer Studio

Hello!

I was waiting for CCS v9 in hope it can eat my all 32GB of RAM ;-) , so installed a copy soon after its release.

One thing I noted the path for installation was proposed as c:\ti\ccs900, which, I think was similar with previous release. However, when I installed it side by side with ccs v8 in my d:\ti folder, on startup v9 could not install my other products, there was complaint like the were not compatible. Unfortunately, I have deleted that installation already because of its update issues and reinstalled into d:\ti\ccs900. Here, however, it does not detect other products, like DSPLIB, MATHLIB and alike.

So the question is what is v9 coexistence policy with older products? Do I need a separate copy of PDKs, SDKs as well?

Thanks.

  • 0
    TI__Guru**** 162305 points
    rrlagic,

    It is fine to install CCSv9 beside previous versions. Personally I have each version in its own directory under C:\ti (c:\ti\ccs620... c:\ti\ccs900) on another PC I have them in E:\ti\<version>

    There is no need to install separate copies of each PDK, SDK for each version of CCS. CCS will attempt to discover software packages on startup. You an also configure where CCS looks for software products in the Preferences dialog. Do you recall what the error message was when CCS was complaining about the products it found. One I see with some packages is that they are not properly signed, I just ignore those warnings.

    Regards,
    John
  • 0 in reply to JohnS
    Guru 13202 points

    Hello!

    Thank you for suggestion. It looks I could define software search path for CCSv9. However, it still does not work for me. One trouble I face is error  

    File devices/C6670.xml does not exist.  Was included by file [my path was here]/targetConfigs/TMS320C6670.ccxml	TMS320C6670.ccxml

    I see both MCSDK and MCSDK PDK C6670 are checked, but project does not build.

  • 0 in reply to Victor Kazmirenko
    TI__Guru**** 162305 points
    When do you get that error? That looks like what we call a device xml file. It is part of CCS and not part of the SDK. These files are located in <installdir>/ccs/ccs_base/common/targetdb/devices

    I just took a look at my CCSv9.0.0 install on Windows and that file is there. If it is not present in your install then likely the necessary device family selections were not made during installation. You can modify those selections by running the CCS installer again, point it to your existing v9 install, it will then allow you to update your installation selections.

    Regards,
    John
  • 0 in reply to JohnS
    Guru 13202 points

    Hello!

    Thank you for suggestion. Here is screenshot of installation process:

    And here is contents of my devices folder:

    66AK2E05.xml
66AK2G01.xml
66AK2G02.xml
66AK2G12.xml
66AK2H06.xml
66AK2H12.xml
66AK2H14.xml
66AK2L06.xml
defaultProperties.dat
TCI6630K2L.xml
TCI6634K2K.xml
TCI6636K2H.xml
TCI6638K2K.xml

  • 0 in reply to Victor Kazmirenko
    TI__Guru**** 162305 points
    We used to have more detailed descriptions that show up on the right when you select an item but I don't see those in v9. I have all families installed so I can't tell which one installed that support. I would try checking C6000 Power-Optimized DSP. I will ask around this morning and figure out which package those files are in.

    John
  • 0 in reply to JohnS
    TI__Guru**** 162305 points
    rrlagic

    I did a test install and only installed support for "C6000 Power-Optimized DSP". That installed support for C667x devices for me. So if you check that box then you should be all good. I will look into what happened to the descriptions.

    Regards,
    John
  • 0 in reply to JohnS
    Guru 13202 points

    John,

    Thank you very much for suggestion. Installing "Power optimized C6000" added C6670 support for me too, though knowing their power consumption I would rather mark them as power draining devices :-)

    Nevertheless, target support issue is fixed, but another one still exist. As I installed ccsv9 into its own subfolder, it sees only one version of XDCtools, and it appears it does not work with other package, I see error

    error: xdc.cfg.Program: "D:/TI/ccs900/xdctools_3_55_00_11_core/packages/xdc/cfg/Program.xs", line 71: xdc.cfg.Program : The package 'ti.sysbios.family.c64p' is not compatible with XDCtools used in this build. Please either use XDCtools compatible with that package, or update the product containing that package, or rebuild the package with XDCtools 3.50 or later.

    What could be a cure to it?

    Thanks.

  • 0 in reply to Victor Kazmirenko
    TI__Guru**** 162305 points

    Yeah it looks a bit funny when we have similar language for other families like MSP430.

    CCSv9 ships with XDCTools 3.55. Looks like this software package wants an earlier version of XDCTools. You can change the project to use an older version.  Assuming it has discovered them. I would take a look at v8 and check which version of XDCTools is being used by the project there.  Then in CCSv9 you can change the project properties to use that version here:

    If the version you are looking for does not show up in the list then we will need to make CCS discover it.

    You can do that in the preferences dialog here:

    Just add the path in the top part of the dialog and then click the rediscover button.

    Regards,

    John

  • 0 in reply to JohnS
    Guru 13202 points

    Hello!

    Thanks again for guiding me.

    I have rediscovered older xdctools from parent directory and after few more shaman moves finally I was able to build my project.

    Though this case is technically over, still I wonder, what is a reason to have number of xdctools versions in ti/, and in ti/ccsvXXX. If they are expected to be used by all ccs versions, why don't we have flat folder layout?

  • 0 in reply to Victor Kazmirenko
    TI__Guru**** 162305 points
    The xdctools that are shipped with CCS will be located in ti/ccs the ones that you get independently from CCS will default to ti/

    CCS should be setup to automatically discover the ones in its own install folder and the ones in ti/. It should also automatically find ones inside other CCS installs that are in ti/ccsX. When I look at my screen capture above I see that it only has the 2 default search locations and it has found the xdctools inside a number of my old CCS installs.

    XDCTools discovery works a bit differently than compiler discovery. For compiler discovery it all happens automatically with no user interaction. With XDCTools and some of other other software products you will get a Discovery Dialog that opens up in CCS saying it has discovered a list of products. It then prompts you to enable them which requires a CCS restart. These products have little Eclipse plug-ins in them. If that dialog gets dismissed then you won't see those products in your CCS.

    Regards,
    John