Fixes for the multi power domain generation, custom IO placement, and diode insertion strategy 4 #609
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
write_powered_def.py
assumed that the default vdd and gnd nets always exist at index 0. This isn't always the case because the nets are ordered differently in the def file. This PR fixes the issue by enforcing the index of the default power and ground net (the default power domain is assumed to be the first net specified by::env(VDD_NETS)
and::env(GND_NETS)
).FP_PDN_ENABLE_MACROS_GRID
will either enable or disable connecting internal macros to power.FP_PDN_MACRO_HOOKS
gives the ability to specify explicit power connections for internal macros. It is useful when the design has multiple power domains. For example,set ::env(FP_PDN_MACRO_HOOKS) "
mprj vccd1 vssd1"
will connect macro with instance name
mprj
to the power domain ofvccd1
andvssd1
. This depends on Update common_pdn.tcl RTimothyEdwards/open_pdks#161place_diodes.py
to remove the dependency on thenew_int
API which is no longer available in openroad.