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.

CCSv4.0 can not disconnect when target power is lost

When the dsp power is cut before CCSv4.0 has finished its disconnect sequence, the CCSv4.0 Progress window does not respond to the cancel nor disconnect buttons (Blackhawk ICE). It times out after about an hour and exits gracefully. If I use Task Manager to abort it, I have a mess to clean-up when I reboot. Is there a parameter to change the CCSv4.0 no-response timeout period?

  • I have this same issue (Blackhawk drivers) and would appreciate a solution.

    What I do is (1) try to remember to disconnect the emulator using the CCSv4 UI before removing target power, and (2) if I do abort the Java engine and restart CCS, then I immediately quit CCS after cleaning up the mess, because quitting saves the orderly setup in the files that do not get saved when the process is terminated.  Between those two workarounds, I can almost barely function.

    Unfortunately, the prototype revision of my DSP platform seems to have an issue where I cannot use the Reset function, and thus I need to power-cycle the DSP to reset it.  This means my workflow is seriously slowed by the 30-minute timeout that Steven and I are experiencing.  Again, a fix for this would be great!

  • Brian, what version of CCS are you using?

    Just want to confirm that the issue exists with the latest CCS versions...

  • Ki-Soo Lee, that is a good question.  I know that I am not running the latest version of CCSv4, because when I tried to update my emulator stopped working.  I was forced to downgrade to an older version, and thus I know that I am not on the latest.

    If you are saying that the problem has been fixed in recent releases, then I might not be able to help.  I have a demo copy of CCSv4, because I spend my money purchasing CCS 3.3 for product development.  Thus, I think I'm stuck with the old CCSv4 until my demo expires.  Meanwhile, I'm also trying to get an officially licensed copy of CCS 3.3 working.

    Sorry, maybe Steven can say which version of CCS he is using, and perhaps that will help get to the bottom of the issue.