Minutes of P2654 Working Group Meeting No.147, 2022-04-25

 Meeting called to order:  11:04 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) (left 11:56)
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)


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 #146, April 18 (Updated draft circulated April 20)
    • No corrections noted.
    • Brad moved to approve, seconded by Joel, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • TTSC Test Language sub-committee is looking for participants.

7. Discussion Topics

7 a) Clause 6 (Software Model) - Bullet points for paragraph topics

  • {Slide 17}
  • Review of IEEESTD-P2654_Draft_D01_BGVT_20210418.docm {shared}.
  • Noted that year shown in the filename has been incorrect so far this year, corrected from this point forward.
  • Existing sub-clause headings are legacy from the original bullet point exercise.  May no longer be relevant.
  • Add new bullet point based on current understanding:
    • Tree graph of circuit topology
    • Nodes on graph: Circuit elements/entities
    • Edges of graph:
      • Relationships between entities (1:1, 1:0, 1:*)
      • Message interfaces between entities
    • Protocols wrapped by RVFMessage carrier packets (could span H/W boundaries)
    • Discussion on need/purpose for serializing and using ProtoBufs (see also Figure 1 and Figure 2 below, shared by Brad)
    • "Wrapping" occurs in two ways:
      • a) RVFMessage wrapping within the Software Model
      • b) Wrapping of data with e.g. essential routing information as it passes through the hardware
      • The wrapping b) is evaluated within the software model
    • Need portable descriptions from the entity provider
    • Internal forms within tooling could be proprietary
    • Black boxes might encompass several nodes but will present like a single leaf
      • Could be provided as an executable?
      • May have proprietary messages passed between black boxes - we have not considered that
        • Might that be a "dot 1" consideration?
    • Characteristics for Nodes listed:
      • Parameters provide for addressing of specific instances
      • Parameters my pass keys for licensed IP or for encryption/decryption
    • Started listing characteristics of Edges - to be continued
  • Marked-up version with today's edits: IEEESTD-P2654_Draft_D01_BGVT_20220425.docm (https://ieee-sa.imeetcentral.com/p/aQAAAAAE7K-Q).
HW Implementation from Code
Figure 1
Example Grammar
Figure 2

8. Any Other Business

  • {Slide 18}
  • None.

9. Takeaways:

  • Consider proprietary messages between black boxes. 

10. Glossary: 

  • None.
  • 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 2, 2022

12. Topic for next meeting

  • Clause 6 structure - continued (Software Model).
  • Follow with clauses 7, 8.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

  • Eric moved to adjourn, seconded by Joel.
  • Meeting adjourned at 12:01 PM EDT

Respectfully submitted,
Ian McIntosh