Introduction Flashcards

1
Q

Difference between Testing and Design Verification.

A

Testing: Detect fabrication defects and faults that appear during operation.
Verification Detect erros introduced in the design phase.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Which is the “stuck at fault” problem formulation?

A

Given a combinational circuit and a stuck at fault, determine a set of assignmets at the inputs (test pattern) such that the faulty-free and faulty circuit produce different outputs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Which are the 3 basic approachs to design verification?

A

Simulation:
Stimuli are chosen to show a certain behaviour, or they are generated randomly.

Emulation: Construction of a prototype (e.g. using FPGA).

Formal Verification:
Application of exact mathematical proof methods (performed by software) to check circuit properties.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Motivation for formal verification (5 reasons).

A
  • Important for safety critical systems
  • Increasing complexity of SoC designs (simulation not always provide cover).
  • IP core based designs (it has to function in different circuits).
  • Better trade off between productivity and quality.
  • High portion of the design spent on verification.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Why can simulation fail?

A

Due to logic structures, some internal circuit nodes are difficult to stimulate using random patterns (“random pattern resistant”).

Circuits with large sequencial depth (couter).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Question to be responded by design verification.

A

Does the formal description(RTL) of design fullfil the expectations of the designer (informal verification)?

  • Can unexpected things occur? (Deadlock)
  • Do certain things always work?
  • Are there unexpected side effects?

Method: formal: property checking
informal: simulation.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Question to be responded by Implementation Verification.

A
Is the formal specification (e.g. at RT-Level) translated correctly into the implementation (e.g. at gate level)?
Sources of errors:
-Bugs in the tool.
-problems with interfacing of tools
 -manual interaction of designers 

Method/tool, formal: “equivalence checking“
non-formal: simulation (almost disappeared)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Can simulation be used in formal verification?

A

Yes, simulate all possible inputs and sequence of inputs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly