Troubleshooting
Each feature page ends with an If it doesn’t work table for its own symptoms. This page covers problems that affect several features at once, and points to the page that owns each fix.
Start here
Section titled “Start here”| You see | Likely cause | What to do |
|---|---|---|
| Nothing is colored, or the file looks like plain text | The plugin is not installed or enabled, or the file has another extension | Installation: if it doesn’t work |
| An “undeclared name” underline, “not found” in Find Usages, or code you expect is greyed out | A macro is not defined where the IDE looks (an `ifdef branch is inactive), the setting that evaluates `ifdef is off, or the file is not covered by your compile file (the simulator’s .f list of sources, like sim.f in the sample project) |
Conditional compilation |
| A check you expect shows no underline | The check (an inspection) is switched off, or indexing has not finished | See Undeclared names. Open Settings (⌘, on macOS, Ctrl+Alt+S on Windows/Linux), Editor | Inspections | SystemVerilog; wait for the progress bar at the bottom right |
| Completion or Parameter Info is empty | Indexing, or the declaration is not in the project | Code completion |
UVM names (uvm_driver, uvm_info) do not resolve |
The UVM sources are not in the project | Navigation does nothing below |
| A balloon about the license | The license is missing or expired | License |
Go to Declaration or Find Usages does nothing
Section titled “Go to Declaration or Find Usages does nothing”Go to Declaration is ⌘B / Ctrl+B (or ⌘-click / Ctrl-click) and Find Usages is ⌥F7 / Alt+F7. When they find nothing, the editor stays where it is or the Find panel says nothing was found.
| Likely cause | What to do |
|---|---|
| The project is still indexing (the IDE scanning your files so that it can look names up; a progress bar at the bottom right shows it) | Wait until the progress bar is gone |
The declaration is not in the project. UVM library classes resolve only when the UVM sources (the folder with uvm_pkg.sv and uvm_macros.svh) are inside the project folder, or are listed in your compile file (+incdir+<uvm>/src and <uvm>/src/uvm_pkg.sv) |
Add them, then wait for indexing again; see Known limitations |
| The name is declared by a macro that is called outside a class body | Names a macro declares among a class’s items (type_id from uvm_component_utils) do work, see UVM testbenches; names a macro declares anywhere else are not navigable. Macro names and the names passed to a macro are navigable (Macros) |
| The name is in greyed-out code | Its `ifdef branch is inactive; see Conditional compilation |
Rename reports a conflict
Section titled “Rename reports a conflict”The rename would change what some code refers to. A dialog titled Conflicts Detected (or a similar list) quotes the code whose meaning would change. See Rename conflicts for what each message means. Pick another name, or choose Cancel to leave the code unchanged.
Results look out of date
Section titled “Results look out of date”If files were changed outside the IDE (a git checkout while the IDE was closed, a generated file) and results do not
match the code, wait for indexing to finish, then use File | Invalidate Caches…, leave the checkboxes as they are,
click Invalidate and Restart, and wait for the progress bar after the restart. This only clears the IDE’s index and restarts it; your files and settings are kept.
License notification
Section titled “License notification”A balloon about the license has the action Register…; see License.
Still stuck?
Section titled “Still stuck?”First check Known limitations: the behaviour may be documented there. If not, report it where you got the plugin and include:
- the IDE and plugin versions (Help | About, and Settings | Plugins | Installed);
- a small file that reproduces the problem, with the compile file if one is used;
- the IDE log (Help | Show Log in Finder on macOS, Help | Show Log in Explorer on Windows, Help | Show Log in Files on Linux).