Minutes of P2654 Working Group Meeting No.15, 2019-04-08

Meeting called to order: 11:07 AM EDT

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

1. Roll Call

Ian McIntosh (Leonardo)
Heiko Ehrenberg (GOEPEL Electronics)
Terry Duepner (National Instruments)
Brian Erickson (JTAG Technologies)
Peter Horwood (Firecron Ltd.)
Bill Huynh (Marvell Inc.)
Joel Irby (Arm)
Richard Pistor (Curtiss-Wright) (joined 11:14)
Jan Schat (NXP Semiconductors)
Naveen Srivastava (Nvidia)
Jon Stewart (Dell) (joined 11:08)
Brad Van Treuren (No affiliation) (joined 11:12)
Carl Walker (Cisco Systems)


By email (non-attendees):

Eric Cormack (DFT Solutions)
Louis Ungar (A.T.E. Solutions)

2. Agenda

Brian moved to accept the agenda as proposed, seconded by Terry, no objections.

3. IEEE Patent Slides

  • {Slides 5-9}
  • Patent slides reviewed.
    • No comments.

4. Review and Approve Previous Minutes

  • {Slide 10}
  • Meeting #14, April 1 (updated draft circulated April 3)
    • No further corrections noted.
    • Terry moved to approve, Carl seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Discussion Topics

6 a) Differences between retargeting and transformation cases (continuation) {Slide 12}

  • As Brad was on voice only, Ian re-shared the slide on the definitions for Retarget and Transform used last week  (http://files.sjtag.org/P2654WG/Transformation_vs_Retargetting_Meeting_14.pdf) {slide BGVT 2}.
  • Some email discussion had arisen over the use of "patterns" and "vectors" in the definition of Retarget. Brad referenced his second last response in the email thread, proposing the revision:
    • Retarget: to translate an instrument pattern to one or more network-level patterns using the same protocol and structure would be better.
  • A pattern could be anything, but a vector is really just series of numbers.
  • A pattern may be a sequence of events? "Event" is an overloaded term, but a pattern is a single transaction but may have several steps involved in performing it.
  • A serial to parallel conversion would be a Transform rather than a Retarget operation.
  • "State" may also be overloaded: Could refer to "model state" being used to update the "hardware state" via an iApply or a logic state of a pin or an interrupt/push model request for service.
  • Jan suggested the following NXP terminology:
    • A node state may be low, high, don't care, undefined, high-Z and perhaps clock pulse.
    • A set of states is a vector.
    • A sequence is an ordered list of states on a node.
    • A pattern is an ordered list of vectors.
  • Are we free to make these definitions?  Are any reserved IEEE definitions?  There does not appear to be any formal definitions to follow and many standards make basic assumptions that terms are known/defined meaning that many terms have no precise definition.  TTSC are pushing to unify definitions across test standards.
  • May qualify terms to help with disambiguation, e.g. "STAM pattern" instead of just "pattern".
  • Key is that people understand what interpretation we intend when we use these expressions.

7. Any Other Business

  • {Slide 13}
  • None.

8. Today's Key Takeaways

  • None.

9. Glossary Terms from This Meeting

  • "State", "Vector", "Sequence" and "Pattern" as proposed above.
  • 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, Retargetting.
    • 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.

10. Schedule next meeting

  • April 15, 2019.
    • Joel will be out.
  • April 22, 2019 will be Easter Monday
    • Peter and Joel will be out - decide next week if we are likely to have a quorum.

11. Topic for next meeting

  • Update from TTSC meeting.
  • Differences between retargeting and transformation (continuation).

12. Reminders

  • TESTA preparation discussion to follow immediately after this meeting.

13. List New Action Items

  • None.

14. Adjourn

  • Terry moved to adjourn, seconded by Peter.
  • Meeting adjourned at 11:52 AM EDT

Respectfully submitted,
Ian McIntosh