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 have generated a inductor Ind1 with a Passive Component Designer
(PCD) tool. The inductor is used in LC VCO schematic.After LVS run I
get the following errors and discrepances:1)Error:
Ind1(Generic) on Schematic is unbound to any layout device2)in
LVS report I get that pins of the inductor are not found in layout,
although seen in schematic by the tool.
I tried to solve problems by:
- adding a line in bind.rul file : 'C Ind1(Generic) Ind1'
what eliminated the error 1), but in the LVS debug tool pin
discrepances are found between VCO schematic and layout and
Ind1(generated by PCD) schematic and layout.
- used a avCompareRule command indDevice to turn Generic device
into inductor IND - still pin mismatch LVS error.
Any ideas how to solve the problem? Thanks in advance!
Hi pitterWould you please upload the following files which can be located in the lvs run directory?a. design.erc fileb. design.cls file
To upload a file, please go to "Options" tab and use the "file attachment" function.ThanksQuek
In reply to Quek:
here are the files you asked. They have been generated without adding a line in bind.rul file and using indDevice command.
In reply to pitter:
Hi pitterFrom erc file, we can see the following:
info: Assign pin label "Pout" at (388.050, -938.250) to layer `net_met2'. info: Assign pin label "vdd!" at (1270.800, -927.400) to layer `net_met1'. info: Assign pin label "gnd!" at (304.800, -927.050) to layer `net_met1'. info: Assign pin label "Mout" at (384.300, -931.250) to layer `net_met1'. WARN: Multiple label discarded: "Mout" at (384.300, -931.250) and "Pout" on net C3. info: Assign pin label "RestartTrigger" at (1265.650, -940.500) to layer `net_met1'.
It looks like labels "Mout" and "Pout" might have been mistakenly placed on the same net. Would you please try to correct this? Because both labels are on the same net, Assura discards them and hence results in missing Mout and Pout layout pins.Best regardsQuek
There is a section in the VPCM User Guide called "Virtuoso PCD black-box Recognition and ExtractionUsing Assura" which explains how to modify your existing LVS rules to recoginze PCD inductors.
You are right Quek.
But the error is caused by the architecture of the differential VCO. Namely the differential output is labeled with pins, that in turn is connected to the spiral. The spiral (there is actually a couple of spirals) is treated by Assura as a typical connection, a short. I will get familiar with the suggested section of the VPCD User Guide. I've just only had a brief look on it, it looks like it addresses the issue, but might be challenging. Modifying PDK scripts - I have never done it, but I will give it a try.
Thanks both of you,
Take care, pitter.
As for the problem 1) (described in the very first post of this thread), there is a avParameter ?blackBoxCell in the LVS run dialog box. By its means, I can specify the balck box cell (custom inductor Ind1). It solves the problem 1). But I still get errors concerning the unnbound pins between schematic and layout of the inductor.
Hi pitterWould you please post the contents of the erc file?
Hi Pitter, Quek
Have you figured out about the pin errors? I ran into the same problem...