I see below numbers being used as area in config.t...
# openlane
r
I see below numbers being used as area in config.tcl in RUNS area-- how does openlane estimate these number ?? set ::env(CORE_AREA) {5.52 10.88 44.16 48.96} set ::env(DIE_AREA) {0.0 0.0 50.045 60.765}
v
can you share your
config.tcl
r
set ::env(DESIGN_NAME) "ABC" set ::env(VERILOG_FILES) [glob ./designs/ABC/src/*.v ./designs/ABC/src/*.h ] set ::env(CLOCK_PERIOD) "10.000" set ::env(CLOCK_PORT) "clk" set ::env(CELL_PAD) 4 set ::env(FP_IO_MIN_DISTANCE) {0.5} set ::env(PL_BASIC_PLACEMENT) {1} set filename ./designs/$::env(DESIGN_NAME)/$::env(PDK)_$::env(STD_CELL_LIBRARY)_config.tcl if { [file exists $filename] == 1} { source $filename }
v
update
FP_CORE_UTIL
with
30
. i.e increase die size to place pins
set ::env(FP_CORE_UTIL) 30
There many ways to fix this issue. You can reduce default value of
set ::env(FP_IO_MIN_DISTANCE) {3}
to fit all pins within default area
r
set ::env(FP_IO_MIN_DISTANCE) {0.5} - already did , but had some other issue, let me try the FP_CORE_UTIL var
v
0.5 is two low. maybe 1/2 try
Or else go with fixed die size 100x100
r
accha.... i have now given a fixed die dize of 500x500
yeah ... 500x500 seems way to high . lot of space getting wasted
image.png