Minutes of P2654 Working Group Meeting No.125, 2021-10-04

 Meeting called to order:  11:05AM EDT

The slide references relate to the pack used during this meeting, located here: 

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)
Eric Cormack (DFT Solutions)
Terry Duepner (National Instruments)
Heiko Ehrenberg (GOEPEL Electronics)
Brian Erickson (JTAG Technologies)
Peter Horwood (Digital Development Consultants Ltd) (joined 11:16)
Joel Irby (AMD)
Richard Pistor (Curtiss-Wright)
Jon Stewart (Dell)
Brad Van Treuren (VT Enterprises Consulting Services)
Louis Ungar (A.T.E. Solutions)
Carl Walker (Cisco)

Tom Thompson (for IEEE) (joined 11:38)

Bill Huynh (Marvell Inc.)

2. Agenda

  • Eric moved to accept the agenda, seconded by Brad, 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 #124, September 27 (draft circulated September 27)
    • No corrections noted.
    • Brian moved to approve, Brad seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • 1687.1 setting up Tiger Team to standardise API calls.
  • 1149.7 has one issue to resolve before recirculation ballot.

7. Discussion Topics

7 a) Continue Review of Standard Draft

  • Continuing review, starting at foot of page 7 / top of page 8.
  • The discussion of top down and bottom up is introduced here because P2654 will typically involve a request being passed from the top, while P1687 will consider how a register access is propagated up through the device edge. P2654 doesn't know much of what's going on under the cover, P1687 knows all about what under the cover.
  • Might consider that P2654 is posing a question (or a problem) - How do I make this happen? - while e.g. P1687 provides an answer (or part of the answer) - You need to do these things...
  • When we talk about "IP" we don't mean to imply only "soft" designs, it could just as easily be a device, circuit block, PCA, etc.
  • Do we mean to mention SOC on page 8? Might that imply a limitation on scope that we don't intend?  Wording is taken from P1687 and was used for consistency. May need consideration and re-wording.
  • Reminder that Figure 5 needs the positions of the orange and green arrows swapped.
  • Text still refers to "callback mechanism" - this should now refer to "transfer procedures", which will be in common with P1687.1 and P1687.2.
  • Should note that transfer procedures may be supplied as binaries (e.g. for security) rather than solely as source code.  Allows for "black box" implementations.
  • Referencing Draft Standards:
    • Covered in section 12.3.1 of the Style Guide.
    • Where a referenced draft standard is published while the standard referencing it is still in the editorial/publication stages then the reference will be updated.
    • It is adequate that a draft can reference itself as "this standard" or "this document".
  • Do we need to have consistent definitions for terms?  TTSC has an aim that definitions should be consistent across standards. The IEEE online dictionary suffers from having multiple definitions, taken from different standards over the years. We have recognised the need, in some cases, to add qualifiers where there may be differences, e.g. "P2654 network" or "P1687 network" instead of simply "network".
  • Review to continue from the top of Page 9.
  • Version edited today saved as IEEESTD-P2654_Draft_D01_BGVT_20211004.docm in the Drafts/Group Submissions folder.

8. Any Other Business

  • {Slide 15}
  • None.

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:

  • A network is non-transformative while a bridge is transformative. 

11. Schedule next meeting

  • October 11, 2021
    • Joel, Carl, Richard and Louis will be out for October 11.

12. Topic for next meeting

  • Continue review of standard draft
    • IEEESTD-P2654_Draft_D01_BGVT_20211004.docm
    • Start at top of page 9.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh