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.
Has anyone run into a problem with cdb2oa dropping layers when converting a cdb library to oa? When I use the tool, it seems to convert the "drawing" purpose layers OK but not our "mk" layers. There is no error or warning in the log file and everything appears to have been converted properly but when I look at the layout, the marker layers are not there. The layers are in the LSW (for OA) and they are set to valid/visible/selectable. I have also confirmed that the layers exist in the CDB database. I know I am probably just doing something funky but I don't have a clue what it is that I am doing wrong. To the best of my knowledge, I believe I have followed the steps defined in section 4 of the "CDB to OpenAccess Translator User Guide" correctly. Has anyone else had a problem like this and if so, what was the cause and the cure?
I have seen such thing, but it's more then 4 years back since I did my last conversion.
Check if there are some layers in your OA database which have either the layer name or the purpose "unknown".
I can't remmeber to what the layers have been assigned to, also I don't know if the "unkown" was in small or capital letters.
Best is to filter your shapes for the layer name or lpp throug SKILL.
If you find such a layer in the OA db check if the shape is the same as the layer your missing form CDB.
In reply to berndfi:
Thank you for the response. We were actually able to figure out the problem. We had created the tech layer information manually (without using CDB2OA to convert the tech file). When we did that we were defining one of the pre-defined purposes to a different number from what OA recognizes as the default. This resulted in a conflict and apparently, that purpose and all subsequent purpose definitions were ignored. Once the tech layer definitions were corrected, we were able to convert the layouts with all layers intact.