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.
Please let me know how to use scoreboard across two instances of an
env. I've created two scoreboards-- one, to add what i transmitted and
another to add what i received in an env.Now i've created two instances
of it and the two env's are binded such a way that the output of env
is an input to env.
Pls let me know how should i proceed to check a packet i've transmitted
in one env with that in received scoreboard in env.
Thanks in Advance...
Prabhuk, I assume that you have an instance of the monitor for
capturing transactions across the shared i/f between your 2 envs. So
that monitor should be used to forward transactions to the 2 scorebards
in your 2 envs. If the monitor is instantiated in the envs themselves,
then you'll need to find a way to disable one of them so that only 1
monitor is talking to both scoreboards.
What exactly are you checking between the 2 envs, just that the top-level signals are correctly connected between the 2 devices?
Thank You Joseph,
The env consists of a bfm which is driving a packet on a serial line
and a monitor which is collecting packet
on the serial line. So, i binded the two instances of this env such a
way that the output of one env instance is connected to input of
Meanwhile, I'll try by implementing the monitor independently as you said...
Hi Prabhu,From my experience, there is no need to change your VE design by implementing the monitor outside the environment. Sometimes it is even necessary, e.g. when creating an interface eVC that typically has a monitor instantiated within the environment and you want to check it by cross-connecting two instances and simulate them. This way you will end up with a monitor in each environment instance and it seems to me that this is exactly what you are doing.If so, I would suggest the following:1) Provide hooks in your monitor when a packet is received/transmittedThis provides the flexibility to change the behavior of scoreboarding when your environment is integrated in a larger environment (e.g. system-level) or when using layered verification environments. You may then choose to disable scoreboarding, change its behavior, or even use a system-level scoreboard according to your requirements. This behavior can be set by extending the monitor instance through the hooks provided.2) Instantiatiate your scoreboards separately from the rest of the environmentThis is helpful in system-level verification or layered environment where you may have multiple instances of your environment running and you may want to place scoreboards only in strategic locations or even use a totally different scoreboard. Of course, you will have to provide a basic scoreboard unit as part of your environment.3) Use separate configuration files according to the verification scenarioDoing so will allow you to specify the scoreboarding instantiation and functionality you wish to have from a block-level up to a system-level verification scenario with the maximum level of code reuse and the least amount of changes.4) Provide some sort of synchronizationThere is a potential problem with this configuration, when the monitor from one end will see a packet transmitted and the monitor from the other end will see a packet received at the same time. For example:At time X:Env's BFM will start transmitting a frameAt time X+Y:Env's monitor will detect a frame transmitted and try to push it on the scoreboardEnv's monitor will detect a frame received and try to compare it against the scoreboardDepending on the order of execution, Env's compare might run first, resulting in an empty scoreboard compare. So it is a good idea to sometimes delay the compare by one cycle, if this is permissible by the specification, or provide some sort of syncronization between the two.This of course is mostly the case when cross-connecting two environment instances together. Usually, there is a delay between when the packet is transmitted and when it is received on the other end.The eRM Developer Manual offers quite a few guidelines on scoreboards, including the ones mentioned above at Section 9.3, "Adding Scoreboards".Hope that helps!Regards,--Iraklis.
Thank you very much for providing me a solution.
I've used ur suggestions and able to make my scoreboard work.
Thanks again for providing me very useful information and analysis of the problem.