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

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 14035
  • 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

specman clock

hellohi
hellohi over 12 years ago

Hi

i need to use specman clock for the simulation in standalone mode instead of DUT clock. I read about si_util_time_mgr in a cadence newsletter.

http://www.cadence.com/newsletters/incisiveplatform/incisive_q406.pdf?CMP=NLC-TD5628415825 

But it is not working. Is it possible to get a specman clock to handle the timing in the verification environment? Please help on this

  • Cancel
  • StephenH
    StephenH over 12 years ago

    To make an e event tick like a clock, you can do the following (when Specman isn't attached to an RTL simulation):

    event clock_rise is only @sys.any;

    This replaces the more usual approach where the event is defined from an RTL signal:

    event clock_rise is rise(tb_clk$) @sim;

    Hope this helps.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • hellohi
    hellohi over 12 years ago

    Thank you for the response,

    I tried as you mentioned, but the simulation/TCMs are not progressing but the time. Time is going infinity but there is no TCM invoked. This is the case when the TB clock is generated but not used.

    If I dont generate TB clock, it is not at all progressing with sys.any and simulation is stopped. 

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • hellohi
    hellohi over 12 years ago

    Hi,

    It worked for me using sys.any event itself . I got it by not loading any design files.

    • 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