Minutes of P2654 Working Group Meeting No.127, 2021-10-18

 Meeting called to order:  11:05AM EDT

The slide references relate to the pack used during this meeting, located here: 

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)
Peter Horwood (Digital Development Consultants Ltd) (joined 11:16)
Joel Irby (AMD) (joined 11:17)
Richard Pistor (Curtiss-Wright)
Jon Stewart (Dell)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco)

Tom Thompson (for IEEE)

Bill Huynh (Marvell Inc.)
Heiko Ehrenberg (GOEPEL Electronics)
Brian Erickson (JTAG Technologies)
Louis Ungar (A.T.E. Solutions)

2. Agenda

  • Terry moved to accept the agenda, seconded by Jon, 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 #125, October 4 (draft circulated October 4)
    • No corrections noted.
    • Brian moved to approve, seconded by Carl, no objections or abstentions → minutes approved.
  • {Slide 12}
  • Meeting #126, October 11 (draft circulated October 11)
    • Noted that as the meeting had no quorum these are 'notes' rather than formal 'minutes'.
    • No corrections noted.
    • Brian moved to approve, seconded by Carl, no objections or abstentions → notes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 14}
  • None.

7. Discussion Topics

7 a) Continue Review of Standard Draft

  • {Slide 15}
  • Continuing review, starting at top of page 11.
  • Brad's new PUML Request-Response diagram should serve as the "simple" replacement suggested by the existing note. This is drawn with the Child at the top (above the Parent) in order to better illustrate that as the source of the request.
  • Brad introduced article on "Orchestration vs Choreography" (central control versus autonomous action): https://medium.com/@jacobsee/microservice-coordination-at-a-high-level-f588917bc7e7. Retargeting is orchestration, P2654 is more choreography.  Article uses JSON notation to describe microservices.
  • Looking at clause 4.2, Relationship to other Standards, we had drafted a list of potentially relevant standards and interface types during the Study Group phase. This file was located. It includes the formal standards and industry standards such as I2C, SPI, etc., as well some general concepts, e.g. indirect access via a programmable controller (FPGA, CPLD, microcontroller, Arduino or Raspberry Pi module, etc.).  This could possibly be considered as a 'bridge'. Equally, it might apply to a COTS item/Black Box that sits in the path.  
  • We probably don't want this to imply any dependency but we do want to support/exploit these other standards where we can.  Maybe don't want to try to list all, but leave open the inference of what can be supported. perhaps talk about CSU types and memory mapped register types.
  • "Standardised but open" - let implementors define behaviours.
  • There will be omissions from the list, e.g. JESD DDR5 is coming along.  Might be able to get some of the material being presented to P1581 shared here to see if we can fit that to our model.
  • Version edited today saved as IEEESTD-P2654_Draft_D01_BGVT_20211018.docm in the Drafts/Group Submissions folder.

8. Any Other Business

  • {Slide 16}
  • None.

9. Glossary: 

  • None.
  • Carried over:
    • Network will need to be defined
    • PTPG - Programmable Test Pattern Generator/Generation
    • Better define structural test boundary vs functional test
    • Transfer module/library
    • Injection transfer module/library
    • RVF Message (to be refined)
    • RVF Command (to be refined)
    • "Tooling" - need to be clear on what is meant.
    • "True System".
    • Comment that "End-User" is subject to perspective and so needs to be qualified.
    • 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.

10. Takeaways:

  • None. 

11. Schedule next meeting

  • October 25, 2021
    • Louis and Tom will be absent

12. Topic for next meeting

  • Continue review of standard draft
    • IEEESTD-P2654_Draft_D01_BGVT_20211018.docm
    • Start at clause 4.3.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

  • Brad moved to adjourn, seconded by Jon.
  • Meeting adjourned at 11:56 AM EDT

Respectfully submitted,
Ian McIntosh