Professional Documents
Culture Documents
Return ATPG -
Save Test pattern - Writing test pattern (serial, parallel, scan, chain)
1. build_model -workdir mydir -designsource design file1 -techlib tech_-file1 -cell top_module_name
2. build_model -designsource a.v:b.v:c.v -techlibtsmc13.v:techlib1.v -definemacro text_macro
3. build_model -workdir /local/sub_unit -designsource /local/dlx/tbdata/hierModel -techlib /local/techlib/tech90.v -cell
sub_unit
4. build_model -workdir /local/dlx -designsource /local/source/dlx.v -techlib /local/techlib/tech90.v -allowincomplete yes -
blacboxoutputs x
It is used to build test modes which define the scan structure and active logic for testing.
3. Build_faultmodel (Similar to perform DRC( calling SPF file, setting stuck or @speed fault, setting all fault in all module
or particular module)
create_logic_tests -testmode FULLSCAN -experiment tg1 -effort high (effort high means – increase test coverage)
Commit_test – (it store the pattern or test vector in database, then we can use command write_vector to store patterns in
separate file).
Append_test – (if we want to run a script multiple times with different ATPG controls)
Delete_test – if we want to delete previous test pattern due to many reasons (like low coverage, high pattern count), we can
delete previous run for that we can use “build_model” command, this command automatically delete all previous runs).
■ Example of deleting multiple experiments (deletes experiments tg1, tg2, and tg3):
3. Prepare_fault_subset : (
It allows you to specify a subset of faults to be included in an experiment. It also allows you to adjust the fault status.
The resulting experiment is used as input to create tests that target the specified faults; or ignore the faults with adjusted
status.
X-source messages -- may want to determine if there are ways you could reconfigure the testmode to eliminate sources of X.
Critical X-source messages from verify_test_structures are: TSV-101.
If running a SDC/SDF timed methodology, are there a large number of constraints that shutdown major portions of the logic?
❑ Faults along constrained paths are untestable and lead to lower test coverage
Compact_vectors:
The most commonly used options for the compact_vectors command are:
■ -resimulate yes|no - Set to no to not resimulate the result patterns. Default is yes to resimulate the results.
■ -reordercoverage both|static|dynamic - Specify the fault types to drive sorting. The default is based on the type of ATPG
patterns that are being simulated.
■ -maxcoveragestatic # - Stop patterns at a specific static coverage number (for example 99.00)
■ -maxcoveragedynamic # - Stop patterns at a specific dynamic coverage number (for example 85.00)
The most commonly used options for the simulate_vectors command are:
■ -language stil|tbdpatt|evcd - Type of language in which the patterns are being read.
■ -gmonly no|yes - Perform good machine simulation (no fault mark off). Default is no
The following is an example of fault simulation using FULLSCAN testmode:
-assignfile ./verilog_source/FULLSCAN.pinassign
build_faultmodel -includedynamic no
## If you omit the commit step you can reference the functional patterns
The following is an example of fault simulation using non-scan test mode and reduced fault count:
build_faultmodel -includedynamic no
## If you report_faults you can then edit the output to create a reduced list.
If you found that your pattern count was acceptable at your target test coverage, use one or both of these options to limit the
coverage to your target.
■ create_logic_tests -maxcoverage - maximum static coverage
For example, the following command will stop static ATPG when the test coverage is at least 90%.
The following option is used to limit the pattern count ATPG tries to attain during the run.
For example:
❑ The following command will stop static ATPG when the number of patterns is at least 9500.
❑ The following command will stop delay ATPG when the number of dynamic patterns is at least 7500.
-logfile ./log_report_untested_faults \
-faulttype static