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

Resource estimate executive summary lacks BRAM numbers #2288

Open
anshumanmohan opened this issue Sep 24, 2024 · 6 comments
Open

Resource estimate executive summary lacks BRAM numbers #2288

anshumanmohan opened this issue Sep 24, 2024 · 6 comments

Comments

@anshumanmohan
Copy link
Contributor

Synthesis 101 is a short guide about generating syntheses from .futil files. In refreshing it, I noticed that the executive summary, generated using the command:

fud e --to resource-estimate <filename>.futil

makes no mention of BRAMs. If you generate the actual report using:

fud e --to synth-files -o report <filename>.futil

the report has, deep in its guts, the appropriate numbers.

If you digest the report directory into an executive summary using:

fud e --from synth-files --to resource-estimate report

the executive summary again lacks the BRAM numbers.

So: it's all in there, and it's not a fud chaining issue. Some script is just failing to grab and display the BRAM numbers.

@anshumanmohan
Copy link
Contributor Author

cc @polybeandip in case you have anything to add!

@anshumanmohan
Copy link
Contributor Author

Heh I have tried to give this issue an appropriate label, but nothing seems to fit. Sorry Rachit, I know those are important

@polybeandip
Copy link
Collaborator

polybeandip commented Sep 24, 2024

Not much to add from me!

I guess in case anyone wants to tackle this issue, I think the function to be tweaked is place_and_route_extract in extract.py. Not fully sure though

@rachitnigam
Copy link
Contributor

Yup, you need to find the right table using the parser’s API and then extract the information!

@polybeandip
Copy link
Collaborator

Just to clarify, is this number from report/out/FutilBuild.runs/impl_1/main_utilization_placed.rpt what we want?
bram

@rachitnigam
Copy link
Contributor

Yup, looks like the right place to me. It is surprising and perhaps a little concerning that no BRAMs are used. Maybe the internal memories used in FIFOs are not getting mapped correctly?

OTOH, John Demme did mention that LUTRAMs often get used to map FIFOs...

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

3 participants