Minutes of P2654 Working Group Meeting No.56, 2020-03-02

Meeting called to order: 11:07 AM EST

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

1. Roll Call

Ian McIntosh (Leonardo)
Eric Cormack (DFT Solutions)
Terry Duepner (National Instruments)
Heiko Ehrenberg (GOEPEL Electronics)
Brian Erickson (JTAG Technologies)
Peter Horwood (Digital Development Consultants Ltd)
Bill Huynh (Marvell Inc.)
Joel Irby (AMD)
Richard Pistor (Curtiss-Wright)
Jan Schat (NXP Semiconductors)
Naveen Srivastava (Nvidia)
Jon Stewart (Dell)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco Systems)

Guests:
---

By email (non-attendees):
---

Excused:
---

2. Agenda

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

3. IEEE Patent Slides

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

4. Review and Approve Previous Minutes

  • {Slide 11}
  • Meeting #55, February 24 (draft circulated February 24)
    • No corrections noted.
    • Eric moved to approve, Terry seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • None.

7. Discussion Topics

7 a) Sketch out an outline of the draft

  • {Slide 14}
  • Bullet points recorded during the earlier meetings are now moved to a separate reference file: http://files.sjtag.org/P2654WG/P2654_Reference_Pack.pptx.
  • Draft outline is in slides 17-25 of this week's pack (linked in the heading of these minutes).
  • Discussion centred around the meaning of "Assembly of assemblies" in 8 a) {slide 21}.
  • How does "Assembly of assemblies" relate to "system" or "hierarchy"? Do we have inconsistent terminology for the same thing or are we sometimes using the same term for different things or a bit of both?
  • Is "Assembly of sub-assemblies" more accurate? Possibly, at least in some views: Sub-assembly indicates that it has more to it than a lowest level part, that it could be further sub-divided.
  • Noted that a given sub-assembly is not necessarily tied to particular "level" in a hierarchy and could exist at one level in one branch of a hierarchy while an identical sub-assembly may exist at much lower level in another branch.
  • "Assembly" is simply meant to show that there is an aggregation of things at the next lower level, perhaps an aggregation of components (a board) or an aggregation of boards (a shelf or sub-rack). 
  • The "assembly of assemblies" concept arose from an attempt to abstract or generalise away from terms that were specific to a view of a particular point in the hierarchy, e.g. a board of components or a rack of boards. In this way, the same two-level description could be applied at any point in the hierarchy. This also offers a description that supports recursion; any operations applied at the highest level would operate recursively through each pair of levels.
  • Forum thread for comments on the outline: http://forums.sjtag.org/viewtopic.php?f=3&p=1444#p1444.

8. Any Other Business

  • {Slide 15}
  • None.

9. Today's Key Takeaways

  • Recursion involves re-use of the same type of calls at each different level in the hierarchy.

10. Glossary Terms from This Meeting

  • None.
  • Carried over:
    • "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.

11. Schedule next meeting

  • March 9, 2020.
    • Absences: None advised.
    • DST begins in US on 8th. Meeting remains at 11 US Eastern, so 3 PM BST/4PM CET.

12. Topic for next meeting

  • Continue on outline of the draft: Assembly of assemblies, "system" definition.
  • Use Cases: Intent and objectives.

13. Reminders

  • None.

14. List New Action Items

  • [56.1] Brad to request "LoA in principle" from Michele.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh