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.

CCSv6 Beta 4 version 176 stops responding (windows 7)

Guru 20045 points


Hello,

I am having this issue where CCSv6 Beta 4 version 175 stops responding every once in a while. 

Ending the program seems corrupt my build file, because CCS wants to rebuild all of my files again.

I don't know if it's the issue or not, but I am using an XDS100v2.  It seems to happen when I click outside of the CCS application; however, I am not too sure if that is what's causing the issue.

Please help.

Thanks

  • Hi,

    This happens during loading the code or building the code? CCS freezes right?

    Regards,

    Gautam

  • No, it doesn't occur during loading of code or building of code. 

    It just froze right now.  Before it froze, I had enabled automatic updates of the expression windows. 

    I also noticed the following:

    1. CCS indicated it was refreshing paths and windows (0%)

    2. The console showed:

          CS28xx: Unable to determine target status after 20 attempts.

          CS28xx: Breakpoint Manager: Unable to remove requested AET Job

          CS28xx: Breakpoint Manager: Unable to remove requested AET Job

  • Hi,

    do you see any error logs (hs_err ...) or .dmp (dump) files generated?  These are what might help us determine what might be going on.  Also, if this is reproducable, some steps for us to try here could also be helpful in finding the issue.

    Best Regards,

    Lisa

  • Hello Lisa,

    Can I post the logs to you directly?

    Stephen

  • Hi Stephen,

    my ID is a link you may use for a friend/conversation request.

    Best Regards,

    Lisa

  • stevenh said:

    It just froze right now.  Before it froze, I had enabled automatic updates of the expression windows. 

    I also noticed the following:

    1. CCS indicated it was refreshing paths and windows (0%)

    2. The console showed:

          CS28xx: Unable to determine target status after 20 attempts.

          CS28xx: Breakpoint Manager: Unable to remove requested AET Job

          CS28xx: Breakpoint Manager: Unable to remove requested AET Job

    Based on that, does it mean that CCS freezes when debugging?

    If so:

    1) Once CCS has frozen, does unplugging the XDS100v2 from the USB port of the computer unfreeze CCS?

    2) Enabling CCS Debug Server Logging and supplying the debug server log file might give more information.

  • Lisa: Ok.  How can I email you the log file using that method.

    Stephen

  • Hello Chester,

    1) Once CCS has frozen, does unplugging the XDS100v2 from the USB port of the computer unfreeze CCS?

    unplugging the XDS100v2 doesn't unfreeze CCS. 

    2) Enabling CCS Debug Server Logging and supplying the debug server log file might give more information.

    Ok, I look into that.

    Stepen