Pepijn de Vos
06/14/2022, 11:26 AMArman Avetisyan
06/14/2022, 12:27 PMPepijn de Vos
06/14/2022, 12:29 PMprBoundary.boundary
Arman Avetisyan
06/14/2022, 12:30 PMArman Avetisyan
06/14/2022, 12:32 PMArman Avetisyan
06/14/2022, 12:33 PMPepijn de Vos
06/14/2022, 12:35 PMPepijn de Vos
06/14/2022, 12:35 PMPepijn de Vos
06/14/2022, 12:38 PMMitch Bailey
06/14/2022, 12:42 PMPepijn de Vos
06/14/2022, 12:43 PMPepijn de Vos
06/14/2022, 12:44 PMMitch Bailey
06/14/2022, 12:52 PMPepijn de Vos
06/14/2022, 12:53 PMMitch Bailey
06/14/2022, 12:54 PMPepijn de Vos
06/14/2022, 12:55 PMMitch Bailey
06/14/2022, 12:56 PMHarald Pretl
06/14/2022, 6:00 PMmetal1
that draws where metal will be later), and quite a few are helper layers used by the one or the other tool e.g. help to recognise resistors during layout extraction. And still others are helper layers for mask generation, like suppressing automatic fill in a certain area, for force a fill in an area. Since there are many mask layers (30–70), plus many helper layers, this gives a lot of different layers.
• magic
is still more special: Instead of creating a device by an intersetion of two or more other layers, it uses yet a another layer in this intersection area (uff).
• Since there are now so many layers, layout engineers switch visibility A LOT, means turning on or off the layers that are needed. Since you switch visibility constantly, people are definining macros for that, so that you have that at a fingerstroke.
• I have defined a few helpful ones here: https://github.com/hpretl/iic-osic/blob/main/iic-magic-bindkeys
• Define your own macros in magic similar to this: macro 0 "see no * ; see locali ; see mcon"
Makes sense?Pepijn de Vos
06/14/2022, 6:03 PM