comments

Document Sample
comments Powered By Docstoc
					Name              Category    Page   Subclause   Line   Comment                                 File

LEY, ADAM W       Editorial    20       6         1     The first line in sub-clause 6
                                                        includes the text "STIL0", which is
                                                        not defined.

LEY, ADAM W       Editorial    1        All       1     Please note that my comment
                                                        concerning use of "TRC
                                                        LANGUAGE" in the header applies
                                                        to all pages notwithstanding the
                                                        fact that the comment entry cites
                                                        page 1.
LEY, ADAM W       Editorial    1        All       1     The use of "TRC LANGUAGE" in
                                                        the page header doesn't seem
                                                        appropriate. I believe that the usual
                                                        convention is to spell out the full
                                                        name of the document across
                                                        facing pages starting from page 2.

LEY, ADAM W       General      1      front       2     In the document title, given in D14
                                      matter            as "P1450.3 - Standard for
                                                        Extensions to Standard Test
                                                        Interface Languge (STIL) (IEEE
                                                        Std. 1450-1999) for Tester Target
                                                        Specification", it seems improper
                                                        to cite the STIL.0 standard by year
                                                        of issue since the latest version
                                                        should apply.
SANTIAGO, JOSE M Technical     65                898    In Annex D.1, the 'Module'
                                                        statement is missing the module
                                                        name per the syntax.

SANTIAGO, JOSE M Technical     64                882    The 'PatternAttributes' statement
                                                        uses 'MaxVectors', which is old
                                                        syntax.

SANTIAGO, JOSE M Technical     63                       In the Annex D.2, the first
                                                        paragraph states "&The
                                                        PatternAttributes block is used to
                                                        define the MaxVectors &"
SANTIAGO, JOSE M Technical     59                763    In Annex B.1, the 'Module'
                                                        statement is missing the module
                                                        name per the syntax. The same is
                                                        true for line 766.
SANTIAGO, JOSE M Technical     50      17.2      691    The 'PatternAttributes' statement
                                                        uses 'MaxVectors', which is old
                                                        syntax.

SANTIAGO, JOSE M Technical     50      17.2             Should the 'LoopMatch' parameter
                                                        be 'Loop' based on syntax
SANTIAGO, JOSE M Technical   47   17.1   12   In the syntax for PatternAttributes,
                                              the 'MultiBitData' statement has
                                              the + sign and 'No' selected as
                                              default.

SANTIAGO, JOSE M Technical   47   17.1        Should the 'Loop' parameter be
                                              'LoopMatch' based on example


SANTIAGO, JOSE M Technical   47   17.1        There is no descriptions for any of
                                              the "instruction_enum" list of
                                              parameters

SANTIAGO, JOSE M Editorial   45   16.1        In the definition for syntax line
                                              number 1, the default option is not
                                              underlined.

SANTIAGO, JOSE M Editorial   43   15.1        In the definition for syntax line
                                              number 11, the default option is
                                              not underlined.

SANTIAGO, JOSE M Editorial   42   15.1        In the definition for syntax line
                                              number 6 through 10, the default
                                              option is not underlined.

SANTIAGO, JOSE M Technical   36   13.1   7    Why do we need two statements
                                              called 'NumberDCLevels' in this
                                              block?

SANTIAGO, JOSE M Editorial   34   12.1        In last paragraph, " (a)
                                              Synchronous: Signals&"


SANTIAGO, JOSE M Technical   34   12.1        In the definition for syntax line
                                              number (5) InOut, both 'InOnly' and
                                              'OutOnly' are not described




SANTIAGO, JOSE M Technical   33   12.1   4    In the syntax for SignalAttributes,
                                              the 'InOut' statement does not
                                              have 'Static' listed as an option but
                                              it is defined in page 34.

SANTIAGO, JOSE M Technical   33   12.1   4    In the syntax for SignalAttributes,
                                              the 'InOut' statement does not
                                              have a default selected from the
                                              group
SANTIAGO, JOSE M Technical   32   11.2   538   The 'PatternAttributes' statement
                                               uses 'MaxVectors', which is old
                                               syntax.

SANTIAGO, JOSE M Editorial   29   11           In last paragraph, " Constraints:
                                               This&"


SANTIAGO, JOSE M Technical   29   11     10    Should the MODULE_NAME be in
                                               parenthesis to make it optional


SANTIAGO, JOSE M General     27   10.1         In last paragraph, fix sentence
                                               "&tags may may be used &"


SANTIAGO, JOSE M Editorial   15   5.3          In the description for Note 8, The
                                               following sentences "The
                                               CompareStrobe & states." is
                                               invalid since the 'DriveState'
                                               statement are not used in
                                               example.




SANTIAGO, JOSE M Editorial   15   5.3          In the description for Note 6, The
                                               following sentence "The DriveState
                                               & states." is invalid since the
                                               'DriveState' statement is not used
                                               in example.
SANTIAGO, JOSE M Technical   15   5.3    214   The 'Module' statement is missing
                                               the module name per the syntax


SANTIAGO, JOSE M Technical   14   5.3    186   The first entry 'In' preceeding
                                               'RTO_FORMAT' does not match
                                               the syntax

SANTIAGO, JOSE M Technical   13   5.2    134   The 'PatternAttributes' statement
                                               uses 'MaxVectors', which is old
                                               syntax.

SANTIAGO, JOSE M Technical   11   5.2    79    The first entry 'In' preceeding
                                               'INTVC' does not match the syntax.
                                               Same is true for lines 87, 93, 100,
                                               108, 116, and 123 in pages 11-13.
SANTIAGO, JOSE M Technical   10   5.2   73   Multiple attributes used with
                                             'FormatSelect', only one must be
                                             selected

SANTIAGO, JOSE M Technical   9    5.1   37   The 'PatternAttributes' statement
                                             uses 'MaxVectors', which is old
                                             syntax.

SANTIAGO, JOSE M Technical   9    5.1   33   The 'PatternAttributes' statement
                                             uses 'MaxVectors', which is old
                                             syntax.

SANTIAGO, JOSE M Technical   9    5.1   21   The 'CompareEvents' statement
                                             uses 'Edge', which is invalid syntax


SANTIAGO, JOSE M Technical   8    4.3        In line starting with "Clause 17.2.
                                             "MAP_STRINGS" syntax and 17.3,
                                             &"

SANTIAGO, JOSE M Technical   8    4.3        In line starting with "Clause 17.
                                             Environment block &"


SANTIAGO, JOSE M Technical   8    4.3        In line starting with "Clause 10.
                                             Variable block &"


SANTIAGO, JOSE M Technical   8    4.3        In line starting with "Clause 8. STIL
                                             statement &"


SANTIAGO, JOSE M Technical   8    4.3        In line starting with "Clause 6.
                                             Expresions constructs &"


SANTIAGO, JOSE M Editorial   8    4.2        In last listing, "(e) In the tutorial
                                             (clause 5), bold numbers&"


SANTIAGO, JOSE M Editorial   7    4.1        In last paragraph, "&as identified in
                                             the list above (Clause 4).


SANTIAGO, JOSE M General     6    2          In 'IEEE Project.P1450.6'



SANTIAGO, JOSE M General     6    2          In 'IEEE Project.P1450.1'
TAYLOR, TONY   General     Comments have been submitted
                           for reviewers as follows:
                           JC = John Cosley
                           HK = Hirofumi Kamitokusari
                           GR = Gordon Robinson
TAYLOR, TONY   Technical   GR: Section 10.1 on Resouce ids
                           states that "the resouce id within
                           the angle bracket is a format as
                           required by the tester loader. The
                           following are all allowed formats for
                           resource id tags." Igonoring the
                           picky distinction
                           between "resource id" and
                           "resource id tag" I could take this
                           as implying either
                           1. Anything is allowed (as required
                           by the tester loader, but undefines
                           here)
                           2. Whatever is allowed must be
                           one of the following forms.


TAYLOR, TONY   Technical   GR: I believe that the section
                           (5.4.3) that states that using
                           InheritWaveformTable
                           is an implicit mechanism for
                           resouce assignment could be
                           considered to be
                           changing the existing 1450
                           meaning.
