Algoritm for checking one gate's output to be stuck-at-1 or stuck-at-0?

Question

0.00/5 (No votes)

See more:

Ruby

algorithm

What is the algorithm to check one gate's output to be stuck-at-1 or stuck-at-0 ? Thanks in advance.

Posted 22-Jun-13 14:57pm

Sunil Kumar

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Andreas Gieriet · Answer 1 · 2013-06-22T18:00:00

First of all, have a look at Stuck-at-Fault[^] to get an understanding on what this exactly mean.
Then follow up with Design-For-Test (DFT)[^], which is an approach to get this fault model under control. Finally, get an understanding on Automatic-Test-Pattern-Generation (ATPG)[^] for the above mentioned DFT approach. See the D-Algorithm[^] for a possible pattern generation algorithm.

Cheers
Andi