• 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. Conditional SHM probe

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 65
  • Views 15065
  • 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

Conditional SHM probe

Sharjeel
Sharjeel over 17 years ago

Hi,

   I am running a large simulation, and want to make a conditional SHM database.

To be more specific, consider a signal P. I want to buffer (buffer, not save) the SHM database between every two successive P posedges. If at current posedge of P, signal Cond is 1, write the buffered data to database, otherwise discard it.

 Any ideas?

 Thanks,

 Sharjeel Saeed

  • Cancel
  • StephenH
    StephenH over 17 years ago

     Hi Sharjeel.

    Interesting challenge! I don't know if it's natively supported.

    You could try the following via TCL:

    1. Set up all the probes with "probe -create -name <unique_name>" choosing a unique_name that corresponds to the DUT signal that gates the probe.
    2. At time zero, use "probe -disable <unique_name>" to start with no probing.
    3. Add TCL breakpoints via the "stop" command to monitor the signal and turn the probes on and off:
      stop -if <dut_sig>=1 -execute {probe -enable <unique_name>} -continue
      stop -if <dut_sig>=0 -execute {probe -disable <unique_name>} -continue
    This is a bit simplified, as I can't think if the breakpoints are edge or level sensitive. I'm sure you can work it out from this example and the docs. Good luck, and please post back when you've got it to work, I'm sure others would thank you for it...
    • 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