Siemens EDA Tool Flow for NSF Chipshub
Overview
In this project, students implement a complete digital RTL-to-GDSII flow using the Siemens EDA toolset and the open-source SkyWater SKY130 process design kit (PDK), hosted on NSF ChipsHub. Starting from a provided reference design, students install and configure the tools and PDK, write and verify the TCL scripts that drive each stage of the flow, and carry the design from RTL through signoff to a DRC- and LVS-clean GDSII layout. The emphasis is on the flow itself: understanding what each tool consumes and produces, how stages hand off to one another, and how to script the flow so it is repeatable and debuggable.
Learning Objectives
By the end of the project, students will be able to:
- Install and configure the Siemens EDA tools and the SKY130 PDK in the ChipsHub environment, including license setup, environment variables, and PDK collateral (Liberty, LEF, technology files, and rule decks).
- Write modular, parameterized TCL scripts for each stage of the RTL-to-GDSII flow.
- Verify their TCL scripts by checking stage outputs, logs, and reports against expected results, and by testing scripts against more than one design.
- Run functional verification, synthesis, place-and-route, static timing analysis, and physical verification, and interpret the reports each produces.
- Diagnose and resolve common flow failures such as timing violations, congestion, DRC errors, and LVS mismatches.
Completion of a flow in the Chipshub comes with a DOI, which means you will automatically get a publication.
Project Phases
- Environment setup. Install and configure the Siemens tools and the SKY130 PDK on ChipsHub. Deliverable: a documented setup script and a short verification checklist showing each tool launches and reads the PDK correctly.
- Front-end verification. Simulate the reference RTL in Questa using a scripted TCL flow. Deliverable: passing testbench results and the simulation script.
- Synthesis. Write the TCL synthesis script, including SDC timing constraints. Deliverable: gate-level netlist plus area and timing reports.
- Physical implementation. Script floorplanning, power planning, placement, clock tree synthesis, and routing in Aprisa. Deliverable: routed design with timing closed at the target clock.
- Signoff. Run gate-level simulation, DRC, and LVS. Deliverable: clean DRC/LVS reports and the final GDSII.
- Flow integration. Combine the stage scripts into a single, parameterized flow and run it on a second design to show it is reusable. Deliverable: the complete flow repository and a short technical report.
TCL Scripting and Verification
TCL is the thread that ties the project together. Students write scripts that are modular (one script per stage), parameterized (design name, clock period, and paths are variables, not hard-coded values), and self-checking. Each script must check its own results, such as confirming that output files exist, that no errors appear in the log, and that timing slack and DRC counts meet thresholds, and must fail loudly when they do not. Running the finished flow unchanged on a second design is the final test of whether the scripts are correct and general.
Deliverables and Assessment
- Environment setup script and checklist
- Stage-by-stage TCL scripts with inline documentation
- Reports from each stage (simulation, synthesis, timing, power, DRC, LVS)
- Final DRC- and LVS-clean GDSII
- Integrated flow run on a second design