when in debugging mode with CCS4 and xds510LC, my lap topcrash

Hi Bertrand,

could you please provide a bit further information.

- is this limited to the one project you are working on?

- could you possible zip and send any error logs and .dmp files generated?

- could you please provide more details - is the crash at a very specific step each time?  Is it reproducable? 

- does the same code cause any issues on other PCs?

- have you recently changed anything in your environment?  Updates?  New PC?  Was this project always seeminly crashing?

Any further information would be helpful.

Best Regards,
Lisa

Bertrand,

Bertrand Poulain said:

it happened more when termiante the debugging mode.

Are you using the latest build of CCSv4, 4.2.4? If not, could you please update to this version to make sure you are availing of all bug fixes to date?

Regarding CCS crashing when terminating a debug session, please take a look at this related thread. As mentioned there, could you try renaming the file ctools.dll and see if makes the crash go away? If it does, it would be very helpful if you could provide the diagnostic logs. The link in the other post describes how to generate the logs. You would need to go back to using the original ctools.dll before generating the logs so the crash is reproducible. You can then zip them up the logs and attach them here.

We have only one project using CCS . my laptop crashed three times yesterday when terminating the debug session and once while reprogramming the flash memory before starting a debug session. I started using CCS 6months ago and it always happened but now is more often. 

I will try to create the log files.

thanks,

Bertrand

Here is my diagnostic log file.

I will rename ctools.dll and istall the latest CCS

8546.attachement.zip 

I have attached the log file in an other post

Hi Bertrand,

the attached zip file seems to have come in empty/corrupted for me.  Could you please repost.  Also please keep us informed how the renaming and reinstallation goes.

Best Regards,
Lisa

Hi Bertrand,

glad to hear that Aarti was able to point you to the ctools.dll issue and things now seem much better for you.

Best Regards,

Lisa

Bertrand Poulain said:

CCS4 has not crashed since I have renamed the ctools.dll

Glad to hear this. We'd still like to get to the root cause for this, so could you please take a few minutes to provide some additional information?

- which version of CCS are you using? If you're on a version older than 4.2.4, could you either install 4.2.4 in a separate location or update your current version to 4.2.4 and verify if the problem still persists (with its original ctools.dll in place)?

- if v4.2.4 does crash, could you please generate a few more logs and send them to us? Note that you would need to keep the original ctools.dll in place before running CCS and reproducing the issue.

The logs that would be most helpful are the Debug Server logs and Trace logs. The debug server log can be enabled from 'Help->CCS Support Activities' menu. The ctools/trace log requires a more manual process. This page describes the procedure to generate both: http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#CCS_Diagnostic_Logs

 I am using CCS 4.2.3.00004

I will install CCS4.2.4 and rename ctools.dll

thanks

It did not take long to trigged a blue screen.

I ran  ccs Version: 4.2.4.00033  in debug mode, terminated the debug mode and it crashed.

0410.debugServerLog.zip

6215..TI-trace.zip

Thanks for taking the time to generate and provide the debug logs. I have forwarded these on to the development team so they can analyze it, and we can hopefully have this fixed for a future release. In the meantime, please use the workaround of the renamed ctools.dll.