DRC report thread for <@U016EM8L91B>
# magic
m
DRC report thread for @User
image.png
image.png
image.png
image.png
image.png
image.png
image.png
image.png
image.png
lvs errors already reported here: https://github.com/RTimothyEdwards/netgen/issues/7
image.png
So apart from the LVS error they are all the same: All nwells must contain metal-connected N+ taps (nwell.4)
t
My understanding was that those are false positives
m
yeah, was just talking to @Ahmed Ghazy and he suggested posting them here anyway
the LVS error needs looking at tho
t
Are you running DRC on the GDS or on the DEF ?
m
these reports are from runs/xxxx/logs/magic/magic.drc
if that answers the question?
t
Not really. Do you set
::env(MAGIC_DRC_USE_GDS)
?
or leave it default ?
m
default
t
ok, then it's on the GDS. (Default is
1
)
m
@Matt Venn Looks like the LVS error might be similar to the one in zipdiv. It appears to be a buffer discrepancy, but it may be something that does not make a significant difference in the final design. There was some discussion on #verification-be https://skywater-pdk.slack.com/archives/C017UA7LEUV/p1605706697015700 @Ahmed Ghazy says he's not getting the error in rc5 (develop).
@Matt Venn @tnt Quick check.
MAGIC_DRC_USE_GDS
is used in the
openlane/scripts/magic_drc.tcl
. Is this the standalone DRC script? I think the
openlane/flow.tcl
script calls
run_magic_drc
which is
located in scripts/tcl_commands/magic.tcl
and only uses the
maglef
views, AFAICT.
t
No.
run_magic_drc
from
scripts/tcl_commands/magic.tcl
invokes
magic
and tells it to run
scripts/magic_drc.tcl
m
@tnt Thanks for the quick response. So when
MAGIC_DRC_USE_GDS
is set, the
set ::env(MAGTYPE) maglef
line in
scripts/tcl_commands/magic.tcl
effectively doesn't do anything?
t
yup
AFAIU