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 would like to create bindkeys for "DC Operating Points" and "Design
Defaults" to easily toggle between the displaying DC Node Voltages and
Operating points, and the design defaults for devices.
Unfortunately, when I select "Results -> Annotate -> Design
Defaults", etc... the ICFB window isn't showing the functions being
Can anyone comment on what I what the necessary procedure names are that I need to call?
No need to comment on how to bind to bindkeys, etc.
Hello,I encountered a similar situation. My problem was to toggle the schematic node information. First a comment about the ICFB window. Do you know that you can show more log results in the ICFB window? But even if you know for example the "hiiSetCurrentForm('hiSomeFormName)"command, and the following commands, repeating them from some function did not gave me the same result. What I found out is that ICFB behaves differently if commands are clicked by you or if they are runned from within a function. But when using the load("someFile") function, it behaves as if you clicked the forms. So what I did, was to save the desired commands to a file, and load them to 'replay' the form actions. To finish, here is my toggle node info function. I think you will be able to reuse it yourself. procedure( wrSchematicNode( @optional value) let( ( instance wrError) cv = geGetEditCellView( ) wrError = nil unless( cv->mode != "r" wrWindowName( strcat( wrDecodeBindKeysText ": wrSchematicNode: error: cell must be editable")) wrError = t ) ;; xxx 060516 the cell must be editable. Or a copy of the device must be openend in a ;; dummy view which is editable. It is not that exactly this cell must be editable. unless( wrError unless( boundp( 'wrSchematicNodeValueN) wrSchematicNodeValueN = 0 ) if( ! null( value) then wrSchematicNodeValue = value else ;; 060907 Add "pin name" "net name" "voltage" "current" if you like. Increase the ;; number (now 3) for the modulo operation. wrSchematicNodeValueList = list( "none" "pin name" "net name") wrSchematicNodeValueN = modulo( wrSchematicNodeValueN 3)+1 wrSchematicNodeValue = nthelem( wrSchematicNodeValueN wrSchematicNodeValueList ) ) wrWindowName( strcat( wrDecodeBindKeysText ": wrSchematicNode: toggle terminal names: " wrSchematicNodeValue)) wrShFile = outfile(".wrCadenceFile") fprintf( wrShFile " \n ;; A device must be selected. If not, select a device. \n instance = car( geGetSelectedSet( )) \n if( null( instance) \n then \n instance = car( setof( shape cv->instances shape~>libName == wrDeviceLibName)) \n ) \n asaEditCompDisplay( ) \n hiiSetCurrentForm('_ahiiUniqueSymbolformannotateForm0) \n _ahiiUniqueSymbolformannotateForm0->labelInfo->terminal->value = t \n geSelectObject( instance) \n _ahiiUniqueSymbolformannotateForm0->tdisplay->value = wrSchematicNodeValue \n hiFormDone(_ahiiUniqueSymbolformannotateForm0)") close( wrShFile) load( ".wrCadenceFile") hiRedraw( ) ) ))A few extra remarks: This function is copied from my Cadence customization file. You can find it at http://relyveld.wordpress.com/cadence-page/ wrDeviceLibName is the name of the attached technology file name.wrWindowName is a function (part of my wrAltEdit.il file) which prints status information in the editor window.