Simulate Translate Test

Customer Support Question: Viewing a STIL File in DFTView with GTKWave Viewer

Sunday, 30 April 2017 16:13

Our Support Team is always available to help our clients with their vector conversion needs. Sometimes, we receive a question that is applicable to both current and future clients, and we share it here on the website. The following is a question about viewing a STIL file in the GTKWave viewer with DFTView.

Question: I’m working with DFTView on Linux. I am having a problem getting DFTView to work with GTKWave Viewer. When I try to view a .stil file, I receive the following message:

Warning: Tab 1 unable to communicate with GTKWave... retrying...
Warning: Tab 1 unable to communicate with GTKWave... retrying...
Warning: Tab 1 unable to communicate with GTKWave... retrying...

Please let me know what needs to be done to fix this problem.

Answer:

DFTView 10.0 (shipped with VTRAN 10.0) had a known connectivity issue with GTKWave which was addressed in release 10.1.  In addition, we found that GTKWave 3.3.34 as installed with Ubuntu 15.04 (but also potentially on other Linux distros) was shipped with memory debugging enabled which interferes with communication with DFTView (as it does with all other external applications).

We strongly recommend that you upgrade to the latest available software release for VTRAN and DFTView which is currently 10.4 and is available in the "Source III Software Bundle" available at:  http://sourceiii.com/download-software.html .

Next, if you are running the aforementioned 3.3.34 version of GTKWave you might want to try a precompiled version of GTKWave 3.3.46, which Source III has prepared (mostly for systems without access to a current version).  You can directly download the 32-bit or 64-bit precompiled binaries for Linux here:

http://sourceiii.com/files/dftv_support/gtk2/gtkwave.linux32.tar.gz

http://sourceiii.com/files/dftv_support/gtk2/gtkwave.linux64.tar.gz

Unpack the relevant file into a new, empty directory (this is important as the contents will be unpacked into the current directory) and then add this location to the beginning of your $PATH.  This is explained in more detail in the README file included in the package.