If the user interface of Sigasi Visual HDL (SVH) is unresponsive, you can interrupt the internal compilation process by pressing the stop button in the progress view. To activate the progress view, select Window > Show View > Other… > General > Progress, or click the tiny conveyor belt icon , on the right side of the status bar.
SVH has a built-in profiler. By default this profiler is not active.
On some occasions we’ll ask you to provide an anonymized performance snapshot from the profiler.
To obtain this snapshot, follow the steps below.
Activate the profile using Help > Sigasi > Performance > Start Async Sampling
On Windows, use Help > Sigasi > Performance > Start Sampling instead.
Perform the laggy operations in SVH
Stop the profiler using Help > Sigasi > Performance > Stop Profiling
It may happen that, as part of a support case, we’ll ask you to
provide an anonymized memory snapshot of a running Sigasi application.
To obtain this snapshot, select Help > Sigasi > Performance >
Capture Heap . You’ll be prompted for a location and a filename to
store the memory snapshot.
The snapshot you’ve obtained needs to be obfuscated to anonymize it and it needs to be uploaded.
For this a snapshot_anonymizer script is provided in the SVH installation folder.
You can verify the obfuscation first before sending the uploading the snapshot to us.
Sigasi support will provide instructions for uploading the snapshot.
If you edit a file outside of SVH with an external editor, SVH will normally notice the changes and ask if you want to load the changes. If
it doesn’t, you can refresh the editor’s content by pressing F5 or by right-clicking a file or a project in the project explorer and
selecting Refresh.
By default, SVH assumes that all VHDL or Verilog files are part of the project. However, some projects may contain multiple files with older or alternative definitions of a VHDL object. We call these stale files, because they are no longer used. In such a case you will want SVH to ignore certain files.
On some computers, the standalone version of SVH will fail to start with an error message similar to: “Could not create the Java virtual machine.” The reason is that the Java virtual machine tries to allocate more memory than what is available. Note that we recommend a minimum of 8 GB of free memory.
In order to solve this, you can decrease the default heap size settings. You can do this by adding following lines to sigasi.ini or eclipse.ini in your SVH installation folder:
-vmargs
-Xmx1000m
This sets the maximum heap size to 1000 MB (instead of the standard 8 GB).
Note: Do not use eclipsec.exe, as this will ignore all of the settings configured in the eclipse.ini file.
If you ever suspect that the state of your project is inconsistent in SVH, you can do one or all of the following things. Consider these
steps to be advanced usage; you should not need them during normal operation.
Sometimes markers remain visible, even after the problem is fixed or when a file is excluded from compilation. We call these stale markers and they are can be caused by a crash during compilation.
You can delete these stale markers from the Problems View: In the Problems View, select the markers and press DEL (or right-click and select Delete).
Note that during the next build, the tool may generate new markers. If you want to suppress certain warnings, you can configure the linting rules.
For faster performance SVH is using a cache.
Sometimes the cache can get corrupted which might cause internal errors.
The cache is located in your workspace.
By default, SVH’s workspace is located in ${HOME}/workspaceSigasi.
To remove the cache, stop SVH and delete the folder workspaceSigasi/.metadata/.plugins/com.sigasi.hdt.shared.ui/resource.cache/sigasiBuildCache.
Much of your configuration and cached data is stored in your workspace.
By default, SVH’s workspace is located in ${HOME}/workspaceSigasi.
A lot of this data is stored in the hidden .metadata directory.
Sometimes, a part of your metadata can become corrupt.
It can help to remove the .metadata directory (take a backup first!).
This clears all of your workspace state.
You will need to enter your license code again.
You will need to import your projects again. Import > General > Existing Projects into Workspace
If you are using the integration with Intel Quartus. Some people keep getting a dialog box that says something like:
Incompatible version of Quartus
Project interface was created with an older, incompatible version of Quartus.
Is it OK to upgrade the project to match the installed version of Quartus?
Obviously, you should upgrade the project. If this message keeps popping up, you may want to check that SVH is using the correct version of Quartus, in the SVH application: Window > Preferences > Sigasi > External Compilers > Intel Quartus.
The version number of your SVH: Help > About Sigasi > Installation details Note that the version number contains the date of the release. (For example, version 2.0.1.20110809… was released on August 9, 2011.)
The log file: Help > Open Log
This website uses cookies. By
continuing to use this site you are giving consent to cookies being used.
Accept & close
, on the right side of the status bar.
icon in the project explorer view.