• 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. Communication between Verilog BFM and C-Based Verification...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 15089
  • 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

Communication between Verilog BFM and C-Based Verification bench

Arun Nellur
Arun Nellur over 11 years ago

Hi

I have a SOC verification bench in C/ASM and integrated SV/Verilog based BFM/VIP. The system level tests are based on C/ASM.

To carry out functional simulations, the C/ASM tests are compiled, linked at the binary data of instructions are read into the On-Chip Memory for execution.

How can we enable the above environment where BFM(say its a master), waits for the system to reach to a point where system is ready and BFM(say its a master) can request data from/to the SOC?

To say in a short words, how can we achieve effective handshake between Verilog/SV(BFM) - C/ASM environments.


Could somebody please donate your ideas. 

 

Thanks
Arun

  • Cancel
  • StephenH
    StephenH over 11 years ago

    Assuming that your C/ASM is running on a CPU inside the SoC, a common techniqueis to have some GPIO ports on the SoC connected to "registers" in the testbench. Your BFM would be triggered by the data written into the registers when the C/ASM test wants to control the BFM. This is one of the approaches used by the Cadence VIPs for SoC-level, our VIP documentation refers to it as "virtual register interface".

    An alternative approach is to stub out the CPU and use a BFM instead. This BFM is driven by your test software which runs on the host workstation and talks via SV-DPI to the BFM.

    • Cancel
    • Vote Up 0 Vote Down
    • 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