Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 3394
  • 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

How to avoid compiling Verilog/sytemVerilog views every time you netlist (AMS)?

iguerra

Hi,

I would like to know if is possible to avoid compiling the Verilog/sytemVerilog views every time you generate an AMS netlist in ADE-L (based on a config file with a sytemVerilog template).

The compilation time is extremely long and I only want  to confirm if there is no netlist errors (no simulating).

Thanks.

Parents
  • Andrew Beckett

    First of all, cell-based is obsolete nowadays - you really should move to using UNL (especially with recent versions, as you're presumably using if using ICADV - you didn't say which number though). However, regardless of that...

    1. Unchecking the "incremental" options will just cause it to compile all, I think. So you should check the incremental options.
    2. There normally isn't a "clean snapshot and pak files" option with cell-based netlisting.
    3. The method you said about unloading the incisive module makes absolutely no sense to me. Some level of compilation is required to allow it to see hierarchy underneath textual views.
    4. The vmsNcvlogExecutable is related to when you are "checking and saving" the textual view - nothing to do with netlisting. So messing with that makes no sense either.

    One thing to be aware of is that it may still call ncvlog during netlisting - sometimes this may take little time as it's incremental though.

    However, you really should explore moving to using the Unified Netlister (UNL) technology instead.

    Regards,

    Andrew.

Reply
  • Andrew Beckett

    First of all, cell-based is obsolete nowadays - you really should move to using UNL (especially with recent versions, as you're presumably using if using ICADV - you didn't say which number though). However, regardless of that...

    1. Unchecking the "incremental" options will just cause it to compile all, I think. So you should check the incremental options.
    2. There normally isn't a "clean snapshot and pak files" option with cell-based netlisting.
    3. The method you said about unloading the incisive module makes absolutely no sense to me. Some level of compilation is required to allow it to see hierarchy underneath textual views.
    4. The vmsNcvlogExecutable is related to when you are "checking and saving" the textual view - nothing to do with netlisting. So messing with that makes no sense either.

    One thing to be aware of is that it may still call ncvlog during netlisting - sometimes this may take little time as it's incremental though.

    However, you really should explore moving to using the Unified Netlister (UNL) technology instead.

    Regards,

    Andrew.

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.