Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 2009
  • 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 netlist/elaboration views

caveman54

I have a large digital block that I am simulating at gate level in a mixed signal (ams/spectre) environment. It has 200K verilog gate modules in it so it takes a large amount of time to netlist and create the elorated views. The digital block does not change. Can I save the netlist and/or elaborated view and point the ams simulator to those views for use on later suimulations? It seems everytime I simulate, say after changing temperature, the simulator re-netlists and recreates the elaborated views.

Thanks - caveman

  • Hi Caveman,

    AMS has an option to compile/elaborate incrementally, i.e. only modified modules are getting recompiled/re-elaborated. You must use incremental insted of 'all'.

    Cheers,

    Riad.

  • Thanks Riad- that works great. Is there any way to save the netlist/elaboration files for the large digital block so that other members of the team can use them without they having to go thru the long netlist/elaboration cycle? Can I create a view and place these files in them and point the HED to that view?
     
    Caveman
  • The Snapshot from elaboration is written into the simulation directory when using AMS in ADE.I haven't used AMS from the HED plugin for a while and as far as I can remember, AMS in HED writes the snapshots into the design libraries unless specified otherwise using some AMS options (implicit_tmp_dir ... etc). Assuming the snapshot is written down into the design library and all users are pointing to the same design library, then all of them would see the same snapshot. hence, if nothing changes in the origin, then all designers will see the compile/elab skipping that digital block.I do admit I don't use the above mode. I run AMS in ADE and every designer get his own simulation directory with everything compiled/elaborated the first time and then in incremental as design evolves. This is the best option I could find. I would advise a similar approach too, i.e. avoid working into the same area as multiple write could lead into more troubles. you Cadence AE can give you more advise in the matter as I'm a bit biaised towards my approach :-)

    Cheers,Riad.

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.