Minutes of P2654 Working Group Meeting No.151, 2022-05-23

 Meeting called to order:  11:06 AM EDT

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)
Brian Erickson (JTAG Technologies)
Peter Horwood (Digital Development Consultants Ltd)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)

Tom Thompson (for IEEE)

Joel Irby (Flex Logix Technologies, Inc.)
Carl Walker (Cisco)
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 #150, May 16 (draft circulated May 16)
    • No corrections noted.
    • Brad moved to approve, seconded by Louis, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • Panel at ETS tomorrow (24th) on 1687: "I wish IJTAG would do this..."

7. Discussion Topics

7 a) Clause 6 - Flesh out  subclauses

  • {Slide 17}
  • Work from IEEESTD-P2654_Draft_D01_BGVT_20210516.docm {shared}.
  • Brad shared further diagrams that are being worked on by the P1687.1 Tiger Team on alignment between P1687.1 and P2654.
    • Diagrams were initially failing to capture the P2654 case properly.
    • Brad had guided further development, now quite close {slide 22}.
    • Top and bottom RVF messages are the "same messages", only the payload differs.
    • EHPIC (formerly P1687.1's DPIC) is not directly relevant to P2654.
    • Slides 23 and 24 added to provide further explanation.
  • Copy Specifications, Rules, Recommendations and Permissions sub-headings into 6.2, 6.3 and 6.4.
  • How much of 6.1 is going to have Rules or will the rules all come in the following sections?  Probably needs to mention rules but may just be forward references.
  • There will be rules related to each of the interfaces/APIs of a node.
  • Probably needs something (either in 6.1 or perhaps earlier) to convey that there must be communication between nodes.
  • Rules need to describe the behaviour, order of events, etc., and not prescribe implementation specifics that could be differentiators for tool vendors.
  • 9.1.2 Role of the client interface and 9.1.3 Role of the host interface might need to be in clause 6. However 9.1 and 9.2 were meant for discussing hierarchical matters, more a practical application.  Need to think about whether there's a different aspect of 9.1.2 and 9.1.3 for clause 6. 
  • Material in 6.5 (was 6.1) has yet to be moved into 5.
  • Marked-up version with today's edits: IEEESTD-P2654_Draft_D01_BGVT_20220523.docm (https://ieee-sa.imeetcentral.com/p/aQAAAAAE87n9).
  • It might help if we can clean up the WIP document (clean up edits and merge back to "official" draft) {ACTION}.

8. Any Other Business

  • {Slide 18}
  • None.

9. Takeaways:

  • None. 

10. Glossary: 

  • None.
  • Carried over:
    • 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

  • June 6, 2022
  • No meeting on May 30 due to Memorial Day holiday.

12. Topic for next meeting

  • Clause 6 - Flesh out  subclauses (continued).
  • Follow with clauses 7, 8.

13. Reminders

14. List New Action Items

  • [151.1] Brad/Eric to attempt to consolidate WIP edits into draft.

15. Adjourn

  • Peter moved to adjourn, seconded by Eric.
  • Meeting adjourned at 11:59 AM EDT

Respectfully submitted,
Ian McIntosh