1989
DOI: 10.1109/43.39071
|View full text |Cite
|
Sign up to set email alerts
|

A synthesis and optimization procedure for fully and easily testable sequential machines

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
13
0

Year Published

1991
1991
2007
2007

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 79 publications
(13 citation statements)
references
References 12 publications
0
13
0
Order By: Relevance
“…Synthesis methods are also being applied to sequential circuits under stuck-at [4] and delay faults models (e.g., [5]). …”
Section: Introductionmentioning
confidence: 99%
“…Synthesis methods are also being applied to sequential circuits under stuck-at [4] and delay faults models (e.g., [5]). …”
Section: Introductionmentioning
confidence: 99%
“…In some problems, a constraint is satisfied if the corresponding function fi is respected in every column of the constraint, like code compatibility constraints [2] or output constraints [3]. There are also cases where the fi need to be satisfied in a specific number of encoding columns [5]. That is why the domain of the satisfaction functions gi are all possible encodings of length k. Given this mapping, the state assignment problem can be reduced to the general BCE problem, and we need to look for an optimum encoding h of the state set Q, such that k is the minimum possible and c(h) is maximum.…”
Section: Problemmentioning
confidence: 99%
“…To satisfy one such constraint one encoding column suffices. Distance-2 constraints were proposed in [5] to guarantee fully stuck-at testable state assignment for FSMs. One such constraint is satisfied only if a Hamming distance of 2 is obtained between the codes of the symbols involved in it.…”
Section: Constraint Classesmentioning
confidence: 99%
“…The following constraints are imposed on the logic synthesis process in order to result in a fault-secure implementation. During state encoding, all valid controller states are constrained to have the same parity [14]. The outputs are also constrained to be encoded with the same parity with the help of an extra output.…”
Section: Moves In the Iterative Improvement Proceduresmentioning
confidence: 99%
“…The controller finite-state machine (FSM) is made faultsecure by constraining the state encoding procedure to assign codes having the same parity to all the states and, in addition, constraining the primary outputs and next state outputs of the controller to be implemented by disjoint cones of logic [14]. The parity of the primary outputs of the controller is also generated as a controller output.…”
Section: Introductionmentioning
confidence: 99%