P2654 WG Minutes - 2023-03-06

Minutes of P2654 Working Group Meeting No.181, 2023-03-06

Meeting called to order:  11:04 AM EST

The slide references relate to the pack used during this meeting, located here: 
http://files.sjtag.org/P2654WG/P2654_Meeting_181.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)
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)
Eric Cormack (DFT Solutions)
Heiko Ehrenberg (GOEPEL Electronics) (joined 11:05)
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:
---

Excused:
Tom Thompson (for IEEE)

2. Agenda

  • Eric moved to accept the agenda, seconded by Brad, 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 #180, February 27 (draft circulated February 27)
    • No corrections
    • Brad moved to approve, seconded by Heiko, no objections or abstentions → Approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 16}
  • Brad noted hat Tom Thompson is due to speak to P1687 on Wednesday at 10:oo AM Eastern on Open Source and how it might be used to further the Language discussions.  If anyone is interested then contact Martin Keim and request in invite.
  • Ian noted that in a change of IEEE-SA policy the WG Chair Fundamentals training is no longer mandatory for WG chairs.  

7. Discussion Topics

7 a) Continue discussing Sequence Diagrams: Debug/Diagnostic, Command Flow

  • {Slide 17}
  • DebugCommandFlow.puml:
  • Anything related to p[arsing the debug output is outside the scope of the Translator API.
  • At 4. HandleRequest, are we missing parameters on this call, e.g to detail the XXRequest that is to be handled? No, because HandleRequest is conveying an RVF packet which will contain meta data that details this.
  • There is an assumption that this is all within the scope of a single system/control computer.
  • CommandFlow.puml:
  • Very large and complex diagram, will be difficult to fit in a single page (or perhaps even across two pages).
  • thePDLInstance is a "singleton"* and should really be contained within the OPT box where it gets instantiated.  The same goes for theSymbTblInstance and theModelInstance.
  • * With a singleton, it is intended that only one instance is ever created that all object refer to, and will typically have a getInstance method that if the instance is NULL will create the instance and return the handle to it, otherwise it will simply return the existing handle.
  • CommandFlowRun.puml:
  • Breaks out the Run element from the diagram. This is much simpler and more compact. 
  • What do we lose by simplifying the larger diagram in this way, perhaps losing the singletons?  Very little as it should be obvious to anyone that's familiar with implementing parser that there can only be e.g. a single symbol table to reference.
  • We need to see what the upper part of the CommandFlow diagram would like if simplified in the manner of CommadnFlowRun.
  • 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:

  • Simplified diagrams are desired. Command Flow needs to be simplified. 

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

  • March 13, 2023.

12. Topic for next meeting

  • Review simplified diagrams.

13. Reminders

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh