Skip to content

Add fixed ASAP7 1x tech LEF for M1-M3 - #4532

Merged
maliberty merged 1 commit into
The-OpenROAD-Project:masterfrom
LeeJaKang:JKL/asap7-tech-lef-m1-m3-drc
Sep 16, 2026
Merged

maliberty merged 1 commit into
The-OpenROAD-Project:masterfrom
LeeJaKang:JKL/asap7-tech-lef-m1-m3-drc

Conversation

@LeeJaKang

@LeeJaKang LeeJaKang commented Sep 13, 2026 •

Copy link
Copy Markdown
Contributor

Summary

This adds a new file, flow/platforms/asap7/lef/asap7_tech_1x_260907.lef. It is the same as
asap7_tech_1x_201209.lef, but with fixes to layers M1, M2, and M3. The fixes make
these layers match the ASAP7 Design Rule Manual
and the original ASAP7 paper. This PR only adds a new file. It does not change the old
file. So nothing that uses asap7_tech_1x_201209.lef will break.

What changed (only layers M1-M3, layers M4-M9 are the same)

  • Min area (M1, M2, M3): AREA 0.000666 -> AREA 0.000504 um^2. Matches
    M1.A.1 / M2.A.1 / M3.A.1.
  • End-of-line spacing (M2): LEF58_SPACING ... WITHIN 0.02 -> WITHIN 0. With
    WITHIN 0.02 on, cases that should be checked as corner-to-corner (M2.S.6) were
    instead checked as tip-to-tip (M2.S.4).
  • Width (M2, M3): removed LEF58_WIDTHTABLE
    (WIDTHTABLE 0.018 0.09 0.162 0.234 0.306 0.378). This rule only exists for M4-M7
    (M4.W.3 / M4.W.4).
  • Grid (M2, M3): removed LEF58_RIGHTWAYONGRIDONLY. M4.AUX.2 is M4-M7 only.
  • Rectangle-only shapes (M2, M3): removed LEF58_RECTONLY. M4.AUX.3
    ("may not bend") is M4-M7 only.
  • Corner spacing (M2, M3): CORNERSPACING CONVEXCORNER WIDTH 0.0 SPACING 0.02
    -> adds CORNERONLY 0.02. Matches M2.S.6, corner-to-corner spacing >= 20 nm.

Related pull request

The same content is also included in The-OpenROAD-Project/asap7sc7p5t_28#9.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new LEF technology file, asap7_tech_1x_260907.lef, for the ASAP7 platform. The review feedback identifies a minor issue where the TYPE ROUTING ; and DIRECTION VERTICAL ; statements are duplicated within the LAYER M7 block, which should be cleaned up to prevent parser warnings.

Comment on lines +496 to +497
TYPE ROUTING ;
DIRECTION VERTICAL ;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The statements TYPE ROUTING ; and DIRECTION VERTICAL ; are duplicated on lines 496-497 within the LAYER M7 block. They are already defined on lines 483-484. These redundant lines should be removed to keep the LEF file clean and avoid potential parser warnings or errors.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not new but worth fixing.

Signed-off-by: LeeJaKang <wkrkd95@postech.ac.kr>
@LeeJaKang
LeeJaKang force-pushed the JKL/asap7-tech-lef-m1-m3-drc branch from 4792394 to db813d4 Compare September 13, 2026 01:16
@openroad-ci

openroad-ci commented Sep 13, 2026 •

Copy link
Copy Markdown
Member

🔍 QoR check

Metrics reflect the PR merge build — i.e. what will land on the target branch.

Commit 5d8d32c · Jenkins build #3 · Baseline: build · View build on dashboard

62 design(s) checked — 0 with regression(s), 0 without a comparable baseline.

@maliberty

Copy link
Copy Markdown
Member

I've assumed that the LEF58_RIGHTWAYONGRIDONLY & LEF58_RECTONLY were representing double patterning. If you remove them then you should add a MASK statement if they are such. Please clarify.

@LeeJaKang

Copy link
Copy Markdown
Contributor Author

Yes, that is correct. Those rules were added due to multi-patterning.
However, M1–M3 in ASAP7 use single-patterning EUV.
Please refer to both Section 3.1." Layers" and Section 4.4, “BEOL Design Rules” in the following paper:

https://www.sciencedirect.com/science/article/pii/S002626921630026X

I have also attached the image below for reference.

image image

@maliberty

Copy link
Copy Markdown
Member

Thanks. This PR doesn't actually switch to using the new tech but we can take that up in another PR.

@maliberty
maliberty merged commit fbc8fa4 into The-OpenROAD-Project:master Sep 16, 2026
11 of 12 checks passed
openroad-ci pushed a commit to The-OpenROAD-Project-staging/OpenROAD-flow-scripts that referenced this pull request Oct 26, 2026
Signed-off-by: Matt Liberty <mliberty@precisioninno.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants