The discussion forum for the SJTAG Initiative Group

PAR scope and direction

Discuss the generic proposals for SJTAG
User avatar
Bradford Van Treuren
SJTAG Chair Emeritus
Posts: 76
Joined: Fri Nov 16, 2007 2:06 pm
Location: NOKIA / USA

Re: PAR scope and direction

Postby Bradford Van Treuren » Wed Aug 31, 2016 4:24 pm

In today's meeting we refined the PURPOSE further. Here is what we came up with as Slide 33 in the new stack:

PURPOSE: The purpose of this standard is to provide a means to seamlessly integrate component access topologies (that follow a Capture, Shift, Update Cycle), interface constraints, and other dependencies at the board and system level with a uniform description that focuses on topology and behavior (as opposed to physical structure). By modeling this topology at the board and system level, a common set of interfaces may be used by higher level tools defined to coordinate these access topologies (communication interfaces) providing and provide a means of routing data sets to particular destination registers in the correct time order.


We also added two bullet points for Seamless Access and one for Problem Domain. The new set of brainstorm items is:
  • Seamless Access
    • system, board, device meld into a uniform description (Abstraction of “Assembly”)
    • Behavioral aspects than structural
    • treat the interfaces (access links, data links) as "black boxes“
    • Standardize on the right-hand side following the CSU protocol.
    • Schedule, Order, Application of vectors
    • Provide a means for higher level tools to make use of
  • Problem Domain (what we are trying to do)
    • Inadequacy of existing standards
    • Aggregation of circuit boards (w/ varying protocols e.g., 1149.x, 1687, I2C, USB, SPI)
    • Trying to create a software abstraction to the existing hardware standards

Please review the latest revision and make your comments on the forum. Next time we want to begin looking at the bigger picture of the SCOPE, PURPOSE, and NEED. You may recall we moved the old PURPOSE to the NEED and we should review the NEED accordingly. You may view the latest version of the NEED here:

http://forums.sjtag.org/viewtopic.php?p=1158#p1158
Bradford Van Treuren
Distinguished Member of Technical Staff
NOKIA MN

User avatar
Bradford Van Treuren
SJTAG Chair Emeritus
Posts: 76
Joined: Fri Nov 16, 2007 2:06 pm
Location: NOKIA / USA

Re: PAR scope and direction

Postby Bradford Van Treuren » Wed Sep 07, 2016 4:20 pm

The revisions to the PURPOSE are listed below:

PURPOSE: The purpose of this standard is to provide a means to seamlessly integrate component access topologies (that follow a Capture, Shift, Update cycle), interface constraints, and other dependencies at the board and system level with a uniform description that focuses on topology and behavior (as opposed to physical structure). By modeling this topology at the board and system level, a set of familiar and yet interchangeable interfaces may be used by higher level tools to coordinate these access topologies and provide a means of routing data sets to particular destination registers in the correct time order.

The revised NEED section follows:
NEED: A standardized method is needed to coordinate component access topologies, interface constraints, and other dependencies at the board and system level in order to be able to effectively leverage the existing and future component level standards. Thus, a new supervisory standard is required to define the coordination and dependencies of instruments as well as configuration, management, and application of vector based testing at the board and system levels. For example, IEEE 1687 and IEEE 1149.1-2013 provide methods for describing each of the instrument interfaces on a per component basis, but fail to provide the contextual prerequisites for the dependence on each instrument configuration and/or aggregation of multiple instruments for the overall board and/or system maintenance operations. Further, many components only support non-JTAG interfaces (e.g., I2C or SPI) to their instrumentation registers. This standard will provide a means to utilize the pin level access provided by other standards.
Bradford Van Treuren
Distinguished Member of Technical Staff
NOKIA MN

User avatar
Bradford Van Treuren
SJTAG Chair Emeritus
Posts: 76
Joined: Fri Nov 16, 2007 2:06 pm
Location: NOKIA / USA

Re: PAR scope and direction

Postby Bradford Van Treuren » Wed Sep 21, 2016 4:17 pm

Today we wrapped up the SCOPE, PURPOSE, and NEED statements with a minor change to PURPOSE and NEEDS. The finalized text for each is presented below.

SCOPE: This standard defines methods to allow, in conjunction with existing methods, for the coordination and control of device, board, and sub-system test interfaces to extend access to the system level. The standard does not replace or provide an alternative to existing test interface standards, but aims instead to leverage them by defining a description to better manage how they are used in the system.

PURPOSE: The purpose of this standard is to provide a means to seamlessly integrate component access topologies (that follow a Capture, Shift, Update cycle), interface constraints, and other dependencies at the board and system level by using a uniform description that focuses on topology and behavior (as opposed to physical structure). By modeling this topology at the board and system level, a set of familiar and yet interchangeable interfaces may be used by higher level tools to coordinate these access topologies and provide a means of routing data sets to particular destination registers in the correct time order.

NEED: A standardized method is needed to coordinate component access topologies, interface constraints, and other dependencies at the board and system level in order to be able to effectively leverage the existing and future component level standards. Thus, a new supervisory standard is required to define the coordination and dependencies of instruments as well as configuration, management, and application of vector based testing at the board and system levels. For example, IEEE 1687 and IEEE 1149.1-2013 provide methods for describing each of the instrument interfaces on a per component basis, but do not provide the contextual prerequisites for the dependence on each instrument configuration and/or aggregation of multiple instruments for the overall board and/or system maintenance operations. Further, many components only support non-JTAG interfaces (e.g., I2C or SPI) to their instrumentation registers. This standard will provide a means to utilize the pin level access provided by other standards.

The working slides from today may be found under my file manager directory as Final SPN Draft 20160921.pptx.
Bradford Van Treuren
Distinguished Member of Technical Staff
NOKIA MN


Return to “SJTAG General Discussions”

Who is online

Users browsing this forum: No registered users and 1 guest