Minutes of P2654 Working Group Meeting No.71, 2020-06-29

Meeting called to order: 11:06 AM EDT

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

1. Roll Call

Ian McIntosh (Leonardo)
Terry Duepner (National Instruments) (joined 11:32)
Brian Erickson (JTAG Technologies)
Peter Horwood (Digital Development Consultants Ltd)
Bill Huynh (Marvell Inc.)
Joel Irby (AMD)
Richard Pistor (Curtiss-Wright) (joined 11:10)
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:
Heiko Ehrenberg (GOEPEL Electronics)

2. Agenda

  • Brad moved to accept the agenda, seconded by Joel, no objections.

3. IEEE Patent Slides

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

4. Review and Approve Previous Minutes

  • {Slide 11}
  • Meeting #70, June 22 (draft circulated June 22)
    • No corrections advised.
    • Brian moved to approve, Carl seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • TTSC meeting is next week.  One topic on the agenda is a suggestion, published in EE Times, that IEEE should drop the use of the terms Master/Slave in Standards (https://www.eetimes.com/its-time-for-ieee-to-retire-master-slave/#).  However, it is not clear that IEEE is actively considering this at the present time. 

7. Discussion Topics

7 a) Definitions from forum

  • {Slide 14}
  • Callback: 
    • Discussed last week.
    • We already have a qualified definition as STAM Callback.  This is more like the classical definition of a callback.
  • AccessLink
    • Previous discussions developed the terms Access Point (derived from IEEE 802.11 in contexts similar to STAM) and then Access Interface (proposed by Michele Portolan in the P1687.1 group). These latter two provide more abstracted representations.
    • In 1687, AccessLink is expected to provide a mapping of pins to ports, whereas the Access Interface is really only concerned with the port information.
    • AccessLink was intended to convey control (e.g. addressing, set-up) information as distinct from DataLink which carries the "payload".
    • AccessLink, Access Interface and Access Point are all quite similar so need supporting diagrams to remove ambiguity and show the distinction (or are we overloading terms onto single concept?)
    • We have AccessLink, Access Point and Access Interface defined in our wiki currently.  
    • AccessLink probably needs to be considered alongside DataLink.
    • Control information and data may travel along the same signal paths or distinct signal paths, or control information may be embedded within the protocol of the data stream. May need further diagrams to help illustrate these different cases. 
  • Further notes recorded on slides 51-53 of the meeting pack.

7 b) Diagrams for Standard

  • Absorbed into 7a).
  • Brad introduced the context diagram he mentioned last week, prepared by Jeff Rearick (slide 54 of the meeting pack).

8. Any Other Business

  • {Slide 15}
  • None.

9. Today's Key Takeaways

  • AccessLink (and associated terms) need diagrammed for clarity.
  • Risk of overloading multiple terms onto single features/concepts.  

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

  • July 13, 2020.
    • [Post meeting note] Richard will be out.

12. Topic for next meeting

  • Continue from today:
  • a) Definitions from forums
  • b) Diagrams for Standard

13. Reminders

  • None.

14. List New Action Items

  • None.

15. Adjourn

  • Terry moved to adjourn, seconded by Peter.
  • Meeting adjourned at 12:04 PM EDT

Respectfully submitted,
Ian McIntosh