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.

DC script - Need to port block level script to top level

Status
Not open for further replies.

gurucharapathy

Newbie level 5
Joined
Jun 29, 2005
Messages
9
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
1,327
Hi,
I have block level dc constraints. I need to port them to top level. Can anybody let me know if I can use some kind of wildcards to do that ?
Ex:
Block level constraint : [get_pins clka]
Right now I am doing top level constraint by replacing this with the following
/top/blocka/clka
Is there any wildcard that I can directly add to block level constraint to port it easily like this [get_pins *clka] ?
Thanks in advance.
Guru.
 

Hi,
I have block level dc constraints. I need to port them to top level. Can anybody let me know if I can use some kind of wildcards to do that ?
Ex:
Block level constraint : [get_pins clka]
Right now I am doing top level constraint by replacing this with the following
/top/blocka/clka
Is there any wildcard that I can directly add to block level constraint to port it easily like this [get_pins *clka] ?
Thanks in advance.
Guru.

Hi, gurucharapathy:
There are usually two difference:
1): hierarchy name different, as you mentioned.
2): IO port name different.
For 1), you can set some variables in your tcl script as the hierarchy name. Then at top level, you just need change the variable value is ok. Such as:
set hir_nam "blocka"; get_pins $hir_name/clka

Then at top level:
set hir_name "/top/blocka"; get_pins $hir_name/clka.

For 2): I really don't know what to do.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top