Minutes of P2654 Working Group Meeting No.167, 2022-10-31

Meeting called to order:  11:03 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)

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

1. Roll Call

Ian McIntosh (Leonardo) (chair)
Eric Cormack (DFT Solutions)
Heiko Ehrenberg (GOEPEL Electronics)
Brian Erickson (JTAG Technologies)
Joel Irby (Self)
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)


2. Agenda

  • Brad moved to accept the agenda, seconded by Eric, 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 #166, October 24 (updated draft circulated October 26)
    • Brad moved to approve, seconded by Eric, no objections or abstentions → Approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • Brad has passed on our observations from the last meeting (wrt P1687.1 outline), Jeff has acknowledged that there may be things there that need added to the P1687.1 document.

7. Discussion Topics

7 a) Compare P2654 structure with Jeff's outline (clause 8.2.1 onwards)

  • {Slide 17}
  • Compare outline for P1687.1 standard (https://ieee-sa.imeetcentral.com/p/aQAAAAAE-qIF) with the outline in the latest revision of our document (https://ieee-sa.imeetcentral.com/p/aQAAAAAE95fm) - comparing headings from 8.2.1 onwards.
  • Are ProtoBufs the only way to go?  We need a common method for conveying the information and that's what the ProtoBuf gives us.
  • We inserted a new clause 9 and sub-clauses last week to cover the APIs.
  • Talked through the ProtoBuf example for JTAG/1149.1.  As this is a specific example it can't really be part of the normative aspect of the standard - not every case will need 1149.1 and we need to distil out the rules for the generic case. 
  • Rules would probably cover:
    • ProtoBuf version 3 is to be followed,
    • Enumeration,
    • Types of messages,
    • Assigning unique IDs per sending node, etc.
  •  However, we probably need examples to illustrate how the rules are to be applied and these should go into an Appendix.  Added Appendix B for Transfer Procedure examples, and Appendix C for Command examples (top-down flow, e.g. applying a SVF).
  • "Specification" heading should be an empty container for the Rules, Permissions, etc., sub-clauses.
  • We maybe have some commonality on Portability with P1687.1 as we both expect to be used by EDA tooling. Security might be different as we don't want to impose anything and in many cases security will be embedded within the data streams we pass, hence the importance of serialization.
  • Wrappers are generic but Black Boxes might not conform to the ProtoBufs, especially in the case of Black Box to Black Box messages that may use proprietary formats. Added a note on this in 5.1.
  • Current WiP document is now IEEESTD-P2654_Draft_D02_BGVT_20221031.docm, on iMeetCentral at https://ieee-sa.imeetcentral.com/p/aQAAAAAE-30o

8. Any Other Business

  • {Slide 18}
  • Replacement SJTAG server: The File Manager and Forums have now been moved over (URLs are unchanged).  The Wiki and main site should get moved during the coming week.

9. Takeaways:

  • None. 

10. Glossary: 

  • None.
  • Carried over:
    • 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

  • November 7, 2022
    • "Normal" time for everyone.
    • Eric will be out; Joel is likely to be out.

12. Topic for next meeting

  • Brad hopes to present the Generic Figures he is working on.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

  • Eric moved to adjourn, seconded by Carl.
  • Meeting adjourned at 12:02 PM EDT

Respectfully submitted,
Ian McIntosh