- Installation Checklist
- Predefined Projects
- Getting Started
- What is a Workspace
- What is a Project
- Project Natures
- Workspace and Workbench
- Refresh
- Linked Resources
- Backup and Local History
- Basic Tutorial
- Switch to the DVT Perspective
- Open a Project
- Configure the Build
- Build the Project
- Inspect the Compilation Errors
- See Comments in Tooltips
- Use Hyperlinks to Move Around in the Code
- Quickly Open a Type (Class, Module, Interface)
- Quickly Inspect the Class Hierarchy
- Quickly Open a File
- Quickly Move Inside the Editor
- Inspect the Class Hierarchy and Class Members
- Inspect the Design Hierarchy
- Inspect the Verification Hierarchy
- Browse Through All the Available Types (Classes, Modules, Interfaces)
- Look for the Implementation of an Extern Function or Task
- Search for Entities
- Use Content Assist (Autocomplete)
- Use Code Templates
- Use Module Auto Instance
- Expand Macros (Apply Preprocessing)
- Trace Macro Errors
- Track Tasks using TODO Markers
- Quickly See the Current Scope in the Status Bar
- Fold Code Regions in Order to Improve Readability
- Access the Context Sensitive Help
- Build Configurations
- Non-top files
- default.build
- Auto-config
- Simulator Log-config
- Emulating compiler invocations
- Multiple .build Files
- Compatibility Modes
- Paths
- Strings
- Comments
- Environment Variables
- Including Other Argument Files
- Build Persistence
- DVT Auto-Linked
- Run a Script Before Build
- All Build Directives
- e Language Test Files
- e Language SPECMAN_PATH
- SystemVerilog OVM or UVM Library Compilation
- Xilinx Libraries Compilation
- Intel(Altera) Quartus Libraries Compilation
- Questa Libraries Compilation
- Use of External Programs
- Compile Checks
- Content Assist (Autocomplete)
- Quick Fix Proposals
- Add Parameter to Module
- Add Port to Module
- Add Signal to Sensitivity List
- Add Virtual Qualifier to Interface Type
- Correct Spelling In Comments and Strings
- Create Class In New File
- Create File From Build Config Editor
- Create Included File
- Create Interface Class In New File
- Declare Method
- Declare Variable
- Did You Mean
- Fully Qualify Type
- Implement Extern Method
- Implement Missing Pure Virtual Methods
- Import Type
- Remove 'local' or 'protected' Qualifier
- Remove Signal from Sensitivity List
- Remove Signal Never Used
- Update Extern Prototype/Implementation
- Update Module Instance
- Update Virtual Method Signature
- Waive Compilation Problems
- Quick Assist Proposals
- Bind Method Call Arguments by Name
- Bind Method Call Arguments by Position
- Connect Instance Ports by Name
- Connect Instance Ports by Position
- Expand .* Port Connections
- Explicitly Declare
- Extract to Variable
- Extract to Method
- Extract to Module
- Move Selection to New File
- Join Extern and Implementation
- Split to Extern and Implementation
- Rename in File
- Content Filters
- Code Templates
- File Templates
- Project Templates
- Code Formatting
- Override Functions
- Generate Getters and Setters
- Module Automatic Instantiation
- Semantic Search
- Show Usages, Readers or Writers
- Favorite Searches
- Show Constraints
- Show Instances
- Quick Search in Views
- Trace Connections
- Breadcrumb Navigation Bar
- Code Factory
- > Refactoring
- Rename Refactoring
- Rename Port Across the Design Hierarchy
- Bind Method Call Arguments by Name
- Bind Method Call Arguments by Position
- Connect Instance Ports by Name
- Connect Instance Ports by Position
- Expand .* Port Connections
- Explicitly Declare
- Extract to Variable
- Extract to Method
- Extract to Module
- Move Selection to New File
- Join Extern and Implementation
- Split to Extern and Implementation
- > Connect Instances Across the Design Hierarchy
- Add Port to Module from Selected Field
- Add New Port to Module
- Add New Parameter to Module
- Refactoring Scripts
- Diagrams
- Low Power Format Support
- Export HTML Documentation
- External Tools Integration
- Debugger Integration
- Custom Dialogs
- Command Line Interface
- dvt_cli.sh
- Syntax
- Examples
- Makefile Example
- Commands
- Create a Project (Mixed-Language Capable)
- Create a Project From an Existing Template
- Import an Existing Project
- List Compiled Files
- Compare Files
- Launch a Run Configuration
- Open a File
- Close a File
- Open a Custom Dialog
- Open a Perspective
- Refresh a Project
- Rebuild a Project
- Print Edited File
- Quit
- Query the running status
- Print version
- Macros Support
- Reminders (TODO Markers)
- OVM Support
- UVM Support
- VMM Support
- Settings Management
- Reference
- Comments Formatting
- Common Shortcuts
- Custom Pragmas
- Editor Right Click Menu
- Hyperlinks
- Icons and Decorations
- Scripts
- Syntax Coloring
- Themes
- Toolbar Actions
- Tooltips
- Views
- Checks View
- Code Templates View
- Compile Order View
- Console View
- Coverage View
- Call Hierarchy View
- Design Hierarchy View
- Inspect View
- Layers View
- Macros View
- Outline View
- Problems View
- Tasks View
- Trace Connections View
- Types View
- Type Hierarchy View
- UVM Browser View
- UVM Sequence Tree View
- Verification Hierarchy View
- Application Notes
- Tips and Tricks
- Q & A
- I am new to Eclipse, where should I start from?
- Where can I find DVT Help?
- How do I see and configure the key shortcuts?
- Are there any backup files in Eclipse?
- Workspace in use, cannot launch eclipse...
- Locking is not possible in the directory...
- How to start DVT Eclipse with a different eclipse.ini
- Save could not be completed
- IBM Clearcase Plugin
- Non existing package mti_fli
- DVT is crashing with "Problematic frame ld-linux-x86-64.so.2 _dl_rtld_di_serinfo
- libxul.so undefined symbol
- How to use Working Sets for filtering Problems/Task/Search views?
- How to handle Simulator and Command Line Macros
- How do I Access Files Outside Project Dir - Working with Linked Resources
- Mapping Linux to Windows (/proj/ to Z:\proj\)
- Subversive vs Subclipse
- How do I associate a project with both DVT and CDT?
- Can I use vi/vim along with DVT?
- Can I perform dos2unix or unix2dos from DVT?
- How can I configure Eclipse to use a local CVS repository?
- I am using the Common Desktop Environment via Citrix and experiencing crashes. What can I do?
- How do I change the background color of the Editor?
- Some widget colors are not displayed properly. What can I do?
- How do I change the tooltip colors?
- How do I change Internet Proxy Settings?
- Eclipse does not start, there is no Workspace, metadata or log file created
- Workspace permissions
- How do I link mylyn with Bugzilla?
- How do I print source code?
- How do I disable Eclipse Software Sites?
- How do I revert to a previous version?
- What are the most common shortcuts in DVT?
- How does DVT integrate with emacs?
- How does DVT integrate with CVS?
- How to set an environment variable within a Run Configuration?
- How to run a remote Unix commnad from DVT Eclipse for Windows?
- Rebuild shortcut (Ctrl + Alt + R) does not work
- I want to use an alias in a DVT Generic Run Configuration, but it's not recognized
- How to set multiple paths as sources of predefined projects ?
- Lines are suddenly changing indentation when I edit text or move the cursor through the editor.
- How to change the directory where the build log file is saved ?
- How to find the DVT logs on Linux/Unix ?
- How to create resource filters ?
- How to create custom shortcut and button for a Run Configuration?
- I know that file.foo is present in the project location, but I can't see it in the Navigator View
- How to copy the full path to the file in the current editor?
- How to adjust the console logs filters matching parameters?
- When I switch to Block (Column) Selection mode the font changes
- In Block (Column) Selection mode I see strange editng artifacts
- How to modify the font size in the code editors?
- How to automatically checkout/lock files from the revision control system ?
- How can I see if a file is read-only?
- How can I open a file in DVT from the terminal?
- How can I open a file in DVT from Questa?
- How do I change the name of the xterm opened by a DVT Generic Run Configuration?
- What is New?
- How to Report an Issue?
- Legal Notices
- Third Party Licenses
Any change to a module or entity definition, like new ports or new signals being added, affects all its instances. Before proceeding to source code changes, you can preview the design structural changes.
Terminology:
output instance is the module instance where the connection starts. It outputs the signal that will be connected. output module is the module being instantiated as an output instance.
input instance is the module instance where the connection ends. It inputs the signal that will be connected. input module is the module being instantiated as an input instance.
closest parent instance is the parent instance through which a signal is routed to connect the ports leading from the output instance to the input instance across the design hierarchy. No ports will be added to the closest parent instance. The closest parent module is the module corresponding to the closest parent instance.
relevant modules are the modules that will change by adding new ports and/or new signals. relevant instances are instances of relevant modules.
Ports are added only to modules that are instantiated on the paths leading from the output module instance and the input module instance to the closest parent instance. Ports are added to the output module or the input module only if the connection is not using an existing port.
All the instances that will not change are grayed out. All relevant instances are highlighted. If you hide the irrelevant instances, only the grayed out instances enclosing relevant instances are kept in the tree.
The following filters in the Connect Instances Toolbar help you understand the structural changes:
Show Design Hierarchy to see the unfiltered design hierarchy.
Minimal Path highlights just the affected path from the output instance to the input instance. It includes the closest parent instance through which the signal is routed. It presents the connection between the instances you've selected without considering the side effects caused by other instances.
Direct Changes highlights all the "similar" instances that are connected. It practically presents all the instances of the closest parent module.
Indirect Changes highlights all the changes in the design that are not Direct Changes. For example an output module could be instantiated outside the closest parent module design hierarchy, in "isolation" from the input module. As such these may be unexpected changes that lead to dangling ports.
All Changes highlights all the changes in the design. Here you see all the relevant instances. It is the union of Direct Changes and Indirect Changes.
Note 1: Changes are computed on all tops.
Example
We connect blue1: Blue ( output instance) to d1 : D ( input instance). b1 : B is the closest parent instance and B is the closest parent module. The relevant instances are highlighted.
The structural changes of the filters above are:
| Show Design Hierarchy | Minimal Path | Direct Changes | Indirect Changes | All Changes |
 |
 |
 |
 |
 |
IMPORTANT NOTE: This feature is currently supported only in the Old Design Hierarchy View. To switch to/from the Old Design Hierarchy View, go to Window > Preferences > DVT and toggle Switch to Old Design Hierarchy View