• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification Shared Code
  3. AHB master slave per instance coverage in multiple ahb ...

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 38
  • Views 13420
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AHB master slave per instance coverage in multiple ahb bus

archive
archive over 18 years ago

AHB evc does per_instance coverage for master and slave. This coverage holds good when only one AHB evc is instantiated. In SOCs with multiple AHB buses [evc instantiation], the coverage of master and slave gets reported as combined coverage of masters from different AHB buses. To work it around here is a piece of code that needs to be appended.

Two files are included :

1) macro.e : In this file macro is defined to create unique names for all masters and slaves using EVC instance name as well as its own name.
2) top.e : Copy paste all lines of this file into config file. Change the AHB evc instantiation names while calling the macro. Macro should be called for each eVC instantiation with appropriate master/slave names.

Warm Regards,

Vishal
vishalj@cadence.com


Originally posted in cdnusers.org by vishalj
ahb_per_instance.zip
  • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. 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. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information