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.
When you steer toward Manufacturing->Drill Customization a
spreadsheet-looking form comes up, obviously built using the
Anyone know how to access this info directly thru SKILL? I
vaguely remember it had something to do with axlGetParam
but I might well be wrong.
local Cadence guru
Hi Chris,The table looks to be built directly from the drills used in your design.You could easily emulate this using the pin/via definition attributes.eg. pin ->definition ->drillCharCheers, Dave
Hey Dave,Ya I could cycle through every pin/via in the design and build up a table but I was hoping for a more elegant solution.fxf gave me a clue to do something very similar to this 3 companies and 6 years ago, I just don't recall. Argh.fxf you out there?Chris Walterslocal Cadence guru()
You could do it via the extracta. I have generated my own drill tables that way - it's much faster than going through each object dbid by dbid. I would be interested in Frank's answer.
This form builds its table by finding all pins and vias in the design. Remember to set the "invisible" option in the axlSetFindFilter. For performance reasons, it uses this list of pins/vias to build a hash (see Skill association tabke) tableof all padstacks used in the design.See example finding all dbids of a type @ /share/pcb/examples/skill/select/ashfindall.il
Thanks Dave, fxf for responding.I solved the problem by picking off the drillfigure name and character info while iterating over axlDBGetDesign()->padstacks . And boy was the client surprised when we found the list contained some entries not in the manaully-editied drill legend! Thx again,Chris Walterslocal Cadence guru()
You should note that padstacks may be in axlDBGetDesign()->padstacks that are not used by thedesign. You should always get the list of vias and pins and build the used padstack list from that.
Ah, like if someone placed something that used padstack Z, then later deleted the something but the padstack itself remains in the design file. Subtle.Thx for the tip!Chris Walterslocal Cadence guru()
I run axlPurgePadstacks before I attempt to do anything that looks at ALL the pad stacks.
axlPurgePadstacks('padstacks nil) can also be used before axlDBGetDesign()->padstacks so that this list justhas padstacks used in the database. You might want to do axlDBRefreshId(axlDBGetDesign()) after the purge call.