• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. ADE XL - Adding a pre-run script

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 4435
  • 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

ADE XL - Adding a pre-run script

Michele Ancis
Michele Ancis over 9 years ago

Hi, I am using Virtuoso 6.1.6-64b.500.10

MMSIM version 131_ISR10

Spectre version 13.1.1.205.isr10 32bit

I had used a pre-run script in a previous life and I seem to remember - especially for the use I made - it was fairly simple to set up.

I wanted to rebrush my knowledge in view of a more advanced use, but I find I am stuck at the really basics, so I am checking whether I am doing something fundamentally wrong or something else is preventing me to achieve my goal.

I do what I think should be the easiest thing, i.e. from an ADE XL test, just right-click -> Pre-Run script... then choose "a" template (there is only one ;-)), enable it by ticking the box, and slightly modifying it.

 

In detail:

 

  1. I have a simple test bench with a capacitor, whose value is declared as
  2. Cvar a variable
  3. I set up an adexl view with Cvar as a global variable
  4. RMB on test name, Pre-Run script --> Load Template --> modify --> enable
  5. The template is an OCEAN file fully commented out. For my purposes, I just want to  change the value of Cvar , therefore all I do is to add a statement like: desVar( "Cvar" 3p )
  6. I run the simulation

I cannot observe any hint, after the run cycle, of the pre-run script having been launched. I find no trace of it, neither in the Output Log, nor CIW.

If I observe the netlist actually input to the simulator, I see that Cvar has the unchanged value, not the one that should have been set by my desVar() statement.

Am I doing something fundamentally wrong?

I found this interesting appNote, where one can read on page 21:

 For releases before IC6.1.6 ISR3, add just a printf(“ “) in the editor and save it with .ocn extension and click at the Enable checkbox (only needed for testverif). In the later versions of IC6.1.6 ISR3 and above, just enabling the ‘Pre Run Script’ would turn on the functionality.


The text above is referred to the addition of a Pre-run script. I did add the dummy printf() statement, however I could not find a way of referencing the *.ocn file, no matter what I selected in the dialog box, I always ended up pointing at preRunScript, not my preRunScript.ocn

All in all I am not sure I am doing something wrong or there is a detail I am missing, because I do not remember sweating this much last time I tried!

Thanks for any hints,

Michele

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Michele,

    First of all, any messages will go into the job log file, not the normal CDS.log - because it's run by the ICRP processes.

    However, it's probably simplest to contact customer support so that we (or rather one of the team since I'm on vacation!) can take a look at your issue via a web-sharing session. This ought to be fairly straightforward, so it will be much easier to see what is going wrong that way.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Michele Ancis
    Michele Ancis over 9 years ago

    Andrew,

    well...Thanks for replying even when on vacation!

    I have checked Output Log, Run Log, Job Log :-O

    Job Log is a large file compared to the other two, some 2000 lines, but apart from functions redefined and other seemingly unrelated warnings I could not spot any hint of pre-run activity.

    Anyhow, I filed a ticket :-)

    Thanks!

    Michele

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information