<@U017X0NM2E7> <@U016EM8L91B> I'm extracting my te...
# lvs
y
@Mitch Bailey @Tim Edwards I'm extracting my test.gds which contains two instances inside, if I extract two instances separately, there wouldn't be any
VSUBS
ports in their spice files and the lvs check passed for both. While if I just put them (bgr_final, bgr_gen7) together even without any connection in
test.gds
and get the
test.spice
(extracted from layout test.gds), there would always be some weird VSUBS ports, and this leads to the lvs mismatch. I attached the test.gds, test.spice, my source netlist test_source.spice (two instances bgr_final_0, bgr_gen8_0; name changes a bit from layout). After debugging, I still have no idea about the causation of the auto-generated VSUBS port. Looking forwards to your advice! My guess is this somehow relates to the psubstrate connection, as all VSUBS ports only adds in psubstrate-(should) to-GND devices.
I tried to run
netgen -batch lvs "test.spice bgr_gen7" "test_source.spice bgr_gen8_0" xxx/PDKs/open_pdks_1.0.313/sky130/sky130A/libs.tech/netgen/sky130A_setup.tcl lvs_results.log
while got this lvs error:
t
@Yueting Li: I just did an extraction from the posted test.gds and I get the common substrate VSUBS in the netlist. What version of magic are you using?
y
@Tim Edwards I used magic 8.3.285, I got VSUBS in
test.spice
as well, what does common VSUBS mean?
@Mitch Bailey @Tim Edwards do you know how to avoid this issue? My new VSUBS port actually lead to LVS mismatches
m
What Tim was saying is that when extracted with the latest version of magic, the VSS and VSUBS nets are connected. Can you try with the current magic version?
y
Thanks Mitch, I'll update the magic version and try again!