FastScan and FlexTest Reference Manual, V8.6_4
2-296
Report Failures Command Dictionary
oThe position in the scan chain of the failing scan cell. This position is 0
based, and 0 position is the scan cell closest to the scan-out pin.
You use this command primarily for diagnostics.
Arguments
The Report Failures command requires that you, at minimum, either provide no
arguments or provide the pin_pathname and -Stuck_at value. If you choose to
provide the pin_pathname and -Stuck_at value, you can further modify the
command’s behavior by adding the -Max and -Pdet switches.
•pin_pathname -Stuck_at 0 | 1
A string paired with a switch and literal pair that specifies both the location and
the value of the fault that you want to check for failing patterns. The following
describes each of the arguments in more detail:
pin_pathname — A string that specifies the pin pathname of the fault
whose failing patterns you want to identify.
If you do not specify a pin_pathname, the command performs a good
machine simulation. You can use this good machine simulation to check
that the measured values from the test patterns are consistent with simulated
values. Any columnar failing patterns results indicate a mismatch.
-Stuck_at 0 | 1 — A switch and literal pair specifying the stuck-at values
that you want to simulate. The stuck-at literal choices are as follows:
0 — A literal that specifies for FastScan to simulate the “stuck-at-0”
fault.
1 — A literal that specifies for FastScan to simulate the “stuck-at-1”
fault.
•-Max integer
An optional switch and integer pair specifying the maximum number of failing
patterns that you want to occur on the specified fault before the command stops
the simulation. The default is: all failing patterns.
To use this option you must also specify the pin_pathname and -Stuck_at value