License Agreement

SOURCE III, Inc. SOFTWARE LICENSE AGREEMENT

CAREFULLY READ ALL THE TERMS AND CONDITIONS OF THIS AGREEMENT PRIOR TO USING THIS SOFTWARE. USING THIS SOFTWARE INDICATES YOUR ACCEPTANCE OF THESE TERMS AND CONDITIONS.

If you do not agree to these terms and conditions, please remove any files downloaded from our web site, delete any license keys, and your money will be refunded.

1. LICENSE: You have the non-exclusive right to use the subject program. This program can only be used on a single computer (or at a single site if a Network License, or on any of your corporate sites if a WAN license) by employees of your company. The use of the program by anyone outside your company is not allowed. You may not distribute copies of the program or documentation to others. You may not modify or translate the program or related documentation without prior written consent of Source III.

   YOU MAY NOT USE, COPY, MODIFY, OR TRANSFER THE PRORAM OR DOCUMENTATION, OR ANY COPY, EXCEPT AS EXPRESSLY PROVIDED IN THIS AGREEMENT.

2. BACK UP AND TRANSFER: You may make copies of the program solely for backup purposes. You many transfer and license the product to another party if the other party agrees to the terms and conditions of the Agreement. If you transfer the program, you must at the same time destroy any backup copies of the program and license keys you have. With an active maintenance and technical support contract, there is no charge to move the node-locked license to a new node. Source III requires only that it be provided with a written request, stating the old hostid, the new hostid and the assurance the software will not be run on the old machine after it is installed on the new machine.

3. COPYRIGHT: The program and its related documentation are copyrighted. You may not copy the program except for backup purposes and to load the program into the computer as part of executing the program. All other copies of the program are in violation of this Agreement. With this License Agreement, you are granted the right to print copies of the documentation (available from our web site) for internal use.

4. TERM: This license is effective until terminated. You may terminate it by destroying the program and license keys and all copies thereof. This license will also terminate if you fail to comply with any term or condition of this Agreement. You agree, upon such termination, to destroy all copies of the program and license keys.

5. LIMITED WARRANTY: THE PROGRAM IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. THE ENTIRE RISK AS TO THE RESULTS AND PERFORMANCE OF THE PROGRAM IS ASSUMED BY YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU (AND NOT SOURCE III OR ITS DEALERS) ASSUME THE ENTIRE COST OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION, FURTHER, SOURCE III DOES NOT WARRANT,GUARANTEE, OR MAKE ANY REPRESENTATIVES REGARDING THE USE OF OR THE RESULTS OF THE USE OF THE PROGRAM IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, CURRENTNESS, OR OTHERWISE, AND YOU RELY ON THE PROGRAM AND RESULTS SOLELY AT YOUR OWN RISK. NOTWITHSTANDING THE FOREGOING WARRRANTIES, LICENSOR REPRESENTS AND WARRANTS THAT THE LICENSED SOFTWARE CONTAINING OR CALLING UPON A CALENDAR FUNCTION, INCLUDING WITHOUT LIMITATION ANY FUNCTION INDEXED TO A CPU CLOCK, AND ANY FUNCTION PROVIDING SPECIFIC DATES OR DAYS, OR CALCULATING SPANS OF DATES OR DAYS, SHALL RECORD, STORE, PROCESS, PROVIDE AND WHERE APPROPRIATE, INSERT, TRUE AND ACCURATE DATES AND CALCULATIONS FOR ALL THOSE DATES AND SPANS, INCLUDING AND FOLLOWING THE DATE JANUARY 1, 2000. THE ABOVE IS THE ONLY WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PATICULAR PURPOSE THAT IS MADE BY SOURCE III ON THIS SOURCE III PRODUCT. NEITHER SOURCE III, OR ANYONE ELSE WHO HAS BEEN INVOLVED IN THE CREATION, PRODUCTIONS , OR DELIVERY OF THIS PROGRAM SHALL BE LIABLE FOR ANY INDIRECT, CONSEQUENTIAL, OR INCIDENTAL DAMAGES ARISING OUT OF THE USE, THE RESULTS OF USE, OR INABILITY TO USE SUCH PRODUCT EVEN IF SOURCE III HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR CLAIM. SOME STATES DO NOT ALLOW THE EXLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU.

