Browse Prior Art Database

Technique to Check for Local Redundancy Without Involving Remake Decisions During Circuit Testing

IP.com Disclosure Number: IPCOM000037661D
Original Publication Date: 1989-May-01
Included in the Prior Art Database: 2005-Jan-29
Document File: 1 page(s) / 12K

Publishing Venue

IBM

Related People

Godoy, HC: AUTHOR

Abstract

When a remake decision is made during the testing of an electronic logic circuit without redundancy and a conflict is indicated, it is clear that the conflict is due to the decision, and a remake of that decision will further the test. However, if there is redundancy present in the circuit logic, the test will proceed endlessly until a preset maximum number of remake decisions is completed.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 99% of the total text.

Page 1 of 1

Technique to Check for Local Redundancy Without Involving Remake Decisions During Circuit Testing

When a remake decision is made during the testing of an electronic logic circuit without redundancy and a conflict is indicated, it is clear that the conflict is due to the decision, and a remake of that decision will further the test. However, if there is redundancy present in the circuit logic, the test will proceed endlessly until a preset maximum number of remake decisions is completed.

A difficulty that arises, when remake decisions are involved during the testing of an electronic circuit having redundancy, is simply whether a conflict that is indicated is due to the decision or is due to the redundancy in the circuit. Therefore, the present technique proposes to check for redundancy before any decisions are made, and by following the technique, the presence of redundancy can be detected quickly.

The present technique is as follows:

1.) Backtrace the correct, pre-established values to the first decision block and imply those correct values forward through the circuit's logic, checking for conflicts with all of these values. 2.) Check each decision block for the elimination of any and all input options due to other requirements, and repeat step 1 if it develops that a block is no longer a decision block. (Steps 1 and 2 are repeated until all decision blocks are valid decision blocks.) 3.) Check each decision block for non-conflicting input values.

Disclosed anony...