-
Notifications
You must be signed in to change notification settings - Fork 52
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
Comments
cc @polybeandip in case you have anything to add! |
Heh I have tried to give this issue an appropriate label, but nothing seems to fit. Sorry Rachit, I know those are important |
Not much to add from me! I guess in case anyone wants to tackle this issue, I think the function to be tweaked is |
Yup, you need to find the right table using the parser’s API and then extract the information! |
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... |
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:
makes no mention of BRAMs. If you generate the actual report using:
the report has, deep in its guts, the appropriate numbers.
If you digest the
report
directory into an executive summary using: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.The text was updated successfully, but these errors were encountered: