• 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. AMS simulation error after moving to xrun/xcelium

Stats

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

AMS simulation error after moving to xrun/xcelium

forXTer
forXTer over 6 years ago

I recently migrated a project to IC6.1.7 which I understand uses xrun/xcelium instead of irun/incesive. I am getting an elaboration error in an AMS simulation that works fine in IC6.1.6. 

I am trying to including a systemverilog package, but I get the following error:

xmvlog: *E,EXPMPA (/home/package.sv,1|6): expecting the keyword 'module', 'macromodule' or 'primitive'[A.1].

It seems like it is trying to interpret this as verilog even though I have other .sv files that are fine. Nothing is defined in hdl.var that overwrites the default file associations. 

Current tool versions:

IC6.1.7-64b.500.23

xrun(64): 18.09-s009

  • Cancel
  • RiadKaced
    RiadKaced over 6 years ago

    Weird, if it worked before then sounds like a bug to me but that needs further investigation ...

    can you add the "-checkargs" to your xrun command line or into your xrunArgs file, this will dump a list of the command line arguments, just making sure you don't have a redifinition of the extention based resolution ...etc.  If you could post more useful information then it would greatly help.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to RiadKaced

    Actually whether IC617 uses XCELIUM or INCISIVE depends on what you have in your path.

    Understanding the error is going to be rather hard without knowing what the line in the code is which triggers the error, how you're referencing package.sv and so on. I suggest you contact customer support so that we can look at your setup... this is unlikely to be just because you're changing versions, but more to do with how your local environment has been configured, and you've not given enough information here to to be able to diagnose it.

    Kind Regards,

    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