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

Missing area metrics for ASIC synthesis #1002

Closed
thomasdingemanse opened this issue Jun 12, 2024 · 2 comments
Closed

Missing area metrics for ASIC synthesis #1002

thomasdingemanse opened this issue Jun 12, 2024 · 2 comments
Assignees
Labels
Component:Doc For issues in the Documentation (e.g. for README.md files) Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system

Comments

@thomasdingemanse
Copy link

thomasdingemanse commented Jun 12, 2024

Missing area metrics for ASIC synthesis

The FPGA synthesis section of the CV32E40P User Manual says the following about the area:

The core occupies an area of about XX kGE. With the FPU, the area increases to about XX kGE (XX kGE FPU, XX kGE additional register file).

It seems like XX is meant to be a placeholder for specific numbers. I'd be happy to help, but I'm not sure how the core should be synthesized for ASIC to get accurate area metrics. Is there an example workflow I could follow or a synthesis script I could use?

Component

Component:Doc

Steps to Reproduce

Not applicable.

@pascalgouedo pascalgouedo self-assigned this Jun 12, 2024
@pascalgouedo pascalgouedo added Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system Component:Doc For issues in the Documentation (e.g. for README.md files) labels Jun 12, 2024
@pascalgouedo
Copy link

pascalgouedo commented Jun 12, 2024

Hi @thomasdingemanse ,
Yes ASIC synthesis section contains place-holders for CPU and FPU size numbers in KGE unit. All those sentences will be replaced by new text explaining the synthesis context and some new tables.
We are collecting the numbers right now.

No workflow is available as the Core is available as a soft IP.
An IOs constraint file is given as an example in constraints directory.

@pascalgouedo
Copy link

PR #1020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component:Doc For issues in the Documentation (e.g. for README.md files) Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system
Projects
None yet
Development

No branches or pull requests

2 participants