Minutes of P2654 Working Group Meeting No.180, 2023-02-27

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)
Heiko Ehrenberg (GOEPEL Electronics)
Joel Irby (Microsoft)
Teresa McLaurin (Arm) (joined 11:42, left 11:45)
Richard Pistor (Curtiss-Wright)
Louis Ungar (A.T.E. Solutions) (joined 11:09)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco Systems)

Tom Thompson (for IEEE)

Eric Cormack (DFT Solutions)
Brian Erickson (JTAG Technologies)

2. Agenda

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

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • Brad noted three topics from TTSC Language group:
    • Desire for a faster method of updating standards, in respect of languages.  Tom noted that there was some notion of "continuous updates" but had no details and would enquire.
    • Question of copyright: BNF in a standard is subject to copyright so does that imply that products built using that BNF are also subject to copyright?
    • Resolution of inconsistencies across standards. 

7. Discussion Topics

7 a) Debug/Diagnostic Diagrams

  • {Slide 17}
  • DebugTransactionMiddleNode.puml:
  • This is bottom-up, to a Middle Node and adds in the DebugLib API.
  • Noted that this API is "receive only": it just listens to what the Translator does.  Does this mean that a Translator should always offer debug output?  Do we perhaps need to capture the debug concept earlier in the document so that it's doesn't come as a surprise?
  • Can we show the DebugLib API as an optional entity in the PUML?
  • DebugTransactionDriverNode.puml:
  • ModelPoint and Translator both talk to the DebugLib API here, but ModelPoint is a specialisation of a Translator.
  • What's missing is that the Translator is technically talking to a different instance of the DebugLib API from that used by the ModelPoint.
  • Brad briefly talked over some diagrams on Hardware Module Categories although these are not yet ready for release.
  • Current WiP document is now IEEESTD-P2654_Draft_D03_BGVT_20230227.docm, on iMeetCentral at https://ieee-sa.imeetcentral.com/p/aQAAAAAFBHNU

8. Any Other Business

  • {Slide 18}
  • Elections - reminder sent to Jeff and Jason, but no response yet - might be confusing this with P1687.1 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

  • March 6, 2023.

12. Topic for next meeting

  • Continue discussing Sequence Diagrams:
    Debug/Diagnostic, Command Flow.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

  • Joel moved to adjourn, seconded by Brad.
  • Meeting adjourned at 12:02 PM EST

Respectfully submitted,
Ian McIntosh