Stats

Locked Locked
Replies 6
Subscribers 65
Views 3252
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

can't import uvm_ml for using sv test with e component

zeevg over 2 years ago

In my test I have : import uvm_ml::*;

after compilation with : xrun -V93 +UVM_TESTNAME=test_cosim -ml_uvm ...

I got an error:

xmvlog: *E,NOPBIND (...) package uvm_ml could not be bound

I run with xrun(64) 21.03-s001

How can I enable runing in multilanguage?

StephenH over 2 years ago

Hello Zeev.

According to the docs here, you should be importing ml_uvm::*, not uvm_ml::*.
Cancel
Vote Up 0 Vote Down

Cancel
zeevg over 2 years ago in reply to StephenH

Thanks stephen,

I imported ml_uvm and it worked.

Now I got an error on "uvm_ml_create_component" :
Cancel
Vote Up 0 Vote Down

Cancel
zeevg over 2 years ago in reply to zeevg

I tried it with ml_uvm:: and without it as mentioned in support.cadence.com/.../techpubDocViewerPage
Cancel
Vote Up 0 Vote Down

Cancel
StephenH over 2 years ago in reply to zeevg

Ah, so you're trying to use the newer "OA" library! There are two, a legacy "ml_uvm" package and a newer Open Architecture one, confusingly named uvm_ml. In this case, revert the package name to what you had originally: uvm_ml.

Did you use the other required option from that page, i.e. "-uvmhome CDNS-1.2-ML" so that it picks up the ML-enabled UVM library?
Cancel
Vote Up 0 Vote Down

Cancel
zeevg over 2 years ago in reply to StephenH

do I have to use in xrun command the "-ml_uvm" in addition to "-uvmhome CDNS-1.2-ML"? I used them both and got an error
Cancel
Vote Up 0 Vote Down

Cancel
StephenH over 2 years ago in reply to zeevg

To be honest, I'm a bit rusty on this, but it looks like -ml_uvm is the legacy flow and if you're using the OA version then it's the -uvmhome plus -uvmtop to specify which language sits at the top of the testbench hierarchy. So don't use -ml_uvm.
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.