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.
While trying to perform place and route using Encounter I'm "encountering" errors importing my design from Virtuoso. When I try to import the design, I get the following:
Reading tech data from OA Library 'NCL' ...FE units: 0.001 microns/dbu, OA units: 0.001 microns/dbu, Conversion factor: 1**WARN: (ENCOAX-775): Layer 'OVERLAP' has already been defined in Encounter database, the contents will be skipped.**WARN: (ENCOAX-713): Unsupported Layer direction for layer 'RX'. Check the layer information in OA technology database.**ERROR: (ENCOAX-719): Pitch of layer 'RX' is 0. Check the layer information in OA technology database.**ERROR: **ERROR: (ENCSYT-16006): Error in reading LEF information from OA reference libraries. Check the OA database provided.
RX is the active layer and should not be routable, however, Encounter is looking for pitch information. This layer should not be used in place and route at all. The only reason I can think of that Encounter might need it would be in RX_M1 vias. How do I tell Ecnounter to ignore this layer? Could I change the prRules section of my technology file? Here is that section of my tech file:
prRules( prRoutingLayers( ;( layer preferredDirection ) ;( ----- ------------------ ) ( PC "halfRoute" ) ( RX "halfRoute" ) ( M1 "horizontal" ) ( M2 "vertical" ) ( M3 "horizontal" ) ( M4 "vertical" ) ( M5 "horizontal" ) ( M6 "vertical" ) ( M1_2B "horizontal" ) ( M2_2B "vertical" ) ) ;prRoutingLayers prViaTypes( ;( device viewName viaType ) ;( --------------- ------- ) ( ("PC_M1" "symbolic") "default" ) ( ("RX_M1" "symbolic") "default" ) ( ("M1_M2" "symbolic") "default" ) ( ("M2_M3" "symbolic") "default" ) ( ("M3_M4" "symbolic") "default" ) ( ("M4_M5" "symbolic") "default" ) ( ("M5_M6" "symbolic") "default" ) ( ("M6_M1_2B" "symbolic") "default" ) ( ("M1_2B_M2_2B" "symbolic") "default" ) ) ;prViaTypes prRoutingPitch( ;( layer pitch ) ;( ----- ----- ) ( "M1" (plus (techParam "grM1Width") (techParam "grM1Space")) ) ( "M2" (plus (techParam "grM2Width") (techParam "grM2Space")) ) ( "M3" (plus (techParam "grM3Width") (techParam "grM3Space")) ) ( "M4" (plus (techParam "grM4Width") (techParam "grM4Space")) ) ( "M5" (plus (techParam "grM5Width") (techParam "grM5Space")) ) ( "M6" (plus (techParam "grM6Width") (techParam "grM6Space")) ) ( "M1_2B" (plus (techParam "grM1_2BWidth") (techParam "grM1_2BSpace")) ) ( "M2_2B" (plus (techParam "grM2_2BWidth") (techParam "grM2_2BSpace")) ) ) ;prRoutingPitch) ;prRules
Thank you for your help.