How sukanyasmeher/sfal-vsd works
Project type and purpose
• This repository “sfal-vsd” is not a web app, but an educational hardware-design tutorial. It walks a user through RTL design in Verilog, open-source synthesis/simulation (Icarus/GTKWave/Yosys), then Synopsys flows (Design Compiler, DFT, STA, ICC2) and finally PVT-corner timing analysis.
File structure
• Top-level docs (README.md, tutorials.md, AdvancedPhysicalDesign.md) describe Day-by-Day labs.
• old_sky130_lib holds a legacy copy of the SkyWater 130nm PDK.
• No code folders—source files (Verilog, TCL, SDC) are referenced in the tutorials.
• Assets (images) are embedded in README to illustrate tool outputs.
README for technical stack
• Tools: Iverilog, GTKWave (simulation), Yosys (open-source synthesis), Synopsys DC (logic synthesis), DFT compiler, PrimeTime (STA), ICC2 (physical compile).
• PDKs: sky130_fd_sc_hd (multiple PVT libs), AVSD DAC & PLL libraries.
• Workflows: RTL → Synthesis → Gate-Level Simulation → DFT → STA → PVT analyses.
Main components
• Verilog RTL (lab source files & testbenches)
• PDK Libraries folder (old_sky130_lib + downloaded .lib files)
• Iverilog → .vcd waveforms → GTKWave
• Yosys + sky130 PDK → synthesized netlist → GLS with primitives and sky130 cells
• Synopsys Design Compiler + SDC constraints → gate-level netlist
• DFT Compiler → scan-enabled netlist → scan chains
• STA (PrimeTime) using timing .db libraries → slack reports
• ICC2 (GUI) for physical database
d. Outputs (rightmost):
• Waveform screenshots (GTKWave, GLS)
• Netlist files (.v, _net.v, _net_sdc.v)
• Reports: QoR, timing (setup/hold), PVT slack graphs
• Lab deliverables (labs Day0–Day14)
Relationships & data flow
• Verilog RTL + PDK LIBS feed both open-source and Synopsys flows in parallel.
• Open-source flow is for early validation (Day0–Day3).
• Design Compiler flow takes the same RTL + SDC → netlist → post-synth simu.
• DFT and STA operate on the synthesized netlist, producing test‐patterns and timing analyses.
• ICC2 can import the netlist + DEF for backend placement/routing (Day5–Day6).
Architectural patterns & principles
• Linear pipeline: write RTL → simulate → synthesize → verify → analyze → physically compile.
• Modular structure: each lab/day is an independent stage/component.
• Reuse of PDK libs via link_library/read_liberty in DC and read_lib in lc_shell.
• Separation of concerns: open-source PoC vs. production Synopsys flows.
• A footnote listing key commands (read_verilog, synth −top, create_clock, read_sdc, compile_ultra, report_timing).