Kristaps Jurkans fa5f55e8cd feat(datasheet): automatically determine appropriate pinout table
This is determined by looking at the `pdk` key in the config. If `pdk` doesn't exist, `id` will be used (assuming that the structure of the shuttle ID follows ttX where X=[sky, ihp, gf]). If any part fails, it will fall back to `openframe_sky130`.

The pinout can also be manually controlled by setting the `datasheet_config.pinout` key in the shuttle config, and that will be used verbatim. Note that `datasheet_config.pinout` is not checked, so it *must* be exact, otherwise it will cause the datasheet build to fail.
2025-12-05 13:17:06 +00:00
2025-12-05 13:17:06 +00:00
2024-05-01 23:13:21 +03:00
2024-05-29 16:18:08 +03:00
2023-03-13 18:06:49 +01:00
2023-09-19 19:52:47 +03:00
2023-10-19 19:57:00 +03:00
2023-02-21 13:44:16 +01:00
2024-05-29 16:18:08 +03:00
2025-12-05 13:17:06 +00:00
2023-12-23 21:27:22 +02:00

Tiny Tapeout tools

Tools used mostly by the Tiny Tapeout GitHub Actions

Setup

pip install -r requirements.txt
pre-commit install

Documentation

  • checks that basic fields are present in the info.yaml
  • create a PDF data sheet for this one design
  • create SVG and PNG renders of the project's GDS

Reports

  • routing & utilisation
  • yosys warnings
  • standard cell usage and summary

Configuration

  • creates a little TCL shim that tells OpenLane where the source is and the name of the top module
  • makes sure the top module is not called 'top'
  • if you have OpenLane installed locally, then you can harden the design with --harden
S
Description
Miroir GitHub, requis par le checkout interne de TinyTapeout/tt-gds-action sur Gitea Actions
Readme Apache-2.0
9 MiB
Languages
Python 95.6%
Tcl 2.9%
Verilog 0.8%
Makefile 0.4%
Nix 0.2%
Other 0.1%