Home
  • Products
  • Solutions
  • Support
  • Company

This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  • Products
  • Solutions
  • Support
  • Company
Community Custom IC Design Waveform file is empty?

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 13410
  • 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

Waveform file is empty?

Woodhouse
Woodhouse over 4 years ago

For generating waveform, I did following steps:

a. Place an instance of "vsource" from "analogLib" in schematic
b. Set the "source type" to "pwl"
c. Specify the path for csv or txt file in the properties form

d. In ADE->Setup->Simulation Files specify the Include Path to include the directory which contains the tx.txt file.

tx.txt file:

0 1

0.5 1

1 0

In the log file, it shows a Error (CMI - 2197) : Waveform file 'tx.txt' is empty.

Any idea about this Error? I tried txt/csv/prn, but all failed.

Thanks,

Wood.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 4 years ago

    Hi Wood,

    The only way I can reproduce that problem is if the tx.txt file is actually empty. If it contains the lines you mention, whether it's got DOS or Unix line endings, or blank lines between the rows, it works fine. Are you sure the file has been saved in the location in the path and is not really empty? Which IC subversion and spectre subversion are you using? The IC version can be found with Help->About in Virtuoso and the spectre subversion should appear at the top of the spectre log file.

    You should see in the spectre output  log a line like this appear (even if it fails with error):

    Time for NDB Parsing: CPU = 76.988 ms, elapsed = 128.895 ms.
    Time accumulated: CPU = 122.98 ms, elapsed = 128.898 ms.
    Peak resident memory used = 62.1 Mbytes.

    Reading file: /export/home/myuser/demos/OCEAN/Models/tx.txt
    Time for Elaboration: CPU = 139.979 ms, elapsed = 139.731 ms.
    Time accumulated: CPU = 262.959 ms, elapsed = 268.884 ms.
    Peak resident memory used = 69.6 Mbytes.

    and ADE should show the file name as a hypertext link. For me, if it's empty - clicking on the link causes ADE to tell me that it's empty. Otherwise clicking on the link will bring up another window showing the contents. So first is to check that it's really being included from the location you think it is, and the second is to see whether it is truly empty or not.

    It seems pretty unlikely that spectre would complain about a file being empty when it isn't. Reading PWL files has been supported for at least 25 years (almost certainly since the beginning of Spectre's life, so longer than that), so I'd be very surprised if this was broken.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Woodhouse
    Woodhouse over 4 years ago in reply to Andrew Beckett

    Many thanks, Andrew.

    The reason why this error happens is the WINDOWS-UNIX file conversion. 

    I checked those files in WINDOWS only, and then move them to UNIX. Those files moved to UNIX are not original files anymore because they are encrypted automatically. 

    Sorry for a silly question, my bad.

    Regards,

    Wood.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Woodhouse
    Woodhouse over 4 years ago in reply to Andrew Beckett

    Many thanks, Andrew.

    The reason why this error happens is the WINDOWS-UNIX file conversion. 

    I checked those files in WINDOWS only, and then move them to UNIX. Those files moved to UNIX are not original files anymore because they are encrypted automatically. 

    Sorry for a silly question, my bad.

    Regards,

    Wood.

    • 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