Stats

  • Locked Locked
  • Replies 5
  • Subscribers 90
  • Views 15534
  • 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

Get all register related to ONE clock?

archive

    we have ECLK and MCLK in my design, I now want to list all the registers related each of the clock. Here is the porblem I met.

Approach One:
dbForEachCellInst [dbgTopCell] instPtr {
    set cellPtr [dbInstCell $instPtr]
    if {[dbIsCellStdCell $cellPtr]} {
      if {[dbIsCellSequential $cellPtr]} {
        dbForEachInstTerm $instPtr termPtr  {
        dbIsTermClk $termPtr
        ......

But I can know which clock this term is connect to

Approach Two:
dbForEachHeadClock [dbgHead] clockPtr {
        set sel [dbIsClockSel $clockPtr]
        set name [dbClockName $clockPtr]
        puts "$name"
}
setClockDomains -sClk ECLK -dClk ECLK  -fromType register -toType register e

I now want to use this command, dbForEachClockDomainInst, but I don't know the syntax since the Encounter Database Access Command Reference did tell use how to used it.

Any suggestion and feedback is welcome! Thanks 


Originally posted in cdnusers.org by aidans
Parents

  • Yes, we can trace all the clock net in theory, since there are limited clock nets in the database.
    But I think this kind of appoach is to difficult to handle more complex clock tree. Is there a smart way to do this ?

    In PrimeTime, we can get this register list easily. And now we try to do all the thing inside SOC Encounter, since we our backend team use Encounter flow.


    Originally posted in cdnusers.org by aidans
Reply

  • Yes, we can trace all the clock net in theory, since there are limited clock nets in the database.
    But I think this kind of appoach is to difficult to handle more complex clock tree. Is there a smart way to do this ?

    In PrimeTime, we can get this register list easily. And now we try to do all the thing inside SOC Encounter, since we our backend team use Encounter flow.


    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.