Home > Community > Forums > Digital Implementation > How to constraint the Input/output Port in SignalStorm?

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 How to constraint the Input/output Port in SignalStorm?  

Last post Sun, Feb 3 2008 4:45 AM by archive. 2 replies.
Started by archive 03 Feb 2008 04:45 AM. Topic has 2 replies and 1276 views
Page 1 of 1 (3 items)
Sort Posts:
  • Sun, Feb 3 2008 4:45 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    How to constraint the Input/output Port in SignalStorm? Reply

    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
    • Post Points: 0
  • Thu, Feb 7 2008 5:57 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: How to constraint the Input/output Port in SignalStorm? Reply

    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
    • Post Points: 0
  • Tue, Feb 12 2008 10:58 PM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: How to constraint the Input/output Port in SignalStorm? Reply

    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
    • Post Points: 0
Page 1 of 1 (3 items)
Sort Posts:
Started by archive at 03 Feb 2008 04:45 AM. Topic has 2 replies.