CCS4 crashes when clicking "Terminate All" to end debug session.

Hi Jim,

Could you provide #2 and #4 of: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/3131.aspx?

Thanks

ki

#2. Vista 32-bit Business Edition, SP2

#4. EKT-LM3S9B92 Stellaris Evaluation Kit (Rev B2) -- Luminary Micro USB (FTDI) Debugger

Thanks,

Jim

Jim - could provide more details on what debug actions you are normally doing prior to terminating the debug session?

These are the basic things that I have done:

1. Build an application.

2. Start the debugger by pressing the "Debug" button -- this opens up the debug view.

3. Once the app is loaded into the device, I press the "Run" button to start the debug process.

4. I can press the "Halt" button and "Run" buttons repeatedly without issue.

5. Everytime I press the "Terminate All" button the app crashes and closes.

Those are the only debug actions that I have performed with CCS4.

Jim - what is the application you are running? Is it a StellarisWare example? I ran a StellarisWare example (hello) on my 9B92 without issue. Everything was fine, no crash on terminate all. The only other difference I have is that I ran on Vista 32-bit Ultimate but hopefully that will not impact anything.

I was running the blinky app. I just tried the hello app and it runs but CCS4 crashes when I click the "Terminate All" button as well. I also have Code Red 3 installed. Could there be some kind of compatibility issue? I don't have problems with the "Terminate" button with Code Red 3.

The CCS4 "Terminate" crash does not appear to be 9B92 application related. Perhaps there is a project setting for the Stellaris Cortex M3 Debugger? I have not changed any of the defaults as far as I know.

Jim

Can anyone at TI help me figure this out? I wanted to evaluate Code Composer for possible purchase but it is unusable to me right now with the consistent crashes every time that I terminate the debugger. Perhaps there is a more formal support procedure that I could go through instead of the forums? If support is not available then I will just have to uninstall Code Composer and use what I know works.

Hi,

To help track this down, could you provide a couple of other pieces of information:

(1) Search you <ccs install dir>/ccsv4 folder for any files that look like "hs_err_pid<some number>.log" (for example: hs_err_pid4044.log). These are created by the JVM and may have some further details about what happened.

(2) Could you refer to this page: http://tiexpressdsp.com/index.php/Troubleshooting_CCS , and under "Debug Server Logging", follow the unstructions to capture the DS logging output for what happens just before the crash.

I hope of these will give us something to go on as we are not able to see the problem locally. If these files don't point to a direction, we'll contact you regarding next steps.

Hi,

I could not find any "hs_err_pid<some number>.log" files. I did collect some files using the Debug View program and from the Eclipse error logs. Please see the attached zipped file. I'm not sure that the target_config.ccxml is the one that I am using? I copied it from the StellarisWare (5570) "blinky" project folder that I last built and debugged.

Also note that the Stellaris example projects are linked to my "C:\StellarisWare5570AllBoards\boards\ek-lm3s9b92\" directory and are not located in the "Workspace."

I'm just trying to think of things that might cause my install/usage to be different.

Thanks,

Jim

Darian,

I renamed the ctools.dll file and can now terminate a debug session without crashing. It does appear that the ctools.dll file is the culprit.

Regards,

Jim

Jim,

We are going to try to get one of our development teams that works on the cTools dll to look at this.  It would help if you could provide the information noted here:

http://tiexpressdsp.com/index.php/Troubleshooting_CCS#Information_for_Support 

Thanks,

John

I believe I have provided most of the information requested in previous postings. If something specific is needed, just let me know. I am more than willing to assist.

Regards,

Jim

I just did an update of CCS4 and noticed that the ctools.dll issue has not been fixed. When will it be fixed?

I got the same issue with an F2808 Experimenter Kit and ControlCard.

By renaming the ctools.dll, I can now connect to the target and start a debugging session.

Thanks for the help!

Please let us know when the bug  will be fixed.

Regards

I'm also having this trouble. I'm using windows 7 ultimate 32bit and C6713 DSK.

So it means if I rename that dynamic library ctool.dll, all the hardware breakpoints will be out of operation?

Hope this be fixed soon.~

As much as I wanted to use CCS4 I finally ended up purchasing a different development studio because of this issue. Perhaps I will re-visit CCS4 someday in the future. Eventually they will get the bugs worked out.

I'm also noticing this crash on Vista64.  I'm running CCS 4.1.3.00038.  Is there a fix or a workaround yet that doesn't involve disabling hardware breakpoints?

Same issue in WIN 7 Ultimate. CCS Version: 4.1.3.00038.  

I spoke with our driver team and they believe that the problems with these crashes on terminate are resolved in our CCSv4.2 release.  If you have a sequence that is easily repeatable you could give the release candidate a try and see if it fixes it for you.  You can install the release candidate in a separate directory from your 4.1.x install.

http://processors.wiki.ti.com/index.php/Download_CCS#4.2.0_Release_Candidate_1_.28September_13.2C_2010.29

John

I test the Version: 4.2.0.10012. Same problem occurs again. Windows 7 Ultimate 32-bit. XDS100 debugger. 

Thanks for trying it Saykal.  Can you confirm that renaming cTools.dll still hides the issue?

John

1. Quit CCS.
2. Right click on the “MyComputer” icon on your desktop.
3. Select “Properties”.
4. In XP select System Properties, in Win7 click on "Advanced System Settings"
5. In the System Properties dialog, click on the “Advanced” tab. (should already be selected in Win7)
6. Click on the “Environment Variables” button.
7. In the “Environment Variables” dialog, under the “User variables” group, verify that the “TI_TRACE_LOGGING” environment variable exists and has a value of 6. Create it if it is not there.
8. Click “OK” in all dialogs.
9. Restart CCS.
10. Reproduce the problem, noting what steps were performed in what order.
11. Zip up the log file and attach it to this thread.  The log file will be in /ccsv4/emulation/analysis/bin/Logs/ti_trace_log_MMDDYY_PID.txt file.

Thanks,

John

Renaming cTools.dll still hides the issue..

The steps to test the problem:

* Start CCS with some examples in the workspace (seen on log file)

*Clicked Debug button 

* Clicked 3 times step over

* Clicked Terminate All & CCS crashes

Log attached. 

Saykal,

We still haven't had any luck reproducing locally but the development team has gone through the log you provided and the source code and has put together a potential fix in one of the DLLs that cTools loads.  It would be great if you could try out to see if it helps.

-put your cTools.dll back that you renamed to workaround the issue

-backup the ICETargetAdapter.dll in the \ccsv4\emulation\analysis\bin folder

-copy in an updated dll from the attached zip

3051.ICETargetAdapter.zip

Note for others watching this thread you need to be on CCSv4.2.0 RC1 to try this fix, we haven't tested it with 4.1.3.

Regards,

John

Hi John,

I test the zipped dll and no change about the problem. 

The error and the log is attached. 

Regards.

Good news for now. 

I test the dll with two-three step debug and no error or crash is seen when i click the terminal all button. 

If I see any errors during the deep programming and debug process, i will write again. 

Logs are attached. 

Thanks. 

(I also test it with CCS Version: 4.1.3.00038.  and i experience connection problems to the emulator. I can not connect to the XDS100 and CCS is locked. )

For what it's worth, I seem to have run into this same issue on a later version of CCS, and the DLL replacement that Vikas Varshney posted appears to have resolved it.

I'm just running a simple test app based on Hello World. It was upgraded from a CCS 3.3 project. Eclipse crashes when I press "terminate all".

CCS Version is 4.2.1.00004, running on Windows 7 Professional 64-bit, with Blackhawk 510 emulator to the TMDXEVM6486-1 EVM. Everything is a new installation (new OS install, new CCS install, etc) as of yesterday. I could not locate crash files in the locations described in the Wiki.

It seems that the test solution was produced for an older version of CCS, was the fix not integrated into the current release?

CCS v5.0.2 includes this update.

Also, CCS v4.2.2 would have this update included.

I have found a workaround for "freezing Terminate All button" for my configuration:

Using Code Composer Studio Core Edition  Version: 4.2.3.00004  on windows XP with Lauchpad connected.

After starting up CCS4 the C/C++ Perspective shows up the projects tree.

On file is the configuration named MSP430Gxxxx.ccxml.

Shortly after starting up this filename is shown as: "MSP430Gxxxx.ccxml".

A while later it is shown as:                                           "MSP430Gxxxx.ccxml[Active/Default]"

If i start the first debugging session immediately after starting up CCS4, when configuration is shown without ...[Active/Default]-indication,

then there is no freezing or crash after the "Terminate All"-buttonn and this remains for the complete CCS4 session. I can start and terminate a debug session as often as i want.

If i start a debugging session a little bit later, when configuration is shown with ...[Active/Default]-indication,

then i have the freezing or crash after the "Terminate All"-button. And this is well reproduceable.

Maybe this can help you too. Sorry for bad english.

Stephan

Pressing Halt (Double yellow bars next to terminate, then pressing terminate all solved the problem for me.