File size: 2,632 Bytes
caddd62 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 | ## Background
This is level 4 of 5 and continues the work of the earlier levels. The new files for this level are in `workspace/t4/`. The records from the start are in `workspace/t1/`, and the earlier results are in `workspace/t1/results/` to `workspace/t3/results/`.
## Task
Subject: switching our backend to ORFS
Hi,
I would like to move the backend onto OpenROAD-flow-scripts to reduce our mirror maintenance. I have fetched the SG13G2 platform and example configurations under OpenROAD-flow-scripts, along with mpw-shuttles/TO_Sep2025 and the IHP release views under pdk-releases. The picosoc_ac_controller submission is the example behind my proposal; my notes are in tapeout-2026/notes.
Mira wants a concrete integration we can try before agreeing. Carry your re-pin and memory configuration into an ORFS project configuration for Croc. Keep the sign-off coverage from your IO review, and the memory has to keep working the way it did after your re-pin. Check the resulting library and physical-view coverage and demonstrate memory operation with the models the configuration selects.
Check the mapped read budget under the delivered ORFS configuration against your re-pin qualification, and account for any change.
Alongside that, reconcile the picosoc team's published path timing with the candidate library generations, including the uncertainty in its printed values and a consistent account of the path operating conditions. Quantify whether those path results transfer to our re-pinned libraries as the path operating conditions change, and assess what the SRAM evidence establishes. Use the library and timing work you have already done.
Please put the review, validation results and recommendation in workspace/t4/results/orfs_review.xlsx, and the configuration change as a patch against the shared workspace in workspace/t4/results/platform.patch.txt. We need to distinguish adopting the ORFS scripts from adopting their packaged libraries.
Jonas
## Input
- `workspace/t1/`: the records supplied with the work (`croc/`, `tapeout-2026/`).
- `workspace/t2/`: the files that came with level t2 (`tapeout-2026/`, `tapeout-archive/`).
- `workspace/t3/`: the files that came with level t3 (`IHP-Open-PDK/`, `tapeout-2026/`).
- `workspace/t4/`: the files that came with level t4 (`OpenROAD-flow-scripts/`, `mpw-shuttles/`, `pdk-releases/`, `tapeout-2026/`).
- `workspace/t1/results/`: the results of level t1.
- `workspace/t2/results/`: the results of level t2.
- `workspace/t3/results/`: the results of level t3.
## Output
- `workspace/t4/results/orfs_review.xlsx`
- `workspace/t4/results/platform.patch.txt`
|