Stats

  • Locked Locked
  • Replies 8
  • Subscribers 91
  • Views 17368
  • 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 Connectivity Information between given modules

Nataraja G

after searching the pdf i found this dbHInstConnection but  it say's not working !!!

can i get that information from dbGet commands .....

 

thks in advance ..... 

Parents

  • I think that would work, but it might be more efficient to capture the nets associated with each hinst and then find the nets common to both hinsts. There's a script in the gifts dir that could help with the list intersection part:

    encounter 12> set hinst1 [dbGetHInstByName DTMF_INST/TDSP_CORE_INST]
    0x2aa8959d60
    encounter 14> set hinst2 [dbGetHInstByName DTMF_INST/RESULTS_CONV_INST]
    0x2aa895a8c0

    encounter 15> set a [dbGet $hinst1.hInstTerms.net]
    encounter 16> set b [dbGet $hinst2.hInstTerms.net]

    encounter 16> source <path_to_gift_scripts>/userListUtilities.tcl
    encounter 17> userIntersectLists $a $b
    ->returns list of nets common to 2 hinsts

    -Bob

     

Reply

  • I think that would work, but it might be more efficient to capture the nets associated with each hinst and then find the nets common to both hinsts. There's a script in the gifts dir that could help with the list intersection part:

    encounter 12> set hinst1 [dbGetHInstByName DTMF_INST/TDSP_CORE_INST]
    0x2aa8959d60
    encounter 14> set hinst2 [dbGetHInstByName DTMF_INST/RESULTS_CONV_INST]
    0x2aa895a8c0

    encounter 15> set a [dbGet $hinst1.hInstTerms.net]
    encounter 16> set b [dbGet $hinst2.hInstTerms.net]

    encounter 16> source <path_to_gift_scripts>/userListUtilities.tcl
    encounter 17> userIntersectLists $a $b
    ->returns list of nets common to 2 hinsts

    -Bob

     

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.