Timing Command Dictionary

SET SPLIT_MEASURE_CYCLE TIME

 

 

Arguments

integer

The time value at which to split the cycle. This number must match the period of the shift procedure.

Examples

The following FastScan example writes out a pattern set that tests for transition faults. When init_force_pi is the first non-scan event in the cycle, FastScan splits the ATPG non-scan cycle into two cycles. The first cycle includes only the init_force_pi event, while the second cycle begins with the force_pi and includes the remaining events in the non-scan cycle. When specified in the timing file, the SET SPLIT_MEASURE_CYCLE TIME command further splits each of these two cycles, causing the measure_po event to be the last event of the new test cycle.

So the timeplate timing definition should specify that the force_pi event time equals 2*test_cycle_length. Also, the period of the whole ATPG cycle should equal 4*test_cycle_length. These calculations assume the SET SPLIT_MEASURE_CYCLE command specifies test_cycle_length.

This example demonstrates the proper timing definition for this situation.

//FastScan application commands add scan group g1 ckt2.tp

add scan chain c1 g1 SI SO set fault type transition add clocl 1 clks

add clocl 0 clk

set DRC handling C2 war set system mode atpg add faults -all

run

save patterns pattern_file -replace time_file -Zycad -serial

//Timing file “time_file” set time scale 1 ns; Timeplate "tp0" =

init_force_pi 0;

force_pi 400;

measure_po 520;

FastScan and FlexTest Reference Manual, V8.6_4

A-17

Page 769
Image 769
Mentor v8.6_4 manual Initforcepi Forcepi Measurepo