instance renaming

Could you clarify whether you are truly looking to change the level of hierarchy at which the instance resides? In other words, if I specified the a/b hierarchial instance as a partition, and the design was partitioned after renaming a/b/c to x/y/z- would you expect to see x/y/z within the netlist written out for a/b?

Thanks,
Bob

 Hi Bob,

I'm not looking to change the hierarchy of the instance. I still want to maintain the same hierarchy, but just want to rename the instance.

I have a db whose one module name is changed in the latest verilog. Instead of redoing the entire flow, i'm trying to convert the existing db to match with the new netlist.

 Is there any way to do it?

Thanks,

Rajesh

### usage: rename_FEhcells  a/b/c  a1/b1/c1 

proc rename_FEhcells { oldhcell newhcell } {

set ptr_oldhcell [dbGetHInstByName $oldhcell]
set ptr_newhcell [dbGetHInstByName $newhcell]
set i 0
dbForEachHInstTreeInst $ptr_oldhcell instptr {
 set oldHinst [dbInstName $instptr]
 set oldhcells_rootpath_length [expr [string length $oldhcell] + 1]
 #set last_name [dbInstBaseName $instptr]
 set last_name [string range $oldHinst $oldhcells_rootpath_length end]

 set cellName [dbInstCellName $instptr]
 set instLoc [dbInstLoc $instptr]
 set x [dbDBUToMicrons [lindex $instLoc 0] ]
 set y [dbDBUToMicrons [lindex $instLoc 1] ]

 set R [string range [dbInstOrient $instptr] 3 end]

 deleteInst  $oldHinst
 addInst -cell $cellName -inst $newhcell/$last_name -loc $x $y -ori $R   -physical

incr i

                                              }
puts "#######################################################"
puts "Total $i Hinsts changed Hierarchy for ECO in Encounter!"
puts "#######################################################"
}
~                                              

magicflute said:

### usage: rename_FEhcells  a/b/c  a1/b1/c1 

proc rename_FEhcells { oldhcell newhcell } {

set ptr_oldhcell [dbGetHInstByName $oldhcell]
set ptr_newhcell [dbGetHInstByName $newhcell]
set i 0
dbForEachHInstTreeInst $ptr_oldhcell instptr {
 set oldHinst [dbInstName $instptr]
 set oldhcells_rootpath_length [expr [string length $oldhcell] + 1]
 #set last_name [dbInstBaseName $instptr]
 set last_name [string range $oldHinst $oldhcells_rootpath_length end]

 set cellName [dbInstCellName $instptr]
 set instLoc [dbInstLoc $instptr]
 set x [dbDBUToMicrons [lindex $instLoc 0] ]
 set y [dbDBUToMicrons [lindex $instLoc 1] ]

 set R [string range [dbInstOrient $instptr] 3 end]

 deleteInst  $oldHinst
 addInst -cell $cellName -inst $newhcell/$last_name -loc $x $y -ori $R   -physical

incr i

                                              }
puts "#######################################################"
puts "Total $i Hinsts changed Hierarchy for ECO in Encounter!"
puts "#######################################################"
}
~                                              

Are you sure with this solution? It will only construct a DUMMY hier instance with not right connections. Please think harder when you want to propose an answer.

this script should be used for postmask eco flow.   after performing the script, you should modify the DEF file.(for hier renamed cell ,there will be such as a/\b/\c  structure, which should be manully modify to a/b/c) , then do ecoDefIn old.def  .  it will restructure the netlist database for routing.