P2654 WG Minutes - 2023-01-09

Minutes of P2654 Working Group Meeting No.174, 2023-01-09

Meeting called to order:  11:05 AM EST

The slide references relate to the pack used during this meeting, located here: 
http://files.sjtag.org/P2654WG/P2654_Meeting_174.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)
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)
Brian Erickson (JTAG Technologies)
Richard Pistor (Curtiss-Wright)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)

Guests:
---

Excused:
Joel Irby (Self)
Tom Thompson (for IEEE)

2. Agenda

  • Eric moved to accept the agenda, seconded by Brian, 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 #173, December 12 (draft circulated December 12)
    • No corrections
    • Eric moved to approve, seconded by Brad, no objections or abstentions → Approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • None.

7. Discussion Topics

7 a) Review status

  • {Slide 17}
  • Now starting the 2-year PAR extension period.
  • Should hope to be well into ballot by the end of that period.  Working backwards, and allowing for MEC, etc., that suggests we need to have a ballot-ready draft at the end of this year - Is that feasible?  Else we may need a further extension and that is more awkward to justify.
  • What we have now is a bit better than just a skeleton but still needs a lot of work. Many diagrams are drawn using the top-to-bottom flow rather than the right-to-left we want.  Some are placeholders that need revised diagrams created, others are technically "correct" but need adapted to conform to the IEEE-SA style guide.
  • Elections have yet to take place but Editor is no longer an elected office. This mean we can have an "editorial board", but we still need to work out we can divide up the editing effort.
  • Brad has tried in recent meetings to act as "educator" to bring the group up-to-speed so that each could take on some of the work.
  • We could use input from people like Peter and Terri again as that brings in other views and provides counter arguments that help to test out/challenge proposals.
  • Should we try to get a D03 draft to use as a baseline to build on from now?
  • One way to use the members might be to get them to review a section once it has been fleshed out - see if they can see how the APIs, etc., can be implemented, draw out any queries there might be.
  • Likely to be commonality/overlap between APIs - Is it worth taking the common elements out separately, or cleaner to leave them duplicated within the APIs?  Probably the latter.
  • We've talked about "use cases" frequently, and SJTAG had an extensive list of these.  Part of our problem is that we can now see a broader scope for application than perhaps was envisaged by e.g. 1149.1 when it was first drafted, and we can't document every possibility.
  • However, for an annex we could sort these into classes of use case: A use case that involves playing a SVF or STAPL file, where the SVF/STAPL cmight be at the sub-chain level and P2654 handles the linker; a use case that accesses a register where there is no 1687 involvement, showing the injection action; a use case involving 1687 where part of the flow is from the bottom up; etc.  These are really examples of how to apply the APIs, so gives users the tools to allow them to exploit the APIs for other uses cases. We can develop this thought next week.
  • Current WiP document remains 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 16, 2023

12. Topic for next meeting

  • Classified Use Cases
  • Host API.

13. Reminders

14. List New Action Items

  • [174.1] Ian to review D02 vs D02_BGVT to determine what can be brought into D03.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh