Minutes of P2654 Working Group Meeting No.74, 2020-08-03

Meeting called to order: 11:03 AM EDT

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

1. Roll Call

Ian McIntosh (Leonardo)
Eric Cormack (DFT Solutions) (joined 11:21)
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)
Jan Schat (NXP Semiconductors)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco Systems)

Guests:
---

By email (non-attendees):
---

Excused:
Richard Pistor (Curtiss-Wright)
Jon Stewart (Dell)

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 #73, July 27 (draft circulated July 27)
    • No corrections advised.
    • Terry moved to approve, Carl seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • 1149.7 is preparing to go to ballot; Ballot group formation notices can be expected shortly.

7. Discussion Topics

7 a) Diagrams for Standard

  • {Slide 14}
  • Previously discussed:
    • AccessLink, Access Point, Access Interface need explanatory diagram; Hierarchy; Order vs Timing.
  • Suggestion from Ian: Flow of modelling information vs conventional view of flow of test control and data.
  • Brad had given a glimpse of some diagrams at the previous meeting and now expended on those {slides 59-61 and 64-74}.
    • Intent was cover the physical aspects (section 5.1 of our Outline {slide 18}).
    • Brad had started with a diagram Jeff Rearick had used in P1687.1, then developed a similar diagram to show P2654 networks.
    • "Assembly Interface" is used as that was our generic term to abstract from device/board/module etc., and could be the Access Interface.
    • The Assembly Interface is probably what is seen by the sending side so if the interface is bidirectional then it really encompasses the arrows, spanning between the blue boxes.
    • Brad ran through a series of diagrams describing different views of IEEE 802, picking out notable aspects that each highlighted:
      • Slide 65: Bridging represented at the ATM-to-LAN conversion stage. 
      • Slide 66: Notion of Medium Independent Layers and Medium Dependent Layers - separating out common aspects from elements that are specific to the physical implementation.
      • Slides 68-70: Framing of packets by successively wrapping for each protocol layer that must be negotiated.
      • Slide 71: A redirector performs a function similar to our bridge.
    • Questions from slide 61: Do we represent context from a physical or modeling perspective?
      • Likely both. Hardware people probably need to see the physical side while tool creators will want to see the modelling side.
    • Can P2654 Network be inferred from CAD data or does it need a new description format like 1149.7 does with HSDL.7?
      • CAD data will only tell you about connectivity. You may be able to infer some purpose from signal names but you couldn't easily know how ports on one side of a device might relate to ports on the other side.
    • What are the types of P2654 Networks? Serial? Bused? Parallel/Digital?
      • Probably don't want to constrain this.  But could complexity become self-limiting, e.g. for a dynamic, embedded application?
    • Or should we represent data message context with host and client interfaces binding assemblies
      over P2654 Networks? Or is that a diagram of the Access and Data Link Layers?
      • A software query/response allows access without necessarily exposing the IP contained in sensitive assemblies. For a single board you may have direct access to/knowledge of the interfaces described by standards, but that's less likely at the top level of a system. May be a question about what a P2654 compliant device (assembly?) needs to present.
    • Further notes on slides 62-63 of the meeting pack.

7 b) Definitions from forum

  • Absorbed into 7a) but not discussed during this meeting.
  • Previously discussed:
    • Callback; AccessLink, Access Point, Access Interface; Component; Device; Hierarchy; BIST/BIT.

8. Any Other Business

  • {Slide 15}
  • None.

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 10, 2020.

12. Topic for next meeting

  • Continue from today, perhaps pick up further on the questions posed by Brad today.
    • a) Diagrams for Standard
    • b) Definitions from forums

13. Reminders

  • None.

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh