Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
I am using Specman together with an HDL simulator. I am trying to load two compiled eVCs not to be connected by a single e-top. The goal is to let each one of them access the same HDL DUT at the same time.
I don't know how to use SPECMAN_DLIB to do this?
I don't think this is possible. The output from sn_compile.sh is a *.esv and *.so file. These are tightly linked; you can't use one without the other. If you have two eVCs, for example vr_ad and vr_axi, and you compiled them separately, you'd get the following files:vr_ad_top.esv, libsn_vr_ad_top.so, vr_axi_top.esv, libsn_vr_axi_top.so
When you invoke your simulator using SPECMAN_DLIB=libsn_vr_ad_top.so, this also causes the vr_ad_top.esv to be read in, to restore the state of Specman.Now, maybe one of the Specman R&D gurus mightknow better, but I think there's no way to merge or load two *.esv files at the same time, even if you could merge the *.so files.
Having said all of that, I can't see why you would want to do this anyway. Can you explain why you can't (or don't want to) have a single e top file that gets compiled? Normally we define a fake "top" file that imports all the eVCs needed by the testbench, so that we can compile that file without having to compile the testbench. The following blog post has a good description of this approach: http://www.cadence.com/Community/blogs/fv/archive/2009/03/19/import-guidelines-for-e-part-1.aspx
You can also do incremental compilation, whereby the results of the 1st compile are rolled into the 2nd, etc. That can be useful where you want to compile your mature / external eVCs for speed, but still run a loaded testbench for debug. You can compile all the mature eVCs in one step, then do another compile step to compile the whole testbench for regression performance. Because you have the intermediate compile result, you can then still run with the loaded testbench.
Give us some better idea of the problem you are trying to solve, and we'll see if there's a way to do it! :-)