Minutes of P2654 Working Group Meeting No.153, 2022-06-13

 Meeting called to order:  11:05 AM EDT

The slide references relate to the pack used during this meeting, located here: 
http://files.sjtag.org/P2654WG/P2654_Meeting_153.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)
Joel Irby (Flex Logix Technologies, Inc.)
Richard Pistor (Curtiss-Wright)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco)

Guests:
Tom Thompson (for IEEE)

Excused:
Heiko Ehrenberg (GOEPEL Electronics)
Brian Erickson (JTAG Technologies)

2. Agenda

  • Brad moved to accept the agenda, seconded by Joel 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 #151, May 23 (draft circulated May 23)
    • Tom Thompson should be recorded as excused, not attending.
    • Brad moved to approve, seconded by Carl, no objections or abstentions → minutes approved.
  • Meeting #152, June 6 (informal notes circulated June 6)
    • No corrections noted, formal approval not required.

5. Review Open Action Items

  • {Slide 15}
  • [151.1] Brad/Eric to attempt to consolidate WIP edits into draft.
    • Due to Eric's frequent unavailability we need a more flexible approach to editing the draft.
    • Waiting on firmed up text from P1687.1 to work off of, maybe later this week.
    • Ongoing.
  • Action Item Register: http://files.sjtag.org/P2654WG/ActionItemRegister.xlsx

6. Inter-group Collaboration

  • {Slide 16}
  • P1687.1 would like a purely C API rather than C++ - more consistent with what other plug-ins might use, but trickier as means more needs to be managed directly (e.g. instances).
  • P2427 moving towards SA ballot.

7. Discussion Topics

7 a) Clause 6 - Flesh out  subclauses

  • {Slide 17}
  • Work from IEEESTD-P2654_Draft_D01_BGVT_20210523.docm (renamed for this week) {shared}.
  • Brad's proposal {slide 30} shared with P1687.1 and led to discussion around what the flow represented.
  • Slide 29 modified for completeness by adding RVF Protobuf.
  • From slide 26, are SI, TI, DI separately transacted or all part of a single entity?  The same question could arise for any interface used by P2654, we need to have allowances for the client to define that.  For P1687 to P1687.1 it may be more strictly defined although the left-most EHPIC interface will remain undefined.
  • In P2654, the top down (right-to-left) flow will do many of the things that EDA tooling might be expected to do in the P1687.1 case.
  • Slide 29 probably goes somewhere in the introductory parts of clause 6. Slide 30 is more detailed and perhaps supports explanation of how it works later on.  But we possibly need a simpler version that can be used to introduce the coupling between the software model and the hardware.  The simpler version could omit showing e.g. protobufs, the debug messages, etc., (more like slide 27).
  • On slide 30, the intermediate Host RVFs are really both Host and Client - may require alternative terms. At the left side, there isn't really an API as such and is really the driver for the hardware.
  • Added slide 31 - expansion of 29 to add Injection and Debug Procedures.
  • As we reuse the Translator/Transfer Procedures/Host Protobuf/Client Protobuf block repeatedly, can we have a symbolic "macro" for this to simplify the more complex diagram? 
  • Add slide 32 - attempt to wrap re-usable diagram blocks, as suggested above, for Translator and Retargeter.
  • {Slides 33-35 added post-meeting using these "macro-blocks"}
  • "Current" version remains: IEEESTD-P2654_Draft_D01_BGVT_20220523.docm (https://ieee-sa.imeetcentral.com/p/aQAAAAAE87n9).

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 20, 2022

12. Topic for next meeting

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

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

  • Brad moved to adjourn, seconded by Carl.
  • Meeting adjourned at 12:00 noon EDT

Respectfully submitted,
Ian McIntosh