Minutes of P2654 Working Group Meeting No.179, 2023-02-13

Meeting called to order:  11:05 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)
Joel Irby (Microsoft)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco Systems)

Tom Thompson (for IEEE)

Brian Erickson (JTAG Technologies)

2. Agenda

  • Eric moved to accept the agenda, seconded by Brad, 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 #178, February 6 (draft circulated February 6)
    • No corrections
    • Brad moved to approve, seconded by Eric, no objections or abstentions → Approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • TTSC participation encouraged.

7. Discussion Topics

7 a) Review more Sequence Diagrams (subset diags)

  • {Slide 17}
  • Do we want to include the PUML source of the diagrams in the standard. They're not normative in themselves but are resources, perhaps in GitHub?  The text is not huge, two pages at worst, might make sense for it to be provided in an annex, allowing readers to reconstruct diagrams locally. Could also be helpful if we need to revise diagrams at a later date.
  • Decomposition of the Top-Down flow - a couple of diagrams just now to see if these are heading in the right direction.
  • Top-down Command Flow:  Flatten out the inner loops.
  • Horizontal divider bars essentially expand out to other diagrams, e.g. "Pt 2" so these bars probably ought to have figure references, although can only be added once the document layout is more stable.
  • May need to add an object diagram to show how the entities relate to one another.
  • Should these diagrams go into clause 6? If clause 6.1 then the title "Introduction" may need to be revised or is it a new clause 6.2? 
  • Question if clause 5 should actually be moved to be after the present clause 6. Reality is that there are interdependencies across clauses - we're describing things that exist in parallel so there is no clean linear progression that guides the documentation.
  • Two APIs still to consider: Diagnostic/Debug (clause 10.6) and Description Parsing (clause 10.7).
  • Description Parsing probably can't be detailed yet as we need to develop what the data is first.
  • Diagnostic/Debug important to bring out that this simply exposes the messages being passed e.g. what is going into the transfer library, so it is not complicated.  The Use Case provides the functionality, and those are not normative but could be illustrated in a non-normative Annex (D4 and D5 added to the WiP draft as placeholders).
  • Current WiP document is now IEEESTD-P2654_Draft_D03_BGVT_20230213.docm, on iMeetCentral at https://ieee-sa.imeetcentral.com/p/aQAAAAAFA-DL

8. Any Other Business

  • {Slide 18}
  • Elections - reminder sent to Jeff and Jason.

9. Takeaways:

  • Dependencies exist between document sub-clauses. 

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

  • February 27, 2023.
    • February 20 meeting cancelled.

12. Topic for next meeting

  • Debug/Diagnostic API diagrams.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh