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.
I am using e testflow, and encountering an interesting case that i would like to share and get your feedbacks.
I have an environment "A" with tf_domain == domain_a.
Under this environment i am instantiating an environment "B" which is testflow unit and have 2 sequence drivers which are also testflow units.
According to the Cadence test flow document, if the tf_domain field is untouched, it is determined to be (with soft constraint) to be the same as the nearest enclosing testflow unit, if there isn't such tf_domain is set to DEFAULT.
However, what i see is:
env_b.tf_domain = domain_a
env_b.seq_driver_1.tf_domain = domain_a
env_b .seq_driver_2.tf_domain =DEFAULT
How come the second sequence driver didn't got the same tf_domain value like the other units?
Moreover, the tf_domain field is declared as const, thus can not be changed after generation.
I will be happy to hear your feedbacks.
I've create a small testcase to try and reproduce your issue. However (as so often) it works fine here. I'm using 13.10.010-s and I only constrain the env tf_domain. All sub units (which are all testflow_units) inherit they tf_domain setting from the enclosing unit. If you want to force the tf_domain, you can use constraints, i.e.:(in the env)keep seq_driver_2.tf_domain==tf_domain;
In reply to hannes:
First, thanks for your quick response, I have tried your suggestion and it fix the problem.
Moreover, even constraining only the env "B" solve it.
It seems like the generation solver somehow ignored the soft constrain.
The explicit keep on the tf_domain solve this problem.
While we are talking on e testflow I want to ask one more question.
Does the usage of testflow make the e objection mechanism redundant ?
What are Cadence recommendation on this subject ?
In reply to myonlyscreen: