Tom
09/01/2022, 3:52 AMOpenROAD 4a99e88667b0840531ca0096c4fa0da8f80d6cb1
This program is licensed under the BSD-3 license. See the LICENSE file for details.
Components of this program may be licensed under more restrictive licenses which must be honored.
[INFO ODB-0222] Reading LEF file: /openlane/designs/test/runs/RUN_2022.09.01_03.47.42/tmp/merged.nom.lef
[WARNING ODB-0220] WARNING (LEFPARS-2036): SOURCE statement is obsolete in version 5.6 and later.
The LEF parser will ignore this statement.
To avoid this warning in the future, remove this statement from the LEF file with version 5.6 or later. See file /openlane/designs/test/runs/RUN_2022.09.01_03.47.42/tmp/merged.nom.lef at line 930.
[INFO ODB-0223] Created 13 technology layers
[INFO ODB-0224] Created 25 technology vias
[INFO ODB-0225] Created 441 library cells
[INFO ODB-0226] Finished LEF file: /openlane/designs/test/runs/RUN_2022.09.01_03.47.42/tmp/merged.nom.lef
[INFO ODB-0127] Reading DEF file: /openlane/designs/test/runs/RUN_2022.09.01_03.47.42/results/floorplan/test.def
[INFO ODB-0128] Design: test
[INFO ODB-0130] Created 2 pins.
[INFO ODB-0131] Created 3 components and 14 component-terminals.
[INFO ODB-0133] Created 2 nets and 2 connections.
[INFO ODB-0134] Finished DEF file: /openlane/designs/test/runs/RUN_2022.09.01_03.47.42/results/floorplan/test.def
[ERROR PDN-0108] Spacing (-1.3100 um) specified for layer met4 is less than minimum spacing (0.3000 um).
Error: pdn_cfg.tcl, 123 PDN-0108
designs/test/runs/RUN_2022.09.01_03.47.42/logs/floorplan/6-pdn.log (END)
Thats the log. I created a design called test using
./flow.tcl -design test -init_design_config -add_to_designs -config_file config.tcl
And then created the following verilog file in the src folder
OpenLane Container (b6bacc9):/openlane$ cat designs/test/src/test.v
module test (
input wire in,
output wire out
);
assign out = ~in;
endmodule
OpenLane Container (b6bacc9):/openlane$
Why is open lane violating spacing rules and how do i change the config to prevent it from doing so?
Thanks in advanceArman Avetisyan
09/01/2022, 6:32 AMArman Avetisyan
09/01/2022, 6:32 AMMatt Venn
09/01/2022, 1:56 PMMatt Venn
09/01/2022, 1:56 PMTom
09/01/2022, 2:41 PM