Search found 77 matches

by Bradford Van Treuren
Tue Feb 20, 2018 11:52 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

You have a bit of a problem with your analogy. As an FAA Certified Airframe & Powerplant mechanic, I used to have to measure the thickness of crankcase bearings during overhaul. The micrometers at the shop did not have a curved platform matching the bearing curve. The proper practice was we had a go...
by Bradford Van Treuren
Mon Feb 19, 2018 6:16 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

The issues you raise can arguably be part of the PAR. However, none of them negate the overriding need of the industry to do what we do in order to bring about better tests. So it is not a case of "my" needs vs. "your" needs. I submit again that if there would be no need for better tests (as measur...
by Bradford Van Treuren
Mon Feb 19, 2018 4:57 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

Since Ian needed to cancel the meeting today, I thought I would use this time to mine important ideas/comments from various email threads to post them to the forum so we have a single place for the repository of ideas. Certainly, I am not having the time to investigate all the discussions, but will ...
by Bradford Van Treuren
Wed Feb 14, 2018 12:04 am
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

I would have to courteously disagree with Louis. Test Coverage is not the only reason for the existence of SJTAG. There are many factors, too many to enumerate in a PAR. Example 1: Standardized interface/mechanism for embedded instrument access by product application code. IEEE 1687 makes access to ...
by Bradford Van Treuren
Mon Feb 12, 2018 5:04 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

Notes from February 12, 2018 meeting: SJTAG 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...
by Bradford Van Treuren
Tue Feb 06, 2018 9:55 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

...may allow you to do something you could already do, but with much less work. Ian is quite right. I have been doing ad hoc embedded boundary-scan testing since 1990 based on 1149.1 standard (actually started before that). The key to Ian's point is making it easier to do what I am already doing an...
by Bradford Van Treuren
Mon Feb 05, 2018 4:59 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

Here are the notes from the Feb 5, 2018 meeting: SJTAG Need: More implementation than things in the PAR (e.g., First Red block) Need more than what is just listed in first bullet. Need as part of design so it can be part of the end game (DFT, DFM, etc.). Still need some reference to “What is a good ...
by Bradford Van Treuren
Thu Feb 01, 2018 8:42 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

Heiko's response is why I stated the sentence is good, but needs some tweaking. The points Heiko made are important. What we need is something in the middle of Louis' sentence and the original sentence. Both sentences represent the extreme end cases. The difficulty here is Louis' sentence is talking...
by Bradford Van Treuren
Mon Jan 29, 2018 5:22 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

Here is the content of the Needs Brainstorming discussion by the SJTAG Study Group on 29 January 2018. Please post your further comments using this forum page so we can keep a record of the ideas passed around this week before next meeting. Thanks. SJTAG Need: SJTAG is intended to improve the abilit...
by Bradford Van Treuren
Wed Nov 08, 2017 9:57 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

Ian, I think you are spot on with your assessment. They are related, but not dependent on each other. For Need A in the embedded environment is typically implemented as a series of agents running on the next lower level entity that is responsible for performing the operations requested by the upper ...
by Bradford Van Treuren
Wed Jul 19, 2017 8:14 pm
Forum: Weekly Meetings
Topic: Study Group title and Call for Participation
Replies: 20
Views: 442

Re: Study Group title and Call for Participation

I too vote for System TEst Access Management (STEAM).
I also agree with Ian regarding swapping 2nd and 3rd paragraphs.
by Bradford Van Treuren
Wed Sep 21, 2016 4:17 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

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...
by Bradford Van Treuren
Wed Sep 07, 2016 4:20 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

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 des...
by Bradford Van Treuren
Wed Aug 31, 2016 4:24 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

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 othe...
by Bradford Van Treuren
Wed Aug 24, 2016 4:11 pm
Forum: SJTAG General Discussions
Topic: PAR scope and direction
Replies: 99
Views: 3911

Re: PAR scope and direction

The following is the paragraph developed during the meeting today as the proposed new PURPOSE statement. It is a very, very rough draft to be reviewed. There were only four of us on the call today, so we could sure use your feedback on the forum before next meeting. Thanks. The purpose of this stand...