Minutes of P2654 Working Group Meeting No.106, 2021-04-26

Meeting called to order: 11:05 AM EDT

The slide references relate to the pack used during this meeting, located here: http://files.sjtag.org/P2654WG/P2654_Meeting_106.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)
Brian Erickson (JTAG Technologies)
Peter Horwood (Digital Development Consultants Ltd)
Joel Irby (AMD)
Richard Pistor (Curtiss-Wright)
Jon Stewart (Dell)
Louis Ungar (A.T.E. Solutions)
Carl Walker (Cisco Systems)

Guests:
---

By email (non-attendees):
---

Excused:
Bill Huynh (Marvell Inc.)
Brad Van Treuren (VT Enterprises Consulting Services)
Tom Thompson (for IEEE)

2. Agenda

  • Brian 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 #105, April 19 (draft circulated April 19)
    • No corrections noted.
    • Terry moved to approve, Peter seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • Nothing advised.

7. Discussion Topics

7 a) Continue Use Case diagramming

  • {Slide 14}
  • A revised version of the diagram from slide 75 is presented on slide 15.  This adds illustration of signal paths and the possibility of different hardware interface buses (for clarity).
  • Given the structure, and from a modelling perspective, should the blue lines from the tops of GPIO and Frequency Counter actually link to the Target Sub-Assy rather than the System Tester?  Ultimately the System Tester will need to know how to use those instruments, but should we be reflecting that the Target Sub-Assy will be providing a Transformation here since the physical buses are distinct?
  • Can we draw a dotted box to show where the "system edge" is?  Last week we concluded that we could apply P2654 to external instruments so the box could be drawn almost anywhere, so as in slide 76 the box can be drawn round everything below the System Tester.  But that may not always be the case:  If the instruments are external, then there may be no P2654 description to include in the model, hence they would be out-of-scope for P2654 (slide 77).  Not immediately clear if there's a way to assemble tests that include P2654 and non-P2654 test structures, but it would be up to the end user to determine how to handle it.
  • How does the modelling deal with the case where the testing of an item depends on the control of a component part that is physically below it in the design hierarchy, e.g. where the GPIO in the example is required to test the Target Sub-Assy? the Test target must be transforming the data used in its own test - is this a problem?

7 b) Look towards documentation

  • Drafts of the standard will be on iMeet Central (see link at the top of these minutes) - this is a "private" area for the WG, noting that drafts should not be available outside of the WG, or later the ballot group. 
  • IEEE-SA requires that all users of the iMeet site have accepted the IEEE Privacy Policy.
  • Some of the group members either haven't accepted invitations to sign up on iMeet (logins may be different to those used on other parts of the IEEE web services - it's important that the Privacy Policy is accepted using the email address used for iMeet).  Ian will be sending prompts to complete signups where necessary.
  • Presently only the bare template is in iMeet but Eric has started on the basic population of front matter, and may have some of the nominal section headings inserted.
  • iMeet will allow members to review and comment on the document outside of the weekly meetings.
  • It'll likely be necessary to delegate some of the drafting out within the group, but we need a firm grasp of the concepts before we can do that.
  • Important to note that Brad's demonstrations should be treated as Proof of Concept and not necessarily a binding implementation method.

8. Any Other Business

  • {Slide 16}
  • None.

9. Today's Key Takeaways

  • Some instruments (e.g. external rack and stack instruments) may not have P2654 descriptions available.
  • If there is no P2654 description then they are out-of-scope of the standard - end user will need to determine if and how these can be linked into a P2654 test.

10. Glossary Terms from This Meeting

  • None.
  • Carried over:
    • 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 3, 2021

12. Topic for next meeting

  • Review standard template and initial layout.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

  • Peter moved to adjourn, seconded by Terry.
  • Meeting adjourned at 11:56 AM EDT

Respectfully submitted,
Ian McIntosh