Minutes of P2654 Working Group Meeting No.175, 2023-01-16

Meeting called to order:  11:07 AM EST

The slide references relate to the pack used during this meeting, located here: 

Reference pack 1 is located here: http://files.sjtag.org/P2654WG/P2654_Reference_Pack.pptx (all 2020 material)
Reference pack 2 is located here: http://files.sjtag.org/P2654WG/P2654_Reference_Pack_2.pptx (all 2021 material)
Reference pack 3 is located here: https://files.sjtag.org/P2654WG/P2654_Reference_Pack_3.pptx (all 2022 material)

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

1. Roll Call

Ian McIntosh (Leonardo) (chair)
Eric Cormack (DFT Solutions)
Heiko Ehrenberg (GOEPEL Electronics) (joined 11:14)
Brian Erickson (JTAG Technologies)
Richard Pistor (Curtiss-Wright)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)


Carl Walker (Cisco Systems)
Tom Thompson (for IEEE)

2. Agenda

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

3. IEEE Slides

  • {Slides 5-13}
  • Patent, Copyright and Behavior slides reviewed without comment.

4. Review and Approve Previous Minutes

  • {Slide 14}
  • Meeting #174, January 9 (draft circulated January 9)
    • No corrections
    • Brian moved to approve, seconded by Brad, no objections or abstentions → Approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • None.

7. Discussion Topics

7 a) Classified Use Cases

  • {Slide 17}
  • Refresh on the four classes suggested last week.
  • New Slide 19 added to record these.
  • Expanded to provide some descriptive detail and show additional sub-cases within each of the broad headings.
  • Added new Use Cases for CTL/STIL/1500 and for JTAG/I2C bridge leveraging EDA tooling.
  • Collected these into three major headings:
    • Canned tests
    • Dynamic tests
    • Hybrid cases that involve mixed methods
  • Practical tests may well involve a mix of use cases.
  • System to sub-system control is effectively control of state of the sub-system.
  • May have visibility into the sub-system (can model the entirety) or may not (don't really care how the sub-system does what the sub-system does) - like the black-box case.  There may be a delegated model of the sub-assembly being actioned unseen.  In some cases, the notion of a sub-assembly may be irrelevant, and it just becomes part of the whole system.
  • Be wary of trying to conceive of too many examples: Try to keep to examples that are illustrative enough to allow users to see how elements can be assembled and applied to their specific applications.
  • The JTAG/I2C bridge example is very specific, in that it refers to particular interface types: Can we find a way to express this in more generalized terms?
  • Start copying these headings into Annex D of the draft.
  • Current WiP document is IEEESTD-P2654_Draft_D02_BGVT_20230116.docm, on iMeetCentral at https://ieee-sa.imeetcentral.com/p/aQAAAAAFArCu

7 b) Host API

  • Deferred to next meeting due to lack of time.

8. Any Other Business

  • {Slide 18}
  • Probably another week before Jeff and Jason can start on P2654 elections.

9. Takeaways:

  • None. 

10. Glossary: 

  • None
  • Carried over:
    • 2654 Interface Translator Node (2654ITN)
    • Translator: See 2654 Interface Translator Node (2654ITN)
    • Transfer Channel, replacing P2654 Message Channel
    • Network will need to be defined
    • PTPG - Programmable Test Pattern Generator/Generation
    • Better define structural test boundary vs functional test
    • Transfer module/library
    • Injection transfer module/library
    • RVF Message (to be refined)
    • RVF Command (to be refined)
    • "Tooling" - need to be clear on what is meant.
    • "True System".
    • Comment that "End-User" is subject to perspective and so needs to be qualified.
    • 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

  • January 23, 2023

12. Topic for next meeting

  • Host API.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

  • Eric moved to adjourn, seconded by Brad.
  • Meeting adjourned at 11:54 AM EST

Respectfully submitted,
Ian McIntosh