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.

MSPM0G3507: Why is the "current" version 1.4.1.1 of CCS theia that I downloaded and installed YESTERDAY many revisions AHEAD of the "latest" 1.4.0.12 version?

Part Number: MSPM0G3507

Tool/software:

Yesterday I downloaded and installed from ti web site CCS Theia.  Its broken (see my other post about broken help links, no way to set project directory, no way to use github etc) so I tried to update thinking surely these bugs must have been fixed and I have a bad release and I see this:

 Current version is 1.4.1.1 and latest is 1.4.0.12?!  When I learned to count 1 came after 0, pretty sure it still does so HOW IS THIS POSSIBLE?  Do I have a alpha pre release version and you want me to downgrade?  What am I missing?

  • Hello Chris,

    The latest version of CCS Theia which you can download in Ti.com is the actual latest version. Maybe that when our software team colleague updated the version of CCS Theia, they forget to modify the related description in the "software update" window, but I think it won't affect you using the CCS Theia. And about your questions about the broken link, etc. I have replied to you in your another post.

    Best Regards,

    Janz Bai

  • I Clicked "check for updates".  You have a update server which reported a LOWER revision as more recent than the revision that is currently downloaded.  That is a critical and serious BUG.  It is not text string the developers "forget to modify".  That is not at all how revision control works.  The revision numbers are all automatically generated by the development environment.  When you check for updates a update server is queried for the latest revision and that is compared to the installed revision.  Normally if the version from the update server is a lower number than what is installed the "install" button would instead be replaced with a warning that says "this is a downgrade" and the button would say "downgrade" and after you clicked it you would get a final warning that says "are you sure you want to downgrade".  Downgrading is very dangerous because it often makes the application unstable or incompatible with projects created by the higher rev of code.

    Again, you have a serious bug, fix it!!

  • Hello Chris,

    I have double checked this issue and I will assign this issue to our SDTO team to give your some commons.

    Best Regards,

    Janz Bai