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 trying to alter the
parameter 'numInst' for an iterated instance.i.e.,I am trying re-assign the numInst paramter.But I can see that the value is not getting updated.
The assignment was working fine in 5.1 version but it is not working in OA
instId=dbOpenCellViewByType(<libName> <cellName> "symbol" "" "r")
cellId = dbCreateInst(cv instId "test" <coord> "R0" 5)
The above will
return me an iterated instance 'test<4:0>' at the location defined by <coord>.
Now if i have to alter the number of instances to 2 later in the code, in older version 5.1, I could do
something like cellId~>numInst=2 which will return me an instance
'test<1:0>'.But the same is not working in 6.1.5.
After doing some research i found the command 'dbSetAnyInstNumInst' in 'Integrator’s
Toolkit: Database Reference Manual,Product Version 5.0'.
Is there any equivalent
command for 'dbSetAnyInstNumInst' in 6.1 or is there some other way in which we can change the numInst value.
Thanks in advance,
I have never tried to set numInst directly, I always assumed that it would be derived from the instance name (e.g. I<4:0> would yield numInst of 5) - the IC61x dbCreateInst function still accepts the x_numInst argument, so what doesn't work, modifying it directly? I could not find this documented anywhere. It may be that you have encountered a feature which was undocumented which happened to change between releases - I don't know without investigating deeper. By the way in your code example I think the names should be swapped for less confusion, i.e. cellId should be used for the return value of the dbOpenCellViewByType function, and instId should be used for the return value of dbCreateInst.
Hope this helps,
In reply to skillUser:
I need to modify the numInst value based on certain conditions.i.e,I will be needing different bit instances to be used as I will be using a skill code to generate my toplevel block.
In reply to Chikoo:
Use the dbCreateParamInst(celview master name x:y rotation numberOfInst parameters)
In reply to Slayer:
I can use the suggested command or even dbCreateInst ,but I will be losing the connectivity information,otherwise I need to do a Check and Save in between after instantiating the block.Again I need to retrieve the co-ordiante information before removing the old instance so that I can re-instantiate
Thats why I was checking for a work around.:-)