P2654 WG Minutes - 2022-11-21

Minutes of P2654 Working Group Meeting No.170, 2022-11-21

Meeting called to order:  11:07 AM EST

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

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)
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)

Guests:
Tom Thompson (for IEEE)

Excused:
Heiko Ehrenberg (GOEPEL Electronics)
Joel Irby (Self)

2. Agenda

  • Eric moved to accept the agenda, 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 #169, November 14 (draft circulated November 14)
    • Eric moved to approve, seconded by Carl, no objections or abstentions → Approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • 1149.4 is forming a ballot group.  Question on extent of use, noted that there are currently no commercial parts offered (TI withdrew the two parts that were offered after acquisition of Nat Semi) - these were 5V only on the interface so of limited use in newer designs. Mixed signal ASICs are probably the only place they are still used.  Test tooling does offer support for the standard.

7. Discussion Topics

7 a) Document structure

  • {Slide 17}
  • Continue with populating the API definition at clause 9.4.2.1 for the create method and its arguments.
  • Much of this will need to be refined but it sets out a template on how we should continue for other methods and APIs.  Some things that might need to be considered in due course:
    • May want to change, e.g. children_uid to child_uid for readability.  Such names can be revised later
    • Some of the rules for the arguments may become sub-rules tied to some common element.
    • Use string types or char *?
    • Do we have empty lists or NULL?
    • Need to take care when selecting 'shall' (rule) vs 'may' (permission).
  • Not useful to pursue editing in this manner extensively during the meeting - better that bulk is done off-line.
  • Current WiP document is now IEEESTD-P2654_Draft_D02_BGVT_20221121.docm, on iMeetCentral at https://ieee-sa.imeetcentral.com/p/aQAAAAAE_cVQ. 

8. Any Other Business

  • {Slide 18}
  • None.

9. Takeaways:

  • None. 

10. Glossary: 

  • None
  • 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

  • November 28, 2022

12. Topic for next meeting

  • Continue discussion of document structure.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh