Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Summary output report formats? #78

Open
mithro opened this issue Oct 14, 2017 · 3 comments
Open

Summary output report formats? #78

mithro opened this issue Oct 14, 2017 · 3 comments

Comments

@mithro
Copy link
Contributor

mithro commented Oct 14, 2017

Does Project IceStorm toolchain (yosys, arachne-pnr, IceStorm Tools) have some type of standard output format for getting reports about things like;

  • Messages like info, warnings & errors (for all stages)

  • Synthesis information like;

    • Parameters set for modules
    • Optimisations applied
    • Transformations
    • Component + Blackbox Statistics / Usage
    • etc
  • Place & Route like;

    • Resource usage
    • Timing information
    • etc

The reason I'm asking is that in my CI system, I would like to track how a design is changing over time. For example, I would like to understand if merging a change will dramatically increase resource usage, introduce new warnings, etc.

I don't quite know what would be the most useful to track yet, so also open to suggestions there :-). I don't really want the extreme low level details, more high level and hierarchical summaries.

I eventually hope to write some crappy Python scripts which translate the proprietary tools (like Vivado and ISE) into the Yosys / OpenFPGA formats to reuse the tracking for designs I can't yet use the open tools for.

Thank you for your help!

@cliffordwolf
Copy link
Collaborator

Yosys uses special functions to log warnings and errors. But there is no API yet for writing them to an extra file. (By in -q mode only warnings and errors are printed to stdout.)

The Yosys command stat prints resource usage statistics. You can run something like tee -o stat.txt stat as last command in your Yosys script.

Practically all of the Yosys log is "Optimisations applied" and "Transformations". You can run a command with trace to print additional trace information for every design change caused by the command (for example trace opt).

@qaarah
Copy link

qaarah commented Jul 23, 2018

Hi,
I used a blif file to input Arachne-pnr for place and route. I got outputs that are .asc and txt format. Can I get .blif file from Arachne after Place and route, Just like VPR? Is there any possibility to get a blif file from arachne-pnr after place and route.
Thanks

@proppy
Copy link

proppy commented Jun 27, 2023

note that stat now has a -json output: https://yosyshq.readthedocs.io/projects/yosys/en/latest/cmd/stat.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants