Hello, I have a problem with FIXED_BBOX property in Magic. In the screenshot, there is a cell having 16100 22576 size. In Magic file I see the string FIXED_BBOX 0 0 16100 22576 but exporting the cell in GDS the abutment (in green) area is just the half. Looking into mag file I see also a line with "magscale 1 2." I suspect this has to do with the misalignment. I have no idea what messed up the layout. Can someone help me out in fixing by hand the mag file in order to correct the abutment area?

I'm not sure what happened. Magic is supposed to track the scale. The values given to FIXED_BBOX normally would be in internal units, which are units of the sky130 minimum manufacturing grid, or 5nm. That corresponds to "magscale 1 2" (which declares the relationship between internal and lambda units, where lambda units are fixed at 10nm). Anyway, if the box is half the size it should be, then just load the cell into magic and type:

property FIXED_BBOX "0 0 32200 45152"

Then save and regenerate GDS.

I'm playing with Tiny Tapeout, I think (I'm not 100% sure of that) the pipeline that validate the project checks FIXED_BBOX. If the size doesn't match the expected value, the validation test fails. For this reason I asked if it possible to fix manually setting the expected values not scaled.

Was the FIXED_BBOX value originally generated manually or by a script?

There is a template generation the initial layout setting FIXED_BBOX. The value changed at some point when I started to add my stuff.

What is the init script?

Size comes from def file.

This looks like an error in magic that I will need to investigate. It can be easily worked around; it will not happen if magic is started with the correct technology startup file (sky130A.magicrc) that it is supposed to be run with, which would scale the grid to the SkyWater 5nm manufacturing grid before the bounding box is declared and before any instances are placed. However, it appears that magic, in attempting to rescale the bounding box when it rescales the grid in response to placing the first instance, is multiplying it up by 4 and not 2, which is an error, so I will have to figure out why it does that.

magic_init_project.tcl

The

magic_init_project.tcl

is sourced from inside magic. Whether or not magic is invoked with the command-line argument for reading the startup script (

-rcfile /path/to/sky130A.magicrc

) would only be found in whatever script runs magic on the

magic_init_project.tcl

file.

I confirm the workaround you suggested worked out. I will try to apply it on my original project. I let you now when done. Thanks for helping me out.

Thanks for surfacing a bug (even though now I have to go investigate it. . . )!