mirror of
https://github.com/retroSoC/retroSoC.git
synced 2026-11-04 22:32:36 +00:00
maksyuki
bab01352f8
- Added support for optional files in GDS generation to handle legacy layouts. - Introduced macro-level LVS/ERC processing to improve verification of hard macros. - Updated STA scripts to adopt PrimeTime analysis settings from legacy flows. - Enhanced synthesis settings to align with CX55 legacy flow, including clock gating and area optimization. - Improved reporting functions to include detailed synthesis summaries and area metrics. - Updated package generation script to support both TINY and MINI SOC configurations. - Added comprehensive tests for ECO translation, timing contract generation, and constraint handling. - Ensured compatibility with new timing contract formats and enhanced error handling for domain drift.
1.7 KiB
1.7 KiB
Physical Design
This directory owns physical-design integration, managed technology inputs, smoke implementation-flow sources, and the self-developed commercial-flow drivers.
pdk/contains the locked PDK setup helpers and managed PDK checkouts.smoke/syn/contains Yosys synthesis and source-export integration.smoke/sta/contains OpenSTA constraints and timing integration.librelane/contains the open-source IHP130 implementation flows, organized per product line:librelane/mini/(core hardening and full-chip pad ring) andlibrelane/tiny/(Tiny full-chip pad ring).ecc/contains the ICS55 padless-core adapter and the official ECClatestinstaller entrypoint. Installation does not qualify physical-flow compatibility.commercial/contains licensed-tool orchestration and flow logic for the ICS55 implementation flow, parameterized per product line (SOC=MINIandSOC=TINY, extensible to future series). PDKs, foundry decks, commercial libraries, site configuration, and results remain outside Git; see commercial/README.md for the three-layer configuration model and stage graph.sdf/, when supplied by an implementation flow, contains post-layout netlist and SDF collateral consumed by post-layout simulation.
The local Makefile is reserved for implementation flows that require the selected PDK, technology collateral, and often site-specific tools.
Generated layout, report, and database outputs must remain outside tracked source paths. Treat PDK-dependent physical-design results as toolchain-specific evidence and record the selected profile, PDK, and validation command when handing off a change. See Engineering Workflow.