6. MISC.: This License Agreement shall be governed by the laws of the State of California and shall inure to the benefit of Source III Corporation, its successors, administrators, heirs, and assigns.

Should you have any questions concerning this Agreement, please contact in writing to:

Source III, Inc.
3941 Park Drive #20-342
El Dorado Hills, CA 95762

Notes:

TERMS are Net 30 days.

VTRAN-P subscription licenses are specific to one or more translation paths. Paths between simulation environments (for example VCD to TDL_91, or WGL to Verilog testbench) begin at $6,000. Paths between simulation or ATPG environments and testers begin at $10,000 (for example WGL to Credence, or STIL to Agilent 93000). Please contact Source III for specific quotations.

For Licensing, Source III offers two mode options. The first is a NODE-LOCKED LICENSE which can be run on a single machine, either thru local login or thru remote login. Multiple copies of the program can be running at the same time. The second form of licensing is a SITE LICENSE which allows the software to run on any machine physically connected to the network at a licensed site. Any number of copies can be running simultaneously on different machines in the subnetwork.

In addition, Source III offers both annual subscription licenses and perpetual licenses.

For subscription licenses, maintenance and technical support are included. This maintenance and technical support includes telephone "hot line" and internet technical support as well as automatic updates of new releases via our web site. Pricing for a perpetual license includes 12 months of software maintenance and technical support. Following the first year, software maintenance and technical support for a perpetual license is available for 20% of the current license price per year.

Distribution of Software and documentation is done entirely electronically. The latest copies of our software, brochures and manuals are available from the Product pages and Download page of this web site. Software License Keys, for evaluation of the software as well as permanent keys issued from a Purchase Order, are delivered to customers via email. Due to this method of distribution, all software sales, whether in California or not are exempt from sales tax per the following regulation:

California Code of Regulation, Title 18, Chapter 4, Section 1502(f)(1)(D)

All prices are subject to change without notice.

VTRAN™ is a vector translation program which reads the state/time information from simulation or ATPG data files, performs some optional processing on this data and then re-formats it for any of over 30 popular logic simulators and testers. The program deals with the general class of problems involving simulation stimulus/results re-formatting encountered by designers who must deal with more than one logic simulation environment. A collection of TEST options for VTRAN™ also provide interfaces to many popular device testers, offering a direct path from logic simulation/ATPG vectors to test programs.

Applications

• Re-formatting existing simulation data files which were generated by one simulator into files compatible with another simulator./li>
• Translating state data files from logic analyzers, test programs or other data sources into stimulus files compatible with logic simulators. This includes the incorporation of pin timing.
• Modifying simulation data files including changing pin lists, pin order, bus radixes, time offsets, pin timing and time scaling.
• Translating simulation/ATPG output vector data or test programs into testbench data files for Verilog/VHDL resimulation and verification.
• Vector translation from simulation or ATPG-generated vectors into functional test vectors for physical device testers.
• Act as a front-end to graphical waveform tools enabling them to read and display nearly any vector data file.

VTRAN™ is able to handle a wide range of input data formats by essentially letting the user describe the format. This is done in one of two ways. The first way is with the User-Programmable Reader using a single, or a collection of format descriptors which the user customizes to describe the input data format. The input format parameters which can be specified by the user include:

• Pin names & order.
• Whitespace characters.
• Type & location of time tag, absolute or delta time.
• Location of state data & bus radixes used.
• Selection of TABULAR, SCRIPT or WAVE format.

In addition to this User-Programmable Reader, VTRAN™ also provides a comprehensive collection of "canned" readers for popular simulator, ATPG and tester formats. Check the latest release for a current list of these "canned" readers.

