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.
When I looked into FE timing report after clock tree build, I am expecting the actual clock propagating delay will be used in the setup timing check report. I did see the actual clock propagating delay to the launch ff clock pin (from clock root through all the buffers/inverters) is used, but for the capture ff, the data required time is simply calculated by: Phase Shift - setup. For examle, for the timing arc ff-->ff, if the clock cycle is 10ns, capture ff setup time is 0.1ns, then, FE simply told me the required time = 10 - 0.1 = 9.9ns. Why is the clock delay to the capture ff clock pin (required time) not calculated by actual clock path propagating delay while the clock path to the launch ff clock pin did? Did I do something wrong?Thanks,Tongju
Hi Tongju,It sounds like something has malfunctioned in the process of switching the design from ideal clock mode to propagated clock mode, and peculiarly it has affected only the capturing clock in your case. I would first look to check whether different clocks driving the launch and capture- they probably are different. If they are different then I would examine the postCTS SDCs you're using and look at the "set_propagated_clock" SDCs that are present. The way clocks are propagated in Encounter is that for each AutoCTSRootPin in your clock tree spec file, a set_propagated_clock statement is appended to your SDCs. If this has malfunctioned for some reason, you'd see it reflected as a missing set_propagated_clock in your postCTS SDCs. Sometimes, users choose to manage clock propagation themselves and insert "set_propagated_clocks [all_clocks]" either interactively or as part of their postCTS SDCs. You may want to try that to see if you can cause the capture clock to be propagated.Hope this helps,Bob