Minutes of P2654 Working Group Meeting No.182, 2023-03-13

Meeting called to order:  11:06 AM EDT

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

Reference pack 1 is located here: http://files.sjtag.org/P2654WG/P2654_Reference_Pack.pptx (all 2020 material)
Reference pack 2 is located here: http://files.sjtag.org/P2654WG/P2654_Reference_Pack_2.pptx (all 2021 material)
Reference pack 3 is located here: https://files.sjtag.org/P2654WG/P2654_Reference_Pack_3.pptx (all 2022 material)

iMeetCentral site: https://ieee-sa.imeetcentral.com/sjtag-sg/ 

1. Roll Call

Ian McIntosh (Leonardo) (chair)
Heiko Ehrenberg (GOEPEL Electronics) (joined 11:08)
Brian Erickson (JTAG Technologies)
Richard Pistor (Curtiss-Wright)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco Systems)

Tom Thompson (for IEEE) (left 12:02)

Eric Cormack (DFT Solutions)

2. Agenda

  • Brad proposed a change to the main discussion topic. 
  • Brad moved to accept the agenda as amended, seconded by Carl, no objections.

3. IEEE Slides

  • {Slides 5-13}
  • Patent, Copyright and Behavior slides reviewed without comment.

4. Review and Approve Previous Minutes

  • {Slide 14}
  • Meeting #181, March 06 (draft circulated March 06)
    • One correction: Delete joining time from the attendance record against Louis' name.
    • Brad moved to approve with the above amendment, seconded by Carl, no objections or abstentions → Approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • None.  

7. Discussion Topics

7 a) IEEE P2654 Architecures & Concepts

  • {Slide 17}
  • Discussion of presentation on iMeet at https://ieee-sa.imeetcentral.com/p/aQAAAAAFB-bJ - Note that this is a Work-in-Progress draft, in which Brad retains copyright but grants IEEE the rights to use.
  • Comparison of the scopes of both P2654 and P1687.1, highlighting the much simpler remit for the latter.
  • Hardware Module Categories: Works left-to-right from hosts through to clients, and results in the bottom (black) boxes being the ultimate simplification (abstraction) of what is represented above.
  • This is carried over onto the slide on Scalability of H/W design, using Fig 7 from the 1687 standard.
  • Similarity of Architecture Models: The H/W architecture models maps quite cleanly onto the P2654 S/W architecture Model.
  • Examples of problems that P2654 is trying to solve: Provides a simpler way of representing the problem space, but at this stage is still just a representation of the problems - it offers no solutions yet.
  • Non-normative IEEE 2654 Concept Example, slide 11.
  • Slide 12 takes the problem example from slide 10 and re-draws it as tree of nodes, noting that the Configured FPGA is now shown as comprising three nodes: One to represent the 1149.1 client and one each for the I2C and SPI hosts.
  • Moved on to what is basically a generalised node architecture (where the translator is a common element that gains speciality from the plugin libraries that surround it) and then to show scalability.
  • Examples of:
    • Client Modules
    • Intermediate Modules
    • Host/Controller Modules - Black diamond represents a S/W interface
    • Trunk Modules - coordintors of the Host/Controllers
  • Very quickly run over Layers of Interconnection.
  • Current WiP document remains IEEESTD-P2654_Draft_D03_BGVT_20230227.docm, on iMeetCentral at https://ieee-sa.imeetcentral.com/p/aQAAAAAFBHNU

8. Any Other Business

  • {Slide 18}
  • Elections - no progress to report

9. Takeaways:

  • None. 

10. Glossary: 

  • None (forthcoming as Brad’s Excel spreadsheet)
  • Carried over:
    • 2654 Interface Translator Node (2654ITN)
    • Translator: See 2654 Interface Translator Node (2654ITN)
    • Transfer Channel, replacing P2654 Message Channel
    • 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.

11. Schedule next meeting

  • March 20, 2023.
    • Heiko may be absent March 27.

12. Topic for next meeting

  • Continue presentation.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh