-
Notifications
You must be signed in to change notification settings - Fork 13
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
How to get the area breakdown of plugins in Vexii? #29
Comments
Hi, I would say, the only way is to run the synthesis flow between a configuration with and without a feature to get its "real" ressource usage. It may not be faisable for everything thing as there may be some coupling between a few plugins. |
Just made some data analysis on the impact of generation options on the area (LUTs+FFs): Basically, I generated 1024 Vexii designs with random configurations and ran a Vivado script to synthesize them, then got the area report. For boolean options (like with-late-alu), the blue points are those that set the option to Could be a reference for those who want to resize their Vexii I hope 🤔. |
Nice :D |
5 minutes per design, so around 4 days in total XD. |
Hi,
I'm trying to check the area breakdown of the plugins in Vexii (like the area of IntAlu, Lsu or Branch).
Is there a way to generate plugins as separate verilog modules? Or are there any other ways to analyze their area?
The text was updated successfully, but these errors were encountered: