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 Graph tool : CPU Removed And/Or Terminated



Hi,

I am currently using CCS  Version: 4.2.0.10017 on Windows XP-SP3.

I would like to use the Graph tool to debug part of my code but I am having some difficulties. I have found the following errors

1.- The graph will stop working after terminating the debugging mode (CPU Removed And/Or Terminated). The only way to get it working again is by generating a new graph.

2.- CCS does not remember the last folder used to import a grah file (graphProp)

3.- The export data option in the graph does not work.

 

Is there any workround for any of these problems?

Thank you

 

Alejandro

 

 

 

  • Alejandro,

    1 - The graph needs to be recreated after the Debug session is terminated; this was done to increase robustness of the debugger, as previous data stored usually caused more harm than good. However, it should keep its configuration while you are rebuilding and reloading code for the same debug session.

    2 - There is an enhancement filed for this. You can also check the forum thread below that mentions a workaround:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/54862/194607.aspx#194607

    3 - It works for me on the same CCS version. What do you exactly mean by not working? Is the button inoperative, the file is not saved or it saves with corrupt information?

    Best regards,

    Rafael

  • Hi Rafael,

    Thank you

    1.- I still don't understand why the user has to create a new graph everytime the debug session is terminated. I don't know what you are really gainning with that.

    As Roger mentioned "If I then rebuild the code & re-execute, the graph will disappear & be replaced with a message that says "CPU Removed And/Or Terminated"" ( thanks for the link).  So I am not sure why you are saying that "it should keep its configuration while you are rebuilding and reloading code for the same debug session.". At least it does not work in my CCS version.

    Also, is there any way I can request the graph to stop the x-axis from being updated? When working with arrays the continuos samplig update of the x-axis is not very usefull at all.

    I am assuming that TI thinks that neither of these issues is a problem, and that they do not need to be fixed. Is the correct?

    2.- I could not understand that work around. The problem is with both, the export and the import.

    3.- The "Export all" button is operative, but it does not save any file. Can you send me the content of the file you saved in your test? I am curious to see its content.

     

    Thank you for your fast response.

     

    Alejandro

  • Alejandro,

    1 - This is not an intended feature but a limitation of the graph tool, therefore its fix will not happen in the short term. The issue reported by Roger is fixed in 4.2.0.00017 (it works for me in both 4.1.3 and 4.2.0.00017). As for the continuous X-axis increments, an enhancement was filed to address this in a future implementation of the graph tool.

    2 - The workaround for not finding the last saved directory is shown in the last post of the thread and I copy it below:

    "In the File dialog, in the File name combo box, can use the drop down to see the saved file history to select any files exported to a different directory. This way do not have to navigate through all the folders."

    3 - See the attached file I just created. One thing to check is if the destination directory is writable. I really don't recall this feature being broken in CCS.

    Since you reported some things that were already fixed in your release of CCS, I think the issue may be somewhere else. If you haven't done so, can you try to clean the workspace according to the section General IDE of the page below?

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

    Hope this helps,

    Rafael

    myProp.graphProp
  • Hi Raphael,

    I just installed teh lastest CCS (Version: 4.2.1.00004 ) and I am still have the problems.

    1.- I still don't see how you have reload the code without stopoing the CPU first. CCS stops the debug mode everything you "Debug Active Project".It is very cumberson having to rebuild the graphs everytime you reload the code.

    2.- OK

    3.- I am glad I asked you for the file. We are talking about different things. I can save the graphs settings just fine (.graphProp files). The problem is with the "Export All". Open a graph, right click on the graph, select data and them "Export All". The file extension is supposed to be .csv. That option does NOT work, that is, it does not save any files.

    Thank you

     

    Alejandro

  • Alejandro,

    1 - Stop (or halt) the CPU does not mean the debug session must be terminated. If you stop the CPU using the Halt button (or Shift-F8 or menu Target --> Halt), you can go back to the C/C++ Perspective, modify your project and simply rebuild it (right click and select Build Project or menu Project --> Build Active Project). CCS will ask if you want to reload the newly built code to the target. This will keep the graphs active.

    3 - Thanks for the clarification; I checked and the export to .csv file is a bug that was already reported (number SDSCM00026882). Its fix is only committed to CCSv5, but I can check if they will integrate this into a future version of CCSv4.

    Regards,

    Rafael

  • Hey Rafael,

    I also met the same problem while trying to export the graph to a .csv file. And There was no file in my export folder.  :(

    But I googled your bug number (SDSCM00026882) and didn't find it. Could you give me a link about the bug?

     

    Thank you!

    Qing