• 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. Mixed-Signal Design
  3. error during IE generation(mixed signal simulation)

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 64
  • Views 2921
  • 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

error during IE generation(mixed signal simulation)

RAMYA1
RAMYA1 over 12 years ago
I have created a project in virtuoso in which i had schematics and verilog codes. All these analog schematics and digital blocks are instantiated in anoyher schematic in the same project. I choose mixed signal simulation option (verimix) . Under verimix, i have given partion options, IE library and selected IE cells.(analogLib->MOS),

In ADE, in setup design- i have given the config of topcell. simulator-spectreverilog.

I am getting following error during netlist generation---- error in interface element generation.

Can you suggest me any corrections.

Can you also suggest me how to change the design so that i will avoid the mixed signals.

Please find the log file screenshot in the attachment.

I have also tried to instantiate MOS_d2a and MOS_a2d in my design. Input of MOS_a2d is pure analog but output is a mixed signal. Reason i thought is---- In verimix, under partitioning options i gave spectre under analog partition. so, as the MOS_a2d has the view spectre, it is considered as analog block so the output is a mixed signal instead of digital.

I also tried not giving spectre in analog partition, but iam getting error.

Please can you suggest me any solution for instantiating MOS_a2d without making it a part of either analog or digital partition.

Also please help me to solve the error in IE(Interface Element) generarion.

Thanks & Regards,
RAMYA
  • log file screenshot.png
  • View
  • Hide
  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Is there a reason why you're using the really old "verimix" (spectreVerilog) simulator as opposed to "ams" (AMS Designer) which is much newer and supports far more in terms of language support? spectreVerilog is essentially obsolete...

    I'm not sure of the reason for the failure (without doing research that I don't have time to do right now unfortunately) - if you really can't use AMS Designer, I'd suggest you contact customer support.

    Kind Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RAMYA1
    RAMYA1 over 12 years ago

    hai,

              I have changed my simulator to ams. Now iam having  verilogams codes and schematic in my design.Netlist generation is working well. But elaboration is skipped. Can you suggest any idea when this happens. Can you also give me an example stimulus file for simulation to undertand the syntax.

     Thanks&Regards,

    RAMYA

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RAMYA1
    RAMYA1 over 12 years ago

    hai,

        Iam able to get the elabotaion. But during simulation iam getting x/z in digital domain which cannot be converted in analog domain.

    I think this is because i didn't provide any stimulus file. So, please provide me an example stimuls file to know the syntax. If it is due to timing, please suggest me a solution.

     

    Thanks&Regards,

    RAMYA

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Not sure what "stimulus file" you're talking about. It may be a spectre syntax file, or you may want to have some Verilog code, or you may just put sources from analogLib in to drive your circuit. Your mileage may vary.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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