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

Update VTR quick start guide to use yosys / parmys #2739

Closed
vaughnbetz opened this issue Sep 21, 2024 · 6 comments · May be fixed by #2776
Closed

Update VTR quick start guide to use yosys / parmys #2739

vaughnbetz opened this issue Sep 21, 2024 · 6 comments · May be fixed by #2776

Comments

@vaughnbetz
Copy link
Contributor

The VTR quick start guide uses Odin II as the synthesis tool, but the yosys/parmys flow is now the default VTR flow. We should update the quick start to use yosys/parmys. The Odin II section should be moved down to a later, optional part of the quick start that just describe how to run Odin II (as the primary example of yosys/parmys would have already covered the whole flow).

Proposed Behaviour

Change all mention of Odin II to the equivalent parmys / yosys flow commands. Move the Odin II command(s) down to the end of the quick start under an Odin II section.

Current Behaviour

Odin II is the only synthesis tool described in the quick start.

@vaughnbetz
Copy link
Contributor Author

@ZohairZaidi : this would be a great issue to fix if you have the time ... it's a bit annoying that the quick start doesn't cover our newly default synthesis flow.

@ZohairZaidi
Copy link
Contributor

Hi @vaughnbetz, just to clarify, you are referring to the "Manually Running the VTR Flow" section right?

@vaughnbetz
Copy link
Contributor Author

Yes, that's right.

@ZohairZaidi
Copy link
Contributor

Hi @vaughnbetz, I was wondering if you knew the equivalent steps to generate the blif file outside of the VTR flow script as I was trying to follow the guide posted on the original parmys GitHub repo (https://github.com/CAS-Atlantic/parmys-plugin) but it seems to be out of date.

@vaughnbetz
Copy link
Contributor Author

I haven't done it, so I'm not sure. @alirezazd @amirarjmand93 : can you summarize the commands? @ZohairZaidi : you can also probably infer them by printing out / watching the various commands run by run_vtr_flow.

@ZohairZaidi
Copy link
Contributor

I just realized that my issue has been answered in the original repo. thanks for the help.

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

Successfully merging a pull request may close this issue.

2 participants