Minutes of P2654 Working Group Meeting No.104, 2021-04-12

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_104.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)
Eric Cormack (DFT Solutions) (joined 11:42)
Terry Duepner (National Instruments)
Heiko Ehrenberg (GOEPEL Electronics)
Brian Erickson (JTAG Technologies)
Peter Horwood (Digital Development Consultants Ltd)
Joel Irby (AMD)
Richard Pistor (Curtiss-Wright)
Jon Stewart (Dell)
Brad Van Treuren (VT Enterprises Consulting Services)
Louis Ungar (A.T.E. Solutions)

Guests:
---

By email (non-attendees):
---

Excused:
Bill Huynh (Marvell Inc.)
Carl Walker (Cisco Systems)
Tom Thompson (for IEEE)

2. Agenda

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

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • P1687.1: Action on Brad/Michele to select slides from the pack that has been shared here that are pertinent to that effort, noting that P1687.1 is addressing a specialism with set assumptions whereas P2654 is addressing generics.

7. Discussion Topics

7 a) Continue definition of 'Transformation' and diagramming

  • {Slide 14}
  • Question seems to be "Does Transformation happen only the dashed lines in Peter's diagram (slide 71) or are there transformations through the stages in between?"
  • Probably needs to be a transformation at the dashed lines as that would be all that is available for an "IP protected" COTS sub-assembly. But you could potentially have intermediate transformations if you have sufficient information on the workings inside a sub-assembly.
  • Bullet point on slide 70 didn't quite capture Terry's intended point from the previous meeting as the presumption of an I2C script was not part of the scenario.
  • Explanation, using slides 73 and 41 of the different route taken by "injection" (e.g. of a SVF) to that taken through retargeting.
  • Could have a number of scenarios we need to support:
    • Where there is a functional system, including operational software,
    • Where there is a degree of assembly but no operational software and so there is reliance on the hardware IP (e.g. FPGA firmware) to operate interfaces,
    • Where there is no firmware but interfaces can be controlled indirectly (e.g. using JTAG to bit-bang an I2C bus from a FPGA).
  • Do we care which of these performs the transformation? Perhaps not, but it might influence the approach P2654 needs to take and what it might be feasible to do.
  • P2654 provides a means to orchestrate tests that require multiple interfaces to co-operate.
  • IEEE 1149.6 could be argued to offer some degree of "functional" testing, but the intent was to improve structural testing of ac-coupled paths.  But structural testing is still important for system test as it can provide a check that the system has been assembled correctly.  Structural testing could in fact involve analog signalling between modules as well as digital signalling.
  • P2654, supported by appropriate tooling, could allow a test developer to produce effective tests without necessarily needing to know that JTAG or I2C or SPI, etc. are being involved.
  • Tests could evolve as the product matures, possibly without altering the "top-level" test software.
  • It will be essential to ensure that readers of the standard can grasp the separation between the modelling and the hardware implementation.
  • Slide 74 is the start of an attempt to see if the themes we have discussed could applied to an arrangement of instruments (or sub-systems) around a sub-system under test (this may be broader than the scope that Terry had originally envisioned). 
  • Further notes are recorded on slide 72.

8. Any Other Business

  • {Slide 15}
  • SJTAG.org website is scheduled to be upgraded/migrated in the coming weeks. This may result in some brief site downtime.

9. Today's Key Takeaways

  • None.

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

  • April 19, 2021

12. Topic for next meeting

  • Continue definition of 'Transformation' and diagramming.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh