-
Notifications
You must be signed in to change notification settings - Fork 4
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
Rail Analysis (EM/IR drop) #58
Conversation
… for ASAP7 first)
…nets from set_rail_analysis_config sets a constant supply voltage for subsequent power analysis regardless of view
Not that it would necessarily need to be included in this PR, but do you think it would be useful to generate an Ah, just saw the TODO for future PRs, so that's covered already! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, comments were resolved. We just need to make sure to track the remaining TODOs.
Added ability to characterize technology (stdcells) library and macros for EM + IR drop analysis (both static + dynamic).
Some notes:
init_technology
step creates these once for the technology (stdcells) and for all macros (given invlsi.inputs.extra_libraries
), unless the list of extra libraries has changed.static_rail
andactive_rail
steps.set_pg_nets
fromset_rail_analysis_config
overrides the supply voltage for subsequent power analysis.read_spef
command was fixed--it was erroring out because the corner/file pairing wasn't done properly.Fixes needed before this PR can be merged:
reset_design
errors out) orinit_design
to be called first?read_spef
sequence relying on fact that the list of spefs was written in the[setup, hold]
order by Innovus pluginTODOs potentially in other PRs:
power.inputs.database
from Innovusreport_irdrop_regions
, the highest run number in the rail analysis output dir needs to be parsed and incremented in order to reference the correct database.