Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 9055
  • 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

SOA Warnings

PhilCGD

Hello.

I want all my SOA warnings to go to a (text) file not the log file.

I realise I can do this:

How to change the output destination of Spectre SOA (Safe Operation Area) Check result (cadence.com)

But it puts it in a sqldb format but I want a text file.

Ideally a CSV for excell but that may be asking too much :-)

Thanks

Phil

  • ShawnLogan

    Dear Phil,

    PhilCGD said:
    I want all my SOA warnings to go to a (text) file not the log file.

    I do not know a specific command to create a csv file from the SOA asserts. However, there are a couple of methods that you may (or may not?) be aware of that I thought I would mention

    1. From the Cadence On-line support article at URL:

    support.cadence.com/.../ArticleAttachmentPortal

    you can use ADE to read in the SQL formatted results and create a table. This table can be saved in csv format

    2. If you use the option to save the SOA checks to an SQL file, there are a number of sites that will attempt to re-format the SQL file to a csv file. As an example of one site:

    products.groupdocs.app/.../sql-to-csv

    Shawn

  • Andrew Beckett

    Phil,

    It appears that the built-in SOA checks can't be written to a separate text file (unlike Spectre asserts, which can be via the checklimitdest/checklimitfile options). There's this article: What are foundry SOA checks? which compares SOA checks to asserts, but if it's an SOA check, it would need an enhancement to allow them to truly be written to a separate file (it seems a reasonable request to me, as it's similar to what the checklimit* options provide).

    Andrew

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.