At invocation, a command file is specified which contains the VTRAN™ commands and descriptors. This file is composed of three major blocks; the OVF_BLOCK which specifies the format of the input data file, the PROC_BLOCK which defines any processing to be done on the data, and the TVF_BLOCK which defines the format of the output file and the target simulator.

The frustration of dealing with dissimilar simulator data formats is eliminated with VTRAN™. Files can easily be translated between most of the popular simulators in use today, with virtually any data manipulation desired. In support of vector translations from logic simulators or ATPG programs to physical device testers, VTRAN™ is unmatched for its speed, user friendliness and low cost. The new collection of Read-Back canned reader modules also provide a way to verify VTRAN™-generated test programs thru testbench re-simulation prior to loading on a tester.

VTRAN™ reads data files from simulators, or other sources, using one of two methods. For some of those more popular simulators, VTRAN™ has canned readers which know how to read the time/state information of those files. Canned readers are currently available for the following file formats:

• Verilog VCD (and EVCD) files
• Toshiba TSTL2 files
• Mentor LOG files and FORCE files
• WGL and TSSI TDS ascii files
• Valid Tabular I/O files
• Fujitsu FTDL files
• Synopses VSS WIF files
• IMS Test MEM format files
• TDL_91 format files
• Quickturn CBC and QUEST files
• STIL (1450.1999 IEEE Standard Test Interface Language) files
• HP-3070 PCF files
• VTRAN™-generated Teradyne Catalyst files
• VTRAN™-generated Teradyne J750 files
• VTRAN™-generated Teradyne J973 files
• VTRAN™-generated Teradyne FLEX files
• VTRAN™-generated Credence SWAV files
• VTRAN™-generated Agilent (HP)93000 files

Additional canned readers are released periodically.

Data formats for which a canned reader is not available can be read by VTRAN™ using its User-Programmable Reader Technology. Here, the user describes the format of data to be read using one or more "format strings" and VTRAN™ then uses these strings to extract the time/state information from the file. This method can be used with any tabular or script file format - whether created from a simulator, tester or logic analyzer.

When translating time/logic data from one simulation/ATPG/tester format to another, it is often necessary to modify this data to clarify its intent, support debugging methodologies and conform to the target simulator/tester parameters and constraints. VTRAN™ can perform an array of mapping and translation operations on the vector data it has read. These include:

• State Mapping
• Adding/removing pins
• Modifying timing (scaling, offsetting, shifting edges)
• Collapsing print-on-change data to cycle-data (cyclizing of vector data)
• Imbedding timing into cycle-data
• Separation of I/O data on bi-directional pins
• Merging of bi-directional data
• Masking vector data based on time windows, logic equations or state transition
• Defining strobe windows for outputs
• Pin name aliases
• Extract Repeats or Loops in vector data

All of these operations are under complete user control so that the data in the output (translated) file can be customized for specific needs.

Once a set of simulation data has been read, and optionally processed, the output file format can be selected from any of the following currently available simulator interfaces (not a complete list):

ABLE, CUPL, EPIC/nanosim, FSIM, FTDL, HILO, LASAR, LSIM, MAXPLUS, MENTOR, ORCAD, QUEST, QSIM, SILOS, SPICE, STIL, SUSIE, TDL_91, TDS(TSSI), TSTL2, VERILOG Testbench, VERILOG VCD/EVCD, VHDL Testbench, VIEWSIM, VTI, WAVES, WGL

In additional to these standard formats, a UDF (User Defined Format) is also available for defining a custom output format. New formats are being added constantly and custom formats can also be made available. With the TEST options, VTRAN™ can output vectors for physical device testers including:

Teradyne Catalyst, Teradyne J750, Teradyne J971/973, Teradyne FLEX, Credence SWAV, Agilent(HP)83000/93000, Advantest T66xx/T33xx, HP-3070, ITS9000 and IMS.

