|Non-Confidential||PDF version||ARM DUI0446Z|
|Home > Running DS-5 Debugger from the operating system command-line or from a script > Capturing trace data using the command-line debugger|
To capture trace data using the command-line debugger, you must enable the relevant trace options in the Debug and Trace Services Layer (DTSL) configuration settings in DS-5.
For this task, it is useful to setup the DTSL options using the graphical interface of DS-5 Debugger.
Once you have setup the DTSL options, the debugger creates a file that contains the DTSL settings. You can then use this file when invoking the command-line debugger to perform trace data capture tasks, for example, run a script which contain commands to start and stop trace capture.
An example script file might contain the following commands:
loadfile C:\DS-5_Workspace\fireworks_panda\fireworks_panda.axf # Load an image to debug start # Start running the image after setting a temporary breakpoint wait # Wait for a breakpoint trace start # Start the trace capture when the breakpoint is hit advance plot3 # Set a temporary breakpoint at symbol plot3 wait # Wait for a breakpoint trace stop # Stop the trace when the breakpoint at plot3 is hit trace report FILE=report.txt # Write the trace output to report.txt quit # Exit the headless debugging session
In this example, the settings are stored in the default.dtslprops file.
debugger --cdb-entry "pandaboard.org::OMAP 4430::Bare Metal Debug::Bare Metal Debug::Debug Cortex-A9x2 SMP::RealView ICE" --cdb-entry-param "Connection=TestFarm-Panda-A9x2" --cdb-entry-param "dtsl_options_file=C:\DS-5_Workspace\my_dtsl_settings.dtslprops" --script=C:\DS-5_Workspace\my_script.txt.