Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
Scan test is the methodology where registers in a design are connected with a long chains. These registers are pre-loaded with specific values shifting serially values using the scan chains. Then we clock once the design and capture the inputs of these registers. These values are shifted out and the results are read and checked againsts expected values.
If you have a specific 'scan_test' pin, then that is the pin to put the device into scan mode, so that it can run ATPG (Automatic Test Pattern Generation) vectors, for manufacturing test. Many devices use this 'scan_test' signal to disable clock gating and sequentially derived asynchronous resets, which is necessary during scan test.
Hi,As testing is an costlier effort,the designs r made in such a way tht they r easily testablefor ICs in which registers r involved registers r replaced with scan register which r made easier for testability,basically the concept is easily testing the IC.one of the procedure is scan test.for more info refer DFT by abromovicci.
scan test or JTAG is a serial protocol included in some complex chips to diagnose the port functionality ..all components with Jtag are link together in a daisy chain maner .So is possible to send test patterns and test if the ports work .JTAG is also employed to load FIRMWARE in FLASAH or eeprom in MIcrocontrollers.And to do debug
what are the chip level I/O's associated with scan chains? specifically, how do you control the scan test and shift in/out of the scan chains (from the I/O's)? All the documents that I read only discuss a scan cell connecting to another scan cell. Are scan_in, scan_out, scan_en chip level I/O's? If so, does each scan chain have dedicated chip-level I/O?
There are some scan inputs and outputs at the chip level I/Os but there are probably muxed.
It means this I/Os are some different function at normal mode.To use this I/Os as scan_in you need to go to scan mode.
Sometime for small design there are enough I/Os and scan_in can be directly accessed.
SCAN tests from a chip testing perspective also talk about coverage meaning how much of the logic can be tested. Depending on the design coverage numbers can be anywhere between 90 - 98% (< 100%). The main advantage of SCAN tests is a lot of logic can be tested very quickly. SCAN tests are generally not checking for speed problems but are looking for stuck at faults (logic 1 or 0) in the design.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.