Stats

  • Locked Locked
  • Replies 8
  • Subscribers 143
  • Views 15402
  • 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

Auto-create an ADE state, howto?

GaneshShamnur
Hi All,

In a flow that I am working at, an ADE session state needs to be created automatically after a testbench schematic is created.

An ADE state is desired to have analysis, design-variable-values and signals-to-be-saved in it.I am thinking of below two approaches:

Approach 1: Without user-intervention Having known the format of ADE state ( a directory with several .state files ), we can create such directory and create the required files.

Cons:

a) This method of saving state is without using native SKILL routines  but instead of simple file-writing routines with logic.

b) If ther format/syntax of an ADE state is changed by Cadence in future releases, this approach would fail.

Approach 2: With user-interventionRequest User to open an ADE session. Thereafter trigger an action to perform the required ADE settings.

Cons:

a) An intermediate step of User invoking an ADE session is required.

 
Any ideas/suggestions on the above approaches?

Please mention if you have any other ideas altogether.


Thanks,

Ganesh

  •  Ganesh,

    I would strongly advise against using 1 - it is likely to change. There really is no public API to create an ADE state outside of ADE - whilst in theory it might be possible using the asiSaveState() API, that requires a "sev" (simulation environment, i.e. ADE window) around to about to save the state. That's because mostly the save state functionality is really part of the ADE interface.

    Andrew.

  • Hi Andrew, Thanks for the reply. I tried the below two methods to save state and my inferences are as below: Schematic and ADE are open. Both were opened manually.

    Method 1:

    sevS = hiGetCurrentWindow()->sevSession

    // Obtain ADE's o_session

    sevSo1 = sevEnvironment(sevS)

    //Add a new DesignVariable

    asiAddDesignVarList(sevSo1, list('("x" "1"))

    //Save state

    sevSaveState(sevS)

    This opens a FORM to save the state. Human interface needs to be avoided !

     

     

    Method 2:

    so2 = asiGetCurrentSession()

    //Add a new DesignVariable

    asiAddDesignVarList(list('("x" "1"))

    // Save ASI State

    asiSaveState(so2)

    WARNING (ADE-1071): Cellview nil of type nil already exists.

    nil

    Above warning appears. However, so2->cellName has the correct value and is not 'nil'. But so2->name is nil.

    Any clues on which approach is right and if Method(2) is correct, what is wrong in ASI state not getting saved.

     

    Thank You,

    Ganesh

  • Run out of time to check now, but my first guess is that in method 2 you need to provide some of the keyword arguments to asiSaveState (such as ?name, ?cell, ?lib etc) - see the documentation. Note that it's the lib/cell/view of the state that matters here, not the design.

    Andrew

     

  • Hi Andrew,

     

    Your guess was partly correct. The API needed 'name' parameter.

    After passing a name for the state to save, i.e asiSaveState(so2 ?name "spectre_custom_state"), a proper ADE session state could be saved.

     

    However, the interesting question is why does it seek 'name' as argument while the session-object already has a value for 'name'.

    In API description, 'name' is an optional argument.Moreover the warning message didn't mean that either !.

    But the API does work. Thank You.

     

    Best Regards,

    Ganesh

  • Ganesh,

    How would the session object have a name for the state? I agree the error messages are not that great though - this API doesn't have as much checking as it should...

    Andrew.

  • Hi Andrew,

    I meant about the default 'name' a session picks.

    I expect it to save with the same name when no 'name' parameter is passed.

    e.g:

    se4 = asiGetCurrentSession()

    se4->name

    spectre6

     

    So, 'spectre6' is the expected state to be saved.

     

    Best Regards,

    Ganesh

  • Ganesh,

    I have no idea why you think that name would have anything to do with the state name. It's a unique name given to the session (used to generate unique identifiers for certain objects), and is unrelated to the name of the state that you are saving.

    It doesn't (as far as I know) say anywhere in the documentation that this is the state name.

    Note that in general you should not be querying attributes on asi objects - these are not a public interface and may change without warning. Instead you should use the public API to isolate you from any necessary implementation that we might have to make to improve the tools in the future.

    Regards,

    Andrew.

     

  • Hi Andrew,

    Thanks for the explanation.

    Regards,

    Ganesh 

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.