Minutes of P2654 Working Group Meeting No.132, 2021-11-22
Meeting called to order: 11:05 AM EST
The slide references relate to the pack used during this meeting, located here:
http://files.sjtag.org/P2654WG/P2654_Meeting_132.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)
Heiko Ehrenberg (GOEPEL Electronics)
Brian Erickson (JTAG Technologies)
Peter Horwood (Digital Development Consultants Ltd)
Joel Irby (AMD)
Richard Pistor (Curtiss-Wright)
Jon Stewart (Dell)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (VT Enterprises Consulting Services)
Carl Walker (Cisco)
Guests:
Tom Thompson (for IEEE)
Excused:
Bill Huynh (Marvell Inc.)
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 without comment.
4. Review and Approve Previous Minutes
- {Slide 11}
- Meeting #131, November 15 (draft circulated November 15)
- No corrections noted.
- Bard moved to approve, seconded by Jon, no objections or abstentions → minutes approved.
5. Review Open Action Items
- {Slide 12}
- None.
- Action Item Register: http://files.sjtag.org/P2654WG/ActionItemRegister.xlsx
6. Inter-group Collaboration
- {Slide 13}
- P1500 re-circulation ballot has closed, 35 comments to resolve.
7. Discussion Topics
7 a) Continue Review of Standard Draft
- {Slide 14}
- NOTE: New slides have been inserted into the meeting pack as slides 112 - 114 and consequently some references from last week's minutes do not transfer directly into this week's pack.
- Re-capping and expanding on the material presented last week from Brad's work for P1687.
- Key Assumption (slide 111) is showing a right-to-left flow for consistency with P1687 conventions.
- The Target Grammar is stating the objective from the perspective of the application.
- The Transformed Grammar is the result of transforming the stated objective into instance specific (fully qualified) instructions.
- Slides 112 - 114 work through a specific example: The top left blue box from "1687 to 1687.1 Transformation Process" maps on to the grey box on the right of the two "1687.1 to 2654" diagrams - different stages of the process, the latter supporting the Transformation Node Model on slide 115.
- Discussion on how this was different to the approach Peter had suggested that used nested wrappers.
- Proposition that if all or part of the downstream hierarchy was known (it often is) then than known section could be described like a single node (effectively a black box) which might provide an efficiency and allow easier swap-in of Form-Fit-Function substitutes.
- This would work where the injection node was at or above the top of that block.
- Document was not updated and latest version remains IEEESTD-P2654_Draft_D01_BGVT_20211115.docm.
8. Any Other Business
- {Slide 15}
- None.
9. Glossary:
- None.
- Carried over:
- 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.
10. Takeaways:
- None.
11. Schedule next meeting
- November 29, 2021
- Louis and Brian expect to be absent.
12. Topic for next meeting
- Continue review of standard draft
- IEEESTD-P2654_Draft_D01_BGVT_20211115.docm
- Continue with clause 4.3.
13. Reminders
- Brad’s first demo code: https://github.com/bradfordvt/P2654Model.
- Brad's slides and diagrams in docs folder: https://github.com/bradfordvt/P2654Model2.
14. List New Action Items
- None.
15. Adjourn
- Brad moved to adjourn, seconded by Peter.
- Meeting adjourned at 12:04 PM EST
Respectfully submitted,
Ian McIntosh