• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Mixed-Signal Design
  3. where does a layout view get verilog module name from?

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 64
  • Views 13104
  • 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

where does a layout view get verilog module name from?

drdanmc
drdanmc over 8 years ago

I'm curious about how layout (and for that matter, symbol and schematic) views in Virtuoso get module names and if this can be accessed and changed via skill.  I've noticed that sometimes if I use the library manager to copy a cell to a new cell, make my various symbol, schematic, and layout updates and then later do:

oa2verilog -lib myLib -cell myNewCell -view layout -verilog -

and look at the module name,  I will see the cell name of the old cell, not the new one.  This can then cause headaches when pulling into encounter with assembleDesign when trying to do an AOT STA.    The only reason I'm using oa2verilog is it seems to be a fast way to check if the module name matches the cell name.

So... can I check this with skill?  I did some digging through cell view properties and didn't find it but stopped short of trying to write skill code to follow every possible path from a cell view id.

Also of note, I get the same mismatch if I check the symbol or schematic view.  I can see the bad value in the binary .oa file (strings file.oa | grep "oldCellName").

My work around is painful.  Instead of copying a cell via the library manager if I want a similar cell, I create each view from scratch and then, for example, go to the old symbol, select all, copy, and paste to the new.  But that is tedious.

Thanks

-Dan

  • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information