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
[Team Specman welcomes Principal Support Application Engineer Avi Farjoun to share some important tips on the famous “vhdlsync” switch]
As users with mixed VHDL and Verilog environments know, even in this day & age mixed HDL simulation cycle semantics are not very well defined. Even worse: there is no standard that specifies the order of execution of always blocks and VHDL processes, which can lead to simulation results in differing from an equivalent pure VHDL or pure Verilog simulation. Specifically, there are two very common problem scenarios, both of which can get trickier when Specman comes into the picture. Consider:
Scenario 1 - VHDL entities that drive Verilog regs and netsIn this scenario, Specman might sample Verilog signal values that are premature
Scenario 2 - Verilog entities drives VHDL signalsIn this case, Specman might not sense a change on VHDL signals.In order to better understand why these scenarios happen, let's look at a "normal" Specman-simulation cycle:
The following Diagram better illustrate this flow (Specman is operating in the "Red Zone"):
When you tie this sequence of activity to Scenario 1 above, Specman will sample the Verilog signal after it is already changed to the next value (instead of seeing the value before the change).
In reference to Scenario 2 above, Specman might miss the change on the VHDL signal since it is updated after the synchronization sample is taken.To avoid both of these problems, the switch 'vhdlsync' has been added to irun/ncelab. In short, this switch separates VHDL process and Verilog always block execution lists. Thus, if you want to consider VHDL signal assignments to be treated as NBAs, and want Specman to sample the VHDL values just before they are updated, then 'vhdlsync' should be used. In such a case Specman starts synchronizing after the execution of VHDL process list and before it loops for more signal updates in the same simulation time (VHDL delta cycle increments), i.e. order of execution will be Verilog followed by VHDL and Specman gives consistent results irrespective of if it samples a signal in Verilog or VHDL.
Conversely, if this switch is not used, the order of evaluation is arbitrary, (as mentioned, there is no standard that specifies the order). Nevertheless, there might be many designs that count on that order (or should I say, “disorder”), and using 'vhdlsync' might change the behavior of their simulation. For example, consider the case where there are messages coming from different blocks at the same simulation time which may come in a different order. In this case the switch is not default, and both behaviors (with and without the switch) are supported, and "correct".
There are more details and examples where this switch can be required in Specman's Integrator's Guide, Chapter 13.4.6, "Mixed HDL Synchronization Issues”
Avi FarjounPrincipal Support Application EngineerIncisive & Specman Technology