• State TI Thinks Resolved
  • Locked Locked
  • Replies 14 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1156 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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: Code Composer Studio silent installation hangs on VMs

user6016437
Prodigy 75 points

Tool/software: Code Composer Studio

We are trying to update our silent package for Code Composer Studio from Version 8.0.0.00016 to 9.0.0.00018.

 

We're executing the setup with the following parameters:

"--mode unattended --unattendedmodeui none --optionfile setup\optionfile.txt --prefix C:\ti"

 

On physical computers the silent installation works without problems, but on virtual machines we have a strange behaviour. Sometimes the installation hangs at a certain point without an obvious reason. The setup.exe is still running but it does nothing for hours.

 

OS is a clean Windows 10 (1809).

 

What we've tried so far:

  • Installing the software over GUI -> works fine
  • Autologon of the user who installs the software (admin) before the installation starts (screen not locked)
  • Disabling Windows Defender during installation (with Powershell command or Group Policy)
  • Comparing the log files of working and not-working installations -> no errors found

 

 

  • 0 in reply to user6016437
    TI__Guru**** 171044 points

    Hi,

    Thanks for sending such detailed post. Do you have the logs of a successful install on the physical machine? This would be useful to compare the differences between two identical sets of installation options.

    Also, do you have the optionfile.txt? That could be useful to try and reproduce this issue here.

    Interesting; the log files show the installation goes quite ok up until the very last bit, thus the problem seems to be either in creating the shortcuts on the desktop area or something else. Despite we don't officially validate CCS on VMs, the differences between the VM and the physical machine shouldn't matter, apart from aspects such as network access problems (which shouldn't influence this), virtual disk or other machine settings (delays in disk access, power saving issues, etc.).

    At last, which VM engine are you using?

    Regards,
    Rafael

  • 0 in reply to desouza
    Prodigy 75 points

    Thanks for the fast answer. Here are all the logs (VM - working / VM - hanging / Physical - working) and our optionfile:

    install_logs_2.zip

     Our VM engine is Hyper-V Version 10.0.14393.0.

    We will try to disable the shortcuts in the option file and test the installation again.

  • 0 in reply to user6016437
    Prodigy 75 points

    We tried to disable the shortcuts in the option file but the setup is still creating desktop and start menu shortcuts. Behavior still the same, on one VM it works on the other not.

    Fullscreen optionfile.txt Download 
    CreateDesktopShortcut: No
CreateQuickLaunchShortcut: No
InstallDir: c:/ti/ccs901
InstallMode: Standard
LaunchApplication: No
edition_selection: Custom
feature_selections: EMU_TI EMU_BH EMU_SD IDE_MSP430 MSP430_BUILD_DEBUG MSP430_GCC_SUPPORT EMU_MSP430 TIVA_STELLARIS_DRIVERS SEGGER_J_LINK SEGGER_J_LINK_DRIVERS JRE JRE32 P2APP ECLIPSE ECLIPSECORE P2TOOLS GMF IDE_MAIN IDE_WORKFLOW DVT_COMMON DVT_UIA DVT_VIA_CCS TIREX XULRUNNER INSTALLER IDE_CHROME IDE_TOOLS_COMMON IDE_GC TARGET_CONTENT_CORE TARGET_CONTENT_CORE_LEGACY NODEJS DS DS_FLASH CLOUDAGENT SYSCONFIG MSVC80 MSVC2012 MSVC2015 MSP430_CGT_HELP CGT_DEFAULTLIBS_MSP430 DMED GCC_MSP430_COMPILER DVT_ENERGYTRACE MSP432_BUILD_DEBUG EMU_MSP432 EMU_MSP432_FLASH ARM_CGT_HELP CGT_DEFAULTLIBS_TMS470 IDE_ARM GCC_ARM_COMPILER DVT_TRACE DEV_SUPPORT_CC26XX EMU_STELLARIS DEV_SUPPORT_CC32XX DEV_SUPPORT_CC3220 DEV_SUPPORT_CC32XX_COMMON DEV_SUPPORT_CC3230 DEV_SUPPORT_CC2538 IDE_C2000 EMU_C2000_FLASH EMU_C2000 GREE_C2000_SUPPORT C2000_CGT_HELP CGT_DEFAULTLIBS_C2800 TIVA_TM4C TIVA_TM4E EMU_HERCULES DEV_SUPPORT_SITARA DEV_SUPPORT_SHARED C6000_CGT_HELP CGT_DEFAULTLIBS_C6000_V8P BBONE_FTDI_DRIVERS IDE_C6000 DEV_SUPPORT_INTEGRA CGT_DEFAULTLIBS_C6000 DEV_SUPPORT_DAVINCI DEV_SUPPORT_OMAP DEV_SUPPORT_AUTOMOTIVE EVE_SIM_TI CGT_DEFAULTLIBS_EVE IDE_C5500 DEV_SUPPORT_C55XX DEV_SUPPORT_C6000 KEYSTONE1 KEYSTONE2 DEV_SUPPORT_MMWAVE DEV_SUPPORT_C6000MC DEV_SUPPORT_UCD31XX DEV_SUPPORT_PGA
product_selections: PF_MSP430 PF_MSP432 PF_CC2X PF_CC3X PF_CC2538 PF_C28 PF_TM4C PF_HERCULES PF_SITARA PF_OMAPL PF_DAVINCI PF_OMAP PF_TDA_DRA PF_C55 PF_C6000SC PF_C66AK_KEYSTONE PF_MMWAVE PF_C64MC PF_DIGITAL_POWER PF_PGA

  • 0 in reply to user6016437
    TI__Guru**** 171044 points
    Hi,

    Thanks for sending the files and the logs and please apologize for the delay; this week we had a few product releases that backed me up completely.

    I am making room on my system to accommodate Hyper-V and see if I run into a similar issue as yours. I will be using a clean Windows 10 dev environment version.

    I will report back.

    Regards,
    Rafael
  • 0 in reply to desouza
    TI__Guru**** 171044 points
    Hi,

    I couldn't make Hyper-V work on my system (perhaps Admin restrictions), but I just tested on VmWare without issues. Unfortunately that does not prove much in one way or another. I will try to see if someone else may have a Windows 10 machine where Hyper-V works and see if they can reproduce this. Unfortunately, at this point I can't promise much, given the operation in Virtual Machines is not tested by us nor officially supported by CCS.

    I will report back to this thread if I find any additional relevant details.

    Regards,
    Rafael
  • 0 in reply to user6016437
    TI__Mastermind 22060 points
    Hi,

    Could you please run the install on the vm where it's hanging with the additional parameters below:
    --syncdebugtrace c:\temp\debug.txt
    where c:\temp is a folder that exists and is writable.

    Thank you,
    Danish
  • 0 in reply to danishinnis
    Prodigy 75 points

    Thank you for your answer. Here's the logfile.debug.txt

  • 0 in reply to user6016437
    TI__Mastermind 22060 points

    The debug trace suggests that the installation scripts have already been deleted. If you're able to reproduce the issue on the same vm all the time, can you give this a try? Add the parameters below to the other command line you're using. It won't delete the temporary folders.  Then we could verify that the files haven't been deleted.

    --test true

    Thank you for your patience.

    Danish

  • 0 in reply to danishinnis
    Prodigy 75 points
    I tried the installation with the parameter, but the result is the same. One VM hangs, the other one works.

    The CCS temp folder (C:\users\<username>\appdata\local\temp\ccs_...) is also present without the "--test true" parameter at the time the setup hangs.
  • 0 in reply to user6016437
    TI__Mastermind 22060 points

    Can you check to see if the file tcl\bin\tclsh exists in the temporary folder that's left behind?

  • 0 in reply to danishinnis
    Prodigy 75 points
    Yes, the tclsh.exe exists.
  • 0 in reply to user6016437
    TI__Mastermind 22060 points
    Hi,
    I'd like to send you a debugging executable via email. If you can accept my friend request, that would be great.
    Thanks,
    Danish
  • 0 in reply to danishinnis
    TI__Guru**** 162295 points

    Was there any progress on this issue?