Minutes of P2654 Working Group Meeting No.76, 2020-08-24

Meeting called to order: 11:10 AM EDT

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

1. Roll Call

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


By email (non-attendees):

Brian Erickson (JTAG Technologies)

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. 

4. Review and Approve Previous Minutes

  • {Slide 11}
  • Meeting #75, August 10 (updated draft circulated August 12)
    • No further 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}
  • P1149.7 ballot group formation is in progress. It should be possible to sign up for the ballot through IEEE MyProject if you have previously recorded an interest or contact Jason Peck.

7. Discussion Topics

7 a) Discussion of perspectives on STAM

  • {Slide 14}
  • Ian talked through slides 16-20 which had been circulated prior to the meeting.
    • Struggled with definitions in trying to distinguish between a device/component/instrument that you want to interact with and devices/components that you may need to navigate data through.
      • Side-thought, originating from PDM tool used in Leonardo, is that some of the confusion/conflicts in definitions might be removed by thinking in terms of two classes of item:
        • An item that your organisation makes (a "part") and
        • An item that your organisation buys (a "component")
      • Thus a component could still be a high level assembly (e.g. a COTS power supply module or processor card) but is still a non-decomposable item so far as your organisation is concerned.
    • There are many potential actors (users) of a P2654 standard but their involvement is going to differ in line with the role they perform, and what they see of the standard and what they need of it will similarly vary. The list on slide 17 is not comprehensive (e.g. IP integrators are not shown). We're trying to serve many different customers.
    • Each role may bring knowledge that adds to the P2654 picture.
    • P2654 is trying to connect the test applications at the top level (system boundary) to the test "instruments" at the bottom end of the system network.
  • Peter presented his views on vector delivery in slides 21-22.
    • In essence, it doesn't matter what tools are used or what format the vector data is held in, ultimately the IO stream data is the same and when applied at the system boundary will have the same effect.
    • IO stream is probably more accurate a term than "file", although files are typically how "canned" tests may be conveyed.
    • P2654 needs to supply a description of the system network to the generation and result analysis tools.
  • Insufficient time to consider Brad's slide 23.
  • Additional notes added on slides 24-25 of the meeting pack.

7 b) Diagrams and Terms

  • Not discussed during this meeting.

8. Any Other Business

  • {Slide 15}
  • Elections of group officers should be raised at the next TTSC as we probably need to run the election process ahead of the terms of the current officers expiring at the end of the year.

9. Today's Key Takeaways

  • None.  

10. Glossary Terms from This Meeting

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

  • August 31, 2020.
    • Peter expects to be out.
    • No meeting September 7 (Labor Day, US).

12. Topic for next meeting

  • Continue from today.
    • a) Discussion of perspectives on STAM
    • b) Diagrams and Terms

13. Reminders

  • None.

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh