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 work with the technology of IBM CMOS7RF on Cadence 5.1 (IC5141). Currently I am trying to extract parameters for a self-customized inductor. By setting "ind" model in schemetic as a blackbox and ignoring mismatches, I go through LVS. Now an error happens in QRC as below.
*WARNING* at "capgen": x-tile size is not floating point number
*ERROR* at "capgen": capgen job quit due to process file errors.
-blocking coupled5_shield1:0.02,M1,M2,M3,M4,M5 -blocking coupled5_shield2:0.02,M2,M3,M4,M5 -blocking coupled5_shield3:0.02,M3,M4,M5 -blocking coupled5_shield4:0.02,M4,M5 -blocking coupled4_shield1:0.02,M1,M2,M3,M4 -blocking coupled4_shield2:0.02,M2,M3,M4 -blocking coupled4_shield3:0.02,M3,M4 -blocking coupled3_shield1:0.02,M1,M2,M3 -blocking coupled3_shield2:0.02,M2,M3 -blocking coupled2_shield1:0.02,M1,M2 -blocking singleEndA_shieldT:0.02,MT,ML -blocking singleEndA_shield5:0.02,M5,MT,ML -blocking singleEndA_shield4:0.02,M4,M5,MT,ML -blocking singleEndA_shield3:0.02,M3,M4,M5,MT,ML -blocking singleEndA_shield2:0.02,M2,M3,M4,M5,MT,ML -blocking singleEndA_shield1:0.02,M1,M2,M3,M4,M5,MT,ML -res_blocking singleEndA_shieldT:0.02,ml -res_blocking singleEndA_shield5:0.02,ml -res_blocking singleEndA_shield4:0.02,ml -res_blocking singleEndA_shield3:0.02,ml -res_blocking singleEndA_shield2:0.02,ml -res_blocking singleEndA_shield1:0.02,ml -blocking singleEndT_shield1:0.02,M1,M2,M3,M4,M5,MT -blocking singleEndT_shield2:0.02,M2,M3,M4,M5,MT -blocking singleEndT_shield3:0.02,M3,M4,M5,MT -blocking singleEndT_shield4:0.02,M4,M5,MT -blocking singleEndT_shield5:0.02,M5,MT -blocking singleEnd5_shield1:0.02,M1,M2,M3,M4,M5 -blocking singleEnd5_shield2:0.02,M2,M3,M4,M5 -blocking singleEnd5_shield3:0.02,M3,M4,M5 -blocking singleEnd5_shield4:0.02,M4,M5 -blocking singleEnd4_shield1:0.02,M1,M2,M3,M4 -blocking singleEnd4_shield2:0.02,M2,M3,M4 -blocking singleEnd4_shield3:0.02,M3,M4 -blocking singleEnd3_shield1:0.02,M1,M2,M3 -blocking singleEnd3_shield2:0.02,M2,M3 -blocking singleEnd2_shield1:0.02,M1,M2 -blocking ml_transmission,sti,ML -blocking symind3_mlml_m1,sti,M1,MT,ML -blocking symind2_mlml_m1,sti,M1,MT,ML -blocking ind2_mtml_m1,sti,M1,MT,ML -res_blocking symind3_mlml_m1,mt_resistive,ml -res_blocking symind2_mlml_m1,mt_resistive,ml -res_blocking ind2_mtml_m1,mt_resistive,ml -blocking symind3_mlml_bb,sti,MT,ML -blocking symind2_mlml_bb,sti,MT,ML -blocking ind2_mtml_bb,sti,MT,ML -res_blocking symind3_mlml_bb,mt_resistive,ml -res_blocking symind2_mlml_bb,mt_resistive,ml -res_blocking ind2_mtml_bb,mt_resistive,ml -blocking bondPad_PC:5.28,sti,PC,ML -res_blocking bondPad_PC:5.28,ml -blocking bondPad_BB:5.28,sti,ML -res_blocking bondPad_BB,ml /home/zheng072/zy_senser/inductor_test1
*WARNING* Bad return status from RCX script generator. 0x100
I cannot figure out what's wrong with "process file". I have installed Assura QRC package exactly as the document states. Any advices are appreciated.
Hi bjbitWould you please provide the specific version of QRC which you are using? This might be an old bug which has already been fixed.Best regardsQuek
In reply to Quek:
Thanks for the quick response. Here is what I found from the document.
PDK version: V126.96.36.199
Assura version: 4.1USR2_HF3
QRC version: 10.1.2-s078
In reply to bjbit:
Hi bjbitThanks for the info. I meant the actual QRC version which you are using. You can check it in a terminal window using:terminal>qrc -versionBest regardsQuek
Sorry I cannot find this "qrc" command in any directory from linux console. There is no "bin" folder in the installed PDK. I am confused. Could you please help out? Thanks.
Hi bjbit"qrc" is the executable file for running the extraction. If it is not present in your path, it most probably means that you are not using QRC. You might have used the old Assura RCX for the extraction. Please request your IT to download and install PVE package and it should resolve the problem. Please note that Assura and QRC comes in separate packages. Assura comes from "Assura" package. QRC comes from "PVE" package. Best regardsQuek
Thanks a lot for the info. It seems you are right, since I used "run RCX" under "Assura" manu in Cadence virtuoso. By checking the assura installed in the server, I found the version is 4.1_USR1_HF11, while the version tested in document is 4.1_USR2_HF3. Is RCX default integrated with assura, and QRC is seperated tool? Does the assura version matter for installing and using QRC? So I need to install QRC tool for the availability of the QRC package in my PDK, right?
Hi bjbitYes, RCX is integrated with Assura. QRC is a separate tool. You will need to use the latest version of Assura (41USR2_HF12) together with QRC. Please install PVE and add the following to your .cshrc file:setenv QRC_HOME /your-path/PVE11set qrcPath=($QRC_HOME/bin $path)Yes, you need to install QRC for your PDK.
I appreciate all of your helps. Thanks a ton.
Hi bjbitYou are welcomeBest regardsQuek
Finally I asked my server manager to get PVE11 package installed. Now my working environment is Assura41 _USR2_HF10 under IC614. Here is a question regarding to setup QRC. When I type "qrc -version" to check version (actually also other commands), no any information poped, even command errors. When I open a layout view and click the QRC menu, "Loading QRC menu..." is shown under it, and a warning of "RCX UI is already loaded" is given in CIW. I guess it maybe a conflict issue between QRC and the integrated old RCX? Any advices to solve it? Thanks in advance.
Hi bjbitMy guess is that you are using redhat enterprise 4.x. You will need redhat enterprise 5.5 and above in order to use PVE package. : ) If it is not possible to find a machine with RHEL5.5 and above, you can also also use the slightly older EXT10.1.2 package. It should also resolve your problem. The history of QRC is as follows:a. Named as "rcx" and comes from Assura packageb. Combined with cell level extractor and renamed as "QRC". Comes from EXT package.c. Packaged together with PVS in PVE package.Best regardsQuek
Thanks for the advices. I will ask the manager to have a check.
bjbit QRC menu, "Loading QRC menu..." is shown under it, and a warning of "RCX UI is already loaded" is given in CIW
Sorry for my English.
I have the same problem. I Upgrade EXT91 to EXT101 and now The QRC menu only give me "Loading QRC menu..." and I ha ve the same warning about RCX UI.
Does anyone has an idea?
Thanks in advance
In reply to Jonjohn:
As Quek advised, I have fixed this problem on PVE11 by using the newer version of Linux system. I am not sure about the compatibility of EXT10, but did EXT9 work for you? If so, probably you are having the same Linux issue. I guess you may try on another machine with newer version OS, and see what's going on. Anyway, I believe Quek can provide further advices.
I'm working on Fedora 15. With EXT9, it works. But not with EXT10. The two install have the same configuration...
I don't know why.