Mitch Bailey
10/11/2023, 5:08 PM"FP_PDN_MACRO_HOOKS": "lane0 vdda1 GND_GPIO vdda1 GND_GPIO",
"FP_PDN_MACRO_HOOKS": "lane0 vdda1 GND_GPIO vssa1 GND_GPIO",
magic adds _uq?
suffices to nets that have the same name but are not connected.
FP_PDN_MACRO_HOOKS
and let us know if you have other problems.JC
10/11/2023, 6:09 PMmodule blackbox_test_5(
`ifdef USE_POWER_PINS
inout vdda1,
inout GND_GPIO_top,
`endif
.
.
.
bitsixtyfour_EESPFAL_switch_2 lane0 (
`ifdef USE_POWER_PINS
.vdda1(vdda1),
.GND_GPIO(GND_GPIO_top),
`endif
Based on the top verilog file and the macro's pins I should be doing the following "FP_PDN_MACRO_HOOKS": "lane0 vdda1 GND_GPIO_top vdda1 GND_GPIO"
. But openlane is saying it can't find the power pins.
Looking at the 11-global.odb
, should I define the pins out of the way for the pdn lines?JC
10/11/2023, 9:22 PMMitch Bailey
10/11/2023, 11:44 PM<instance_name> <vdd_net> <gnd_net> <vdd_pin> <gnd_pin>
So
"VDD_NETS": "vdda1",
"GND_NETS": "GND_GPIO",
"SYNTH_USE_PG_PINS_DEFINES": "USE_POWER_PINS",
"FP_PDN_MACRO_HOOKS": "lane0 vdda1 GND_GPIO vdda1 GND_GPIO",
should be good.
Check out the vdda1 text in your design to see if there are multiple texts that aren’t connected. If your macro is close to a border, there may be met5 that is not connected but has the same label. (I have seen multiple texts that are connected, but still get the _uq?
suffix. This shouldn’t be and I believe @Tim Edwards fixed it. What version of magic are you using?)JC
10/11/2023, 11:51 PMJC
10/12/2023, 12:05 AMPDN_MACRO_HOOKS
line and see what happens