Minutes of IEEE P1500 Working group Meeting
April 27, 2003; Napa California

Attendees

Scribe

Minutes

1. Erik Jan Presented the Scalable Architecture TF status update
   • No major open issues
   • Question: Can parallel access to WIR be provided?
     Answer: Yes, but it is not supported in the standard. It is a user extension.
   • Status bits may be captured into WIR, in that case it needs to be shifted out before update; else WIR will be corrupted.
   • Compliancy need to be defined for partial shift
   • Transfer is an optional function
   • Ring mode: internal scan chains are loaded from WBR in parallel
   • Scan mode: WBR and internal scan chains loaded serially in scan mode
   • How will situations where you have one scan input fanning to multiple scan chains handled?
     • Using user defined Intest instruction.
   • Harness cells are used for TEST only IOs.

2. Rohit Kapur presented update on CTL TF status
   • Working on some active issues with 1450.1
   • No change in CTL syntax
   • Defined functionality for synchronizing patterns
   • Need more eyes to review the definitions and CTL documentation
   • Balloting schedule:
     • Review to sync with 1500 (June 2003)
     • Ballot to sync with 1500 (Sept 2003)

3. Francisco da Silva presented Documentation TF status update
   • Document version D0.6 released March 2003
   • Document version D0.7 to be released in June 2003
   • Looking for external reviewers

4. Mergeable Core Test TF update was presented by Sudipta Bhawmik
   • DFT Disclosure document to be released as IEEE standard recommended practice document for 2 year trial
   • Does the standard impose a DFT process?
     • DFT disclosure document implies a process but does not impose one.

5. Yervant Zorian mentioned that if any WG members know of any patents which may be within the scope of P1500, please report. For any reported cases P1500 will contact the patent assignees. Four patents have been mentioned so far. Letters will be sent to the owners of these patents.

6. Karim Arabi presented the latest status update on the Compliancy TF. Some of the issues raised were:
   • Common rules: change signal to core terminals
   • Should complete pattern set be included?
   • Should bi-dirs and differential ios be included? CTAG does not address these now.
   • Rules with multiple lines should be broken down to smaller rules.
   • Are the rules in the right direction? Yes, but it is still at an early stage.
   • Francisco to collect feedback on the rules and pass it to Karim. Yervant recommended that the Compliancy TF continue discussing the rules with the Scalable Architecture TF. A common one day meeting or a series of conference calls were suggested to address this request.

7. The meeting was adjourned.