• 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. How do I control probe start/stop in ncsim from embedded...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 65
  • Views 7608
  • 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

How do I control probe start/stop in ncsim from embedded CPU?

Ncsim User 1
Ncsim User 1 over 6 years ago

I am running an RTL simulation with an embeddd CPU and some encryption logic. 

The CPU runs some codes to check the result of encryption logic and can run hours or days. 

My idea is to let the CPU control when to dump waveforms, likely when some conditions are met in the logic. Then stop when the conditon elapses. 

How should I do that? 

  • Cancel
Parents
  • StephenH
    StephenH over 6 years ago

    The simplest way would be to use Tcl breakpoints to execute the probe commands when certain signal values are observed. For example, at the start of simulation, create the probe for the signals you want to debug, and give the probe a name, then immediately disable it (unless you want to probe at time 0):

    probe -create -shm -name myprobe <list_of_signals>
    probe -disable myprobe

    Then, create breakpoints to turn the probe on and off:

    stop -create -execute {probe -enable myprobe} -continue -condition {[value top.sig_to_start_probing] = 1'b1}
    stop -create -execute {probe -disable myprobe} -continue -condition {[value top.sig_to_start_probing] = 1'b0}

    There are many other types of breakpoints so you'll need to use your imagination to decide which is the most appropriate for your scenario.

    I would also suggest thinking about whether it's better to check the encryption result using some zero-time method in the testbench instead of having a simulated CPU to crunch the data, your tests would finish much quicker and be much easier to debug!

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • Ncsim User 1
    Ncsim User 1 over 6 years ago in reply to StephenH

    Thank you. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Ncsim User 1
    Ncsim User 1 over 6 years ago in reply to StephenH

    Thank you. 

    • 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