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.
Hello,I am trying to use the cdlIn function to import an existing cdl netlist and create a schematic. While I was successful in getting a simple inverter to generate, when I try to import a 3 input and gate, the tool creates a multipage schematic. It seems as if the tool cannot handle more than 2 fets per sheet. The and gate is composed of simple primitives (8 fets).Also, the cdlIn was not straightforward. Even though I have my libraries attached to an existing techlib, cdlIn would not recognize the primitives within the PDK library. I had to copy all my nfet and pfet symbols to my working directory and call them pmos and nmos, otherwise the tool created a generic symbol called mos with an empty schematic and created an empty top level schematic with ports, but no fets.I am using version 5.1.41 on a Linux box.Thanks,Chris
Chris,I am finding it a bit strange that:1. It is creating multisheet, it should not.2. Naming them pmos and nmos, not required unless you are using a device map file.Try cdlin again after deleting mos cell in your import lib.1. In the "reference library list" field specify the lib name which has nfet and pfet.2. Don't specify device map file unless you are doing some property matching stuff.Import again.Thanks,RR
Hi RR,If I just specify the reference library (analogLib for instance) and have no device map file, the schematic ends up empty, with no components and just ports. Are you saying run the cdlIn once with the primitives not skipped, so that it creates that "mos" device in my working library, then delete it, skip primitives and try cdlIn again? If I don't have the "skip primitive" box checked, I don't get a top level schematic.BTW, the analogLib that I'm using has no pfet or nfet. It has pmos, pmos4, nmos and nmos4, so I think I have to have a device map. It can't seem to find the fets otherwise.Thanks,Chris
Hi,I just tried to run cdlIn again without specifying a device map file. Using a schematic called "and3", here are the steps I took:1) Created an "and3" schematic using pmos4 and nmos4 fets from analogLib. It has 3 input ports (A, B and C), one output port (Y), a bidirectional power port (VDD) and a bidirectional ground port (VSS). I tied all the backgates to their respective power and ground rails so that all 4 ports for the primitives were used.2) Ran Export->CDL3) Ran Import->CDL, using a new input library so I didn't clobber my old schematic. I did not use a device map file. I did use analogLib as my reference library, since that is what I pulled the fets from originally.One of the log files (ni.log or nino.log...I can't remember which one) notes that the tool could not find the fets in any library and finally says "Bingo! mos->symbol found". They are listed as PM and NM in the cdl netlist, exactly as cdl out wrote it. There is no top level "and3" schematic generated. Only a "mos" symbol was generated in my working input library and it is a stub (4 ports). It does not matter if I change the names of the fets in the CDL netlist to pmos4/nmos4 or pfet/nfet. The results are the same. If I delete the "mos" cell, it regenerates. If I enable "skip primitives", I get an empty schematic with just ports.I also tried using OA with its SpiceIn feature. Unfortunately, we don't have the license for that, so I'm stuck with 5.1.41.Chris
This one should work with device map file as below:devMap := nfet nmos4propMatch := subtype n3devMap := pfet pch_33propMatch := subtype p3Note that n3 and p3 are the models in the propMatch line. By model I mean following in a netlist:M_0 VDDESD NET_0 VSSESD VSSESD p3 W=33U L=0.13UFor pmos devices model in netlist should have p* and for nmos device it has to be n* in the netlist. If this is not the case, you would need to modify the netlist you are importing.In the reflib you must specify analogLib.Make sure the import lib is empty. mos is not needed at all. mos gets created only if correct mapping is not found in reflib and that is an indication that things went wrong. RR
Hi,This is what I had in my device map file when I got the multi-page schematics:devMap := nfet nmos4propMatch := subtype NMdevMap := pfet pmos4propMatch := subtype PMThe NM and PM are in the CDL netlist like such:.subckt and3 A B C VDD VSS Y*.PININFO A:In B:In C:In Y:Out VDD:B VSS:BMP0 vdd A Y vdd PM w=2u l=0.18uMP1 vdd B Y vdd PM w=2u l=0.18u
MP2 vdd C Y vdd PM w=2u l=0.18u
MN0 net1 A Y vss NM w=1u l=0.18uMN1 net2 B net1 vss NM w=1u l=0.18uMN2 vss C net2 vss NM w=1u l=0.18u.endsI got a warning saying the propMatch items were more than 2 characters long. My library was empty when I started. I also called out my reference library to be analogLib.I got an empty schematic when I DIDN'T use the device map file.When I look in the Cadence docs, it appears that I'm doing things correctly...it just doesn't turn out that way. I can't find anything in SourceLink that helps. Chris
Oops...forgot to type in the final inverter for the and3...what I typed is a nand3 of course :-).Chris
On the "Schematic Generation" form check the value of "Maximum number of rows" and "Maximum number of Columns". Keep the values high in this field. Make it 1024. If it still creates, let me know:What is the behavior of tool if you create a new schematic using menus? Does it creates multisheet? Or, it is happening only in case of cdl import? Which version is this (icfb -W)?
The settings you describe are the default. I also set the density to maximum (100). I still get multipage schematics. I have never had problems creating schematics from scratch. It is only a cdl in problem. I have no problem with cdl out, no problems with simulation, no problems with layout, no problems with stream in, no problems with stream out.Chris
I would suggest that you file a Service Request with Cadence and get it resolved with help of some AE. The AE might want to look at your display to see whats going on. Because, I have tried your exact netlist and I don't see any multisheet being created. I have used iC5141USR5 and latest ISR of IC5141 without any issues.RR
Oh and I forgot...it's IC5141/USR3
That's what a Cadence rep told me today. I just submitted an SR. Thanks for all your help.Chris
USR3 gives me same result.
Just for the record, in case anyone is following this thread, the problem was with me using USR3. I was able to get cdlIn using IC5141/USR5. Yes you need a device map file. Chris