TAYLOR, TONY   Technical   GR: I still hate all of the "global and
                           named block merge rules",
                           particularly
                           when they get below "genuine top-
                           level" blocks.
TAYLOR, TONY   Editorial   GR: There are some obvious
                           "loosely specified parts" such as
                           where the
                           whole of "Mastering Regular
                           Expressions" syntax is included by
                           reference.
                           This contains some extremely
                           powerful and difficult to implement
                           features.
                           (Anyone thought what this implies
                           for STIL lexing? And how are
                           options
                           such as embedded whitespace in
                           regexes being handled? 'Nuff
                           said).
TAYLOR, TONY   Editorial   GR: I've abstained on this one,
                           because although I dislike
                           the document, I can't easily identify
                           specifics that I could
                           state in a no vote comment, and I
                           ended up feeling, "if that's
                           what the active crew want, good
                           luck to them implementing
                           it fully."
TAYLOR, TONY   Editorial   HK: (13) Underline to show default
                           (page 29)
                           The underline to show default is
                           given in syntax, but there is the
                           case that
                           underline is given and is not given
                           in the explanation of statement
                           after syntax,
                           For example:
                           page 29 : Constraints,
                           page 34 : Synchronous,
                           page 42 : Dynamic (6 place)
                           It is better to unify the description.

TAYLOR, TONY   Editorial   HK: (12)STIL0 (page 20)
                           STIL.0 is correct.


TAYLOR, TONY   Editorial   HK: (11) The description of (flow3),
                           (flow4) (page 15)
                           In other page( page 8,9 etc,), it is
                           described as flow(1). so it is better
                           to use the same description.
TAYLOR, TONY   Editorial   HK: (10) "per pin tester" and
                           "shared tester"
                           The distinction of "per pin tester"
                           and "shared tester" is necessary.

TAYLOR, TONY   Editorial   HK: (9)The sample description in
                           Subclause 5.2 (page 11)
                           The syntax for
                           WaveformDescriptions block
                           states "WFNAME", and the syntax
                           does not allow describing "In".
                           But the sample description in the
                           Tutorial (page 11) use "In".
                           If sample is not correct, please
                           correct.

TAYLOR, TONY   Editorial   HK: (8-2)
                           Macro statement must have one of
                           the option values. It is not allowed
                           to
                           describe Macro statement as
                           "Macro;", but it is explained that its
                           default
                           value is "WithParameters". The
                           same thing can be said for
                           ProcedureCalls
                           statement.
                           Is this syntax correct?
                           If syntax is not correct, please
                           correct.
TAYLOR, TONY   Editorial   HK: (8)The Macro and
                           ProceduresCalls in
                           PatternAttributes (pages 49-50)
                           (8-1)
                           In case "No" is selected for Macro
                           and ProcedureCalls statements
                           defined
                           in PatternAttributes block, and if
                           either Macro or Call is defined for
                           InstructionAttributes statement in
                           the same PatternAttributes block,
                           the interpretation of the test
                           patterns for Macro and Call
                           becomes unclear,
                           whether they are to be supported
                           or not. Also, if "Yes" or
                           "WithParameters"
                           is selected, and if Macro or Call is
                           not defined by the
                           InstructionAttributes
                           statement, its interpretation also
                           becomes unclear. The
                           specification should
                           have additional explanation for
                           such cases.

TAYLOR, TONY   Technical   HK: (7)The clock pins and scan
                           pins (page 33)
                           The constraints for number of
                           clock pins and scan pins is
                           necessary.
                           For example, the constraint that
                           limits the waveform types available
                           and availability of bi-directional
                           pins.



TAYLOR, TONY   Technical   HK: (6)The limit of test cycle for
                           multiclock (page 39)
                           The minimum cycle constraint for
                           cycles making one clock in
                           the multiclock waveform is
                           necessary.
TAYLOR, TONY   Technical   HK: (5)The instruction memory
                           (page 47)
                           The specification to define the
                           constraint of instruction memory
                           is necessary.




TAYLOR, TONY   Technical   HK: (4)The units (prefixes) that can
                           be used by testers (page 39)
                           The constraints of units (prefixes)
                           that can be used by testers is
                           necessary.
                           For example some testers have
                           the constraint that the time can be
                           specified in "ns" but not in "ps".
                           Not only time(second) but also
                           constrain of Ampere, Ohm, Volt
                           are
                           necessary.


TAYLOR, TONY   Technical   HK: (3)The number of nests and
                           pattern steps in Procedure (page
                           48)
                           The statement to define
                           constraints of number of nests and
                           maximum
                           steps is necessary to
                           ProcedureCalls block in
                           PatternAttributes block.
TAYLOR, TONY   Technical   HK: (2)The waveforms on-the-fly
                           (page 39)
                           The specification to define whether
                           user can use the waveforms
                           on-the-fly as the tester constraint is
                           necessary.
                           Because some testers cannot be
                           used by tester's constraint,
                           And some testers have constraints
                           on the types of waveforms
                           available after switching.
                           Therefore, the specification to
                           define
                           the combination of the waveform
                           type is also necessary.
TAYLOR, TONY   Technical   HK: (1)The minimum edge cycle in
                           a multiple cycle (page 46)
                           The specification to describe the
                           constraint of the intervals
                           of the drive edges (including the
                           case of strobe edges) between
                           the previous Vector pattern and
                           next Vector pattern is necesary.

TAYLOR, TONY   Editorial   JC: Annex B 2nd paragraph:
                           discussion here refers to using
                           Spec-Var and Spec-Cat for
                           handling Fluid specs. Then the
                           examples use ParamConstant,
                           ConfigConstant and Assert to
                           handle it.
TAYLOR, TONY   Editorial   JC: 18.1 p.52, (4) regular_expr,
                           should have brief definition here or
                           in Appendix.

TAYLOR, TONY   Technical   JC: 17.1 p.48: Don't agree with the
                           following defaults:
                           (6)
                           (b) MaxIteration = 1 (should be no
                           limit)
                           (c) MaxLength = 1 (should be no
                           limit)
                           (d) MaxNest = 1 (should be no limit
                           - also typo here 'MaxNext')
                           p.49 (7) should be (6)(i) then all
                           numbers after decrease by 1
                           (12) Ths -> This
TAYLOR, TONY   Technical   JC: 17.1 p.47: instruction_enum,
                           should it also include Vector in
                           instruction list?

TAYLOR, TONY   Editorial   JC: 13.1 p.36, (5): have many
                           acronyms, should we give more of
                           a definition here as to exactly what
                           they mean? some are obvious, but
                           others not.
TAYLOR, TONY   Editorial   JC: 11.2 p.31, line 526: should only
                           have 1 }


TAYLOR, TONY   Editorial   JC: 11.1 p.31, (18): spelling
                           DCResourceAttributes
TAYLOR, TONY   Editorial   JC: 11.1 p.30, (14), 4th line: is -> if



TAYLOR, TONY   Technical   JC: 11.1 p.29, line (15):
                           SignalAttributes should not have * -
                           per later description can only have
                           1. Actually I like the idea of having
                           multiple, perhaps change (15) on
                           page 30?
TAYLOR, TONY   Editorial   JC: 11. p.28, (c): 'SignalAttributes
                           Data Clock { }' is a syntax error
TAYLOR, TONY   Editorial   JC: 11. p.28, 2nd paragraph, last
                           sentence: does not make sense,
                           also should reference specific
                           section of document.
TAYLOR, TONY   Technical   JC: 7.5 (e): The rules for
                           application/merging of block
                           names are not consistent with
                           other STIL rules. Using 2 block
                           names should be OK and they get
                           merged, but no conflicts allowed.
                           For example, you can have
                           multiple InheritWaveformTable
                           statements (timing gets merged)
                           as long as they do not have
                           conflicting information, so why not
                           be able to have multiple named
                           PatternAttributes blocks be
                           merged in the same way?

TAYLOR, TONY   Editorial   JC: 6.1 P.20: shouldn't this list also
                           include Assert, ConfigConstant &
                           ParamConstant?

TAYLOR, TONY   Editorial   JC: 5.4.1 p.16, line 233: L3-x
                           should be quoted




TAYLOR, TONY   Editorial   JC: 5.2 page11-13: Figures are
                           confusing without any explanation
                           of what @@ and @ or t>10 mean.



