• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Subscribers 53 subscribers
  • Views 4895 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/CC3200MODLAUNCHXL: CCS 7 "Not Responding" when finishing Debug, locks workspace until reboot

Xeeb
Intellectual 290 points

Part Number: CC3200MODLAUNCHXL

Tool/software: Code Composer Studio

Hi!

When I stop the debugger, Code Composer Studio stops responding. I have to right click the program on the taskbar and select close.

On restarting, I have to use a different workspace because the one from before the lockup is now "in use" and is not available until I reboot.

Any advice or workarounds?

  • 0
    TI__Guru**** 450771 points

    Hello,

    Xeeb said:
    When I stop the debugger, Code Composer Studio stops responding. I have to right click the program on the taskbar and select close.

    When you use a new workspace, does the issue happen again?

    Xeeb said:
    On restarting, I have to use a different workspace because the one from before the lockup is now "in use" and is not available until I reboot.

    Regarding the locked workspace, can you browse to the workspace folder and inside the .mestadata subfolder, can you delete the .lock file in there? This should free up the workspace

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 290 points

    Ki-Soo Lee said:

    Hello,

    Xeeb
    When I stop the debugger, Code Composer Studio stops responding. I have to right click the program on the taskbar and select close.

    When you use a new workspace, does the issue happen again?


    Yes. I've actually created 4 work spaces and it locks each on Debug end. 

    Example Worskapces A, B, and C:

    Open Workspace A, debug, end debug, CCS crashes.
    Terminate and restart. Unable to use workspace A as it is "In Use"
    Select Workspace B, debug, end debug, CSS crashes
    Terminate and restart. Unable to use workspaces A or B, select C. etc.

    Ki-Soo Lee said:
    Xeeb
    On restarting, I have to use a different workspace because the one from before the lockup is now "in use" and is not available until I reboot.

    Regarding the locked workspace, can you browse to the workspace folder and inside the .mestadata subfolder, can you delete the .lock file in there? This should free up the workspace

    Thanks

    ki

    I am not able to delete the file "because the file is open in ccstudio.exe" - however, there is no ccstudio.exe in taskmanager. Good times :)

  • 0 in reply to Xeeb
    Intellectual 290 points
    @Ki-Soo Lee any other suggestions?
  • 0 in reply to Xeeb
    TI__Guru**** 450771 points
    Hello,
    Please provide the crash/hang dump files and debug server logs mentioned in the link below:
    processors.wiki.ti.com/.../Troubleshooting_CCSv7

    Note that the debug server log needs to be explicitly enabled first.

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 290 points

    Here you go. The work space that I ran debug with was named "Experiment" - I had to use another workspace to get the logs, as that one locked.1526.logs.zip

  • 0 in reply to Ki
    Intellectual 290 points

    Ki-Soo Lee said:
    Hello,
    Please provide the crash/hang dump files and debug server logs mentioned in the link below:
    processors.wiki.ti.com/.../Troubleshooting_CCSv7

    Note that the debug server log needs to be explicitly enabled first.

    Thanks
    ki

    HI Ki! Any follow up?

  • 0 in reply to Xeeb
    TI__Guru**** 450771 points
    Hello,
    My apologies for the delay. This thread has slipped from my radar. I am investigating this currently

    Thanks
    ki
  • 0 in reply to Ki
    TI__Guru**** 450771 points
    It appears that when terminating the debugger, the debugger first makes a request to terminate the ICDI connection to the target and blocks on this call, forcing you to terminate CCS manually. But there is some process that is still hanging on, keeping the workspace locked. One thing to try is when you terminate the debugger, try unplugging the usb cable that connects the PC from the target.

    Judging by your logs, looks like you are using CCSv7.1.0.00016. Which TI emulation pack version are you using?

    And is the issue easily reproducible for you? To reproduce, can you simply start a debug session for your target, connect to it, and then try to terminate the session?

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 290 points

    The emulator info is:

    TI Emulators 6.0.576.0 com.ti.emulation.pack.win32.feature.group Texas Instruments

    If I unplug the board after I end debug, then I can close CCS7 normally, BUT - when I reopen it, it will not run debug again - it locks up and I have to restart, which locks the workspace, etc.

    The issue is easily reproducible, I just have to reboot the computer to unlock the works pace to reproduce each time :)

    @Ki-Soo Lee

  • 0 in reply to Xeeb
    TI__Guru**** 450771 points
    After you successfully shut down CCS and before you restart, can you try checking which process has control of the .lock file? There are many utilities like Unlocker that can be used to check which process has control.

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 290 points

    According to Unlocker, the process locking the file is CCSTUDIO.exe - though I don't see how it can have it locked if it isn't in the list of running processes.

  • 0 in reply to Xeeb
    TI__Guru**** 450771 points
    Very strange. There must be some child process running that don't get shut down properly. Next time when you terminate the debugger, do not shut down CCS but instead, kill it from task manager. Right click on the ccstudio process and select "End Process Tree" in the context menu. That should kil ccstudio and any child processes. Then try to see if you can remove that lock file