Hello all, I created a new project to use the repo...
# shuttle
j
Hello all, I created a new project to use the repository from my MPW4 analog project, which could pass the precheck. Unfortunately, this time it fails due to "Klayout FEOL" error. Any idea if anything changed since then? It's exatcly the same project. Or in case it's an issue, does anyone know how to solve it? cc @User @User or anyone else who could help! thx! Jorge
m
can you check what tag your local precheck is on? does it fail on the efabless platform?
j
@User yes, on the platform, the new created project is this one (not sure if you can see any report from your side): https://platform.efabless.com/projects/797 how can I check the local prcheck tag?
@User here a screenshot of the error
@User I'm using exactly the same github link I used for MPW4 (without updating any tags), do you think this could be a problem? if so, what/how do you recommend to update for compatibility?
j
Jorge - there are rules for nsd and psd that were missed for MPW-4. these need to be addressed for projects on MPW-5 onward.
@User
m
what would the process be?
get the new drc deck and edit your design in klayout or magic until it passes?
👍 1
j
indeed, I'm wondering @User
can't I just change the values in the Magic rules?
hello @User , I continue the coversation in this thread OK, so what I see in Klayout is that magic somehow seems to be adding some poligons to merge regions around different pdiff/ndiff regions, and these are not respecting the psd/nsd rules... any advice @User @User @User? I really have no idea how to solve this
t
@User: Magic will add polygons where it sees DRC violations on implant region geometry; usually this works but it is possible to have layout which looks like it should work but for which there is no solution to place the implants without generating errors. It's necessary to use the klayout checks (or magic's sky130-GDS.tech tech file) to check for these errors and do something to mitigate them. How many such errors are you seeing reported?
j
@User OK, I see... I see 14 errors in Klayout, but since psd and nsd are layer which cannot be seen in Magic, I'm not sure how to solve it, I need to extend the psd and nsd regions I guess
m
Can you edit in klayout?
j
@User not sure, I'll install it and see (I've used it for the first time this morning for viewing, never edited on it)... should I try to directly modify the gds?
m
Adding nsdm/psdm directly. in klayout may be the easiest thing to do at this stage. Other people who have run into the same problem, moved the cells in the layout so that magic generated gds with no errors, but that's trial and error.
j
@User ouf that sounds like a lot of work, mostly because it requires to loop between magic, precheck and klayout... I'll see what I can do, but I'm wondering if it's ok to do this directly on the gds file, do you know?
m
I believe others have modified the gds via klayout to fix drc errors, but I haven't done it myself.
j
@User OK, thanks for the info!
t
The
MASKHINTS_PSDM
and
MASKHINTS_NSDM
properties can be used as a last resort to specify geometry for the NSDM and PSDM layers; set the property to be equal to a string of one or more rectangles in magic's internal coordinates in the form
"llx0 lly0 urx0 ury0 llx1 lly1 urx1 urx2 ..."
. That keeps the corrections upstream and avoids having to do back-end fixes in klayout.
👍 1
j
@User I don't get it, how can exactly MASKHINTS_P/NSDM be used? I couldn't find any documentation online
t
1. Place the cursor box over the area where you want the layer, e.g., NSDM, to be defined 2. Use the
box
command to find the four coordinates of the cursor box 3. Type the command
property MASKHINTS_NSDM "
(+ the four coordinates +) `"`; e.g.,
property MASKHINTS_NSDM 110 60 120 72
. 4. If you want to see the resulting layer, use the command
cif see NSDM
(which can be used to view the layer at any time, not just after using the mask-hints property method).