Stats

  • Locked Locked
  • Replies 6
  • Subscribers 127
  • Views 3600
  • 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

Using ALTER statement in ADEL/XL

AlbertoGS

Hi,


I am trying to modify the width of some devices in a extracted view. The normal flow would be to modify the width in the schematic and then re-extract the cellview. However, as a hack I want to be able to modify the design and test it with a different width. I could manually modify the netlist but this is cumbersome when using ADEL/ADEXL and launching a new job recreate a new netlist without my changes.


I am aware that in Spectre it is possible to use ALTER statements to achieve this. It is possible to do the same in ADEL/XL? where can I add such command?

Many thanks,

Alberto Gomez

  • AlbertoGS
    How will a design variable help me change a parameter (say width) of an already extracted view?
  • Frank Wiedmann
    I was not talking about design variables but about device instance parameters.
  • AlbertoGS
    Thanks for that! I wasn't aware of that possibility.

    However, it doesn't completly solved my problem. I am only able to add a instance parameter in the schematic view not in the extracted (as it appears as a layout with tons of parasitc components). And adding the parameter in the schematic will not have any effect in the extracted view. Any suggestion?
  • Frank Wiedmann

    I must admit that I have not tried it with an extracted view yet. However, in my extracted views, I can select the devices in the layout and view their instance properties like for example the instance name. This might be tool-dependent, however (we are using QRC).

  • Andrew Beckett

    You have to be using QRC and at least IC616 for this to work (that's when support for extracted view parameters was added, if my memory is correct - it might have been an IC616 ISR, so check you're using something recent).

    Andrew

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.