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 currently using Cadence version IC18.104.22.1680.8. I am a regular user of Virtuoso Schematic Editor. However I don't have any experience related to automation in Schematic editor.
I am currently designing an IC that has around 15 - 20 IO Pads. Between each of these Pad's and internal logic (input or output) port, series of buffers (50-200) needs to be placed. I have the information related to the number of buffers corresponding to each Pad in an excels sheet. Doing this work manually is very boring and also tiring?
Would you kindly advice if its possible to automate the placement of buffers in the schematic between two signals based on the information provided via text file or .xls file.
Thanks and Best Regards,
Yes, this can be done. You need to first write some Skill code to read the text file using code like the following:
;Assume the txt file is a csv (comma separated values) dumped from an Excel spreadsheet looking like this:;portName,numBuffers
txtFileName="/tmp/my.csv"/*The text file for this example looks like this:port1,10port2,5port3,6*/procedure(myReadCsv(txtFileName) let((portTable filePtr lineData line) portTable = makeTable("portTable" nil) filePtr = infile(txtFileName) while(gets(line filePtr) lineData = parseString(line ",") portTable[car(lineData)] = evalstring(cadr(lineData)) ) close(filePtr) portTable ) ;let) ;proc
procedure(myBuildBufferSchematic(txtFileName) let((portTable cv x y dx inPinId outPinId buffId wireId bufInst bufWidth ) cv = geGetEditCellView() portTable = myReadCsv(txtFileName) x = y = 0 dx = 5.0 inPinId = dbOpenCellViewByType("basic" "ipin" "symbol") outPinId = dbOpenCellViewByType("basic" "opin" "symbol") buffId = dbOpenCellViewByType("myLib" "myBuf" "symbol") foreach(port portTable schCreatePin(cv inPinId port "input" nil x:y "R0") for(i 1 portTable[port] wireId=schCreateWire(cv "draw" "full" list(x:y x+dx:y) 0.05 0.05 0.0) bufInst = dbCreateInst(cv buffId nil x+dx:y "R0") bufWidth = abs(rightEdge(bufInst~>bBox) - leftEdge(bufInst~>bBox)) ;Subtract 0.05 so the wire overlaps the instance pin (adjust as needed for your buffer) x = x + dx + bufWidth - 0.05 ) wireId=schCreateWire(cv "draw" "full" list(x:y x+dx:y) 0.05 0.05 0.0) schCreatePin(cv outPinId strcat(port "_out") "output" nil x+dx:y "R0") y=y+1 x=0 ) printf("Finished\n") ) ;let) ;proc
;lbl = schCreateWireLabel(cv car(wireId) x:y+0.05 labelName "lowerCenter" "R0" "stick" 0.05 nil)
Your needs will certainly vary from what I've provided, but here are some things to note:
I didn't name the wires between the buffers, but if you need to you can use the schCreateWireLabel command shown above.
Generally this is possible.- Output a csv file form Excel.- Read it in with SKILL file IO commands.- Post processes in SKILL- Do a schematic placement with db* commands e.g. dbCreateInst
In reply to dmay:
Thanks Derek for your detailed reply and also the sample script. That's very helpful.
I followed all the steps that you have mentioned above.
1. So first I created a sample csv file (myfile.csv) with following data:
In CIW I entered
The copied your SKILL script to a .il file (build_buffer.il) and added the buffer library and cell name.
Then in CIW I did
However I am getting an error:
*Error* evalstring: argument #1 should be a string (type template = "ts") - nil
Is it something to do with "portTable[car(lineData)] = evalstring(cadr(lineData)) ", since the buffer numbers in the txt file are not strings??
In reply to shamore:
I'm guessing there is probably a blank line in the text file. The evalstring is going to convert the string to a number when it stores it in the table. Make sure there are no trailing blank lines in the file.
You could error check for that this way: while(gets(line filePtr) lineData = parseString(line ",") when(length(lineData)==2 portTable[car(lineData)] = evalstring(cadr(lineData)) ) )
Also, if you are going to write Skill, the following commands will give you even more detail when your Skill fails:sstatus( stacktraceDump t )sstatus( stacktrace 8 )sstatus(traceArgs t)
Thanks again Derek. You were right, there were trailing blank lines in my text file.
Now the script runs perfectly.
Also thanks for the tips related to debugging.
That was indeed very helpful !
In reply to berndf:
Thanks Bernd for the inputs !
Thanks Derek for this information. Actually I am also trying to do same thing. But to add on this, this is possible to read any text file and fetch information to build any schematic.
Please let me know is this also possible to fetch the information from schematic using skill and load in some text file? Information is like no. of wires, no. of components, no. of pins in schematic etc.
or instead of storing any information in text file, can we also store in some model like UML diagram?
In reply to Skill User:
Really? Your question seems to be to do the opposite - to extract some (vaguely described) information from the schematic and write it to a text file, not the other way around.
Also, the forum guidelines ask you not to append to old threads, especially if asking different or only loosely related questions. You can always reference an old thread in a new one if you want to point people to threads that you think might be relevant.
In reply to Andrew Beckett:
Perhaps dbWriteSkill will do what he wants.
dbWriteSkill( d_cellViewId t_fileName t_mode t_release [ g_conn ] db[ g_ref ] [ g_lppString ] ) => t / nil
Creates a file that contains all the SKILL commands needed to recreate a cellview, so that the design can be recreated in the current or previous release by loading the file in the current or previous release, respectively.
Open a cellview and run this:dbWriteSkill(geGetEditCellView() "/tmp/mycell.il" "w" "6.1")
This will write out a skill file of all the contents of the cellview. The Skill file could be used to recreate the cellview if that is what is desired.