• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 825 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.

Original question:

CCS/DRA829V: How to get the complete log of a debug session?

CCS/MSP430F5438A: Debug Server Scripting (DSS)

steve spaeth
Prodigy 225 points
Part Number: MSP430F5438A


Tool/software: Code Composer Studio

I really like the power of using DSS for testing requirements that require getting internal information such as a state transition.

Instead of writing a large number of procedures containing a list of steps, and performing the steps via the GUI interface (load program, set break-point, run, when break-point is hit - get actual value of symbol, compare actual value with expected value, write down information, terminate debugger, verify with the quality assurance representative, make any notes/comments.... ...start next procedure.

I am using DSS to automate these steps making a simple script to traceWrite the information such as the actual value of a variable or memory.  It isn't tough writing the scripts, but I am wondering if the GUI is built on top of the same engine, wouldn't it be very easy to auto-generate a large portion of the DSS script making things like break-point properties or watch-points easy.  

I came across https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html#debug-server-logs - but the log file is not DSS and I am not familiar how to use them with DSS.   Would it be possible (or is it possible) to record a debug session into a DSS script file?

Thanks,

  • 0
    TI__Guru**** 473161 points

    Hi Steve,

    steve spaeth said:
    but I am wondering if the GUI is built on top of the same engine, wouldn't it be very easy to auto-generate a large portion of the DSS script making things like break-point properties or watch-points easy.  

    Both CCS IDE and DSS sit on top of the same debug engine, it is true. CCS IDE does not sit on top of DSS, if that is what you are wondering. There is no way to auto-generate a DSS script by recording GUI actions (which is what I assume you are asking about).

    However, if you are interested in automation specifically from the GUI, You can use the Scripting Console to send commands to control CCS. These commands can be recorded to a file (enableLog) and then played back later (execCmdFile) from the Scripting Console. It's not as nice as have CCS automatically create a full DSS script for you but it is one option.

    steve spaeth said:
    I came across https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html#debug-server-logs - but the log file is not DSS and I am not familiar how to use them with DSS. 

    This is an internal diagnostic log most useful for the engineers here to decipher to help investigate debugger issues. It is not really related to DSS

    Thanks

    ki