How to Quickly Bring up a Project in DVT Eclipse IDE by Reusing Simulator Arguments

Overview

This video shows how you can easily bring up a DVT project by reusing arguments from a simulation log or invocation, and how to integrate DVT in existing script-based or makefile-based automated flows.

The dvt_cli.sh command in the makefile is:

dvt_cli.sh createProject /path/to/project -lang _DVT_LANGUAGE_ -force -default.build +dvt_init+_COMPAT_MODE_ $ARGS

This video was shot using DVT 20.1.44

Explore the design and verification tools: https://www.dvteclipse.com
Or request a license: https://www.dvteclipse.com/request-license

Details

You can quickly bring up a project in the DVT Eclipse IDE by reusing simulator arguments.

For example, you can start from the simulator logs, or from a printout of the simulator invocation.

Just copy the arguments and paste them into the DVT build configuration file. Prefix the arguments of each simulator invocation with a dvt_init directive, depending on the specific tool you are using (e.g. IUS, VCS or Questa).

The compatibility mode instructs DVT to parse the arguments the same way as your simulator. Rebuild the project using the toolbar button, and you're done.

Handling Multiple Simulator Invocations or Log Files

Depending on the simulator that you use and how it is set up, there might be multiple invocations or multiple log files, like: compilation, elaboration, simulation, and so on.

To be on the safe side, wrap them all, since DVT will simply ignore the switches it doesn't care about.

Using Scripts or Makefiles to Start a Simulation

If you already have a script or makefile to start a simulation, ramping up DVT is even easier.

Simply add an extra script switch, or makefile rule, which starts DVT using the dvt_cli.sh script, as illustrated in this example. And make sure that the full list of simulator arguments comes last.

Now the DVT build configuration will always be in sync with the simulator configuration.