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: CCSv8 - Crashes as soon as splash screen appears

Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

Hi,

My problem (as far as I'm knowledgeable) doesn't go much deeper than what the thread title says: whenever I try to launch CCSv8 (either directly or through a shortcut), the splash screen flashes for a split second and then disappears without CCS progressing further in starting up. This is on a completely fresh install (offline install, only selected SimpleLink MSP432), in that I removed all traces of CCS prior to installing it again. This happens whether I run as administrator, or from whatever drive.

I would provide logs if they would help, but I'm not sure where to look for them.

Thanks, Layne

  • Hi Layne,
    Which exact version of CCS are you using? And on which host OS (provide the full version number of the OS)

    Thanks
    ki
  • I'm having this issue while trying to use CCSv8.2.0.00007 on Windows 10 version 1803 (OS build 17134.345). The problem persists when using CCSv7 as well.

    Just to further clarify the problem, when it's installed on a USB drive and run on another computer, the program starts and runs normally. Only when I use it on this PC does CCS crash in the way I've described (whether that be from the USB or not).
  • Layne Hoelscher said:
    Just to further clarify the problem, when it's installed on a USB drive and run on another computer, the program starts and runs normally. Only when I use it on this PC does CCS crash in the way I've described (whether that be from the USB or not).

    If I understand correctly, CCS is installed on a USB stick. When plugged into your Windows 10 b1803 machine, it does not run (crash). When you take that same stick and run it from another PC, it runs ok? What is the OS of that PC where it runs fine? Which PC was used to install it on the USB stick?

    Thanks

    ki

  • I installed CCSv8 to both the original computer (the one it crashes on) and to the USB stick using the "crashes-on" computer. The build number for the computer that CCSv8 launches fine on (running from the USB install) is also 1803 (Windows 10).

  • Do both (working and non-working) PC have basically the same setup (security software like antivirus, etc)? If so, then the only other thing I can think of is to see if the MSVC redistributes are properly installed:
    software-dl.ti.com/.../ccs_troubleshooting.html

    Also, can you go to .\ccsv8\eclipse and launch the IDE by executing 'eclipse.exe'?

    Thanks
    ki
  • The only difference that I can see having any effect is that the non-working PC has Avast antivirus whereas the working one(s) have another form of antivirus (Windows Defender only or other antivirus software). Launching the eclipse executable results in nothing happening.
  • Sorry for the delay, I was out of the office for some time.

    Can you try temporarily disabling Avast to see if that has any impact?
  • Diabling the Avast shields doesn't remedy the problem, even after a restart while they are disabled. I did make sure that Avast was disabled while I installed it as well. I might later try uninstalling Avast to see if it has any effect.
  • Hi Layne,
    Did you try uninstalling Avast? I really doubt that will resolve it since you already disabled it. But I guess we are grasping as straws here.

    Also browse to :
    .\ccsv8\eclipse

    And try launching CCS from the command line via:
    > ccstudio -debug

    This will open a console with debug messages being displayed. I'd like to see what messages are in the console before the crash. Now one big issue I see is that I think it may kill the console when CCS crashes. This would make it hard for you to grab a snapshot before it goes away. I don't think you can pipe the messages to a file either
  • Hello,
    I haven’t heard back from you, hence this issue is being closed. If you wish to continue the discussion, please post a reply with an update below (or create a new thread).

    Thanks,
    ki