Stats

  • Locked Locked
  • Replies 2
  • Subscribers 90
  • Views 2130
  • 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

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

  • Hi aidans,

    From the syntax you show here, it looks like you're using standalone SignalStorm (as opposed to running within SoC-Encounter or Encounter Timing System). Within SoC-Encounter, it seems like [all_outputs]/[all_inputs] would work as you expect:

    encounter 9> help set_driving_cell
    Usage: set_driving_cell [-library ] [-lib_cell
    ] [-pin ]
    [-from_pin ]
    [-rise | -fall] [-min | -max]
    [-input_transition_rise ]
    [-input_transition_fall ]


    It sounds like the behavior is different in standalone SignalStorm. If you're unable/don't want to run SignalStorm from within SoC-Encounter or ETS, maybe you could target the ports with a "*"? Have you tried that? The commands might be smart enough to know that set_load should only be applied to all outputs and set_driving_cell to all inputs.

    Please post back and let us know whether this is still an issue for you.

    Thanks,
    Bob


    Originally posted in cdnusers.org by BobD

  • 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

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.