This is for creating "artwork" or identifiers
m
This is for creating "artwork" or identifiers
m
I had a play with pygds, seems to work ok
But I never worked out to actually include the output in openlane
Maybe next time
I thought it might be easier to make custom cells and then hand place in the verilog
If they were just identifiers
m
Is M4 visible or would we have to use the RDL?
s
There’s a (2019) klayout script in this thread, but specific comment linked-to (2015) implies easily (manually) done via menus, like import DXF image, save-as GDS. https://www.klayout.de/forum/discussion/comment/3322/#Comment_3322
t
@Matthew Guthaus: If you want visible text or bitmap, put it on metal5, and then put fill block around it so that it isn't surrounded so closely by fill that you can't see it. Note that all projects have text identifiers in the padframe, including the eight-hex-digit project ID number.
@Matthew Guthaus: Place it in the area of the padframe if you want to make sure it isn't under a bump bond. The areas between pads along the bottom of the chip are free of circuitry and good for this purpose. The first three of these areas are being used for the project ID number, the caravel name and date, and the open source hardware logo, respectively. The rest of the bottom side of the padframe is free to use for artwork.
m
@Tim Edwards I was considering labeling memory IP to help track versions but I suppose this could just be text in the GDS since M5 and the bump bonds could block it
t
@Matthew Guthaus: For the purpose of IP version tracking, I would go ahead and put it on any metal layer---even if it is not visible, it can still be traced back to a mask, which a text entry in GDS cannot.
@Matthew Guthaus: Maybe we should make that a standard practice.