Stats

  • Locked Locked
  • Replies 4
  • Subscribers 90
  • Views 14033
  • 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

How to get the database address of the subModule?

archive

In GUI design bowser, I can see the level ONE sub-module, I know dbgTopCell return the top level Module address. Now in my scripts, I need the database address of these cells, How can I get this ?


Originally posted in cdnusers.org by aidans
Parents

  • Thank you for your in-time response to my post.
    By dbGet*ByName do retrieve the DB address of the NAMED Objects. To use these kind of command, I must know the hierarchical topology of my verilog netlist, which means I must know the sub-modules’ name.

    Of cause I can open the Design Browser, and type the sub-modules’ name into my scripts. But this is not a good way to do things, since my scripts are also used by other Block-level designers. (we use hierachical design method to implement the back-end design flow), It’s better to get the sub-module names automatically.

    I come across this question while I writing scripts to get the sub-module related IO Pins.
    dbForEachCellFTerm [dbgTopCell] ftermPtr { } get all the PINs.
    If I use this scripts structure, I have lots of pain to decide which sub-module of particular PIN belongs to. So if I can get the Level ONE sub-module names, then I can report the IO Pins related to this sub-module in a neat way:
    dbForEachCellFTerm $subModuleCellPtr ftermPtr { }


    Originally posted in cdnusers.org by aidans
Reply

  • Thank you for your in-time response to my post.
    By dbGet*ByName do retrieve the DB address of the NAMED Objects. To use these kind of command, I must know the hierarchical topology of my verilog netlist, which means I must know the sub-modules’ name.

    Of cause I can open the Design Browser, and type the sub-modules’ name into my scripts. But this is not a good way to do things, since my scripts are also used by other Block-level designers. (we use hierachical design method to implement the back-end design flow), It’s better to get the sub-module names automatically.

    I come across this question while I writing scripts to get the sub-module related IO Pins.
    dbForEachCellFTerm [dbgTopCell] ftermPtr { } get all the PINs.
    If I use this scripts structure, I have lots of pain to decide which sub-module of particular PIN belongs to. So if I can get the Level ONE sub-module names, then I can report the IO Pins related to this sub-module in a neat way:
    dbForEachCellFTerm $subModuleCellPtr ftermPtr { }


    Originally posted in cdnusers.org by aidans
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.