P2654 WG Minutes - 2022-05-02

Minutes of P2654 Working Group Meeting No.148, 2022-05-02

 Meeting called to order:  11:08 AM EDT

The slide references relate to the pack used during this meeting, located here: 
http://files.sjtag.org/P2654WG/P2654_Meeting_148.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)
Eric Cormack (DFT Solutions)
Heiko Ehrenberg (GOEPEL Electronics)
Brian Erickson (JTAG Technologies)
Joel Irby (Flex Logix Technologies, Inc.)
Louis Ungar (A.T.E. Solutions) (joined 11:18)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco)

Guests:
---

Excused:
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 #147, April 25 (draft circulated April 25)
    • No corrections noted.
    • Eric moved to approve, seconded by Brad, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • P1149.7 2nd recirculation ballot closed with 100% approval - will move to RevCom approval and pre-publication editing.
  • TTSC Test Language sub-committee: Express permission of participant is required to be added to the email list.

7. Discussion Topics

7 a) Clause 6 (Software Model) - continued

  • {Slide 17}
  • Review of IEEESTD-P2654_Draft_D01_BGVT_20210425.docm {shared}.
  • Left off last week having started listing characteristics of Edges.
  • Alignment with P1687.1 (added to bullets on "For each Node"):
    • Transformation Transfer diagram {slide 19}.
      • EHPIC instead of DPIC - trying to move away from using "device".
    • Retargeted Transfer diagram {slide 20}.
      • Transfer Channel: Is this a new term?  Generalised form of what we've previously called the "P2654 Message Channel"; It is what RVF messages are sent over.
  • Is "right-to-left" and "left-to-right" clear in describing what is meant?  Needs to be supported by diagrams, but essentially the "client" is on the right and the "host" is on the left.
  • Add bullets on Injection.
    • But should we talk about "Insertion" (or some other term) instead?
  • Add bullets on Transformation Library.
    • Code construct 
    • Could have an anonymous (i.e. unpublished) grammar between Black Boxes.  It would conform to RVF but only be known/agreed between the producers of the Black Boxes.
    • Most points here can be replicated for Injection (or whatever we end up calling that).
  • Marked-up version with today's edits: IEEESTD-P2654_Draft_D01_BGVT_20220502.docm (https://ieee-sa.imeetcentral.com/p/aQAAAAAE7QWk).

8. Any Other Business

  • {Slide 18}
  • None.

9. Takeaways:

  • Injection, used in the Top-down flow, may be better described as something else. 

10. Glossary: 

  • Transfer Channel, replacing P2654 Message Channel.
  • Carried over:
    • 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

  • May 9, 2022

12. Topic for next meeting

  • Clause 6 - define subclause headings.
  • Follow with clauses 7, 8.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh