• 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. Digital Implementation
  3. How to constraint the Input/output Port in SignalStorm?

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 90
  • Views 2131
  • 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 constraint the Input/output Port in SignalStorm?

archive
archive over 17 years ago

I use the SignalStorm to calculate delay, the scripts use db_delay db_screen like command.

 I know there are two ommand  related to the IO enviroment, set_driving_cell and set_load
and  there are sytax in the docs, but I could not set it right in my scripts.


set_load
set_load
{-pin | -net | -inst}
name
value


set_driving_cell
set_driving_cell
-pin [cell]:pin
-cell cell_name
-from input_pin
-to output_pin

How should  I define all the Inputs ports or the outputs ports ?

[all_inputs] and [all_outputs] do NOT work.

Anyone interested this problem ?


Originally posted in cdnusers.org by aidans
  • Cancel
Parents
  • archive
    archive over 17 years ago

    Thanks Bob

    Yes, It is standalone version of Signalstorm

    with your sugesstion, I use * as the target port, porblem is solved.
    The driver cell and load have effect as expected.

    The tools are really very smart.

    Thank YOU !


    Originally posted in cdnusers.org by aidans
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 17 years ago

    Thanks Bob

    Yes, It is standalone version of Signalstorm

    with your sugesstion, I use * as the target port, porblem is solved.
    The driver cell and load have effect as expected.

    The tools are really very smart.

    Thank YOU !


    Originally posted in cdnusers.org by aidans
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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