• 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. please help on verilog and vhdl combination problems

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 66
  • Views 16042
  • 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

please help on verilog and vhdl combination problems

victorhan
victorhan over 11 years ago

Hi Candence,

I met a problem in using verilog and vhdl:

1) I use verilog to make a testbench while the DUT all are made by VHDL

2) I want to initialize the lower level memories in DUT. I have tried to use $nc_mirror, but it seems useless.

So would you like to give me some suggestions on how to initial memories in VHDL designs through  verilog testbench?

Thanks!

  • Cancel
Parents
  • shalem7
    shalem7 over 11 years ago

    I am not sure about the error.I did not inderstand the # in #data[i].

    data[i] also needs to be in  " ".

    nc_force command has to be like this.

    If your memarray is of size 5,each single bit

    $nc_force("tb_top.vhdl_top:ocmem:memarry" , "10010"); //if it is a single bit. 

    Regards,

    Shalem

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • shalem7
    shalem7 over 11 years ago

    I am not sure about the error.I did not inderstand the # in #data[i].

    data[i] also needs to be in  " ".

    nc_force command has to be like this.

    If your memarray is of size 5,each single bit

    $nc_force("tb_top.vhdl_top:ocmem:memarry" , "10010"); //if it is a single bit. 

    Regards,

    Shalem

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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