• 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. Custom IC SKILL
  3. Why ocnWaveformTool('awd) only displays 19mS instead of...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 149
  • Views 1249
  • 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

Why ocnWaveformTool('awd) only displays 19mS instead of 60mS

vanderpollator
vanderpollator over 12 years ago
I sill prefer to use ocnWaveformTool('awd) in oceanscript for Spectre transient analysis.( Cadence:  IC5141-usr6).    Strangely, even stop time is 60mS in Spectre transient analysis, ADE only shows 19mS waveform data on the screen even Spectre has gone through all 60mS simulation.   Any idea why is going on?
  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    This is probably due to an issue with the SST2 output format (since resolved - I think it was fixed in a later subversion). I'd suggest you use:

    envSetVal("spectre.envOpts" "simOutputFormat" 'string "psfbin")

    If you do this, I'd suggest you do a Simulation->Netlist->Recreate before running a simulation.

    Regards,

    Andrew.

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

     Thank you, Andrew.

    It is working.    I also found that if I closed the icfb (or msfb) window and started Cadence from scratch, it also solved the problem (until it rears its ugly head again!)    

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    If I remember rightly, the problem is caused by running a short simulation and then a longer one - something in memory is not correctly updated and hence it does not realise that the stop time is longer. So quitting and restarting would fix that too. This only happens with SST2, and only if the change in stop time is significant enough.


    Regards,

    Andrew

    • 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