Pad Cell Generator: Difference between revisions
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
Please look at our reference technology folders like the design rule constraints and parameters, for which we introduced a somewhat standardized format with the advent of our [[Danube River]] test wafer generator. | Please look at our reference technology folders like the design rule constraints and parameters, for which we introduced a somewhat standardized format with the advent of our [[Danube River]] test wafer generator. | ||
https://github.com/thesourcerer8/StdCellLib/tree/master/Tech.GF180MCU<blockquote>Note: | https://github.com/thesourcerer8/StdCellLib/tree/master/Tech.GF180MCU<blockquote>Note: We are still waiting for the NLNet grant, so there isn't any code to speak of yet for this tool, but the general use of the tool will be pretty much the same as for generating the standard logic cell lib and the Danube River test structures for characterizing your target process.</blockquote>First clone the repository | ||
git clone https://gitlab.libresilicon.com/leviathan/PadCellGenerator.git | git clone https://gitlab.libresilicon.com/leviathan/PadCellGenerator.git | ||
cd PadCellGenerator | cd PadCellGenerator | ||
Then you fetch the Dockerimage with all the LibreSilicon tools preinstalled, just as with DanubeRiver and the Standard Logic Cell generator library: | Then you fetch the Dockerimage with all the LibreSilicon tools preinstalled, just as with DanubeRiver and the Standard Logic Cell generator library: | ||
docker pull leviathanch/libresilicon-tools:latest | docker pull leviathanch/libresilicon-tools:latest | ||
Then you've got to start the Docker container and build the pad cells for your specific process | Then you've got to start the Docker container and build the pad cells for your specific process | ||
docker run -v `pwd`:/work -it leviathanch/libresilicon-tools | docker run -v `pwd`:/work -it leviathanch/libresilicon-tools | ||
After that there's some make commands telling my Python scripts, which I haven't pushed yet, what to do, as soon as they can actually do it... when depends on NLNet. | |||
For now it's just Perl scripts and some loose Magic files | |||
Revision as of 17:48, 30 November 2024
The LibreSilicon Pad Cell Generator is an extension of the Standard Logic Cell Library generator, which besides the driver logic also dynamically generates the mixed signal parts needed for over current and static discharge protection and providing the currents needed for doing useful things with an actual physical chip, like driving an LED or a small motor.
The Pad Cell Generator has the task of generating a Pad Cell for generating a pad frame for taping out a circuit with any given set of design rules for any given process.
Just as with the Standard Cell Generator, you need to provide the Pad Cell Generator the appropriate configuration telling it about all the design constraints and mixed signal characteristics of the process you are targetting.
Please look at our reference technology folders like the design rule constraints and parameters, for which we introduced a somewhat standardized format with the advent of our Danube River test wafer generator.
https://github.com/thesourcerer8/StdCellLib/tree/master/Tech.GF180MCU
Note: We are still waiting for the NLNet grant, so there isn't any code to speak of yet for this tool, but the general use of the tool will be pretty much the same as for generating the standard logic cell lib and the Danube River test structures for characterizing your target process.
First clone the repository
git clone https://gitlab.libresilicon.com/leviathan/PadCellGenerator.git cd PadCellGenerator
Then you fetch the Dockerimage with all the LibreSilicon tools preinstalled, just as with DanubeRiver and the Standard Logic Cell generator library:
docker pull leviathanch/libresilicon-tools:latest
Then you've got to start the Docker container and build the pad cells for your specific process
docker run -v `pwd`:/work -it leviathanch/libresilicon-tools
After that there's some make commands telling my Python scripts, which I haven't pushed yet, what to do, as soon as they can actually do it... when depends on NLNet.
For now it's just Perl scripts and some loose Magic files