How djuara-rbz/tt_spi_pwm works
[Design Sources] → [Build System] → [Output Artifacts]
Detailed Component Breakdown
A. Design Sources Layer (Left Side):
• edge_detector.v
• pwm.v
• spi_own_clock.v
• spi_sampled.v
• project.v (mark as top module)
• Configuration container:
• config.tcl
• info.yaml
B. Build System Layer (Middle):
• OpenLane Build Flow container
• GitHub Actions Workflows container showing:
• GDS workflow
• Documentation workflow
• Test workflow
C. Output Artifacts Layer (Right Side):
• ASIC Layout (GDS) container
• Documentation container
• Test Results container
Connections and Data Flow
• How source files are compiled together
• How configuration files influence the build
• The flow through the OpenLane toolchain
• Test verification paths
• Documentation generation paths
Additional Elements
• External dependencies (OpenLane)
• TinyTapeout platform integration
• Testing framework
• The hierarchical nature of the Verilog design
• The automated build and verification process
• The integration with TinyTapeout's manufacturing flow
Key Relationships to Highlight:
The final ASIC generation pipeline
• Symbols for files, processes, and external tools
• Build/verification stages with appropriate markers
Level of Detail:
• Timing or sequence information where relevant