( ESNUG 381 Item 12 ) ------------------------------------------- [11/08/01]
Subject: ( ESNUG 380 #5 ) I Accidentally Used DFT Compiler, Not TetraMax
> With TetraMax, (via dc_shell) I used
>
> create_test_patterns -output core.vdb
> write_test -input core.vdb -output corepatterns.v -format verilog -first
> 1
>
> This generated a huge test that applies patterns at the core inputs,
> toggles clocks, and checks outputs.
>
> - Don Dattani
> Zucotto Wireless, Inc. Ottawa, Ontario, Canada
From: Don Dattani <dond@zucotto.com>
Hi, John,
To follow up on my ESNUG 380 #5 question, the short answer is (and it came
directly from Synopsys): don't use DFT Compiler to create_test_patterns!!
DFT Compiler (although it uses a separate licence) is invoked through
dc_shell -- which is what I did the first time. I had mistakenly thought
I was using TetraMax through dc_shell there! DC directives such as
create_test_patterns are legacy commands (were used in the past and are
still around), BUT it is not easy to set the scan options via dc_shell
that recognizes a design with:
a) full-scan methodology elements
b) test logic elements (no scan insertion)
So their recommendation is: I should use the real TetraMax. TetraMax allows
you to fully specify the nature of the test logic (how to setup the state
in scanable mode for ATPG.)
I have been using TetraMax now, but, there seems to be a TetraMax bug
(that Synopsys is aware of) with its reading in UDP files. The fun
never stops.
- Don Dattani
Zucotto Wireless, Inc. Ottawa, Ontario, Canada
|
|
