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.
A while back, I posted a blog called Getting Started with dbGet. It was a brief introduction to this database access mechanism. Well, dbGet is only half the story - there is also a command called dbSet, which can give you even more power in your scripting or manipulating of the design database. It works in much the same way as dbGet. As a quick review, let's say we wanted to find out the placement status of the instances in our design. If we didn't remember the exact syntax, we would start with:> dbGet top.?The ? will list all the things we can look at regarding "top", the top cell of our design.> topCell: fPlan hInst insts name nets numBidirs numInputs numInsts numNets numPhysInsts numPhysNets numTerms objType pgTerms physInsts physNets props statusClockSynthesized statusGRouted statusIoPlaced statusPlaced statusPowerAnalyzed statusRCExtracted statusRouted statusScanOpted termsWhat we want is insts, or all the instances in the design:>dbGet top.insts.?>inst: box cell instTerms isDontTouch isHaloBlock isJtagElem isPhysOnly isSpareGate name objType orient pStatus pgCellTerms pgTermNets ptAnd finally, pStatus (placement status):>dbGet top.insts.pStatus>fixed placed placed placed placed... (etc.)So now that we have the attribute we want, let's change it! Suppose we want all the instances to be fixed and not just placed. Well, dbSet makes this very easy:>dbSet top.insts.pStatus fixedIf you reissue the dbGet command, you'll see that all the instances are now fixed.Here's a more realistic example. I had a design where I wanted to fix the placement of all of my adder cells. They were large cells, and allowing them to be moved around after their initial placement would cause them to be placed far away from their original location. So, first I had to grab pointers to all of the adder cells:>dbGet -p2 top.insts.cell.name ADD*The -p2 means to grab the database pointers of the instances gathered by this command, which means all instances whose master cell names start with ADD. (For some more explanation of how the -p function works with dbGet, see the post A dbGet Code Example).Now that I have those pointers, I can examine the placement status of these instances:>dbGet [dbGet -p2 top.insts.cell.name ADD*].pStatusBut what I really want to do is set the placement status to fixed, so the final line would look like this:>dbSet [dbGet -p2 top.insts.cell.name ADD*].pStatus fixedFor a list of attributes that are editable with dbSet, you can check out Appendix B of the Encounter Text Command Reference. Scroll down the tables and look at the "Editable" column. Most of the editable attributes fall under the "inst" database object.I hope this short introduction to dbSet has inspired you to check it out and use it in your scripts. Let me know in the comments how you're using dbSet. I'm always interested to see clever one-line dbGet/dbSet commands. In fact, I'm collecting them for a future post. (Don't worry, I'll give you credit!)
Kari...as usual simple and clear...thanks a lot...Pls continue this so that we all learn db scripting from this :-)..thanks again...