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.

CCSTUDIO: CCS 20.2.0 debug issues

Other Parts Discussed in Thread: C2000WARE, LAUNCHXL-F28379D

thanks for the suggestion. This indeed solves the stuck on initialization problem. But now I opened the epwm_up_aq_cpu01 example from C2000Ware again and the debugging is unusable laggy again. I opened Dissassembly view while I'm in a breakpoint and the dissassembly view jumps around like crazy. Second start of programm and the initialization problem is still gone. So that problem is solved. Shall i open another question for my debug problems to seperate topics?

  • I split this issue to a separate thread.

  • I am unable to reproduce the issues you are seeing. Can you provide a test case with explicit details on how to reproduce? 

    Thanks

    ki

  • Sorry, I missed your reply since I did not see a notification. I try to write down what I do, but its quiet simple.

    1. Fresh environment of the newest version
    2. Start Program with LAUNCHXL-F28379D connected
    3. "Get Started" "No compatible board detected", Therefore I type "LAUNCHXL-F28379D" myself
    4. "Browse software and examples"
    5. "Rescource Explorer", "C2000Ware (5.04.00.00), "English", "Devices", "F28379D", "Examples", "Bitfield", "cpu1", "epwm_up_aq", then Import Button
    6. "Run", "Debug Project (epwm_up_aq)"
    7. "Debug Core Selection" -> "C28xx_CPU1"
    8. "View", "Dissassembly"
    9. Breakpoint by mouseclick on the beginning of InitEPwm1Example(), "Continue"
    10. When I now right click on Dissassembly and choose "Show symbols" it jumps around crazy and becomes unasuable

  • Thank you. I tried the same example. The only difference is that use the CPU1_FLASH configuration. I didn't see any issue. Can you try the CPU1_FLASH configuration and see if you see the same issue?

  • Thanks for testing. Yes, tried a fresh environment and changed to CPU1_FLASH configuration. The problem still remains. But when I deactivate "Show Source" in Dissassembly View then it becomes normal. It seems that the problem ist the "Show source" function. But this function is important to me. Have you tested with "Show source" activated?

  • This is the behavior I see:

    Is this similar to what you observe or do you see something more extreme?

  • Thanks for testing. What I see is a lot more extreme. I'm not touching keyboard and mouse and I'm unable to read the dissassembly because of the many quick jumps. But in the video you selected "Show symbols". My problem begins with "Show source" instead.

  • My problem begins with "Show source" instead.

    Ah ok. Yes, I see the issue for this.

    Second start of programm and the initialization problem is still gon

    What do you mean by "second start"? I've tried restarting the application and also restarting the debug session but the issue persists for me.

  • Yes, I see the issue for this.

    I filed a bug for this. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-12686

    Thanks

    ki

  • Hi Ki, thanks for the bug ticket. "Second start" was a leftover of the previous topic "stuck in initialization". After this one was solved you splitted both topics. The problem with "show source" in Disassembly view is reproducable for me any time.

  • "Second start" was a leftover of the previous topic "stuck in initialization".

    Ah, got it. Thanks for clarifying.

    The disassembly issue is likely due to the view constantly rendering to interleave the source line. It should really only do it for the disassembly shown in the view and for an x amount before and after. Instead it looks like it just keeps going and this causes the jitter and IDE performance issue.