TAYLOR, TONY   Editorial   JC: 2nd sentence: 'These numbers
                           are ... '
TAYLOR, TONY    Editorial             JC: 3.1 (same as above)



TAYLOR, TONY    Editorial             JC: 2.0 References: shouldn't we
                                      use 1450.1-2005 now?


WILDER, GREGG   Editorial   66        Shape: This term refers to the
                                      wave shape the is created


WILDER, GREGG   Editorial   51   18   Table 3



WILDER, GREGG   Editorial   49   10   Max: This statement specifies the
                                      minimum number of vectors (or the
                                      minimum

WILDER, GREGG   Editorial   49   8    Macro: This statement pecifies



WILDER, GREGG   Editorial   47   17   Table 3



WILDER, GREGG   Technical   46   9    NumberTimeSets




WILDER, GREGG   Editorial   45   6    NumberPeriods: complex shapes
                                      the encompass


WILDER, GREGG   Editorial   45   16   Table 3



WILDER, GREGG   Editorial   43   19   MinDrivePulse: Specify the
                                      minimum allowe


WILDER, GREGG   Editorial   40   15   Table 3
WILDER, GREGG   Editorial   39   6         TimeLimits: by the period
                                           generatoor


WILDER, GREGG   Editorial   36   13        Table 3




WILDER, GREGG   Editorial   34   12        Numbered comments don't match
                                           syntax


WILDER, GREGG   Editorial   32   11        Table 3



WILDER, GREGG   Editorial   30   9         MultipleSites: If this statement is
                                           omitted, the only


WILDER, GREGG   Editorial   30   8         MultipleDevices: If this statement is
                                           omitted, the only


WILDER, GREGG   Editorial   30   5         See clause B



WILDER, GREGG   Editorial   29   3         STILExtensions



WILDER, GREGG   Editorial   29   11        In the case were multiple blocks



WILDER, GREGG   Editorial   26   9    2    See clause B



WILDER, GREGG   Editorial   22   7    14   A TRC file that is to be used for the
                                           constraining


WILDER, GREGG   Editorial   15   5         There are two pragmas contained
                                           in this example.
WILDER, GREGG     Editorial   8    4   16   (see Clause C)



WILDER, GREGG     Editorial   8    4   7    (see Clause B)



WILDER, GREGG     Editorial   6    2        IEEE Project P1450.6



WILDER, GREGG     Editorial   6    2        IEEE Project P1450.1



WILDER, GREGG     Editorial   6        1    The variations in archetecture
                                            makes if


MASTON, GREGORY Editorial     73            last word first paragraph is
                                            misspelled


MASTON, GREGORY General                     I have a concern about how to
                                            identify or classify Signals into
                                            SignalAttributes blocks; does one
                                            take each Signal and identify ALL
                                            the SignalAttributes blocks that it
                                            passes, and then start taking sets
                                            of Signals that pass each block
                                            and running checks given this
                                            number of signals? This strategy is
                                            not deterministnc, and is likely to
                                            end up with implementations of
                                            TRC behavior that do not behave
                                            the same way. Which at the root
                                            says the spec is incomplete
                                            because of the potential to
                                            interpret the same STIL data
                                            against the same TRC in different
                                            ways.

MASTON, GREGORY Editorial     56            "ESSM" : is this trade-marked?
MASTON, GREGORY Editorial   56          "on-the-fly" definition says "see
                                        also "static", but "static" carries the
                                        opposite meaning

MASTON, GREGORY Technical   50   17.1   bullet (16) NumVecPerShift: is this
                                        the unrolled number of vectors
                                        (dependent on the data passed
                                        into the Shift), or the number of V
                                        statements contained in the Shift
                                        block? Note that a STIL to WGL
                                        translator is constrained to 1
                                        Vector in the Shift block to map to
                                        the WGL scan statement.

MASTON, GREGORY Technical   50   17.1   bullet (10) Max < Loc | Vec > says
                                        the statement identifies the
                                        minimum number of vectors.

MASTON, GREGORY Editorial   47   16.1   bullet (8) says "comples"



MASTON, GREGORY Technical               Is the PatternAttributes the only
                                        block that allows multiple
                                        references to named blocks and
                                        merges unnamed blocks? All other
                                        blocks (PeriodAttributes,
                                        SignalAttributes, and
                                        WaveformAttributes) appear to
                                        only allow a single reference which
                                        replaces the unnamed block - as
                                        least according to the description
                                        on pg 31. In this case, clause 7.5
                                        should be made clear that it affects
                                        only the PatternAttributes block,
                                        and it should be identified that this
                                        block scoping does not apply to
                                        these other blocks. Or the other
                                        blocks need to have similar
                                        scoping support as to the
                                        PatternAttributes.

MASTON, GREGORY Technical   31   11.1   bullet (13) says "there may be
                                        multiple global". I am confused by
                                        the context of "multiple global"
                                        here; this statement references
                                        named blocks and the pertinence
                                        of global (unnamed) blocks is
                                        questionable for interpreting this
                                        statement.
MASTON, GREGORY Technical   29   11     bullet (c) and (d) reference "Data"
                                        and "Clock" constructs that I think
                                        were removed from this spec

MASTON, GREGORY Technical   29   11     bullet (d) says "any of the
                                        conditions may be met". Does this
                                        mean that in the example that
                                        follows, that if the conditions on
                                        SignalAttributes Data are met, but
                                        not the attributes on
                                        SignalAttributes Clock, that the test
                                        passes?
MASTON, GREGORY Editorial   29   11     bullet (b), "for all intent and
                                        purpose" is wordy


MASTON, GREGORY Editorial   29   11     bullet (a), the Note is confusing
                                        because it doesn't identify what it
                                        pertains to.

MASTON, GREGORY Editorial   29   11     last sentence second paragraph I
                                        think cites the wrong reference


MASTON, GREGORY Technical   29   11     last sentence first paragraph
                                        identifies a key piece of processing
                                        functionality that requires
                                        elaboration/clarification. The term
                                        "to choose" is too weak here.


MASTON, GREGORY Technical   29   10.1   end of section, options (b) and (c):
                                        why not just use the definition of a
                                        STIL username as defined in dot0?

MASTON, GREGORY Technical   27   9.1    last word on (2) and (3) is "engr
                                        unit". This term is not defined



MASTON, GREGORY Technical   27   9.1    third sentence on Assert - "the
                                        application is expected to report an
                                        error". This is actually a
                                        REQUIREMENT of this standard,
                                        not an expectation.
MASTON, GREGORY Editorial   27   9.1   first sentence on Assert - "result -
                                       TRUE". The "-" makes this look
                                       like "not TRUE"




MASTON, GREGORY Editorial   27   9.1   first sentence on Assert - "that
                                       when executed is expected" is
                                       wordy.

MASTON, GREGORY Editorial   27   9     last paragraph "Assert statement is
                                       a tool that allows for the" is wordy
                                       and vague.

MASTON, GREGORY Editorial   27   9     paragraph at top of page&.
                                       Another reference to the infamous
                                       clause B

MASTON, GREGORY Technical   26   9     definition of "fluid constraints" as
                                       "defines sets of things may be
                                       varied or adjusted" is not really
                                       accurate. Variables, by definition,
                                       are variable, and fit in this
                                       definition. But the notion of fluidity
                                       is that there is a SET AMOUNT of
                                       some resource that may be shared
                                       or allocated between multiple uses.
                                       It's fluid because there is a set
                                       amount and you can't overshare
                                       that amount (the amount is not
                                       expandable or compressible ... like
                                       a fluid...)

MASTON, GREGORY Technical   26   8     EXT_NAME in point (2) is not
                                       present in the syntax


MASTON, GREGORY Technical   26   8     Definition of EXT_VERSION needs
                                       to change to be "2006" and
                                       parenthetical sentence removed

MASTON, GREGORY Technical   25   7.5   Example (e) is not a rule and will
                                       cause usage problems
MASTON, GREGORY Technical   25   7.5   Example (a) indicates that in the
                                       named TRC block, both
                                       SignalAttribute blocks from the
                                       unnamed TRC block are applied..
                                       However example (b) indicates
                                       that if there are additional named
                                       SignalAttribute blocks in the
                                       named TRC block, these blocks
                                       are merged to the unnamed blocks
                                       on a conditional basis. This is
                                       inconsistent.



MASTON, GREGORY Technical   24   7.5   first paragraph, second sentence
                                       "It may contain global (unnamed)
                                       blocks". The plural "blocks" implies
                                       to me that there may be multiple of
                                       the same type of unnamed block,
                                       which I do not believe is supported.

MASTON, GREGORY General                several references are made to
                                       IEEE Std 1450-1450-1999, or 1450-
                                       1999, *and* to the defined
                                       reference STIL.0
MASTON, GREGORY Editorial   22   7     Table 3 identifies new terms
                                       "Constraint", "Report", Target" and
                                       "Load", which appear to map to the
                                       prior references of Flow (1) - (4). In
                                       the footnote section it would be
                                       nice to correlate these new terms
                                       with the prior flows, or identify how
                                       they do not match.
MASTON, GREGORY Editorial   14   5.3   first paragraph, last word is
                                       redundant


MASTON, GREGORY Technical   11   5.2   STIL code fragment contains "STIL
                                       1.0 { Design 2005; TRC D12; }"
                                       TRC D12 is incorrect




MASTON, GREGORY Editorial   10   5.1   Note3 says "If according"& (twice)



MASTON, GREGORY Editorial   10   5.1   Note2 says "output compare can
                                       be Compare&
MASTON, GREGORY Editorial   10   5.1   Note1 contains the phrase "calls
                                       out", which is somewhat idiomatic


MASTON, GREGORY Editorial   9    5.1   Remove quotes around "simple" in
                                       the clause title


MASTON, GREGORY General                All STIL fragments contain a
                                       source comment that needs to be
                                       modified for the final version of the
                                       doc
MASTON, GREGORY Editorial   9    5     The first paragraph introduces the
                                       different flow, and different effects
                                       on STIL files. But it doesn't identify
                                       WHY this is being stated here.




MASTON, GREGORY Editorial   9    5     First paragraph, sentence starts
                                       "The (2) and (4)&" is confusing




MASTON, GREGORY Editorial   9    4.3   First and third bullets reference
                                       "clause B", 5th bullet references
                                       "clause C". Clauses are numbered;
                                       what is the reference here?

MASTON, GREGORY Technical   7    1.3   The reference to the 80/20 rule -
                                       the interpretation of this rule "this
                                       standard provides 80% of the TRC
                                       info by defining 20% of the rules" is
                                       not standard. Normally 80/20
                                       refers to a total of 100% of
                                       something - that the amount of
                                       effort it takes to define 80% of the
                                       issues is equivalent to the amount
                                       of effort necessary to define the
                                       remaining 20%.
MASTON, GREGORY Editorial   5   1   First 2 sentences in overview are
                                    stilted




MASTON, GREGORY General     2       "code used for edits to this doc"
                                    and table 1 need to be removed


SAYOGO, BARTIEN   General           The title should be revised: IEEE
                                    Std for Standard Test Interfase
                                    Language (STIL) - Part 3: Tester
                                    Target Specification.
                                    In 3.1 Definitions:
                                    The text should be revised:
                                    STIL.3 Refers to IEEE Std. 1450.3
                                    (i.e this standard). The extention of
                                    the STIL base standard is
                                    commonly referred to as "dot 3":
                                    Tester target specification.
                                    (Note: For STIL.1, STIL.2 etc. the
                                    title should follow as above).

MICEK, TOM        General           In review
                                    Tom Micek
                                    Freescale
Must Be Proposed Change                             Resolution
Satisfied                                            Status
  No      Replace with "STIL.0".                     DONE



  No      Change header on all pages.                DONE




  No      For the draft, use "DRAFT                  DONE
          STANDARD FOR EXTENSIONS TO
          STANDARD TEST INTERFACE
          LANGUAGE (STIL) (IEEE STD 1450)
          FOR TESTER TARGET
          SPECIFICATION".

  No      Omit the year of issue for STIL.0 from     DONE
          the title such that the new title reads
          "P1450.3 - Standard for Extensions to
          Standard Test Interface Languge
          (STIL) (IEEE Std 1450) for Tester
          Target Specification".



  No      Add module name after 'Module'             DONE



  No      Change it to 'Max Vectors' per syntax      DONE



  No      Since 'MaxVectors' is not valid syntax,    DONE
          change to "&define the maximum
          number of vectors &"

  No      Add module name after 'Module'             DONE



  No      Change it to 'Max Vectors' per syntax      DONE



  No      Correct syntax or example                  DONE
No   Remove the + sign from the syntax,       DONE
     since the description does not have it
     and it is inconsistent.


No   Correct syntax or example                DONE



No   Add detailed descriptions                DONE



No   Underline 'Rule' since it is a default   DONE
     attribute for 1.


No   Underline 'Dynamic' since it is a        DONE
     default attribute for 11.


No   Underline 'Dynamic' since it is a        DONE
     default attribute for 6 through 10.


No   These statements should be combined      DONE



No   Underline 'Synchronous' since it is a    DONE
     default attribute


No   Add descriptions for 'InOnly' and        DONE
     'OutOnly'.




No   Add 'Static' to the list of options.     DONE




No   Suggest to make "WithinCycle" the        DONE
     default
No   Change it to 'Max Vectors' per syntax   DONE



No   Underline 'Constraints' since it is a   DONE
     default attribute


No   Consider making the MODULE_NAME         DONE
     optional


No   Change to "&tags may be used&"          DONE



No   Remove sentences                        DONE




No   Remove sentence                         DONE




No   Add module name after 'Module'          DONE



No   Need to remove the 'In' word.           DONE



No   Change it to 'Max Vectors' per syntax   DONE



No   Need to remove all invalid words        DONE
No   Change from 'In Out' to 'InOut' or &?    DONE



No   Change it to 'Max Vectors' per syntax    DONE



No   Change it to 'Max Vectors' per syntax    DONE



No   Remove 'Edge' from example.              DONE



No   Change '17.2' and '17.3' to '18.2' and   DONE
     '18.3' respectively


No   Change '17' to '18'                      DONE



No   Change '10' to '9'                       DONE



No   Change '8' to '7'                        DONE



No   Change '6' to '5'                        DONE



No   Replace 'bold' with 'circled'.           DONE



No   Remove (Clause 4). This is unclear.      DONE



No   Change 'Project' to 'Std.'               DONE



No   Change 'Project' to 'Std.'               DONE
No   NO-CHG




No   DONE




No   DONE




No   DONE
No   DONE




No   NO-CHG




No   DONE




No   DONE



No   DONE
No   DONE




No   DONE




No   DONE
No   DONE




No   DONE




No   NO-CHG
No   DONE




No   DONE




No   NO-CHG




No   NO-CHG
No   DONE




No   DONE




No   DONE



No   DONE




No   NO-CHG



No   NO-CHG




No   DONE



No   DONE
No   DONE



No   DONE




No   DONE


No   DONE



No   DONE




No   DONE



No   DONE




No   DONE




No   DONE
No                                           DONE



No                                           DONE



No   This term refers to the wave shape      DONE
     that is created


No   Add Length from 18.1                    DONE



No   This statement specifies the maximum    DONE
     number of vectors (or the maximum


No   This statement specifies                DONE



No   Add Base, MinAfter, MinBefore,          DONE
     Infinite, Modulus, Macro, Max,
     VectorCompression from 17.1

No   This definition doesn't seem right to   DONE
     me. From Annex E, it looks like this
     should be something about indirect
     memory. Or at least it should be
     different from the definition of
     NumberShapes.
No   Complex shapes that encompass           DONE



No   Add NumberSignals from 16.1             DONE



No   Specify the minimum allowed             DONE



No   Add MinCompareToDriveOn,                DONE
     MinDriveOffToCompare from 15.1
No   By the period generator                   DONE



No   Add PerPinConfiguration,                  DONE
     DifferentialConfiguration,
     NumberTesterChannels, DCLimits,
     NumberLevels, NumberDCLevels
     from 13.1
No   For example, FanOut is 3 in syntax, 4     DONE
     in comments


No   Add AllowedScanPadWaveforms,              DONE
     InOut, DCResourceAttributes,
     UndrivenInOut from 12.1

No   If this statement is omitted, then only   DONE



No   If this statement is omitted, then only   DONE



No   See Annex B                               DONE



No   Define extensions: eg, Design is for      DONE
     1450.1, etc


No   In the case where multiple blocks         DONE



No   See Annex B                               DONE



No   A TRC file that is to be used for         DONE
     constraining


No   Add (refer to Clause 19 of 1450.1 for     DONE
     definition of pragma)
No   (see Annex C)                             DONE



No   (see Annex B)                             DONE



No   IEEE Std. 1450.6-2005                     DONE



No   IEEE Std. 1450.1-2005 for                 DONE
     Semiconductor Design Environments


No   Change archetecture to architecture; if   DONE
     to it


No   helpful has 1 ell                         DONE



No   Augment the spec to identify how to       DONE
     "match" a STIL file into a set of TRC
     constructs.




No   Check we are not treading on              DONE
     something. Google has some great
     hits here: Emergency Ship Salvage
     Material, Evolved Sea Sparrow
     Missile, and the European Society for
     Sexual Medicine.
No   Change "see also" to "contrast with".       DONE
     Likewise on the definition of "static"


No   Clarify definition: both quantities may     DONE
     be important.




No   Either change the statement to Min <        DONE
     Vec | Loc > or change the
     explanation&.

No   change to "complex"                         DONE



No   A uniform scoping rule across all           DONE
     blocks needs to be established.
     Different rules for each type of block is
     not a good definition.




No   remove the reference to "multiple           DONE
     global", or if necessary to indicate
     potential of global blocks then add a
     separate sentence "Global (unnamed)
     blocks may also be present and
     included based on the handling
     presented in clause 7.5".
No   Change examples to something               DONE
     current


No   It is not an OR, but rather a logical      DONE
     combination of the checks for EACH
     block that needs to be performed. This
     statement needs to be reworded




No   remove "that for all intent and            DONE
     purpose"


No   Try: "(Note: optional statements are       DONE
     identified by parenthesis under the
     syntax definitions.)"

No   Change last sentence to "See clause        DONE
     7.5 for information about block
     sharing&"

No   Replace the last sentence with: "When      DONE
     a TRC file contains multiple TRC
     blocks, the application processing that
     file may process all blocks present or
     specify which blocks to apply,
     depending on the application."

No   replace (b) and (c) with: (b) STIL user-   DONE
     defined name (STIL.0 clause 6.8).


No   Either define "engr unit" or change        DONE
     wording to something like "constant
     expression", might need to reference
     dot1 here for completeness.

No   Change "the application shall report       DONE
     this failure to satisfy this statement".
     Remove the next sentence starting
     with "If the result is TRUE" -- we don't
     care and should not constrain an
     application from returning information
     about non-violated asserts if it so
     chooses.
No   Remove the dash, change wording.          DONE
     Lets start the whole sentence over
     again. "The Assert statement contains
     a boolean expression that is expected
     to be TRUE in order for the rules
     checking to pass successfully."

No   Remove "when executed", redundant.        DONE



No   Try "the Assert statement (defined        DONE
     below) allows for the &"


No   Change clause B to something              DONE
     appropriate.. Is this supposed to be
     Annex B??? There are multiple
     occurrences of this situation.
No   Reword the definition of fluid            DONE
     constraints. Try" fluid constraints are
     used in this standard to define how a
     set amount of a resource may be
     allocated or shared between multiple
     uses of that resource. Each use may
     require different amounts of that
     resource, and there is an identified
     limit to the amount of that resource
     available."




No   Eliminate the term "ext_name" here        DONE
     and change to be TRC, change
     wording in (2) appropriately.

No   Change EXT_VERSION to be 2006             DONE
     and eliminate parenthetical sentence


No   Eliminate the "choice" here - if both     DONE
     named blocks are referenced, then
     why are they not merged together and
     both used?
No   If rule (a) is applied uniformly, all      DONE
     blocks whether named or unnamed
     from an unnamed TRC block will be
     applied to all other named TRC blocks
     and merged across all blocks of the
     same type uniformly and not based on
     names. The alternate solution is to
     merge only unnamed blocks from the
     unnamed TRC section uniformly, and
     require a mechanism to reference
     named blocks form the unnamed TRC
     block if those attributes are also to be
     merged.

No   Clarify reference - "It may contain an     DONE
     unnamed instance of a block used to
     define global information."




No   Replace all occurrences of 1450-1999       DONE
     and other forms with "STIL.0"


