open-source-silicon.dev

image.png

Hello, all.
I have a problem on using Openlane to synthesize and make gds from verilog code of combinational logic
As shown below, I configured .json file and ran openlane, but error happend.
How can I solve it?

<@U04TWKZ0JSU> It maybe that the default synthesized size is too small.
If you don’t want to set an explicit size, maybe a lower utilization will work. (default is 50)
```"FP_CORE_UTIL": 10,```

<@U017X0NM2E7> Thank you! it works!
After generating, I viewd layout as below. but it seems to be large due to distance between pins(left and right)
I modifed some variables in config.json but effectless.
Can you tell me an advice?

<@U04TWKZ0JSU> using `FP_PIN_ORDER_CFG` causes the pins to be distributed evenly along a side. There are a few things you can do to skip slots, but you’ll have to look through the documentation/code. Another way to handle pins is to define them in a def file. This is what `user_project_wrapper` does so that the pins are always in the expected location.

As far as your example above, I think the `DIE_AREA` solved the original problem, not the `FP_CORE_UTIL` like I suggested.

See `FP_PIN_ORDER_CFG` and `FP_DEF_TEMPLATE` <https://github.com/The-OpenROAD-Project/OpenLane/blob/master/docs/source/reference/configuration.md|here>.

<@U017X0NM2E7>
to make smaller,  distance btw to pins needs to be short, so I set "FP_PDN_VOFFSET" and "FP_PDN_HOFFSET" as 3 but effectless.
Why openlane set the wafer size bigger than actual chip size?
It will be better that 1,2 marked in layout will be less

I think the FP_PDN variables only affect the power nets. To change the input/output pin locations, look into the pin_order.cfg options. 

Thank you. I resized core and die area c by configuring variables.

<@U04TWKZ0JSU> Looks like the pins are distributed evenly over each side. From the <https://github.com/The-OpenROAD-Project/OpenLane/blob/master/docs/source/reference/configuration.md|configuration variable explanation>
```Points to the pin order configuration file to set the pins in specific directions (S, W, E, N). If not set, then the IO pins will be placed based on one of the other methods depending on the rest of the configurations. 
$&lt;number&gt; i.e. $1 can be used to place a virtual pin where &lt;number&gt; is the count of virtual pins. This can create separation between pins. 
You can also use @min_distance=&lt;number&gt; i.e. @min_distance=0.8 to set preferred min distance between pins in a specific direction. 
See spm configuration file as an example.
(Default: None)```
<https://github.com/The-OpenROAD-Project/OpenLane/blob/master/designs/spm/pin_order.cfg|Here’s the example> mentioned above.

In your case, this would add dummy pins above and below to push the real pins more towards the middlle.
```#E
$5
*
$5```