CCS V4 profiler for C67xx

Thank you, John.

Steve

Hi John,

We can run Statistics data on our project with CCS 3.3.  Now we moved to CCS v4,  I can not find STS window. 

How do we run STS on CCS v4?

Thanks.

Regards,

Steve

Steve,

Look under Tools -> RTA -> Statistics Data

Regards,

John

Thanks.  I am running it.

Steve

Hi John,

When running STS, CCSv4 crashes consistently.

Is there any work around?

Thanks.

Steve

Steve,

Does the crash happen at a particular time or is it more random? Can you get the view to work at all?

Can you provide the crash dump file and error logs?

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

Thanks

ki

Ki,

After starting STS view, CCSv4 will crash within a few minutes.  There is no *.dmp files generated.

This makes the STS unusable.

Regards,

Steve

What emulator are you using with your 6713?

I am using Spectrum Digital's XDS510 USB emulator with 6726, not 6713.  Thanks.

Thanks. So far Statistics view is working fine but I have not use your emulator/target combo.

We have a very simple program and the following are the only tasks running.    Just start STS, it will crash within 3 minutes.  Thanks.

One more question - did you rebuild your BIOS example in v4? or are you using the executable from v3?

We are using ROM BIOS, version 5.20.05.  Since it's in ROM, not rebuilt.

If you double click on the exception in the Error log, you should see an exception message and maybe some stack trace. Could you post the message here?

Thanks,

Chris

Chris,

Please give more detailed instructions for looking at the Error log.  CCSv4 crashed.

Thanks.

Steve

When you captured that screenshot of the Error log that you posted, are you still able to open the errors in that table?

If the GUI's unresponsive, you could try launching CCS with the -consolelog flag, and the error message may appear there. The easiest way to do this is to modify the properties of the CCS shortcut and add -consolelog to the end of the 'target' field on the 'shortcut' tab. If there are spaces in the path to the executable, then the path needs to be surrounded by quotes and -consolelog should be outside of the quotes.

Officially, BIOS 5 RTA in CCSv4 only supports BIOS 5.40 and later (it hasn't been verified on earlier versions), and there's a good chance the issue you're running into is caused by the fact that you're using 5.2, and maybe also because it's a ROM'd version of BIOS. It'd be interesting to see if the problem you're encountering is a more general issue, though.

Thanks,

Chris

Chris,

I setup -configlog as you described.  After launch CCSv4, I got the following from CMD window.

!SESSION 2010-09-20 09:53:34.484 -----------------------------------------------

eclipse.buildId=4.1.3.00034
java.version=1.5.0_14
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86 -consolelog

!ENTRY org.eclipse.core.resources 2 10035 2010-09-20 09:53:35.995
!MESSAGE A workspace crash was detected. The previous session did not exit normally.

CCSv4 startup normally.

Thanks.

Steve

Thanks for trying it. That all looks ok--it's just a message saying that your last CCS session crashed.

If you reproduce your issue, do you see any additional info in the consolelog, or is that it?

Thanks,

Chris

This problem is readily reproducible.  I re-ran STS and got the following.  If you need to see anything else.  I can preset my window.  As soon as STS crashed, CCSv4 won't respond.  Thanks.

After reproducing the crash, can you copy and paste the contents of the -consolelog as you did a couple posts back? Or is it not any different than what you posted there?

That very top exception in the error log is the one we need to look at, and the stack trace for it should show up in the -consolelog I think.

Thanks,

Chris