Phone Conference P1450

Status:

DONE+UNCH = 274 (91%)

ASSIGN+TBD+REVIEW = 26 (9%)

Table 10 - Backslash pattern data

- table re-done per Jose's suggestion

- and to address DM issues

- need WG review and approval

TT-2 - Subclause 19.4 - Shift and LoopData statements

- new writeup

- need WG review and approval

DB-5R, Annex-N - re-work underway by Bruce K

DO-1 - Set of expression related issues

- also NO votes by GR and DM

RK-3 - "Multiple Inheritance in the Environment is a problem"

- Should we suggest that dot6 impose this restriction, if they so desire?

- Or should we restrict it in dot0?

RK-4 - "NameMaps should be implemented outside the environment for it

to be used as an infrastructure block."

- How to respond?

RK-5 - "The fail data syntax is very valuable. However, it is not clear to me at

this point how the syntax supports the different test methods and flows fail

information. For example, how does one pass address information of

Memory BIST as part of the fail information.,
Propose: Add examples or explanatory text to show how fail information

of different test methods are covered."

- How to respond?

RK-6 - "Annex F has nothing to do with the scope of 1450.1. The contents

also go against CTL's mechanism which is much simpler. This solution

does not work for situations where the patterns are not available.,
Propose: Delete this Annex."

- How to respond?

DM-22AW - 19.x - rules for If/Else/While/GoTo?

- any suggestion by WG?

- should a GoTo be allowed out of an If/Else/While/Loop/Shift/LoopData block?

- why don't we have a Next/Last to restart/exit a loop?

DM15 - "What is the nature of STATE_ELEMENT? For this whole scheme to work, it has to match a design object. Modern libraries have many cells with multiple internal states not accessible as design objects. Even in the cases where the state_elements are accessible, the type-based names of the ScanCellType must be somehow matched with instance names in design. This would require extention to NameMap., Unless there is a clear usage path form an ATPG tool to a simulation tool, remove CellIn and CellOut constructs. Consider replacing with mechanism usable from the interface of a scan cell."

- PW to discuss with DM

Meeting discussion

IEEE meeting clearances

Nothing under discussion or presentation for this meeting

was identified as being proprietary or restricted.

Table 10:
backslash-operator interactions. Added BNF-style definition
in table to clarify interactions.

Some discussion about /S (or a question about /s). /S pulls the "last
value present from a previous S or s event", but there is no escaped
lowercase-s

Group accepted this addition to table 10 without additional comments.

Loop Data, and Shift
- intent: Shift only supports signals with parameters that have Scan
attributes, and supports padding behavior.

Loop Data consumes data, if data expires (on shorter data sets) then
the last specified WFC persists with no other padding behavior.

John identified a clause in rule 3 that indicates Shift may have a
dependency on Scan Length values, which needs clarification or
elaboration on the circumstances of applications. This application is
under LockStep only, John would like additional words to clarify when
the length is applied.

Open for the moment for complete review.

Annex N
Reviewed Bruce's addition. Issue is if there are Vectors after the
Shift that are part of the chain, there is no way to clearly identify
the end of the actual shift operation. Optional X-end statement to
identify end of actual Shift.

Question about whether X statements attach to Vectors, like
labels. Current definition is that the X statement sits between
statements, but the first Vector after an X statement counts as zero
offset from this X statement.

Discussion about whether the Load_Unload_End X statement, occurring at
the end of a procedure, would ever be applied, since the return from
the procedure would cause the upper-level X statements to be visible
again. In this context (the X statement being the last statement in a
procedure), it is doubtful that this statement would be referenced in
failure information, but again the purpose is to identify the end of
the scan operation.

RK-5: issue raised about specific applications interpreting the data;
we have a mechanism to log the data, but not interpret the data. No
change proposed for this comment.

Expressions Issues
Properly raised by the chairperson as an open action item that needs
resolution to complete several issues.

Specific Issues
RK-1: request to eliminate multiple inheritance in the Environment. no
change to what we do; even a single statement still supports an
ordered nesting of Environment that appears unnatural.

RK-4: no change.

RK-6 / Annex F: no change at the moment; haven't identified an example
to change to.

DM: Rules for If, Else, Goto interactions:
After discussion, identified:
- need some rules
- need some examples
for instance, how do these constructs interact; can Goto's jump into
If's and Elses, can they jump out of Whiles? What rules *should* be in
place and what are the consequences of these rules (hence the issues
of how to do certain things - for instance, terminating loops "early").

PW-DM: reviewing complex scan cell descriptions, and implications of
the descriptions in specific contexts. Discussion started, Peter
understands Denis' perspectives.