Files
retroSoC/physical
maksyuki 3ac9e73ab9 feat: refactor tests for mailbox and environment validation
- Updated mailbox purpose tests to reflect new write order and sequence handling.
- Added tests to ensure Linux-ready values match LP contract and constants match Linux helper.
- Introduced tests to verify that offset changes do not hide stale Linux helpers.
- Enhanced environment tests to report current locked launcher and runtime versions.
- Added checks for SBT launcher presence in environment labels.
- Improved full diagram tests to validate storage geometry and RSA vector configurations.
- Expanded register tests to ensure crypto interrupt registers publish all events and lifecycle annotations preserve security boundaries.
- Modified script tools tests to include Vexii generation validation and updated workflow assertions.
2026-09-30 10:51:04 +08:00
..

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) and librelane/tiny/ (Tiny full-chip pad ring).
  • ecc/ contains the open-source ICS55 padless-core hardening flow backed by the locked ECOS Chip Compiler release.
  • commercial/ contains licensed-tool orchestration and flow logic. PDKs, foundry decks, commercial libraries, site configuration, and results remain outside Git.
  • 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.