• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 54 subscribers
  • Views 2100 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 crashes if debugger disconnected while debugging

Ben Sheard
Prodigy 30 points

Other Parts Discussed in Thread: CCSTUDIO

Hi

Is it a known issue that CCS crashes if you disconnect the debugger while in the debug window? It sounds like a stupid thing to do, but it happens more often than you'd think.

I'm using the Tiva C Series Launchpad with the in-circuit debug interface.

  • 0
    Guru 192875 points

    Hi,

    I've noticed the same thing too; but I've started ignoring it :)

    Regards,

    Gautam

  • 0
    TI__Guru**** 173310 points

    Ben Sheard said:
    Is it a known issue that CCS crashes if you disconnect the debugger while in the debug window?

    Which version of CCS are you using? Do you see this behavior fairly consistently? 

    There were some stability issues likes these in older versions of CCS but it has been greatly improved in the more recent versions. In CCS 5.5, I don't see CCS crash if the ICDI is disconnected while in a debug session on a Tiva C Launchpad. Rather there is a message that "Connection with the target was unexpectedly lost". At this point I can reconnect the ICDI, reconnect to target device and reload the program.

    If are able to reproduce the crash consistently with a recent version of CCS, please provide additional details on the exact steps you take so we can try to duplicate it at our end.

  • 0 in reply to AartiG
    Prodigy 30 points

    Hi there

    Thanks so much for the response. I've just realised my Code Composer is out of date - version 5.2. I am busy upgrading now and will report back if I'm still having the same issues.

    Thanks once again.

  • 0
    Prodigy 30 points

    Hi,

    I'm having the same problem with the CCS v5.5 (Win XP) using the Tiva C Series Launchpad.

    I've followed all the recommendations in this post, but this problem still happening. =(

  • 0 in reply to Francisco Carvalho Neto
    TI__Guru**** 173310 points

    Francisco Carvalho Neto said:

    I'm having the same problem with the CCS v5.5 (Win XP) using the Tiva C Series Launchpad.

    I've followed all the recommendations in this post, but this problem still happening. =(

    What are the exact steps you follow to get CCS to crash? Please describe them in detail so we can reproduce the behavior. Does the crash happen consistently every single time or is it intermittent?

  • 0 in reply to AartiG
    Prodigy 30 points

    AartiG said:

    What are the exact steps you follow to get CCS to crash? Please describe them in detail so we can reproduce the behavior. Does the crash happen consistently every single time or is it intermittent?

    Hi AartiG,

    Now, I'm doing the Tiva C Workshop Lab's, and the CCS crashes while i'm debuging, and happens intermittently (between the time i resume until terminate the debug).

    If I try to resume any code of the workshop labs, and let the debugger running, in a few minutes or sometimes in  seconds, the CCS will stop responding and even after I close the CCS by Task Manager of Windows, the CCS cannot be reopened claiming that the workspace folder cannot be launched. Then the CCS only back to work normally if i reboot my notebook.

    I wanna know where I can find some tutorial to how to obtain the log files of the crashes of CCS.

    Thanks, 

    Francisco

  • 0 in reply to Francisco Carvalho Neto
    TI__Genius 16510 points

    Hi Francisco,

    I would like to verify my understanding of the issue in your description. When you say crash, you mean the CCS GUI becomes unresponsive. The GUI is still displayed, but you cannot do anything. You cannot close it by clicking the "x". Your only option is to kill the ccstudio.exe process from the Windows task manager. Even after killing the CCS process and restarting CCS, you cannot open the same workspace you were using. CCS says the workspace is in use. 

    Is this description correct?

     

  • 0 in reply to Ben Sheard
    Prodigy 30 points

    Sorry for the late reply, but just to confirm that upgrading to the latest version did solve the issues I was experiencing.

    Thanks again.

  • 0 in reply to AndyW
    Prodigy 30 points

    AndyW said:

    Hi Francisco,

    I would like to verify my understanding of the issue in your description. When you say crash, you mean the CCS GUI becomes unresponsive. The GUI is still displayed, but you cannot do anything. You cannot close it by clicking the "x". Your only option is to kill the ccstudio.exe process from the Windows task manager. Even after killing the CCS process and restarting CCS, you cannot open the same workspace you were using. CCS says the workspace is in use. 

    Is this description correct?

    AndyW,

    Yes, I agree with your description. Everything you said is correct, the only thing different is when I kill the process in task manager, the unresponsive CCS GUI window closes, but the ccsstudio.exe continue working in the process list, no matter how many times I try to close this process. Then the only way is rebooting the machine to remove this process. 

    One important issue I'd forget to mention, is that I'm using a Macbook with a VM (Virtual Machine, Parallels v9) to execute the Windows XP.

    It's quite complicated to describe this crash, every time i reboot the Windows to kill the CCS process makes the shutdown WindowsXP procedure unresponsive, needing to "force quit" the VM. After that, the VM cannot reopen the XP (informing problems on initialization of XP),  unless rebooting the notebook OS (OS X Mavericks(10.9)). After rebooting, everything turns back to work normally.

    Regards,
    Francisco

  • 0 in reply to Francisco Carvalho Neto
    TI__Genius 16510 points

    Fancisco,

    Thanks for the additional information. That helps a lot.

    What you describe sounds like a "zombie" process is being created. The term is used to describe cases where a call is made to a kernel device driver but the that call never gets a response. The process cannot be completely killed because there is still an open kernel API call so it remains in the task list as a "zombie". The only way to free up whatever resources remain locked is to reboot the OS.

    As you are using XP from a VM, there is probably an incompatibility between one of the device drivers and the VM's virtualization of that hardware. That could be a bug in the device driver or the VM's hypervisor. Either way, I'm not sure I'm going to be able to help much with this.  Is it an option of you to run Windows natively (IE not with a VM)?