#Gtkwave linux install how to#
#Gtkwave linux install code#

#Gtkwave linux install how to#

How to enable run-time node start/stop event logging In the case of a pipelined graph, the fourth file shows the interactions between the nodes and data reference queues for the first pipeline ID of a graph. (Note: this file requires a more in-depth knowledge of the framework and is mainly intended for debugging issues within the framework.) In the case of a pipelined graph, the third file shows how each of the data reference queues are acquired and released by the framework. In the case of a pipelined graph, the second file shows the interactions between the nodes and data reference queues for every pipeline ID for the pipeline depth of a graph. The first file shows the interaction between all nodes and data objects in a graph.

In the case of a pipelined graph, this API outputs 4 separate files:.

In the case of a text file called graph.txt, the following command would be used to generate a JPEG called graph.jpg in the current directory: The command to generate the JPEG can be seen below: jpg file can be generated on a Linux machine using the dot command. txt file located at the specified output path. In target mode, this API will generate only a. The graph diagram will not show the cores that each node runs on, it will simply show the interactions between nodes in the graph. jpg file located at the specified output path.

In PC emulation mode, this API will generate both a.

Below are a few notes on how to use this tool. The tiv圎xportGraphToDot API provides the ability to generate a JPEG diagramming the nodes in a graph. How to use the graph JPEG generation tool

#Gtkwave linux install code#

In order to add additional documentation to custom code written on a given core, reference the VX_PRINT API. Note, these have to be called for the individual cores, not system-wide. Logging levels can be enabled and disabled for each core by calling the tivx_set_debug_zone and tivx_clr_debug_zone respectively.

By default, the VX_ZONE_WARNING and VX_ZONE_ERROR logging are enabled on each core.

The logging levels can be found as a part of the enum tivx_debug_zone_e. The logging print statements are enabled based on which level of logging that has been set. The TIOVX framework contains informative debug logging that can be enabled and disabled.