Stats

  • Locked Locked
  • Replies 2
  • Subscribers 91
  • Views 2713
  • 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

dbGet query inst/term driver

fitz

I have a list of max transition terminal violations from a third party tool : ( .
ie.  <inst>/<term> max_tran tran violation
coding/CODING_SW_REGS_inst/v8_lite_inst/A   0.6800   0.7106  -0.0306 (VIOLATED)

I would like to find out the instname/cellname and netname of the driver driving a specific "terminal".
Online support search pointed me to the following  ... very very close ... but not quite.

Useful single line dbGet scripts
Solution ID:    11598038

27. To find out the instname/cellname of the driver driving a specific net.
    set netName <netName>
    set inst [dbGet [dbGet -p [dbGet -p top.nets.name $netName].allTerms.isOutput 1].inst]
    Puts "Net: $netName, driving inst name: [dbGet $inst.name], driving cell name: [dbGet $inst.cell.name]"

Any dbGet gurus out there??

Shawn

  • Hi Shawn,

    Looks like you need to traverse from instTerm to net then you'll have it?

    With dbGet you can string match on instTerm off the inst like this:
    encounter 3> dbGet [dbGet -p top.insts.instTerms.name i2/A].net
    0x2aaab4c7e0c0

    But really, this is one of those cases where I find it more straightforward to go to older-style FE-TCL commands for a single command that gets instTerm pointer by name:
    encounter 4> dbGetTermByInstTermName i2/A
    0x2aaab51a5110
    encounter 5> dbGet [dbGetTermByInstTermName i2/A].net
    0x2aaab4c7e0c0

    Either way should work the same.

    Hope this helps!
    -Bob
  • Bob: Bingo, Thank You.
    When I get past this tape out I 'm going to seriously study dbGet.
    Shawn

     

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.