Minutes of P2654 Working Group Meeting No.107, 2021-05-03

Meeting called to order: 11:05 AM EDT

The slide references relate to the pack used during this meeting, located here: http://files.sjtag.org/P2654WG/P2654_Meeting_107.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)
Terry Duepner (National Instruments)
Brian Erickson (JTAG Technologies)
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)

Guests:
Tom Thompson (for IEEE)

By email (non-attendees):
---

Excused:
Bill Huynh (Marvell Inc.)
Eric Cormack (DFT Solutions)

2. Agenda

  • Brian moved to accept the agenda, seconded by Carl, 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 #106, April 26 (draft circulated April 26)
    • No corrections noted.
    • Terry moved to approve, Carl seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • Nothing advised.

7. Discussion Topics

7 a) Review standard template and initial layout

  • {Slide 14}
  • Latest draft on iMeet is D01 from November 2020, however Brad has markups from December 7 and December 14 indicating where diagrams might be used and which types might be appropriate. Eric had confirmed prior to the meeting that he had done no work since the D01 draft, so Brad's markups have not been included.  Markup files were copied to the "Drafts/Group Submission" folder during the meeting.
  • Navigation of the iMeet site was demonstrated: On reaching the workspace "Home" page, select the "Files & Discussions" tab and open the "Drafts" folder.  The "Drafts in Progress" folder will hold working copies of the drafts during editing, "Mature Drafts" will in time hold stable versions that are candidates for formal review/balloting.  It is suggested that submissions from members go into the "Group Submissions" folder. The Editor can then pick up material from there to incorporate into the working draft.
  • Brad has today made further markups to place some existing diagrams in the relevant places, although these will need to be re-worked to meet IEEE-SA requirements.
  • Jeff Rearick is proposing a change of terminology in P1687.1, replacing "Transformations" with "Transfer Functions". This arises from considerations of commonality of purpose with P1687.2 where Transformation is a less meaningful description (see slide 78).
  • In the right hand diagram, the transfer functions in effect emulate the process that a test engineer would go through to manually detail a test, e.g. accounting for amplification in the analog path.
  • Some observations on problems with 1687 PDL keywords as they apply to the analog domain (effects may be wider): iMerge (detailing code that can be run in parallel), iTake (take exclusive control of the execution flow), nested iCall and nested iMerge.
  • In a 1687 environment, EDA tools may require additional information on how bits are mapped that is not available from the current 1687 implementation. P2654 doesn't actually need that mapping.
  • Concurrency in P2654 could exist above anything embodied by 1687's iMerge: Could tiers of concurrency present a problem? Should not - the lower level concurrency will happen as a side effect and things will ripple up at the same time.  
  • Transfer Function is being proposed as common terminology that would apply to both analog and digital domains equally.
  • Noted that current examples don't realy consider where there may be multiple inputs to (or multiple outputs from) a circuit under test.  Timing of input application to analog circuits is maybe less important that for digital circuits that may be locked to clocks.
  • Management of drafts:  There is essentially a workflow of Group Submission → Draft in Progress → Mature Drafts.  Probably best to leave it to the Editor to incorporate from Group Submissions into Drafts in Progress [post meeting note: However, anyone can post comments against the files in Draft in Progress at any time].
  • While iMeet includes a word document viewer it cannot handle .docm formats (as used by the draft) nor does it show any revision markings that might be included, hence it recommended to download a local copy of the document - but do not use the Download and Lock feature (leave that for the Editor)!
  • How does the modelling deal with the case where the testing of an item depends on the control of a component part that is physically below it in the design hierarchy, e.g. where the GPIO in the example is required to test the Target Sub-Assy? the Test target must be transforming the data used in its own test - is this a problem?

8. Any Other Business

  • {Slide 16}
  • None.

9. Today's Key Takeaways

  • Proposal to replace "Transformations" with "Transfer Functions".

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

  • May 10, 2021

12. Topic for next meeting

  • Review standard draft in more detail - Section 4.

13. Reminders

14. List New Action Items

  • [107.1] All: Check access to iMeet site and look over current draft structure.

15. Adjourn

  • Brad moved to adjourn, seconded by Jon.
  • Meeting adjourned at 12:03 PM EDT

Respectfully submitted,
Ian McIntosh