• 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. Interfacing Specman with NCSIM

Stats

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

Interfacing Specman with NCSIM

archive
archive over 17 years ago

I have written a perl script for interfacing specman with NCSIM. I have automated it upto the ncsim prompt, after that i hv to write mannually "call sn" cmd to giving control to specman. I want to further automate it so that i don't hv to give the cmd manually. Please help me. Thanks & Regards


Originally posted in cdnusers.org by vlsi_dude
  • Cancel
  • archive
    archive over 17 years ago

    If you're using a recent version of Specman and IUS, then the irun command is your friend.
    irun will compile your Verilog, VHDL, e, SystemC etc in one easy step - no need for your own scripting.

    Also, there is no need to use the "call sn" command any more.
    Now, at the ncsim prompt you can just do "sn " - there is no need to switch back and forward manually.
    For example, your ncsim.tcl script can mix specman and ius commands:

    sn load test.e
    sn test
    sn trace sequence transactions
    probe -create -shm -all -depth all
    run 100 ns


    Originally posted in cdnusers.org by stephenh
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Thanks Steve,

    I will try this.


    Originally posted in cdnusers.org by vlsi_dude
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Hello Steve,

    I have tried these commands.
    But ncsim giving the error that "sn" is not an command in ncsim.
    I m using specman 5.0 and IUS 5.5.

    I used "call sn" command also in that it's getting hanged at design browser of ncsim.
    If i m using call sn then sn test, both of these commands are running at ncsim prompt but i need that sn test will run on specman prompt.

    Please help me..

    Thanks


    Originally posted in cdnusers.org by vlsi_dude
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    OK, the problem is that you're using fairly old versions of IUS and Specman.
    If you can upgrade to Specman 6.11 and IUS 6.11 you will find that they play very nicely together.
    In fact the integration is much better even from Specman 5.1 and IUS 5.7, but if you're upgrading then it's best to jump to the latest versions...
    For example the Specman buttons are now integrated into SimVision GUI, and the SimVision Design Browser also shows the "sys" hierarchy next to the HDL. You can trace sequences direct to the waveform window ("sn trace sequence transactions" command).

    If you really cannot upgrade, I think you should be ok to do things like this from the NCSim TCL script:
    call sn {load test}
    call sn {test -seed random}
    run


    Originally posted in cdnusers.org by stephenh
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Hi

    I am using "irun" command for mixed hdl simulation (i.e. verilog testbench and vhdl dut) with e env.

    I am facing problem that i am not able to see the values of internal module signals in the waveform.

    My verilog testbench is top.v and vhdl top(DUT) is dut.vhd.

    Command that i am using is:

    "irun top.e top.v dut.vhd -top dut -gui"

    Thanks


    Originally posted in cdnusers.org by vlsi_dude
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Hi vlsi_dude. This would probably have been a good point to start a new topic.

    By default, ncelab and irun do not instrument the snapshot with access to signals in the design.
    This is done for performance reasons - less visibility makes for faster simulations.
    You can use the "-access +r" option to ncelab or irun to add read access to signals, allowing you to trace the waveforms.
    Alternatively use "-access +rc" to enable connectivity tracing as well, so you can trace drivers / loads in SimVision.

    Finally, you could use an access control file "-afile access.cfg" to list all the blocks where you need visibility - this lets you trade performance and visibility into the design by selecting only the areas you need to see into.


    Originally posted in cdnusers.org by stephenh
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Thanks Steve,

    Now I am able to access the internal signal.


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