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 met a problem in using verilog and vhdl:
1) I use verilog to make a testbench while the DUT all are made by VHDL
2) I want to initialize the lower level memories in DUT. I have tried to use $nc_mirror, but it seems useless.
So would you like to give me some suggestions on how to initial memories in VHDL designs through verilog testbench?
I think we can only do this sort of initializing [vhdl DUT,verilog testbench and vice-versa]by using $nc_force and $nc_release.You can try this.
Please correct me if I am wrong.
In reply to shalem7:
Thanks for your kindly reply. It works by using $nc_force.
BTW, how can I transfer a integer variable from verilog to VHDL?
As the code shows bellow:
tb_top is verilog module;
vhdl_top and bellows are vhdl module.
$nc_force("tb_top.vhdl_top:ocmem:memarry[i]" , #data[i]);
The ERROR message is:
expecting a integer index i.
In reply to victorhan:
I am not sure about the error.I did not inderstand the # in #data[i].
data[i] also needs to be in " ".
nc_force command has to be like this.
If your memarray is of size 5,each single bit
$nc_force("tb_top.vhdl_top:ocmem:memarry" , "10010"); //if it is a single bit.
The important thing is not about how to use #data[i].
It's how transfer a integer i from the top file in verilog to the inner module writen by VHDL.
At test bench top file which was written in verilog:
for (i=0, i < 4096, i=i+1) begin
The array mem_int is beneth vhdl designed module, so my question is how can I transfer
the integer i to VHDL designed module mem_int?
I believe the problem is that you are passing the index into the $nc_force command as a variable rather than a constant. The task is expecting a string with the name of a signal. It isn't going to parse that name and do variable substitution in it. You need to do that yourself.
Try something like this:
integer i; reg [72*8:1] targetname, srcname;initialfor (i=0, i < 4096, i=i+1) begin $swrite(targetname,"tb_top.arcsys:ocram:aram:now:mem_int[%0d]",i); $swrite(srcname,"#data[%0d]",i); // I'm not sure exactly what #data refers to, but we're not talking about that... $nv_force(targetname,srcname,"verbose");end
In reply to TAM1:
Thanks for your kindly reply.
I have tried the method that you told me.
But it's still useless, the variable i still can't be transfered from verilog top file to the deep VHDL.
I put together a small example and this code appears to work:
reg [7:0] data [31:0]; integer i; reg [72:1] destname; reg [7:0] dataval;
for ( i=0; i < 32; i=i+1 ) data[i] = i;
for ( i=0; i < 32; i=i+1 ) begin $swrite(destname,"s1:mem(%0d)",i); dataval = data[i]; $nc_deposit(destname,"#dataval"); end
You may want to use $nc_deposit rather than $nc_force if you want to later be able to write to the memory later from inside the VHDL model.