Minutes of P2654 Working Group Meeting No.102, 2021-03-22

Meeting called to order: 11:08 AM EDT

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

The cumulative reference pack is located here: http://files.sjtag.org/P2654WG/P2654_Reference_Pack.pptx (updated Dec 31, 2020)

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

1. Roll Call

Ian McIntosh (Leonardo) (chair)
Terry Duepner (National Instruments)
Heiko Ehrenberg (GOEPEL Electronics)
Brian Erickson (JTAG Technologies)
Joel Irby (AMD)
Richard Pistor (Curtiss-Wright)
Jon Stewart (Dell)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services) (joined 11:12)
Carl Walker (Cisco Systems)

Guests:
Tom Thompson (for IEEE)

By email (non-attendees):
---

Excused:
Bill Huynh (Marvell Inc.)
Eric Cormack (DFT Solutions)
Peter Horwood (Digital Development Consultants Ltd)

2. Agenda

  • Joel moved to accept the agenda, seconded by Terry, no objections.

3. IEEE Patent Slides

  • {Slides 5-10}
  • Patent and Copyright slides reviewed without comment.

4. Review and Approve Previous Minutes

  • {Slide 11}
  • Meeting #101, March 15 (updated draft circulated March 17)
    • No further corrections noted.
    • Brad moved to approve, Terry seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • None.

7. Discussion Topics

7 a) Outline documentation from concept descriptions

  • {Slide 14}
  • Email discussion on 'Transformation' prior to meeting. Further discussion deferred until Peter can be on the call.  Question summarised on slide 68.
  • What we have for now is still just propositions, there is no settled position we can document.
  • Suggestion to attempt to draw out a Use Case that represents the broader interests of those on the group (slide 69).
  • Important to ease people through the transition from the view of the physical, hardware hierarchy through the abstraction and into the model space.
  • Draw a system of sub-systems where each sub-system used a different bus.
  • For a COTS sub-system, expect to be able to use some predefined (by the vendor) set of commands.  Treat the COTS item as a single entity even if it is a collection of boards (we may have no knowledge of construction anyway). 
  • Show a case where one sub-system is commanded to output something that is then read by a different sub-system - this is a common operation.  Can infer that each sub-system will comprise at least one PCB.  Want to be able to perform testing without reliance on system software (but perhaps a test load of software needed since our example uses USB). 
  • Illustrate simple use of PDL that would implement such an interaction. PDL for the register/device/instrument level is effectively re-used at the system level (although it needs transformed/retargeted to account for the path to the register/device/instrument).
  • A sub-system may have a "controller" on Ethernet that commands other PCBs within the sub-system over PCIe. This case has a presumption of some level of software load exists on all PCBs. (this case was not fully explored during the meeting and is to be continued).

8. Any Other Business

  • {Slide 15}
  • AutoTestCon cancelled again for 2021; Louis looking looking for other similar events where P2654 could feature.

9. Today's Key Takeaways

  • None.

10. Glossary Terms from This Meeting

  • None.
  • Carried over:
    • 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 29, 2021
    • Return to usual 11 AM EDT, 4 PM BST timing.
    • Louis will be absent.
  • April 4 is Easter Sunday, may affect attendance for April 5.

12. Topic for next meeting

  • Continue Use Case diagramming
  • Discuss definition of 'Transformation'.

13. Reminders

  • Second NTF online session will be March 23rd at 1 PM CET.
  • Michele looking for P2654 representation in TAAA Workshop (CfP circulated by email). No immediate offers to participate.
  • Brad’s first demo code: https://github.com/bradfordvt/P2654Model.

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh