Minutes of P2654 Working Group Meeting No.176, 2023-01-23

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)
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)
Brian Erickson (JTAG Technologies)
Joel Irby (Self)
Richard Pistor (Curtiss-Wright)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco Systems) (joined 11:05)


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 #175, January 16 (draft circulated January 16)
    • 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}
  • P1149.4 ballot invitation has been extended.

7. Discussion Topics

7 aHost API

  • {Slide 17}
  • Refresh on the basis of the Host API (see slide 104 in Reference Pack 2).
  • We advertise the handleRequest() [ref 2] and send Response() [ref 9] methods for the Host. These have reciprocals [Ref 4, ref 7] on the Client side.
  • In the example code shared, the latter few methods are specific to the implementation and only the first four are key to the API.
  • The diagram may be difficult to follow, might be more understandable as a UML Sequence Diagram, but that may need some explanation for some members of the group.
  • Simple example in PlantUML shared, see also PlantUML.com.
  • Word template/add-in is available for inserting/editing PlantUML diagrams directly in Word (Note: From the description, this has only been tested with Word 2010, but may work with other versions).
  • New diagram assembled in 9.1.1 to display the object interactions associated with the Host API.
  • This in fact spans to the Client side, and there are really two different interactions involved so adding a separator may be beneficial.  These diagram will generally span APIs so may need to be in the preliminary discussion rather than in individual API descriptions.
  • Addressing Injection will likely require a diagram twice as big.
  • We may be missing a level 2 heading at 9.1 (or do 9.1.1 and 9.1.2 become 9.1 and 9.2?).
  • Current WiP document is now IEEESTD-P2654_Draft_D02_BGVT_20230123.docm, on iMeetCentral at https://ieee-sa.imeetcentral.com/p/aQAAAAAFAvdg

8. Any Other Business

  • {Slide 18}
  • Jeff and Jason due to start on P2654 elections.  May need to pursue if no movement this week.

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 30, 2023
    • Eric will be out.

12. Topic for next meeting

  • Review Sequence Diagrams.

13. Reminders

14. List New Action Items

  • [176.1] Brad to attempt to draw up more UML Sequence Diagrams.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh