2011 IEEE International Test Conference 2011
DOI: 10.1109/test.2011.6139140
|View full text |Cite
|
Sign up to set email alerts
|

Surviving state disruptions caused by test: A case study

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
2
0

Year Published

2013
2013
2016
2016

Publication Types

Select...
1
1
1

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(2 citation statements)
references
References 1 publication
0
2
0
Order By: Relevance
“…Since the last revision of the standard in 2001, the industry witnessed a drastic change in the IC technology. Many of these changes have been driven by design complexity and there are many devices available with programmable features including programmable IO behaviour [4]. Boundary scan testing put the device IOs in to test mode were their IOs are controlled by boundary register contents.…”
Section: Ieee 11491-2013 Revisionmentioning
confidence: 99%
See 1 more Smart Citation
“…Since the last revision of the standard in 2001, the industry witnessed a drastic change in the IC technology. Many of these changes have been driven by design complexity and there are many devices available with programmable features including programmable IO behaviour [4]. Boundary scan testing put the device IOs in to test mode were their IOs are controlled by boundary register contents.…”
Section: Ieee 11491-2013 Revisionmentioning
confidence: 99%
“…The standard uses instructions like EXTEST and CLAMP for this. When the non-test instructions like BYPASS or IDCODE is encountered between the test mode instruction the TAP pass through TLR state and IO pins are revert back to functional mode [4]. These switching events are completely unsynchronised with current activities in the board, so that the internal logic of each IC may see completely illogical states [3].…”
Section: Ieee 11491-2013 Revisionmentioning
confidence: 99%