• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 54 subscribers
  • Views 1399 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Upgrading from CCSv6.1.1

RandyP
Guru* 84110 points

With CCSv6.1.1 installed (Win7 64-bit), I used the Help->Check for Updates feature.

I saw on the Processor SDK site that it has a link for CCSv6.1.2, so I assumed the Check for Updates would take care of that update, but it did not.

Q1: Should minor releases like this be handled by the Check for Updates feature? Or is there a preferred method for staying with the most recent release?

Q2: I noticed 6.1.3 is available, but since the Processor SDK did not mention it, I was concerned there could be issues if the SDK was not tested with it. Is there a major change when moving to Eclipse 4.5 as in the 6.1.3 update? Or should I not worry about it and just stay with the latest?

[Ed RP added -] Q3: When I did the install of v6.1.2, the icon it put on the desktop said it was for v6.1.1. I did install 6.1.2 into the same folder as the v6.1.1 was installed (and v6.1.0 before that), and there was an icon in the CCS folder already named Code Composer Studio 6.1.1 but I am not sure if there was an icon on the desktop already (I usually move it to a special CCS subfolder). That icon in the installation folder seems to have been reused, the date is today. Not sure if that is expected behavior by you, but it wasn't by me. So my question is - is that what should have happened or should a new icon have been created that said 6.1.2 on it?

Regards,
RandyP

  • 0
    Guru 92251 points

    RandyP said:
    Q1: Should minor releases like this be handled by the Check for Updates feature? Or is there a preferred method for staying with the most recent release?

    From CCS 6.1.2 onwards there is going to be a CCS Incremental Update Policy which says if it is possible for a minor release to be handled by the CCS Update Manager.

    That Wiki page says that for both CCS 6.1.2 and 6.1.3 the releases will NOT be available as an update. 

  • 0 in reply to Chester Gillon
    TI__Guru* 84110 points
    Chester, Thanks for pointing that out. I now see the comments for each saying it is not available as an update.

    Q1a: When doing a non-update upgrade, such as 6.1.1 to 6.1.2, is it still perfectly fine to install the new release on top of the old release?

    Regards,
    RandyP
  • 0 in reply to RandyP
    Guru 92251 points

    RandyP said:
    Q1a: When doing a non-update upgrade, such as 6.1.1 to 6.1.2, is it still perfectly fine to install the new release on top of the old release?

    I don't know what the "official" answer is, but the last time I installed a new release of 6.1.2 on top of an existing 6.1.1 installation under Linux had some issue with CCS reporting that the PROCESSOR-SDK-RTOS-AM335X and PROCESSOR-SDK-RTOS-AM437X products were no longer installed when attempted to compile projects - see https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/491383#1775416.

    Therefore, I am bit wary about installing a new CCS release on top of an old release. 

  • 0 in reply to Chester Gillon
    TI__Guru**** 169754 points
    Randy, Chester,

    >> Therefore, I am bit wary about installing a new CCS release on top of an old release.
    I personally tend to do the same as I like starting with a clean slate, and have suggested this a few times around this forum.

    In fact, I usually install CCS side-by-side (C:\CCSv6_1_1, C:\CCSv6_1_2, and so on) and use a different workspace where I migrate my previous projects one-by-one (unnecessary to say that I usually slack and forget to migrate all of them, thus ending up with zillions of workspaces, but that is another story).

    For projects that are frozen - i.e., tied to an existing combination of tools and dependencies, I zip the CCS directory, the workspace directory and any libraries or SDKs stored under C:\ti - storage is cheap nowadays.

    For certain hosts that I need to strictly follow the default install directory (C:\ti), I usually wipe out the previous version (Shift+Delete works wonders) and install the new one. I also wipe the installed xdctools_core tools as well, so I can start clean.

    Anyways, YMMV.

    Regards,
    Rafael