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 a generate statement to instantiate a delay module (cur_starved_delay) 11 times. The basic idea is to model a 11 stage ring oscillator using current starved delay cell. But i get syntax error in generate statement. Can anyone help me with this. The code is attached below.
module multiphase_vco(Vbias_p,Vbias_n,Vdd,Vss, out);parameter integer NO_STAGE = 11;parameter real C_load = 1e-12;parameter real Kp = 1;parameter real Kn = 1;parameter real Vt = 0.2;parameter real pos_tol = 0.2;parameter real neg_tol = -0.2;
genvar i;input Vbias_p,Vbias_n,Vdd,Vss;output [11-1:0] out;voltage Vbias_p,Vbias_n,Vdd,Vss;electrical [NO_STAGE-1:0] out;real ph_out[NO_STAGE-1:0];generate for (i =1;i<=11;i=i+1) begin cur_starved_delay #(.C_load(C_load),.Kp(Kp),.Kn(Kn),.Vt(Vt),.pos_tol(pos_tol),.neg_tol(neg_tol)) D_i(.Vin(ph_out[i-1]),.Vbias_p(Vbias_p),.Vbias_n(Vbias_n),.Vdd(Vdd),.Vss(Vss),.Vout(ph_out[i])); endendgenerateph_out = ph_out[NO_STAGE]);@(initial_step) begin ph_out = V(Vss);endend endmodule
Please ignore the extra end statement after initial_step block
In reply to write2rammy:
In fact it's not just the end statement that's wrong. The whole:
ph_out = ph_out[NO_STAGE]);@(initial_step) begin ph_out = V(Vss);endend
is wrong. The first line has got an extra close parenthesis. It probably needs to be inside an @(initial_step) block, or similar, in which case it's superflous. Also, these need to be inside an analog block.
Next is that the D_i instance appears to be connecting to a real array, rather than a voltage array.
Finally is the main issue, that assuming that cur_starved_delay is an analog module (you didn't give the details), this is not supported in AMS. If I omitted the lines above, it compiles OK with no errors, but during elaboration I get:
D_i(.Vin(ph_out[i-1]),.Vbias_p(Vbias_p),.Vbias_n(Vbias_n),.Vdd(Vdd),.Vss(Vss),.Vout(ph_out[i])); |ncelab: *E,VHANAG (./gencode.v,38|19): Module "cur_starved_delay" has analog element(s) in it. Instance multiphase_vco.genblk1.D_i of this module is not yet supported inside generate statement.voltage Vin,Vbias_p,Vbias_n,Vdd,Vss,Vout; |ncelab: *E,VGDADS (./gencode.v,6|10): multiphase_vco.genblk1.D_i.Vin has got declared analog discipline "voltage". Use of analog element inside Generate statement is not yet supported.voltage Vin,Vbias_p,Vbias_n,Vdd,Vss,Vout; |and many such errors. If I expand these errors with nchelp I get:
UNIX18> nchelp ncelab VHANAGnchelp: 09.20-s020: (c) Copyright 1995-2010 Cadence Design Systems, Inc.ncelab/VHANAG = The module/architecture pointed out by this error message has analog element(s) inside it. Instantiation of this analog unit inside a Verilog or VHDL generate statement is not yet supported.UNIX19> nchelp ncelab VGDADSnchelp: 09.20-s020: (c) Copyright 1995-2010 Cadence Design Systems, Inc.ncelab/VGDADS = The net pointed out by this error message is declared as analog. Use of this analog net inside a Verilog or VHDL generate statement is not yet supported.
You will need to contact customer support and request an enhancement to support analog elements inside a generate statement. There is already a request for this, CCR 700708, but it's best if each customer requests it who needs it, then there's a fair reflection of the amount of demand, which helps in prioritization.