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

Meeting called to order:  11:02 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)

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:03)
Joel Irby (Self) (joined 11:10)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco Systems)


Brian Erickson (JTAG Technologies)
Tom Thompson (for IEEE)

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

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • Adam Ley is a Standards Medallion honoree for 2022.
  • Jeff Rearick starting to revise draft for P1687.1.

7. Discussion Topics

7 a) Document structure

  • {Slide 17}
  • Host and Client APIs.
  • Brad showed his code, architecture illustrated using slide 21 from our Reference Pack 2 - Injection nodes hanging off other Nodes.
  • Slide 8 from Generic Figures, "Generalised Translation": Client at RHS RVF to Host at Translator; Client at Translator to Host at LHS RVF.  Add this diagram to 9.2.1, but needs amendment to annotate the Hosts and Clients.  May also want to make it clear that the API is not tailored to the Translator, i.e. it is agnostic to the contents of the RVF messages, and simply conveys the messages.
  • Brad was constructing text/bullet points on API methods in a local slide; copied into 9.2.2 and corrected to match the type definitions as set out in the HPP file.
  • Start of detailing the rules for the Create method.  The overall process is quite complicated and may require explaining step-by-step.  If we use UML Sequence Diagrams then that may serve as the documentation.
  • More to do on this API, probably won't get to the Client even at the next meeting.
  • Current WiP document is now IEEESTD-P2654_Draft_D02_BGVT_20221212.docm, on iMeetCentral at https://ieee-sa.imeetcentral.com/p/aQAAAAAFAXI_

8. Any Other Business

  • {Slide 18}
  • Jeff and Jason expected to start on P2654 elections shortly.

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 9, 2023
    • Joel may be absent.

12. Topic for next meeting

  • Continue to populate Rules for the Host API.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh