Minutes of P2654 Working Group Meeting No.150, 2022-05-16

 Meeting called to order:  11:03 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)
Heiko Ehrenberg (GOEPEL Electronics)
Richard Pistor (Curtiss-Wright) (joined 11:06)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco)

Tom Thompson (for IEEE)

Brian Erickson (JTAG Technologies)
Peter Horwood (Digital Development Consultants Ltd)
Joel Irby (Flex Logix Technologies, Inc.)

2. Agenda

  • Brad moved to accept the agenda, seconded by Heiko, 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 #149, May 9 (draft circulated May 9)
    • No corrections noted.
    • Brad moved to approve, seconded by Carl, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • P1149.7 and P1500 are on the RevCom June agenda.
  • P1149.1 PAR is on the NesCom Jun agenda. 

7. Discussion Topics

7 a) Clause 6 (Software Model) - continued

  • {Slide 17}
  • Review of IEEESTD-P2654_Draft_D01_BGVT_20210509.docm {shared}.
  • Brad shared diagrams that are being worked on by the P1687.1 Tiger Team on alignment between P1687.1 and P2654.
    • Diagrams for both are similar in form, but the P2654 version represents the general case while the P1687.1 version is a specialisation.
    • P2654 needs to deal with both Left-to-Right and Right-to-Left.
  • In Clause 6, do we need to expand points for both the L-to-R and R-to-L cases? Would it be better to have these as higher level heading and then fill the detail below?  There are some aspects that will be common, so maybe three top-level headings.
  • Clause 6.2 onwards are all "legacy" headings.
    • Demote these to bullets to clean up the document navigation. 
    • {Some time expended on bullet formatting issues in Word}
  • These bullets re-structured into new sub-clauses that fit current perspectives:
    • 6.2 Circuit Model - what nodes and edges do.
      • Nodes - child relationships and required assumptions.
    • 6.3 Circuit Description - how to construct the tree.
      • Some connections may come from netlist and be obvious.
      • Some may be obscure, e.g. between elements of IP.
    • 6.4 Transformation Description - getting from point A to point B.
  • 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_20220516.docm (https://ieee-sa.imeetcentral.com/p/aQAAAAAE82Pd).

8. Any Other Business

  • {Slide 18}
  • AutoTestCon 2022: Paper submission extended to May 31.
  • Par extension request form included as Slide 21, includes guidance notes. TTSC will be looking at extension requests at the July meeting, so we need to consider how we formulate the request before then.

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

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

12. Topic for next meeting

  • Clause 6 - Flesh out  subclauses.
  • 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:03 PM EDT

Respectfully submitted,
Ian McIntosh