There are two command blocks required in every VTRAN™ command file, and a third optional command block. The first of these is the OVF_BLOCK, which contains commands describing the format of data in the Original Vector File.

The second required command block is the TVF_BLOCK, which contains commands that essentially tell VTRAN™ how to format the vectors for the Target Vector File.

The third (optional) command block is the process block (PROC_BLOCK) which must occur between the OVF_BLOCK and TVF_BLOCK in the file and is used to specify further processing to be done on the data prior to output formatting.

The VTRAN™ command file structure can be summarized as follows:

OVF_BLOCK

BEGIN
OVF_BLOCK_COMMANDS
END

PROC_BLOCK {Optional}

BEGIN
PROC_BLOCK_COMMANDS
END

TVF_BLOCK

BEGIN
TVF_BLOCK_COMMANDS
END

END

Statement text in the VTRAN™ command file is not case sensitive. However, the case of pin names is preserved in the TVF file. Pin names can be composed of printable ASCII characters with the exception of the following: space, comma, semicolon, <, >, [, ], {, }, (, ), =, \, &, | and @.

AUX_FILE [=]"filename";

Used to specify an auxiliary file for some canned readers.

BEGIN_LINE [=] n;

Used by the User-Programmed Reader to define the line number in the OVF file at which VTRAN™ should begin processing vectors.

BEGIN_STRING [=] "string";

Used by the User-Programmed Reader to define a unique text string in the OVF file after which VTRAN™ should begin processing vectors.

BIDIRECTS [=] pin_list;

Defines the names and order of pins in the OVF file which are bidirectional.

BUSFORMAT radix; or BUSFORMAT pin_list = radix;

Specifies the radix of busses in the OVF file. (User-Programmed Reader)

CASE_SENSITIVE;

Allows there to be more than one signal with the same name spelling but differing only in case of letters in the name.

COMMENTS [ON | OFF];

Enables/Disables the passing of comments from the OVF to the TVF.

GROUP n [=] pin_list;

Together with the $gstatesn keyword, it tells VTRAN™ how the pin states are organized. (User-Programmed Reader)

INPUTS [=] pin_list;

Defines the names and order of input pins in OVF file.

MAX_UNMATCHED [=] n [verbose]:

Specifies the number of, and information contained in, warnings for lines in the OVF which don't match a format_string. (User-Programmed Reader)

MERGE_FILE,  INPUTS/OUTPUTS/BIDIRECTS, orig_file, time_offset, .. end_Merge statements;

Used to merge or concatenate more than one input vector file.

ORIG_FILE [=] "filename";

Used to specify the OVF file name to be translated.

OUTPUTS [=] pin_list;

Defines the names and order of output pins in OVF file.

SCRIPT_FORMAT [=] "format#1" [, . ."format#n"] ;

Format descriptors for User-Programmed reader. For canned readers, un-quoted reader module name is specified instead of descriptors.

TABULAR _FORMAT [=] "format #1" [, . . "format#n"] ;

Format descriptors for User-Programmed reader. For canned readers, un-quoted reader module name is specified instead of descriptors.

TERMINATE TIME [=] n;

TERMINATE LINE [=] m;

TERMINATE STRING [=] "string";

Defines where in the OVF to stop processing, at a certain time (n) , line number (m) or when a "string" is reached. This is used only by the User-Programmed Reader.

WAVE_FORMAT [=] "format #1" [, . . "format#n"] ;

Format descriptors for User-Programmed reader.

WHITESPACE [=] 'a','b', 'c', . . ,'n';

Defines characters in the OVF file that are to be treated as though they are space, (they are ignored - User-Programmed Reader).

ADD_PIN pinname = state1 [WHEN expr=state2, OTHERWISE state3];

Tells VTRAN™ to add a new pin to the TVF, and allows you to define the state of this pin.

