Home

XTOS Pattern User Manual (P/N 57010495 R 6)

Contents

1. m H w 113 Pattern Block This Pattern block is the main section of a STIL pattern This block defines the contents of the pattern vectors and contains one or more of the following Pattern statements 1 14 1 Pattern File STIL Description 9 9 6 9 6 6 9 6 6 ooo 6 9 6 6 6 6 6 6 6 6 9 6 9 6 6 6 6 6 6 6 6 6 9 9 6 9 6 6 6 6 6 6 6 e 6 6 e ooo o o WaveformTable reference W waveformTable_name defines the waveform table to use for the Vector translation Vector V defines stimulus and response for one test vector Condition C defines a stimulus and or response to be set up but deferred from being performed until a Vector statement is defined Call Call procedure name Where procedure is a previously defined Procedures block section XTOS replaces the Call statement by in lining the vectors in the procedure for a regular procedure If the procedure is a NPTSubroutine procedure then the Call is converted to a Call opcode Macro Macro macro name lnitiates the previously defined MacroDefs block section XTOS replaces the Macro statement by in lining the vectors in the Macro Defs block Loop Loop n Where n is an integer number of times on which a block of pattern statements is looped MatchLoop MatchLoop n Where nis an integer number of times on which a block of pattern statements is looped until all pattern statements are executed without differences between the output information in t
2. event STIL s event state see Event States in STIL on page 1 9 The relationship between the period name or sequence name of a test program s Timing block and resource tag in a STIL pattern is shown in Figure 1 1 XTOS Timing Block XTOS STIL Pattern Timing name norm_timing gt Timing WaveformTable _default_WFT_ Period 5ns lt TimingDomain name main gt lt Period name lt Value gt 5ns lt Value gt Waveforms lt SignalRef name pi gt 01 1 2ns D U lt Waveform name Sea mpi CSeq23 Zz ons z lt Time gt 1 2ns lt Time gt so A lt Seqy gt LH Ons X 40ns lt Event gt DF lt Event gt lt Waveform gt lt Seqz gt T Ons X 40ns T lt Waveform name lt Time gt 0ns lt Time gt lt Event gt DZ lt Event gt lt Waveform gt lt SignalRef gt lt Timing gt STIL 1450 3 lt Resource Tag gt Figure 1 1 Timing Block and STIL Pattern Connection 19 Resource Tags As per the P1450 3 extension XTOS software uses the resource tag period name lt sequence name gt to map between the waveform character WFC and the timing sequence name in the test program The lt period_name gt and lt sequence_name gt must be the timing sequence for the corresponding signal in the Timing block of the test program If these names are not found in the corresponding Timing block then timing shaping error will happen after the pattern is installed
3. Cbus Cbus D gt 01 Ons D U Cbus Z gt Z Ons Z Cbus S LH 25ns L H Dbus Dbus D 01 Ons D U Dbus Z Z Ons Z Dbus S LH 25ns L H If F2 data is used for some of the signals then the representation of multiple data waveform is needed The bracketed event 0 represents the first F data and the bracketed event 1 represents the second F data Timing Vec Def WaveformTable VecDef_0 period 0 Period 10ns Waveforms Abus Abus DF2 aA 0ns D U 0 50ns D U 1 Abus Z Z tons z Bbus lt Bbus_SF2 gt bB 25ns L H 0 75ns L H 1 lt Bbus_X gt X Ons x Cbus lt Cbus D gt 01 Ons D U lt Cbus_Z gt Z Ons z Dbus lt Dbus S LH 25ns L H 110 PatternBurst and PatternExec Blocks These two blocks are required blocks in the XTOS pattern files They ensure that the PatternExec block contains the name of the PatternBurst block and that the PatList contains the name of the Pattern block XTOS software uses functional equivalent constructs known as functional test templates and the PatternBurst block from the test program in place of these blocks 1 12 111 1 Pattern File STIL Description 6 6 ee e ooo o o The syntax of the PatternBurst is PatternBurst pat burst name PatList Pattern or burst name The syntax of the PatternExec is PatternExec pat exec name Timing timing
4. 1 Pattern File STIL Description 192 Event States in STIL STIL has a total of 23 event states They have fixed value and purpose Table 1 1 through Table 1 4 list the available event states Table 1 1 Drive States Drive State Description Timing Events D ForceDown DO U ForceUp D1 Z ForceOff DZ P ForcePrior NOP N ForceUnknown DZ Table 1 2 Compare State Compare State Description Timing Events L CompareLow TO H CompareHigh T1 X or x CompareUnknown X T CompareOff TZ V CompareValid X CompareLowWindow TO h CompareHighWindow T1 t CompareOff Window TZ V CompareValidWindow X Table 1 3 Expect States Expect State Description Timing Events R ExpectLow G ExpectHigh X Q ExpectOff X M Marker X XTOS Pattern User Manual P N 57010495 Rev 6 Table 1 4 Indeterminate States Indeterminate State Description A LogicLow DZ B LogicHigh DZ F LogicZ DZ Unknown DZ 193 Waveform Character The waveform character WFC is a user defined ASCII character representing a timing sequence The waveform character can be one of 63 characters upper case and lower case alphabetic numeric and underscore The general convention to use the WFC and representations are listed in Table 1 5 Table 1 5 WFC Conventions WFC Conventional Waveform Character Representation 0 Drive low 1 Drive hi
5. PatternBurst dummy Pattern Pass all W Vec 0 V Abus 00 Bbus LL v Bbus LH Abus still has value 00 V Abus 10 Bbus holds value of LH Loop 1000 Repeat 1000 times V Abus 11 Bbus HH lt Abus Aa Bbus Bb V Abus aa Bbus bb Vec_1 Change Waveform table from Vec 0 to Vec 1 Bbus 00 Abus LL Abus LH Bbus holds value of 00 Bbus 10 Abus HL Bbus 11 Abus holds value of HL 1 19 XTOS Pattern User Manual P N 57010495 Rev 6 6 o 6 9 6 6 6 06 6 6 6 9 6 6 6 6 6 6 6 9 6 6 9 6 6 6 6 6 6 6 6 o6 e 5 The Include file pattern include inc for the above Pattern is STIL 1 0 TRC D08 Signals Abus 0 InOut Abus 1 InOut Bbus 0 InOut Bbus 1 InOut SignalGroups Abus Abus 1 Abus 0 Abus 1 is MSB Abus 0 is LSB Bbus Bbus 1 Bbus_0 allPins Abus Bbus Abus 1 is MSB Bbus 0 is LSB Timing Vec Def WaveformTable Vec_0 period 0 Period 10ns Waveforms Abus Abus D gt 01 Ons D U Abus D2 aA Ons D U 50ns U D Bus Bbus S LH 25ns L H lt Bbus_S2 gt bB 25ns L H 75ns H L WaveformTable Vec_1 period 1 Period 10ns Waveforms Abus Abus S LH 25ns L H Bbus Bbus D 01 Ons D U 114 2 Example 2 A pattern that uses 2 bits of functional data per pin F2 pin mode Application of W V and Loop statemen
6. Vector sigl 10 Generator trigger DoMyTool here NPTGenerateTrigger doMyTest Vector sigl 11 Vector sigl 00 Vector sig1 01 Generate trigger ToolIsDone here NPTGenerateTrigger testIsDone Vector sigl 11 NPTWaitTrigger endTest Vector sig1 00 MatchLoop Infinite Vector sigl 01 BreakPoint Vector Vector sig1 00 Continuous Call Application The test system supports continuous as one flavor of sync trigger Support Continuous Loop is mapped to WUS Wait Until Sync and continuous subroutine is mapped to CUS Call Until Sync 2 5 XTOS Pattern User Manual P N 57010495 Rev 6 6 9 6 6 9 6 6 6 6 6 6 00000000000 6 6 6 06 6 9 6 6 6 6 6 6 6 6 9 6 6 06 6 0000000000000 6 9 6 6 6 6 6 6 e 6 6 Example Continuous Loop UserKeywords NPTTriggerDef NPTWaitTrigger NPTLatencyPipeDef NPTTriggerDef CPUResumePattern NPTLatencyPipeDef 400 Pattern TRY WaveformTable MY WFT Vector sigl 00 sig2 11 NPTWaitTrigger CPUResumePattern Vector sigl 00 MatchLoop Infinite Vector sigl 01 BreakPoint Vector Vector sigl 11 Vector sigl 00 The trigger CPUResumePattern consumes one SST Select Sync Type location This trigger comes from the CPU in the test template code Waitfor Trigger Assignment SST 0 CPUResumePattern 0 0 Example Continuous Subroutine Any Call instruction proceeded by NPTWaitTrig
7. lt Domain gt lt DomainList gt lt Composite gt lt blocks gt 5 3 2 XTOS Pattern CompositeLink Command Line Interface Windows 2000 The command line interface for the XTOS Pattern compositor is as follows XTOS release_numbenbin CompositeLink exe Typing the above command with the help parameter displays the following command usage for the pattern compositor usage XTOS release_ number bin CompositeLink exe options lt CompositeFile gt Required Arguments lt CompositeFile gt Name of the Composite file which is to be parsed Optional Arguments help Display help message noxml No Composite XML file is needed a single pof file has to be given as input The CompositeLink application the compositor parses the input XML block containing the details on patterns to be composited and creates a composite pattern object file composite domain name cpof containing the shared data by the patterns in the composite In the multiple time domain applications multiple composite object files are generated one for each time domain 5 3 3 XTOS Pattern CompositeLink Command Line Interface Solaris The command line interface for the XTOS Pattern compositor is as follows XTOS release_number bin CompositeLink exe Typing the above command with the help parameter displays the following command usage for the pattern compositor usage XTOS release number bin CompositeLink exe options lt CompositeFile gt Required
8. 6 6 0 6 6 6 6 6 6 6 6 6 6 6 9 6 ooo 6 6 6 6 6 6 e oe 9 e 5 6 4 Index Numerics 96 pin DC Channel instrument pattern application 2 10 timing block 2 10 usage model 2 10 A analog support capture signal 4 1 example 4 1 source signal 4 1 annotation statement 1 21 STIL 1 21 syntax 1 21 arguments 5 2 5 4 5 5 ASCII 1 10 ATPG tool 1 3 3 1 B block composite 5 6 header 1 3 MacroDefs 1 13 NameMap 1 3 5 2 pattern 1 12 1 14 1 18 PatternBurst 1 12 1 18 PatternExec 1 12 1 18 procedure 1 12 1 13 ScanChain 1 7 ScanStructure 1 6 3 2 shift 3 1 SignalGroups 1 5 1 18 signals 1 4 1 18 STIL 1 3 block cont timing 1 7 1 18 2 10 WaveformTable 1 7 1 18 BNZ operation 1 17 BreakPoint statement 1 15 2 7 C call match 2 8 statement 1 13 1 14 1 16 2 8 syntax 1 16 call until sync See CUS comment statement 1 22 syntax 1 22 compare state 1 9 compiler 5 7 CompileStil exe 5 2 composite block 5 6 file 5 8 pattern creation 5 7 image 5 6 CompositeLink application 5 8 5 9 utility 5 6 compositor 5 9 concatenation 1 4 condition statement 1 16 syntax 1 16 construct 2 1 Index 1 XTOS Pattern User Manual P N 57010495 Rev 6 e o o 6 9 o continuous loop 2 5 CUS 2 5 2 8 D DAP 2 4 DataBitCount 1 6 Dial a Pipe See DAP domain 5 6 drive state 1 8 E EDA ATPG tool 2 1 environment 3 1 tool 2 1 EESM 5 6 event sequence store memory See ESSM expec
9. diag output This option prints diagnostics messages such as the elapsed time for parsing phase and the pattern image generation parse only This option only performs the parsing phase of the compilation resulting in the generation of the pattern object file directory with only virtual pattern representation vpr file and the statistics text file CompileStats txt gen image only This option re generates the pattern image provided that the pattern object file directory already exists previously parsed namemap This option uses an XML input file to be used to map the signal pin definitions as described in the test program The file name here is the one that contains the name map XML block s name used by the test program showstats This option prints the compilation process s statistical information such as the Vector Type Select definitions and procedure call statistics verbose This option displays the compilation process details such as the signal names associated with each Event Sequence Store location nospin This option silently performs the compilation without the spinning progress indicator and the elapsed time information nolink This option overrides the default behavior of the complier so that a composite image is not generated only a loadable pattern image is generated Please refer to the XTOS Software Tools Manual P N 57510507 for details on name map XML block 5 2 Pattern Decomplier XTOS pat
10. Call load unload SI 0101010101 V in pins 1011101110010110 out pins HHLLLLHH Call load unload SI 1110001110 SO HHHLLLHHHL V in pins 1000000111010000 out pins HLXXXXLH Call load unload SO HLLLLHLLLL 3 3 ScanStructure Block The optional ScanStructure block defines the scan chain content to support scan testing The details have been described in ScanStructures Block on page 1 6 34 Scan Pattern Examples There are several styles of programing a scan pattern Each style has its own strengths and flexibility The following are few examples 34 Example Scan Pattern with MacroDefs but without ScanStructures block STIL 1 0 TRC D08 Header Title Simple Scan Pattern 1 No ScanStructure Date Sun Dec 13 22 10 00 2003 Signals sigl In sig2 In bus1 InOut bus2 InOut sig3 In sig4 In sig5 In Sig6 Out sig7 Out sig8 Out SignalGroups sil sig3 ScanIn 20 Note 1 si2 sig4 ScanIn 30 si3 sig5 ScanIn 25 sol sig6 ScanOut 20 so2 sig7 ScanOut 30 3 2 so3 sig8 ScanOut 25 Scan in sil si2 si3 Note 2 scan_out sol so2 so3 pa_pin sigl sig2 busl bus2 all pin pa pin scan in scan out Timing T1 WaveformTable W1 Period 100ns Waveforms scan in in sc 01 Ons D U scan out ou sc LHX 0ns L H X pa pin in seq 01 Ons D U
11. LH 25ns L H WaveformTable VecDef_1 lt period_0 gt Period 10ns Waveforms Abus Abus S LH 25ns L H Bbus lt Bbus D gt 01 Ons D U Cbus lt Cbus_S gt LH 25ns L H Dbus Dbus D gt 01 Ons D U WaveformTable VecDef 2 period 0 Period 10ns Waveforms Abus Abus Z gt Z Ons Z Bbus Bbus S LH 25ns L H Cbus lt Cbus Z2 Z Ons Z Dbus Dbus S LH 25ns L H WaveformTable VecDef 3 period 0 Period 10ns Waveforms Abus Abus S LH 25ns L H Bbus Bbus Z2 Z Ons Z Cbus lt Cbus S LH 25ns L H Dbus Dbus Z gt Z Ons Z The WaveformTable also can be defined as all waveform events are defined for each signal signal group In this construct the selection of WaveformTable in each vector has a set of WFC selection and the selection of WFC maps to the corresponding timing for that vector LI XTOS Pattern User Manual P N 57010495 Rev 6 6 9 6 6 9 6 6 6 6 9 6 6 6 9 6 6 06 6 9 0 6 6 6 6 6 69 6 9 6 6 6 9 6 6 9 6 6 6 6 6 6 6 6 9 6 6 6 6 6 6 6 5 6 6 6 9 6 6 ooo 6 6 6 e 6 e Timing Vec Def WaveformTable VecDef period 0 Period 10ns Waveforms Abus Abus D 01 Ons D U Abus Z gt Z Ons Z Abus S LH 25ns L H Bbus Bbus D gt 01 Ons D U Bbus Z gt Z Ons Z Bbus S LH 25ns L H
12. mixed signal applications 1 XTOS Pattern File STIL Structure The XTOS software facilitates the test pattern from data EDA STIL phase to the test target phase through a series of phase steps as follows A utility is provided to break up the STIL file into various block Signals WavefromTable and so on related files for easier file management This is a very useful tool in handling fairly large STIL files Tester targeting Aresource tag is added in the Timing block to allow timing and pattern sequence matching communication by mapping event lists to timing waveform sequences WaveformTable is the only one that needs to be modified to address the timing and pattern communication Compile a single STIL pattern file This phase compiles a source STIL file into a XTOS specific binary loadable image For example a pattern PAT1 stil file after compiling results in a PAT1 pof pattern object file directory containing the following three files vpr virtual pattern representation Hardware independent intermediate output from the STIL parser XTOS Pattern User Manual P N 57010495 Rev 6 e o o ee ee rpr runtime pattern repository Stores pattern related mapping and meta data generated by the LIG Ipi loadable pattern image Binary image suitable for direct loading on the target instrument hardware These files are for use by XTOS software only Generate a composite image for a group of pa
13. 0 6 6 6 9 6 9 6 6 9 6 9 6 6 9 6 6 6 6 6 6 6 6 9 6 6 06 6 6 6 6 6 6 9 6 9 6 6 6 9 6 6 6 6 9 6 6 9 6 6 6 6 9 6 6 6 6 e 5 Sites lt SignalRef name Abus 0 gt lt SlotPogo gt 7 0 lt SlotPogo gt lt SignalRef gt lt SignalRef name Abus 1 lt SlotPogo gt 7 4 lt SlotPogo gt lt SignalRef gt lt SignalRef name Bbus_0 gt lt SlotPogo gt 7 2 lt SlotPogo gt lt SignalRef gt lt SignalRef name Bbus_1 gt lt SlotPogo gt 7 6 lt SlotPogo gt lt SignalRef gt lt SignalRef name Cbus_0 gt lt SlotPogo gt 8 0 lt SlotPogo gt lt SignalRef gt lt SignalRef name Cbus_1 gt lt SlotPogo gt 8 4 lt SlotPogo gt lt SignalRef gt lt SignalRef name Dbus_0 gt lt SlotPogo gt 8 2 lt SlotPogo gt lt SignalRef gt lt SignalRef name Dbus_1 gt lt SlotPogo gt 8 6 lt SlotPogo gt lt SignalRef gt lt NameMaps gt lt blocks gt An example command file that compiles and then creates a composite image is CompileStil namemap Loadboard 1 xml vec_dir Pass_all_ F2 stil CompileStil namemap Loadboard 1 xml vec_dir Clock both F2 stil CompositeLink vec_dir Comp_F2 xml 513 XTOS Pattern Complier Command Line Interface Solaris The command line interface for the XTOS pattern compiler is located at XTOS release_number bin CompileStil exe Compilation of a pattern in XTOS software results in a pattern object directory with the pattern object files to be used by va
14. 5 3 XTOS Pattern Composite Linker XTOS software provides facilities to accommodate patterns that contain resources that are shared between multiple patterns These patterns contain references to and information for a number of shared resources such as main Event Sequence Store Memory ESSM Source Data Select SDS Select Sync Type SST and SUBROUTINE FE In order to be burstable execute all patterns together as one pattern every pattern in the burst has to be consistent in the references to the shared resources The CompositeLink tool takes one or more individual patterns and makes a composite image of the sharable resources for them along with a set of remap tables so that the references into those resources can be adjusted in the patterns at the pattern load time The composite image contains the composite image for each of the shared resources a list of the patterns in that composite group and the maps for each of the patterns for each resource The Composite block defines the patterns that may be chained together and the patterns that must always be run in parallel as part of an multiple time domain pattern execution The following rules are applicable to the composite 1 2 3 A given pattern may be used in multiple Composite blocks Composite blocks define the patterns that may be chained together Composite blocks define pattern domains the division of a pattern into multiple sections Composite blocks defin
15. 6 6 6 9 6 6 e 6 e 6 6 e ooo o o Timing statement MacroDefs statement PatternBurst PatternExec Pattern statement UserKeywords Amnotations In addition to the newest features introduced in the STIL 1450 3 standard a few extensions have been made to the standard to take advantage of the NPower architecture Most of these extensions make use of the UserKeyword construct provided by STIL 12 STIL Blocks The XTOS pattern file structure supports STIL standard 1450 1999 syntax for direct compile of the STIL pattern from an ATPG tool Additionally mapping of the STIL names to the Sapphire NP environment through NameMap block P1450 1 and the mapping of timing and pattern data P1450 3 are also supported Extensive usage of the STIL UserKeywords statement is also made to expand the STIL syntax to best utilize the architectural advantages of the Sapphire NP systems and mixed signal applications A description of the STIL block statements supported in the XTOS pattern structure is listed in this following sections 13 STIL Statement A STIL pattern file must start with a STIL statement The STIL statement may be either a single statement or a block statement such as STIL 1 0 single statement to indicate 1450 1999 STIL file STIL 1 0 block to include P1450 3 extension TRC D0 8 14 Header Statement An optional block after the STIL statement is the Header block The Header block must be the first block
16. 6 6 6 6 6 69 6 9 6 6 9 0 9 02 6 6 6 6 6 6 6 9 6 6 9 6 6 6 6 6 6 9 6 9 6 6 6 6 9 6 6 6 9 06 6 6 6 6 6 9 6 6 6 oo oso 2 6 Parameter Passing Parameter passing concept facilitates a mechanism to select functional data for a Signal either from the Subroutine or from the Main memory This mechanism is supported as a part of the XTOS extension to the STIL standard Parameter passing feature is supported for a per vector basis Syntax Extension UserKeywords NPTIncMain The NPTIncMain statement can be used in the subroutine to increment the main memory address that converts a regular Vector instruction into a parameter The NPTIncMain results in the increment of main address XTOS then retrieves the corresponding data from the main memory based on the user defined symbol for this alternate source The main data source to be used is defined using a UserKeyword NPTAlternativeDataSourceDef statement as follows Below is a complete example pattern showing the usage of the parameter passing concept UserKeywords NPTAlternativeDataSourceDef NPTIncMain NPTSubroutine NPTAlternativeDataSourceDef Main Procedures PROC STIL WaveformTable MY WFT Vector sigl 11 sig2 11 2 Vector sigl 00 3 NPTSubroutine MY SUBR MY SUBR WaveformTable MY WFT NPTIncMain This will set IncMain in HW opcode Vector sigl 11 sig2 t 6 using sig2 11 NPTIncMain This will set IncMain in HW opcode Vect
17. 6 9 06 6 6 6 6 6 9 6 9 6 6 6 9 6 6 9 6 6 6 6 6 6 6 9 6 6 6 6 6 6 6 5 6 6 6 9 06 6 6 9 6 6 6 6 6 6 e 6 e V all pin 10HH111HHL V all pin O1ZZ001LHX V all pin 0011000xxx Scan pat 2 Call all scans pa pin 00HH sil 10101111110000011001 si2 111110000011111000001111100000 si3 1111111111111111111111111 SOl HLHHHLXXLLXXXXLLLLHH So2 HHHHLLLLLLXXXXXXXXLLHHLLHHHXXL SO3 LLLXXXXHHHXXXLHHHLLLHHHXL V all pin 0000111LLL Scan pat 3 Call all scans pa _pin 00ZZ SOl HLHHHLXXLLXXXXLLLLHH SO2 HHHHLLLLLLXXXXXXXXLLHHLLHHHXXL SO3 LLLXXXXHHHXXXLHHHLLLHHHXL end pattern pat3 Notes 1 Procedures In this Procedures case it should have a Condition C statement to define the default state of each signal The default states will provide scan signals padding WFC and broadside signals WFC 2 Call statement The Call statement invokes scan operations by expanding the procedure all scans Notice the very first scan operation scan pat 0 only has scan input chain scan output chain is filled with X by the Compiler The very last scan operation scan pat 3 only has scan output chain scan inputs will be filled with 0 by the Compiler The signal WFC will be back to prior call statement for a non defined signal for a procedure Analog Support 4 Analog support in the Sapphire NP syste
18. Arguments CompositeFile Name of the Composite file which is to be parsed Optional Arguments help Display help message noxml No Composite XML file is needed a single pof file has to be given as input The CompositeLink application the compositor parses the input XML block containing the details on patterns to be composited and creates a composite pattern object file composite domain name cpof containing the shared data by the patterns in the composite In the multiple time domain applications multiple composite object files are generated one for each time domain 5 9 XTOS Pattern User Manual P N 57010495 Rev 6 6 9 6 oooooo o 9 06 9 06 6 9 06 6 6 6 6 6 9 6 9 6 6 9 6 6 6 6 9 6 6 6 6 6 0 6 6 6 6 6 6 6 6 6 6 6 9 6 ooo 6 6 6 6 6 6 e oe 9 e 5 Test Template for Pattern Loading The XTOS software includes a test template to facilitate the loading of multiple pattern files into the tester local memory This template loads all patterns listed in a PatternBurst The following Java code is an example of the pattern loading test template J CRCICROIR ROI RO ROO RR OOOO c Copyright 2002 2003 NPTest Inc This computer program includes Confidential Proprietary Information and is a trade secret of NPTest All use disclosure and or reproduction is prohibited unless authorized in writing by an officer of NPTest All Rights Reserved NA package com nptest sapphire test
19. by any number of alias names There are no restrictions on the types of the signals that may be grouped together However a particular signal can appear only once in a group Unlike the Signals statement multiple SignalGroups statements are allowed in a test pattern as long as these SignalGroups are assigned different names Only one global Sig nalGroups one without any name is allowed per test pattern The grouping of signal group should use single quotation marks The default order of signals in any signal group is from left to right For example group A B C then the data of group The syntax of the S SignalGroups group_ name group_name XYZ will map the assignment as A X B Y C Z ignalGroups block is signal reference expression signal reference expression DataBitCount decimal integer p Where signal_reference_expression DataBitCount Contains the signal name or signal group name with expression operators such as and STIL does not allow duplicate signal names in the same group so parenthesis may also be used as part of expression to eliminate a duplicate signal before evaluation Indicates number of bits of data for multiple bit data Below is a SignalGroups example SignalGroups Abus Bbus Cbus Dbus allPins Abus 1 Abus Or Bbus 1 Bbus 0 Cbus 1 Cbus 0 Dbus 1 Dbus 0 Abus Bbus Cbus Dbus XTOS Patter
20. mapped to opcode LDC 94 and BNZ The pseudo code is similar to Subroutine Memory MY SUBR INCMY WFT sigl 00 sig2 11 RET MY SUBR MY SUBRZ2 SLC A previous vector INC LDC 94 INC MY LOOP INC INC BNZ MY LOOP Main Memory INC INC previous vector INC INC INC CALL MY SUBR CALL MY SUBR2 INC MY W MY W MY W MY W MY W MY W MY W MY W MY W MY W MY W MY W MY W MY W MY W MY W MY W E ij n E sigi 11 sigi 00 sigl 10 sigl 00 sigl 11 sigl 10 sigl 00 sigl 11 sigl 00 sigl 00 sigl 11 sigl 00 sigl 00 sigl 01 sigl 00 sigl 00 sigl 11 sig2 11 sig2 11 sig2 10 sig2 01 sig2 01 sig2 10 sig2 01 sig2 01 sig2 11 sig2 11 sig2 11 sig2 11 sig2 00 sig2 10 sig2 00 sig2 11 sig2 11 SLC attached to Expand lst Loop Call attached on PROC s PROC s TIL 1 TIL 2 2 3 XTOS Pattern User Manual P N 57010495 Rev 6 e o o 6 9 ooo 6 6 6 6 9 06 9 90 6 9 6 6 6 6 6 ooo 6 9 6 6 96 6 9 6 6 9 6 6 6 6 6 6 9 6 6 6 9 6 6 6 02 o 2 2 Syncand Trigger Support Pattern files do not need to know the complete definition of the triggers they only need to know about the trigger names and types of the trigger generate or waitfor A pattern file contains or includes a STIL trigger
21. name PatterbBurst pat burst name Procedures The STIL Procedures block is an optional block A single unnamed Procedures block may exist and all the procedures are defined in the Procedures block XTOS s subroutine capability is also supported through the STIL s procedure with the NPTSubroutine UserKeyword This UserKeyword identifies it is a subroutine instead of a regular STIL procedure The syntax of the Procedures block is Procedures optional Procedure block name NPTSubroutine procedure name procedure name pattern statement p Each procedure contains any combination of the STIL pattern statements such as Vector Condition and WaveformTable reference In addition to these regular statements a procedure may also contain the Shift statement for scan vector Procedure is invoked through a Call statement When a procedure is called no information about the current signal state is transferred into that procedure A WFC for all signals used in the procedure must be specified and a WaveformTable reference must also be defined by the first Vector in the procedure When a procedure ends the context of the last statement of the procedure will not transfer back to its caller A procedure does not return any change back to the calling environment no matter how the signals may have changed during the procedure The Vector after the Call statement will inherit the states from the Vector prior to the Call statement An
22. o Vector sigl 11 Vector sigl 00 In addition to the vector statement usage example shown above XTOS software also supports a Call statement in a NPTSubroutine This feature is called a Call Until Sync CUS Any Call instruction preceded by a NPTWaitTrigger is translated to a CUS A Call statement in the subroutine that does not meet this criterion of being preceded by a NPTWaitTrigger is translated to a regular Call or is expanded into in line vectors if itis STIL Procedure Call Example Match Call UserKeywords NPTTriggerDef NPTWaitTrigger NPTSubroutine NPTOpcode NPTLatencyPipe NPTMatchDef NPTTriggerDef MatchFound NPTMatchDef Sequence PFP Signal name Name3 NPTLatencyPipeDef 400 Procedure NPTSubroutine normal subr normal subr W Seq1 v v v Pattern CUS test v NPTWaitTrigger matchfound V CUS vector Call normal_subr v lt lt lt 2 5 Keep Alive Vector XTOS software supports the KeepAlive vector statement to allow the continuation of clock signals to keep the Device Under Test DUT in an pre defined active state This functionality is supported by a STIL extension syntax that identifies the KeepAlive vector in the specific pattern Note that only one Vector statement is allowed to be a KeepAlive vector Syntax Extension UserKeywords NPTKeepAliveVector 2 8 2 Hardware Support 6 6 9 6 6 9 6 9 06 6 6 6
23. v all_pin 01HH100HHL V all pin 11LHO11LXH Scan pat 1 Macro all scans sil 10101111110000011001 si2 111110000011111000001111100000 si3 1111111111111111111111111 SOl HLHHHLXXLLXXXXLLLLHH SO2 HHHHLLLLLLXXXXXXXXLLHHLLHHHXXL SO3 LLLXXXXHHHXXXLHHHLLLHHHXL v all_pin 10HH111HHL V all pin O1ZZ001LHX V all pin 0011000xxx Scan pat 2 Macro all scans si1 10101111110000011001 si2 111110000011111000001111100000 si3 1111111111111111111111111 SOl HLHHHLXXLLXXXXLLLLHH SO2 HHHHLLLLLLXXXXXXXXLLHHLLHHHXXL SO3 LLLXXXXHHHXXXLHHHLLLHHHXL v all pin 0000111LLL Scan pat 3 Macro all scans SOl HLHHHLXXLLXXXXLLLLHH SO2 HHHHLLLLLLXXXXXXXXLLHHLLHHHXXL SO3 LLLXXXXHHHXXXLHHHLLLHHHXL end pattern pat2 3 7 XTOS Pattern User Manual P N 57010495 Rev 6 e o o 6 9 6 9 6 6 oo 6 69 6 9 6 6 6 9 6 6 9 6 6 6 6 6 6 9 6 9 6 6 6 6 6 6 0 0008000000000m0008000 00000000000u0 08 Notes 1 SignalGroups Some of signals are declared as scan input port with keyword Scanin and some signals are declared as scan output port with keyword ScanOut The declaration can be part of Signals block or SignalGroups block No ScanLength is declared here because it is declared in the ScanStructure 2 ScanStructures This structure holds the definition of scan shift chain It defines the length of each scan shift chain ScanLength Based on this information the comp
24. z seq Z Ons Z ou seq LH Ons L H end WaveformTable W1 end Timing T1 g MacroDefs all_scans W W1 Note 4 C sil 0 si2 0 si3 0 sol X so2 X so3 X pa_pin Shift V scan_in scan_out PatternBurst burst1 PatList pat1 end PatternBurst hello tester burst PatternExec Timing T1 PatternBurst burstl end PatternExec Pattern pat W W1 V all pin 00ZZ000xxx scan_pat_0 Macro all scans pa pin 10ZZ si1 10101111110000011001 si2 111110000011111000001111100000 813211111111111111171111111111 V all pin 01HH100HHL V all pin 11LHO11LXH Scan pat 1 Macro all scans pa pin 10ZZ si1 10101111110000011001 Note 3 Note 5 Note 6 3 Scan Support 6 6 9 6 6 9 6 9 06 6 9 6 6 6 6 6 6 6 9 6 9 6 6 0 9 6 6 9 6 6 lt o o 9 6 oo 6 5 6 6 coco o 6 6 6 9 6 6 6 9 06 6 9 6 6 6 6 9 6 6 e 5 e XTOS Pattern User Manual P N 57010495 Rev 6 6 9 6 6 9 6 6 6 6 6 6 0 9 6 6 9 6 6 6 6 6 6 6 9 6 6 6 6 9 6 6 5 6 6 6 9 6 6 6 9 6 6 6 69 6 6 e 6 6 si2 111110000011111000001111100000 si3 1111111111111111111111111 SOl HLHHHLXXLLXXXXLLLLHH SO2 HHHHLLLLLLXXXXXXXXLLHHLLHHHXXL SO3 LLLXXXXHHHXXXLHHHLLLHHHXL v all_pin 10HH111HHL V all pin 01ZZ001LHx V all pin 0011000xxx
25. 14 1 13 1 WaveformTable Reference 0 00 ccc ccc cence eee ener keen e ees 1 15 1 13 2 Vector Statement 2 cased oak is 1 16 1 13 3 Condition Statement 0 nr 1 16 1 13 4 Call Statement 25 22 is a 1 16 113 5 Macro Statement eoe pae e De Ern diem Gin ette e T E NONE UR OR etes 1 17 1 13 6 Loop Statement 5 eco isis ENEE a sql e Gee nea Ladd eve ed de 1 18 1 13 7 MatchLoop Statement cient ra od HO e eet Wee eles AN 1 18 114 Pattern Examples sesos p Re EES Re as C ECRRENSET e anos R EES 1 19 1141 Example l a P 1 19 1 14 2 Emploi ra 1 20 XTOS Pattern User Manual P N 57010495 Rev 6 ee ee 115 Additional STIL Statements 1 22 1 15 1 Annotations ey sees REEL a A bi a 1 22 1 15 2 COMMENTS M sss P OM 1 22 1 15 3 ERI CQuulo EM 1 22 115 4 Label Staten bas 1 22 Chapter 2 Hardware Support ew 6 A VEER NEEN ENEE RENE as e RE RR E CE EE ans EEN ER 2 1 21 Subroutine Memory Support 2 1 2 2 Sync and Trigger Support yes cece cece e e HH Hh e He eee 2 4 2 3 Continuous Call Application css sags seneti neari Ie eee 2 5 24 ster Mettet c mET 2 7 2 5 Keep Alive Vector 3 det donar ii o a sass 2 8 2 6 Parameter Passing voii a uk P oa 2 9 2 7 DC Channel Pattern Application 2 10 2 7 1 Usage Model oo ias ao Vade 2 10 Chapter 3 Scan Support 6 444505 KEEN REENEN EN REN EE REENEN EEN 3 1 31 Scanln and ScanOut Declaration oooococcccccccccnccncnncnnc rn me een 3 1 3
26. 2 Shift Statement merida ii ee Tc dien odds eb br ae 3 1 3 3 ScanStr ct re Block e d keng tiena eR NEE REE E ERI a TE EN ie 3 2 3 4 Scan Pattern Examples tenete ts a dla add 3 2 3 4 1 Example liada didas 3 2 3 4 2 EXAMPLE iii A teen A cet 3 5 3 4 3 EXaMple3 awe d tached ar ia eee 3 8 Chapter 4 Analog Support Ad a AER Ee Ke Ee ER ANA KEE RENE REENEN E 4 1 41 Digitized Analog Pattern Example oooocccccccccccccccncnccn cece me ees 4 1 Chapter 5 XTOS Pattern Compiler and Composite Linker oooooooooommommo 5 1 51 Pattern Complier acaricio rata da PE EAE 5 1 511 XTOS Pattern Complier Command Line Interface Windows 2000 5 1 5 1 2 NameMap Support in XTOS Pattern Compiler 00 cece eee cee cece eee 5 2 5 13 XTOS Pattern Complier Command Line Interface Solaris 5 3 5 2 Pattern Decoinplier ocur NEEN dE sade ORAE dere a e de 5 4 5 2 1 XTOS Pattern Decomplier Command Line Interface Windows 2000 5 5 5 2 2 XTOS Pattern Decomplier Command Line Interface Solaris 0 0008 5 5 5 3 XTOS Pattern Composite Linker sisse me hee 5 6 5 3 1 Compositing Patten sss esso ENER ee et eme e esed kr eR exce e eee 5 8 5 3 2 XTOS Pattern CompositeLink Command Line Interface Windows 2000 5 9 5 3 3 XTOS Pattern CompositeLink Command Line Interface Solaris Lie 5 9 Chapter 6 Test Template for Pattern Loading o ooo
27. 6 e o o ee ee Macro Macro A one 1 two H v one 0 Macro Macro A one 0 two L 113 6 Loop Statement STIL supports a repeating construct with Loop statement A Loop statement maps a single vector into one or more RPT sequencer opcodes RPT operation or multiple Vector statements into a loop BNZ operation XTOS supports RPT in both Main and Subroutine memory but only BNZ loop operation in the Subroutine memory The multiple vector Loop construct of a STIL pattern is expanded to straight line vectors in the Main pattern section Pattern compiler also takes care of the loop count if the value is beyond the maximum count value that the hardware supports In other words the compiler may break a single Loop statement into multiple RPT vectors in order to to accommodate the pattern requirements given the test system limits Pattern Compiler also takes care of the hardware restriction that does not allow back to back RPT opcode in two consecutive vectors Pattern compiler ensures there is an INC opcode inserted between the two RPT opcode vectors and keeps the total test count identical to the source code cycle count The syntax of the Loop statement is Loop loop count vector_statement Below is an example of a loop in Match memory Pattern XXY W default waveformtable V all signals 0101000111XXXXX11001 Loop 10 v Simple Repeat 10 times Loop 33 W
28. AnalogCapture to define the corresponding signal to get data from an analog instrument Note that a given sequence can only be marked as either source or capture and not both The following is an example of the analog pattern UserKeywords NPTAnalogSource NPTAnalogCapture Timing MY TIMING WaveformTable one PERIOD 1 Period 500ns Waveforms sigl SEQ Dr A NPTAnalogSource Ons D U 4 1 XTOS Pattern User Manual P N 57010495 Rev 6 6 ooo 6 9 6 9 6 6 9 6 6 6 6 9 6 6 6 6 6 06 6 6 6 6 6 6 6 6 6 6 6 9 6 6 9 6 6 6 6 1 2 0 sigl sig2 sig2 sig3 sig3 sig4 A A AS c sig4 SEQ Dr 01 Ons D U SEQ Cmp gt C NPTAnalogCapture Ons L H SEQ Cmp gt LH Ons L H SEQ Dr1 gt K NPTAnalogSource 10ns D U SEQ Dr2 01 50ns D U SEQ Cmpl gt J NPTAnalogCapture 10ns L H SEQ Cmp2 LH 80ns L H end WaveformTable one Pattern TRY WaveformTable MY WFT Vector Vector Vector Vector Vector Vector Vector Vector Vector Vector Vector sigl 00 sigl A sigl 11 sigl A sigl 00 sig2 C sigl 11 sigl A sigl 00 sig2 C sig2 HH Sig2 HH sig3 11 sig4 HH sig2 LH sig3 K sig3 10 sig2 C sig3 K sig4 J sig2 LL sig3 00 sig4 J sig2 HL sig4 LL sig3 K sig2 LL sig3 00 sig4 J sig3 11 sig4 LL This pattern
29. FC in that vector Prior to the very first Vector statement there must be the WaveformTable reference statement to specify the WaveformTable If a Vector statement has empty content it implies that every signal keeps the same WFC as the previous assignment The possible syntax of the Vector statement are Vector signal assignment v signal assignment Where signal assignment has syntax as signal ref WFC or WFC list 113 3 Condition Statement The Condition statement does not generate actual test events It only establishes new waveform assignment to signals that may be applied to the subsequent Vector statements until a change in WFC occurs The possible syntax of the Condition statement are Condition signal assignment c signal assignment where signal assignment has syntax as signal ref WFC or WFC list Here is a Condition statement example Pattern XXY W default waveformtable C all signals 0101000111XXXXX11001 vi first vector value defined in C vi first vector value defined in C V Abus HH 113 4 Call Statement A Procedure is invoked in the pattern section through the Call statement STIL s Procedure supports parameter passing that the Call statement can pass the value assignment to the corresponding procedure The Call statement does not generate a physical test cycle and all the signal assignments are used for parameter passing The NPTest S
30. I scan pat 2 Macro all scans pa_pin 10LL si1 10101111110000011001 si2 111110000011111000001111100000 si3 1111111111111111111111111 SOl HLHHHLXXLLXXXXLLLLHH SO2 HHHHLLLLLLXXXXXXXXLLHHLLHHHXXL SO3 LLLXXXXHHHXXXLHHHLLLHHHXL V all pin 0000111 Scan pat 3 Macro all scans pa pin 10ZZ SOl HLHHHLXXLLXXXXLLLLHH SO2 HHHHLLLLLLXXXXXXXXLLHHLLHHHXXL SO3 LLLXXXXHHHXXXLHHHLLLHHHXL end pattern pati Notes 1 SignalGroups Some of signals are declared as scan input port with keyword Scanln and some signals are declared as scan output port with keyword ScanOut The declaration can be part of Signals block or SignalGroups block The second parameter defines the length of each scan chain associated with the scan port It should have matched length for the corresponding scan inputs and outputs for example sil and sot 2 SignalGroup scan_in scan_out Scan shift chain has its own input and output port and its data is always standalone lt may have scan input and output group for the convenience of defining a scan Procedure or Macro The signal group can also be used in WaveformTable but not in the data assignment 3 WaveformTable The scan input signals are always using WFC 0 to represent drive low state and 1 to represent drive high state It should be combined as 01 event list to imply F1 mode The scan output signals sho
31. STIL supports two forms of comment information as part of STIL statements Annotations Comments 1151 Annotations Ann is the STIL keyword followed by special identifies to enclose the annotation body The syntax of the Annotation statement is Ann text string for annotation Annotations are maintained through the XTOS system and preserved as comments Generally to maintain association of an Ann statement as a part of STIL the Ann statement should be placed inside a block construct 115 2 Comments STIL supports the second form of comment information with Comment statements The syntax of the Comment statement is comment text string until end of line comment text string in between Comment statements are not preserved in XTOS These statement are converted to Ann statements which can be preserved in XTOS This is a user controlled option 115 3 UserKeywords STIL supports syntax extensions through the UserKeywords statement XTOS uses the UserKeywords to define various NPTxxxx UserKeywords to support Sapphire NP hardware capabilities and mixed signal applications All XTOS UserKeywords have a NPT prefix 115 4 Label Statement Any Pattern statement can have an optional associated label to identify start stop vectors or a specific pattern location scan pattern set Pattern label Labels are scoped to its Pattern block and to individual Procedure bodies Labels are required to be unique Any l
32. XTOS Pattern User Manual nptest Copyright Notice This document and all information contained herein is proprietary to NPTest and protected by copyright or other laws of the United States and other countries No part of this publication may be distributed to another party reproduced or copied without the express permission of NPTest Additional copies of this and any other publication are available at any NPTest sales office Accelerated Vector Mode AVM APTEON ASAP BatchProbe DeFT IDS IDS OptiFIB ISOCHRONOUS FABRIC INTERFACE ITS IVS Keep Alive NanoBlade NPower NxGenConnect NxGenSupport OptiCA SABER Sapphire NP Sequencer Per Pin TimeStamper TrueEdge Ultra Low Voltage Voice Grade XTOS and Yosemite are trademarks or registered trademarks of NPTest The following are trademarks or registered trademarks of their respective companies or organizations UNIX X Open Company Ltd Sun Microsystems Sun Workstation OpenWindows SunOS NFS Sun 4 SPARC SPARCstation Java Solaris Sun Microsystems Ethernet Xerox Corporation Microsoft Windows Windows NT Microsoft Corporation IEEE Institute of Electrical and Electronics Engineers Inc All other brand or product names are trademarks or registered trademarks of their respective companies or organizations A reader comment form is provided at the end of this publication Suggestions and comments are appreciated In no event shall NPTest be liable for any
33. abel within Macro is ignored T22 Hardware Support 2 The XTOS pattern syntax also supports Sapphire NP s hardware capabilities and mixed signal applications The following sections cover these extensions 21 Subroutine Memory Support Sapphire NP test system has subroutine memory as one of the data sources for pattern data STIL has a Procedure construct in the 1450 1999 standard however not all the procedures can be mapped into subroutine usage due to Subroutine is a limited resource in the test system STIL s procedure macro is a software construct that may be used extensively For example scan vectors in STIL are 100 in procedure macro construct due to the nature of scan load unload capture vectors Sapphire NP s subroutine memory can not handle parameter passing no equivalent PARAM opcode available Sapphire NP subroutine memory size is 4k To preserve the capability of digital STIL patterns especially scan patterns to be processed by EDA ATPG tools for failure analysis XTOS keeps the Subroutine extension syntax as that of a STIL procedure statement A STIL UserKeyword is defined to support Sapphire NP s subroutine memory However the STIL procedure statement is used as much as possible as the base of Subroutine syntax If the Sapphire NP subroutine capability is not used the default behavior for the procedure and macro statements is inline with the pattern statements Additionally a UserKeyword is defined to su
34. after the STIL statement and before any other STIL blocks in the file Header blocks contains file oriented information The defined statements of the Header block are Header XTOS Pattern User Manual P N 57010495 Rev 6 e o o 6 9 6 6 09 1 0 n 0000000080000 0o 6 9 6 6 6 9 6 6 6 6 6 6 6 s o 6 56 Title title string Date date string Title of the file Source source string Date of the file being generated History How is this file generated 15 Include Statement The STIL Include statement may appear any place a STIL statement block may be found It is recommended to always quote filenames in the Include statement Generally a filename contains at least a period character which has other semantic meanings in STIL concatenation It is recommended that top level STIL files are named with the suffix stil while all the include files are named with other suffix such as inc The include file path is supported by both a relative file path and a absolute file path The IfNeed option is ignored in XTOS environment The pattern compiler includes the Include file regardless of the IfNeed option The Include file must start with the STIL statement as the first statement in the file 16 Signals Block Only one Signals block is allowed for one STIL pattern file The Signals block will not have a name associated to it This block defines the Signals used in the tes
35. ain SCH 1 37 ScanLength 30 ScanIn si2 ScanOut so2 ScanInversion 0 ScanCells CH 2 1 CH 2 2 CH 2 3 CH 2 4 CH 2 57 CH 2 6 T CH 2 7 CH 2 8 CH 2 9 CH 210 CH 2 11 CH 2 12 CH 2 13 CH 2 14 CH 2 15 CH 2 16 CH 2 17 CH 2 18T CH 2 19 CH 2 20 CH 2 2 UCH 2 22 CH 2 23T MCH 224r CH 2 25 UCH 2 26 CH 2 27 CH 2 28 CH 2 29 CH 2 30 5 ScanChain SCH 1 16 ScanLength 25 ScanIn si3 ScanOut so3 ScanInversion 0 ScanCells CH 3 1 CH 3 2 CH 3 3 CH 3 4 CH 3 5 T CH 3 G CHI 3 7 mCH 3 8 CH 3 9m U CH 3 10 CH 3 11 CH 3 12 CH 3 13 CH 3 14 MOH SLIGT CH 3 16 MCH 3 L7 CH 3 198 CH 3 19 CH 3 20 CH 3 21 CH BRAT CH 3 23 CH 3 24 CH 3 25 gt MacroDefs all scans W W1 Note 3 C sil 0 si2 0 si3 0 sol X so2 X so3 X pa pin 10ZZ Shift V scan_in r3 d scan_out r3 Note 4 PatternBurst burst1 3 6 3 Scan Support 6 6 6 6 9 6 9 06 6 6 6 6 6 6 6 6 6 6 9 6 6 9 0 9 6 6 9 6 6 6 6 6 6 6 6 9 6 6 9 6 6 6 6 5 6 6 9 6 9 6 6 6 6 9 6 6 6 06 6 6 6 6 6 PatList pat2 end PatternBurst hello tester burst PatternExec Timing T1 PatternBurst burstl end PatternExec Pattern pat2 W W1 V all pin 00ZZ000xxx Scan pat 0 Macro all scans si1 10101111110000011001 si2 111110000011111000001111100000 13 1111111111111111111111111
36. definition that simply lists the trigger names along with their optional exit conditions The latency pipe is also required when sync triggers across different instruments are used It provides enough latency to allow instrument to instrument synchronization A latency pipe definition must be supplied before any type of trigger is used This latency pipe definition is applicable to all types of triggers and is the integer number of the pipeline The minimum length of the pipeline for the NPTLatencyPipeDef is 50 confirmed sync see Table 2 1 period value For example the current test program utilizing five instruments with a test period of 5 ns must have a minimum latency pipeline length of 149 50 495 5 Table 2 1 Maximum Total Latency Instruments Confirmed Sync ns 5 495 10 645 15 795 20 945 25 1095 30 1245 35 1395 40 1545 50 1845 60 2145 70 2445 80 2745 In multiple time domain applications different timing domains can be exited on the wait loop by matching with the ratio by using the exit condition of onRatio For example in a case where there are two time domains and the patterns Pat A and Pat B have a 2 3 ratio between these two domains the user may desire to exit on the boundary where the ratios match Pat A always exits on an even number of cycles and Pat B can only exit on every third cycle to ensure these two domains are keeping the 2 to 3 ratio The user can also contro
37. e 2 Scan pattern with MacroDefs and ScanStructures blocks STIL 1 0 TRC D08 Header Title Simple Scan Pattern 2 with ScanStructure Date Sun Dec 13 22 00 00 2003 Signals sigl In sig2 In busl InOut bus2 InOut sig3 In sig4 In sigs In Sig6 Out sig7 Out sig8 Out SignalGroups sil sig3 ScanIn Note 1 si2 sig4 ScanIn si3 sig5 ScanIn sol sig6 ScanOut so2 sig7 ScanOut so3 sig8 ScanOut scan_in sil si2 si3 Scan out sol so2 so3 pa_pin sigl sig2 busl bus2 all pin pa pin scan in scan out Timing T1 WaveformTable W1 Period 100ns Waveforms onsen D U Ons L H X Ons D U Ons Z Ons L H scan in in sc 01 scan out ou sc LHX pa pin in seq 01 z seq Z c ou seq LH 3 5 XTOS Pattern User Manual P N 57010495 Rev 6 6 oo 6 9 6 6 6 6 9 6 6 6 6 9 6 6 6 6 6 0 9 6 6 o 2 0o o 2 ooo 0202 o 2 o 02 o o 12 o ooooc oo occ end WaveformTable W1 end Timing T1 g ScanStructures Note 2 ScanChain SCH 1 33 ScanLength 20 ScanIn sil ScanOut sol ScanInversion 0 ScanCells CH 1 1 CH 1 2 CH 1 3 CH 1 4 CH 1 5 CH l G CH 1 7 CH 1 8 CH 1 9 CH 1 109 CEL 11 CH 1 12 CH 1 13 CH 1 14 5CE 1 15 CH l 16 CH l1 17 CH 1 18 CH 1 19 CH 1 20 ScanCh
38. e compiler does not generate any content from it The BreakPoint statement is handled as a Null statement lts presence in the MatchLoop statement is required to comply with the STIL standard only The STIL syntax allows Vector statement s inside the BreakPoint statement but Sapphire NP s digital instruments do not support any extra vectors in the Match equivalent functionality The presence of any Vector statement s is treated as an error in XTOS The XTOS compiler s syntax extension to STIL MatchLoop and an example are shown below UserKeywords NPTMatchDef NPTMatchDef Sequence pass fail sequence Signal lt signal_name gt Where pass fail sequence is up to 32 P pass or F fail character string For example PFPFP means 5 match sequence with toggle Pass and Fail signal name is the signal reference to match on Example Match Loop UserKeywords NPTTriggerDef NPTMatchDef NPTLatencyPipeDef NPTWaitTrigger NPTTriggerDef MatchFound NPTMatchDef Sequence P Signal name Namel Name2 NPTLatencyPipeDef 550 Pattern TRY WaveformTable MY WFT Vector sigl 00 sig2 11 NPTWaitTrigger MatchFound Vector sig1 00 MatchLoop 3000 Vector sigl 01 BreakPoint 2 7 XTOS Pattern User Manual P N 57010495 Rev 6 e o o 6 0 6 9 6 6 9 6 6 9 6 9 6 6 6 9 6 6 9 6 6 6 6 6 6 9 6 9 6 6 6 6 6 6 6 6 6 9 0 9 6 6 6 6 9 6 6 6 6 6 6 6 6 9 6 6 6 e e e e
39. e the sub patterns in each pattern sections 5 PatternLists within PatternBurst blocks may list either pattern name or sub pattern names of the primary section the very first domain in the case of multiple time domain patterns PatternLists within PattenBurst blocks always refers to one and only one Composite block Identical PatternLists may be declared in multiple PatternBursts each referring to a different Composite block The following example illustrates a multiple time domain group of patterns consisting of three patterns Each pattern has three sections Each section exists in a different domain A domain is associated with unique tester resources these resources are defined in the pattern files The resources in turn determine the timing domain that the patterns are executed 5 XTOS Pattern Compiler and Composite Linker 6 9 6 6 9 6 9 06 6 0 a oooooo o 0 6 06 6 9 6 6 6 6 6 6 6 6 9 oo oo 6 6 6 o oo o ccoo oo 6 6 6 6 9 6 6 6 Below is a Composite block layout example Pattern Domainl FullTime Section Multiply PatF1 Divide PatF2 Boolean PatF3 Domain2 HalfTime Section PatM1 PatM2 PatM3 Domain3 QuarterTime Sections PatQ1 PatQ2 PatQ3 In the above example Multiply Divide and Boolean are three user names referring to the three sections of Pattern Usage of user names is optional Patterns PatF1 PatM1 and PatQ1 belong to the user name Multiply Pattern
40. ed Pattern invoke Load System out println Loaded pattern Pattern getS Name pattern loaded true else if PatternBurst null amp amp pattern burst loaded PatternBurst invoke Load System out println Loaded PatternBurst db PatternBurst getS Name pattern burst loaded true else if all_pattern_bursts_loaded Find all the PatternBurst blocks and load them BlockManager block manager cap getBlockManager PatternBurst String pattern burst block names block manager getSarray Blocks 0 0 if pattern burst block names length 0 testprogram System out println No PatternBurst blocks found in for int i 0 i pattern burst block names length i 6 2 6 Test Template for Pattern Loading 6 9 6 6 9 6 9 06 6 6 6 6 6 6 6 6 9 6 ooooo 6 6 6 6 6 6 6 6 9 6 6 9 6 6 6 6 6 6 9 6 9 06 6 6 6 9 6 6 6 6 6 6 6 6 6 9 6 6 6 6 e 5 GenericBlock pattern burst block manager getBlock pattern burst block names i pattern burst invoke Load System out println Loaded PatternBurst pattern burst block names il all pattern bursts loaded true TestStatusArray testStatusArray new TestStatusArray return testStatusArray get 6 3 XTOS Pattern User Manual P N 57010495 Rev 6 6 9 6 oooooo o 9 06 9 06 6 9 06 6 6 6 6 6 9 6 9 6 6 9 6 6 6 6 9 6 6 6
41. ed using the XTOS pattern compiler CompileStil By default the pattern compiler creates a composite image for the single pattern being complied This is overridden with a nolink option 5 7 XTOS Pattern User Manual P N 57010495 Rev 6 e o o 6 9 6 9 6 6 9 6 6 9 6 9 6 6 6 9 6 6 9 6 6 6 6 6 6 9 6 9 6 6 6 6 6 6 6 6 6 9 0 9 6 6 6 6 9 6 6 6 6 6 6 6 0 o o Secondly the application CompositeLink XTOS release_numbern bin CompositeLink exe should be executed with a composite XML block as an input argument Please refer to the Command Line Interface see XTOS Pattern Composite Linker on page 5 6 section for details on invoking the CompositeLink application the compositer The compositer processes all the patterns within a composite block and creates a composite image 5 3 Compositing Patterns An example composite file Comp F2 xml is shown below In this example the composite linker creates a composite image containing the shared resource for patterns Pass all F2 stil and Clock both F2 stil file lt xml version 1 0 encoding ISO 8859 1 gt blocks Composite name Comp F2 lt DomainList gt lt Domain name Primary gt lt Stilfile gt Pass all F2 lt Stilfile gt lt Stilfile gt Clock both F2 lt Stilfile gt lt Domain gt lt DomainList gt lt Composite gt lt blocks gt For the example above the CompositeLink application creates a directory named Comp_F2 cdir ins
42. erence 1 14 1 15 STIL 1 13 subroutine support 2 1 PatternBurst block 1 12 1 18 5 6 patterns 6 1 syntax 1 12 PatternExec block 1 12 1 18 syntax 1 12 PatternLists 5 6 procedure block 1 12 1 13 construct 2 1 statement 2 1 syntax 1 13 Q quotation marks 1 4 R remap tables 5 6 repeat until match statement 2 7 resource tag period_name 1 8 sequence_name 1 8 RPT operation 1 17 RPTM 2 7 S scan chain 1 6 1 7 input 1 6 output 1 6 pattern 3 1 vector 2 1 ScanChain block 1 7 ScanLength statement 1 7 ScanOutLength statement 1 7 ScanStructure block 1 6 3 2 syntax 1 6 SDS 5 6 sections 5 6 select sync type See SST shared resources 5 6 shift block 3 1 statement 3 1 signal declaration 3 1 name 1 4 state 1 13 type 1 4 signal state 1 14 SignalGroups block 1 5 1 18 declaration 3 1 example 1 5 global 1 5 syntax 1 5 signals block 1 4 1 18 syntax 1 4 source data select See SDS source syntax ix SST 5 6 standard test interface language See STIL Index 3 XTOS Pattern User Manual P N 57010495 Rev 6 ec c cc 6 9 6 6 9 6 9 6 6 eee 9 6 9 6 6 9 06 6 9 6 9 06 6 9 6 6 9 6 6 9 6 ee state compare 1 9 drive 1 8 expect 1 9 indeterminate 1 9 signal 1 13 1 14 statement annotation 1 21 BreakPoint 1 15 2 7 call 1 13 1 14 1 16 2 8 comment 1 22 condition 1 16 header 1 3 include 1 4 KeepAlive vector 2 8 label 1 22 loop 1 17 macro 1 14 1 17 2 1 MatchLoop 1 18 2 7 NPTIncMain 2 9 null 2 7
43. eriod 40us The following are the pre defined names for the ten timing sequences DCC Nop NOP DCC D1 Drive High at beginning of cycle DCC DO Drive Low at beginning of cycle DCC DZ Drive Z at beginning of cycle DCC T4H Strobe High at end of cycle while Terminate High at beginning of cycle DCC T1L Strobe High at end of cycle while Terminate Low at beginning of cycle DCC T1Z Strobe High at end of cycle while Terminate Z at beginning of cycle DCC TOH Strobe Low at end of cycle while Terminate High at beginning of cycle DCC TOL Strobe Low at end of cycle while Terminate Low at beginning of cycle DCC TOZ Strobe Low at end of cycle while Terminate Z at beginning of cycle An example of the Timing Block for the DCC pattern is shown below only shows user programming section Timing name norm timing SignalGroupsRef name sig groups1 gt TimingDomain name DCChannelDomain gt Period name Period_lus gt lt Valuel000e 9 lt Value gt lt Period gt lt SignalRef name SIG_1 gt lt SignalRef gt lt SignalRef name SIG_2 gt lt SignalRef gt lt TimingDomain gt lt Timing gt The DC Channel pattern acts as one of multi timing domain patterns The WaveformTable uses these pre defined period and sequence names with user defined WFC to construct the mapping The pattern section uses the same source syntax defined in this document The user has the flexibility to use any WFC for these pre defined timing sequence
44. ger is translated to CUS otherwise it is translated to a regular Call if it is Subroutine Call or is expanded to straight line if it is STIL Procedure Call UserKeywords NPTSubroutine NPTTriggerDef NPTLatencyPipeDef NPTWaitTrigger NPTTriggerDef CPUResumePattern NPTLatencyPipeDef 400 Procedure NPTSubroutine subrX subrx W Segl V sigl 00 sig2 11 V sigl 10 sig2 01 v Pattern CUS test W Seq1 sigl 00 sig2 11 sigl 11 sigl 01 sig2 10 sigl 11 NPTWaitTrigger CPUResumePattern V sig1 00 CUS Vector Call subrX V sigl 00 V sigl 11 V V V V 2 6 2 Hardware Support 6 9 o oooo 6 6 6 o oooo oo 6 6 6 6 6 6 6 6 oo oo o oo e V sigl 00 V 2 4 Match Vector To support a feature similar to the RPTM lt count gt Repeat the current vector until match condition is found or until a number of lt count gt is reached XTOS uses the STIL statement MatchLoop and an additional extension to specify the Match sequence and pipeline length The XTOS equivalent for the Repeat Until Match statement is called Wait Until Sync WUS The STIL equivalent statement for the Repeat statement is shown below MatchLoop lt count Infinite gt Vector BreakPoint Vector STIL syntax requires the BreakPoint statement as the exit condition for a match vector In XTOS the BreakPoint statement is a do nothing statement and th
45. gh Z Disable the driver Drive to tri state H Compare high Compare low X Do not compare 194 Merge Waveforms STIL supports a single WFC to map to a single event in a event list such as Abus 0 Ons D Abus 1 Ons U STIL also supports merge waveforms that map two or more WFCs to multiple event states in a event list such as Abus 01 Ons D U Bbus LH Ons L H Cpin aA Ons D U 1 10 1 Pattern File STIL Description 6 6 9 6 6 9 6 9 06 6 6 6 e 6 012 020 02x0 o oo 6 6 6 6 9 6 6 96 6 6 6 6 5 6 6 9 6 9 6 6 6 9 6 6 6 6 6 6 6 6 6 6 9 6 6 6 6 e 5 The XTOS pattern compiler takes the merge waveform and implies F data and FM mode operation The combined D U or L H event state implies that the current waveform timing sequence has F data The combined L H X L X or H X event state implies that the corresponding signal has FM mode such as Bbus LHX Ons L H X The WaveformTable can be defined as a single waveform per signal signal group In this construct the selection of WaveformTable in each vector has a fixed WFC selection and fixed timing sequence to map with the vector Timing Vec Def WaveformTable VecDef_0 period 0 Period 10ns Waveforms Abus Abus D 01 Ons D U Bbus Bbus S LH 25ns L H Cbus lt Cbus D 01 Ons D U Dbus Dbus S
46. gnalGroups of Abus and F2 mode for Bbus SignalGroups Abus Abus 1 Abus oi DataBitCount 8 Bbus Bus 1 Bbus_0 DataBitCount 4 Cbus Cbus 1 Cbus_0 Dbus Dbus 1 Dbus 0 allPins Abus Bbus Cbus Dbus The D 4032 instrument supports up to F4 data rate 18 ScanStructures Block This block is an optional block and describes the interconnection of scan chain information in the DUT Details related to the length of the scan chain definitions of the scan input and output signal associated with the chain and the definition of the internal scan cells are contained in this block 1 Pattern File STIL Description 9 9 6 9 6 6 9 6 6 6 6 9 6 6 6 9 6 6 6 6 6 6 6 6 9 6 9 06 6 6 6 9 6 6 6 6 9 6 6 9 6 6 6 6 6 6 6 e 6 0 zs eeeeseeee The syntax of the ScanStructures block is ScanStructures scan name ScanChain chain name ScanLength decimal integer ScanOutLength decimal integer ScanCells cell name list ScanIn signal name ScanOut signal name ScanMasterClock signal name list ScanSlaveClock signal name list ScanInversion 0 1 ps 181 Scan Data Alignment Scan Padding When a scan pattern has more than one scan chain and the scan chains are not all the same length then the XTOS pattern compiler will provide padding to make all scan chains equal length The scan length of each scan chain is specified in the ScanLength and ScanOutLength sta
47. guments lt STILFileName gt STIL file to compile Optional Arguments diag output Print diagnostic messages gen image only Regenerate pattern image only help Display this usage message namemap lt NameMapXMLFile gt Name map XML input file 5 1 XTOS Pattern User Manual P N 57010495 Rev 6 5 2 see e 9 9 6 9 6 6 06 6 6 9 6 6 6 9 6 6 5 e nospin parse only showstats verbose Don t show spinning progress indicator on console Parse the STIL but don t generate a pattern image Print compilations statistics after compiling Print lots of program messages Without any of the optional arguments the compile command displays a spinning progress indicator on the console The optional arguments produce specific informational messages as indicated diag output parse only gen image only namemap showstats verbose nospin nolink This option prints diagnostics messages such as the elapsed time for parsing phase and the pattern image generation This option only performs the parsing phase of the compilation resulting in the generation of the pattern object file directory with only virtual pattern representation vpr file and the statistics text file CompileStats txt This option re generates the pattern image provided that the pattern object file directory already exists previously parsed This option uses an XML input file to be used to map the signal pin defi
48. he pattern statement and the response from the device or until n number of loops is executed GoTo Goto LabeL Currently XTOS software does not support this statement BreakPoint statement Defines a location in the pattern where the device is in a stable state XTOS software currently processes this statement as a NULL vector 1131 WaveformTable Reference A WaveformTable Reference statement must be present before any Vector statements This statement is used to identify the timing sequences associated with the WFCs assigned to signals in the vectors following this statement A WaveformTable Reference statement must precede the first vector in the section The selected WaveformTable remains in force until another WaveformTable Reference statement is used to select a different WaveformTable The two possible syntax of the WaveformTable reference are WaveformTable wavefromtable name W waveformtable name 1 15 XTOS Pattern User Manual P N 57010495 Rev 6 e o 6 9 6 9 ooo 6 6 9 6 9 6 6 6 9 6 6 9 6 6 6 6 6 6 9 6 9 6 6 6 6 6 6 6 6 6 9 o oo 6 6 6 o o o 6 e e 6 e e 6 113 2 Vector Statement The Vector statement defines stimulus and response for one test vector The first Vector statement in a Pattern block needs to have a WFC assigned for every signal used in the pattern After the first vector subsequent vectors only need to contain signal assignment when there is a change to a different state W
49. hile Terminate High at beginning of cycle Strobe Low at end of cycle while Terminate Z at beginning of cycle Strobe High at end of cycle while Terminate Low at beginning of cycle Strobe High at end of cycle while Terminate High at beginning of cycle Strobe High at end of cycle while Terminate Z at beginning of cycle There are no timing value control on these timing events 8K vectors Vector s instruction set supports INC RPT Trigger and Wait for Sync 27 Usage Model The usage model considers both XTOS architecture impact and usage consistent between high speed digital instruments and the DC Channel Instrument Even though there is no flexibility to program timing period values and timing edge values a timing block is provided to satisfy system architecture XTOS provides most of the timing block content Every signal in the DC Channel instrument has these 10 timing sequences built in regardless of whether these timing sequences are used or not The usage model of the timing block is Pre defined period name to select one of four pre defined period values Every signal will have all 10 pre defined timing sequences always available The following are the pre defined names for the four period values 2 10 2 Hardware Support e o 9 6 9 6 6 9 06 6 6 6 6 6 0 6 6 6 9 9 9 6 9 6 6 5 6 6 6 6 6 6 6 9 6 6 9 6 9 6 6 6 6 6 6 6 6 ooo o Perod 5us Period 10us Period 20us P
50. ide which there are two sub directories named Pass_all_F2 cpof and Clock_both_F2 cpof Each of these cpof composite pattern object file directories contain their respective composited LPI Loadable Pattern Image and RPR Runtime Pattern Repository files that are used subsequently by the XTOS pattern loader and other components It is required that the two patterns be compiled before the CompositeLink application is executed on the composite file The above example illustrated the compositing of patterns that belong to a single time domain application XTOS supports the compositing of the multiple time domain patterns through the same mechanism The following example shows the composite block structure for an application with two timing domains named Primary contains pattern files MyPat1 pri stil and MyPat2_pri stil and Secondary contains pattern files MyPat1_sec stil and MyPat2_sec stil This concept is applicable to multiple time domain lt xml version 1 0 encoding ISO 8859 1 gt lt blocks gt Composite name Comp F1 lt DomainList gt lt Domain name Primary gt lt Stilfile gt MyPatl_ pri lt Stilfile gt lt Stilfile gt MyPat2 pri lt Stilfile gt lt Domain gt lt Domain name secondary gt lt Stilfile gt MyPatl sec lt Stilfile gt 5 8 5 XTOS Pattern Compiler and Composite Linker 6 6 oo 6 6 o o oooo 6 6 6 6 6 6 6 9 6 6 6 9 6 6 6 6 6 6 6 6 e 6 e 5 Stilfile MyPat2 sec Stilfile
51. iler will pad each scan chain to make all scan shift chains the maximum length in this example it is 30 The padding is based on the Condition statement in the macro The padding will be provided to the beginning of each input scan chain and to the ending of each output scan chain 3 Condition statement The scan operation is defined as macro In the Condition C statement the default states provide scan signals padding WFC and broadside signals WFC No passing in broadside states in this example if broadside is always fixed states 4 Shift statement The Shift statement defines the scan shift operation The r means repeat the following WFC times This short hand notation provides the convenience of applying the shift instruction to all three scan inputs and outputs In other words V3 If there are 100 scan shift chains then we can use r100 3 4 3 Example 3 Scan pattern with Procedure but without ScanStructures block STIL 1 0 TRC Dos Header Title Simple Scan Pattern 3 No ScanStructure Use Procedure Date Sun Dec 14 14 10 00 2003 Signals sigl In sig2 In bus1 InOut bus2 InOut sig3 In sig4 In sig5 In Sig6 Out sig7 Out sig8 Out SignalGroups sil sig3 ScanIn 20 si2 sig4 ScanIn 30 si3 sig5 ScanIn 25 sol sig6 ScanOut 20 so2 sig7 ScanOut 30 so3 sig8 ScanOut 25 scan_in sil si2 si3 Scan out
52. ill be expanded to straight line v Abus HH v Bbus LH 1137 MatchLoop Statement 1 18 The MatchLoop construct in STIL provides basic capability to wait for certain conditions state of specific signal s or other condition to be met before exiting the loop It is used to support Match Continuous Sync and Trigger capabilities in the system The XTOS pattern compiler ignores the BreakPoint block in the MatchLoop construct Some UserKeywords are added to support Sapphire NP hardware capabilities 1 Pattern File STIL Description 6 0 0 lt 0000000 0 6 6 6 6 6 9 6 6 9 6 6 6 6 6 6 9 6 9 6 6 6 9 6 6 9 oo 6 6 6 6 6 9 6 6 6 6 e 5 The syntax of the MatchLoop statement are MatchLoop loop count Infinite gt vector statement BreakPoint vector statement 114 Pattern Examples The contents of PatternBurst PatternExec and Pattern blocks are shown in the working examples below These examples illustrate various STIL statements and their applications The Signals SignalGroups Timing and WaveformTable blocks are used through the application of the Include statement 1141 Example 1 A pattern that uses 1 bit of functional data per pin Application of W V and Loop statements are illustrated here STIL 1 0 Include pattern include inc Using Include file to hold identical information PatternBurst dummy PatList Pass all PatternExec Timing Vec Def
53. injury or loss whether direct or indirect or consequential damages of any kind caused by a failure to adhere to the safety standards and procedures in this manual 2003 NPTest All rights reserved P N 57010495 Rev 6 Printed in U S A ECO Number 27668 December 2003 Contents Preface MERERI EIL LCD aa ix Intended Audience coi rep Ya eve UN a EA E RUE E E PEE ERE WERT dr ege ix Revision Histoby ios oper A et odas be Bur d Sabe e V UE deir a Vp qs darn e PR eR ix Related Publications ix Chapter 1 Pattern File STIL Description 1 1 11 XTOS Pattern File STIL Structure 1 1 12 STL BVO GS ae ee A EL M eae M edu 1 3 13 STIL Statement a d 8 AS dt dg te d eg 1 3 1 4 Header Statement da dee 1 3 15 Include Statement serere das cocinada a is Leeda SREL a 1 4 1 6 Signals Block cuina dos 1 4 17 SignalGroups Block armo sr ies ed 1 5 174 F2 and Fn Mode Declaration lisse eh 1 6 18 ScanStructures Block 1 6 1 8 1 Scan Data Alignment Scan Padding 0 cece cece cece eee eee eee 1 7 19 Timing and WaveformTable Block 1 7 1 9 1 Resource Tags icons adn cased dew tended da dace eee ee wens 1 8 1 9 2 Event States In STIL det RRA IR AES 1 9 1 9 3 Waveform Character 1 10 1 9 4 Merge Waveforms mein a e die dae 1 10 110 PatternBurst and PatternExec Blocks 1 12 LI Procedures iii Ad a E ENEE EE e EA 1 13 112 Ma roDefs a ee deg RE Sdt SE da Gon des DEDE 1 14 113 Pattern Block iii Div rd ia died ba 1
54. l the exit condition to only exit on a Dial a Pipe DAP boundary with the keyword onDAP For example if the DAP is 250 the match always exits on multiples of 250 cycles If match happens on cycle 600 the match loop exits on cycle 750 These two exit conditions can be used separately or combined together 2 4 2 Hardware Support 6 9 6 6 9 6 9 06 6 6 6 6 6 6 6 6 9 6 9 6 6 9 0 9 6 6 6 6 6 6 6 6 6 6 9 6 6 9 6 6 6 6 5 6 6 9 6 9 6 6 6 6 oeoo ooo 6 6 9 6 6 e 6 e e 2 3 The STIL extensions are defined as UserKeywords NPTTriggerDef NPTGenerateTrigger NPTWaitTrigger NPTLatencyPipeDef NPTTriggerDef trigger name Exit onDAP onRatio NPTLatencyPipeDef pipeline length Example 1 Possible NPTTriggerDef Syntax NPTTriggerDef aTrigger Exit onDAP onRatio NPTTriggerDef 2Trigger Exit onRatio NPTTriggerDef 2Trigger Exit onRatio bTrigger NPTTriggerDef 2Trigger Exit onRatio bTrigger Exit onDAP NPTTriggerDef aTrigger bTrigger cTrigger NPTTriggerDef aTrigger Example 2 UserKeywords NPTTriggerDef NPTGenerateTrigger NPTWaitTrigger NPTLatencyPipeDef NPTTriggerDef startMyTest doMyTest testIsDone NPTTriggerDef endTest Exit onDAP onRatio NPTLatencyPipeDef 400 Pattern TRY WaveformTable MY WFT Vector sigl 00 sig2 11 NPTWaitTrigger startMyTest Vector sigl 00 MatchLoop Infinite Vector sigl 01 BreakPoint Vector sigl 11
55. m is provided through alternative data source selection process A set of different symbols may be defined as STIL extension syntax to support various data sources These symbols are used to distinguish the alternative data source between analog source and analog capture It is important to note that within a pin slice all analog source signals source at the same time and all analog capture signals capture at the same time However the analog source signals and capture signals do not have to be used at the same time This results in three different alternative data selection combinations involving analog signals within one pin slice They are all source all capture and all source and capture The XTOS STIL complier support for the analog application is provided using the waveform characters in the WaveformTable This is accomplished by defining dedicated timing sequences when alternative data source selection is needed in the pattern Two new keywords NPTAnalogSource and NPTAnalogCapture are used to define digitized analog applications These keywords are used in front of the event list to mark the current event list and WFC to be used for analog application Only one waveform character is allowed for the event list since the analog instrument and not the digital pattern memory provides the pattern data 41 Digitized Analog Pattern Example The user can mark any sequence containing a single waveform character with the use of NPTAnalogSource or NPT
56. n User Manual P N 57010495 Rev 6 e o 6 9 6 9 6 6 9 6 6 9 6 9 6 6 6 9 6 6 9 6 6 6 6 6 6 9 6 9 6 6 6 6 6 6 6 6 oo oo 6 6 6 6 9 6 9 6 000000 171 F2 and Fn Mode Declaration If some signals or signal groups need to have multiple F data to support the data rate then the attribute of DataBitCount can be used to imply the number of F data bits The DataBitCount is number of signals number of F data bits For example F2 mode with signal group of 2 signals will have DataBitCount 4 F4 mode with signal group of 2 signals will have DataBitCount 8 It should be noted that a databit count is the number of signals multiplied by the number of F data bits only when defining the databit count inside a SignalGroups It is also valid to declare a databit count for a single signal The DataBitCount does not represent a direct declaration of F data bits Instead the maximum DataBitCount is determined for each signal across the whole pattern considering each occurrence in the in the Signal or SignalGroup block The remaining F data bits are also padded if the signal expression calls for fewer fdata bits than the maximum Below is an example of F2 mode SignalGroups of Abus and Bbus SignalGroups Abus Abus 1 Abus oi DataBitCount 4 Bbus Bbus 1 Bbus_0 DataBitCount 4 Cbus Cbus 1 Cbus_0 Dbus Dbus 1 Dbus 0 allPins Abus Bbus Cbus Dbus Below is an example of F4 mode Si
57. nitions as described in the test program The file name here is the one that contains the name map XML block s name used by the test program This option prints the compilation process s statistical information such as the Vector Type Select definitions and procedure call statistics This option displays the compilation process details such as the signal names associated with each Event Sequence Store location This option silently performs the compilation without the spinning progress indicator and the elapsed time information This option overrides the default behavior of the complier so that a composite image is not generated only a loadable pattern image is generated Please refer to the XTOS Software Tools Manual P N 57510507 for details on name map XML block 51 2 NameMap Support in XTOS Pattern Compiler The XTOS pattern compiler uses an XML NameMap block that is associated with the test program to define blocks containing references of STIL names to names defined in the XTOS test program This is a required argument to be used with the XTOS pattern compiler CompileStil exe An example of the NameMap file used is lt xml version 1 0 encoding ISO 8859 1 gt lt Created by XML decompiler version 1 0 gt blocks NameMaps name Loadboard 1 Sites count 1 gt lt ThreadModel gt Single lt ThreadModel gt 5 XTOS Pattern Compiler and Composite Linker 6 6 9 6 6 9 6 9 06 6 6 6 6
58. ompatible Subroutine Statements UserKeywords NPTSubroutine NPTOpcode NPTSelectCounter Procedures PROC STIL WaveformTable MY WFT Vector sigl sig2 11 Vector sigl 00 NPTSubroutine MY SUBR EDA readable MY SUBR WaveformTable MY WFT Vector sigl 00 sig2 11 Vector sigl 11 NPTSubroutine MY SUBR2 EDA readable MY SUBR2 WaveformTable MY WFT Vector sigl 00 sig2 11 MY LOOP NPTSelectCounter A Select Counter A Loop 95 Vector sigl 10 sig2 10 Vector sigl 00 sig2 01 Vector sigl 11 Pattern TRY WaveformTable MY_WFT Vector sigl 00 sig2 11 2 Hardware Support 6 9 6 6 9 6 9 06 6 6 6 6 6 6 6 6 9 6 9 6 6 9 0 9 6 6 9 6 6 6 6 6 6 6 6 9 6 6 o 6 6 5 6 6 9 6 9 06 6 6 9 6 6 6 9 6 6 6 6 6 6 9 6 6 6 6 e e e Vector Call PROC_STIL sigl 11 WaveformTable MY WFT Vector sigl 00 sig2 00 Vector sigl 01 sig2 10 Call MY SUBR No parameter passing for Subroutine WaveformTable MY WFT Vector sigl 00 sig2 00 sig2 11 Vector Call MY SUBR2 No parameter passing for Subroutine WaveformTable MY WFT Vector sigl 11 Pattern Compiler expands procedure PROC STIL to be a straight line vectors and map procedure MY GUDD and MY SUBRe to be test system subroutines The corresponding Call vector is handled properly as well The last vector is mapped to opcode RET in the procedure MY SUBR The Loop vectors of MY SUBR 2 are
59. oooooomcoooconcconcromssnoo 6 1 jj AP PI EEN Index 1 seess Figures Figure 1 1 Timing Block and STIL Pattern Connection 0 cece cece cece nee eee cr 1 8 XTOS Pattern User Manual P N 57010495 Rev 6 6 eo o 6 O6 9 6 6 9 6 9 6 6 6 6 06 6 9 6 6 6 6 9 6 6 09 6 6 6 6 6 6 6 6 6 9 6 9 6 6 9 6 6 6 6 6 6 6 6 6 0 6 6 000 6 vi Tables Table 1 1 Table 1 2 Table 1 3 Table 1 4 Table 1 5 Table 2 1 Drive States cuicos a e 1 9 Compare State isse al a e oe ee e e ne a dile 1 9 Expect States victor pb E REIP PRAGA Wa A AE A TERR TA E Me gether CO E 1 9 Indeterminate States eder eurer A 1 10 WFC CONVENTIONS 3 3 tede aladas Quinti uere p 1 10 Maximum Total Latency e e he ee e een 2 4 vii XTOS Pattern User Manual P N 57010495 Rev 6 6 9 6 6 9 06 9 6 6 6 6 6 o 6 O 9 eo 9 6 6 6 6 6 6 9 6 6 6 6 9 6 6 9 6 6 6 6 6 6 6 6 9 6 6 6 6 9 6 6 6 6 6 6 6 6 6 6 6 6 6 9 e 6 viii Preface This XTOS Pattern User manual describes the details of the source syntax accepted by the XTOS Pattern Compiler Intended Audience This manual is intended for use by anyone using the Sapphire NP test system with XTOS software Familiarity with the digital testing concepts and prior test experience with the IEEE 1450 Standard Test Interface Language STIL for Digital Test Vector Data Standard are recommended Revi
60. or sigl 00 sig2 t 7 using sig2 33 Vector sigl 11 8 Pattern TRY WaveformTable MY_WFT Vector sigl 00 sig2 11 o Vector sigl 00 sig2 11 FS Call PROC STIL Vector sigl 00 sig2 11 4 Vector sigl 00 sig2 11 5 Call MY SUBR Vector sigl 00 sig2 11 Param Vector sigl 00 sig2 11 9 returns here after MY SUBR Vector sigl 00 sig2 33 Param sigl 00 sig2 11 10 Vector 2 9 XTOS Pattern User Manual P N 57010495 Rev 6 e o o 6 9 6 6 6 6 6 6 6 6 6 6 06 9 0 6 6 6 6 6 6 6 6 00000 6 96 6 9 6 6 9 6 6 6 6 6 6 0 6 6 6 9 6 6 6 6 6 6 6 o 6 56 In the above example the pattern uses to indicate sig2 Fdata is coming from Main data 27 DC Channel Pattern Application The 96 pin DC Channel instrument is one of the Sapphire NP instruments This instrument provides a very limited timing pattern capability to the 96 channels on each instrument The characteristics of the DC Channel instrument can be summarized as following Four fixed period values 5 us 10 us 20 us 40 us no period switching on the fly Ten fixed timing sequence per channel timing sequence can be changed on the fly NOP Drive Low at beginning of cycle Drive High at beginning of cycle Drive Z at beginning of cycle Strobe Low at end of cycle while Terminate Low at beginning of cycle Strobe Low at end of cycle w
61. pattern 1 13 1 14 1 22 2 1 sync trigger pin 1 4 syntax annotation statement 1 21 call statement 1 16 comment statement 1 22 condition statement 1 16 KeepAlive vector statement 2 8 loop statement 1 18 macro statement 1 17 MacroDefs block 1 14 MatchLoop statement 1 18 PatternBurst block 1 12 PatternExec block 1 12 procedure block 1 13 ScanStructure block 1 6 SignalGroups block 1 5 signals block 1 4 source 1 ix subroutine memory 2 1 2 2 timing block 1 7 vector statement 1 15 procedure 2 1 T ScanLength 1 7 template ScanOutLength 1 7 i SE ER shift 3 1 si STIL 1 3 block 1 7 1 18 2 10 subroutine 2 2 dod UserKeywords 1 22 EES vector 1 15 2 7 U WaveformTable reference 1 15 UserKeywords STIL extensions 1 3 annotation 1 21 NPTAlternativeDataSource 2 9 block 1 3 NPTAnalogCapture 4 1 comment 1 22 NPTAnalogSource 4 1 defination ix NPTIncMain 2 9 extension 2 4 NPTOpcode 2 1 extension syntax 4 1 NPTSubrountine 2 1 2 8 standards 1 1 NPTSubroutine 1 12 statement 1 3 NPTWaitTrigger 2 6 2 8 UserKeywords 1 22 statement 1 22 subroutine STIL statement 1 3 EDA compatible 2 2 subroutine support 1 12 2 1 extension 2 1 parameter passing 2 9 Y vector resource 2 1 statement 2 2 syntax 2 1 2 2 SUBROUTINE F 5 6 Index 4 file 1 1 statement 1 15 2 7 syntax 1 15 wait until sync See WUS waveform character See WFC waveform event 1 11 WaveformTable analog support 4 1 block 1 7 1 11 1 18 reference 1 14 reference s
62. pport hardware capability in which case an EDA tool may not be able to simulate this pattern directly from STIL syntax If a specific STIL procedure is targeted to be a Subroutine then the keyword NPTSubroutine needs to be attached in front of the procedure as an identifier If there is any Loop construct or load counter in the Subroutine then NPTSelectCounter should be used to select one of the counters as the loop controller XTOS pattern compiler 2 1 XTOS Pattern User Manual P N 57010495 Rev 6 e 2 0e 1 o 12 xo 0 0000 9 6 6 9 6 6 6 6 6 6 6 9 6 6 6 6 6 6 6 5 6 6 6 9 6 6 6 9 6 6 6 6 6 6 e 6 6 2 2 handles the proper loop expansion to satisfy the hardware requirement The test System has eight counters available for loop control A through H and the last two pair E F and G H can be concatenated The extension syntax for Subroutine support is UserKeywords NPTSubroutine NPTOpcode NPTSelectCounter NPTSubroutine subroutine name NPTOpcode CALLZ LDC BNZ Operand Where 1 NPTSubroutine is used to declare the following STIL Procedure block is a Subroutine NPTOpcode is used either in main pattern section as CALLZ or LDC opcodes or in the subroutine section as LDC or BNZ opcodes subroutine name is the subroutine name 4 5 NPTSelectCounter is used to select a counter A through H Operand is a count for LDC or label for BNZ Example 1 EDA C
63. psed time for parsing phase and the pattern image generation verbose This option displays the compilation process details such as the signal names associated with each Event Sequence Store location 5 2 2 XTOS Pattern Decomplier Command Line Interface Solaris The command line interface for the XTOS pattern decompiler is located at XTOS release_number bin DecompiletoStil exe Decompilation of a pattern file in XTOS software results in a STIL source file of the same name Typing the decompile command with the help parameter displays the following command usage for the pattern decompiler usage XTOS release_number bin DecompiletoStil exe options lt POFFileName gt Required Arguments lt POFFileName gt pattern object file to decompile Optional Arguments diag output Print diagnostic messages help Display this usage message verbose Print lots of program messages Without any of the optional arguments the decompile command displays a spinning progress indicator on the console The optional arguments produce specific informational messages as indicated diag output This option prints diagnostics messages such as the elapsed time for parsing phase and the pattern image generation 5 5 XTOS Pattern User Manual P N 57010495 Rev 6 5 6 see e zs eseeseesese verbose This option displays the compilation process details such as the signal names associated with each Event Sequence Store location
64. ration The load_unload operation is commonly implemented as a STIL Procedure or Macro 3 Scanln and ScanOut Declaration A Signal or SignalGroups declaration supports scan operation with two attributes Scanln and ScanOut The signal must be assigned one of these attributes to be allowed to operate as a scan signal SignalGroups scan in name signal name ScanIn scan out name signal name ScanOut 32 Shift Statement The main statement to support scan in STIL is the Shift statement which contains one or more vectors required to shift one scan event in or out of scan chains Vectors within the Shift block use a special waveform character in signal assignments to indicate that scan data is to be substituted in the vector for the signal The values to be substituted are defined in the Call or Macro invocation The scan data passed in the Shift block is presented in left to right order the left most waveform character is the first data for that signal Procedures load unload W scan timing C SI 0000000000 SO XXXXXXXXXX shift 3 1 XTOS Pattern User Manual P N 57010495 Rev 6 6 9 6 9 6 6 6 6 9 6 6 6 0 06 6 06 6 9 0 6 6 6 9 6 6 9 6 9 6 6 6 9 6 6 9 6 6 6 6 6 6 6 6 9 6 6 6 6 6 6 6 6 6 6 6 9 6 6 6 9 6 6 6 6 6 6 00 0 0 V SI IHHHHHHHHHE SO THHHHHHHHHE scan clk 1 Pattern scan pat W scan timing V all pins 0010XXXX0011100HHLHXXX01010
65. rious features that access the pattern data An example structure of a pattern object directory is Source file PAT1 STIL Upon compiling the above file a PAT1 pof directory is created with a vpr rpr Ipi and a text file containing the compiler statistics The first three files are binary objects used by the XTOS software while the fourth one is for the user s information Typing the compile command with the help parameter displays the following command usage for the pattern compiler usage XTOS release number bin CompileStil exe options lt STILFileName gt Required Arguments lt STILFileName gt STIL file to compile 5 3 XTOS Pattern User Manual P N 57010495 Rev 6 e o o 6 9 6 9 6 6 o o 6 6 6 9 6 6 9 6 6 6 6 6 6 9 6 9 6 6 6 6 6 6 6 6 6 9 6 9 6 6 6 9 6 6 6 6 6 6 6 6 9 6 0 0 e Optional Arguments diag output Print diagnostic messages gen image only Regenerate pattern image only help Display this usage message namemap lt NameMapXMLFile gt Name map XML input file nospin Don t show spinning progress indicator on console parse only Parse the STIL but don t generate a pattern image showstats Print compilations statistics after compiling verbose Print lots of program messages Without any of the optional arguments the compile command displays a spinning progress indicator on the console The optional arguments produce specific informational messages as indicated
66. s A Waveform Table block example is shown below Timing WaveformTable MY WFT lt Period_lus gt Period 1000ns Waveforms SIG 1 lt DCC_T1L gt L Ons D 995ns h DCC DO O Ons D SIG 2 DCC DZ a Ons Z DCC DO b Ons 0 2 11 XTOS Pattern User Manual P N 57010495 Rev 6 6 oso oo o o oo 9 6 6 o 6 6 6 9 6 6 9 6 6 6 0 6 6 6 6 6 6 6 6 6 6 6 9 6 6 9 6 9 6 6 6 6 6 6 o6 e 5 DCC D1 c O0ns 1 DCC TOL d Ons D 995ns 1 DCC T1L e Ons D 995ns h DCC TOZ f Ons Z 995ns 1 DCC T1Z g Ons Z 995ns h A DC Channel pattern block example is shown below Pattern TRY WaveformTable MY_WFT Vector SIG 1 L SIG 2 g Vector SIG_1 0 SIG 2 f Vector SIG_1 L SIG 2 a SIG_1 0 SIG 2 29 Vector DCC Sequence Memory ADV 4 MY WFT DCC Pattern Data Memory SIG 1 L SIG 2 g SIG 1 0 SIG 2 f SIG 1 L SIG 2 a SIG 120 SIG 2 29 Scan Support 3 STIL has adopted the use of scan test patterns by various ATPG tools in many EDA environments Scan pattern is a repeat process of scan load operation followed by a launch and capture operation and ends with a scan unload The effect of scan in a scan pattern is often the result of the merge of the previous unload operation with the next load operation The resulting scan pattern is typically shown as a scan load_unload operation followed by a launch_capture ope
67. s PatF2 PatM2 and PatQ2 belong to the user name Divide Patterns PatF3 PatM3 and PatQ3 belong to the user name Boolean A composite block may only contain the Pattern sections It is important to note that in a multiple time domain composite the number of patterns in each domain must be the same An example XML block syntax for the above composite block is shown below This results in three composites named FullTime HalfTime and QuarterTime lt Composite name myComposite gt lt PatternList gt this list is optional if specified then these names may be used in the PatternBurst list lt Pattern name Multiply gt lt Pattern gt lt Pattern name Divide gt lt Pattern gt lt Pattern name Boolean gt lt Pattern gt lt PatternList gt lt DomainList gt lt Domain name FullTime gt lt Stilfile gt PatF1 lt Stilfile gt lt Stilfile gt PatF2 lt Stilfile gt lt Stilfile gt PatF3 lt Stilfile gt lt Domain gt lt Domain name HalfTime gt lt Domain gt lt Stilfile gt PatF1 lt Stilfile gt lt Stilfile gt PatF2 lt Stilfile gt lt Stilfile gt PatF3 lt Stilfile gt lt Domain name QuarterTime gt lt Stilfile gt PatF1 lt Stilfile gt lt Stilfile gt PatF2 lt Stilfile gt lt Stilfile gt PatF3 lt Stilfile gt lt Domain gt lt DomainList gt lt Composite gt The creation of a composite image is achieved in two steps First the patterns need to be compil
68. sion History The following table presents the revision history of this publication for the current revision and if applicable the previous two revisions dip Date Notes 6 12 03 Enhanced Chapter 3 Scan Support 5 12 03 Updated to clarify information in Chapter 1 4 11 03 Updated to conform to latest documentation standards Related Publications In addition to the IEEE standard 1450 these NPTest publications provides additional information for some of the topics covered in this publication References to these related publications are made in the text of this publication whenever appropriate XTOS Software Tools Manual P N 57510507 XTOS Pattern User Manual P N 57010495 Rev 6 6 9 6 o o 6 6 9 06 9 06 6 9 0 6 6 6 6 6 9 6 9 6 6 9 6 6 6 6 9 6 6 6 6 6 06 6 6 6 9 6 6 6 6 6 6 6 9 6 6 9 6 6 6 6 6 6 6 6 0 Pattern File STIL Description This chapter describes the basic capabilities of the pattern source file The pattern source file contains statements providing functional test vectors for the Sapphire NP test system The pattern file provides a convenient way to specify the stimulus and expected response data for functional testing XTOS pattern language is based on IEEE 1450 standard Standard Test Interface Language STIL and its extensions Some extensions are added through STIL s UserKeywords to expand the scope to support NPTest s hardware capabilities and
69. sol so2 so3 pa_pin sigl sig2 busl bus2 all pin Da pin scan in scan out 3 Scan Support 6 e 6 6 6 6 6 6 9 6 6 9 0 9 6 6 9 6 6 6 6 6 6 0 6 6 9 6 6 6 6 5 6 6 9 6 9 6 6 6 6 9 6 6 6 6 06 6 9 6 6 6 6 9 6 6 6 6 e 5 e Timing T1 WaveformTable W1 Period 100ns Waveforms Ons D U Ons L H X Ons D U Ons Z onsen L H scan in in sc 01 scan out ou sc LHX pa pin in seq 01 z seq Z c ou seq LH end WaveformTable W1 end Timing T1 g Procedures all_scans Note 1 W W1 C pa_pin scan in 000 scan out XXX Shift V scan_in r3 d scan_out r3 PatternBurst burst3 PatList pat3 end PatternBurst hello tester burst PatternExec Timing T1 PatternBurst burst3 end PatternExec Pattern pat3 W W1 V all pin 00ZZ000xxx Scan pat 0 Call all scans pa pin 10ZZ Note 2 sil 10101111110000011001 si2 111110000011111000001111100000 si3 1111111111111111111111111 v all pin 01HH100HHL V all pin 11LHO11LXH Scan pat 1 Call all scans pa pin 00LL sil 10101111110000011001 si2 111110000011111000001111100000 si3 1111111111111111111111111 SOl HLHHHLXXLLXXXXLLLLHH SO2 HHHHLLLLLLXXXXXXXXLLHHLLHHHXXL SO3 LLLXXXXHHHXXXLHHHLLLHHHXL XTOS Pattern User Manual P N 57010495 Rev 6 6 9 6 6 9 6 6 6 6 6 6 6 6 0 06
70. t program and their types such as In Out InOut Supply and Pseudo The type In Out or InOut is used to define a regular signal The type Supply is used for power or ground pins there is no functional data with these pins The type Pseudo is used to support certain test operations with no device signal association such as sync trigger pin It also defines the base signal names for all the ports of the design Signal names must begin with an alphabetic character or an underscore Signal names can also be enclosed in double quotes Signal names with double quotes use the two double quotes as part of the signal name In other words signal Abus is a different signal from signal Abus Signal names are also case sensitive and hence the same names with different cases refer to different signals The syntax of the Signals block is Signals sig name In Out InOut Supply Pseudo gt d Below is a Signals block statement example Signals Abus_0 In Abus 1 In 1 7 Bbus_0 Bbus_1 Cbus 0 Cbus 1 Dbus 0 Dbus 1 SignalGroups Block 1 Pattern File STIL Description 9 0 6 6 6 6 6 6 6 6 6 9 6 9 6 ooo 6 6 6 oo e 9 e 5 zs eeeeseeee This block is an optional block and refers to a group of signals These groups can only refer to a collection of existing signals A SignalGroup of one signal simply results in the renaming of that signal This feature facilitates a mechanism to reference the same signal
71. t state 1 9 F F2 data 1 12 mode 1 6 F data 1 6 1 10 FM mode 1 10 FTest 1 12 H header block 1 3 statements 1 3 I IEEE 1450 ix 1 1 2 1 1450 3 1 1 1999 1 1 2 1 IfNeed option 1 4 include file 1 4 1 19 statement 1 4 indeterminate state 1 9 K KeepAlive vector statement 2 8 syntax 2 8 Index 2 label statement 1 22 latency pipe 2 3 loop continuous 2 5 statement 1 17 syntax 1 18 M macro MacroDef 1 17 statement 1 14 1 17 2 1 syntax 1 17 MacroDef 1 17 MacroDefs block 1 13 syntax 1 14 match call 2 8 MatchLoop statement 1 18 2 7 syntax 1 18 memory main 1 17 2 9 subroutine 1 17 2 1 2 2 2 9 merge waveform 1 10 N NameMap block 1 3 5 2 file 5 2 NPTAlternativeDataSourceDef 2 9 NPTAnalogCapture 4 1 NPTAnalogSource 4 1 NPTest UserKeywords NPTAlternativeDataSource 2 9 NPTAnalogCapture 4 1 NPTAnalogSource 4 1 NPTIncMain 2 9 NPTOpcode 2 1 NPTSubroutine 1 12 2 1 2 8 NPTWait Trigger 2 6 2 8 NPTIncMain 2 9 NPTIncMain statement 2 9 NPTOpcode 2 1 NPTSubroutine 1 12 2 1 2 8 NPTWaitTrigger 2 6 2 8 null statement 2 7 opcode NPTOpcode 2 1 PARAM 2 1 operation BNZ 1 17 RPT 1 17 P PARAM opcode 2 1 parameter passing 2 1 2 9 PatList 1 12 pattern block 1 12 1 14 1 18 compiler 5 2 5 7 compositor 5 9 statement BreakPoint statement 1 15 call 1 14 1 16 condition 1 14 1 16 GoTo 1 15 loop 1 14 1 17 macro 1 14 1 17 MatchLoop 1 15 1 18 vector statement 1 14 1 15 WaveformTable ref
72. tatement 1 15 WFC ASCII 1 10 conventions 1 10 event mapping 1 10 resource tag 1 8 signal state 1 14 signals 1 13 WUS 2 5 2 7 Index 5 XTOS Pattern User Manual P N 57010495 Rev 6 9 6 6 0 6 6 6 9 0 6 9 6 6 9 9 6 9 0 6 0 9 06 6 9 0 6 6 0 9 0 9 6 0 9 0 6 9 0 9 06 0 9 6 6 6 9 6 6 9 06 9 06 9 6 0 6 6 6 6 Index 6 Reader Comments We would appreciate your taking the time to complete this form and return itto us Your answers are a valu able aid in improving the quality and usefulness of our documentation All responses are confidential and remain the property of NPTest Publication XTOS Pattern User Manual Part Number P N 57010495 Rev 6 Date December 2003 How do you use this publication As an introduction L As a reference L As a training text L Other L Yes L No If a user guide is it easy to understand If a reference is it easy to use If not please explain why L Yes L No If a user guide does it contain all the relevant information to understand and operate the product If not what additional information would you like Yes No Were the illustrations helpful If not please explain why L Yes L No Would you like more illustrations If so of which subjects L Yes L No Is the information in the publication accurate If not please identify the inaccuracies Other Comments Name Tite Dae Compan
73. tements in the ScanChain block The XTOS pattern compiler uses the longest scan chain to determine the padding required for the shorter ones The pad data is added to the beginning of the scan in data and to the end of scan out data 19 Timing and WaveformTable Blocks Timing and WaveformTable blocks are required in a STIL pattern to define timing information The Timing block contains definitions of event behavior across all signals in the test pattern A collection of these definitions is contained in the WavefromTable blocks All WaveformTables used in a pattern must be defined in one Timing block WaveformTable block consists of one or more Waveform s for each signal or signal group The Waveform statement is used to map a signal s waveform character WFC to an event list also known as the timing sequence XTOS Pattern User Manual P N 57010495 Rev 6 zs 6 9 6 6 6 6 6 6 6 6 02 0 0 o ooo 9 6 9 6 ooo 9 6 6 9 6 6 6 6 6 6 6 6 9 6 6 6 o 6 6 co 6 6 9 6 6 6 9 6 6 6 6 6 6 oo 6 The syntax of the Timing block is Timing timing domain name SignalGroups group name WaveformTable Waveform table name period name Period time expression Waveforms signal ref sequence name WFC List time expression event p p ps Where lt period_name gt lt sequence_name gt The lt resource tag gt to map pattern s Waveform to test program s timing sequence see Resource Tags
74. templates pattern loader import java io import Sapphire CAP import Sapphire ITA import com nptest sapphire test templates public class PatternLoader extends TestTemplateBase These variables are initialized by the setParam methods protected PatternBlock Pattern null Temp for a while protected PatternBurstBlock PatternBurst null private ParameterInfo PatternBurstParamInfo new ParameterInfo PatternBurst ParameterInfo OPTIONAL PatternBurst to load private ParameterInfo PatternParamInfo new ParameterInfo Pattern ParameterInfo OPTIONAL Pattern block to load private boolean pattern loaded false Temp for a while private boolean pattern burst loaded false private boolean all pattern bursts loaded false 6 1 XTOS Pattern User Manual P N 57010495 Rev 6 6 9 6 6 6 6 6 6 6 9 6 9 6 6 9 06 9 06 6 9 0 6 6 6 6 6 6 9 6 9 6 6 9 06 6 6 6 9 6 6 6 6 6 06 6 6 6 9 6 6 6 6 6 6 6 9 6 6 9 6 6 6 6 6 6 6 e oe 5 5 Validate method x Checks that all parameters are correct public void validate throws java lang Exception move the checking of the PatternBurst block down to execute Execute method Loads either the specified PatternBurst block or all PatternBurst blocks public Sapphire CAP TestStatus execute throws java lang Exception if Pattern null amp amp pattern load
75. tern decompiler can be invoked from a Command Line Interface in a Command Prompt window XTOS pattern decompiler decompiles the vpr virtual pattern representation file into the source STIL file The pattern decompiler is available for the Windows 2000 and Solaris operating systems 5 4 5 XTOS Pattern Compiler and Composite Linker 9 6 6 9 6 6 9 6 6 6 6 6 6 6 9 6 6 9 0 6 6 6 6 0 9 06 6 6 9 6 6 6 6 9 06 6 6 6 6 6 9 6 6 6 6 69 6 6 6 6 e e e e e wee eee 5 2 XTOS Pattern Decomplier Command Line Interface Windows 2000 The command line interface for the XTOS pattern decompiler is located at XTOS release_numben bin DecompiletoStil exe Decompilation of a pattern file in XTOS software results in a STIL source file of the same name Typing the decompile command with the help parameter displays the following command usage for the pattern decompiler usage XTOS release_number bin DecompiletoStil exe options lt POFFileName gt Required Arguments lt POFFileName gt pattern object file to decompile Optional Arguments diag output Print diagnostic messages help Display this usage message verbose Print lots of program messages Without any of the optional arguments the decompile command displays a spinning progress indicator on the console The optional arguments produce specific informational messages as indicated diag output This option prints diagnostics messages such as the ela
76. ts is illustrated here STIL 1 0 This is MyPat_F2 stil file Include MyPat F2 include inc PatternBurst dummy PatList MyPat_F2 1 20 1 Pattern File STIL Description 6 6 9 6 6 9 6 9 06 6 6 6 6 6 6 6 6 9 6 9 6 6 9 6 9 6 6 6 6 6 6 6 6 0 9 0 6 6 6 5 6 6 9 6 9 6 6 6 6 9 6 6 6 6 6 6 6 6 6 6 9 6 6 6 6 e 5 PatternExec Timing Vec Def PatternBurst dummy Pattern My pat F2 W Vec 0 FF FF FF FF 12 12 12 12 V Abus 00 00 Bbus LL LL vi d V Abus 01 01 Loop 500 V Abus 11 01 Bbus HH LL W Vec 1 V Abus LL LL Bbus 00 00 V Abus LH LH The contents of MyPat F2 include inc file are STIL 1 0 TRC D 0 8 Signals Abus_0 In Abus 1 Tn Bbus 0 Out Bbus 1 Out SignalGroups Abus Abus 1 Abus oi DataBitCount 4 Bbus Bbus 1 Bbus 0 DataBitCount 4 allPins Abus Bbus Timing Vec Def WaveformTable Vec 0 period 0 Period 10ns Waveforms Abus Abus D gt 01 Ons Bbus Bbus S LH 25ns WaveformTable Vec_1 period 1 Period 10ns Waveforms Abus Abus S LH 25ns Bbus Bbus D 01 Ons 50ns D U 1 75ns H L 1 75ns H L 1 50ns D U 1 XTOS Pattern User Manual P N 57010495 Rev 6 e o o 6 6 6 9 6 6 9 06 6 6 oo 6 9 6 6 9 ooo 6 6 6 9 6 6 6 6 6 6 6 6 6 6 e e 5 115 Additional STIL Statements
77. tterns This phase is used to optimize the pattern resources in Sapphire NP test systems This is implemented during a post STIL compile step using an application called CompositeLink The compositing of patterns provides an optimized scheme of resource usage by creating a common set for the following resources ina composite directory Common Event Sequence Store Memory ESSM locations Common Source Data Select SDS Common Triggers Syncs Common Subroutine Data Note that the set of patterns that can be processed into a single composite should belong to the same timing domain Details related to the process of compiling and compositing the STIL patterns are covered in the subsequent chapters of this document STIL maintains a define before use mandate on most information This requirement sets a general ordering of the STIL blocks There are also several exceptions to the define before use rule In general the Pattern blocks are located at the end of the STIL file and after the PatternBurst block The STIL s data block organization is Signals SignalsGroups Timing PatternBurst PatternExec Pattern XTOS pattern structure supports the following STIL top level statements and features in processing the pattern data STIL statement Header statement Include statement Signals statement SignalGroups statement ScanStructures statement 1 Pattern File STIL Description 9 0 ooo 6 9 06 6 9 6
78. ubroutine version of Procedure does not allow a signal assignment statement in the Call statement 1 16 1 Pattern File STIL Description 6 0 6 6 9 6 9 6 6 9 6 6 6 6 6 6 6 6 9 6 6 96 0 6 6 6 6 6 9 6 6 6 6 6 9 6 6 6 6 6 06 6 6 6 6 6 6 6 6 6 e 5 The syntax of the Call statement is Call signal assignment Where signal assignment has syntax as signal ref WFC or WFC list Below is an example of a Call statement Procedure Proc A W timing X one 1 two V V one d two V in I OG one 0 two Pattern XXY W timing X V one 0 two H Call Proc A one 1 two v one 0 I ba Call Proc_A one 0 two I m Ww 113 5 Macro Statement A MacroDef is invoked in the pattern section through the Macro statement STIL s macro supports parameter passing as in the Procedure The Macro statement does not generate a physical test cycle and all the signal assignments are used for parameter passing The syntax of the Macro statement is Macro signal assignment Where signal assignment has syntax as signal ref WFC or WFC list Below is an example of a Macro statement MacroDefs Macro A v one 1 V one ff two V one 0 two H Pattern XXY W timing X V one 0 two H 1 17 XTOS Pattern User Manual P N 57010495 Rev
79. uld use WFC LHX to imply FM mode while L means strobe low H means strobe high and X means do not care The non scan signals just use 01 for drive cycle and LH for strobe cycle 4 Condition statement The scan operation can be defined as macro or procedure In the Macro case it should have a Condition C statement to define the default state of each signals The default states will provide scan signals padding WFC and broadside signals WFC Broadside signals pa_pin use the symbol to allow the passing of WFC per macro call 3 4 3 Scan Support 6 6 6 6 9 6 9 06 6 6 6 6 6 6 6 6 6 6 9 6 6 9 0 9 6 6 9 6 6 6 6 6 6 6 6 9 6 6 9 6 6 6 6 5 6 6 9 6 9 6 6 6 6 9 6 6 6 6 06 6 6 6 6 6 9 6 6 e 6 e 5 5 Shift statement The Shift statement defines the scan shift operation The means to apply to each one of the signals in the signal group The will consume scan shift data per scan length of each scan chain The compiler will pad each scan chain to the maximum length 6 Macro statement The Macro statement invokes the scan operation by expanding the macro all scans Notice the very first scan operation scan pat 0 only has scan input chain scan output chain is filled with X by the compiler The very last scan operation scan pat 3 only has scan output chain scan inputs are filled with 0 by the compiler The Macro statement also provides the static state of each broadside signal pa pin 34 2 Exampl
80. uses waveform character A and K to indicate that the corresponding signal is sourcing from an analog source C and J are used to indicate the corresponding signal is capturing for the current vector XTOS Pattern Compiler and Composite Linker 5 This chapter covers the pattern complier and the composite linker that accompany XTOS 5 Pattern Complier XTOS pattern compiler can be invoked from a Command Line Interface in a Command Prompt window The Command Line Interface for the pattern compiler is available for the Windows 2000 and Solaris operating systems 511 XTOS Pattern Complier Command Line Interface Windows 2000 The command line interface for the XTOS pattern compiler is located at XTOS release_numben bin CompileStil exe Compilation of a pattern in XTOS software results in a pattern object directory with the pattern object files to be used by various features that access the pattern data An example structure of a pattern object directory is Source file PAT1 STIL Upon compiling the above file a PAT1 pof directory is created with a vpr rpr Ipi and a text file containing the compiler statistics The first three files are binary objects used by the XTOS software while the fourth one is for the user s information Typing the compile command with the help parameter displays the following command usage for the pattern compiler usage XTOS release_number bin CompileStil exe options lt STILFileName gt Required Ar
81. y Division Street City State Zip or Country Phone Return Address USA Technical Publications Manager NPTest 150 Baytech Drive San Jose CA 95134 Fold here Fold here BUSINESS REPLY MAIL FIRST CLASS PERMIT NO 7698 SAN JOSE CA POSTAGE WILL BE PAID BY ADDRESSEE NPTest 150 BAYTECH DRIVE SAN JOSE CA 95134 Attn Technical Publications Manager NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES
82. y STIL Procedures without a NPTSubroutine attached are expanded as in lined vectors in the system s Main memory section This is a example of the correct Procedure with WaveformTable references and complete signal state assignments Procedure Proc A 1 13 XTOS Pattern User Manual P N 57010495 Rev 6 e o o 6 9 6 o 9 6 6 9 6 6 6 6 6 6 9 6 9 6 6 9 6 6 6 6 6 6 6 9 0 9 6 6 6 9 6 6 6 6 6 6 6 6 6 o eo 6 e 6 W timing X V one 1 two L v two H v Below is an improper Procedure it is missing WaveformTable references and has incomplete signal state assignments Procedure Proc A v one 1 v two H SS 112 MacroDefs The STIL MacroDefs block is an optional block The syntax of the MacroDefs block is MacroDefs optional macrodef block name macro name pattern statement n Each macro contains any combination of the STIL pattern statements such as Vector Condition and WaveformTable reference Macro is invoked through a Macro statement When a macro is called it maintains the state of the calling environment Only changes to the signal states such as different WFC for signals or different WaveformTable reference need to be specified in the macro A macro returns all changes back to the calling The Vector after the Call statement inherits the states from the macro Macro Macro A V one V two vi

Download Pdf Manuals

Related Search

Related Contents

128573 - Englisch_neu.qxp  APC NetShelter SX  LS-20M - Olympus  Compact NSX 100/630A Sistema ULP  Frymaster 35 Series Fryer User Manual  User's Manual  

Copyright © All rights reserved. Failed to retrieve file