Stats

  • Locked Locked
  • Replies 1
  • Subscribers 90
  • Views 12985
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Renaming a spare module

KVBABU

 
Hi All,

Iam handling a hierarchical mixed signal design, in which i dont have spare modules either at block level  or at top level. So i have added them using "createsparemodule " command.
But, unfortunately, i have added them with same name at block level and at top level. So, i wanted to rename the spare module either at block level or at top level.

Is there any script or encounter command to this ? . I dont want to delete the existsing module and add again with new name. Because, all the exsisting spare  modules were spreaded evenly in between the exsisting logic. So , i expect that removing and adding spare cells may disctrub the exisiting scenario of my layout which is very timing critical.

PLease help in this regard .

Thanks in advance.

Regards,
K.VISWANADH BABU

Parents
  • Kari

     A general practice is to include the block name as a prefix to the spare module so you don't have conflicts at the top level. But it sounds like it's too late for you to go back now. What I would probably do is edit the verilog and def to have the new spare module/cell names. It can be tricky, depending on how complex your design is. You may want to write a perl script or something to do it. 

Reply
  • Kari

     A general practice is to include the block name as a prefix to the spare module so you don't have conflicts at the top level. But it sounds like it's too late for you to go back now. What I would probably do is edit the verilog and def to have the new spare module/cell names. It can be tricky, depending on how complex your design is. You may want to write a perl script or something to do it. 

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.