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.

Slow Watch Window on CCS v6.0.1

Other Parts Discussed in Thread: CONTROLSUITE, MOTORWARE

I've started using CCS v6.0.1 however I've noticed that the watch window has a much slower update rate than CCS v5.5.  

I have a timer on my target that indicates the number of 0.1ms counts that have passed.  In CCS v6.0.1 the watch window updates every 2-3 seconds.  In CCS v5.5 the watch window will update every 300ms.  

In the settings under Window->Preferences->CCS->Debug the continuous refresh interval is set to 100ms in both versions.

I am using the same hw, usb port, project, workspace, and variables in the watch window for CCS v5.5 & CCS v6.0.1

  • That's odd. I was playing with continuous refresh the other day on a F28377D (w/CCSv6.0.1) and it was definitely much faster than 2-3 seconds... probably the 500ms that is the default. What device and emulator are you using? I see InstaSPIN mentioned in your signature... are you using a F2806x?

    Also, you mentioned 5.5 was noticeably faster.  Is the environment basically similar in the sense that both 5.5 and 6.0.1 was run on the same PC, target and emulator and with a similar IDE setup (same amount of windows and data being refreshed, etc?

    Thanks

    ki

  • Ki,

    I've been seeing this issue on the F28377D ControlCard.  I have not yet tried with the F28054M ControlCard or the F28069M ControlCard.  

    When I took my approximate time measurements I tried to make the environment as similar as possible.  It was done on the same PC, same target hardware, and same debug setup (including watch window contents).

    Thanks

  • LineStream - Adam Reynolds said:
    I've been seeing this issue on the F28377D ControlCard

    Same exact target I was playing with recently. Using the onboard XDS100 via usb cable.

    I'll need to do a direct comparison with v5.5. I'll keep you posted

    ki

  • I tried this again with CCSv6.0.1 connected to my F28377D via onboard XDS100v2. I changed the refresh rate to 100ms and the Expressions view updates constantly (looks every 1/10 of a second). I can't seem to reproduce this your issue.

    Do you see this issue with all applications? I was playing with the epwm deadband example in controlsuite, with EPwm1TimerIntCount, EPwm2TimerIntCount, EPwm3TimerIntCount all in the expressions view. Setting the refresh rate to 100ms has those variables constantly being refreshed and updated immediately with continuous refresh enabled.

  • Ki,

    Very interesting.  I'll try with that same example project and report back.  

    Only CCS v6 is where I've seen this issue.  CCS v5.5 has never had this problem.  I have also tried uninstalling CCS v6 and reinstalling it, making sure I'm on the latest version (6.0.1) and the problem persists.  

  • Ki,

    I think I've got the issue figured out.  In my expressions window I had quite a few items (~15) that were not present in the .out file that I loaded into the F28377D.  When I removed the expressions that were "Error: identifier not found" it allowed my watch window to refresh at the rate I was expecting it to.

    If I purposely add in expressions that don't exist in my project I can get the update rate to slow down.

    I haven't seen this behavior in CCS v5.5, is this something that changed between the two versions?

    Thanks for you help!

  • Adam,

    I can somewhat see the issue. In v6.0.1, if add ~15 or so invalid entries, the refresh does slow down. Not to where it is 2-3 seconds a refresh (more like 1 second max). Removing those entries speeds up the refresh.

    I also see a similar issue on v5.5. The difference is that having invalid entries does not slow the refresh rate down as much as in v6. But it is definitely noticeable no doubt. Is this similar to what you see?

  • Ki,

    I haven't noticed this issue in CCS v5.5, but this is similar to what I see.

  • Ki,

    Sorry to bring up this old issue, but I am still seeing a large amount of slow down when using a typical number of items in the watch window when using CCS v6.0.1.  I've taken two videos of what I see when I interact with the watch window.  I tried with both Silicon RT Mode enabled and disabled.  In this test I am using lab 06a from MotorWare 13 on the DRV8312-69M-Kit, Telco motor, and F28069M ControlCard.  I am using the on-board debugger.  

    https://linestream.box.com/s/zne4ewooq39qwrydch5o - CCS v6.0.1 Silicon RT Off

    https://linestream.box.com/s/32oaz9m0m2bke7wfyxsb - CCS v6.0.1 Silicon RT On

    When I run the same workspace, software, board, USB port, and number of programs open with CCSv5.5 there is a very fast update rate on the watch window.  I've included videos below.

    https://linestream.box.com/s/yjr0bb4lhs7uq649hw2j - CCS v5.5 Silicon RT Off

    https://linestream.box.com/s/1vkvr7gxapd6eyxy1jkh - CCS v5.5 Silicon RT On

    With the response of the watch window being this slow, it really makes CCSv6.0.1 difficult to work with as a debugger.  I've noticed that this issue occurs when both writing values and reading values.  I've made sure that I am on the latest version of Java and there are no available updates for CCS.  

    Is there anyway to speed up the refresh rate of the expressions window?  This really impedes progress.

  • LineStream - Adam Reynolds said:
    When I run the same workspace

    Are you using the same workspace folder for both v5 and v6? If so, can you try using separate workspace folders? I ask this because it is not recommended to share workspace folders between different versions of CCS. You can get away with it if it is a minor revision difference (like CCSv5.4 and v5.5) but for major revision differences, it can lead to all sorts of instability.

    It is a bit of a long shot that the workspace folder would be the issue but I just want to rule that out before i escalate this issue to engineering.

    Thanks

    ki

  • Ki,

    I was using the same workspace folder.  I still see the issue when I make a new workspace folder and only run CCS v6.0.1 using it.

    Thanks for advancing this issue.