Minutes of Study Group Meeting, 2018-04-30

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/StudyGroup/SG_Meeting_33.pdf

1. Roll Call

Ian McIntosh (Leonardo MW Ltd.)
Eric Cormack (DFT Solutions)
Terry Duepner (National Instruments) (left 11:57)
Brian Erickson (JTAG Technologies)
Peter Horwood (Firecron Ltd.)
Bill Huynh (Marvell Inc.)
Joel Irby (ARM)
Richard Pistor (Curtiss-Wright)
Naveen Srivastava (Nvidia)
Jon Stewart (Dell) (joined 11:07)
Brad Van Treuren (Nokia)
Carl Walker (Cisco Systems)
Russell Shannon (NAVAIR Lakehurst) (joined 11:09, left 11:30)
Louis Ungar (ATE Solutions) (joined 11:07)
Sivakumar Vijayakumar (Keysight)

By email (non-attendees):
---

Excused:
Mukund Modi (NAVAIR Lakehurst)

2. IEEE Patent Slides

  • {Slides 5-9}
  • Patent slides reviewed, no comments.

3. Review and Approve Previous Minutes

  • {Slide 10}
  • April 23 (revised draft circulated April 26)
    • Link the single edited slide should be added at the end of the main discussion.
    • Brad moved to approve with this amendment, Eric seconded.
    • No objections or abstentions → minutes approved.

4. Review Open Action Items

  • {Slide 11}
  • [21.1] Brad: Supply Ian with glossary definitions used by 1687.1 for "transformation" and "retargeting".
    • No updates.
    • ONGOING.
  • [27.2] Legacy Initiative Group to propose definition for "SJTAG".
    • No updates.
    • ONGOING
  • [32.1] All: consider and discuss Purpose and Scope on the forum, in respect to incorporating Adam’s concerns.

5. Discussion Topics

a) Continue Purpose and Scope discussion, focus on Adam’s questions.

  • Recent forum posts summarised {shared: http://forums.sjtag.org/viewtopic.php?p=1332#p1332}. Brad's post describes some history, including work by other groups, that this group may not be aware of and which shows gaps in the overall process flows that we could be addressing.
  • {Slide12 - headings, Slide 13 - Draft Purpose, Slide 14 - Draft Scope}
  • Elected to deal with Scope instead of continuing with Purpose as it looked easier to complete.
  • Brad prepared a copy of the Scope slide for editing {shared}.
  • Adam had previously suggested some grammatical improvements - accepted.
  • Question on incorporating a list of interface standards under consideration. The list was previously mentioned in the March 12 meeting (Study Group Minutes - 2018-03-12).
  • {List of interfaces shared: http://files.sjtag.org/Brad/StandardsTable20170313.xlsx}
  • {List of "requirements" shared: http://files.sjtag.org/Brad/SJTAG%20Requirement%20List%2020170118.xlsx - Possibly more useful later on, categorises many observations as forming a requirement, suggesting a capability, making a recommendation or simply a note.}
  • Probably don't want to list candidate interfaces in the scope as it may be taken as limiting the scope to only those listed.
  • Returned to considering Scope.
  • Neither "manner of" nor "format for" seem to be very good. "Interfaces" is not inclusive of the intra device transformations. Having "describes" and "descriptions" in the same sentence seems clumsy. "Representation" maybe captures the notion of modelling better than "description" does.
  • "Methods" could mean different things to different people. In patent terminology a method is a process, which is what we really mean. This should be added to our glossary.
  • We seem to be saying that the standard will do two things - say how the behaviours will be detailed and define how you could then make use of those behaviours - so set them out as a list.
  • Split first sentence into two sentences so the list "looks right".
  • Bring in the words "test", "access" and "management" to emphasise how this relates to the study group title (possibly PAR title).
  • Refer to "sub-assemblies" rather than boards, etc., and "test assets" rather than "instruments" or "registers".
  • Revised version of Scope:
    • This standard: 1) defines a representation of conforming behavioral descriptions of interfaces and transformations, 2) defines new methods for utilizing those representations to enhance the test management and access to sub-assembly test assets. This will allow, in conjunction with existing methods, for the coordination and control of a variety of digital interfaces to devices, boards, and sub-systems to extend test access to board and system levels. The standard does not replace or provide an alternative to existing test interface standards, but aims instead to enable their usage throughout the hierarchy of systems.
  • Edited slide: http://files.sjtag.org/StudyGroup/SG_Meeting_33_bgvt_singleslide.pdf
  • Reference slides (not used during this meeting):
  • {Slide 15 - Draft Need}
  • {Slide 16 - Collated comments}

6. Today's Key Takeaways

  • {Slide 17}
  • None.

7. Glossary Terms from This Meeting

  • "Method" - a systematic approach to accomplish an objective.
  • 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.
    • 1687.1: Transformation, Retargetting.
    • IEEE 1856: Sense - "Sensor" done, Acquire, Analyze not really defined.
    • SJTAG: Discussion on forums - http://forums.sjtag.org/viewtopic.php?f=3&t=782

8. Topic for next meeting

 9. Schedule next meeting

  • May 7.
    • Russell expects to be out on May 7th and 14th.

10. Reminders

11. Any Other Business

  • None.

12. List New Action Items

  • None.

13. Adjourn

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

Respectfully submitted,
Ian McIntosh