CCS6 hang up

Hi Iain,

in order to help diagnose things we need any logs generated when this happens.  .dmp files and hs_err files are the best.  Please see this wiki

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

Have you tried v6 or a fresh installation?

Best Regards,
Lisa

Hi Lisa

These are the logs from today. The problem occurred about 3 hours ago.

Regards Iain2235.CCS6logs140814.zip

Iain,

Can you confirm that this only happens when you start a compile?  I'd like to confirm that it's happening when starting a compile, and not something to do with starting/terminating a debug session (if you hit the green debug button, you will start a compile, but you'll also start a debug session as soon as the compile finishes).  If you're not sure, then could you keep an eye out for this moving forward?  Ideally, always terminate your debug session before recompiling, and also clear the terminated session out of the debug view too.

Could you also check in the windows system event logs to see if something suspicious is logged in there?

Darian

Darian,

It is unlikely that the situation is as you describe because I am debugging C6748 code using the ARM of the OMAPL138 to initialise and load the DSP application. I then run the debugger with symbols only. I do recompile whilst the debug is active but I used to do this frequently with CCSV5 without a problem.

Examining the event log does show a bootup error at the time of the incident but this is consistent because I had to use the power button to recover. No other suspicious events are shown just prior to the incident.

Iain

Iain,

Could you set the environment variable TI_DS_OFS_USE_ENTIRE_FILE to 1 (either globally, or from a command prompt before you start CCS) and see if that makes any difference?

In addition, are you using trace?  If not, could you try backing up and deleting ctools (located here: ccsv6\ccs_base\emulation\analysis\bin) and see if that makes any difference?

Darian

Darian,

I have done as you requested. I presumed that ctools.dll was the file you wished me to remove.

I will monitor the situation over the next week to see if the problem occurs.

Iain

Darian,

It is now over a week since I set the global variable and removed ctools and I have had no more occurrences of the hang up. I can therefore assume that this fixes the problem.

I am interested to know whether it is the global variable or the removal of ctools which sorts the issue, or is it both?

Iain

Iain,

The two changes aren't really related, they are just things that I knew could be disabled/altered and that might be making low level OS calls (and thus could cause an OS hang).  So I doubt that it's both of them, but specifically one.

Try re-enabling one of them for a week and see what happens. 

Darian

Darian,

I returned ctools.dll back to its original place and have been compiling without problems for over a week now so as a process of elimination it must be the environment variable which has made the difference.

Thanks for your help on this matter.

Iain

Darian,

Unfortunately CCS locked up again this morning while building the makefile so I have removed ctools.dll again.

Hopefully that will cure the problem.

Iain

Iain,

Could you remove the environment variable and just run with ctools.dll removed.  I'd like to make sure that it's isolated to ctools and isn't a combination of both changes.

Also, just to confirm, the lock up is a full OS lock up, and isn't just CCS hanging, right?

Darian

Darian,

This time when I selected build in CCS the message was "building makefile" and the build percentage remained at 0%. After waiting for some time I tried to close down the build application but it remained because the operation is locked. I was able to close down CCS but this window remained and it was not possible to run CCS again with this window present. Also it was not possible to "CTRL ALT DELETE" to either shut down the process or log off. The only method of recovery was to power cycle.

Previously before adding the environment variable and/or removing ctools the OS locked completely and nothing responded so power cycle was the only recovery.

I will remove the environment variable as you request. 

Iain

Iain,

Would you be able to collect a dump file for me while CCS is running?  Start CCS and launch a debug session (connected with symbols loaded), then open the task manager, right click on ccstudio.exe and select create dump file.

Thanks,

Darian

Darian,

Please find dump file as requested.

Iain

Iain,

I don't see it attached.  If the attachment failed because it's too big, let me know and I'll send you a ftp site you can use.

Darian

Darian,

It did take a long time to attach and it indicated it had succeeded. I think the ftp site is the best option.

Iain

Iain,

I got the dump file, but unfortunately nothing looks suspicious.  For now, keep running without ctools.dll present and we'll see if we can isolate this hang...

Darian

Darian,

At the moment I have ctools.dll present and TI_DS_OFS_USE_ENTIRE_FILE removed.

The last hang I had was with ctools.dll removed and TI_DS_OFS_USE_ENTIRE_FILE present.

Do you want me to stay as I am or go back to the above?

Iain

Iain,

I want to try and determine if this OS hang is affected by ctools.dll or the environment variable, or both.  So whatever trials you can do to gather data and determine what combinations (if any) help is good.

Darian

Iain,

I've notified the team that works on the ctools.dll and I'll allow them to follow up with this issue.

Darian

Darian,

I know its been some weeks since we discussed this issue but I may have some further information which may be useful to you.

I think this happens after doing a software upgrade of one of the CCS components such as the compiler or an emulator. I believe if you upgrade and restart, this is when the lock up occurs at the creation of the makefile for the next build.

Iain