while we running caravel_user_project_analog we g...
# shuttle-precheck
s
while we running caravel_user_project_analog we got some errors in precheck. cvc.oeb.log is attached here for reference. How i rectify this error.
m
@Saranya P U Errors or warnings? Can you share the
precheck_results/<tag>/tmp/cvc.oeb.report
?
s
It is showing error.
what abt the cvc. errors... we are not using PMOS but in cvc its there
m
Can you share
precheck_results/<tag>/tmp/cvc.errors.gz
?
s
Ok ..lll try nw and update
cvc.error
m
@Saranya P U I think you can ignore those errors. CVC does ERC rule checking and there are usually false positives on analog designs. BTW, this looks like the default
user_analog_project_wrapper
. Are you just doing a test run?
s
yes this is a test run before integrating our design...now oeb eerror is not there but having lvs error
one more thing how can we integrate our designs gds with the wrapper
image.png
m
I’m not sure how much effort you want to put into making the example project pass LVS. You’ll need to look at the
precheck_results/<tag>/tmp/lvs.report
file and modify
lvs/user_analog_project_wrapper/lvs_config.json
accordingly. To integrate into the
user_analog_project_wrapper
, I’d start with
user_analog_project_wrapper_empty
, rename it to
user_analog_project_wrapper
, place your macro in there and connect the pins. Save the final design to gds and submit to efabless. This might help.
s
Thank you very much for your valuable suggestions.
👍 1
Actually we have no idea how to integrate our gds into user_analog_project_empty . Now we are trying to merge these file in kalyout ,is it a proper way..? or any other way is there.? In magic is it possible , how it can be done.?
m
How did you create the original gds? I think klayout might be easier, but that’s probably a personal preference.
s
Ok. Thank you.
v
@Saranya P U @Mitch Bailey Following steps can be used to integrate your layout inside caravan wrapper layout in magic : • Instantiate your magic layout inside
caravel_user_project_analog/mag/user_analog_project_wrapper.mag
• Manually connect pins of your user layout to pins of wrapper layout • Instantiate user design symbol in schematic
xschem/user_analog_project_wrapper.sch
and export its netlist as
xschem/user_analog_project_wrapper.spice
. During export netlist, select following option in xschem
"LVS Netlist: top level is .subckt"
👍 1
m
And copy that netlist to the
netgen
folder so the precheck consistency check passes.
v
Here are remaining steps in sequence. @Mitch Bailey Please complete if missing any. • Run spice extraction on top level layout
mag/user_analog_project_wrapper.mag
to generate layout netlist
mag/user_analog_project_wrapper.spice
for LVS • Copy this
mag/user_analog_project_wrapper.spice
to
netgen/user_analog_project_wrapper.spice
for running LVS using
netgen/run_lvs.sh
script. • Export GDS for
mag/user_analog_project_wrapper.mag
layout to
/gds/user_analog_project_wrapper.gds
m
@vks copying
mag/user_analog_project_wrapper.spice
to
netgen/user_analog_project_wrapper.spice
doesn’t really do anything besides allowing the precheck consistency check to pass. The
xschem/user_analog_project_wrapper.spice
file, if available, should probably be used instead.
👍 1
s
Ok. We are working on this. Will be moving on to LVS check after the integartion to wrapper is complete.
👍 1