P2654 WG Minutes - 2022-12-05

Minutes of P2654 Working Group Meeting No.172, 2022-12-05

Meeting called to order:  11:06 AM EST

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

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)

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

1. Roll Call

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

Guests:
---

Excused:
Tom Thompson (for IEEE)

2. Agenda

  • Eric 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 #171, November 28 (draft circulated November 28)
    • Brad moved to approve, seconded by Eric, no objections or abstentions → Approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • Ian attending CS-SAB meeting on Thursday.

7. Discussion Topics

7 a) Document structure

  • {Slide 17}
  • Injection API: Refresh on how this is intended to work, largely around slides 11 and 12 from Brad's Theory and Architecture for P2654 presentation.
  • Observed that the draft text in the document omits the Update Request and Update Response methods - Brad has noted this and will those later.
  • One edit changing 'Transformation' to 'Injection' had been overlooked.
  • Important to note that not every node will need an Injection API.  The standard should make this clear, so some text added to the Description of the API to point this out.
  • Debug API: Similar copy/paste/edit as before.
  • We should note what debug/diagnostics are implied here, for the guidance of the reader: This is exposing the API calls and is not related to debug or diagnostics of the target hardware
  • The ProtoBuf descriptions are turning out to be repetitive - these should probably be moved to an annex and referenced by the main body text as necessary.  
  • Current WiP document is now IEEESTD-P2654_Draft_D02_BGVT_20221205.docm, on iMeetCentral at https://ieee-sa.imeetcentral.com/p/aQAAAAAFASWA. 

8. Any Other Business

  • {Slide 18}
  • No progress on elections for this group so far - it is understood that Jeff is otherwise occupied presently.

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

  • December 12, 2022 - Last meeting of 2022

12. Topic for next meeting

  • Populate Rules for the Host and Client APIs.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh