Minutes of P2654 Working Group Meeting No.53, 2020-02-10

Meeting called to order: 11:06 AM EST

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

1. Roll Call

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


By email (non-attendees):

Joel Irby (AMD)
Brian Erickson (JTAG Technologies)

2. Agenda

  • Eric 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 #52, February 3 (draft circulated February 3)
    • No corrections noted.
    • Eric moved to approve, Terry seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • No update on proposed special session at ETS.
  • P1687.1 have discussed the observation that e.g. I2C isn't just the physical interface but also needs the protocol being used to fully define it.

7. Discussion Topics

7 a) Sketch out an outline of the draft

  • {Slide 14}
  • Bullet points recorded during the earlier meetings are now moved to a separate reference file: http://files.sjtag.org/P2654WG/P2654_Reference_Pack.pptx.
  • Draft outline is in slides 17-24 of this week's pack (linked in the heading of these minutes).
  • Discussion of forum post: http://forums.sjtag.org/viewtopic.php?p=1447#p1447
    • Model needs to know something of the physical connectivity.
    • Could be a netlist but may be in other forms too. We should specify the type of data to be supplied, not the format of it.
    • COTS items may be a black box. Possibly something like Asset Intertech's HSDL could be useful (1149.7 uses a similar form of description).
    • For management of access we only need to know about the interfaces, and don't need pin-to-pin information, just which host is connected which client(s).
    • Additional notes added to 6 d) i {slide 19}.
  • Content topics within section 9 expanded textually {slides 22}.
  • Some rules will be mandatory (must have), some are recommendations (nice to have). May be wise to avoid trying to describe things that don't conform.
  • A black box may be compatible or compliant depending on what is supplied. Capabilities of  black box may be declared up-front in a PDL-like format or could be discoverable via a query returning a reference to a PDL-like description. 
  • 1149.10 has a Compliance Verification section at the end of the document. That seems a logical placement.
  • Don't need separate sections to describe compliant vs compatible and to define verifying compliance - both can be covered in one section.
  • Resume next week from section 10.
  • Forum thread for comments on the outline: http://forums.sjtag.org/viewtopic.php?f=3&p=1444#p1444.

8. Any Other Business

  • {Slide 15}
  • IPC APEX: Louis reports that there was little interest from the attendees: A few people made initial enquiries but no follow-ups.
  • LinkedIn: Joel has contacted LinkedIn and determined that we can set up a "company" page for the group. Posts to that page will be public, unlike posts to the SJTAG LinkedIn Group. Posts will probably simply direct to the posts in the Group or, more likely, directly to our website.
  • A major update to the forum software needs to be applied so the forums may be taken out of service for a few hours later in the week.

9. Today's Key Takeaways

  • None.

10. Glossary Terms from This Meeting

  • None.
  • 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.
      • "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.

11. Schedule next meeting

  • February 17, 2020.
    • Absences: Richard.
    • Noted that February 17 is President's Day.

12. Topic for next meeting

  • Continue on outline of the draft from section 10.

13. Reminders

  • None.

14. List New Action Items

  • None.

15. Adjourn

  • Terry moved to adjourn, seconded by Heiko.
  • Meeting adjourned at 12:00 Noon EST

Respectfully submitted,
Ian McIntosh