mirror of
https://github.com/TinyTapeout/tt-support-tools.git
synced 2026-11-02 20:26:10 +01:00
Joni Hendrickson
01d5d2814f
Right now, running `tt_fpga.py --project-dir example/<projectname> harden` will fail if previously, `tt_fpga.py harden` was ran against a project in the root folder. This is because the `_tt_fpga_top.v` file is always read from `src/_tt_fpga_top.v`, even though it's generated in the proper --project-dir location. Similar problem affects the `configure` command, where it looks for the bitstream in `build/<name>.bin` relative to the current dir even with `--project-dir` set. Commit prepends the source_dir from `--project-dir` in the appropriate places such that it's used for both harden and configure. Tested by observing that running the following commands in sequence now succeeds against one of my projects: - tt_fpga.py harden - tt_fpga.py --project-dir examples/tt_um_vga_example_gamepad harden - tt_fpga.py --project-dir examples/tt_um_vga_example_gamepad configure --upload --port /dev/ttyACM0
Tiny Tapeout tools
Tools used mostly by the Tiny Tapeout GitHub Actions
Setup
pip install -r requirements.txt
pre-commit install
On macOS, some third-party libraries are required:
brew install libpng qhull cairo
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 LibreLane where the source is and the name of the top module
- makes sure the top module is not called 'top'
- if you have LibreLane installed locally, then you can harden the design with --harden