• 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. SystemVerilog DPI in NCSim?

Stats

  • Locked Locked
  • Replies 13
  • Subscribers 64
  • Views 25018
  • 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

SystemVerilog DPI in NCSim?

archive
archive over 18 years ago

Hi all, Because it will take some time waiting download IUS583, I tried to use SystemVerilog DPI (mostly imported functions). I heard that Synopsys can simply include C file in file list with SystemVerilog file and run simulation. But Cadence NC seems need C code compile and link to a lib. I have read the NCsim document and find a switch "-sv_lib". But I cannot find a simple example. Is there any step by step tutorial about how to compile, link and run SystemVerilog DPI C file in NCsim? Best regards, Davy


Originally posted in cdnusers.org by davyzhu
  • Cancel
Parents
  • archive
    archive over 18 years ago

    Hi Davy.

    Cadence does not modify the gcc tool, so all the options I showed previously are standard gcc ones.
    "gcc --help" will giv you lots of detail.

    The options I used are:
    "-fpic" : create relocatable code
    "-shared" : create a shared lib rather than a statically linked binary
    "-o libdpi.so" : sets the name of the output file

    One other flag you may need is "-m32", which sets the compiled code for 32 bit mode if you compile on a 64 bit machine.

    Regarding the dpi_example.tar.gz, the version I uploaded is OK, but when I download it, the file is corrupted. I'll try uploading it again here, and if that fails, feel free to email me directly and I'll send it to you by email.

    Regards,
    Steve.



    Originally posted in cdnusers.org by stephenh
    dpi_example.tar
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    Hi Davy.

    Cadence does not modify the gcc tool, so all the options I showed previously are standard gcc ones.
    "gcc --help" will giv you lots of detail.

    The options I used are:
    "-fpic" : create relocatable code
    "-shared" : create a shared lib rather than a statically linked binary
    "-o libdpi.so" : sets the name of the output file

    One other flag you may need is "-m32", which sets the compiled code for 32 bit mode if you compile on a 64 bit machine.

    Regarding the dpi_example.tar.gz, the version I uploaded is OK, but when I download it, the file is corrupted. I'll try uploading it again here, and if that fails, feel free to email me directly and I'll send it to you by email.

    Regards,
    Steve.



    Originally posted in cdnusers.org by stephenh
    dpi_example.tar
    • 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