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 started to use method/event port to sync e modules. I find some problems cadence implementation of the multiple binding of those ports.
We have a list of agent client. Each client has a monitor that reflects out event let say request.
This event is reflected by event port (out) , to this event connected the bfm of each client (in) +
There is in some other eVC arbiter that connected to the whole client events.
Now let’s test a scenario:
One client agent monitored a request and reflects it out through the port,
Expected: the client BFM and the arbiter wake up.
Actually: all the clients bfm wake up + the arbiter.
I added a little presentation that demonstrate the problem
I would like to discuss with you if this implementation of the multiple binding is a bug or my concept of using those ports are wrong
Ronen,Is the eVC arbiter connected to the clients' events using an event port as well? If that's the case, then you are probably connecting all the event ports (monitor, bfm and arbiter ports) in the same port bound set. Take a look at the 'e' Language Reference, section 6.2.2 "Multiple Bindings" and you will see that the topology of a multiple binding is a star topology, with all ports connected via a common "channel". This means that for every event emitted, all the input ports in the bound set of the same type will get the event. You can check for that by passing the "trace bind" command to specman.This looks like one of the port limitations (please correct me if i'm wrong, i'm not 100% clear from the definition):Support for point-to-point connections is between ports only, in other words, each port can be connected to only one other port.A quick workaround would be to create a duplicate port in the monitor and have it emit the request event when the original port does. You can then bind the duplicate port to the arbiter and you will get the desired behavior. If anyone can suggest a better solution, please let us know.Hope that helps!
i agree with you ,i just don't understand why cadence don't change it so the buliding of the star will take into account the direction of the port..in this configuration when i design eVC i can't give the user port that i already used (because he might bind it in star configuration)