Home
  • Products
  • Solutions
  • Support
  • Company

This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  • Products
  • Solutions
  • Support
  • Company
Community Mixed-Signal Design Virtuoso AMS error

Stats

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

Virtuoso AMS error

Emily157
Emily157 over 1 year ago

Hi All,

I failed to create cellview but my parser log file is empty. 

I am sure that my coding is correct. Because the same coding description with half coding lines can successfully create the cellview.

My coding line is up to 10860, I wonder if that is the reason.

I also got a warning : (SCH-1059): Failed to generate pin list from cellview "xxx". Check there are no syntax errors and try again.

Can you please help me out with this? Thank you.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 1 year ago

    Can you share the Verilog-AMS code?

    Also, the XCELIUM and IC versions that you are using.

    Andrew 

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • Emily157
    Emily157 over 1 year ago in reply to Andrew Beckett

    Here is my Verilog-AMS code.
    sttmram0_32_16.txt

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Emily157
    Emily157 over 1 year ago in reply to Andrew Beckett

    Here is my Verilog-AMS code.
    sttmram0_32_16.txt

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 1 year ago in reply to Emily157

    You'll need to contact customer support. It appears that the code compiles OK, but the option used to extract some of the structure information (the xmvlog -zparse option) is failing with an internal error. That needs investigating by R&D. Please log into the support site and then submit a case together with the model code you provided here.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Emily157
    Emily157 over 1 year ago in reply to Andrew Beckett

    OK, thanks.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago in reply to Emily157

    Emily,

    As a stop-gap, you can comment out (with /* and */ ) the contents of the module - leave all the I/O definitions. You also need to comment out (with //) the two parameter real array lines (Rap and Rp); these are the two that seem to be causing the problem with the analysis. Save and Extract, and then remove the comments. At least this way you'll end up with the netlist.oa (and will be prompted for symbol creation), and then having removed the comments it would fail to extract, but you'd still have the previous extraction.

    I had initially thought of suggesting you replacing the core of the module with loops with genvars to create the structure, but I think the real issue is the big parameter array.

    For support (your point about support access seems to have been deleted from the thread), if you're an academic institution then you would either go via Europractice support (if in the Europractice scheme) or elsewhere you can get your University liaison (whoever is responsible for the University program at your institution) to create the support case - it's just not open to everyone so that there is some level of filtering within each institution.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Emily157
    Emily157 over 1 year ago in reply to Andrew Beckett

    Copy that, I'll give it another shot with a different approach, thank you very much!

    Best Regards,

    Emily

    • 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