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.
Hi kristenThank you very much for the detail explanation. Editing the extracted view manually would always result in "check and save" errors during netlisting. If the extracted view was created using QRC, we can add a callProc.il skillscript in the QRC tech directory to correct the extracted view. When QRC is generating the extracted view, it will read in callProc.il file and pass the cellview ID of the extracted view the script. The script can then search for the appropriate fet and modify its properties. Unfortunately, your extracted view has been generated using Calibre xRC and hence callProc.il method does not apply. I think it would be better for you to also post your question on Mentor Calibre forum to see if you can get more ideas. If it is ok with you, kindly update this thread with a link to your post on the Mentor forum so that everybody can benefit from your experience. : ) Thanks.Actually I think the Calibre LVS deck should be corrected to fix this problem. : ) The problem lies with the rule deck and not with extracted view generation. So modifying the extracted view is just a workaround.A 3rd possible workaround is as follows:a. Generate a spice netlist using Calibre xRCb. Use a text editor to correct the fet propertiesc. Create a symbol in Virtuoso to represent the netlist and simulate the netlist directlyBest regardsQuek
In reply to Quek:
In reply to kristen:
Hi KristenIt is possible to run into problems only when generating extracted views and not spectre or spice netlists. This is because when generating extracted view, the device parameters in the parasitic netlist has to match that of the device CDF. E.g. LVS deck extracts a parameter named "W=123u" for fetABC and passes it to QRC(or Calibre xRC). QRC will simply use this parameter when creating the extracted view. But if the CDF info of fetABC is actually looking for a parameter named "width", it will not accept "W" from QRC and will use default value of "width" from CDF. This situation is possible because some pdks do additional mapping from "width" to "w" in CDF. (CDF : Component Description Format)Hence a wrong extracted view will be generated. But if we were to simply use a spice/spectre netlist with "W" and not "width", it would simulate well because "W" is what the model file needs.In the spectre parasitic netlist which you had obtained using Calibre xRC, does it has "simulator lang=spectre" as the 1st line? Is the file named with extension ".sp" instead of ".scs"? It should be named as ".scs".Best regardsQuek
Hi KristenYou should use the symbol view. Would you please check the following?a. Has the spectre netlist been added as one of the model files in ADE-L?b. Please execute the following in ciw and check the return value:getShellEnvVar("CDS_Netlisting_Mode")c. Please upload a snapshot of "spectre" siminfo cdf sectionThanksQuek
Hi KristenWould you please check the following?a. In ADE-L netlist, does the line for the cell look similar to the following?I5 (net1 net2 net3 net4) 100GHz_half_backupIf not, how does it look like?b. Please go to "Setup->Environment". What are the values for "Switch View List" and "Stop View list"?c. Would you please execute the following cmd in ciw and paste the output?ddGetObj("Osc_layouts" "100GHz_half_backup")~>views~>nameThanksQuek
Hi KristenYour setup looks good and it looks like the cell has been netlisted correctly. It is really strange. By the way, may I know the version of spectre which you are using?terminal>spectre -WThanksQuek
Hi KristenSorry that I am not sure where the problem is. I think it should be just a setup problem because this really cannot be too difficult but it would take a good examination of the actual setup to determine the cause of the problem. I would suggest filing a service request with your nearest Cadence support centre and let an engineer assist you on this. : )Best regardsQuek
Hi KristenThis is most likely due to missing termOrder info in CDF. Would you please check if CDF simInfo for "test" cell is as shown below?Best regardsQuek