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.
This is something very unusual regarding the behaviour of RC on different SDC commands provided to it.
I had 2 sdc of the same design:
One sdc was which i had written it manually
Second one was the SDC generated by Spyglass tool.
The interesting thing to be noted here was that with the first SDC file, the tool was showing no error in the log while reading SDC command, but there was a error reported by the second SDC file in the logs.
The Error showed was like this:
Could not interpret SDC command. [SDC-202] [read_sdc] and that too on simple SDC commands.
So in this case wanted to know the behavior of RC on the above SDC commands.
There is no distinction between the Spyglass SDC and your hand created and the commands you mention should be fully supported provided the syntax is legal per SDC app. note
The commands you mention are all supported in full throughout the flow so I would expect some issue in the syntax causing the errors but it is hard to tell without seeing the full log or the SDC. I suggest you share that with your local support or share with the forum if that is possible for you.
hope this helps,
In reply to grasshopper:
i just cross checked again with my designregarding the SDC written, the mistake was on my end as the memory.v was also being fed to Spyglass tool, so it was throughing the error, but the SDC which i was writting manually did not have the memory module so it was passing.
Thanks for the clarification.