Minutes of P2654 Working Group Meeting No.168, 2022-11-07

Meeting called to order:  11:05 AM EST

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)
Heiko Ehrenberg (GOEPEL Electronics)
Brian Erickson (JTAG Technologies) (dropped mid-meeting)
Joel Irby (Self)
Richard Pistor (Curtiss-Wright)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco Systems)


Eric Cormack (DFT Solutions)
Tom Thompson (for IEEE)

2. Agenda

  • Brad moved to accept the agenda, seconded by Joel, 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 #167, October 31 (updated draft circulated November 2)
    • Brad moved to approve, seconded by Carl, no objections or abstentions → Approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • Brad presented new material to P1687.1, bridging between 1687, P1687.1 and P2654.  More P1687.1 oriented.

7. Discussion Topics

7 a) Generic Figures (Brad)

  • {Slide 17}
  • The material presented to P1687.1 (on iMeet at https://ieee-sa.imeetcentral.com/p/aQAAAAAE-8av). 
  • Slide 2 is extracted from the 1687 standard.
  • Slide 3 supports a discussion of Translation as a software modelling alternative to Retargeting. Trnaslation needs a configuration description as well the "rules".  A key differentiator between Retargeting and Translation is timeliness - for P2654 and interactive testing we need quicker response time, which Translation should give. 
  • Slide 4 converts the preceding circuit into a tree-graph in 1687.1 terms.  Argument in P1687.1 that Mask should perhaps be Enable?  Transform Engine equates to Translator - we probably prefer Translator as term.
  • Slide 5, as above but for the P2654 context.
  • Slide 6 is the 1687 to 1149.1 transaction shown one step at a time.
  • Slide 7: Title: Swap SPI with 1687 for consistency.  Note that this replaces the 1149.1 access link entirely.  SPI notation scheme is an arbitrary example.
  • Slide 8 is the 'final' generalization.
  • We inserted a new clause 9 and sub-clauses last week to cover the APIs.  Rules used to establish agreement on the messages exchanged. The Translator validates the messages and should return an error to the sender if it doesn't recognise the message.
  • Slide 9 is a slightly reworked version of the diagram that Jeff has been using.
  • Slides 8 and 9 are probably the diagrams most relevant to us.  
  • Current WiP document remains 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: Essentially complete and using SSL.  Some small issues to tidy up.
  • Heiko looking for additional co-hosts (IEEE-SA Webex account holders) to be able to start the P1149.1 meeting this week.

9. Takeaways:

  • None. 

10. Glossary: 

  • 2654 Interface Translator Node (2654ITN)
  • Translator: See 2654 Interface Translator Node (2654ITN)
  • 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 14, 2022
    • Heiko likely to be out next week and the following week; Joel is likely to be out.

12. Topic for next meeting

  • Resume discussion of document structure.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh