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 5.5 Update problem

Other Parts Discussed in Thread: CCSTUDIO

Hi

I'm trying to update from CCS 5.3 to 5.5. I get an error message saying that not all the components have installed correctly, and asking me to post a ZIP of the log file.

Any help resolving this would be welcome.

3583.60556FE5-C1A1-4061-8DF8-FFB8393BAE2D.zip

  • Hi Nigel,

    I think updates may still be temporarily taken down.  

    No matter what, I would really just do a full fresh installation of v5.5.   Use a new directory.  The updates have been too unreliable.

    Please keep us informed how that goes.

    Best Regards,

    Lisa

  • Hi Lisa

    I followed your advice & tried a fresh install of CCS 5.5 to a new directory. I got a similar error message saying it failed to install com.ti.ccstudio.msp430.emu.win32. I've attached a ZIP of the current log file.

    Kind regards,

    Nigel

    6724.60556FE5-C1A1-4061-8DF8-FFB8393BAE2D.zip

  • Hi Nigel,

    are you sure you tried a fresh installation?  I only see a log for an update attempt to v5.5.  Could you clean out the logs and installation(s) and try again from the start and send in that log?

    Best Regards,
    LIsa 

  • Hi Lisa

    Thanks for your help. I'm not sure what happened to the logs. It certainly made a partial installation to a new directory.

    Anyhow, I can't use the uninstaller for CCS because the installation is broken. So I did the following:

    • Delete the two directories CCS5 had been installed into.
    • Run CCleaner and AusLogic registry cleaners. 
    • Reboot the PC. 
    • Downloaded the CCS 5.5 off-line installer. 
    • Disconnected the PC from the network. 
    • Disabled Sophos anti-virus
    • Run the CCS 5.5 off-line installer.

    Unfortunately the installation stops at the same place with the same error message. I've attached a ZIP of the log file (hopefully).

    Kind regards,

    Nigel

    1777.60556FE5-C1A1-4061-8DF8-FFB8393BAE2D_3.zip

    <Edit> The error message indicates that there's a problem installing the MSP430 emulator stuff. When I look in the installation directory I find another set of install logs, which I've attached here...

    7181.install_logs.zip

    In the MSP430pack log file it says:

    Unknown error while running C:/TI_CCS/ccsv5/ccs_base\emulation\drivers\msp430\DPInst\DPinst64.exe  /q /se /sa /path "C:/TI_CCS/ccsv5/ccs_base\emulation\drivers\msp430\USB_eZ-RF"
    

    So it looks like there's a problem installing the eZ-RF USB driver. It seems to be running the 64-bit installer DPinst64.exe instead of the 32-bit installer DPinst.exe, even though it's on a 32-bit platform (Windows XP Pro SP3).

    In fact, I first saw this error message when I just tried to update the MSP430 emuator component from within CCS5.3, which is consistent with the problem I'm having now.

    If this is right, do you have a fix for the MSP430pack installer?

  • Hi Nigel,

    the installer decides whether to install the 64bit or 32bit installations depending on the existence of the  directory %SystemRoot%\SysWOW64 (normally C:\windows\SysWOW64) . This directory should only exist on 64 bit versions of windows. If this directory exists on your 32bit Win XP Pro installation, the installer assumes to be run under a 64 bit windows and tries to execute the 64 bit versions of dpinst.exe during driver installation. Could you check if the directory is present on your machine?

    Best Regards,

    Bob

  • Hi Bob

    I confirm that the directory %SystemRoot%\SysWOW64 does exist on my system. The only files in it are DLLs for a driver for a P&E Micro emulator. I guess the P&E driver installer is lazy and installs both the 16 and 32-bit DLLs without checking which is actually needed. Presumably that check is done at run time.

    Anyway, I have renamed the %SystemRoot%\SysWOW64 folder and I now find that CCS 5.5 installs correctly.

    Thanks to you and Lisa for helping to resolve this issue.. 

    Kind regards,

    Nigel