Continue to Site

Welcome to EDAboard.com

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.

DFT Question about hard IP scan

Status
Not open for further replies.

HolySaint

Full Member level 3
Full Member level 3
Joined
Aug 31, 2008
Messages
159
Helped
6
Reputation
14
Reaction score
3
Trophy points
1,298
Location
Mars
Activity points
2,109
dft_drc

Hi,
I have a module A:

module A()

B B()

endmodule

The B is a hardware IP, and it is Performed Scan Replacement.
Now I want to insert scan in my design A,and route the flip-flop in IP B which is already scan replaced.
I also don't want to change everything of the IP and just route the regs in B and regs in our design together.

Our design has the test ports. And the IP has test pins too.

How can I do to route them together?

Thanks for ur answers.
 

lan ip scan command

define hard IP scan as " add sub scan chains" in your scan insertion tool.
 

    HolySaint

    Points: 2
    Helpful Answer Positive Rating
hookup_pin scan

santhosh007 said:
define hard IP scan as " add sub scan chains" in your scan insertion tool.

I use the dftc to insert chains, but I dont know how to add it.
I am looking for the ug, can u give me an advice?

Thanks.
 

dc_shell with ip

I think this example may help you.

Use the following command sequence to infer the subdesign scan chain in module B :

dc_shell> current_design B
dc_shell> set_dft_signal -view spec -port scanin_b \
-type ScanDataIn
dc_shell> set_dft_signal -view spec -port scanout_b \
-type ScanDataOut
dc_shell> create_test_protocol
dc_shell> dft_drc


Use the following command sequence to include this scan chain in a top-level scan chain:

dc_shell> current_design A
dc_shell> create_test_protocol
dc_shell> dft_drc
dc_shell> insert_dft
dc_shell> dft_drc
 

    HolySaint

    Points: 2
    Helpful Answer Positive Rating
scan hookup pin

santhosh007 said:
I think this example may help you.

Use the following command sequence to infer the subdesign scan chain in module B :

dc_shell> current_design B
dc_shell> set_dft_signal -view spec -port scanin_b \
-type ScanDataIn
dc_shell> set_dft_signal -view spec -port scanout_b \
-type ScanDataOut
dc_shell> create_test_protocol
dc_shell> dft_drc


Use the following command sequence to include this scan chain in a top-level scan chain:

dc_shell> current_design A
dc_shell> create_test_protocol
dc_shell> dft_drc
dc_shell> insert_dft
dc_shell> dft_drc

I'll try that immediately。
Thanks agains~

Added after 54 minutes:

I tried as U tell me, but in the module B which is sub module,the tool added some ports in it, like test_si and test_so.
But I set ScanDataIn and ScanDataOut in my scripts, why it add the data port again?

I was so confused......
 

how to use command to scan ip

Why did the tool add ports at the module B?
 

dft testmode test_si

santhosh007 said:
try with -view existing option

I mean that the added pins is module B's.

But when I want to hook up the module B's test pin into A's port,what do I need to gen the atpg for testing module B?

Thanks for your answers.
 

dftc spec

with same command i think you have an option
-hook_up
 

    HolySaint

    Points: 2
    Helpful Answer Positive Rating
Hello Friend,

test_si and test_so has been added by tool means, tool doesn't find the scan ports. So, use hookup pin option as follows.

dc_shell> current_design B
dc_shell> set_dft_signal -view spec -port scanin_b \
-type ScanDataIn \
-hookup_pin [xxxx]

dc_shell> set_dft_signal -view spec -port scanout_b \
-type ScanDataOut \
-hookup_pin [yyyy]

///where xxxx and yyyy are the already existing test ports of the IP.

dc_shell> create_test_protocol
dc_shell> dft_drc

Hope this solves the issue.

Still u r finding the problem, I have another flow to follow.

Sunil Budumuru
www.asic-dft.com
 

faint.. It' s hard ip.. hardened one?

if so, you need its test model.., i.e., ctldb or ctlddc.

and use_test_model in top level design.
 

    HolySaint

    Points: 2
    Helpful Answer Positive Rating
entropy said:
faint.. It' s hard ip.. hardened one?

if so, you need its test model.., i.e., ctldb or ctlddc.

and use_test_model in top level design.

Thanks, the test model is very important as you said.

nice day!
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top