Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 15025
  • 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

ADEXL: automaticaly include extracted view

kwsgk

Hi all.

I'm using ADEXL with spectre simulation with Extracted view Created by QRC.

Simulation work well, but I have a problem that it consumes much file size.

One of the reason is input.scs, it involve netlist of extracted view.

For some corner condition simulation or montecarlo, it makes a lot of input.scs, each of them

involve extracted view(~300MB), total file size become very large. But all of extracted view is same. 

Are there any way to shrink input.scs size automatically?

I know that include netlist and replace cell to black box cell avoide this problem, but converting extracted view to netlist one by one and make those cell manually 

are time consuming and cause typo or some mistake. I'm glad if there are some setting to  treat them as include netlist automatically.

Best Regards

KAWAI

Parents

  • Hi Kawai,

    You can use:

    envSetVal("adexl.simulation" "ignoreDesignChangesDuringRun" 'boolean t)

    in your .cdsinit (note, the CIW would be insufficient) or:

    adexl.simulation ignoreDesignChangesDuringRun boolean t

    in the ~/.cdsenv (typically this needs to be your home dir).

    This enables another setting which generates a single netlist for all points and then includes it in each individual run. The effect of ignoreDesignChangesDuringRun is to run netlisting up front, so be aware that this will lead to a delay before simulations start for big designs. Note that the individual setting singleNetlistForAllPoints is not recommended on its own - there are some issues with this which mean that the netlist can get messed up sometimes - so we recommend  you use the ignoreDesignChangesDuringRun setting instead which achieves the same thing.

    We have  new Extracted view format coming in EXT18.2 (out soon) and IC618 (due out October) which should also help significantly too.

    Regards,

    Andrew.

  • in reply to Andrew Beckett

    Hi Andrew,

    Just a follow up question. Would this setting work with Maestro?

    If not, how can we have the same setting for Maestro?

    Thanks and regards,

    Duy-Dong Pham

  • in reply to DuyDong

    Dear Duy-Dong Pham,

    I am not Andrew and will certainly not pretend to have his depth of knowledge!!

    However, I do know that even though the syntax for many former ADE-XL settings contains the "adexl" prefix, maestro honors the same command. I did ask customer support at one time about this as it can be confusing. I was told too many customers were using the former ADE-XL setting syntax in their designs and the effort to change was considered excessive. Hence, Cadence decided to not update the syntax of the ADE-XL settings to one including the "maestro" prefix.

    The setting "adexl.simulation ignoreDesignChangesDuringRun boolean t" is  further confirmed to work in Assembler (with the exception of the "parameters" check-box in versions prior to IC6.1.8/ICADVM18.1 ISR15  as shown at URL:

    https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O3w00000ADokcEAD&pageName=ArticleContent

    and after ISR14 this issue is resolved...

    https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O3w00000AAlADEA1&pageName=ArticleContent

    If you are just modifying an existing netlist, in lieu of re-netlisitng, you could explore using a reference netlist.

    I hope this helps!

    Shawn

  • in reply to ShawnLogan

    Dear Shawn,

    Thanks a lot for your detail reply!

    Duy-Dong

  • in reply to DuyDong

    Dear Duy-Dong,

    I am just glad it was helpful! Good luck!

    Shawn

Reply 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.