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.
Long time lurker, first time poster. I first want to thank Andrew, Lawrence and other regulars for contributing to this forum.
I have a simple problem that I can't seem to figure out and I am hoping you guys can point me to the right direction. I am trying to update the "cutSpacing" of a via using the following code, where cutSpacing= x_width:y_width and I got the error below
*Error* dbReplacePropList: Invalid float - (0.09 0.09)
I figured I am not setting the type of "cutSpacing" correctly but I can't figure what it should be.
list("cutSpacing" 'float cutSpacing)
list("cutColumns" 'int numCols)
list("cutRows" 'int numRows)
Thanks in advance,
PS I am using IC6.1.5-64b.500.12
The 'float before cutSpacing should be 'list. That's because cutSpacing is a list of two floats, rather than a single float.
In reply to Andrew Beckett:
thank you for the quick reply, the problem is fixed with 'list.
In reply to chianga:
I have one more question, relating to via cutSpacing, please let me know if I should start a new thread.
The goal of my code is to create a bindkey such that I can grow and shrink via on the fly and adjust viaSpacing accordingly.
Basically since 2x2 and 3x3 vias in the newer technology node have different via spacing requirements, I am using the code below to extract these infomation for the 3x3 vias. Two by two cutSpacing can be easily obtained using via->viaHeader->viaDef->params.
The problem I am running into is that lxGetValidViaDefs is extremely slow and this is especially true when multiple vias are selected. So I am wondering if there is any other way to retrieve the "spacings" information inside the tech files without using lxGetValidViaDefs and lxComputeViaParams?
I guess one way to bypass all these is to only retrieve via spacing info when via is either 2x2 or 3x3(right now my code does this calculation everytime the bindkey is hit) but I am curious to know if there is a more clean way of doing this.
;get via spcaing parameters for 3x3 via
viaId=caar(lxGetValidViaDefs(cellViewId nil layer1 layer2))
viaParams=list(list("cutRows" 3) list("cutColumns" 3))
viaParams=lxComputeViaParams(viaId cellViewId nil viaParams)
If your via spacing is dependent upon the number of vias, that can be encoded as a technology rule in the constraints in the tech file. Isn't that a better solution than having to compute it yourself every time you change the number of rows and columns? That way it will be correct no matter how you enter the rows and columns of the via...
Look for viaSpacing in cdnshelp and you should find it descrbed in the Virtuoso Technology Data ASCII Files Reference manual.
thanks for the reply. I was having problem finding the correct function to retrieve that data from the tech file but with a bit more digging in the forum, I came up with the solution below just in case someone else is interested doing similar things in the future.
viaParams=techGetSpacingRule(tfId "viaSpacing" viaName)
Thanks again for the help and happy holidays,
I am very new to this community. I am trying to implement creating via automatically using skill code. Thanks for all the information that you provided. I was able to place the via wher I want using skill code. However, in terms of the VIA params, I would like to create a via with the same parameters as what "auto" option provided on the "Via form". The auto via will cover all overlap area and extend over a little bit. Also, it won't violate the DRC rule, etc. I tried to use lxComputeViaParams for the viaDef that from tech file, but it didn't give much info. Is there any SKILL function to do that?
tf=techGetTechFile(cv) viaDef=techFindViaDefByName(tf viaDefName) via_center_point_x=(car(viabox_ll)+car(viabox_ur))/2 via_center_point_y=(cadr(viabox_ll)+cadr(viabox_ur))/2 via_center_point=list(via_center_point_x via_center_point_y)
viaParams=list(list("cutRows" evalstring(cutRows)) list("cutColumns" evalstring(cutColumns)) )
;viaParams=append(viaParams lxComputeViaParams(viaId cv viaParams)) existing_via=setof(z dbGetTrueOverlaps(cv list(viabox_ll viabox_ur)) rexMatchp("Via" z~>objType)==t) if(existing_via then printf("There is an existing VIA. No Via will be created.\n") else if(viaDef via0=dbCreateVia(cv viaDef via_center_point "R90" viaParams)