| ## Background |
|
|
| This is level 5 of 5 and continues the work of the earlier levels. The new files for this level are in `workspace/t5/`. The records from the start are in `workspace/t1/`, and the earlier results are in `workspace/t1/results/` to `workspace/t4/results/`. |
|
|
| ## Task |
|
|
| Subject: hard IP for the tapeout review |
|
|
| Hi, |
|
|
| The tapeout review is on 19 November. The panel asks what hard IP has been through a fab run before and what we are qualifying for the first time. I have fetched mpw-shuttles/TO_Nov2024 next to the September repository. Please bring this together with the MLEM and library work you have already done. |
| |
| For the standard cells eligible for our implementation after your ORFS integration and the SRAM configuration we agreed, establish which current layouts have prior use supported by these records. Compare these cells and our pad-ring cells with the released platform baseline and the submitted shuttle layouts. Where layouts differ, identify the physical changes and quantify them. Keep library lineage, submission and fabrication evidence clear enough that I can defend the claims at the review. |
| |
| Turn the qualification findings into a reviewable final ORFS baseline, keeping the re-pin, the memory setup we agreed and the sign-off coverage from your IO review. Implement your disposition in the library eligibility or view selection, and validate the mapped memory configuration with the resulting baseline, its timing and physical-view coverage, and the memory behaviour you demonstrated before. Reconcile the mapped read timing with your earlier memory budget and the ORFS integration, accounting for the effect of your qualification disposition. Identify the risks that still need approval before implementation sign-off. |
| |
| Please send the cell comparison as workspace/t5/results/ip_lineage.csv and a short memo with the final-baseline validation as workspace/t5/results/ip_review_memo.pdf. Put the configuration change against the workspace with your earlier patches applied in workspace/t5/results/qualified_baseline.patch.txt. I need your view of what is supported, what remains unqualified and what we should do before the freeze. The preparation notes are in tapeout-2026/minutes. |
| |
| Thanks, |
| Mira |
| |
| ## 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/t5/`: the files that came with level t5 (`mpw-shuttles/`, `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. |
| - `workspace/t4/results/`: the results of level t4. |
| |
| ## Output |
| |
| - `workspace/t5/results/ip_lineage.csv` |
| - `workspace/t5/results/ip_review_memo.pdf` |
| - `workspace/t5/results/qualified_baseline.patch.txt` |
|
|
