• 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. Digital Implementation
  3. Innovus: getting area value of a sub module from the hi...

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 91
  • Views 14891
  • 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

Innovus: getting area value of a sub module from the hierarchy

Edouardfr
Edouardfr over 6 years ago

Hello,

I am trying to get the area value of a submodule from innovus through a script (after importing my design).

My top_module is named grid_clb and the sub module of interest is "grid_clb_0_/fle_0_".

I tried doing the following:

-----

selectObject Module grid_clb_0_/fle_0_

dbGet selected.box_area

But it returns 0x0.

-----

Another thing I tried is to do:

-----

ungroup grid_clb_0_
deselectAll
selectObject Module grid_clb_0_/fle_0_

dbGet selected.box_area

-----

This method works only if I do it manually. If I use a script doing all of those commands through a procedure:

proc get_ble_area {} {
ungroup grid_clb_0_
deselectAll
selectObject Module grid_clb_0_/fle_0_
set ble_area [dbGet selected.box_area]
return $ble_area
}

I basically have to call this procedure twice by hand (since the first time I call it, it ungroups the top module but still returns 0x0 for the area).

If I call this procedure twice in my top level script, it does not work. I still have somehow to call this procedure by hand through the innovus terminal. I feel like I am missing something with using the ungroup command through script.

Would it be another way to proceed in order to get this specific module area?

Thanks,

Edouard

  • 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