SJTAG

SJTAG Newsletter
http://www.sjtag.org

 

Issue 24 - Q2-2013

You are receiving this email because you are a valued contact of the SJTAG Working Group. If you no longer wish to receive this newsletter, or would like to change your mailing preferences, then please use the links at the bottom of the newsletter.

Any comments on this newsletter can be mailed to admin@sjtag.org.


From the Chair

We have been producing this newsletter for almost five years and in that time it's almost inevitable that some of our readers will have moved on to other things, so it's maybe about time that we cleaned up our mailing list to ensure that we're only sending this to people that still want to receive it.

We need people to actively assert that they want to continue to get the SJTAG newsletter, so we will shortly be sending you an email with a link that you'll need to follow to either accept or decline your participation. Any accounts that decline or are not validated within one month will be removed from our system.

So remember: As soon as you receive the notification email, please take action to re-validate your subscription to continue to receive the SJTAG Newsletter.

http://www.sjtag.org/misc/validation2013.html


Seeking Some Examples

Over recent weeks, the Working Group has been considering how the various JTAG related standards and protocols might fit into a tiered structure of interfaces for SJTAG. We've now reached the point where it would be immensely useful to have one or two example designs that we could use as case studies of the work required to take a design from an existing board test through to a system level test.

Obviously, we can't expect anyone to volunteer their design to us blindly, so we're happy to discuss any offers prior to anyone making a commitment. Basically, what we're looking for is:

  1. An example or two that are not hugely complex designs (possibly a daughterboard might be a good example). A full reference design implementation from a device vendor could be very useful to us.
  2. Clearly, the design needs to include at least one edge (backplane) accessible JTAG chain. The presence of an embedded JTAG controller/sequencer is optional.
  3. We may require a representative of the designer to be available to answer questions about the design or its testing, either as a party to the conference call or via email.

We can also consider partial designs to reduce the exposure of IP and even abstract/concept designs may usable.

What we hope to achieve is a consolidated view on:

  • What data is needed to transition from board level to system level test,
  • How it might typically be obtained or derived,
  • How tooling would use the data a) to create tests and b) during execution of tests.

Please contact us if you think you may have a design we could use.

http://www.sjtag.org/form/contact.html

Description: Circuit Board

Newsfeed Extracts

Description: News Feed

The column to the right of the page gives an outline of some very recent news items, mainly summaries from recent meeting minutes. You can keep up to date with SJTAG news items through our RSS feeds or for a more detailed description of our activities you can read over our meeting minutes.

http://www.sjtag.org/rss.html
http://www.sjtag.org/minutes.html


Next Newsletter

The Q3-2013 edition of this newsletter will be published towards the end of July 2013. Copies of past newsletters are always available on the SJTAG website.

Please use the link at the foot of the page to forward this newsletter to colleagues who may be interested in the work of the SJTAG Group.

http://www.sjtag.org/newsletters.html


News from the website

Reaffirmation of officers (Issued: Mon, 04 March 2013 22:32:00 GMT)

At the meeting on March 4th, 2013, the Group voted to reaffirm both Ian McIntosh and Heiko Ehrenberg as the Group's Chair and Vice-chair respectively for 2013.

Click to read more...


Meeting Minutes from April 15th (Issued: Tue, 23 April 2013 19:57:00 GMT)

The minutes from the weekly meeting held on April 15th, 2013 have now been published. Key takeaways from this meeting: 1. Need to determine the requirements for data that will inform how a board test might be migrated to system test.

Click to read more...


Meeting Minutes from April 8th (Issued: Sun, 21 April 2013 18:09:00 GMT)

The minutes from the weekly meeting held on April 8th, 2013 have now been published. Key takeaways from this meeting: 1. Test Steps don't care about how the vectors it uses are transported. 2. There may need to be some coordination with other standards to avoid overlapping scopes.

Click to read more...


Meeting Minutes from April 1st (Issued: Sun, 21 April 2013 18:08:00 GMT)

The minutes from the weekly meeting held on April 1st, 2013 have now been published. Key takeaways from this meeting: 1. The Test Access Port/Scan Interface strata needs to be expanded (e.g. to accomodate alternative interfaces).

Click to read more...


Meeting Minutes from March 18th (Issued: Tue, 02 April 2013 19:54:00 GMT)

The minutes from the weekly meeting held on March 18th, 2013 have now been published. Key takeaways from this meeting: 1. The Test Program Interface layer is expected to be highly abstract. 2. The Scan Interface layer represents work being done elsewhere and may not be in the SJTAG domain. 3. Does the Scan Interface layer still represent 'vector patterns' in light of PDL that describes behavioral patterns?

Click to read more...


Meeting Minutes from March 4th (Issued: Tue, 02 April 2013 19:53:00 GMT)

The minutes from the weekly meeting held on March 4th, 2013 have now been published. Key takeaways from this meeting: 1. Abstraction above the Test Step Interface should reference test steps by name. 2. The Test Step Interface is the most likely candidate for standardization, and is point where the delineation between EBST and XBST can occur. 3. A functional test could use either the Test Step Interface to perform a single step or the Test Program Interface where a group of tests is required.

Click to read more...


Meeting Minutes from March 11th (Issued: Tue, 19 March 2013 19:37:00 GMT)

The minutes from the weekly meeting held on March 11th, 2013 have now been published. Key takeaways from this meeting: 1. Important ScanInterface primitives were defined my Mike (Westermeier) in his presentation. 2. Basically, anything you could digitize you could test. 3. Need for a description for defining the interactions between devices/instruments. This is currently missing from any of the current standards. 4. Retargeting becomes more difficult as you include interactions between devices.

Click to read more...