-
Notifications
You must be signed in to change notification settings - Fork 199
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
Power estimation seems too high #242
Comments
It is a known issue that the power numbers have not been calibrated. The cell powers in the tech file are not correct. |
Hi, thank you for the response. Is it possible to obtain the power estimation in another way? |
You can run a spice simulation. These are the placeholder values for leakage: Similarly, there are estimates for capacitance used in dynamic power which might be set correctly. |
Thank you very much. With this approach, is it possible to obtain the .lib file as well? I would like to use these memories as macros in another design on OpenLane and I would like to have a complete power estimation. |
It is, but it will be slow. It'd be nice if someone can contribute new estimates for the tech file so they are correct instead. |
I didn't quite understand this last part. |
Sorry @mguthaus , in this issue it seems to me that you have the same problem as mine. I have a design on OpenLane that uses OpenRAM macros and I need to estimate the entire system power. However, to do this, it seems from this issue that a gate-level netlist is needed rather than the .lib file. Were you able to solve this problem? |
There are no gate-level netlists of SRAM macros. It must use a .lib file. |
I understand, however, it seems that OpenLane is unable to read the .lib files of the macros to calculate power, and it only works when the gate-level netlist is present. So my question is, based on this issue, how can we include the memory macro in power calculation when we only have the .lib file available? |
This would be an openlane issue. Gate level doesn't exist for any memory macro even with other tools. It doesn't use the cells from the library. Openlane should be using the .lib file for the memory macro to get the power. |
Perfect, so you're confirming that it's impossible for OpenLane to estimate the power of these memories since only the .lib file is available? |
I'm confirming that openlane should only need the lib file to estimate power. |
So, did you manage to solve this issue? |
The last comment in the thread says that I did not black box it for STA. I did need to convert the model parameters to constants to get it to work. However, I don't recall if it estimated power correctly, but it did work with timing. That issue is a year old, so I'm not sure what has changed in openlane regarding it. Again, this is an openlane issue. |
Describe the bug
![image](https://private-user-images.githubusercontent.com/142605978/333559561-1d6af79c-b7b6-4376-a679-92150b229605.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ1NjQ0OTgsIm5iZiI6MTcyNDU2NDE5OCwicGF0aCI6Ii8xNDI2MDU5NzgvMzMzNTU5NTYxLTFkNmFmNzljLWI3YjYtNDM3Ni1hNjc5LTkyMTUwYjIyOTYwNS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwODI1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDgyNVQwNTM2MzhaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1jZDhlN2U3MDc2MDI2YTI1OGU3M2M3YzcyNDgwODU1ZjVhZmQwNTgxOTBlMjk5YjliMWM4NWY1ZmUwZDNiYjZjJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.RuT58FNxYQMuUKwp2jH00y1kf1oes9qo5C9-fKM4oJE)
I ran the sky130_sram_1rw_tiny example and the power report shows hundreds of watts, which seems wrong. Could this be a bug? How can I solve it?
Version
1.2.48
To Reproduce
cd OpenRAM/macros
make sky130_sram_1rw_tiny
The text was updated successfully, but these errors were encountered: