Minutes of P2654 Working Group Meeting No.66, 2020-05-18

Meeting called to order: 11:07 AM EDT

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

1. Roll Call

Ian McIntosh (Leonardo)
Eric Cormack (DFT Solutions) (joined 11:27)
Heiko Ehrenberg (GOEPEL Electronics)
Brian Erickson (JTAG Technologies)
Peter Horwood (Digital Development Consultants Ltd)
Bill Huynh (Marvell Inc.)
Joel Irby (AMD)
Jan Schat (NXP Semiconductors)
Jon Stewart (Dell)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco Systems)

Guests:
---

By email (non-attendees):
---

Excused:
Terry Duepner (National Instruments)

2. Agenda

  • Brian moved to accept the agenda, seconded by Brad, no objections.

3. IEEE Patent Slides

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

4. Review and Approve Previous Minutes

  • {Slide 11}
  • Meeting #65, May 11 (draft circulated May 11)
    • No corrections noted.
    • Brad moved to approve, Jon seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Inter-group Collaboration

  • {Slide 13}
  • Expectation that 1149.4 will be renewed (aiming for a "no changes" revision).
  • IEEE proposing to make IEEE standards available for adoption and tailoring by national standards bodies.
    • National standard will "wrap" the full IEEE standard, and any changes to content will be by in-line markup.
    • IEEE has the opportunity, but no obligation, to incorporate edits proposed by a national body.
  • PAR for Array Scan/Debug has been approved by TTSC and now goes to NESCOM for approval.

7. Discussion Topics

7 a) Close in on definition of 'System'

  • {Slide 14}
  • Is it essential that system must have a controller or make decisions?
  • A state machine can decide actions, set flags, etc., but does not need to have a processor. It can provide some interactivity and isn't restricted to just "running something".  The data may be decoupled from the state machine. Are there "Producer models" and "Consumer models" here?
  • A thermostat could be a very simple it system - it senses temperature and decides whether to switch on/off the heating or the air conditioning, and could be electro-mechanical. It need not provide information on the temperature or its state, although that might be informative.
  • There may be higher levels of control: The user may change the setpoint of the thermostat; the thermostat may be part of an IoT home control and remotely controlled or dependent on other conditions - the system(s) may become hierarchical or distributed.
  • You may have a system that has "control" but there may be some higher level of control that can be applied: This reflects that one person's system may be another person's sub-system and the perspective of the user becomes important in determining which applies.
  • Conventional definitions of "system" often refer to "organisation" and "ordered operation": If there is no control then there is chaos, so the absence of control means it cannot be a system.
  • Although a system need not use data interactively, we need to define "system" in the context of P2654 and for this there will be a need for interaction of data between higher and lower levels of the system (and/or outside world).
  • Additional points recorded during the meeting are on slides 46 and 47 of the meeting pack.
  • Bullet points recorded during the earlier meetings are now moved to a separate reference file: http://files.sjtag.org/P2654WG/P2654_Reference_Pack.pptx.
  • Forum thread for comments on the outline: http://forums.sjtag.org/viewtopic.php?f=3&p=1444#p1444

7 b) Select other definitions from forum

8. Any Other Business

  • {Slide 15}
  • None.

9. Today's Key Takeaways

  • None.

10. Glossary Terms from This Meeting

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

  • June 1, 2020.
    • May 25 is a holiday in both US and UK.

12. Topic for next meeting

  • a) Finish off 'system' discussion
    • Diagrams
    • Counter-examples

13. Reminders

  • None.

14. List New Action Items

  • None.

15. Adjourn

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

Respectfully submitted,
Ian McIntosh