No   Add info to the terminology footnotes      DONE
     on table 3, to relate back to the flows,
     and/or rename the flows using these
     terms in the earlier part of the
     document, for consistent referencing.



No   Try: "...Annex E of IEEE Std. 1450-        DONE
     1999." (remove "standard")


No   Change all occurrences of "TRC D12"        NO-CHG
     (or any other draft reference) to TRC
     2006;




No   Try "If applied according"&                DONE



No   Try: Supported Output measure              DONE
     operations are identified to be
     Compare&
No   replace all occurrences of "calls out"      DONE
     with "identifies"


No   same                                        DONE



No   Revise the Source annotation to             NO-CHG
     indicate IEEE Std 1450.3, no draft
     number, and remove the date.

No   Add another paragraph here, and             DONE
     identify of the following clauses what
     flows are being supported. Try: Clause
     5.1 and 5.2 represent standalone TRC
     files usable for flows (3) and (4),
     clause 5.3 presents a pattern report
     generated for flows (2) and (4), and
     clause 5.4 represents test resource
     identification per flows (2) and (4).

No   Try: "Flows (2) and (4) result in data      DONE
     resident in the corresponding STIL file
     while flows (1) and (3) identify usage
     models that rely on separate STIL files
     to contain the TRC information."

No   Correct clause references                   DONE




No   I think what is being stated here is that   DONE
     this standard is intended to address
     80% of the issues involved with TRC
     operations, because the effort to
     address the remaining 20% is too
     complex and would make the standard
     unwieldy to apply in general.
No   Try: The STIL Environment supports       DONE
     transferring tester independent test
     programs to a specific ATE system.
     While native STIL data is tester
     independent, the actual process of
     mapping the test program onto tester
     resources may be critical, and it is
     important to be able to completely and
     unambiguously specify how the STIL
     programs and patterns are mapped
     onto the tester resources.

No   remove these two                         DONE



No                                            DONE




No                                            NO-CHG
Resolution Detail (last updated - Nov 11, 2006)          Other1   Other2   Other3

oct 1 - changed



oct 1 - changed see also next item




oct 1 - changed. However, I could not get all the
suggested words into the header. The IEEE editor
may want to alter it again after it is approved by the
ballotters



oct 1 - The date identifier - "1999" has been
removed from the title. Note: This, however,
conflicts with the requirement to be consistent with
the title in the PAR. IEEE will have final contol over
the title after ballot approval.




oct 1 - added module name



oct 1 - changed to "Max Locations". Did
search/replace over whole doc. Removed
MaxVectors from keyword list - Table 3.

oct 1 - changed



oct 1 - changed



oct 1 - changed



oct 2 - item 11, 13 are related
changed to MatchLoop. Note: There is already a
block for general "Loop" attributes.
oct 2 - removed parens and + sign.




oct 2 - item 11, 13 are related.
See item ll for comment


oct 2 - added description for the enum list



oct 2 - changed



oct 2 - changed



oct 2 - changed



oct 2 - changed



oct 2 - changed



oct 2 - changed
- Also added keywork "Static" to the syntax.
- Also removed the note which applied to syntax
that has been removed - "Note that whereas the
In/Out specification on the top level
SignalAttributes block specifies the basic ability to
either drive or compare, this statement specifies
when the in/out switching may occur."
oct 2 - changed




oct 2 - changed as suggested
oct 2 - changed



oct 2 - changed



oct 2 - The module name has been made optional



oct 2 - changed



oct 4 - other questions are raised by this ex:
- p41; DriveEvents L H L/H 2 1; are the single
event defs reqd? same for CompareEvents.
- p41; the 1st integer expr is optional with a default
of 1; for both DriveEvents and Compare/Events.
- compare states should be h/l/x for window
- CompareStrobe and CompareState stmts
removed; now part of the referenced
WaveformAttributes
- Note: now Annex F

oct 4 - stmt removed; now defined in the
referenced WaveformAttributes stmt.



oct 4 - changed; see also item 25



oct 4 - changed



oct 4 - changed



oct 4 - changed
oct 9 - changed



oct 9 - changed to Max Locations



oct 9 - changed to Max Locations



oct 9 - changed



oct 9 - changed



oct 9 - changed



oct 9 - changed



oct 9 - changed



oct 9 - changed



oct 9 - changed



oct 9 - changed



oct 9 - changed



oct 9 - changed
No change required




oct 9 - changed




sep 29 - This clause does not change any syntax
or interpretation as defined in dot0. It is only an
example of the application of existing syntax. As
proposed by IEEE editors, and to aviod this kind of
mis-interpretation, all of the examples in the tutorial
section (clause 5) have been moved to the Annex.


sep 29 - similar issues = 49-GR, 77-JC, 118-GM,
119-GM, 137-GM, 138-GM. The following changes
have been made:
1) remove subclause 7.5; the following changes
are to make scoping explicit
2) disallow multiple PatternAttr, SignalAttr
statements
3) allow multiple names on a PatternAttr statement
to allow "OR"ing
4) add Inherit statements to provide "AND"ing
5) for consistence the Inherit statement is added to
clauses 12 .. 17.
oct 17 - a new annex has been created that
provides a reference to documentation on regular
expressions and also reference to the GNU library
that can be built in to a STIL reader to implement
regular expressions.




No change required




oct 9 - changed




oct 9 - changed



oct 9 - uniformly changed to reference as "flow #";
no parens used.
oct 9 - added "shared resource architecture" to
Annex A; also added reference in "per pin
architecture in Annex A.


oct 10 - example corrected




oct 10 - The general rule is that if a statement is
omitted then that condition is not checked. In this
case if there is no Macro statement, then all
manner of macros with parameters are allowed.
Hence the default, if no statement, is
"WithParameters". The same thing applies to
ProcedureCalls. The explanation has been
expanded to clarify this point.
oct 10 - see item 57




oct 10 - The technique for defining the number of
pins allowed with a given set of attributes is to
define separate SignalAttributes blocks and use
the MaxSignals statement in each block to define
the limits.
A SignalAttributes statement within a Module block
may now contain multiple names.
The Inherit statement has been added to allow for
common attributes to be identified in a common
block.

Related items - 59-HK, 74-JC
oct 10 - No change to the syntax is required. There
are two ways of constraining the number of multi-
clocks. The DriveEvents statement can specify the
number of edges allowed. Or a multi-clock can be
defined using sub-waveforms; in which case the
ReplicateSubWaveforms defines the constraint.
oct 10 - The technique for constraining instruction
memory is to define a PatternAttributes block for
each type of pattern generation instrument in a
system. Each instrument should have its own set of
constraints. The Module block can select which of
the PatternAttributes blocks are allowed.
The PatternAttributes statement has been changed
to allow reference to multiple names.

oct 28 - added new statemement to define allowed
units - TRC -> Units




oct 10 - No change required. The technique to limit
nesting is to use the InstructionAttributes
statement. This allows the MaxNest to be specified
for each type of statement - Macro, Call, Loop, etc.




oct 28 - No change required.

This capability is provided by the stmt: MaxShapes,
MaxTimeSets, etc. These statements allow to
define either Dynamic (i.e., on-the-fly) or Static.
Also allow to specify the number of waveforms
allowed.
oct 10 - Enhance description
- Added definition of allowed time expr syntax in
WaveformDescriptions -> Shape with references to
the dot0 and dot1 allowed syntax. Added an
example of a two cycle waveform
- The WaveformAttributes -> MinEdgeReTrigger
allows to specify the timing constraint on drive and
compare edges from one vector to the next.

oct 10 - The intro paragraphs to Annex B have
been re-worded.




oct 10 - see item 50



oct 10 - Changes made as sugggested.
1) Note: Having no limit is consistent with the
general rule in clause 11 which states that if a
statement is omitted, then no checking is done -
hence these parameters become unlimited.
2) typo and clause numbering corrected




oct 10 - Upon further investigation by the
commenter it was decided that no change is
required.

oct 10 - No change required. All the DCResource
acronyms are defined in dot2. Dot2 is referenced in
both clause 13.1 and in clause 2.


oct 10 - changed



oct 10 - changed
oct 10 - changed



oct 10 -

Related items - 59-HK, 74-JC



oct 10 - see 49-GR.


oct 10 - changed



sep 29 - similar issues: 49-GR, 77-JC, 118-GM,
119-GM, 137-GM, 138-GM




oct 10 - changed



oct 10 - changed

Note: double quotes have been added for
consistency. However they are not required by this
standard since they are within the Pragma.

oct 10 - changed

Note: The definition of this syntax is in dot1, so a
reference to dot1 has been added to the beginning
of this Annex.

oct 10 - changed
oct 10 - changed



oct 10 - changed



oct 17 - changed



oct 17 - changed

Note: Moved table 3 to clause 6.

oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 17 - changed




oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 17 - changed
oct 17 - changed



oct 17 - changed




oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 17 - changed
oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 17 - changed



oct 30 - minor syntax enhancement

It is recognized that when a TRC is used for the
purpose of contraining a flow that there may be
multiple solutions that are difficult to resolve.

Unfortunately, it is the nature of most ATE systems
to have multiple resources that are capable of
addressing a particular need - signals, pattern
memories, etc.

Either the user must create a simple sub-set of the
TRC or else it is the application's responsibility to
resolve the resource usage issues.

Added additional, optional fields to the Variables ->
ConfigConstant statement with
ALT_CONFIG_NAME(s)

oct 4 - removed the acronym and used the full term
wherever it is needed - "Event Sequence Store
Memory"
oct 20 - changed. Also made same chage to the
definition of "static".


oct 20 - changed




oct 20 - changed



oct 20 - changed



sep 29 - similar issues: 49-GR, 77-JC, 118-GM,
119-GM, 137-GM, 138-GM




sep 29 - similar issues: 49-GR, 77-JC, 118-GM,
119-GM, 137-GM, 138-GM
oct 20 - bullet c, d are removed. Or-ing is now
explicite in the statements that allow it. And-ing is
done by use of Inherit.

oct 20 - see item 120




oct 20 - changed



oct 20 - changed



oct 20 - changed



oct 20 - changed




oct 20 - changed



oct 20 - changed - reference made to dot1, clause
5.7 and 5.9



oct 20 - changed
oct 20 - changed




oct 20 - changed



oct 20 - changed



oct 20 - changed



oct 20 - changed




oct 20 - changed



oct 20 - changed



oct 20 - this subclause (7.5) has been removed
sep 29 - similar issues: 49-GR, 77-JC, 118-GM,
119-GM, 137-GM, 138-GM




sep 29 - similar issues: 49-GR, 77-JC, 118-GM,
119-GM, 137-GM, 138-GM




oct 20 - changed



oct 28
- Table 3 is just a list of keywords used throughout
dot3.
- References have been added in Annex A,
glossary - constraint, tester targeting, usage model.
- Note that Table 3 has moved to clause 6 and is
now Table 2

oct 28 - changed



oct 28 - this is a variable that will be changed to the
"official" wording when the final editing is done after
ballot. Note the the same variable also appears on
page 1 (immediately after the title) and on the top
of every page.
- BTW, it is D14 in the ballot draft. Are you
reviewing an earlier draft?
oct 28 - changed



oct 28 - changed
oct 28 - changed



oct 28 - changed



oct 28 - see item 142



oct 28 - changed

- The turorial has now been moved to the Annex
and each has an intro that defines the purpose and
references the flow in fig 1.




oct 28 - see item 148




oct 28 - changed




oct 28 - changed wording as proposed
oct 28 - changed wording as proposed




oct 28 - changed - Note I think you may have been
reviewing an earlier draft. It is gone in D14.


oct 28 -

- The title has been changed per instruction from
IEEE editors

- changes made to the definitions in 3.1
INSTRUCTIONS: Use this form to enter your comments. When complete, save the file on your hard drive and upload the file into the comment submission area.

Category - This field is optional but if you leave blank, the system will automatically populate with General. If you enter Technical or Editorial, spell out completely or the
upload will be invalidated.

Page/Sub-clause/Line Number - These fields are optional. Any data entered must be integers only. No alpha characters or symbols -- doing so will result in an error and
the upload will be invalidated. If you wish to reference multiple pages, provide the details in the comment field.

Comment/Proposed Change - These fields are required. Enter your comment and proposed change in these fields, respectively. Use plain text characters only. If you use
any characters entered with "Crtl" or "Alt" keys; or if you use symbols of any kind, if will result in an error and the upload will be invalidated.

Must be Satisfied? - This field is required. Enter Yes or No and spell out completely or the upload will be invalidated. If you have already voted Negative (Disapprove), the
data will be associated with your Negative (Disapprove) vote. This categorization is used to differentiate those comments submitted as part of your Negative (Disapprove)
vote from other comments that you may wish to submit. Only those comments that have a "Yes" in the "Must be Satisfied" box will be considered as part of your negative
vote. If you have already voted Affirmative (Approve), the Must Be Satisfied data will not be used by the system. If you have not yet voted, the data will be stored by the
Category       Page Sub-clause                                      Line # Comment                                                                                                          Resolution Resolution Detail (last updated - oct 28, 2006)
                                                                                                                                                                                             Status
Technical         46 16. TRC – WaveformDescription                        29 1. Problem that the specification to define the minimum edge cycle in a multiple cycle is missed                DONE oct 28 - see ballot comment #65
                        16.1 TRC – WaveformDescription –syntax
                         (10) Shape                                          • Problem and Request
                                                                             For input and output waveforms, the D14 specification allows to describe the constraints of the edge
                                                                             intervals for the waveforms defined by Waveforms (the sample description showed in Subclause 5.2 in
                                                                             p.10); however, for the waveform used to run a Vector pattern, the specification to describe the
                                                                             constraint of the intervals of the drive edges (including the case of strobe edges) between the previous
                                                                             Vector pattern and next Vector pattern is not found. It should be added in the specification.

Technical         39 15. TRC – WaveformAttributes                            2. Problem of missing the specification to define whether user can use waveforms on-the-fly by the             NO-CHG oct 28 - No change required.
                        15.1 TRC – WaveformAttibutes –syntax                 tester constraints
                                                                                                                                                                                                       See ballot comment #64
                                                                             • Problem and Request
                                                                             The specification to define whether user can use the waveforms on-the-fly as the tester constraint is
                                                                             necessary. When verifying whether the test pattern can be used in STIL by a tester or not, in case that
                                                                             a waveform is executed on-the-fly in a pattern, sometimes it cannot be used because of the tester’s
                                                                             constraint, the statement to indicate whether a tester has such constraint should be added.
                                                                             Also, if a tester allows using waveforms on-the-fly, some testers have constraints on the types of
                                                                             waveforms available after switching. Therefore, the specification to define the combination of the
                                                                             waveform type should also be added.
Technical         48 17. TRC – PatternAttributes                             3. Problem of missing specification to define constraints of number of nests and pattern steps in              NO-CHG oct 28 - No change required.
                        17.1 TRC – PatternAttributes –syntax                 Procedure
                         (6) LoopAttributes                                                                                                                                                            To specify the max nest for a procedure:
                                                                             • Problem and Request                                                                                                       InstructionAttributes Call {
                                                                             PatternAttributes block has a specification to describe the constraints of number of Loop block nests                         LoopAttributes {
                                                                             and pattern steps, but there is no statement to define the constraints of number of Procedure block                             MaxLength 100;
                                                                             nests and pattern steps. Testers have constraints for running patterns of Procedure block; therefore, at                        MaxNest 5;
                                                                             least a statement to define constraints of number of nests and maximum steps is required, and should                          }
Technical         39 15. TRC – WaveformAttributes                            4. Problem of missing the specification to define the constraints of units (prefixes) that can be used by        DONE     oct 28 - added new statemement to define
                        15.1 TRC – WaveformAttibutes –syntax                 testers                                                                                                                   allowed units - TRC -> Units

                                                                             • Problem and Request                                                                                                     - see item 62 of main comments
                                                                             Some testers have constraints for prefix of unit time that can be used. That is the constraint that the
                                                                             time can be specified in “ns” but not in “ps”. For example, it can be specified as in 0.1ns, but not as in
                                                                             100ps.
                                                                             Even if some testers have constraints to refrain from using ps time unit, it shall meet the constraint if
                                                                             the test pattern converts the ps notation to ns notation in the Timing description and fulfills the time
                                                                             range supported by the tester. Therefore, if a specification to define the prefix of the unit time to be
Technical         47 17. TRC – PatternAttributes                             5. Problem of missing specification to define the constraint of instruction memory                             NO-CHG oct 30 - No change required
                        17.1 TRC – PatternAttributes –syntax
                                                                             • Problem and Request                                                                                                     If the ATE has a separate "instruction memory"
                                                                             There is the specification for defining the number of maximum steps (which can be specified by                            then a separate PatternAttributes block should be
                                                                             MaxVectors statement in PatternAttributes block) and the maximum value of scan memory (which can                          defined for that memory. See TRC -> Module ->
                                                                             be specified by MaxScanMemory statement in SignalAttributes block); however, there is no statement                        PatternAttributes and SignalAttributes ->
                                                                             to define the maximum value for the instruction memory. I suppose this definition is critical for the                     PatternAttributes for references to multiple blocks.
                                                                             tester constraint. Therefore, it should be added to the specification.
Technical         39 15. TRC – WaveformAttributes                            6. The specification to define the limit of test cycle for multiclock is missing                                 DONE     oct 30 - Changed
                        15.1 TRC – WaveformAttibutes –syntax
                                                                             • Problem and Request                                                                                                     - Changed ReplicateSubWaveforms to
                                                                             The testers can use multiclock as the waveform type. When using the multiclock waveform, its cycles                       SubwaverormIteration
                                                                             making one clock must require the minimum cycle constraint, but there is no specification to define it.
                                                                             As for the method of timing definition using multiclock waveform in Waveforms blocks, it can check                        - Added SubwaveformDuration
                                                                             each minimum cycle constraint for multiclock waveform because it can determine the quantities of
                                                                             cycles making a multiclock by the NumberShapes statement in the WaveformDescription block.                                - If multiclock is done with a regular waveform
                                                                             However, the specification is not provided for the case not using SubWaveform block but multiclock                        definition, then see the added examples of time-
                                                                             waveform is defined in Waveforms block. It should be added.                                                               expr rules in WaveformDescriptions -> Shape
Technical         33 12. TRC – SignalAttributes                              7. The specification to define the constraints defining number of clock pins is missing                          DONE     oct 30 - Several changes made to address this
                        12.1 TRC – SignalAttibutes –syntax                                                                                                                                             issue. See following in the ballot comment: 49-
                                                                             • Problem and Request                                                                                                     GR, 77-JC, 118-GM, 119-GM, 137-GM, 138-GM
                                                                             Some testers have constraints for number of clock pins to be used. There should be the specification
                                                                             not only for the constraints of clock pins but also for scan pins (for example, the constraint that limits
                                                                             the waveform types available and availability of bi-directional pins). In D10 specification, it could define
                                                                             each pin type (such as clock and scan) in the SignalAttributes block; however, it is deleted from the
                                                                             syntax in D14, and there is no way to describe it now. Also, it says “selected from the following list:” in
                                                                             the section describing (3) SignalAttributes statement on page 33, but the list is missed from the
                                                                             specification. Please make sure that the pin type description that was available in D10 is still available.
                                                                             Also, the specification for pin type designation is necessary.

Technical     49-55   17. TRC – PatternAttributes                            8. Discrepancy between Macro and ProceduresCalls in PatternAttributes                                            DONE     oct 30 - Changed
                         17.1 TRC – PatternAttibutes –syntax
                          (8) Macro, (18) ProcedureCalls                     • Problem 1 and Request                                                                                                   - Moved the WithParameters statements inside
                                                                             In case “No” is selected for Macro and ProcedureCalls statements defined in PatternAttributes block,                      the InstructionAttributes block - therefore, only one
                                                                             and if either Macro or Call is defined for InstructionAttributes statement in the same PatternAttributes                  way to enable a Macro or Proc.
                                                                             block, the interpretation of the test patterns for Macro and Call becomes unclear, whether they are to
                                                                             be supported or not. Also, if “Yes” or “WithParameters” is selected, and if Macro or Call is not defined                  - The default values apply when the statement is
                                                                             by the InstructionAttributes statement, its interpretation also becomes unclear. The specification should                 omitted. Actually, this becomes "no checking" and
                                                                             have additional explanation for such cases.                                                                               therefor macro/proc with parameters would be
                                                                                                                                                                                                       allowed.
                                                                             • Problem 2 and Request
                                                                             Macro and ProcedureCall statements have the default value, “WithParameters” among the options, but
                                                                             it is not allowed to describe Macro statement as “Macro;”, so, it must have one of the values, and
                                                                             therefore the default value never occurs to be applied; however, it is explained that its default value is
                                                                             “WithParameters”. The same thing can be said for ProcedureCalls statement. It is not allowed to
                                                                             describe as “ProcedureCalls;”.
                                                                             The problem is, according to the descriptions in this specification, it can be interpreted as “Macro
                                                                             WithParameters;”
                                                                             when Macro statement is not described. It should specify more clearly whether it is a misdescription of
                                                                             the syntax,
Editorial         11 5. TRC orientation and capabilities tutorial            or The default value does not exist, or it should be handled as the interpretation described in the
                                                                             9. the problem of the sample description in Subclause 5.2 that is not described in accordance with the           DONE     oct 30 - Changed
                        5.2 TRC used to define waveforms and                 syntax
                     timing                                                                                                                                                                            The example has been corrected to agree with the
                                                                             79: In INTVC { // two cycle double pulse                                                                                  syntax definitions. Note that this example is now in
                                                                             80: Shape {                                                                                                               annex E.
                                                                             81: U/D/P;
                                                                             82: (@@>=@1+10ns) D;
                                                                             83: (@@>=@2+10ns && @@<@1+32ns) U/D;
                                                                             84: (@@>=@3+10ns && @@<@2+25ns) D;
                                                                             85: }
                                                                             86: }

                                                                             • Problem and Request
                                                                             In the sample description of the STIL above, it says “In INTVC” in line 79; however, the syntax for
                                                                             WaveformDescriptions block states “WFNAME”, and the syntax does not allow describing “In”.
                                                                             I suppose the sample description in the Tutorial is wrong, but I request to modify the sample
                                                                             description in order to make clear that the syntax is correct.

                                                                             waveform_descriptions_block =
                                                                              WaveformDescriptions (WAV_DESC_NAME) (< Rule | Explicit >) { (1)
                                                                                WFNAME { (2)
                                                                                  ( NumberData integer_expr ; ) (3)
                                                                                  ( NumberIO integer_expr ; ) (4)
                                                                                  ( NumberMask integer_expr ; ) (5)
                                                                                  ( NumberPeriods integer_expr;) (6)
                                                                                  ( NumberShapes integer_expr ; ) (7)
                                                                                  ( NumberSignals integer_expr;) (8)
                                                                                  ( NumberTimeSets integer_expr ; ) (9)
                                                                                  Shape { (10)
                                                                                    ( (TRC_LABEL:) ( time_expr ) < EVENT | EVENT_LIST> ;)*
                                                                                  } // end Shape
                                                                                })* // end WFNAME
Technical         36 13.TRC - DCResourceAttributes                            } // end WaveformDescriptions
                                                                             10. Problem of missing the specification to define constraints for DCSequence                                    DONE     nov 3 - changes made to DCSequence block -
                        13.1 TRC - DCResourceAttributes - Syntax
                                                                             • Problem and Request                                                                                                     1. PerPinAttributes - changed from a statement to
                                                                             Describing DCSequence is allowed by IEEE Std 145 0 .2-2002. However, the corresponding                                    a block which defines the rules for like pin types
                                                                             IEEE1450.3 TRC descriptions do not exist. I think it is necessary to have the specification to describe
                                                                             constraints for the descriptions already allowed to describe clearly by STIL.                                             2. DCSequenceAttributes - a new block type
                                                                                                                                                                                                       added to define the allowed sequencing of each
                                                                                                                                                                                                       pin type

                                                                                                                                                                                                       3. Shape - a new block type to define the actions
                                                                                                                                                                                                       and timing allowed for each pin type.
Technical         36 13.TRC - DCResourceAttributes                           11. Problem of missing the specification to defile resolution and accuracy for DCResource                        DONE     nov 3 - see previous item for details
                        13.1 TRC - DCResourceAttributes - Syntax
                                                                             • Problem and Request
                                                                             The descriptions to define constraints for resolution and accuracy for Timing are specified. However,
                                                                             the descriptions to define resolution and accuracy for VForce and IForce of DCResource (Supply,
                                                                             PMU, etc) are not specified. I think it is necessary to have specification for set of constraints for
                                                                             DCLevels as well as those for Timing.



General       -       -                                                      12. Question regarding the specification to define constraints with cnosiderations for tester hardware         NO-CHG nov 3 - no change to doc
                                                                             specification
                                                                                                                                                                                                       1. See subclause 1.3 for a general statement as to
                                                                             • Problem and Request                                                                                                     the completeness of this set of tester rules.
                                                                             I assume that the basic items of the constraints for the hardware specification that can be commonly
                                                                             interpreted on general testers can be described as the tester constraints by IEEE1450.3. However, I                       2. There certainly will be resources in a tester for
                                                                             also assume that all of the tester specific hardware specification for each of the tester makers can not                  VMeas, Imeas, Tmeas, etc. The decision by
                                                                             be fully described as the tester constraints. Considering these assumptions, I can not understand very                    earlier working groups (dot1, dot2) has been that
                                                                             well how much IEEE1450.3 is supposed to define the constraints that are closely associated with the                       the measurement process should be defined by
                                                                             tester hardware specification (such as the measurement range of voltage, ALPG patterns, DFM                               means of a test-method (see dot4). When such
                                                                             memories, method of pin multiplex test, etc). As for a simple example, D14 has the syntax regarding to                    test-methods are defined, they also need to define
                                                                             DFM, but there is no syntax for measurement range (e.g., 80mA Range, 800mA Range, etc) How                                the hardware resources and the TRC checks to be
                                                                             much do you assume the standardized STIL should cover to express the tester specific specification?                       done on those resources.
                                                                             Or, do you assume that the "STIL to test program" conversion makers would describe the expressions
                                                                             or syntax that are not presented in the specification on thieir own by using PragmaBlocks and so on?
                                                                             Please let me know your basic idea if it is possible.

General       -       -                                                      13. Question regarding the tester resource mapping considering the tester hardware specification               NO-CHG nov 3 - see previous item for details

                                                                             • Problem and Request
                                                                             It is almost the same contents as of #12 above, however, it is a question from the view point of the
                                                                             tester resource mapping required when converting from STIL to test programs.
                                                                             As for the hardware specification that can be commonly interpretted as for general testers, I assume
                                                                             that the basic items such as Timing and DCResource can be converted from the descriptions in
                                                                             IEEE1450.0/1/2/3 into test programs. However, I also assume that it is difficult to describe for the
                                                                             conversion considering all of the hardware specification for each tester maker as in the STIL common
                                                                             language. Considering these assumptions, I can not understand very well how much IEEE1450.3 or 4
                                                                             or 5 is supposed to define the constraints that are closely associated with the tester hardware
                                                                             specification (such as the measurement range of voltage, ALPG patterns, DFM memories, method of
                                                                             pin multiplex test, etc). Do you assume that the "STIL to test program" conversion makers would
                                                                             describe the expressions or syntax that are not presented in the specification on thieir own by using
                                                                             PragmaBlocks and so on?
                                                                             There is no concrete example of conversion to be referenced in the specification. I would like you to
                                                                             provide a concrete example of
                                                                              STIL to test program conversion and the principle ideas if it is possible.
 WORK    = work in progress
 DONE    = change complete
REVIEW   = change needs review by wg
NO-CHG   = no change required in document
REJECT   = suggestion rejected for reasons specified

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:4/16/2013
language:Unknown
pages:64