Minutes of P2654 Working Group Meeting No.128, 2021-10-25

 Meeting called to order:  11:09AM 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) (joined shortly before the end of the meeting)
Terry Duepner (National Instruments)
Brian Erickson (JTAG Technologies)
Peter Horwood (Digital Development Consultants Ltd)
Joel Irby (AMD)
Richard Pistor (Curtiss-Wright)
Jon Stewart (Dell)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco)


Bill Huynh (Marvell Inc.)
Louis Ungar (A.T.E. Solutions)
Tom Thompson (for IEEE)

2. Agenda

  • Brad 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 #127, October 18 (draft circulated October 18)
    • Document reference at the end of 7 should be IEEESTD-P2654_Draft_D01_BGVT_20211018.docm.
    • Brian moved to approve with this amendment, seconded by Terry, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • Study group forming to consider revision of 1149.1 - contact Heiko (nominated chair) if interested.

7. Discussion Topics

7 a) Continue Review of Standard Draft

  • {Slide 14}
  • Continuing review, starting at clause 4.3.
  • Diagram at the top of 4.3 (TAAA21 slide 8) is too "busy".  Simpler version is included below (demo 2 slide 36).
  • Brad has a new example board diagram {now slide 101 of the meeting pack} and accompanying example board model {slide 102} in a work-in-progress pack.  The model does not go into what's inside the devices - that's for e.g 1687, etc., to detail. Would need further diagrams to introduce gateways.  Important to note that the board has JTAG and I2C interfaces at the edge so there will be two distinct host controllers off the board.
  • A physical example is probably useful but should we be representing a system first? While we may need to describe P2654 in a bottom up manner, many people looking at "system test" will likely be viewing it top down.  What should such a representation look like? A rack of boards {slide 103}?  But a SoC could also be a "system".
  • Perhaps a block diagram might be better {slide 104} (we've probably attempted this before).
  • Example of Test System {slide 105} used to work though some thoughts. The UUT could provide loopbacks to increase the testing that would be possible.  This is similar to a "self-test adapter".
  • What is the UUT actually doing here? Technically, we're probably testing the instruments above it and the UUT is part of the infrastructure that makes that possible.
  • We're looking at testing a test system here. That's a valid case but what about where we are testing some other kind of system and the test equipment sits outside that? The TE probably becomes the Test Controller and the "system under test is everything below it.  In essence the demarcation between Test Controller and UUT is rather flexible and depends on context and perspective.  The dotted boxes on slide 105 attempt to illustrate this.
  • We need to work more on how we introduce and represent a system - we might want to have some fairly generic example that we use for the body of the standard and provide other illustrations as non-normative information.
  • The draft was unedited and remains as IEEESTD-P2654_Draft_D01_BGVT_20211018.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:

  • None. 

11. Schedule next meeting

  • November 1, 2021
    • NOTE: Daylight saving ends in Europe so meeting will be 3PM GMT/4 PM CET (remains 11 AM Eastern for US).

12. Topic for next meeting

  • Continue review of standard draft
    • IEEESTD-P2654_Draft_D01_BGVT_20211018.docm
    • Continue with clause 4.3 and representation of a system.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh