Minutes of P2654 Working Group Meeting No.68, 2020-06-08

Meeting called to order: 11:08 AM EDT

The slide references relate to the pack used during this meeting, located here: http://files.sjtag.org/P2654WG/P2654_Meeting_68.pdf

1. Roll Call

Ian McIntosh (Leonardo)
Eric Cormack (DFT Solutions) (left 11:13)
Terry Duepner (National Instruments)
Heiko Ehrenberg (GOEPEL Electronics)
Brian Erickson (JTAG Technologies)
Peter Horwood (Digital Development Consultants Ltd)
Bill Huynh (Marvell Inc.)
Joel Irby (AMD)
Richard Pistor (Curtiss-Wright)
Jan Schat (NXP Semiconductors) (joined 11:44)
Jon Stewart (Dell)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco Systems)


By email (non-attendees):


2. Agenda

  • Brad moved to accept the agenda, seconded by Terry, no objections.

3. IEEE Patent Slides

  • {Slides 5-10}
  • Patent and Copyright slides reviewed.

4. Review and Approve Previous Minutes

  • {Slide 11}
  • Meeting #67, June 1 (draft circulated June 1)
    • Correction: Joel should be noted as an excused absence.
    • Terry moved to approve with amendment, Joel seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • Brad has shared our STAM System definition with P1687.1.

7. Discussion Topics

7 a) UTAP development

  • {Slide 14}
  • Presentation by Peter {http://files.sjtag.org/P2654WG/UTAP_UsageWithinSTAM.pdf}.
  • Aims to show a means by which some of STAM's principles can be achieved.
  • Does this include interactive execution? It can handle interactivity.  That implies generation of vectors on the fly. This is about relaying the data across interfaces, it doesn't care about what the instrument is or where/how the vectors are generated.
  • Assume that for a COTS item that the vendor will provide SVF or STAPL as these are still really the only ways to provide a portable test.
  • Any transformations between the test controller and the target ought to be known and so any required "wrapping" can be applied when the vectors are generated for the test controller side.  In effect the routing is pre-determined.
  • UTAP provides a common interface that is independent of the physical interface that is being connected to. This is in common with the SCSI scheme discussed previously, and uses the standard 6-byte header with additional bytes available for vendor header data that may be used to introduce some value-adding capabilities.
  • At each transformation level there is an Inquiry Request/Response  followed by a Mode Select/Mode Sense Response.
  • There was insufficient time for questions so this will be taken to the next meeting.
  • As a question regarding copyright was raised and the slides bear a rights affirmation Peter confirmed that he was OK with this material being shared with the group and would send a copy to the reflector to  re-affirm that (although the file is also linked at the top of this section).
  • There may be potential for a live demo of UTAP, depending on circumstances at the the next meeting or it may taken "off-line" for anyone interested.

8. Any Other Business

  • {Slide 15}
  • None.

9. Today's Key Takeaways

  • None.

10. Glossary Terms from This Meeting

  • None.
  • Carried over:
    • System Element.
    • System Resource.
    • 'System' needs the concept of a controller capability added.
    • "Filtering" may need to be defined.
    • "Translation" may need to be defined.
    • "Interface" is missing.
      • No obvious IEEE accepted definition.
      • 1687 has definitions for specialised forms: Device Interface and Instrument Interface.
      • We may need specialised forms for Software Interface and Hardware Interface.
      • "Interface" is overloaded and requires disambiguation.
    • 1687.1: Transformation.
    • IEEE 1856: Sense - "Sensor" done, Acquire, Analyze not really defined.
    • Device - do we mean a packaged device? May be many devices in a package. "Device" is often used as a modifier, e.g. "device package", "device identification".
    • Use Case Context, Application Context
    • Legacy Infrastructure, SJTAG Infrastructure (placeholders for now, really for working group to define).
    • "Generators": May need to be qualified as "Test Generators" (used by the integrator/tester) and "Model Generators" (used by IP providers, interface designers, etc.).
    • AccessLink and DataLink descriptions will need to be revised.
    • See P1687.1's definitions on Slide 31 of the pack presented by Jeff Rearick on Jan 14, 2019.
    • "State", "Vector", "Sequence" and "Pattern" as proposed at April 8, 2019 meeting.
    • "Event", "Access Interface" as proposed at April 15, 2019 meeting.
    • 'Port' needs to be developed.

11. Schedule next meeting

  • June 15, 2020.

12. Topic for next meeting

  • a) Q&A on UTAP

13. Reminders

  • None.

14. List New Action Items

  • None.

15. Adjourn

  • Terry moved to adjourn, seconded by Brad.
  • Meeting adjourned at 12:07 PM EDT

Respectfully submitted,
Ian McIntosh