• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 590 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.

Original question:

Can't Kill ccstudio.exe Process After Crash

CCS: Can't kill CCStudio.exe process after crashing

Freddy Gauss
Intellectual 300 points
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

Code composer studio tends to hang and / or crash now and then. That's not  a big deal, it's not too common and I'm somewhat used to it. However, when it does so I can't kill the process and therefore can't open another instance in the same workspace. This has started happening once I upgraded to Windows 10 and CCS 8.

Currently my only solution is to reboot, which is terribly inconvenient. Anyone have any ideas?

EDIT: I suspect it may have something to do with the JTAG (FTDI?) drivers as the crashes happen when attempting to launch a debugging session. If the driver itself crashes, it may be able to present symptoms like this?

  • 0
    Guru 26200 points

    Hello Freddy,

    could you be a more specific before someone from TI will reply?

  • 0
    TI__Guru**** 472001 points
    Hi Freddy,
    Did you try some of the tips in the below topic:
    software-dl.ti.com/.../ccs_troubleshooting.html

    As for why you cannot kill ccstudio.exe, it is hard to say and could be because of a dependent process that is prevent CCS from being forcibly shut down. It would be better if we can address the hang in the first place.

    Thanks
    ki
  • 0 in reply to Ki
    Guru 39650 points

    Hello Freddy,

    One comment.

    I have same similar experience with some older versions of FTDI drivers used with ours software. Driver hangs during closing COM port and don't allows close parent process/application. WinAPI for closing handle /CloseHandle()/ internally calls FTDI driver. And at some case calling of driver function hangs internally. Because driver is running at kernel context, you have a issue...

    Solution of this situation could by physically disconnect FTDI from USB port and connect it again.

    Jan

  • 0 in reply to Ki
    TI__Guru**** 472001 points
    Hi Freddy,
    Just following up to see if the issue still exists and if you tried some of the suggestions mentioned on the thread.

    Thanks
    ki
  • 0 in reply to Ki
    TI__Guru**** 472001 points
    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