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/CCSTUDIO-C2000: no target configurations for projects after upgrade

Part Number: CCSTUDIO-C2000

Tool/software: Code Composer Studio

When I upgraded from CCS 8.2 to 8.3 and point my workspace path to my projects workspace, all of my projects (I mostly use TMS320F28035 MPUs, from C2000 family) stop working due to Target Device not recognized.

It complains about my ccxml file and I cannot do anything to fix that.

The Properties/General tab only shows Custom C2000 and Generic C28xx devices and all other device options are grayed out. At first it also showed "TMS320C28XX.TMS320F28035" but it was not recognized and then removed.

The same thing happened when I upgraded from ver. 8.1 to 8.2 and I think I had to recreate all my projects to make them work. This is ridiculous.

It all worked before the upgrade.

  • Hello Martin,
    try this:
    create a new and empty workspace,
    import a project from an "previous" and non working workspace to this new one
    and let me know.
  • Hi,

    Just adding to Tomasz reply.

    How did you perform the upgrade? Our recommendation is to either install CCS to a different directory or to completely delete the original directory and reinstall.

    If you are instead performing one install over a previous release, there is a chance the newer files may not be properly acknowledged.

    Also, you can always check if you have the F28x device files under the target database directory under:
    ccsv8/ccs_base/common/targetdb/devices

    Hope this helps,
    Rafael
  • Tom,
    It did not change anything; using new workspace with imported projects gave me the same results.
    After 2nd reinstall, it started to work with either workspace.
    Dzięki,
    Martin
  • I downloaded off-line zip file.
    When run, it gave me a lot of errors and crushed a lot so eventually I had to remove old CCS by running uninstall_ccs.exe and reinstall.
    Then I pointed CCS dialog to my old workspace.
    Creating new workspace and importing projects did not work either.
    Then I repeated the uninstall and reinstall the second time and this time it worked.
    I think I have seen this mentioned before that two reinstalls were needed to fix things.

    The directory:
    ccsv8/ccs_base/common/targetdb/devices
    existed both times and is populated with 109 file of all? F28xx xml files

    My project's ccxml file references following files:
    "connections/TIXDS100v2_Connection.xml" (not found after 1st install, found after 2nd)
    "drivers/tixds100v2c28x.xml" (not found after 1st install, found after 2nd)
    "drivers/tixds100v2cla.xml" (not found after 1st install, found after 2nd)
    "devices/f28035.xml" (found in directory above)

    It seems that I always have some upgrade problems and that the process is very unfriendly. For this reason I never use online upgrades because something always bad happens.
    Martin
  • In the past, I had many issues and in most cases they were related to the workspace conversions.
    As Rafael has said,
    you can install new CCS version in a different directory.
    During an installation there is a prompt to select a install directory. Do not use default, select the second on the list.
    Last tip: never share a single workspace between different CCS versions.

  • I have found the real culprit for this problem.

    After I installed  CCS and run it, and it asked me to update the tools to newer versions available so I did.

    Then I uninstalled the older versions of the tools to get rid of them to save space and then CCS stopped working (as described).

    The second time I installed CCS, I did not update the tools and everything worked.

    Then I updated the tools and it still worked, Then I started to uninstall older/unused(?) versions of the tools.

    Uninstalling older versions of the compilers worked fine but uninstalling older version (8.0.903.2, leaving 8.0.903.6) of "TI Emulators" deleted all the required files mentioned before.

    I do not know how TI keeps track of different versions of TI Emulators but obviously they share the same files in the same directories and deleting one of versions corrupts the other one.

    This should not happen and if TI upgrades tools that share files, the older version should be removed before the new one is installed or they should be kept separate to allow uninstall properly.

    My problem had nothing to do with the install directory nor workspace directory since it all works as long as I do not uninstall unused(?) versions of TI Emulators.

    Martin