• State Resolved
  • Locked Locked
  • Replies 17 replies
  • Subscribers 56 subscribers
  • Views 4030 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 Graphing Tool Problem

Todd Anderson78572
Guru 14640 points
Other Parts Discussed in Thread: CCSTUDIO

All:

I have been using the CCS 5 to show really nice pictures of waveforms. I have up to 8000 32-bit numbers, 2's compliment, and it does a very good job - when it works.

Typically, I will display the waveform, then make a code change, and then re-run to see what impact my change has on the waveform. I halt the emulator to display what is captured in the 8000-deep buffer. This data is put into the buffer during an interrupt service routine.

MANY times I get to the point of displaying a waveform, and "Tools-->Graph-->" will give me grayed out options. I can usually get around this by reloading and rerunning the code. However, there are times when I need to shut down CCS5 and bring it back up to get to display a waveform - which can be very frustrating!

Is there a setting that I am missing? Perhaps a gel-file setting? A CCS 5 setting?

I am running a c5505 processor on a target board, attaching via XDS100 emulator.

Having the graphing capability has been a GOOD thing. Having all of the problems with it is not.

Regards,

Todd Anderson

  • 0
    TI__Guru**** 173310 points

    Todd,

    There is one known issue in CCS where the graph menu would be grayed out if the debug session is started very quickly after launching CCS, especially when there is a lot of content in the workspace. See this related thread: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/153257.aspx

    Sounds like you may be running into the same issue. Are you using 5.1.0 or 5.1.1? That bug is supposed to be fixed in 5.1.1, so if you're on 5.1.0, could you update to 5.1.1 and see if that helps? Please see notes and cautions for updating in the download page: http://processors.wiki.ti.com/index.php/Download_CCS#Code_Composer_Studio_Version_5_Downloads

  • 0 in reply to AartiG
    Guru 14640 points

    Aarti:

    I will try version 5.1.1 - I looked for a newer version on Help->Check for Updates, and it says that 5.1.0 is the latest version...

    Regards,

    Todd Anderson

  • 0 in reply to Todd Anderson78572
    Guru 14640 points

    Unfortunately, upgrading to CCS 5.1.1 did not make the problem go away.

    Regards,

    Todd Anderson

  • 0 in reply to Todd Anderson78572
    TI__Guru**** 173310 points

    Todd,

    I'm sorry to hear 5.1.1 did not help. Have you tried opening a new workspace, importing your project into it and giving it a try? That was a workaround that helped with those previously reported issues. Also you could try giving some time after CCS startup before you initiate a debug session, as I believe that was root cause contributing to the grayed out menus.

  • 0 in reply to AartiG
    Guru 14640 points

    Aarti:

    I created a new workspace and it appears that helps. I will let you know how long I go with the new workspace before I have graph grayout issues...

    Regards,

    Todd Anderson

  • 0 in reply to Todd Anderson78572
    Guru 14640 points

    Aarti:

    Creating a new workspace and porting the code appears to have helped a lot. Why?

    Does a workspace tend to get "too busy" after awhile?

    With the older workspace I was seeing grayout issues with graphing, but I also had situations where Windows 7 would totally lock up, requiring a power-down and reboot. Since moving to the newer workspace, I do not see either of these issues - yet. The project that I am working will be growing, and I am concerned about having to do this on a recurring basis.

    Regards,

    Todd Anderson

  • 0 in reply to Todd Anderson78572
    TI__Guru**** 173310 points

    Todd,

    We found that if a debug session was started very quickly after launching CCS, then the graph menu could get grayed out. This was more easily reproducible when there was more content in the workspace (hence the reason problem goes away when new workspace is created). The root cause is that there is a DVT component (that is started at CCS stratup) which assumes that it is started before a debug session but this was not always guaranteed in CCS. I expect the fix for this to be in CCS 5.2, so in the meantime I hope this workaround is usable.

  • 0 in reply to AartiG
    Guru 14640 points

    All:

    Yesterday the graphing was graying out. This morning I created a new workspace, copied all of the code from the old to the new, and grayout went away. Is this what could be called the "Grecian Formula?"

    So far the workaround is usable.

    Regards,

    Todd Anderson

  • 0 in reply to Todd Anderson78572
    Guru 14640 points

    I am now working with CCS 5.2 - so far, I have not seen issues with the "gray-out" of graphing capability. However, I have noticed that many times after downloading, the program counter does not stop at main. It requires a halt, reset, and restart to get to main. I am using CCS 5.2, C5505 processor.

  • 0 in reply to Todd Anderson78572
    Intellectual 790 points

    Hello,

    Does the problem still occur in the latest version of CCS? Is it worth upgrading from version 5.1.1.00031 to avoid it?

    Regards,

    Adrian

  • 0 in reply to 3446793
    Expert 1145 points

    I'm having the same problem with CCSv5.2.1 and Windows 7 64bit. Very frustrating.

  • 0 in reply to Cam Grant
    Intellectual 470 points

    Is there a fix for this issue?  I am using the TFS plug-in and switching to a new workspace is not that easy.

     

    I was able to graph fine a week ago, but now all the graph options are unavailable (grayed out).

  • 0 in reply to Jeff Talbott
    Expert 1145 points

    The only solution I found was to delete the .metadata directory then re-import the project into the workspace. It is a hassle because you have to re-create any debug profiles all over again too.

    I'm not quite sure, but I think it helps to prevent the greyed out menu by not to rushing into a debug session after starting up CCS. Give it time to fully start up.

  • 0 in reply to Cam Grant
    Intellectual 470 points

    I waited several minutes.  Do you have any feel for how long it should take?

  • 0 in reply to Jeff Talbott
    Expert 1145 points

    The waiting time would depend on how fast your computer is but with a decent computer you shouldn't have to wait much more than a minute or so by the time the disk activity settles down.

  • 0 in reply to Cam Grant
    Intellectual 470 points

    I doubt it's the PC speed.  I waited an hour this morning while i did other work.  I came back to CCS and had no luck.

     

    It's really unfortunate as this was a very useful tool.  I never had any problems in CCS v4.  I don't know if it's due to the Concerto or CCS v5.  I was able to use it just a few weeks ago.

     

    If it weren't for the source control i would open a new workspace.  I really hope this can get resolved by TI soon.

  • 0 in reply to Jeff Talbott
    Intellectual 470 points

    This time code composer sat for about 36 hours before launching a debug session.  Still no graph capabilities.  This used to work.

     

    Can anyone make sense of the error below?  Am i out of sync with eclipse?

     

    Here is the error log. 

    Message: Unhandled event loop exception

    Exception Stack Trace:

    java.lang.NullPointerException  at com.ti.dvt.ccstudioideadapter.CCStudioIDEAdapter.getDspTask(CCStudioIDEAdapter.java:343)  at com.ti.dvt.ccstudioideadapter.VariableObjectNewMenu.getSelectionExpression(VariableObjectNewMenu.java:152)  at com.ti.dvt.ccstudioideadapter.ui.actions.NewDynamicMenu.execute(NewDynamicMenu.java:370)  at com.ti.dvt.ccstudioideadapter.ui.actions.NewDynamicMenu.access$1(NewDynamicMenu.java:368)  at com.ti.dvt.ccstudioideadapter.ui.actions.NewDynamicMenu$1.runWithEvent(NewDynamicMenu.java:231)  at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)  at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)  at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)  at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)  at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)  at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165)  at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754)  at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)  at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)  at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)  at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)  at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)  at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)  at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)  at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)  at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)  at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)  at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)  at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)  at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)  at java.lang.reflect.Method.invoke(Unknown Source)  at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)  at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)  at org.eclipse.equinox.launcher.Main.run(Main.java:1410)

     

    Session Data:

    eclipse.buildId=M20120208-0800 java.version=1.6.0_13 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments:  -product com.ti.ccstudio.branding.product Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ti.ccstudio.branding.product