ALIGN_TO_CYCLE [-warnings] cycle pin_list @ time, . . . , pin_list @ time ;

Print-on-change vectors can be mapped to a set of cycle data, the state of each pin in a given cycle is determined by its state at a specified strobe time in the OVF.

ALIGN_TO_SIGNAL [-novector] ref A->B SAMPLE=pinlist @ offset;

Print-on-change vectors are mapped to cycle-based vectors, with each cycle boundary determined by a reference signal transition, and the state of each pin in a given vector determined at the specified strobe time from the start of a cycle.

ALIGN_TO_STEP [-warnings] step [offset];

Forces a minimum time resolution in the TVF.

AUTO_ALIGN [-warnings] cycle;

Collapses print-on-change data in the OVF to cycle data by computing strobe points from information given in the PINTYPE commands.

BIDIRECT_CONTROL pin_list = dir WHEN expr = state ;

Separates input data from output data on bidirects under control of a pin state or logical combination of pin states.

BIDIRECT_CONTROL pin_list = direction @ time ;

Separates input data from output data on bidirects based upon when the state transitions occur.

BIDIRECT_STATES INPUT state_list, OUTPUT state_list ;

Separates input data from output data on bidirects where unique state characters identify pin direction.

CHECK_WINDOW pinlist @ start1, end1 [start2, end2];

For translating print-on-change data to event output formats, specifies window(s) during which output data is checked in target file; output data is masked to don't care outside of window(s).

CYCLE [=] n;

Used to specify the time step between vectors in the OVF when the format of the vectors does not include a time stamp.

CYCLE_SHIFT [fill_character=c] pinlist @ n;

Causes the states on specified signals in all vectors to be shifter either forward or backwards in time by (+/-)n vectors.

DISABLE_VECTOR_FILTER;

Can be used to disable filtering of redundant vectors.

DONT_CARE 'X';

Defines the character state to which output pins should be set outside of their check windows.

EDGE_ALIGN pinlist @ rtime [,ftime] [xtime];

Can modify pin transition times by snapping them to predefined positions within each cycle.

EDGE_SHIFT pinlist @ rtime [,ftime] [,xtime];

Can modify pin transition times by shifting them by fixed amounts.

MASK_PINS [mask_character ='X'] [pin_list] @ t1, t2 [-CYCLE];

MASK_PINS [mask_character ='X'] [pin_list] @ CONDITION logic_expr ;

MASK_PINS [mask_character="X"] [pinlist] @ TRANSITION A->B [,-1] [, +n];

MASK_PINS [mask_character="X"] [pinlist] @ CONTROL_TRANSITION ctl_pin A->B [,start] [, end];

MASK_PINS pinlist @ SEQUENCE "input_sequence", "output_sequence";

Masks the state of specified pins to the mask_character within the time range between t1 and t2, when a specified logic conditions exists on other pins, for a number of cycles surrounding the pin's transitions, or for a number of transitions surrounding a control pin transition. The SEQUENCE option replaces specified state sequence with new one.

PINTYPE pintype pin_list @ start1 end1 [start2, end2] ;

Defines the behavior and timing to be applied to input and/or output pins during translation.

POIC;

Specifies that vectors in the OVF file should be translated to the TVF only when at least 1 input pin has changed in the vector (used only with CBC format).

SCALE [=] nn;

Used to linearly expand or reduce the time line of the OVF. Happens prior to any timing modifications. Use only with print-on-change input formats.

SEPARATE_TIMING;

Tells VTRAN™ not to incorporate pin timing and behavior into the vectors themselves.

STATE_TRANS [dir] 'from1'->'to1', . . ;

Defines a mapping from pin states in the OVF file to states in the TVF file. [dir] can be ALL_INPUTS, ALL_OUTPUTS, BIDIR_INPUTS, BIDIR_OUTPUTS, PURE_INPUTS, PURE_OUTPUTS.

STATE_TRANS_GROUP pin_list = 'from1'->'to1', . . ;

