• 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. AMS / readic SCS file

Stats

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

AMS / readic SCS file

david0526
david0526 over 10 years ago

hello,

I'm using readic option with AMS to load EE default settings before running my sims.  Presently I have to specify the testbench name for every line item in the .scs file.  Is there a way to make the testbench name a "variable" that can get loaded automatically (instead of me manually changing the .scs file for every testbench in my library)?  I know for probe.tcl files this is possible by doing something like:

>> set testbench_name [scope]

and then using it in the probe statements, i.e.

>> probe -create -emptyok -database ams_database -flow "$testbench_name.I_dut.etc"

Any help would be appreciated!

Thanks in advance.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    I don't understand what you're doing (what are "EE default settings"? Why do you need to specify the testbench name for every line item in the .scs file - it's unclear what you're doing).

    Please clarify (ideally with something to illustrate it)?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • david0526
    david0526 over 10 years ago

    Hi Andrew,

    Thank you for the reply, sorry I wasn't very clear.

    I have an EEPROM block that requires initialization.  I've been doing this by specifying a "default_trim.scs" file in the readic field under "algorithm" tab in Transient sim options.  Here's a snapshot of what the file contains (I'm told this is the format that the PDK requires for the EEPROM model):

    (CellName).IDUT.EEPROM.I_NVM.USER_1.M3.INITIALVOLTAGE -1
    (CellName).IDUT.EEPROM.I_NVM.USER_2.M3.INITIALVOLTAGE -1
    (CellName).IDUT.EEPROM.I_NVM.USER_3.M3.INITIALVOLTAGE -1
    (CellName).IDUT.EEPROM.I_NVM.USER_4.M3.INITIALVOLTAGE 1
    (CellName).IDUT.EEPROM.I_NVM.USER_5.M3.INITIALVOLTAGE -1
    (CellName).IDUT.EEPROM.I_NVM.USER_6.M3.INITIALVOLTAGE -1
    (CellName).IDUT.EEPROM.I_NVM.USER_7.M3.INITIALVOLTAGE -1
    (CellName).IDUT.EEPROM.I_NVM.USER_8.M3.INITIALVOLTAGE -1

    where "(CellName)" is the name of my testbench.  "-1" and "1" specify burned/not_burned in my model.  Presently, for every testbench I build I have to manually replace (CellName).  I would like to (ideally) have (CellName) auto-populate so that way I can use only 1 file for all the testbenches (instead of a single file per testbench).

    Please let me know if I'm still not describing the issue sufficiently.

    Thank you for the help.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    I meant to reply to this a while ago, but somehow overlooked it in the run up to Christmas.

    This is not possible as far as I know. I can see why you want to do it, but initial conditions files can't have a prefix added to them, and don't support any parameterization. BTW, giving the file a ".scs" suffix is a bit confusing, because that suggests it is in spectre netlist syntax, whereas in fact it's a "nodeset" or "ic" file (which is just node-value pairs).

    If you want something like this, it would require an enhancement to the simulator, and so you should contact customer support.

    Kind Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • david0526
    david0526 over 10 years ago

    Thank you for the follow-up, Andrew.

    I ended up creating a "unified" testbench for all my tests of interests, this way I keep the testbench name same in the reaic file, and just change variable in the AMS state.

    David

    • 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