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.

9-27-12 Help>ChkUpdates>download> Program no work-no-more



I updated, what is presently stated as CCS v5.2.0.0069.

At the end of the download, I got the usual prompt to reboot.

When doing so, another window came up that repeated something like "install not successful".

Eventually, had to Ctl+Alt+Del to get out of the loop.

Upon reboot, the program asked to update the MSP-FET430UIF, but it had already been updated for V5.2, but who am I to argue, so I allowed the firmware update.

Now, I can open CCS v5.2, can connect with the target, but get errors during debug, and can not read user memory.  It is the new workspace I made with the new update that failed, it appears the older work spaces still function, but have not wasted too much time trying to fix CCS. I have reverted back to CCS v4.2400033, with the same c-file used in v5.2, v4.2 seems to be working fine.

In v5.2, if I try to Help> Check Updates, I get the message no updates are available.

Ouch!

  • Hi,

    )would you be willing to send us the installjammer registry directory contents? (found under program files or program files(x86)) What installation path for v5 was used in general?

    If you creat a new workspace are they all now problematic in v5?

    Best Regards,
    Lisa

  • Hi Lisa,

    C:\Program Files/InstallJammer Registry

    1) Are you asking for the contents of this file?

    2) There is not a folder named x86 in the Install Jammer Registry folder (there are folders named ccsv4, ccsv5, and MSP430)

    Or, are you asking for a Run > regedit setting?

    3) The location of my install of CCSv5 is:  E:\MSP430_Compilers\CCSv5.2

    4) My transition to CCSv5 has been nothing but painful.  I started with CCSv5.1 (from v4), which did not work at all, it was removed from the computer.  V5.2 was installed, and it worked until I updated it the other day.  I have not tried new work spaces, I am presently moving forward with CCSv4 until v5.2 can get the bugs worked out of it.

    5) If you want files from my computer, I assume it would be best to send them directly to you.  I assume you can send me an e-mail with exact instructions of what you need to diagnose the problem with the update?

    Thanks you for your help!

  • Hi,

    I mean the contents of this folder, which may be hidden.

    C:\Program Files (x86)\InstallJammer Registry\ccsv5

    If you send a friend/conversation request, we can do this offline.

    Best Regards,

    Lisa

  • Hi,

    I am wondering if this issue is due to the unzip utility.   Could you try the 5.3 beta into a new directory?  What unzip utilities do you have?  Is there a way you can double check what your environment is set to use?

    Best Regards,
    Lisa

  • I use Win Zip, and always have.  I have not had a problem yet with Win Zip.  CCS may have a problem with Win ZIP, I do not know?

    It sounds as though I need to remove CCSv5.2, and get  v5.3 when it is ready for the public?

    I need to stay focused on getting projects to market, and not fixing the compiler.

    Would it be posable to send me a CD when 5.3 is ready?  This would eliminate the file zip program issue you feel is the problem.

  • From your install log, it looks to me like the following has occurred: the first phase of the update succeeded in downloading the front-end portion of the update. After CCS restarted, second phase of the update was invoked (CCS has to be restarted to apply the update because that are in use cannot be modified). When the second part of the update started running, it had problems accessing the update site.This caused the a sequence of zero byte files to be downloaded. When the update program went to unzip the zero byte files, it complained about corruption in the files.

    I was able to reproduce a very similar looking failure by fiddling with the network connectivity during the post-restart phase of the update. I was wondering if something similar would happen if the network proxy was set using something other than the usual system proxy settings, but I wasn't able to find a case where the method the proxy was set had an effect. 

    None of this matters to you, but I wanted to provide an explanation of what seems to have happened. I was also wondering if you recall experiencing any network connectivity issues, or if there is anything unusual about how your network proxy is set?

    The simplest way to get v5.3 would be to download the zip file from the download site. There should be no problems with unzipping or installing it this way. Using the full zip download would avoid the installer looking on the network for portions of the install content.

  • Good work Andy,

    1) Yes, my network went down after the reboot because I thought that the network was no longer needed.

    Gee, how about a message that warns the operator to reboot and leave the computer hooked to the internet to complete the install?

    My instrumentation computer is only connected to the internet when I upgrade CCS.  It is an off line computer due to confidentiality agreements.

    2) Do you recommend removing CCSv5.2 before an install of v5.3 beta for a clean install?

    3) What about the license,  will the 5.2 work? 

  • Hi,

    we regularly have multiple versions of ccs on our machines so that is no issue at all.   CCSv5.2 and v5.3 are licensed the same.   If you have a license you will be able to have both installed and select which to use.  Although it should not affect a new installation, it might make sense to clean up the non working version ... why keep it.

    So ... the best suggestion might be to go and reinstall from start into a fresh directory the versions you wish to try.    You can find them here:

    http://processors.wiki.ti.com/index.php/Download_CCS

    Give that a try and keep us informed.

    Best Regards,
    Lisa

  • FYI, I have filed a defect to improve the error recovery and reporting for this scenario.