Simulate Translate Test

VTRAN Version 10.4.2 Release Update

Monday, 30 October 2017 22:07
Source III has recently released VTRAN/VUI version 10.4.2, in an effort to continue to offer new and useful updates for all of our VTRAN users. This release offers several new tools and fixes to help you with your translation efforts. These updates include: WFC_MODE support was added to the Advantest HP93000 Reader. HP93000 avc/dvc files that contain waveform character-based timing formats can now maintain that timing when they are read using the -WFC_MODE flag. The EXPLICIT_BIDIR_INACTIVE_MODE command has been added to the VTRAN OVF_BLOCK. This command causes the VTRAN VCD/EVCD, WGL, and STIL readers to use the '-', state character, to represent the inactive state on bidirectional signals. VTRAN COMMENT_BUS and COMMENT_BUSX commands now ignore non-printable characters (ASCII values < 0x20 or > 0x7E) contained in simulation comments encoded in bus state values. The SmarTest8 Writer module has a new default for signal groups and timing groups. An option has…

QA: STIL Timing Information to 93K

Monday, 26 June 2017 19:02
Source III offers award winning support for our clients, available to answer any queries and problems that you may have. Sometime we receive questions that have answers that we think may be relevant to both customers and non-customers alike. Below is a question about importing timing information from a STIL file to Advantest 93000. Question: We need to get timing information from the .stil file to import to timing information in 93k program. I tried using the –USE_PHYSICAL_WAVEFORMS and GENERATE_X1_TIMING switch’s to get usable information out of VTRAN in the X.dvc file. Also we are using WFC_MODE, but we did not get what we expected, please help. Answer: The first step is to turn off WFC-Mode in VTRAN. VTRAN cannot generate physical waveforms when WFC mode is active. In non-WFC, or "traditional" mode, STIL waveforms are returned as classic formats like RZ, RO, NRZ etc. with corresponding vector states. These…
Source III’s support department is always available to answer any questions you may have. When we feel that we’ve received a question that is useful to a wider audience, we like to turn it into a helpful blog post. A few weeks ago, we received a question about equation based timing format commands. Our answer is below. Question We were working on equation-based timing format/flow, and we added these commands.            -BASIC_TIMING_FORMULAS_B,          -USE_TIMING_PARAMS, I am getting this Warning, but my output seems to be OK. Warning: -USE_TIMING_PARAMS parameter is not supported for this timing format. Parameter will be ignored. Any idea why? Answer The -USE_TIMING_PARAMS is an optional parameter that allows for a user specified name to be output in the timing file in place of the constant value that would normally be seen. An example of how that would work is if you were translating a vcd or…
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…
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 spaces between signals, and how to remove them during conversion with VTRAN. Question: I’m using a canned reader for STIL patterns, and converting them to HP93000K format. After the conversion, the pattern looks like this: XXXXXXXX XXXX XXXXXXZZ 0 0 00 1 1 0 0 ; 1200 XXXXXXXX XXXX XXXXXXXZ 0 0 01 1 1 0 1 ; 1600 XXXXXXXX XXXX XXXXXZZZ 0 0 00 1 0 0 1 ; 2000 XXXXXXXX XXXX XXXXXXXZ 0 0 01 1 0 0 0 ; 2400 XXXXXXXX XXXX XXXZZZZZ 0 0 00 1 1 1 0 ; 2800 There is a space between each signal, and group of signals, which…