1996
DOI: 10.1109/12.485577
|View full text |Cite
|
Sign up to set email alerts
|

Self-checking comparator with one periodic output

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
10
0
2

Year Published

1998
1998
2012
2012

Publication Types

Select...
4
3
2

Relationship

1
8

Authors

Journals

citations
Cited by 40 publications
(12 citation statements)
references
References 2 publications
0
10
0
2
Order By: Relevance
“…Therefore, a periodic self test routine is often applied to execute all resources, thus, activating dormant faults that might accumulate otherwise. The compare unit has to be self checking as in (Kundu et al, 1996), being instantiated only once. Likewise, all external components are instantiated only once, and protected by means of ECC or parity for the RAM and buses.…”
Section: Target Architecturementioning
confidence: 99%
“…Therefore, a periodic self test routine is often applied to execute all resources, thus, activating dormant faults that might accumulate otherwise. The compare unit has to be self checking as in (Kundu et al, 1996), being instantiated only once. Likewise, all external components are instantiated only once, and protected by means of ECC or parity for the RAM and buses.…”
Section: Target Architecturementioning
confidence: 99%
“…To solve this problem additional input registers [5], additional code-preserving shift registers [14], [4], [15], additional periodic inputs [6], [8], [9], additional adder-like structures [16] and others are proposed. In general for these methods the area overhead is high, the delay may increase and in same cases the latency of error detection also increases.…”
Section: Introductionmentioning
confidence: 99%
“…Self-checking comparators and two-rail checkers are well known for their capability to detect faults present at inputs and internal nodes [16,17,18]. However, most of them target Stuck-at-fault only.…”
mentioning
confidence: 99%