Stats

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

avoiding ams re-gen and re-compile the netlist database

DavidLou

hello exports,

I'm using ams to run cosim with both analog (schematic + veriloga) and digital (verilog) blocks. everytime I run it by ocean script, I see it re-generate netlist and then re-compile the design even nothing has been changed yet. 

the log prompt and Ocean script as followed. any clue?

thanks,

David

   Recompiling... reason: file './cds_globals.vams' is newer than expected.
   expected: Mon Sep 10 18:05:29 2018
   actual: Mon Sep 10 18:06:11 2018
   irun: *W,FILOD: The file  ...../ams/cosim_config/netlist/spiceModels.scs is out of date, the exec amsspice will be re-invoked.
   file: ./cds_globals.vams

simulator( 'ams )
solver( 'Spectre )
;open the top schematic view so the simulator can find it in memory for "ocean -replay"
;use "ocean -restore " no longer need this
dbOpenCellViewByType( "lib" "top" "schematic" )

; for config based case
design( "lib" "top" "cosim_config" "r")

ocnAmsSetOSSNetlister()

resultsDir( result_dir )

connectRules("ConnRules_mid")

modelFile(
'("....._usage.scs" "tt_lib")
)
analysis('tran ?stop "1" ?errpreset "conservative" )

envOption(
'amsIEsList '((t "global" "" "1.8" "connectLib.CR_full_fast" "" "logic" "discipline=logic;" "Built-in"))
'builtinuser nil
)

temp( 27 )

run()

  • Andrew Beckett

    David,

    For the same directory, the netlister should be incremental - so it may be it doesn't do too much actual netlisting (although the time may be in the netlist assembly if using UNL - although here you appear to be using the older OSS netlister). Similarly the compilation should actually be incremental - it will run irun again, but it doesn't necessarily recompile everything. There are options in ADE which control whether it does a clean of the simulation data, or does increment modes - but you don't have these in your script.

    Is there a good reason why you're using OSS rather than the newer UNL netlister?

    If you're seeing performance issues, please contact customer support.

    Regards,

    Andrew.

  • DavidLou
    in reply to Andrew Beckett

    Thanks Andrew,

    since it's still kind of re-gen/re-compiling, plus there'll be database locked in running, so I think better to just keep the netlist in different directory for each sim as asked in other thread. 

    the reason to still use OSS is for this: I have a multi-module verilog file which is self-contained with sub-blocks designed and instantiated for AMS cosim (e.g., top, sub1, sub2, sub3,...). I have a digital top cell view for that top block but not any sub-blocks. OSS would find and bind these sub-blocks happily but not UNL (even Hierarchy Editor can't find these sub-blocks). I'm hesitate to create too many more cell views simply for that, as I might keep adding more digital sub-blocks. Is there a way to solve this?

     thanks,

    David

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.