• 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 Design
  3. Date/time (or $system) in verilogA

Stats

  • Replies 2
  • Subscribers 125
  • Views 61
  • Members are here 0

Date/time (or $system) in verilogA

leok
leok 8 hours ago

Hi,

I'm writing a stimulation block in verilogA and search for a method of storing data in a enduring file (outside the simulation directory tree) for postprocessing.

But I'm somewhat missing functions in verilogA that allow me to distinguish the sims by something like date/time or runpoint/corner. A "$system" call would also be sufficient to get at least the date/time information.

Else my data tends to be overwritten (even by parallel running simulations)...  Is there such a feature in verilogA? Or what's the preferred workaround?  I can only think of a postprocessing script collecting the data previously written into separate simulation directories, but that seems not really a reliable way...

Best Regards,
leo

  • Cancel
  • Sign in to reply
Parents
  • Andrew Beckett
    Andrew Beckett 8 hours ago

    Leo,

    See How can you access the current date from a system call in VerilogA?

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • leok
    leok 6 hours ago in reply to Andrew Beckett

    Thank you! That solves the issue. Seems like I had the wrong search terms.. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • leok
    leok 6 hours ago in reply to Andrew Beckett

    Thank you! That solves the issue. Seems like I had the wrong search terms.. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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