Usage Example

Below is an example of using the VAD UI on Ubuntu* host to connect to a Yocto* target:

  1. On the target system open a terminal window and navigate to the VAD root folder.
  2. Start the server (referred to as the "VAD Remote Publisher" above) by invoking the script ./runserver.sh on the Yocto* machine.
  3. The script starts the remote connectivity framework and loads the VAD publisher module making it ready to receive commands from the host system.
  4. Execute the runvad.sh script on the host system.
  5. Click the Remote Connection icon in the toolbar, which brings up a dialog box where the IP for the target system is entered. Select destination IP and click OK.
  6. Connection is now established and confirmed in the host system status panel. Remote Connection icon is indicating that connection is established  .  A log indicating loading of the runtime should is displayed in the target system terminal window.
  7. Load a graph on the host system. For remotely connected targets, avoid using graphs with nodes that use UI windows, such as the intel.helper.render node. Use instead the Debug Watch mode to inspect generated primitive data after executing a graph remotely.
  8. You can now perform all regular operations on the host system such as Build, Verify and Run. Any operation will be executed on the target system.

    NOTE: Keep in mind that the GraphML file and any graph input files are transferred to the target system during building the graph. The UI is suspended showing the progress indicator while the data is being transferred.

    NOTE: Any status and potential error traces are transferred from target system and displayed on the host system.

  9. After executing the graph by invoking run, you can inspect the generated primitives using the Debug Watch mode. In this mode, when the mouse pointer is hovered over a port, the associated primitive data is transferred from the remote target to the host and displays in the VAD UI.
  10. To stop the remote connection on the host system, click the Remote Connection  icon again. Any preceding operations will execute locally on the host system.
  11. Stop the server on the target system by invoking the script ./stopserver.sh
For more complete information about compiler optimizations, see our Optimization Notice.