• 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 SKILL
  3. Testbench Variables in Ocean Prerun Script

Stats

  • Replies 0
  • Subscribers 143
  • Views 357
  • Members are here 0

Testbench Variables in Ocean Prerun Script

Paul Staerke
Paul Staerke 22 days ago

Hello,
I encountered a strange behavior in ADE Assembler with a prerun script for which I could not find any documentation.
I have an Ocean script which is supposed to generated some input files for Spectre based on the current value of multiple design variables. It looks something like this:

ocnxlLoadCurrentEnvironment( ?noAnalysis t)
...set some defaults...

foreach(dvar desVar()
   ...override defaults with 'dvar'...
);foreach

The script itself seems to work fine, but after I deleted some variables from my ADE testbench it started to produce wrong results.
After a lot of debugging and head scratching I found out, that 'desVar()' does not only returns the current variables defined in ADE, but also additional variables directly saved to the testbench cellview.

I usually do not save design variables to the cellview, but it seems this was done automatically after I did a 'Local Optimization' and back-annotated the result.
After I deleted the 'designVarList' property from the cell, the script worked fine again.

However, I now always have to check if the testbench cell has some variables saved in it and manually delete them. 
Is there a way to get only the ADE variables in a prerun script? I checked the generated netlist of my testbench and here only the actual ADE variables are used.

Best regards
Paul

  • Sign in to reply
  • 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