is the .csv in the regression results not valid?
# openlane
m
is the .csv in the regression results not valid?
a
They are, which file are you copying exactly?
Also, I'd advise updating openlane to
master
and using the rc5 tag.
Copy code
git pull
git checkout rc5
and then rebuild. Magic had an issue with flagging false metal hole violations that was fixed sometime last week, so updating openlane to latest rc5 would include that magic version, just in case these spikes you're seeing are false errors.
m
ok
any clues on what --pdk or --standard-cell-library should be set to?
you said: They are, which file are you copying exactly?
I'm just iterating over fp_core_util, then opening the csv file, finding one with no drc, and copying that one number into my config.tcl
a
usually we follow this structure: general configs exist inside https://github.com/efabless/openlane/blob/master/designs/spm/config.tcl and then pdk specific configs are inside another file https://github.com/efabless/openlane/blob/master/designs/spm/sky130A_sky130_fd_sc_hd_config.tcl so the pdk is
sky130A
and the scl is
sky130_fd_sc_hd
m
so I really can't see how I end up with so many drc errors after getting a good run
a
So you're iterating over FP_CORE_UTIL only?
Then this is probably the magic issue I mentioned above
Try updating openlane
m
yeah, there is no difference in the configs
ok
I'll update
when you say rebuild
should I run make in the top level to rebuild the pdk too?
or just make merge in ./docker_build
a
You don't have to rebuild the pdk for now.
However, things should now be stable since we moved to master of openlane and fixed a commit for open_pdks and skywater-pdk, (so rebuilding the pdk would be a good thing to do). However, let's try to know the reason for the strange behavior you're getting first and then we can update the pdk.
m
ok, that fixed it
🎉 1
thanks