We just released a new command that will move your 800_postroute_finishing directory to a 700 eco dir. You can then use this new directory as the eco dir.
When you rerun 800, it "should" do almost nothing since your design is filled and any any patch metal is already inserted.
qinvs_eco --use_postroute_finishing
As far as the ECO goes, this should just be a standard deletion of the gate array cell and placement of the new gate array logical cell. Any gaps need a smaller gate array cell inserted.
Is this a real ECO for you or are you just interested in the process? If this is real, please keep DA in the loop with any learning or problems.
RTO:
We used bcalibre for the split Artwork Release on hammer. Here is the run.rto script I used. The resulting xor.sum
is what I provided to the tapeout team in Allentown.
tech=tsmc3ffe_M1_1Mxa_1Mxb_1Mxc_1Mxd_1Mya_1Myb_6My_2Myy_2Myx_2Mr_1UTRDL
newOas=/project/hammer/giant/giant-2023.10.0.FN0/user/tomob/hammer_FN.0_fp12.27Jan2024/impl/chip_top/aa.4_24.db/outputs/data/chip_top.oas
refOas=/project/hammer/giant/giant-2023.10.0.FN0/user/tomob/hammer_FN.0_fp12.27Jan2024/impl/chip_top/aa.4_23.db/outputs/data/chip_top.oas
block=chip_top
/projects/bcm/bin/bcalibre \
--tech=$tech \
--64 \
--lsf \
--cpu=192 \
--que=priority \
--R="rusage[mem=3840000]" \
--R="span[ptile=48]" \
--barq="-K" \
--beta \
--cmp \
--cal="OUT_LAYOUT_SOURCE=cal_ascii" \
--cal="OUT_LAYOUT_FORMAT=ASCII" \
--cal="OUT_SUMMARY_REPORT=xor.sum" \
--oas=$newOas \
--cell=$block \
--ref=$refOas \
--cell2=$block \
--rto="CM0,M1,M2,M4,M16,M17,M18,M19,VIA1,VIA2,VIA3,VIA4,VIA16,VIA17,VIA18"