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.

Graphs wont stay between debug-sessions

Other Parts Discussed in Thread: TMS320F2808

Hello,

In CCv3.1 my debug-view had a semi-static setup where I always had my 4 graphs ready and live even between program and computer restarts.

After migrating to CCSv5.1 several things have improved considerably. But, the graph-functionality has not, I'm afraid. As soon as I terminate a debug-session or lose contact with target, I have to set up the graphs again from scratch when starting a new debug-session.

Is there any way to make the graphs more permanent?

  • Hi Anders,

    Anders Bennehag said:
    As soon as I terminate a debug-session or lose contact with target, I have to set up the graphs again from scratch when starting a new debug-session.

    You should not have to do this if you are re-launching the same debug configuration. It should remember both that the graph was open and what the properties were. If you launch a new debug configuration, then it may not have the same graph properties. 

    Are you re-launching the same debug configuration (relaunching the same target config file)?

    You can save the graph properties to a file so you can simply reload it again but again, the properties should be remembered. 

    thanks

    ki

  • Hello there,

    I am launching the same debug-configuration, but the graph I set up in my previous debug-session just tells me "CPU removed and/or terminated.".

    See attached screenshot:

    .

  • I found a similar thread about the same problems in CCSv4 at http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/90117.aspx

    Is there really no fix for this?

  • What version are you using? 5.1.0.09000?

  • I'm using version 5.1.1.00031.

  • I can't seem to reproduce this issue. Can you give me detailed reproducible steps (actions you are doing and the graph properties)? Looks like you are using some 28x device with an SDXDS510USB. What is the exact device? And the example being used looks like one of the 28x peripheral examples from TI. Please let me know which exact example you are using.

    Thanks

    ki

  • Hello Ki-Soo Lee,

    Device is TMS320F2808.
    Emulator is Spectrum Digital's XDS510-USB. I think the project originates from the example project called pmsm3_2

    Output from SDConfigEx v5.1:

    Spectrum Digital Configuration and Diagnostic Utility

    Supports:
    Printer Port: XDS510PP, XDS510PP+, SPI515, eZdsp
    ISA Bus: SPI510, XDS510
    PCI Bus: SPI525
    USB Bus: XDS510-USB


    ** Using emulation application from directory c:\texas instruments\ccs5\ccsv5\ccs_base\emulation\drivers
    ** Checking for a valid emulator/eZdsp

    $$ You are connected to:
    $$ EmuProductName=XDS510USB
    $$ EmuPortAddr=0x510
    $$ EmuPortMode=USB
    $$ ProductId=510
    $$ ProductVersion=84


    ** Checking emulator/eZdsp scan connection

    ** Emulator Test **
    $$ EmuProductName=XDS510USB
    $$ EmuPortAddr=0x510
    $$ EmuPortMode=USB
    $$ ProductId=510
    $$ ProductVersion=84
    ** Emulator Scan Test
    -- Found JTAG IR length of 38
    -- Found 1 JTAG device(s) in the scan chain

    Steps to reproduce:
    - Start Code Composer Studio 5.1.0.201201061800
    - Compile project
    - Debug project
    - Enable Silicon Realtime mode
    - Resume
    - Tools->Graph->Dual time
    - Set up graph according to
      Acquisition buffer size: 512
      Data type: 16 bit signed
      Interleaved: True
      Start Address: DLOG_4CH_buff4
    - This creates two graph windows.
    - Click Terminate
      As I do this, I see the graphs turn grey and display "CPU Removed and/or Terminated" as in screenshot above.
    - Now I start my second debug-session, using the same debug-configuration.
    - At this point, the graphs are dead as far as I can tell.
      I can't even create new graphs as that option is grey in the Tools->Graphs menu, see screenshot below.

    It seems as if I must close all non-working graphs, terminate debug-session, and start a new debug-session to be able to create new graphs when this occurs.