Stats

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

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
Parents

  • 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
Reply

  • 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
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.