• 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. configure the form! configure the window!

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13179
  • 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

configure the form! configure the window!

imagesensor123
imagesensor123 over 14 years ago

 Hi,

    i don't know how cadence do the following job, but it is really useful for designers.

   i noticed that there are lots of menus in ADE window, such as "setup" "tools" and so on. i have developped a new form, and i know we can use the hiCreateFormWindow to attach a form to a window with menus.  i think a form will turn up if you push the "setup" menu in ADE window, and user can set some opinions . so the problem is that how can we save the change ,and i find a file name si.env under every design folder, we can see the following contents in that file:

simLibName = "zhenfu"
simCellName = "pdpixel"
simViewName = "schematic"
simSimulator = "spectre"
simNotIncremental = nil
simReNetlistAll = 't
simViewList = '("spectre" "cmos_sch" "schematic" "veriloga")
simStopList = '("spectre" "ahdl" "veriloga")
simNetlistHier = 't
nlFormatterClass = 'spectreFormatter
nlCreateAmap = 't
nlDesignVarNameList = '("rstWidth" "delay" "width" "power" "period" "cpix" "w4" "w3" "w2" "w1" "vbias" "tperiod" "l4" "l3" "l2" "l1")
simViewList = '("spectre" "cmos_sch" "schematic" "veriloga")
simStopList = '("spectre" "ahdl" "veriloga")
simNetlistHier = t 

so how can we generate this file and how does it work?

welcome to any suggestion, thanks!

Regards,

zfeng

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 14 years ago
    Zfeng,

    Your question doesn't make an enormous amount of sense to me, and I'm not sure what you're actually trying to achieve here.

    When you interact with the forms in ADE, these store data in some internal data structures. These can be committed to disk with Session->Save State, and restored using Session->Load State.

    During various parts of the flow, various additional files will get created on a transient basis - for example, the si.env file gets created as part of the netlist creation. It contains information needed to initialise the netlist. Whenever you do a Netlist or Netlist and Run operation it will get created. Not sure why you would care though...

    Regards,

    Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 14 years ago
    Zfeng,

    Your question doesn't make an enormous amount of sense to me, and I'm not sure what you're actually trying to achieve here.

    When you interact with the forms in ADE, these store data in some internal data structures. These can be committed to disk with Session->Save State, and restored using Session->Load State.

    During various parts of the flow, various additional files will get created on a transient basis - for example, the si.env file gets created as part of the netlist creation. It contains information needed to initialise the netlist. Whenever you do a Netlist or Netlist and Run operation it will get created. Not sure why you would care though...

    Regards,

    Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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