Subject: STIL.1 issues for 3/14 phone call
Date: Wed, 13 Mar 2002 19:01:53 -0800
From: Tony Taylor <tonyt@synopsys.COM>
To: gmaston@synopsys.COM, gwilder@dal.asp.ti.com, dsprague@btv.ibm.com,
     peterwohl@adelphia.net, jason_doege@inovys.com, jim@galois.com,
     David Kellerman <david_kellerman@teseda.com>

To STIL.1 working group:

There are no new docs for the meeting tomorrow. No one has sent me any
updates and I haven't made any changes.

Here are new topics for discussion:

1. LockStep requirements
(additional paragraph to clause 12.1, p28)

"When patterns are executing in lock-step mode, an additional constraint is
made on the normalizing of scan chain data. The scan chain length is
determined by the decimal integer value that is specified in the
ScanIn/ScanOut statement. In the process of preparing multiple patterns to
execute in lock-step, the length of the longest scan chain is to be
specified for all scan chains that are to be loaded/unloaded in parallel.
The process that interprets/loads the scan data shall pad the scan chains
to the length specified according to the rules of 1450-1999."

2. double quotes within strings in NameMaps
(additional paragraph to clause 18.1, p43)

"The target "MAP_STRING" is used to map STIL names into an external
environment. If the target name contains either a double-quite or a
back-slash, then the following syntax shall be used in the target string.

double-quote: "blah_blah\"blah_blah"
back-slash:   "blah_blah\\blah_blah"

Note: Per 1450-1999 definition, this syntax is NOT allowed in a STIL string."

3. N event usage
(clarification to 1450-1999, table 12, p89)

"Table 12 contains the list of unresolved timing events. In most cases,
these unresolved events are only used as interim states that are to be
resolved prior to moving a pattern set to a tester. In practice, the 'N'
event (ForceUnknown) is often left as an unresolved state. The
interpretation of the 'N' state is that it may freely be replaced by either
a U or a D event with no consequence to the operation or validity of the
patterns. The reason for leaving it unresolved is that in some applications
optimizing is possible by choosing one state over the other."