All shortcuts | Press
Ctrl+Shift+L to see all shortcuts.
|
Project Properties | Select the project in the
Navigator View,
right click and choose
Properties. Or from menu
Project > Properties.
|
OVM/UVM Compliance Review | To perform the OVM/UVM compliance review of your project click the
SV Lint button in the toolbar of the Verilog Perspective.
.
|
OVM Field Editor | The OVM Field Editor enables you to inspect and edit OVM field registrations. To bring up the OVM
Field Editor, right click inside a class definition and select 'OVM Field Editor' from the pop-up menu, or simply press
Shift Alt F.
|
UVM Field Editor | The UVM Field Editor enables you to inspect and edit UVM field registrations. To bring up the UVM
Field Editor, right click inside a class definition and select 'UVM Field Editor' from the pop-up menu, or simply press
Shift Alt G.
|
Project templates | A project template is a
parameterized directory tree. Both in the file contents (.v, .sv, .sh - practically any file) and in the file or directory names you can use
parameters. Combined with
TODO markers, you can use a project template as a
customized wizard.For more details see the Project Templates chapter in
VlogDT User Guide.
|
System Variables and -f Support | See:
Build_Configurations
|
Generic launch (make, scripts etc.) | You can launch external scripts: Menu
Run > Run.... Select
DVT Generic configuration and click the
New button.# Specify
name, working directory and command. Click
Run.
You can also use the
Run > Quick Run menu (or Ctrl+U shortcut key) to quickly launch any existing Run Configuration:
|
Create dialogs for scripts & flows | You can create
Custom Dialogs for your own scripts:
Follow the wizrd from menu
New > Example > DVT > DVT Custom Dialog, then create a run configuration with the command
echo ${dvt_dialog_prompt:customdialog.swtxml} and run it.
|
Open terminal | You can open a fully working command-line terminal inside of DVT: In the
Navigator View right-click on the desired location and select
Open Terminal Here
|
External Builders | An external builder allows you to invoke any script/tool and back-annotate its output (errors, warnings etc.) to the source code. It is a mean that allows you to connect any 3d party tool (compiler, linter etc.) to DVT error signaling engines.You can configure one or more external builders on a project: - The commands you define will be invoked on project clean, full build and incremental build. - The patterns you define will be applied on the command output to recognize errors, warnings etc. - The pattern matches will be back-annotated to the source code and presented in a similar way DVT signals errors (file, line, in the Errors View etc.)DVT ships with some predefined example configurations to get you started.For more details see the External Tools>External Builders chapter in
VlogDT User Guide.
|
External Documentation | You can browse and search through 3rd party documentation using the Eclipse help system.For more details see the External Tools>External Documentation chapter in
VlogDT User Guide.
|
Context Sensitive Help | A focused set of help topics that is related to the current context can be shown to users on demand using context-sensitive help. This form of user assistance is delivered to users when a platform-specific trigger is activated (e.g. F1 key on Windows, Ctrl+F1 on GTK, Help key on Carbon).For more details see the Getting Started > Context Sensitive Help chapter in
VlogDT User Guide.
|
Mapping Linux to Windows | Linux directories can be mapped to Windows drives, thus allowing editing files from Windows. For example
/home/simi is mapped to
Z:\. This has an impact on paths configured for a DVT project, for example INCDIRs etc. The paths are set using Linux conventions, however Eclipse runs in Windows and the DVT builder needs to know about the mapping in order to compile the files. To specify the mapping, set the system variable
%DVT_CROSSPLATFORM_MAP% before invoking Eclipse. You can add multiple mappings separated by ";" e.g.: /projects/=p:\;/home/lars/=Z:\lars\
|
Recover from abnormal inconsistencies | In the event of unexpected behavior (missing results in search, types in type browsing, hyperlinks, tooltips etc.) please manually trigger a clean build from menu
Project > Clean....
|
OVM Smart Log | DVT ships with predefined filters for OVM that allow you to view colored and hyper-linked logs like the one below:
See
OVM Smart Log for more details.
|
UVM Smart Log | DVT ships with predefined filters for UVM that allow you to view colored and hyper-linked logs like the one below:
See
UVM Smart Log for more details.
|
OVM to UVM Migration | DVT provides an OVM to UVM migration wizard that automatically performs all the necessary changes within an existing OVM project. To start the wizard: right click on a project/file/directory in the navigator, then select
Refactor > Migrate OVM to UVM. See
OVM to UVM Migration documentation page for more details.
|
Add a new file extension to compile list extensions | Go to
Window > Preferences > General > Content Types, select a category from the list (for example
Verilog Source File) then click on
Add and then on
Ok.
|
Sharing workspace settings | Export all Workspace/ Eclipse customization: - Go to
File > Export > General > Preferences - Make sure
Export all is selected - Select a file where the preferences should be exported Now you can share this file with your team. When it is imported into another instance of Eclipse (by using
File > Import > General > Preferences), the configuration (all options available in
Window > Preferences) is replaced by the imported one.
Note: you should restart Eclipse for the changes to be enforced (
File > Restart).
|
Using System Variables in Linked Resources | You can use System Variables in the path of linked resources. For example ${DVT_ENV-SYSTEM_VARIABLE_NAME}/work is equivalent to $SYSTEM_VARIABLE_NAME/work in a console. |
Waive problems reported by DVT | You can use
Compile Waivers to promote, demote or disable the problems reported by DVT.To quickly create a new waiver, in the Problems View right click on any problem reported by DVT and waive it. DVT proposes some default values for the waiver description, path and message. You can easily change them to fine-tune the waiver.To quickly start up a new waivers file click on the
Edit waivers button in the Problems View. The .dvt/waivers.xml is created with a default content and opened. You can easily create your own waivers from the default generated ones.In the waivers editor you can use autocomplete for tags, attributes and attribute values.
|
Open a file in DVT from the terminal | You can use the
Command Line Interface like this: $> dvt_cli.sh -workspace ~/dvt_workspace openFile $(readlink -f my/file.sv)The command can be shortened by defining this alias in your ~/.cshrc: alias dvtopen 'dvt_cli.sh -workspace ~/dvt_workspace openFile `readlink -f \!*`'or by defining this function in your ~/.bashrc: dvtopen () { dvt_cli.sh -workspace ~/dvt_workspace openFile $(readlink -f $1); }Then the command gets much shorter: $> dvtopen my/file.sv
|