ELEC7250:%20VLSI%20Testing%20Spring%202004 - PowerPoint PPT Presentation

About This Presentation
Title:

ELEC7250:%20VLSI%20Testing%20Spring%202004

Description:

Dixit, Ayoush M. Testing - Processing defects due to fabrication technology need to be addressed ... Structural testing allows designers to develop algorithms ... – PowerPoint PPT presentation

Number of Views:29
Avg rating:3.0/5.0
Slides: 10
Provided by: ayoushma
Category:

less

Transcript and Presenter's Notes

Title: ELEC7250:%20VLSI%20Testing%20Spring%202004


1
ELEC7250 VLSI TestingSpring 2004
  • Experimental Analysis of Fault Collapsing Methods

Dixit, Ayoush M
2
Testing
Why?
- Processing defects due to fabrication
technology need to be addressed - Defects in
devices cause faults to exist.
How do we go about testing devices?
Fault Models
  • Structural testing allows designers to develop
    algorithms to detect faults present in the system
    with the help of Fault Models.
  • How?
  • Collapsing is done based on different criteria.
  • Possible ways to collapse faults are dominance
    collapsing, equivalent collapsing, functional
    collapsing, etc.

3
Dominance Fault Collapsing
If all tests of F1 detect another fault F2, then
F2 is said to dominate F1.
4
Checkpoint Theorem Algorithm Used
  • The set of checkpoints consists of the primary
    inputs and all the fanout branches
  • In fanout-free circuit, the set of checkpoints
    consists of the primary inputs alone
  • The Theorem says that any test set which detects
    all single stuck-at faults on check points will
    detect all single stuck faults.

Dominance collapsing was performed as follows
- n1 SSFs for n-input gates (basic gates). -
AND/NAND s-a-1 faults in all inputs s-a-0 fault
on any one input is retained. - OR/NOR s-a-0
faults in all inputs s-a-1 fault on any one
input is retained.
5
Getting fault list
The program reads the netlist file and parses and
writes it into understandable format, which is
then opened to perform all the fault collapsing
  • Primary inputs
  • Gate type
  • Model s-a-1 on all inputs of AND/NAND s-a-0
    fault on any one input
  • Model s-a-0 on all inputs of OR/NOR s-a-1 fault
    on any one input
  • Model both SF on not and buffers
  • Primary inputs fanning out
  • Model both SF on the input and the fanouts
  • Others
  • When the output of a gate fans out then on the
    fanouts model both SF.
  • Equivalent collapsing was done where ever
    possible.

6
Results and Conclusion
Results
Circuit Faults Detected Faults Coverage Collapse Ratio
C17.bench (Equivalence) 22 22 1 22/57 0.407
C17.bench (Dominance) 22 22 1 22/54 0.407
71481.bench (Equivalence) 301 293 0.9734 301/676 0.445
71481.bench (Dominance) 218 209 0.9587 218/676 0.322
For some reason there are 9 undetected faults in
my implementation.
7
Results and Conclusion
Lessons Learned
It was evident from the implementation and
results that the collapse ratio is higher in
circuits with fanouts.
From the results it was found that for the
smaller circuits the fault coverage and the
collapse ratio remains fairly the same in both
Equivalent and Dominance collapsing methods. In
larger circuits dominance fault collapsing can
collapse more faults than equivalence fault
collapsing method. Although that is the case,
fault coverage seems to be better in equivalence
fault collapsing method, which is intuitive
because of presence of more faults
Time management
Suggestions Try to get some knowledge of
output format of software being used. It may
seem redundant, develop algorithm implementation
flow chart. If possible do hand analysis on
smaller circuits before testing bigger circuits.
8
Results and Conclusion
Demonstration
  • Hitec Commands
  • Do_hitec ltfilenamegt
  • Level ltfilenamegt
  • Faultlist
  • Equiv
  • Dominators
  • Testgen

Two level macro
  • Modified Commands
  • dominance
  • Conv (converts my fault list in hitec
    understandable format)
  • Dominators
  • Testgen
  • Proofs
  • Remove TEST.run file
  • do_proofs ltfilenamegt
  • Faultsim ltfilename.vecgt

9
Results and Conclusion
Discussions
C is buggy while reading a file. If the end of
line is found right after the end of the token
read strtok puts that with the last read token.
This creates problem when the comparison vector
is not the last file token read from another
file. Even though the strings are equal, strcmp
cannot do anything. So, since I knew that the
naming file ends right after the second vector,
add in "\n" to the vector read from the fault
file.
Comments and questions can also be directed to
dixitam_at_auburn.edu
Thank you for your time.
Write a Comment
User Comments (0)
About PowerShow.com