Minutes of P2654 Working Group Meeting No.100, 2021-03-08

Meeting called to order: 11:04 AM EST

The slide references relate to the pack used during this meeting, located here: http://files.sjtag.org/P2654WG/P2654_Meeting_100.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)
Eric Cormack (DFT Solutions) (joined 11:33)
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)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco Systems)


By email (non-attendees):

Bill Huynh (Marvell Inc.)
Tom Thompson (for IEEE)

2. Agenda

  • Brian 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 #99, March 1 (draft circulated March 1)
    • No corrections advised.
    • Brad moved to approve, Terry seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • Michele has demonstrated MAST to P1687.1. Jason Doege has joined P1687.1.

7. Discussion Topics

7 a) Primitives: What is needed for a generic group?

  • {Slide 14}
  • See also slides 55 to 62 in the meeting pack.
  • Grey nodes on slide 56 are connection points for H/W interfaces - behaviours are different, this wasn't appreciated previously.
  • Lesson from 1687's treatment of AccessLink is that sticking to a generic could mean anything or the wrong thing. Ned to be able to describe in more detail, hence P1687.1 and P1687.2.
  • How useful then is the generic case?  There is need to future-proof for as yet unknown interfaces.
  • REGISTER (slide 58) is intended to be very generic (doesn't assume e.g. that it is a boundary scan register). 'cproto' refers to client protocol, 'hproto' to host protocol, but these are probably just informative as they are implementationally part of the transformation strategy pointed at by 'tstrategy'.
  • INSTANCE (slide 59) allows inclusion of some other model tree into the current model, e.g. incorporating a sub-system. (Reminder: SIT = Simplified ICL Tree)
  • CHAIN (slide 60) represent hierarchical relationships; child nodes at the same level. A repeatable ordering of the nodes is required. CHAIN can include nodes connected serially or as a star, but entities need to be "alike".
  • Strategies could be predefined by the standard where there is already a good definition, e.g. for JTAG.
  • Some of this may be replicating data already provided by other means but this method helps ensure a consistent format.
  • LINKER (slide 61) is a specialised form of CHAIN, adding things like 'selector', 'control', etc.  Chain contains nothing that is not in LINKER so arguably LINKER could serve as a CHAIN, with some unused fields.  However we could normally expect CHAIN to be applicable more often than LINKER.
  • "Brainpower" is in the strategy, the rest is just supplying parameters for the software.
  • Do we need to write new S/W for every node?
  • Michele provides 3 additional commands to LINKER: select(x), deselect(x) and isselected(x).  May need to know if selections must be exclusive and if so to deselect other paths.
  • MODELPOINT (slide 62) matches information from the non-P2654 domains into P2654 nomenclature.  There are no injectors as at this stage that needs to be inherent in the transform strategy.

8. Any Other Business

  • {Slide 15}
  • Second NTF online session will be March 23rd at 1 PM CET.

9. Today's Key Takeaways

  • A generic case only was insufficient for P1687.

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

  • March 15, 2021
    • Note DST will be in effect: 11 AM EDT, 3 PM GMT.
    • Brian and Terry expect to be absent.

12. Topic for next meeting

  • Primitives: What is needed for a generic group - continue from "CUSTOM".

13. Reminders

  • Reiterate: Michele Portolan has proposed a workshop at ETS 2021 (later this month). Related to a special session of papers to be run by Martin Keim.

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh