Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 18219
  • 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

Pass veriloga parameter to parameters in ADE XL

JakobToft

I'm working on a circuit which requires long transient simulations for a part of the circuit to settle, and I am therefore trying to utilize the State File options of spectre.
I save the state at a point in my simulation when the load has settled, and start simulations from that point.

I know I cannot change the circuit and use my state file, but I can change the parameters of devices, which is what I want to do.

This works fine in ADE L along with parametric sweep.
But, when I try to sweep global variables in ADE XL, the variables does not change in the simulation. If I change parameters the devices do change in simulation.

My problem is that I have a veriloga block, and it does not seem to be possible to pass a parameter from the veriloga block to the parameters in ADE XL.
I can define the parameter of the veriloga block to be equal to the value of a global variable, but since the global variable has no effect when using a state file, that approach is not usable.

I have not been able to figure it out from the documentation how to pass the veriloga parameter to ADE XL parameters.

Does anyone know how to do this?

Or how to make variables in ADE XL work when using a state file?

Regards

Jakob Toft

Parents
  • Andrew Beckett

    Jakob,

    I don't think I entirely understand what you're saying here - the parameter passing you're describing appears to be a bit back to front - I can't see what would be meant by passing a parameter from Verilog A to ADE XL.

    So I'd advise contacting customer support and then it would be easier to discuss the specifics (and maybe see your screen) of what you're trying to do.

    Andrew.

  • JakobToft
    in reply to Andrew Beckett

    I want to set a veriloga parameter from ADE XL, by adressing the parameter directly and not by using a global variable.

    I have the parameters "slew_rate" and "cycles" in my veriloga block, I would like to sweep the parameter "cycles".

    When I am not using a State File for my simulations I could sweep "cycles" by putting in a global variable name instead of "512", and sweeping the value of that global variable.

    When starting transient simulations from a State File in ADE XL, sweeping global variables no longer has an effect in simulations.

    So I can no longer use the approach of putting in a variable instead of "512".

    But if I could set the value of the parameter "cycles", as I do for the multiplier of capacitor C0 below, then I should be able to sweep the parameter cycles while using a state file.

    //Jakob

  • Andrew Beckett
    in reply to JakobToft
    Andrew Beckett said:
    So I'd advise contacting customer support

    As I said earlier... part of this is that right now I just don't have time to try this out and check behaviour and test what is and isn't working (I think you may be using an older version too - not entirely sure).

    Andrew

Reply
  • Andrew Beckett
    in reply to JakobToft
    Andrew Beckett said:
    So I'd advise contacting customer support

    As I said earlier... part of this is that right now I just don't have time to try this out and check behaviour and test what is and isn't working (I think you may be using an older version too - not entirely sure).

    Andrew

Children
  • JakobToft
    in reply to Andrew Beckett

    I went to customer support, but before submitting a case I found documentation that helped me.

    What I needed to do was to edit the CDF of the veriloga block, as it had been generated in a way such that the Variables and Parameters toolbar in ADE XL could not see the parameters.

    Editing the CDF allowed me to access the parameters of the veriloga block, and I am now sweeping while starting simulations using State Files.

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.