• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 701 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 V5 Crashes Windows on Terminate

Daryl Lee
Intellectual 270 points

Other Parts Discussed in Thread: TMS320F28016

I'm finally set up to use CCS 5 as a full debugger, and I get a Windows crash and forced immediate (within one minute) reboot "most of the time" when I click the Termnate button (red square) in the debugger.  Here are the details:

Windows 7-64 on a Macbook Pro Bootcamp environment.  This is my almost full-time working environment and is stable for all other applications.  XDS100-V2 JTAG emulator connected to an Olimex TMS320-P28016 development board.  That board has a TMS320F28016 processor on it.  Code Composer 5; I ran Check For Updates a few minutes ago and got "No updates found".

The crash occurs when I click the Terminate button.  It seems to be slightly safer if I have clicked Pause first, but if I am stepping through the program, it still happens frequently.  I'm open to a workaround.  Right now I just pause the debug session and disconnect power to the development board to stop what ever is there.  Somehow that seems less than ideal. :)

I've looked in the /Users/daryl/AppData/Local/.TI folder for a .dmp file and there is none.

 

  • 0
    TI__Guru*** 130875 points

    Hi Daryl,

    have a look at this wiki to see if there any error logs etc you could send.

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS

    Also, please try renaming ctools.dll.   Is this happening for all workspaces and projects?

    Please keep us posted. 

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Intellectual 270 points

    Renaming ctools.dll seems to have done the trick.  I was getting the crash on both of the two example projects I'm working with.  Now I get it on neither.  Also, it appears that I don't have to Pause before Terminate.

    So what have I lost by renaming ctools?  (Other than the crash and reboot, which I will not miss!)

  • 0 in reply to Daryl Lee
    TI__Guru*** 130875 points

    Hi Daryl,

    ok glad to hear that worked.  This may remove a couple advanced debugging features unfortunately like watchpoints (potentially also breakpoints but these should still be ok)

    Would you be able to send us the error logs and any dump files generated?  (.dmp)

    Would you be able to confirm CCS Version?   This problem was something that actually should be fixed and we would like to check whether it is a new or persistant bug possibly.

    Information on where to find the logs and information to send can be found here.

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS

     

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Intellectual 270 points

    My CCS version is Version: 5.1.0.201110010900, Build id: N201110010900

    I went to the link you gave to find error logs and dump files.  As for Eclipse error logs, I have no "View->Other->PDE Runtime" available.  However, I did find a Window->Error Log menu item.  I didn't find a way to export that, so I did a screen shot (is there no "attach file" on this forum?)  All the errors before 3:00PM were "with problem", after that "problem solved".  The other log files seem not to exist.  I say "seem" because the link you gave me is for CCS 4, and I'm guessing that all that sort of thing should be carried over to CCS 5.

    I'd like to be more help.  I can rename the ctools.dll back and run things again, if you can give me specific instructions.

  • 0 in reply to Daryl Lee
    TI__Guru*** 130875 points

    HI Daryl,

    You should be able to attach a file the same way you attached the screenshot.  If you have problems, please let us know.  Otherwise you can also attach it in a friend request if you wish.

    The logs would help us to investigate this and I have already started to pull in a couple development colleagues here.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    TI__Intellectual 1785 points

     

    Daryl,

    We've made some fixes in this area in the last couple of builds of CCSv5.1. It would be more usefull to us if you tried the GA version of CCS (v5.1.0090) and see if the problem still persists. If you have time, would like to hear back from you on this.

    Raj

  • 0 in reply to Raju Pandey
    Intellectual 270 points

    Mirabile dictu!  Not only does that seem to have cleared things up nicely, but I like the look and feel of the new debugger environment much better.  I've only given it a couple of quick checks, but it seems to be working as I'd like.  The debugger perspective seems much more efficient.

    Thanks for the suggestion and all the work you guys put in!