Stats

  • Locked Locked
  • Replies 3
  • Subscribers 91
  • Views 13219
  • 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

**DIAG message while running a db command

tiEngr

Hi All, 

This is just section of my script that is creating this DIAG message.  In short Iam trying to write every net inside a module. Here I picked one of the module from the design. What I see that this message occurs at the begining of dbForEachCellNet then it does what it suppose to do. Not sure what to make of this message or how to remove it.

 Thanks

Irfan

 

dbForEachCellNet 0x1b7b3c38 cellNetPtr {
    puts "[dbCellName 0x1b7b3c38] [dbVNetName $cellNetPtr] "
}


encounter 77> dbForEachCellNet 0x1b7b3c38 cellNetPtr { puts "[dbCellName 0x1b7b3c38] [dbVNetName $cellNetPtr] "}
**DIAG[dbTclCmd.c:3148:dbiForEachCellNetCmd]: Assert "!dbmIsNetVNet(dbmCellNetList((dbsCell *)p))"
syncstage_54_0 sync
syncstage_54_0 clk
syncstage_54_0 async
syncstage_54_0 reset_N
syncstage_54_0 test_si
syncstage_54_0 test_se
syncstage_54_0 SPCASCAN_N314
syncstage_54_0 fmonDiagReg_0
syncstage_54_0 FE_OFN23_n1
syncstage_54_0 FE_OFN254_softReset_N

  • Can you try using dbGet? The following will report the hierarchical nets for module "iu":

      set modName "iu"

      set modPtr [dbGet -p head.allCells.name $modName]

      set modNets [dbGet $modPtr.hInst.hNets.name]

      puts $modNets

    Regards,

    Brian

  • Thanks Brain,

     This wiil work too.  So is it not recomended to use dbForEach* commands any more.

     

    Irfan

     

  • It's recommended to use dbGet as it is easier to use than trying to remember all the different db* functions. Here are some solutions which are handy for learning dbGet:

    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11618132

    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNu
    mber=11585414

    Regards,

    Brian

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.