Minutes of P2654 Working Group Meeting No.35, 2019-09-23

Meeting called to order: 11:05 AM EDT

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

1. Roll Call

Ian McIntosh (Leonardo)
Eric Cormack (DFT Solutions)
Terry Duepner (National Instruments)
Heiko Ehrenberg (GOEPEL Electronics)
Peter Horwood (Firecron Ltd.)
Bill Huynh (Marvell Inc.)
Joel Irby (Arm)
Richard Pistor (Curtiss-Wright)
Jan Schat (NXP Semiconductors) (joined 11:07)
Naveen Srivastava (Nvidia)
Jon Stewart (Dell)
Louis Ungar (A.T.E. Solutions)
Brad Van Treuren (No affiliation)
Carl Walker (Cisco Systems)


By email (non-attendees):


2. Agenda

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

3. IEEE Patent Slides

  • {Slides 5-9}
  • Patent slides reviewed.

4. Review and Approve Previous Minutes

  • {Slide 10}
  • Meeting #34, September 16 (draft circulated September 16)
    • No corrections.
    • Eric moved to approve, Terry seconded, no objections or abstentions → minutes approved.

5. Review Open Action Items

6. Discussion Topics

6 a) Security - Types and scope for P2654

  • {Slides 12-13}
  • Could Fault tolerance be classed under "security", checking that failover is to authentic and operational resource? More likely this comes under "system availability".
  • Security has become more heightened. Restrictions based on trade agreements, what product can you build off-shore, what firmware can you load?
  • There will be trade-offs between security and testability.  Some arguments are made that JTAG is a security risk and should be shut off.
  • Best paper at AutoTestCon was from Alan Sguigna on JTAG Security (also see https://blog.asset-intertech.com/test_data_out/2019/07/securing-the-jtag-interface.html#more).
  • In terms of using translators already on the board, if these are FPGAs it would help to have a common API that could work across different interfaces and T10 SCSI is well defined and has a new security enquiry mechanism that could be useful (www.T10.org). The detail is only available to committee members so hasn't been examined, but could be worth looking into. It is a packetized protocol but it is necessary to packetize anyway for many interfaces, such as I2C.
  • If security limits access does P2654 really care? There maybe needs to be awareness of the paths that are available.
  • Software could manage a scan path linker such that it will not allow access to certain local scan paths. However software control may not be a particularly secure method.
  • It's not just data were passing, there could be management and setup  activities in there too. The transforms would need to know what is their own setup data and what is to passed on in the datastream. T10 does this and passes on the setup bytes for the next level.
  • Might there be a patents/license issue in proposing SCSI methods?
  • The "software model" expects to draw information from the design topology and device vendor information (and perhaps other sources).
  • P2654 could help users by analysing security trade-offs.

7. Any Other Business

  • {Slide 14}
  • None.

8. Today's Key Takeaways

  • Security query from T10.org is worth looking into.

9. Glossary Terms from This Meeting

  • None.
  • Carried over:
    • "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 meeting.
    • "Event", "Access Interface" as proposed at April 15 meeting
    • LRU and SRA.

10. Schedule next meeting

  • September 30, 2019
    • Louis will be absent.

11. Topic for next meeting

    • Slides on routing/transforming devices.

12. Reminders

  • None.

13. List New Action Items

  • None.

14. Adjourn

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

Respectfully submitted,
Ian McIntosh