• 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
  3. HW/SW Co-verification - Embedded assembly code coverage

Stats

  • Replies 0
  • Subscribers 66
  • Views 59
  • Members are here 0

HW/SW Co-verification - Embedded assembly code coverage

KS20250205199
KS20250205199 11 days ago

Here is a verification challenge I'm facing and gathering ideas on the possible solutions.

I have a custom processor IP in the design which executes some pre-compiled code. The assembly code is compiled into Verilog ROM. This ROM is then simulated within the design. So the Processor starts executing this ROM code after power up.

Are there any tools or methodologies for collecting embedded firmware code coverage during RTL simulation?

The simplest way would be to create cover bins for every ROM address and measure if all instructions were fetched. But this might not be enough, would be good to see if assembly code branches are covered.

Please share your experience, thoughts or ideas you might have seen in similar cases.

Thanks

  • Sign in to reply
  • 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.

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

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