Minutes of P2654 Working Group Meeting No.109, 2021-05-17

Meeting called to order: 11:04 AM EDT

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

The cumulative reference pack is located here: http://files.sjtag.org/P2654WG/P2654_Reference_Pack.pptx (updated Dec 31, 2020)

iMeetCentral site: https://ieee-sa.imeetcentral.com/sjtag-sg/ 

1. Roll Call

Ian McIntosh (Leonardo) (chair)
Eric Cormack (DFT Solutions)
Terry Duepner (National Instruments)
Heiko Ehrenberg (GOEPEL Electronics) (joined 11:07)
Peter Horwood (Digital Development Consultants Ltd)
Joel Irby (AMD)
Richard Pistor (Curtiss-Wright)
Jon Stewart (Dell)
Brad Van Treuren (VT Enterprises Consulting Services) (joined 11:12)
Carl Walker (Cisco Systems)


By email (non-attendees):

Bill Huynh (Marvell Inc.)
Brian Erickson (JTAG Technologies)
Louis Ungar (A.T.E. Solutions)
Tom Thompson (for IEEE)

2. Agenda

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

3. IEEE Patent Slides

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

4. Review and Approve Previous Minutes

  • {Slide 11}
  • Meeting #108, May 10 (draft circulated May 10)
    • Add Peter to attendees.
    • Eric moved to approve as amended, Terry seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • Nothing advised.

7. Discussion Topics

7 a) Continue review of standard draft

  • {Slide 14}
  • Annotation made on IEEESTD-P2654_Draft_D01_BGVT_20210510.docm, and saved as IEEESTD-P2654_Draft_D01_BGVT_20210517.docm (both in folder Drafts/Group Submissions).
  • Ian's "Hierarchy" diagram shared (this was originally presented in 2016: Meeting Minutes - 2016-02-10). It was an attempt to show that for SJTAG (and now STAM) that there was recursion through a hierarchy and that it ought not to matter what level of assemblies were involved.
    • Does this apply to Hardware, Software or doesn't it matter?  Possibly doesn't matter, but it would have been drawn considering a hardware perspective - the concepts of the current modelling proposal did not exist at that time.
    • May not, as drawn, be wholly relevant to the current proposals, but a similar drawing may be useful to link from hardware structure into the aspects of modelling.
    • Perhaps raises a question over whether evaluation of the model is done once the entire model is constructed or whether you can evaluate at each model and then ripple through.  Brad's POC evaluates the whole model.
    • Network corresponds to the Nodes in Brad's recent diagrams.
  • Diagrams are only placeholders and will need to be revised but we must make sure that any terminology is consistent to avoid creating confusion.
  • P1687.1 does not need to consider recursion; that is an important differentiator, as recursion through levels is essential to P2654.
  • Some of the diagrams we have probably need to be simplified (e.g. slide 56), to more simply explain concepts and to ease presentation.
    • May need to provide multiple examples.
    • Probably need to be able to show at least one case that requires more than one interface involved in a test.
  • GPIO example may be the basis from which (some) Custom modelpoints could be built.  The associated PDL may not be simple but it would be possible.
  • Additional notes included in slides 79-81 of the meeting pack.

8. Any Other Business

  • {Slide 16}
  • None.

9. Today's Key Takeaways

  • Recursion is an important concept in P2654.

10. Glossary Terms from This Meeting

  • None.
  • Carried over:
    • ModelPoint
    • 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

  • May 24, 2021

12. Topic for next meeting

  • Continue to review standard draft.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh