Timing Diagram Editing and Analysis

11.12 STIL Test Vectors - Export

11.12 STIL Test Vectors - Export

Previous topic Next topic  

11.12 STIL Test Vectors - Export

Previous topic Next topic  

STIL format is compatible with the IEEE Standard P1450 Standard Test Interface Language and it is used to produce files for test equipment. WaveFormer Pro can generate stimulus vector files in this format. Below is a list of rules and objects that generate code:

This is a clocked format so the timing diagram must have at least one clock and one or more signals with waveforms. See 11.3 Export General Instructions and the subsection on clocking signals. Signals are sampled using the first clock in the timing diagram. Normally the rising edge of the clock is used as the sampling time. However, if the clock's invert property is checked then the falling edge is used as the sampling time. The clock's period property sets the Waveform Table Period in the STIL file.

In the SignalGroups section of the STIL file, a group called ALL is defined as:

ALL = each input signal(black) + each output signal(blue) + each bi-directional inout signal(black and blue)

A waveform vector ALL is generated for each sampling time of the clock.

Signals are sampled from time 0 to the last simulation time. The last simulation time is determined by the first End Diagram Marker in the diagram. If there are no end diagram markers, then the last simulation time defaults to the time of the last drawn signal event in the diagram.

If a signal ends early and there is no event at the current sampling time, then the state at that time is recorded as P for input (black) signals or X for output (blue) signals.

The names of the Timing, Pattern Burst, and Pattern sections can be changed by editing the first three variables in the stil.epl file.

Note: The definitions of input and output are exactly opposite in the WaveFormer Pro and the STIL language. This is because each format defines waveform direction in terms of what is most important to the format. For example, the STIL language defines waveform direction in terms of the tester (inputs drive the tester, outputs are generated by the tester). WaveFormer defines waveform direction in terms of the generated testbench (inputs come from the device under test, or tester, and outputs are generated by the testbench and drive the tester). The WaveFormer STIL documentation uses input/output as defined by STIL, and also the color that the waveforms appear in WaveFormer input (black) and output (blue). General WaveFormer Pro documentation uses the normal WaveFormer definitions.

The naming conventions for representing the signal states are:

Input Signals (black):

 '1' => 'ForceUp' (Waveform: high state),

 '0' => 'ForceDown' (Waveform: low state),

 'N' => 'ForceUnknown' (Waveform: valid or invalid state),

 'P' => 'ForcePrior' (Waveform: unknown state),

 'Z' => 'ForceOff'(Waveform: tri state),

Output Signals (blue) :

 'H' => 'CompareHigh' (Waveform: high state),

 'L' => 'CompareLow' (Waveform: low state),

 'X' => 'CompareUnknown' (Waveform: valid, invalid or unknown state),

 'T' => 'CompareZ' (Waveform: tri state),

InOutput signals (black and blue) : Input and Output signals representation.