Simulate Translate Test

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 states are then further usually modified with STATE_TRANS to map any odd waveform characters to 0, 1, Z, L, H, M or X - and these are the values that the physical waveforms use. in WFC Mode any character (upper or lower case) and/or any digit can be a waveform character.

If you're interested there's a very thorough discussion of STIL translations with WFC Mode in a dedicated Application Note available on the Source III website: http://www.sourceiii.com/notes-wfc-mode.html

Disable the -WFC_MODE option in the OVF block (and keep the -GENERATE_PHYSICAL_WAVEFORM option) and you'll get the physical waveform timing file you expect. In addition, you'll likely need to alter your STATE_TRANS statements when WFC_MODE isn't in use (and in point of fact, no STATE_TRANS is generally used when WFC Mode is enabled as all waveform table entries and vector waveform characters are translated directly).

Here's a set of STATE_TRANS statements which will result in an identical vector file as the one you receive when -WFC_MODE is active:

STATE_TRANS PURE_INPUTS 'U'->'1', 'D'->'0', 'N'->'0';

STATE_TRANS BIDIR_INPUTS 'U'->'1', 'D'->'0', 'N'->'0', 'Z'->'X';

STATE_TRANS PURE_OUTPUTS 'x'->'X', 'l'->'0', 'h'->'1', 'T'->'M';

STATE_TRANS BIDIR_OUTPUTS 'x'->'X', 'l'->'0', 'h'->'1', 'T'->'M';

If you use the VTRAN User Interface (VUI) you'll see that it auto-generates STATE_TRANS statements which map a lot more state characters for STIL -> 93K translations. This may or may not be useful to you for other translations.