User guide

Chapter 25: Trace System MegaCore Function 25–7
Operating the Trace System from System Console
January 2013 Altera Corporation Video and Image Processing Suite
User Guide
trace_read_monitor
<open_service>
<monitor_id>
<index>
Reads a 32-bit value from configuration
space within the specified monitor.
Refer to the trace monitor documentation
for the register maps.
trace_write_monitor
<open_service>
<monitor_id>
<index><value>
Writes a 32-bit value from configuration
space within the specified monitor.
Refer to the trace monitor documentation
for the register maps.
trace_get_max_db_size <open_service>
Gets the maximum (in memory) trace
database size set for this trace system. If
the trace database size exceeds this value,
then the oldest values are discarded.
trace_set_max_db_size
<open_service>
<size>
Returns the current maximum trace
database size. Trace database sizes are
approximate but can be used to prevent a
high data rate monitor from using up all
available memory.
trace_start
<open_service>fi
fo
Starts capturing with the specified trace
system in real time (fifo) mode.
trace_stop <open_service>
Stops capturing with the specified trace
system.
trace_get_status <open_service>
Returns the current status (idle or
running) of the trace system. In future,
new status values may be added.
trace_get_db_size <open_service>
Returns the approximate size of the
database for the specified trace system.
trace_save
<open_service>
<filename>
Saves the trace database to disk.
trace_load <filename>
Loads a trace database from disk. This
returns a new service path, which can be
viewed as if it is a trace system.
However, at this point, the start, stop and
other commands will obviously not work
on a file-based node.
If you load a new trace database with the
trace_load command, the trace GUI
becomes visible if it was previously
hidden.
Table 25–4. Trace System Commands (Part 2 of 2)
Command Arguments Function