Missing connectLib

I would suggest you add:

INCLUDE $(inst_root_with:tools/bin/irun)/tools/inca/files/cds.lib

to your cds.lib

This will give you VHDL libraries and connectLib too.

Andrew.

Thanks for this advice.

We seem to have only encountered the need for this to be added once we switched from using Incisiv to using Xcelium for digital simulations.

Was there a mechanism by which Incisiv defaulted this automatically, which Xcelium doesn't use? Or did Incisiv not demand connectLib?

Typically you might have this in your cds.lib:

SOFTINCLUDE $AMSHOME/tools/inca/files/cds.lib

or:

SOFTINCLUDE $(inst_root_with:tools/bin/xrun)/tools/inca/files/cds.lib

If you've used the first style, with an env var, make sure that whatever env var you're using points to the new installation. If using the second style, make sure that it's using a valid executable name (you might have used irun in the past; moving to run makes sense).

Andrew

Thanks for the further illumination!

The latter form is fine for our purposes if it doesn't have any adverse side-effects (like a long execution time, searching for xrun).

We should probably change the command from xrun to irun, because that is an executable supplied by both INCISIV and XCELIUM releases. It allows users to switch back and forth between them and not lose connectLib.

Good to see you again; answering promptly, accurately and concisely as usual!

We were trying to find why when we switch from Incisiv to Xcelium, we suddenly need the new license Xcelium_SC_DMS_Option when simulating under AMS simulator. 
The list of what the token is required for didn't seem to cover things we were doing, unless we are running multi-CPU. That may be the case. The support response suggested we use the options to tell us which licenses we need for our runs, without really telling us whether running in AMS is going to require this new license key. I'm guessing we're going to have to pay for this option.

I see you have already addressed this, and I wasn't looking carefully enough.

You suggested using irun initially, but added the variant with xrun in your later reply. So you can ignore my next reply, unless you know whether the new license key is always needed for ams using Xcelium.

I'd not even noticed that you'd asked this on an old thread and that I'd already given the answer a few years back (when XCELIUM hadn't been released yet) and so that's why I said irun then.

As for the DMS Option license, that's a complicated topic (and it isn't always needed, it depends on features that you use within the design/testbench/models) - and really is best handled through customer support or with your account team.

Regards,

Andrew