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.
Get email delivery of the Cadence blog featured here
How many times while working in Encounter Digital Implementation system have you wanted to find the transition time on a certain pin? How did you go about finding it? Here are some ways I know that I've used:
Well, there's an easier, cleaner, faster way. The report_constraint command! This is an oft-forgotten little gem that can be very handy. It's worth reading about all of its features in the documentation, but today I wanted to highlight how it can be used to find the transition violation of any pin. Just specify the constraint we want to report (max transition) and the pin:
report_constraint -drv_violation_type max_transition i_BUFX2/Z
And you'll see results something like this:
I bet some of you out there are using this very command for other useful checks -- share your favorites with us in the comments, please!- Kari Summers
Hi Bob, thanks! I like your method as well, lots of info in one shot. And GREAT point about the view, since almost everything is run in MMMC these days. I double-checked the documentation for report_constraint, and there is a -view argument, so we're covered both ways.
Great post Kari. I like it because there are a lot of different ways to do this and I learned something new from your approach.
I always tend to go to a programmatic query of the timing graph. Like this:
encounter 1> get_pins DTMF_INST/TDSP_CORE_INST/i_10084/Y
encounter 2> report_property [get_pins DTMF_INST/TDSP_CORE_INST/i_10084/Y]
max_transition | 4.500
slew_max_fall | 0.398
slew_max_rise | 0.739
slew_min_fall | 0.398
slew_min_rise | 0.739
encounter 10> get_property [get_pins DTMF_INST/TDSP_CORE_INST/i_10084/Y] slew_max_rise
A nice thing about get_property is that you can specify which MMMC view you want query:
encounter 11> get_property [get_pins DTMF_INST/TDSP_CORE_INST/i_10084/Y] slew_max_rise -view setup_func