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.

Re: [CCS V4] Code Composer Studio (4.0.2) C28 Flash update patch 4.0.3

Hello Lori,

I applied this patch - then it seemed the rev rolled back to 4.0.1.x or something like that - is that normal or expected?

I am not on my dev. computer right now - but I can update with the exact updated rev - I think it is something like:

4.0.1.01001  <== verified this is the rev showing *after* the patch.

Thanks,
John

  • John,

    I don't know.  I've moved your question to the CCS forum for the experts there to respond.

    -Lori

  • We've found there is a bug in the Eclipse open source feature management code that causes the oldest feature present in the install to be activated instead of the newest. It is a bit confusing because Eclipse correctly activates the newest plugins even if they don't correspond correctly to the activated feature.  The impact of this bug is that Help->About and the feature configuration GUIs will display incorrect information. You may also be prompted to reinstall a patch that you have already installed.

    We're working on a fix for this with the intention that the C28 patch would be updated to included the Eclipse fix.

  • Andy,

    Do you know if the old version being reported could affect using CCS XDS100 under vista 64-bit?   Please see this post from the same customer.  He is able to get it to connect on windows 7 64-bit.

    http://e2e.ti.com/forums/t/13341.aspx

    -Lori

  • Lori,

    The customer's issues sounds like something different.

    The 4.0.3 flashing patch has been updated to fix the version problem. There was a bug in the Eclipse source that causes the oldest available feature to be selected instead of the newest.

    I didn't increment the patch version number, so it still appears as the same patch in update manager. If the version number is causing concern, the patch can be unininstalled and reapplied to correct the version info. After reapplying the patch, they will see the 4.0.2 version in help->about. This occurs because this targeted patch is being deployed as a DebugServer feature rather than a complete service release. As such, it does not change the Eclipse branding.

    Andy

  • Andy,

    Nope - I don't think it is different - but I am a little confused now. 

    The 4.0.3x patch will roll the rev back to 4.0.2x?

    I am using the 4.1.x Beta now anyway - I may not want to play version hopscotch anymore.

    Regards,
    john

  • John,

    Sticking with the 4.1 beta is probably the thing to do.

    I agree, the numbering is confusing. The short summary is that applying "4.0.3" on top of 4.0.2 replaces two files (a jar file and a DLL) in your install. It does not roll back the rev, but the version that appears in help->about does not change either. Sorry for the confusion around this.