Supplements the STATE_TRANS command by providing state translations on an individual pin or group basis.

TEMPLATE_CYCLIZATION [params] ;

Used with TIMESET blocks to invoke cyclization of print-on-change data with multiple timesets.

TIMESET name ... ENDTIMESET;

Defines timeset block of CYCLE, PINTYPE and IDENTIFIER statements (used with TEMPLATE_CYCLIZATION).

TIME_OFFSET [=] n ;

When reading the vectors from the OVF, the time stamp can be offset by an arbitrary amount.

ADD_VTB_TEXT = "text", Before|After, Location ;

Mechanism for adding text (statements or comments) to Verilog Testbench files.

ALIAS ovf_name = tvf_name, . . . ;

ALIAS "ovf_string" = "tvf_string";

Provides a way to change the names of pins listed in the OVF, for listing in the TVF. The first form changes individual pin names, thesecond form does global string replacement in all pin names.

ALIAS_TSET ovf_tsetname = tvf_tsetname;

Provides a way to change the names of timesets found in the OVF, for listing in the TVF.

BIDIRECTS [=] pin_list;

Defines the names and order of pins to be listed in the TVF file which are bidirectional.

BUSFORMAT radix;

BUSFORMAT pin_list = radix;

Specifies the radix of busses in the TVF file.

COMMAND_FILE [=] "filename";

Allows the user to specify the name of a separate output command file for the target simulator, in addition to the vector data file.

DEFINE_HEADER [=] "text string";

Allows you to inhibit the automatic generation of headers and replace it with a custom text string. For tester formats this inserts text at the top of the test program.

DELETE_PINS pinlist;

Removes the listed pins from the output (TVF) file.

FORCE_SEQUENTIAL_BUSSES [+|-];

Forces busses with non-sequential indexes to be sequential.  For Verilog Testbench format, busses must have sequential indexes.

HEADER [=] n;

Causes a vertical list of the pin names to appear as comments in the TVF every n vector lines.

INPUTS [=] pin_list ;

Defines the names and order of pins to be listed in the TVF file which are inputs.

INPUTS_ONLY;

Causes only input and the input versions of bidirectional pins to be listed in the TVF.

LOWERCASE;

Forces all pin names in the TVF to use lower-case letters.

MERGE_BIDIRECTS state_list ;

MERGE_BIDIRECTS rules = n ;

Merges the input and output state information of a bidirectional pin to a single pin after it has been split and processed.

OUTPUTS [=] pin_list ;

Defines the names and order of pins to be listed in the TVF file which are outputs.

OUTPUTS_ONLY;

Causes only output and the output versions of bidirectional pins to be listed in the TVF.

PIN_INFO_FILE = filename, "file_format";

Specifies file containing signal name aliases and tester channel information.

RENAME_BUS_PINS [buslist =] format;

Provides a way of globally modifying all bus names [or a specified list of them] in the TVF to scalar names.

RESOLUTION [=] n;

Specifies the resolution of time stamps in the output vector file (n = 1.0, 0.1, 0.01, 0.001. 0.0001, 0.00001 or 0.000001).

SCALE [=] nn ;

Linearly scales all times to TVF. Used with event-based output formats.

SIMULATOR [=] name [param_list];

Defines the target vector file format to be compatible with the simulator named.

STOBE_WIDTH [=] n;

Used with several of the simulator interfaces to define the width of an output strobe window.

SYSTEM_CALL ". . .text . . . ";

Upon completion of translating vectors from the OVF to the TVF, VTRAN™ sends this text string to the system just prior to termination.

TARGET_FILE [=] "filename";

Specifies the name of the output Target Vector File.

TESTER_FORMAT [=] testername [param_list];

Defines the target tester for which the output file should be formatted.

TITLE [=] "title";

Specifies a special character string to be placed in the header of certain simulator vector files.

UPPERCASE;

Forces all pin names in the TVF to be listed with upper-case letters.