• 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. Functional Verification
  3. xmelab: *E,CUVDNF (./netlist.vams,1748|8): Could not determine...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 5332
  • 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

xmelab: *E,CUVDNF (./netlist.vams,1748|8): Could not determine discipline for this expression

Abhishek Verma
Abhishek Verma over 6 years ago

Hey experts,

We are facing an error while running xrun for simulation of netlist:

<SomeModule> <SomeModuleInstance> ( .() ..........

xmelab: *E,CUVDNF (./netlist.vams,1748|8): Could not determine discipline for this expression 

I wanted to know what is the meaning of this violation and what might be a tentative fix. I have already made sure that this module is present in filelist.f.

Thanks,

Abhishek

  • Cancel
Parents
  • Abhishek Verma
    Abhishek Verma over 6 years ago

    What more information do you required StephenH. I have only removed hierarchy information. Other than that is the only information I am getting from xrun. Do you might know what is the intention of this violation?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Abhishek Verma
    Abhishek Verma over 6 years ago

    What more information do you required StephenH. I have only removed hierarchy information. Other than that is the only information I am getting from xrun. Do you might know what is the intention of this violation?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • TAM1
    TAM1 over 6 years ago in reply to Abhishek Verma

    I've seen that message when I was connecting an analog signal to a digital port. In a mixed signal simulation, there are auxiliary files that I needed to add that described a "discipline" that indicated how analog values were to be interpreted as digital ones and vice versa.  As Stephen said, we don't know enough about what you are modeling to say what you might be needing.

    • 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