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

How to get the area breakdown of plugins in Vexii? #29

Open
Jzjerry opened this issue Oct 11, 2024 · 4 comments
Open

How to get the area breakdown of plugins in Vexii? #29

Jzjerry opened this issue Oct 11, 2024 · 4 comments

Comments

@Jzjerry
Copy link

Jzjerry commented Oct 11, 2024

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?

@Dolu1990
Copy link
Member

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.
Using verilog module to contains logic feature get messed up a lot with hierarchy flattening.

@Jzjerry
Copy link
Author

Jzjerry commented Dec 26, 2024

Just made some data analysis on the impact of generation options on the area (LUTs+FFs):

image

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 true, and the red ones are false. For integer options (like xlen and lanes), the red points are with higher values.

Could be a reference for those who want to resize their Vexii I hope 🤔.

@Dolu1990
Copy link
Member

Nice :D
Thanks ^^
1024 designs, how long did that toke XD ?

@Jzjerry
Copy link
Author

Jzjerry commented Dec 26, 2024

5 minutes per design, so around 4 days in total XD.
Can be faster if do it in parallel.

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

2 participants