P2654 WG Minutes - 2021-11-29

Minutes of P2654 Working Group Meeting No.133, 2021-11-29

 Meeting called to order:  11:08 AM EST

The slide references relate to the pack used during this meeting, located here: 
http://files.sjtag.org/P2654WG/P2654_Meeting_133.pdf

The cumulative reference pack is located here: http://files.sjtag.org/P2654WG/P2654_Reference_Pack.pptx (updated Dec 31, 2020)

iMeetCentral site: https://ieee-sa.imeetcentral.com/sjtag-sg/ 

1. Roll Call

Ian McIntosh (Leonardo) (chair)
Terry Duepner (National Instruments)
Heiko Ehrenberg (GOEPEL Electronics) (joined 11:12)
Peter Horwood (Digital Development Consultants Ltd)
Joel Irby (AMD)
Richard Pistor (Curtiss-Wright)
Jon Stewart (Dell)
Brad Van Treuren (VT Enterprises Consulting Services) (joined 11:10)
Carl Walker (Cisco)

Guests:
---

Excused:
Bill Huynh (Marvell Inc.)
Eric Cormack (DFT Solutions)
Brian Erickson (JTAG Technologies)
Louis Ungar (A.T.E. Solutions)
Tom Thompson (for IEEE)

2. Agenda

  • Joel moved to accept the agenda, seconded by Terry, no objections.

3. IEEE Patent Slides

  • {Slides 5-10}
  • Patent and Copyright slides reviewed without comment.

4. Review and Approve Previous Minutes

  • {Slide 11}
  • Meeting #132, November 22 (draft circulated November 22)
    • No corrections noted.
    • Bard moved to approve, seconded by Terry, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • None.

7. Discussion Topics

7 a) Continue Review of Standard Draft

  • {Slide 14}
  • Transformation/Injection Node Model {slide 117}:
  • Attempts to explain how the model state gets updated when e.g. and SVF is applied.  If the SVF contains the whole test that is applied then perhaps you don't care, but if the SVF is used to configure registers or paths that will be used by another part of the test then the model will need to know what changes have been applied.
  • Command/Return Flow {slide 118}:
  • Attempts, in part, to show how the Transformation Library plays a role in Injection.
  • Update Request and Update Response are shown with the same directionality as they're simply rippling through synchronisation operations.
  • The diagram is quite complex: Perhaps a sequence of diagrams (emulating an animation) would help to illustrate which parts were "active" at each stage in the process.  Brad had originally tried to do this but found it more confusing.  Part of the issue may be that the diagram shows a single node but is representing what happens across multiple nodes (RHS of one node connects to the LHS of another node).   
  • Might be useful to have a very simple example that follows data through the model and down into the hardware. That would require a lot of diagramming but may aid understanding.
  • In describing the process in the document, it may be an option to use several copies of the Command/Return Flow diagram but apply highlighting/dimming to draw attention to the parts the text is describing at that point.
  • This description may not be appropriate for section 4.3: May be more for the description of the software model in section 6.  We may also need to re-work some of the clause titles as the principles have developed a little since these clause titles were first set out.
  • Brad talked through an example application ("filename.pdl").
  • Document was not updated and latest version remains IEEESTD-P2654_Draft_D01_BGVT_20211115.docm.

8. Any Other Business

  • {Slide 15}
  • Required IEEE Volunteer training being rolled out, presumably to people in WG officers roles.  The two courses seen so far (Conflict of Interest, Integrity in Action) are marked as recurring and so presumably need to be completed annually.

9. 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.

10. Takeaways:

  • The choice of application language is left open-ended for now. 

11. Schedule next meeting

  • December 6, 2021
    • Dec 13 and Dec 20 will be the remaining meetings for this year.

12. Topic for next meeting

  • Continue review of standard draft
    • IEEESTD-P2654_Draft_D01_BGVT_20211115.docm
    • Continue with clause 4.3.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

  • Brad moved to adjourn, seconded by Peter.
  • Meeting adjourned at 12:10 PM EST

Respectfully submitted,
Ian McIntosh