IEEE P1500 Working group meeting
Marina Del Ray, Los Angeles
May 3, 4, 2001

Attendees

May 3, 2001

1. Introduction

2. CTAG Task Force Update

The Wrapper Serial Interface Layer (SIL) is stable.
Wrapper Parallel Interface Layer (PIL) is being specified.

Jason Doege has stepped down as Tiger team chair. His position has been taken over by Francisco Da Silva (Synopsys).

WSAFE instruction is dedicated to put the core output to a safe state.
WCLAMP, WPRELOAD also exists. All these are optional instructions.
WSAFE will put a predefined value on the outputs (as decided by the core provider).
Q: Is the SAFE state for both inside the core and outside?
A: Can be, but the requirement is on the outputs.

3. CTL Task Force Update

He demonstrated how CTL can be used to describe the fact "The test floor has red carpet"

   Env {FileRef tester_floor {
			Userkeyword Testerwall;
			Type Documentation;
			Format txt;
			}
			Testerwall white;
			}

   File tester_floor.txt
   Content: The carpet is Red

Test constraints tiger team has been formed.

Tony: Can we have CTL part of the 1450.1 internal review in August?
Rohit: No commitment from CTL task force.

Rohit would like to merge better with the 1450.1. If CTL has to a part of 1450.1, lot of issues need to be readdressed and re thought. Rohit does not feel that the current CTL is fit to be included in 1450.1.

4. Mergeable Core Task Force Update

The "DFT Disclosure Document" is almost complete and requires final refinement. Michael Wahl is working on developing the XML DTD for the document.

The key issue raised was where will this standard belong? Several suggestions were made:

• Include it as part of the 1500 standard as an appendix
• Create a new PAR under 1500 standard (say 1500.2) and include this as "Recommended Practice" rather than a standard (Gordon Robinson)
• Create a totally separate PAR (other than 1500)
• Merge this with VSIA standard

All members agreed that is is a valuable piece of work and there is a need for such a standard disclosure.

Other suggestions offered were:

• Publish the Disclosure Document on the P1500 website
• Publish a paper at ITC

5. Documentation Task Force Update

Version 0.4 has been delayed, will be made available in a week.

Issues:

• Will Mergeable Core test be included in this doc?
• Will part 2 of the document go to 1450 doc.

Rohit Kapur proposed that CTL task force should be merged with CTAG. The language dependent part should be part of 1450.

Motion proposed: CTL & CTAG be merged as one team.
Motion failed due to lack of a second.

6. VSIA update

The meeting was to be continued the next day.

May 4, 2001

7. Documentation Task Force Update (continued)

Version 0.5 will exclude the majority chunk of CTL.

Q. Do we need to notify the 1450 doc editor?
A. No. However, since Tony is in both teams, this should not be a problem.

Five external reviewers will be invited to the doc for each version. Review comments must be completely electronic. Reviewers will be requested to keep the technical comments and editorial comments separate.

IEEE draft documents must include the standard disclaimers which says that the doc is for standards developers only and not for use yet.

The doc will not be available on the public domain website.

Q: Will the compliance section include deliverables?

The list of deliverables can be included in CTL.

Rohit: CTL contains enough information such that an EDA tool can generate all the information and the models required.

The deliverables list may be in conflict with other standards like VSIA.

Rohit: CTL has been made to be synthesizable, such that it can be consumed by a synthesis tool and ATPG tool.

Q: Can CTL describe test requirements for unwrapped cores?

Gordon: It seems that the members in this group do not have a clear understanding of the capabilities of CTL.

Motion (by Dwayne Burek, after amendment): For wrapped cores it is mandatory to provide a structural view that accurately represents external behavior.

The motion was withdrawn after discussion.

We need to specify the compliancy requirements for wrapped and unwrapped cores. It was decided to have a task force define the compliancy requirements.

Compliancy issues:

• Use cases: what falls under 1500 and what not
• structural definition under ExTest
• easy to find info in CTL for wrapper generation
• naked core terminal type information required for wrapper generation
• Data on test patterns, fault models, fault cov, application time
• wrapper constraints
• tester constraints
• TAM constraints
• CTL specific mandated issues
• hierarchy
• diagnostics

members are invited to join this task force.

Erik Jan gave a summary of the Clock issue which included the WART(?).

Next face to face meeting to be held at DAC on June 20th (Wed).