Can't Kill ccstudio.exe Process After Crash

Craig,

I'm sorry you are hitting this issue. It has been a while since we had users reporting this problem.

Have you had a look at these threads and tried the suggestions there? If killing javaw.exe in the Tasks Manager also does not help, maybe you could try the suggestion in the second post for forcefully killing the processes?

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/74417

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/3391/206750#206750

I STILL can't kill it even with both of those suggestions!

javaw.exe doesn't show up in my processes after a crash.

When I try pskill with the process name, it hangs until I open CCS again. Then it tells me it killed 100s of processes. Hmmmm.

Using the PID, it claims it kills it right away but it's still there. 

EDIT: I just let the pskill -t ccstudio.exe run for about 10 mins, then I opened up CCS. That's a lot of processes, something's wrong there.

Hi,

Quick question: did you try to kill the processes with an elevated command prompt? That could help killing these processes.

Hope this helps,

Rafael

desouza, good suggestion but it didn't do it :/

Trying to pskill it by name still hangs up too. I really need to figure this out, it's killing my productivity.

EDIT: CCS is crashing every time I stop the debugger now. I can restart my computer but it's a temporary fix.

UPDATE: I did a reinstall of CCS 6.1 and it seems to be MUUUUUUUUCH better. I hope I didn't jinx it!

UPDATE 2: Annnnnnnd I jinxed it. It crashed, can't kill process...

It consistently crashed when I terminate a debug session.

Craig Rettew said:

It consistently crashed when I terminate a debug session.

Can you capture a debug server log of the crash and send it to us? You can enable debug server logging as described here just prior to the action that generates the crash, (ie) terminating the debug session.

I think I enabled it. Does '0' mean it's working? I captured a crash if it's working. Where do the logs live?

Craig Rettew said:

Where do the logs live?

You can specify where to save the logs by using eval("DEBUG_LogRedirect") prior to eval("DEBUG_LogEnable"), so something like below:

Ok, I've captured the crash. I'm not sure what you need to see in the log file so I attached the whole damn thing.

ccs.log

EDIT: It referenced this on the last line of the log file:

0x00002894 311498 1  ERT E: A hang occurred on thread 0x0000237C - dump file written to "C:\Users\Craig\AppData\Local\TEXASI~1\CCS\ti\2\dmp\/hang_77c27ec2-cde1-4a7e-b91e-9f24ecdc3f4a.dmp"

So here is that file (changed extension to .txt so it would  upload):

hang_28_77c27ec2-cde1-4a7e-b91e-9f24ecdc3f4a.txt

CCS is hanging on a call to close a handle to the USB port. Since you found cannot kill the user-mode ccstudio.exe process, the hang is probably occurring in the kernel mode driver.  

Assuming you are able to load and debug target programs normally and the hang on exit is the only problem you are seeing, it seems unlikely there is hardware problem with your board.  Maybe the first thing to check is the version of the installed ftdi drivers.  If you browse to c:\ti\ccsv6\ccs_base\emulation\drivers\CC3200\ftdi and run dpinst64.exe, you should see something like the dialog below. Could you confirm the driver versions match?

Looks like my drivers match:

I've occasionally had this same problem with CCS 6.1. What worked for me is unplugging my JTAG and the process ended on it's own.

This was after I tried killing it with the task manager a couple times so if the process doesn't close on it's own, try killing it again after unplugging your JTAG. I think AndyW is correct with the USB driver hypothesis.