• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Logic Design
  3. how to identify unique nets connected to preset/clear pins...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 62
  • Views 1342
  • 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 identify unique nets connected to preset/clear pins of all FFs in a scope

Sporadic Crash
Sporadic Crash over 11 years ago

I have not been able to find an attribute that shows whether a net in a scope is connected to a preset/clear of FF. 

The only way I have found:

foreach FF in a scope {
 foreach pin of this FF {
  if { libpin of this pin is a {async_clear} } { set an async_clear net }
  if { libpin of this pin is a {async_preset} } { set an async_preset net }
  if { libpin of this pin is a {sync_clear} } { set a sync_clear net }
  if { libpin of this pin is a {sync_preset} } { set a sync_preset net }
}
}

This is quite complicated, because in a certain block there can be several FFs each of which can be resetted in a different way, thus HW designer might need to create a TCL associative array to identify unique nets.

Is there an easier way to do this?

  • Cancel
  • grasshopper
    grasshopper over 11 years ago

     Hi Sporadic Crash,

     logical nets have 'driver' and 'loads' attributes

     instances have a libcell attribute 

     libcell have attributes async_clear, async_preset, sync_clear, sync_preset

     That should provide all the pieces of needed solution

    gh-

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information